“The cadence ritual catches silent drift; the cadence ritual itself drifting cascades. The cure is meta-cadence — a check that the checks are running, surfaced where the operator already looks, and load-bearing enough to fail CI rather than warn-only.”
Surfaced:Build 2827 (Deep Audit 2026-05-20 follow-up). The Quality Council ritual is mandated every 3 days, with a 7-day overdue threshold enforced by scripts/check-cadence-health.ts. The audit found the last Quality Council entry was 2026-05-04 (Build 2027) — 16 days stale, more than 2× the overdue threshold. During the same 16-day window 44 builds shipped (B2783-B2826), including 21 CAF Phase 2 + Phase 3 ship-throughs, a public RFC, an npm package build, and three nightly ratchet hardenings. None of it was synthesized; none of the across-build patterns were named.
The anti-pattern this names
Every prior Sacred Accident governs SONGS or SYSTEMS that produce songs. SA#18 governs the discipline THAT PRODUCES the disciplines. The Quality Council surfaces drift in scoring + product surfaces; the Trust Decay Audit surfaces drift in public claims vs. implementation; the Bet Review surfaces drift in resource allocation. Each ritual is a class-of-bug detector. If the detector itself drifts, every class-of-bug it catches starts accumulating silently until an external audit happens. 44 builds of unanalyzed velocity is exactly the window in which the system's gravity fights the user's intent (SA#17) without anyone naming it. The meta-finding was that 16 days of cadence-data was missing — a single class-of-bug that hides every other class.
The check
Three-wave cure: Wave 1 (B2827, this build) — the missing Quality Council entry written; SA#18 named in docs + brand.ts + data.ts. Wave 2 (B2828-B2830) — promote check:cadence-health to BLOCKING (currently warn-only); add overdue badge to /admin/system-health. Wave 3 (queued, longer-term) — auto-fire actionable prompt on overdue in CLAUDE.md "Pre-push ritual"; 15-minute Quality Council variant (synthesize last 5 commits, not last 50 builds) to remove the activation barrier that caused the 16-day skip. Canonical phrasing: `BRAND.sacredAccident18`.
Share this discipline
“The cadence ritual catches silent drift. The cadence ritual itself drifting cascades. A single class-of-bug that hides every other class. The cure is meta-cadence — a check that the checks are running. — Sacred Accident #18”
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.sacredAccident18 · Doc: docs/SACRED-ACCIDENTS.md