Case study · From the Factory’s own records
One task, start to finish. With receipts.
Pet Rap Sheet was built by my delivery loop: a conductor of about 2.9k lines of TypeScript that owns the commits, checks and merges, while agents in threads only write and review. I wrote the brief and the acceptance criteria. This is task 31, exactly as the records show it.
-
01
Brief
Task 31 of 33: the booking flow and the mugshot document. Risk: low. The conductor picked a worker, Claude Opus, saved that intent, then launched it in its own worktree.
WORKER · claude-opus-5-5 · worktree sdlc/t31 -
02
Check failed
The conductor committed the worker’s edit and ran the project’s checks in a throwaway snapshot of that exact commit. One of 26 unit tests failed, a screenshot assertion. The real output went back to the same worker thread.
001-check-c25d6c2.log · EXIT 1 · 57.5 S -
03
Check passed
Second commit, same checks, exit zero. The exit code is the truth; no agent gets to say a check passed.
002-check-7d49b29.log · EXIT 0 · 58.8 S -
04
Review: changes
A reviewer from a different model family, GPT, read the snapshot and answered in JSON. Its blocker named a file, a line and a reachable scenario: pick a JPEG with EXIF orientation 2, a mirrored photo. The loader only rotated images, so mirrored ones came out reversed.
REVIEWER · gpt-6-astra · PhotoLoader.kt:28 · VERDICT changes -
05
Fix, with proof
The worker handled all eight EXIF orientations and wrote a test that tags a 40×20 JPEG with each one and checks three corners. With the old loader put back, the test fails: it expected green and got red, the unflipped pixels.
PhotoLoaderTest.appliesEveryExifOrientationIncludingMirrors -
06
Approved, merged
Round two: approve, no blockers. The conductor rebased, re-ran the checks, fast-forwarded and pushed to a remote it had verified was private. Thread archived, worktree removed.
3de05fb · EXIT 0 · 60.3 S · REVIEW r2 approve
The rules the code enforces
- Agents never commit, push, merge or write task state.
- Every blocker must name a file, a line and a reachable scenario.
- Malformed JSON is never approval.
- Three check rounds, two review rounds; after that, it asks me.
See the app it shipped ↗ · Lookout, the same idea applied to testing →