flow

# /flow — buildflow gated build harness Idea to a **deployed URL**, not idea to paperwork. You walk gated stages; each has an **output artifact** and a **GATE** — a checklist that must be honestly satisfied before you advance. **Kill at any gate is a valid, honored outcome** (killing a weak idea at Scope is cheap and smart). ``` Idea -> Research -> Scope -> PRD -> ADR -> Contract -> Cards -> Build -> Review -> Deploy -> Verify-live -> Retro |------------------ planning (files in flow/) ------------------| |------- shipping (inside cards/) -------| ``` ## Two-layer harness (this is the core idea) `/flow` is **two layers working together**: 1. **Mechanical layer — `runner/flow.sh`** (deterministic, exit 0/1). It manages the stage/card lifecycle and checks the *cheatable* things: unchecked gate boxes, leftover `[FILL]` placeholders, card status validity, empty done-evidence. Always run it first — its exit code is ground truth, never your own judgment. 2. **Semantic layer — YOU (Claude), via this skill** (quality gatekeeper). The script cannot tell a real competitor quote from a fabricated one, or a grade-laundered C feature from an honest B. **That is your job.** After the script passes, apply the per-stage challenges in `references/gate-rules.md` before you let the operator advance. A gate is only truly passed when **both** layers agree. The script can pass while the content is hollow — catch that. ## Running the mechanical layer From the **project ro...