Try Intent-System→
Product

Review is intent diffing. Closeout sets up the next slice.

Intent-System's unit of work is the loop, not the PR. The full cycle is issue → implement → review → fix → accept → closeout → next-slice. Timer-loop mode and Orchestrator Mode use the same review logic; they differ in how work is delegated.

Intent-System · Step 7 of 8↑ Overview
  1. 01Current Flow
  2. 023 Threads × 6 Steps
  3. 03Orchestrator Mode
  4. 04Intent Tree
  5. 05Unified Intents
  6. 06Human + AI Assignment
  7. 07Review & Closeout Loop
  8. 08Roadmap

The seven steps

01
Packet generation
The design thread asks the LLM to slice the intent tree into packets — work units one level above an Issue that carry references to intent and explicit verification points. Before promotion, the design thread also runs the merged app and folds screen-level observations into the packet.
02
Issue cut
A packet with high enough DIF and resolved dependencies becomes an Issue in the implementation repo. The Issue already carries why we build this.
03
Implement
The implementation thread reads the packet/intent, implements, and opens a PR against the target branch. It can be driven by the established timer loop or by an Orchestrator Mode message.
04
Review
The review thread in a different cwd diffs the PR against the packet and intent tree. Findings: pass, repair-in-place, or repair the intent. A human gives final approval before merge.
05
Fix
If repair-in-place: the implementation thread applies the fix to its own PR, pushes, and hands the updated PR back to the review thread. If repair-the-intent: a clarification flows back to the design thread.
06
Accept + closeout
PR merges into ai-develop. The diff is written back into the intent tree as canonical, and state files (queue, runs) are updated.
07
Next-packet re-evaluation
On Approve the loop rewinds to step 01: from the post-merge tree, the design thread re-evaluates which packet to generate next. This rewind is what keeps the next work unit flowing reliably.
Orchestrator Mode

The review rule stays the same

In Orchestrator Mode, the review receiver waits for a concrete message instead of polling on its own timer. After it replies, the orchestrator verifies the claim against intent-cli and GitHub before merge, closeout, or next-slice publication. Read Orchestrator Mode →

Three review outcomes

  • Pass. Implementation honors intent. Proceed to closeout.
  • Repair-in-place. Implementation needs adjustment; intent stands. Implementer fixes the PR.
  • Repair-the-intent. The intent itself was wrong or ambiguous. A clarification flows back to Ⓐ-③.
Try Intent-System→