“The song must survive being heard once.”
Surfaced:Build 2662 WAR Room of the Memorial + Wedding song-creation pipeline — Round 83 (Panel groups B + F unanimous, refined R88, R93).
The anti-pattern this names
Memorial + wedding songs are usually heard exactly once in the context they were made for. Most listeners will not hear them attentively from start to finish. The radio-pop convention puts the most-cuttable line in the bridge or the final chorus — that convention assumes attentive listening from beginning to end. Funerals don't work that way. Weddings don't work that way. By the time the bridge arrives at a graveside, half the audience is already wiping eyes; by the time a wedding song's final chorus hits, guests are watching the couple, not the song. The lyric's strongest moment has to land BEFORE the audience's attention has drifted.
The check
The inside-detail MUST surface by the end of the FIRST CHORUS. The highest-emotional line MUST appear in the first 90 seconds (~first 24 lines). Operationalized in src/lib/life-songs/setting-shape.ts (frontLoadRule per setting) and surfaced by name in the forge prompt (B2638).
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.sacredAccident13 · Doc: docs/SACRED-ACCIDENTS.md