The Unified Context Layer
The layer every agent reads from and writes back to: services, owners, standards, docs generated inline, best practices codified into self-evolving libraries. The ADLC's answer to parallel hallucination.
A floor of specialist agents has a failure mode no single agent has: parallel hallucination. One agent guessing wrong is a bug. Ten agents each acting on their own slightly-wrong picture of the system — which services exist, who owns them, what the conventions are — is an incoherent machine that looks busy while drifting apart. The fix is not better agents. It's one shared picture: the unified context layer.
One source of truth, read and written
The context layer is the floor's collective memory — a live catalog every agent reads before acting and writes back to after:
- Services and ownership — what exists, who owns it, what tier it is, how it scores
- Standards — the conventions, security posture, and golden paths agents must build within
- Docs, generated inline — every phase writes documentation as it works, so the record is a by-product of the work rather than a chore after it
- Codified best practices — patterns that worked become named, reusable, self-evolving libraries: each run that touches one can improve it
The read path is what stops hallucination: the planning agent doesn't guess the service topology — it queries it. The write path is what makes the layer live: monitoring outcomes, review feedback, and shipped changes flow back in, so the next run starts from a truer picture than this one did.
This is the "context lake" pitch behind agentic SDLC platforms like Port — service catalog, scorecards, and workflow context in one queryable layer, so every agent in the pipeline pulls the same tier, team, and standards for a service instead of inferring them. In-house, the same role is played by a well-maintained Backstage catalog plus repo-level agent rules — anywhere the answer to "what is true about our system?" lives in one place agents can read.
The reveal
Step back and look at what this pillar assembled: specs and guardrails shaping behavior — instructions. Agents wielding CI, deploy, and rollback — tool interfaces with an execution environment. A pipeline of gates, retries, and human approval — orchestration. Specialist roles on the floor — sub-agents. Codified practices — skills. Receipts before ship — verification. A context layer feeding every decision — context assembly over shared memory. And a feedback agent turning failures into infrastructure — evolution.
The agentic SDLC isn't a new discipline. It's a harness at organizational scale — the same primitives you'd build around one model, built around a team. Same machine, bigger floor.