“The system can write a good song without writing the same song. The cure is fidelity as a first-class score, orthogonal to quality, surfaced as a separate grade.”
Surfaced:Build 2763 (5-song stress-test WAR Room × 100 rounds, May 2026). The operator ran a 5-song stress test with difficult prompts; the reviewer's response listed 10 concrete recommendations. Across them, ONE pattern emerged: 9 of 10 recommendations were special cases of the same parent failure mode — the model optimizes for craft and forgets the brief.
The anti-pattern this names
Quality measures "is this a good song"; fidelity measures "did this answer the question I asked?" They are independent axes. A song can be A+ quality + F fidelity (gorgeous, wrong prompt) or C+ quality + A+ fidelity (dutiful but bland). Both happen routinely. The 12-metric rubric has been measuring one axis for two years; the next leap is measuring both. Without fidelity scored separately, the system can ship "good" songs that drift from the user's brief and the rubric will reward them. A working writer who hands the system a specific brief and gets back a beautiful song about something else will (rightly) churn.
The check
21-build Constraint-Aware Forge (CAF) roadmap across 3 phases (Phase 1 = brief extractor + structure/thesis/specificity audits + pipeline wiring; Phase 2 = prompt amendments + chorus evolution planner + earned transcendence + conditional sensory rewrite + premise-match Haiku judgment + dashboard two-grade chip; Phase 3 = leaderboard composite + public docs at /scoring/standard/fidelity + RFC-0010 + ratchet CI gate + Rap Mode + npm package). All 21 items shipped between B2763–B2820. Trigger phrase: `Continue Constraint-Aware Forge`. Canonical phrasing: `BRAND.sacredAccident17`.
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.sacredAccident17 · Doc: docs/SACRED-ACCIDENTS.md