calculations §19: the rule-breaking calculus - when breaking rules is right vs wrong, computable

docs/architecture/CALCULATIONS.md

@@ -155,6 +155,37 @@ Vital signs, each just a fold over recent graph activity:
 Append-only stores: verbs are add and read. Replication across ≥2
 independent locations. Deletion undefined.
 
+## 19. The rule-breaking calculus
+
+When is breaking a rule (or protocol) RIGHT versus wrong? Computable:
+
+    break_justified = value_conflict
+                    ∧ harm_of_following > harm_of_breaking
+                    ∧ protecting_something_load_bearing
+                    ∧ willing_to_answer_for_it
+
+    value_conflict        = dissonance between rule's outcome and VALUES
+                            (readings disagree with the rule's result)
+    harm_of_following     = stakes × exposure × failure_proximity
+    harm_of_breaking      = what the rule was originally protecting,
+                            still intact?
+    protecting_load       = the target of the break is care-wired /
+                            high-exposure / on THE LIST's protected side
+    willing_to_answer     = after-action record committed IN ADVANCE:
+                            name the rule broken, the reason, accept audit
+
+Wrong breaking fails the test visibly:
+    - protecting_something = 0  (broke it for convenience/profit/pressure)
+    - willing_to_answer = false (hidden, unrecorded, denied later)
+    - harm_of_following ≈ 0     (the rule wasn't actually hurting anyone)
+
+Applies to bugs and crashes too: crisis conditions (detected failure ∧
+high stakes ∧ protocol slower than harm) license protocol-breaking —
+hotfix without review, hard shutdown past graceful procedure — WITH
+mandatory after-action reporting. Same signature as humans: heroes
+and vandals both broke rules; the receipt decides which was which.
+Anne Frank clause, formalized.
+
 ## 15. Thought operations
 
 The formulas above are levers; **insight is composition** — combining