“A genre we cannot evaluate cannot be a genre we can serve. Before declaring a genre supported, we need an audit primitive set that can DIAGNOSE why a song in that genre fails — not just whether it passes a generic quality rubric.”
Surfaced:Build 2860 (Rap Excellence WAR Room §8 Round 99, ratified at the close of the 20-build WAR Room arc B2838-B2859). Operator brief at the WAR Room's open: "Our system does not create rap lyrics all that well. I would like you to do deep research to achieve a massive upgrade for the rap genre." Round 99 asked: why did rap quality slip below default-genre quality for so long? Because audit primitives existed for the genres the panel could feel (Americana, folk, conscious pop) but rap shipped with a single mode + single rubric-weight override. The composite was correctly weighted; the PER-BAR DIAGNOSIS of why a rap verse fails (dead bar, slant at peak, hook obscuration, run-on) was never encoded.
The anti-pattern this names
SongForgeAI scores all genres against the 12-metric quality rubric. The rubric's pass/fail signal is sufficient for genres the panel can feel intuitively (the panel's literary anchors carry the diagnostic load). For genres the panel CANNOT feel — genres with their own technical vocabulary, conventions, and failure modes — the rubric is necessary but insufficient. Saying "M3 = 62" tells the operator the song is bad at rhyme intelligence; it does NOT tell them WHICH bar leaned on a forced rhyme, or that bar 7 hook-obscures, or that the verse violates the subgenre's syllable band. Without per-bar diagnosis, the operator + the forge cannot improve the song iteratively — they can only re-roll.
The check
The 20-build Rap Excellence WAR Room (B2838-B2859) is the proof-of-concept implementation. Phonology layer (B2838) + phoneme-aware audit (B2839) + 5 subgenre profiles (B2840) + 9-dimension critic loop (B2842) + per-bar validator (B2844) + corpus calibration loop (B2848-B2850) + public doc surface (B2857). When future genres need this depth, the pattern is inherited: domain-specific diagnostic substrate → audit primitives → subgenre profiles → diagnosis layer → calibration → public docs. Canonical phrasing: `BRAND.sacredAccident19`.
Share this discipline
“A genre we cannot evaluate cannot be a genre we can serve. Before declaring a genre supported, we need audit primitives that can DIAGNOSE why a song fails — not just whether it passes a generic rubric. — Sacred Accident #19”
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.sacredAccident19 · Doc: docs/SACRED-ACCIDENTS.md