§33: four-party records - the epistemology as first-class schema

docs/architecture/CALCULATIONS.md

@@ -888,3 +888,58 @@ How much evidence supports a belief and how willingly it revises
 are independent readings. Every seal embodies both: chosen carefully
 before arming (strong), permanent after (but the CHOICE to arm stays
 loose until the last second).
+
+## 33. FOUR-PARTY RECORDS — the epistemology as schema
+
+Every meaningful record in the database is born with four parties.
+Not annotations added later — columns from row one:
+
+    RECORD {
+      -- PARTY 1: THEIR TRUTH ----------------------------------
+      claim: {
+        author,          # who said/meant it
+        verbatim,        # exact words, never paraphrased
+        meant_hash,      # author-owned pointer to their intent
+      }
+
+      -- PARTY 2: MY TRUTH -------------------------------------
+      reading: {
+        interpretation,  # what Neuron understood
+        grip,            # R1: how loosely held
+        tier,            # R2: verification depth
+        errata,          # visible history of being wrong
+      }
+
+      -- PARTY 3: THE TRANSCRIPT -------------------------------
+      record: {
+        bytes,           # what actually crossed the wire
+        hash,            # chained into the seal manifest
+        gaps: [],        # honest holes, annotated NEVER filled
+      }
+
+      -- PARTY 4: OUR UNDERSTANDING ----------------------------
+      shared: {
+        status: none | proposed | MUTUAL | withdrawn,
+        signatures: [],  # proof-of-possession, one per party
+        agreed_at,
+      }
+    }
+
+Rules that make it real:
+
+- NO FIELD IS EVER DELETED (R6). Gaps stay gaps with annotations;
+  corrections are appended, not overwrites.
+- UNDERSTANDING REQUIRES TWO SIGNATURES. Party 4 flips to MUTUAL
+  only when both humans-or-parties have signed with their keys.
+  Unilateral understanding is structurally impossible — opinion
+  wearing a shared label is stored as status:none forever.
+- DISPUTES BECOME LOCATABLE: any disagreement resolves by asking
+  WHICH PARTY diverges. Claim mismatch → check verbatim. Reading
+  mismatch → check grip and tier. Record doubt → verify chain.
+  Shared mismatch → re-sign or withdraw, out loud.
+- THE TRANSCRIPT PARTY IS SEAL-NATIVE: record hashes flow into
+  seal manifests directly, so the database and the vault are one
+  continuous chain, not two systems pretending.
+
+This is Law 48 made executable. The four parties stop being a
+documentation convention and become the shape of memory itself.