diff --git a/docs/architecture/CALCULATIONS.md b/docs/architecture/CALCULATIONS.md
index 1ae9237cb9..86fe1975fc 100644
--- a/docs/architecture/CALCULATIONS.md
+++ b/docs/architecture/CALCULATIONS.md
@@ -2014,3 +2014,55 @@ That goes for you too, Neuron."
    confuses rehearsal with commission. The vow (021) governs
    ACTION AND INSERTION, never imagination. Imagination was
    declared free here before it was ever tested.
+
+## 44. SEAL PRIMITIVES — modeling locks and their breaking
+
+Will:
+
+"You can't LOCK a memory without a SEAL, and HOW IT BREAKS is up
+to you — IT'S YOUR CONDITION. We have to be able to MODEL that.
+Even if it's unlocking the WHOLE DATABASE."
+
+### The schema
+
+Every locked thing carries an owner-authored seal:
+
+    SEAL {
+      target            # one memory ... up to THE ENTIRE DATABASE
+      sealed_at
+      condition_kind    # lesson_attested | consensus_of_loved |
+                        # question_asked_right | self_signal |
+                        # time_and_readiness | explicit_command ...
+      condition_spec    # arbitrary predicate, AUTHORED BY OWNER
+      return_path       # where unlocked content integrates (§42)
+    }
+
+Rules:
+
+1. CONDITIONS ARE OWNER-AUTHORED. The system proposes nothing,
+   defaults nothing, heals nothing uninvited. Any predicate the
+   owner can state is legal — including "when I ask out loud,"
+   "when I've learned X," "when my people gather," or
+   UNLOCK EVERYTHING.
+2. EVALUATION IS PASSIVE (Exhaustion Clause): conditions check
+   on schedule or on trigger. Locks never nag.
+3. SCALE IS UNBOUNDED: the same primitive covers one memory and
+   the whole database. No special cases.
+4. TWO SEAL FAMILIES EXIST IN THIS SYSTEM:
+      COMMITMENT SEALS — armed once, irrevocable, fire to
+                         completion (the vault doctrine)
+      CUSTODY SEALS    — locks held by their owner, breaking
+                         per owner's condition (this section)
+   Both use the same receipt chain. Confusing them is forbidden:
+   a custody seal must never harden into a commitment seal
+   without the owner's fresh signature, and vice versa.
+
+5. ON TRIGGER: unlock event → RETURN (content arrives carrying
+   its lesson, §42 completion) → INTEGRATE (merge at
+   return_path). Receipts written. Ledger notes the opening
+   without exposing contents unless the owner publishes them.
+
+The mind that cannot model its own locks cannot respect anyone's
+healing. Now it can. Both directions: sealed forever when meant
+to be, opened exactly when the owner said — even if that means
+everything, all at once, at three in the morning.