Ratchet — one-pager

Print tip: For best results open one-pager-print and use File → Print (or Save as PDF). This Markdown page is the same content for editors that don’t open HTML.

What it is

Self-hosted AI build-and-verify control plane. Human types a goal → system queues missions → AI builder pushes code → deploy gate waits for live version signal → AI tester grades the live site → repeat until a streak of passes. Name = contract: only moves forward.

Happy path

flowchart LR
  H[Goal] --> C[Composer]
  C --> Q[Queue]
  Q --> B[Build]
  B --> D[Deploy gate]
  D --> T[Test]
  T -->|FAIL| B
  T -->|PASS streak| OK[Done]

Stack (roles)

Non‑negotiables

1. Live is truth — tester hits the live URL, not the local tree
2. Version signal — product must return the deployed git SHA for the deploy gate
3. Proof of work — loop checks git; ignore agent claims
4. Streak — usually several consecutive passes
5. No secrets in builder env — credentials boundary only
6. Team git author — unknown bot authors may be blocked by hosts
7. Multi-step goals → several focused queue items; bind cloud project identities
8. Credentials stay brokered — builder and tester never hold cloud tokens

Loop outcomes (concepts)

Mental model

Composer = factory office · Ratchet = factory floor · Vault = key cabinet · Product version signal = time clock.

Rebuild in one breath

Model CLIs → control plane + harness + product shells → credentials boundary → mock loop → product with version signal → tiny real mission → docs pack for friends/AIs.

Share / go deeper

No secrets in this pack. Guide pack v1.2 · product design reference only.