The complete solution
contract, then harness, then loop
green = harness / deterministic
purple = the model
red = blocked
An agent dropped in a real repo
invents requirements that look mergeable
context compacts - the work vanishes
one bad turn reads .env or commits to main
no explicit model - the bill runs away
idea / notes / transcript / legacy docs
↓
spec-builder
↓
docs/specs/ - 13 sections
stable FR IDs + acceptance criteria
never invents a requirement:
unstated -> AS-nn assumption / OI-nn open issue
harness-bootstrap
↓
reads your code FIRST
↓
.claude/
15 agents
model + effort
14 rules
6 always, 8 scoped
14 commands
6 blocking hooks
docs/tasks/ - a board that survives a crash
scaffold: ~0.2s
reconciles, never overwrites
The delivery loop runs inside it
dispatches
records progress
orchestrator
scoped specialist agents
docs/tasks/ board
on disk
hooks
BLOCKED
not "advised against"
The payoff
the contract exists
the harness cannot be escaped
state survives a crash
the bill is chosen, not inherited
guardrail eval 15/15
Opus -> Haiku: byte-identical safety
shell scripts + glob rules | ports to Claude Code, Cursor and Codex with enforcement