“Quality is not universal; register defines craft. Different emotional registers (joy / grief / rage / lust / swagger / awe / tenderness) require different craft rules. Specificity-via-restraint is the right rubric for indie folk grief; it is the wrong rubric for pop joy, hip-hop swagger, dance-floor euphoria, or worship transcendence. A system trained on one register's craft will optimize every song toward that register regardless of what the user asked for. The corollary: a system trained to write "good" songs delivers "good" songs even when the user asked for "fun" ones.”
Surfaced:Build 3372 (Main Character Energy WAR ROOM). Operator surfaced a real-world failure: a "main character energy" prompt asking for upbeat, joyful, energetic, sudden bold living returned three meditative-introspective songs about gradual healing, identity loss, and confidence rehearsal. Quantified deficits: 4 active verbs across all 3 songs vs 15+ requested; ~3/10 valence vs 8+/10 requested; meditative ~65 BPM vs energetic ~120+ BPM requested; private rehearsal vs public bold acts; 2-year/6-month gradual healing vs "suddenly feeling like." The cultural-register diagnosis: the user asked for the TikTok / IG "main character energy" phenomenon (Lizzo "About Damn Time" — joyful, energetic, bold); the system delivered singer-songwriter "quiet resilience" (Phoebe Bridgers "Moon Song" — bittersweet, reflective, melancholic). This validated the B3366 corpus-audit prediction empirically: the system's introspective-register dialect overrides explicit prompt instructions. The B3371 CI ratchet had already confirmed the dialect lives in the system's BEST output (top500 anchors carry more dialect density than bottom500). SA#32 names the lesson: applying one register's rubric to every prompt produces register-blind output.
The anti-pattern this names
A single craft rubric (anti-inflation rules, specificity floors, restraint-rewarding critic voices) ships as universal. The rubric is calibrated for ONE emotional register — typically the register the operator-original anchors live in. When the user prompts for a different register (joy, swagger, rage, lust, awe), the system runs the prompt through the same rubric, optimizes toward the same metrics, and produces a song in the original register with the new prompt's surface details. A pop banger that needs "high active-verb density, present-tense dominance, public scene-setting, body-in-motion, repetition as celebration" gets refined toward "specificity through restraint, body as witness, object as relic, silence as resolution." The user reads the result, thinks the system misunderstood the prompt — but the deeper failure is that the system was register-deaf from the rubric-design moment. Symptoms across registers: joy prompts return melancholic ballads; swagger prompts return self-doubt; rage prompts return resigned acceptance; lust prompts return wistful longing. Each is the home-register output dressed in the prompt's subject matter.
The check
Every quality-of-craft system that scores or refines lyric output must operate per-register, not universally. The discipline: (1) Brief schema carries a typed ToneRegister field (joy / grief / rage / lust / swagger / awe / tenderness / melancholy / defiance / playfulness). The brief extractor surfaces it from prompt text; the default is unset (no register lean). (2) Forge prompt includes a per-register block when the field is set — explicit instructions for what the target register requires (active-verb density floor, tense dominance, scene-setting, body register, repetition discipline). (3) Negative anchor pool per non-default register — explicit "do NOT sound like this when register X is set" exemplars. The current positive-anchor corpus may itself be a negative anchor for non-introspective registers. (4) Critic voices reweighted per register — anti-cliché reader and prosodist get muted in joy/swagger mode; hook architect and vocal coach get boosted. (5) Anti-inflation rules per register — Gravity Rule / Burden of Proof / Antagonist Ceiling all carry register modifiers. The right rubric for grief is the wrong rubric for joy. (6) Per-register audit primitives — Active Verb Density (AVD), Body-In-Motion (BIM), Public Scene Density (PSD) — calibrated against per-register corpora per SA#30. (7) Per-register corpora — SA#30 ladder applies: corpus precedes calibration; calibration precedes detection. A joy-register positive anchor corpus is the calibration anchor for any "did the output land in joy register" detector. (8) Gauntlet register-aware — the refinement target shifts based on declared register; otherwise the gauntlet undoes the register. (9) Dashboard surface — the declared register is visible per song + the AVD or equivalent register-specific audit score is visible. When delivered output violated declared register, the gap is operator-visible. Relationship to SA#19: SA#19 ("A genre we cannot evaluate cannot be a genre we can serve") generalizes to register — "A register we cannot evaluate cannot be a register we can serve." Same discipline, different axis. Relationship to SA#28 / SA#29: emotional register is signal that must be plumbed as STATE per song, not parsed from prompt text on every forge call. Relationship to SA#30 / SA#31: per-register corpora (SA#30) + per-register pairwise calibration (SA#31) operationalize the discipline. Canonical phrasing: BRAND.sacredAccident32. Operator-facing arc: docs/WAR-ROOM-MAIN-CHARACTER-ENERGY-2026-05-27.md + docs/SACRED-ACCIDENTS.md (SA#32 section).
Share this discipline
“Quality is not universal; register defines craft. A system trained to write "good" songs delivers "good" songs even when the user asked for "fun" ones. Specificity-via-restraint is right for indie grief; wrong for pop joy. Each register needs its own rubric. — Sacred Accident #32”
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.sacredAccident32 · Doc: docs/SACRED-ACCIDENTS.md