ground-truth-gateslisted

# Ground-Truth Gates **The core finding:** more prose rules do not improve a capable model on verifiable work — its gating habits are already native. What is missing is **something to gate against**. Invest in executable ground truth, not in longer instructions. Build gates first where judgment work happens (classification, extraction, routing, prompt output) — that is where habits are weakest and where a gate converts open-ended quality into a number plus a diff. ## The one command Once `template/` has been copied into the project as `checks/` (wire-up below): ```bash bash checks/run-all.sh ``` Discovers every `checks/*/run.mjs` (plus optional `checks/project.sh`), runs each, prints `PASS`/`FAIL` per gate, exits non-zero if any fail. That is the commit/ship gate: "all green" stops being a claim and becomes a checked fact. ## The three gates | Gate | Question it answers | Where it pays | |---|---|---| | **golden** | "Is this prompt/classifier actually better, by how much, and which cases does it miss?" | LLM-judgment steps. | | **replay** | "Did my change alter output on real logged inputs, and exactly where?" | Refactors and regex/prompt tweaks over production data — catches silent drift reading the code cannot see. | | **project** | "Do build/tests/types/lint pass?" | Drop a `checks/project.sh` with `npm test`, `tsc --noEmit`, an SCA scan failing on critical/known-exploited (`npm audit` / `pip-audit`), etc. | A starter implementation lives in this skill's `template/