“A dialect is OWNED, not ASSEMBLED. A song that wears one region's particles, another's pronouns, and a third's slang reads as tourism, regardless of how grammatically Spanish each fragment is. Coherence beats coverage.”
Surfaced:Build 2940 (Latin Excellence WAR Room §1 closing argument, ratified at the close of the 15-build L1-L13 arc B2926-B2939). WAR Room Panels E + I — linguists/dialectologists + adversarial/competitive — surfaced this when arguing what makes Latin lyric generation distinctive. Spanish has three major lyric-engine traditions sharing one grammar but diverging on particles, pronouns, syntax, phonological reduction, and slang. Mixing markers across regions is the genre's distinctive failure mode; native listeners hear region mismatch instantly.
The anti-pattern this names
Generic LLM Spanish-language output mixes dialect markers across regions because the model treats Spanish as one register with vocabulary substitutions. A line with Mexican "ándele" + Puerto Rican "¿qué tú quieres?" + Iberian "chaval" is grammatically correct Spanish but reads as tourism — written by someone who studied the regions from outside rather than by someone who inhabits one of them. The opposite failure (Tourist Spanish — grammatically correct but identity-less, region-free Duolingo Latin) is equally a dialect-ownership failure. Both are caught by the same principle: coherence beats coverage.
The check
The 15-build Latin Excellence WAR Room (B2926-B2940 / L1-L13) ships the dialect-ownership test as system enforcement. The L6 DCS (Dialect Consistency Score) deterministically detects cross-region marker conflicts. The L8 DCT (Dialect Coherence Test, Haiku-judged) catches the subtler Tourist Spanish failure that DCS misses (grammatically correct but identity-less). The L9 critic flags Region Salad + Tourist Spanish + Slang Spam + Translated English Underneath by canonical name. The L11.5 corpus calibration enforces the rule via 40 verified-hit credential-validated anchors across 4 lanes. The L12 forge amendment gates output with the LANE-FIRST commitment — forge declares lane + dialect + persona BEFORE writing line one. Future genres where dialect coherence matters (Worship Anthem regional varieties, Latin-American sub-regions, African-language pop) inherit this pattern. Canonical phrasing: `BRAND.sacredAccident22`.
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.sacredAccident22 · Doc: docs/SACRED-ACCIDENTS.md