Context Architect
The strategic role responsible for translating business needs into machine-readable Live Specs and curating the Context Index that feeds agent execution.
Definition
The Context Architect is the strategic role responsible for translating business requirements into machine-readable Live Specs and curating the Context Index that agents consume during execution. In the Triangular Workflow, the Context Architect occupies the "Why and What" vertex — defining what needs to be built and ensuring agents have the structured knowledge required to build it.
The role maps most closely to the traditional Product Manager, but the shift is significant. Instead of writing user stories for human developers to interpret, the Context Architect engineers specifications that must be precise enough for an LLM to execute without ambiguity. Vague acceptance criteria that a human developer could resolve through conversation become blockers that stall agent pipelines.
Core duties include:
- Drafting Live Specs — authoring Live Specs with precise behavioral contracts, acceptance criteria, and references to Golden Samples. Each spec must be self-contained enough for an agent to implement without additional clarification.
- Curating the Context Index — maintaining the Context Index as a structured knowledge base that agents draw from during execution. This includes API schemas, architectural documentation, domain glossaries, and code conventions.
- Configuring HITL Gates — defining where human-in-the-loop checkpoints occur in the agent pipeline, balancing autonomy with oversight based on task risk and complexity.
Key skills for the Context Architect include logical architecture (decomposing business requirements into discrete, implementable units), data organization (structuring knowledge so that machines can retrieve and apply it effectively), and stakeholder diplomacy (translating between business language and technical specifications).
The Context Architect's output quality directly determines agent success rates. When the Correction Ratio is high or the Spec-to-Code Ratio is low, the root cause often traces back to spec quality — making this role the single highest-leverage position in an agentic team.