The loop, not the slide about the loop
Watch a single change ride the four beats
Every page in this standard describes the loop. This one shows it. A real spec on a real repo — Harbor Claims — goes from a written intent to a deployed change, and you watch the four beats happen in order: Orient, Delegate, Verify, Discern. Nothing is re-enacted; the pull request, the gates, and the sign-off are the real ones.
If you are new here, watch them in order — each clip picks up where the last one ends. If you just want the whole thing, the full module is at the bottom.
Four beats · four clips
The loop, one beat at a time
Orient
Before you touch a file, you read the spec and the rails around it — what “done” means, and what the machine will refuse. You are setting the box the agent works inside.
≈ 4 minDelegate
The agent plans first, you approve the plan, then it builds and self-checks inside the scope and permissions you gave it. You are supervising the work, not typing it.
≈ 2 minVerify
Opening the pull request fires the gates: build and tests, a security pass, a correctness review, and a grader that re-reads the spec cold. Green everywhere — and it still says not done.
≈ 2 minDiscern
The judgment calls the machine surfaced but wouldn’t settle. A high-risk label, a named sign-off that isn’t you, and the merge that ships to deploy. The name on the decision stays human.
≈ 2 minVideos are hosted as release assets and stream on demand — nothing downloads until you press play.
All four, stitched
The full loop, end to end
The same four beats as one continuous film, with title cards between them — the version to put on a screen when you are showing someone the method for the first time.
A Day in the Loop
Orient → Delegate → Verify → Discern, uncut. Roughly ten minutes.