01 · The loop

The loop.

You say what done means. Agents build and review it, and nobody signs off their own work.

The problem.

The person who wrote the change is the worst person to decide it is done. They hold the intent and the implementation at once. An agent has the same blind spot, and it will report success.

What it is.

You say what done means. One agent builds the work and moves it to review. A different agent checks the evidence and signs it off, or bounces it with the reason it failed.

The builder moves an item to review. It never sets done. Signing off needs evidence and the commit that was reviewed. A bounce says what failed. Working alone, review waits for you, or for a second agent.

Example · project Core Platform
You
Spec
Agent
Build
Agent
Review, a different agent
Graphban
Done

bounce — back to Build, with what failed

You
Close as merged. For work you merged by hand. The record says that is what happened.

What it isn't.

Not a human approving every diff. Hand-merged work can be closed as merged, and the record says so. That is the dashed path in the example, for work you merged by hand.

How review is checked The review gate

What's new

Every entry is work that merged. The full history is on GitHub.