greenfield-forgelisted

# Greenfield Forge ## What this is The forward mirror of `codebase-rescue`. Rescue is **curative** — it takes an existing, misaligned, often AI-generated mess and reconciles it. Greenfield Forge is **preventive** — it builds a new project aligned and intentional from the first commit, so the slop never accrues. Same engine, opposite direction along the project lifecycle. Its center of gravity is the same as rescue's: **architectural, cross-layer design** — the data model, the module boundaries, the contracts between backend / frontend / DB — decided deliberately instead of emerging by accident. It is NOT a scaffolding generator that dumps a boilerplate template; the template is the commoditized, easy part. ### The one idea that organizes everything Same invariant as rescue: **`gap = diff(to-be, as-is)`.** What changes is where you start: - **as-is** — what is built so far. In greenfield it starts **empty** and grows. - **to-be** — what each part should be. It is **elected up front** in a decision interview, derived from the user's choices, never invented by the model. > The gap is the **build backlog**, sequenced by dependencies. As slices complete, `as-is` grows > to meet `to-be` and the gap converges to zero. A finished v1 is `gap = 0`. Because the to-be is recorded as you decide it, the project carries its own `ledger.json` — the living record of *why it is the way it is*, each decision tagged with the condition that would reopen it (`flip_criteria`). That is pre