How to read this book
Chapters build in order, concept before command. Every APM feature is introduced as the implementation of one of four properties — Portability Reproducibility Security Governance.
For engineering leaders
Skim the For engineering leaders asides for the risk, ROI, onboarding, and governance story.
Start with Chapter 1A recurring Meridian marker tracks what one team does next, chapter by chapter.
The reading path
Twelve chapters, six parts
Chapters resolve in order — each one depends on the ones before it, like a dependency graph. Read straight through, or jump to the part you need.
Why context needs a manifest
-
ch01
The Context Problem
Articulate why agent context needs a package manager and name the four properties APM is designed to protect.
-
ch02
Lessons from Package Managers
Map package-manager concepts onto agent context so APM feels familiar rather than novel.
-
ch03
Primitives & Harnesses
Know the vocabulary of what APM manages and how those primitives relate to agent harnesses.
Portable by manifest
-
ch04
The Manifest: apm.yml
Author a valid apm.yml that declares Meridian's first shared agent-context dependencies.
-
ch05
Install & Restore
Install and restore a project's agent context with the daily APM consumer loop.
Reproducible by lockfile
-
ch06
The Lockfile & Reproducibility
Reproduce an APM setup exactly and explain how the lockfile supports that guarantee.
-
ch07
Lifecycle
Keep APM dependencies current while detecting drift and risk deliberately.
Secure & governed
-
ch08
Security by Default
Understand and rely on APM's install-time security checks without confusing them with runtime sandboxing.
-
ch09
Governance & Policy
Write and pilot an apm-policy.yml that enforces agent-package rules at install time.
Producing & sharing
-
ch10
Becoming a Producer
Package and publish reusable APM primitives so other teams can consume them through the normal install loop.
At scale & ahead
-
ch11
Enterprise at Fleet Scale
Gate and govern APM usage across an organization without turning developer setup into a bottleneck.
-
ch12
The Landscape & What's Next
Place APM in the market and standards landscape, then decide what to adopt, watch, or build around.