The business outcome
Faster delivery with less rework. When agents start from the right information, work ships sooner and comes back for correction less often, and your AI spend stops growing with every re-explained session.
Before investment
Every session starts from zero. Engineers paste in whatever background they remember, results depend on who wrote the prompt, and agents build confidently on facts that stopped being true a sprint ago. Senior people spend their afternoons repeating themselves and correcting what comes back.
After investment
The background is simply there. An agent picks up a task the way a well-onboarded hire would, already knowing your conventions and history, and the questions it asks are about the genuinely new parts of the problem. Quality stops depending on who typed the prompt.
Collection
An agent can only act on what it can see. Collection is the discipline of putting the right material in front of it: the meeting transcripts where a decision actually got made, the code and its git history, the wiki or knowledge base, the epics and tickets that say what the work is for.
The question
When a new agent picks up a task, does it have the transcripts, tickets, and code it needs, or is someone hand-feeding it every time?
Management
What your agent collected on day one quietly goes out of date. Conventions get revised, specs get superseded, architectural decisions get reversed, and the documents that record all of it drift the moment they stop being anyone's job. Management is the discipline of catching that drift: the CLAUDE.md that still names last quarter's stack, the decision the team walked back but never wrote down, the spec that says one thing while the code does another.
The question
Is the context an agent reads current, or three sprints stale?
Disclosure
Your agent can have everything it needs gathered and current and still drown in it. Disclosure is the discipline of matching what you serve to the task at hand: a focused set of requirements rather than every doc in the repo, an index that routes the agent to the one file it needs rather than pasting all of them in, an orientation note that points, not dumps. It covers picking up where the last session stopped, too: a fresh session starts empty, and re-priming it with the state of the work lets the agent resume instead of starting over.
The question
Do we feed it the right slice at the right moment, or dump everything and hope?
In your org, each of these disciplines already sits at one of four investment tiers: , , , or . Every discipline page walks all four: what each tier buys, what it costs to maintain, and the techniques that get you there.
Context's three disciplines look like separate jobs, but they hold each other up. The returns compound where you invest on both sides of an overlap, and the gaps hide there too. These are the pairings worth reading as one decision.
Within Context
Collection and Management
Collection gets an artifact in the door; Management keeps it true. The wider Collection reaches, the more surface Management has to hold current, and gathering aggressively without the upkeep just delivers stale context at scale.
Fund both and a broad corpus stays trustworthy; fund only the first and you have paid to mislead the agent faster.
Collection and Disclosure
Collection decides what exists for the agent to see; Disclosure decides what actually reaches a given session. A complete corpus is only an asset if the routing can find the one slice a task needs inside it, and one dumped whole is worse than a small, well-aimed one.
The value is in the pair: gather widely, then serve narrowly.
Management and Disclosure
Management makes sure an artifact is still true; Disclosure makes sure the agent reads it at the right moment. The leanest, best-routed context is still wrong if it points at a doc that went stale months ago.
Currency without routing buries the truth; routing without currency delivers a falsehood on time.
Where Context reaches across
Management and Environment
ControlA convention starts in Management as a documented pattern the agent is meant to follow, and crosses into Environment the day you build it into a gate that will not let a change pass without it. It is one rule at two postures: written down it informs and can be ignored, enforced it stops the work until it is met.
Leave it in the doc and you are trusting everyone to remember it on a busy afternoon; promote it to a gate with no doc behind it and you get a red build no one can explain. The rule migrates across the line as the stakes climb, so keep the convention current where it lives and enforce only the few that have earned it.
Capability and Disclosure
ControlWhat an agent can actually do in a single session is a smaller thing than everything your org made reachable: it is the tools Capability connected and the slice of context Disclosure served this run, and nothing outside that. A capable agent handed a briefing that never mentions the tool for the job will not reach for it, and perfectly aimed context is inert the moment it depends on a system Capability keeps off the table.
Reach and briefing have to describe the same working set. Connect a tool without ever surfacing it and you have paid for an ability the agent is never told it has; serve a workflow built on access it does not have and you have written an instruction it cannot follow.
Collection and Capture
ObservabilityCollection and Capture are one instinct aimed in opposite directions: Collection gathers what an agent needs before a run, Capture records what it did after. They rhyme because the record Capture writes down (the decision made, the reasoning behind it, the transcript of how the work actually went) is exactly the kind of artifact Collection exists to feed the next agent.
Instrument every run but never gather from what you logged and a true account of how your team works with AI piles up unread; gather diligently while capturing nothing and you curate only the sources that predate your agents, missing the richest one. The payoff is a loop: the exhaust of one session becomes the context that orients the next.
The agent has what it needs to act.
- CollectionGetting context in: gathering the artifacts an agent needs to orient.
- ManagementKeeping the context your agents read current as decisions and conventions change.
- DisclosureFeeding context in efficiently: routing the agent to the slice it needs, not a data dump.
The agent can only do what it should.
- CapabilityWhat the agent can do: the tools you connect, and the ones you deliberately withhold.
- DelegationWhat the agent should do: the responsibilities you hand over, and the ones you reserve.
- EnvironmentThe system the agent works within: the tests and gates its work must clear, and the points where a human takes over.
The human can see what happened.
- CaptureMaking sure every run leaves a raw record.
- AvailabilityPutting the record of agent work where your team can query and review it.
- TraceWalking back through a single run, end to end, with the reasoning alongside the decisions.
The team gets better over time.
- EvaluationMeasuring whether your processes work, by the numbers and by gut-check.
- PrioritizationChoosing what to change and where to invest next.
- ConvergenceMaking a change stick across the team.