Triangular Workflow
The three-role execution model where a Context Architect defines specs, an agent implements, and an Agent Operator provides oversight.
Definition
The Triangular Workflow is the three-role execution model that replaces the traditional developer-centric workflow in agentic teams. Instead of a single developer owning a task from requirements through implementation to review, the work is distributed across three roles that operate at different levels of abstraction: Context Architect, Agent, and Agent Operator.
Each vertex of the triangle handles a distinct concern:
- Context Architect (Why and What) — translates business requirements into Live Specs with precise behavioral contracts, acceptance criteria, and Golden Samples. This role owns the specification quality that determines agent success.
- Agent (How) — receives the Live Spec and assembled Context Packet, then implements the solution within its Token Budget. The agent operates autonomously until it either completes the task or raises a Blocker Flag.
- Agent Operator (Oversight and Escalation) — monitors agent execution, responds to Blocker Flags with Rescue Missions, and reviews agent output that passes the Eval Harness.
The feedback triangle creates a continuous improvement cycle. When an agent raises a Blocker Flag, the operator diagnoses the root cause. If the cause is a spec gap, that feedback flows back to the Context Architect, who updates the Live Spec. If the cause is a context deficiency, the Context Index is enriched. This feedback loop means each execution cycle improves the inputs for the next.
The Triangular Workflow differs from traditional development in a key structural way: no single person writes and reviews their own code. The separation between specification (Context Architect), implementation (Agent), and validation (Agent Operator) creates natural checkpoints that reduce errors and enforce accountability.