Six explainer clips. They play here in the browser - no download needed. Every clip is captioned, so sound is not required.
The whole product in one clip: the four pain points, then spec-builder writing the contract, harness-bootstrap building the harness, the delivery loop running inside it, and the payoff. Each pain visibly flips from red to green as its fix lands.
An unconstrained agent hallucinates, forgets on compaction, and bills at the top tier. Two skills build a harness.
spec-builder writes the contract; harness-bootstrap reads the code and scaffolds in ~0.2s; then the task loop runs.
Deny list, hooks, path-scoped rules, review gates. The guardrails are shell scripts, so Opus to Haiku is identical safety.
Raw input to a contract: elicit, confirm the FR list first, scaffold the 13 sections, fill them in order, then the traceability check. Nothing is invented - anything unstated becomes a flagged AS-nn or OI-nn. Mirrors diagram 5 in docs/FLOWS.md.
Mode, then the mandatory codebase analysis and Inventory Report, intake and the tool questionnaire, a roster with explicit model and effort, the scaffold that reports ADDED / KEPT / CONFLICT and never clobbers, then orchestration wiring. Mirrors diagram 2 in docs/FLOWS.md.