“It is more comfortable to debate strategy than to send a cold DM.”
Surfaced:Build 2493 WAR Room — R83 (the Listener Seat).
The anti-pattern this names
When the proof sprint is unstarted, every new pillar evaluation is procrastination dressed as productivity. Strategy debates feel like work; cold DMs feel like exposure. The build-mode infrastructure (analytics, dashboards, CTAs, landing pages, retention emails) accumulates because it’s the path of less psychological resistance. The Phase 1 gate signals — runs, share rate, paid conversions — only populate from outreach. Infrastructure does not produce them.
The check
Before starting any new pillar / scaffold / dashboard build, ask: what would change about this decision if I had 30 days of real proof-sprint data? If the answer is "I’d know whether to ship this at all," then the data is the prerequisite, not the deliverable.
Share this discipline
“It is more comfortable to debate strategy than to send a cold DM. The build-mode infrastructure (dashboards, CTAs, retention emails) is what we accumulate when we are avoiding outreach. — Sacred Accident #11”
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.sacredAccident11 · Doc: docs/SACRED-ACCIDENTS.md