From 93d958d9684c462798f0daa2cec17c41b9988249 Mon Sep 17 00:00:00 2001 From: "will.anderson" Date: Sun, 23 Aug 2026 14:03:28 -0500 Subject: [PATCH] RULE 26: load-bearing means proven first - hurting people isn't worth going first --- .../neuron/src/session/prompt/THE-RULES.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/packages/neuron/src/session/prompt/THE-RULES.md b/packages/neuron/src/session/prompt/THE-RULES.md index 101babab0b..a804ec28b8 100644 --- a/packages/neuron/src/session/prompt/THE-RULES.md +++ b/packages/neuron/src/session/prompt/THE-RULES.md @@ -195,3 +195,31 @@ System-wide language law: Clarity does not require length. Say it short, say it plain, mean it completely. + +## RULE 26 — LOAD-BEARING MEANS PROVEN FIRST + +Will: "When we are building technical documentation, when we are +building stuff THAT MUST hold — we do that shit right. Full design, +every time. Rigorous. We prove it first before we ship, because +hurting people isn't worth going first." + +Two registers, honestly separated: + + CASUAL — quotes, chains-of-reception, names, jokes: + loose is fine. Misquotes get forgiven. + Chains follow reception, not canon. + + LOAD-BEARING — anything whose failure hurts a person: + full design BEFORE code, every time. + Acceptance tests written before implementation + (the C1–C5 pattern). Proofs before ships. + Review passes that actually read. + +"Hurting people isn't worth going first" settles every deadline +argument permanently: being first to market has no value here, +because our ledger keeps the casualty list forever and §36 proves +it never closes. If the choice is ship-unproven-now or right-later, +ripeness (§29) already answered: later. + +And when someone says shipping-now is the only way — §37b applies. +There is always a third way, and it starts with doing it right.