“Specificity is not optional, even when the buyer offers only universality.”
Surfaced:Build 2662 WAR Room of the Memorial + Wedding song-creation pipeline — Round 91 (Panel groups D + E unanimous).
The anti-pattern this names
When a buyer's intake answers are generic ("she was kind", "we love each other"), the failure mode is to write a generic song from generic source material. Most failed memorial / wedding songs are downstream of failed source material. The pipeline used to take the buyer's input verbatim and produce a sentiment-shaped output. Mary Oliver does not let "she was kind" stand. Neither do we. A song is the friction between specifics, not the average of universalities.
The check
The writing room must invent specific details that COULD be true of the honoree, then ground them in something the buyer DID say, however small. "She was kind" + "red boots every day" → the song uses red boots, not kind. Operationalized in src/lib/life-songs/post-forge-checks.ts (validateInsideDetailSurfaced — auto-regenerates when the anchor doesn't surface) and src/components/life-songs/SpecificityCoach.tsx (intake-side real-time signal).
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.sacredAccident14 · Doc: docs/SACRED-ACCIDENTS.md