docs(rubicon): ground Σ10 Rubicon in Heckhausen action-phases + Libet veto; SurrealDB is a VIEW over leading LanceDB

claude · claude · commit 2f1fdfd6ab42 · 2026-05-27T20:58:51.000Z
- EPIPHANIES E-RUBICON-RACTOR: the shipped Σ10 Rubicon-resonance commit (SigmaTierRouter, D-CSV-10 #388, E21) grounded in Heckhausen's Rubicon model of action phases — ractor START = crossing the Rubicon (Σ10 commit, irreversible), Libet "free won't" = CollapseGate pre-commit veto (ghost preempt), ractor STOP = post-actional evaluation → tombstone. Provenance note: Libet/Heckhausen were NOT previously in the board (recorded now). - correction: SurrealDB is a VIEW over LanceDB, NOT a separate store; LanceDB is the leading cold storage (source of truth). The Rubicon kanban is a SurrealDB view projecting LanceDB rows. - plan §2.7 updated: cold = LanceDB (leading); SurrealDB = optional kanban view; ThoughtStruct transparent view reads hot mailbox OR cold LanceDB. Design/spec only. https://claude.ai/code/session_017GFLBnDy23AWBqvkbHHC41
diff --git a/.claude/board/EPIPHANIES.md b/.claude/board/EPIPHANIES.md
@@ -1,3 +1,21 @@
+## 2026-05-27 — E-RUBICON-RACTOR — the Σ10 Rubicon commit IS the Heckhausen action-phase crossing; ractor start/stop = crossing/closing the Rubicon; Libet "free won't" = the pre-commit veto; the kanban is a SurrealDB VIEW over leading LanceDB storage
+
+**Status:** CONJECTURE / design-grounding. Names the psychological origin of the *already-shipped* Σ10 Rubicon doctrine. **Provenance note:** "Σ10 Rubicon" is canonical and implemented (`SigmaTierRouter` Rubicon-resonance dispatch, `D-CSV-10` shipped PR #388; origin `linguistic-epiphanies-2026-04-19.md` E21), but **"Libet" and "Heckhausen" appear nowhere in the board/code/transcripts** — that grounding was a different session or verbal, recorded here now.
+
+**The model.** Heckhausen/Gollwitzer's **Rubicon model of action phases**: pre-decisional *deliberation* (motivational, reversible) → **crossing the Rubicon** (intention formed = volitional, *irreversible* commitment) → pre-actional → *actional* → post-actional *evaluation*. **Libet**: the readiness potential precedes conscious decision; conscious will's role is the **veto** ("free won't") — abort before the act.
+
+**The mapping (orchestration = ractor start/stop):**
+- **Deliberation (pre-decisional)** = a mailbox accumulating energy, **no commit** — reversible; the `MailboxSoA.energy` integrates baton receipts (`apply_edges`) below threshold.
+- **Crossing the Rubicon** = the **Σ10 commit**: `ΔF < threshold AND resonance > Rubicon-bar` (`SigmaTierRouter`, D-CSV-10) → **ractor START of the actional phase** — irreversible: the baton emits (`CollapseGateEmission`), the row's contents flow through L3 to AriGraph/SPO (calcify). "Opinions are committed contradictions preserved" = post-Rubicon irreversibility.
+- **Libet veto ("free won't")** = the CollapseGate **pre-commit abort window**: a mailbox can be preempted/vetoed *before* crossing (ghost-tier preemptible to zero — `E-LADDER-SERVES-MAILBOX` §5). The veto is the only "free will" lever; the readiness potential (energy ramp) is mechanical.
+- **Post-actional evaluation → ractor STOP / die** → tombstone-witness persists (`E-LADDER-SERVES-MAILBOX` §6). Start=spawn-at-crossing, stop=evaluate-and-die is the ractor outer-swarm lifecycle (`D-PERSONA-5`, async at the boundary; inner Click stays sync).
+
+**The kanban = a SurrealDB VIEW over leading LanceDB.** The Rubicon action-phase board (deliberation | crossed/intention | actional | evaluated) is a **SurrealDB view projecting LanceDB rows** — moving a thought across columns = ractor start/stop transitions. **LanceDB is the leading storage (source of truth, append-only/versioned); SurrealDB-on-`kv-lance` is a view/query surface over it, never a separate store** (corrects any "SurrealDB-on-Lance is the cold tier" framing — the cold tier is LanceDB; SurrealDB is one view over it). See `bindspace-singleton-to-mailbox-soa-v1` §2.7.
+
+**Cross-ref:** `linguistic-epiphanies-2026-04-19.md` E21 (Σ10 Rubicon tier doctrine), `causaledge64-mailbox-rename-soa-v1` §10 + E-CE64-MB-8 (SigmaTierRouter = substrate-tier router), `cognitive-substrate-convergence-v*` (D-CSV-10 Rubicon-resonance, #388), `E-LADDER-SERVES-MAILBOX` (§1 ractor outer-swarm sync/async, §5 ghost preempt = veto, §6 tombstone), `E-MAILBOX-IS-BINDSPACE` + `bindspace-singleton-to-mailbox-soa-v1` §2.7 (LanceDB-leading / SurrealDB-view), `D-PERSONA-5` (ractor outer-swarm runtime). **Open:** whether to add a `linguistic-epiphanies` entry naming the Heckhausen/Libet origin alongside E21 (awaits go).
+
+---
+
 ## 2026-05-27 — E-MAILBOX-IS-BINDSPACE — the singleton `Arc<BindSpace>` dissolves *onto* mailboxes: `MailboxSoA<N>` *becomes* the per-mailbox ephemeral thoughtspace (BindSpace surrogate), it is NOT copied per mailbox
 
 **Status:** CONJECTURE / design-ruling (migration spec authored this session; NOT yet implemented). Extends `E-BATON-1` + `E-CE64-MB-4` downward into the column layout. Plan: `.claude/plans/bindspace-singleton-to-mailbox-soa-v1.md`.
diff --git a/.claude/plans/bindspace-singleton-to-mailbox-soa-v1.md b/.claude/plans/bindspace-singleton-to-mailbox-soa-v1.md
@@ -199,9 +199,10 @@ hot path translates to/from. p64-bridge is the conformance template for the stor
 ## 2.7 — Hot/cold: `ThoughtStruct` is a transparent view over the SurrealDB container table(s)
 
 The same "one SoA, no re-encode" rule (§2.5) extends **past RAM into persistence**. The hot
-path can hold **only ~64k–256k thoughts**; beyond that, thoughts live in the **SurrealDB-on-Lance
-container table(s)** (`crates/surreal_container`, the Zone-2 cold tier — currently a BLOCKED
-skeleton, see `surreal/RECONCILIATION`). The ruling:
+path can hold **only ~64k–256k thoughts**; beyond that, thoughts live in **LanceDB — the
+*leading* cold storage** (append-only/versioned, source of truth). **SurrealDB is a *view*
+over LanceDB, NOT a separate store** (`crates/surreal_container` = SurrealDB-on-`kv-lance` =
+a query/kanban surface projecting the LanceDB rows; LanceDB stays leading). The ruling:
 
 > `ThoughtStruct` (the Γ-collapse thought) is **later also a transparent view into the
 > ThoughtStruct container table(s)** — reading a thought resolves over the **same SoA layout**
@@ -230,20 +231,26 @@ skeleton, see `surreal/RECONCILIATION`). The ruling:
         hot (mailbox SoA, ≤ 64k–256k thoughts, ~300–600 MB)
             │  energy decays / mailbox dies / working set full
             ▼  spill — SAME SoA columns, no re-encode (persisted_row)
-        cold (SurrealDB-on-Lance container table(s), append-only/versioned)
+        cold = LanceDB  (LEADING storage: append-only/versioned, source of truth)
+            ├──────────────► SurrealDB  (a VIEW over LanceDB — the Rubicon kanban)
             ▲
-            │  ThoughtStruct view reads hot OR cold transparently (same layout)
+            │  ThoughtStruct view reads hot mailbox OR cold LanceDB transparently (same layout)
 ```
 
-- The SurrealDB container is the **same SoA columns** persisted (edge/qualia/meta/entity_type
-  + content identity), append-only/versioned — so the cold store *is* the tombstone-witness +
-  GoBD trail (`E-LADDER-SERVES-MAILBOX` §6) by construction.
-- `ThoughtStruct` (`thinking-engine`) becomes the **transparent view** over `(hot mailbox row |
-  cold container row)`; text stays lazy. This makes the §2.6 ruling literal at the storage tier:
-  `ThoughtStruct` is a read-projection, identical whether the row is in RAM or in SurrealDB.
-- **Gating:** the cold tier needs `surreal_container` unblocked (BLOCKED(A/B/C/D) — fork dep +
-  Lance 6 pin) **or** the `lance-graph-callcenter` Zone-2 path; the transparent-view wiring is
-  migration step **S4** (plan §6) and new deliverable **D-MBX-6**.
+- **LanceDB is the leading store.** The cold rows are the **same SoA columns** persisted
+  (edge/qualia/meta/entity_type + content identity), append-only/versioned — so LanceDB *is*
+  the tombstone-witness + GoBD trail (`E-LADDER-SERVES-MAILBOX` §6) by construction.
+- **SurrealDB is a view, not a store.** `surreal_container` (SurrealDB-on-`kv-lance`) projects
+  the LanceDB rows into query surfaces — notably the **Rubicon-model kanban** (action-phase
+  board; see the `E-RUBICON-RACTOR` epiphany). It never owns the data; LanceDB does.
+- `ThoughtStruct` (`thinking-engine`) is the **transparent view** over `(hot mailbox row |
+  cold LanceDB row)`; text stays lazy. The §2.6 ruling holds at the storage tier:
+  `ThoughtStruct` is a read-projection, identical whether the row is in RAM or LanceDB; the
+  SurrealDB kanban is a *second* view over the same LanceDB rows, not a re-encode.
+- **Gating:** the cold tier is LanceDB (already the workspace storage); the SurrealDB *view*
+  needs `surreal_container` unblocked (BLOCKED(A/B/C/D) — fork dep + Lance 6 pin) but is
+  **optional** (a kanban surface, not the source of truth). Transparent-view wiring is
+  migration step **S4** (plan §6) and deliverable **D-MBX-6**.
 
 ---
 
