“Calibration precedes detection; corpus precedes calibration. Before claiming the system DETECTS a quality, the system must be able to CALIBRATE its detector against a real, traceable, inspectable ground truth — and that ground truth must be assembled as a corpus the operator owns. Without a corpus, every detector threshold is a guess; every claim is unfalsifiable.”
Surfaced:Build 3298 (The One Line WAR ROOM — 100-round audit). The product committed to a bet: detect ONE line per forged song that carries the unrepeatable signature of top-0.5% human writing. The first move every council voted unanimously for was NOT "build the detector" but "build the corpus the detector calibrates against." Operationalized across B3299-B3305 — corpus skeleton + 7-feature taxonomy + 9 structural invariants in CI (B3299), detector + 200 operator-original entries written by the operator themselves as ground truth (B3300), +50 operator-originals + ratio-based calibration that stays stable across corpus growth (B3301), OneLineGenerator with anti-optimization prompt + 250-line few-shot anchor pool (B3303), Haiku final-pass judge for the three features deterministic heuristics could not score (B3304), first public surface in the dossier where buyers see the detector's top candidate One Line + per-feature breakdown (B3305). 75% of the 336-entry corpus is operator-owned — no licensing surface, no third-party clearance, the calibration data is the product's own intellectual asset.
The anti-pattern this names
Detector built first, calibration handwaved. The shape is: someone codes up heuristic feature scorers, picks plausible thresholds by intuition, ships the detector as a public surface, and only later discovers that the thresholds are guesses because there is no inspectable ground truth to test against. When the system later misfires — flags lines that aren't canonical, misses lines that are — there is no trail to walk back. The fix invariably becomes "raise this threshold by 5" or "add another lexicon word", small patches that paper over the absence of foundational calibration data. The B3300 calibration test forced honesty here: three of the seven features failed the ratio test on the heuristic alone, which forced the Haiku judge in B3304. Without the corpus, the heuristic stubs would have shipped as if they worked + the misfires would have been invisible. The corpus made the limits of the heuristic legible.
The check
Before any future detector claim ships as a public surface, six steps in order: (1) Assemble a corpus of canonical examples + counter-examples, operator-owned where possible. (2) Tag the corpus against the taxonomy the detector will use, with inspectable + auditable tags — no opaque LLM grading at the calibration layer. (3) Validate the corpus with structural invariants in CI (sufficient examples per feature, balanced provenance, no orphan tags). (4) Calibrate the detector via a RANKING invariant (tagged > untagged) rather than absolute thresholds — ratio-based assertions stay stable as the corpus grows. (5) Surface the corpus' limits in detector output — when a feature can't be scored deterministically, fall back to an LLM judge with a clear isHeuristic flag in the result. (6) Never ship the detector as a public claim until steps 1-5 are green. The One Line arc B3299-B3305 IS the canonical implementation; future arcs (B3308 vault batch rank, future quality-of-craft surfaces) consume this ladder, they do not invent it. Relationship to SA#19 ("A genre we cannot evaluate cannot be a genre we can serve"): SA#19 is the genre-specific instance of SA#30. SA#30 is the parent discipline; SA#19 is the first place we put it to work. Canonical phrasing: `BRAND.sacredAccident30`. Operator-facing summary of the arc: docs/ONE-LINE.md.
Share this discipline
“Calibration precedes detection; corpus precedes calibration. Before claiming the system DETECTS a quality, the system must be able to CALIBRATE against a real, traceable ground truth — and that ground truth must be a corpus the operator owns. — Sacred Accident #30”
Why this gets its own permalink
Each Sacred Accident is a discipline this codebase operates under — a rule named on the public record, enforced in the build pipeline, and cited in every commit that advances the moat it protects. Permalinking each one turns the discipline into a teaching artifact: a buyer or partner who reads this page can cite the exact principle we operate under without grepping our docs.
Canonical phrasing: BRAND.sacredAccident30 · Doc: docs/SACRED-ACCIDENTS.md