make-factorylisted

# make-factory The meta-process for standing up a new sibling in the factory family. A factory turns a fuzzy idea into a finished, quality-assured artifact of ONE output type — *arrive at an idea → say ship it → know it's in good hands.* Existing legs: **code**, **research**, **landing-page** (see `factories/README.md`). The build is cheap because you don't hand-author the standards — the **research factory generates them**, and this skill supplies the conventions + the skeleton. ## Step 0 — the fit gate (say no here if it fails) **A factory only pays off where the output's *lit state* is machine-checkable.** The medium is light: code is inert until run, a page until a user flows through it. Ask: *can a machine verify the activated state (runs / renders / loads / reconciles / passes a spec)?* - **Yes** → build it. - **No** (taste-dominant: a song's soul, prose voice, a logo's beauty) → **don't build a factory** — build a helper for the mechanical spine only, and say so. A factory whose verify can't check what matters is a false-confidence checklist. Also gate on: is this **repeated** (not one-off) and **worth** the build? One-off → just do it. ## Step 1 — FRAME the two registers Name the output, then split its judgment layer by evidentiary strength (this is the honest core): - **Verify layer** — the parts with real, machine-checkable backing → **hard gates**. - **Advisory layer** — the parts that are taste/hypothesis (no controlled evidence) → **flag as suggestio