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

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.

A packet with high enough DIF and resolved dependencies becomes an Issue in the implementation repo. The Issue already carries why we build this.

The implementation thread — Claude on /loop 5m in its own cwd — reads the packet/intent, implements, and opens a PR against ai-develop.

The review thread — a separate Claude /loop 5m in a different cwd (e.g. *Review worktree) — 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.

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.

PR merges into ai-develop. The diff is written back into the intent tree as canonical, and state files (queue, runs) are updated.

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.