The forward flow is the default. Backflow is allowed but tightly controlled. Parallelization is discouraged by design. GI is depth-first, not breadth-first.
The Planner produces the Execution Plan: scope, constraints, invariants, integration surfaces, and risk notes. Once approved, the Builder begins execution.
The Builder uses AI to execute the plan: code, tests, migrations, refactors, and invariant validation. They keep AI aligned and correct missteps early.
The Reviewer checks intent alignment, invariant preservation, architectural correctness, domain boundary respect, and semantic coherence. If approved, the change merges and deploys to Ring 0 then Ring 1 automatically.
Their decisions control whether work proceeds, whether backflow occurs, whether the domain stops, and whether the system stays coherent.
Domain throughput depends on review capacity.
No nitpicking syntax or style. AI handles that upstream.
A reject signals semantic drift or a planning defect, not a typo.
No democratic review. No multiple approvals. One Reviewer is enough.
Each path has rules designed to minimize chaos and keep the pipeline depth-first.
Output does not match the plan; invariants violated; semantics incorrect; diff too unfocused.
Local and fast. Builder fixes immediately; no parallel tasks.
Planner misunderstood intent; direction is wrong even though output matches the plan.
Planner revises the plan incrementally; Builder resumes execution.
Plan is ambiguous, contract missing, dependency unknown, domain rule unclear.
Cheapest backflow when caught early. Builder stops; Planner clarifies in minutes/hours.
Builders work one plan at a time. Planners focus on one semantic framing at a time. Reviewers handle one review at a time. Backflow is resolved before new forward work begins.
Parallelization under AI acceleration creates thrash, ambiguity, and compounding semantic errors. GI is depth-first by design.