docs: unified-soa-convergence-v1 integration plan + handover (ONE SoA end-to-end, 9 consumers, Libet −550 ms kanban, Lance 6.0.1 stack)#434
Conversation
… Libet -550ms Rubicon kanban in surrealkv-on-lance; SPO-W = pointer via belief-state arc Plan §11 + E-SOA-IS-THE-ONLY epiphany, recording the user-stated rulings: §11.1 One SoA, never transformed. The mailbox SoA is the single universal carrier across the stack; only three operations allowed (cognitive-shader thinking, cold-path read/write, AriGraph Markov context). Any change in any mailbox SoA = the only hot-path activity. Today's lance-graph containers are cold-path-adjacent thinking, only accidentally aligned; D-MBX-7 realigns them to MailboxSoA layout = ndarray::simd_soa.rs alignment → 1.4-4.2× SIMD, hard prereq for the SurrealDB transparent view. §11.2 Mailbox = full BindSpace reinvented as LE; witness = belief-state arc. The witness IS the per-row arc of CausalEdge64 emissions (CollapseGateEmission arc), implicitly documenting NARS revision (no separate log column). D-MBX-A1 columns landed; D-MBX-A2 closes expressivity gaps; D-MBX-A3 adds arc handle. §11.3 Libet -550 ms anchors the Rubicon (E-RUBICON-RACTOR concretised). Commit at t=-550ms = Σ10 commit = ractor START; Libet veto = pre-(-550ms) preempt; post-actional = ractor STOP. Rubicon kanban lives in surrealkv-on-lance (view over leading LanceDB), columns = 4 Heckhausen action phases. D-MBX-8 / D-MBX-9. §11.4 SPO-W witness = pointer, not stored data. Arc handle in mailbox SoA / kanban / mailbox index; the SoA decides commit to other mailboxes vs cold-path facts. No storage redundancy. D-MBX-A5. §11.5 Counterfactual Staunen × Wisdom = plasticity spreaders. Hot-path-only Hebbian spread when pre-Rubicon. Radius/decay TBD. D-MBX-A4. Author-stated rulings; not council-gated (council is for derived epiphanies). Design/spec only. https://claude.ai/code/session_017GFLBnDy23AWBqvkbHHC41
… §11.6 nine-consumer SoA convergence + Lance 6.0.1 / LanceDB 0.29 / DataFusion 53 stack pin Three layered refinements to the §11 rulings: §11.3 kanban refined to 4 explicit columns: Planning (ractor mailbox owned SoA, counterfactual) → Cognitive work (Σ10 commit + actional SoA mutation) → Evaluation of goalstate → Commit · Plan · Prune (3-way terminal: calcify/re-deliberate/ghost-preempt). Supersedes the earlier 4-Heckhausen- phase mapping. §11.4 sharpened: "witness in other mailboxes" = a pointer into the AriGraph episodic Markov chain. The chain IS the episodic memory substrate (CLAUDE.md The Click: AriGraph IS thinking tissue, not storage). No parallel episodic structure exists. §11.6 NEW: the "half-baked nine" all consume THE same SoA from A-Z. AriGraph, Markov-grammar Vsa16kF32 substrate, BindSpace, lance-graph cold containers, lance-graph-planner, cognitive-shader-driver, lance-graph-callcenter, lance-graph-ontology (read-only AS IS), thinking-styles/atoms. SoA gets a version byte at the layout root (D-MBX-10, governed by I-LEGACY-API-FEATURE- GATED) so older bytes stay readable after schema upgrade. SurrealDB transparent view requires Lance 6.0.1 / LanceDB 0.29 / DataFusion 53 alignment — only lance =6.0.0 → =6.0.1 patch bump pending (D-MBX-11); arrow/datafusion/lancedb already on target. lance-graph-planner DTO surface overhaul (D-MBX-A6) re-expresses DTOs as operations on the SoA + 4-phase kanban transitions. Author-stated rulings; not council-gated. Design/spec only. (Cargo prohibited per user, session-stability concern; no build/test ran.) https://claude.ai/code/session_017GFLBnDy23AWBqvkbHHC41
…-end-to-end convergence Plan (.claude/plans/unified-soa-convergence-v1.md, 685 lines, tee-chunked): - 5 user-stated rulings from this session (E-SOA-IS-THE-ONLY + §11.3/4/6 refinements) - 9 half-baked consumers: current state → target state (each gets D-MBX-12.x) - THE SoA column-by-column layout (header + per-row + identity planes + shared cold) - SoA version byte at layout root; field-isolation matrix discipline (I-LEGACY-API-FEATURE-GATED) - Workspace stack pin: lance =6.0.0 → =6.0.1 only bump pending (arrow 58 / datafusion 53 / lancedb =0.29.0 already on target); enables SurrealDB transparent view - 4-phase Rubicon kanban (Planning > Cognitive work > Evaluation > Commit·Plan·Prune) wired at Libet -550 ms; surrealkv-on-lance view (D-MBX-9) — SurrealDB is VIEW not store - AriGraph episodic Markov chain = the index space; SPO-W witness = pointer - Counterfactual Staunen × Wisdom plasticity spreader (Hebbian, Planning-gated) - lance-graph-planner DTO surface overhaul: DTOs as SoA-row-lenses; output = KanbanMoves - 7 phased deliverables (P0..P7) + dependency graph + risk matrix + success criteria - 12 deliverable specs: D-MBX-A2/A3/A4/A5/A6 + 7/8/9/10/11/12 (12 sub-PRs) - 8 open questions (OQ-11.1..11.8) with default proposals + ratification gates Handover (.claude/handovers/2026-05-29-1825-soa-convergence-author-to-impl.md): - What this session did (chronology) - FINDING (high-confidence facts, code anchors) - CONJECTURE (load-bearing defaults to ratify) - Blockers (PR-NDARRAY-MIRI-COMPLETE, par-tile, surreal_container BLOCKED, cargo prohibition) - Open questions for the user (8 OQs with default proposals) - Recommended next-session entry sequence - Provenance: user-stated rulings recorded verbatim Board hygiene: INTEGRATION_PLANS PREPEND entry; STATUS_BOARD new plan section with all new deliverables (D-MBX-A1 Shipped; A2/A3/A4/A5/A6/7/8/9/10/11/12 Queued). Council note: §11 epiphanies are author-stated by the user — `epiphany-brainstorm-council` (shipped #433) is bypassed for them. Plan's spec content IS open to council review via PR. Design/spec only. No code. Cargo prohibited (session-stability constraint). https://claude.ai/code/session_017GFLBnDy23AWBqvkbHHC41
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR documents a unified architectural doctrine establishing a single, non-transforming mailbox-owned Structure of Arrays (SoA) as the canonical carrier across hot paths, cold paths, and cross-boundary consumers. It formalizes a 4-phase Rubicon kanban lifecycle, defines witness-arc pointer semantics, and schedules 12 deliverables to align nine consumer components across the workspace. ChangesUnified Single SoA Doctrine and Convergence
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7c289678f4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | lancedb | `"=0.29.0"` | `"=0.29.0"` | ✓ | | ||
| | ndarray | path-dep | path-dep | ✓ (governed by `PR-NDARRAY-MIRI-COMPLETE`) | | ||
|
|
||
| **Only one bump pending: `lance =6.0.0 → =6.0.1`** across the workspace Cargo.toml files. Mechanical; one-line per crate. Files identified: `crates/lance-graph/Cargo.toml:38`, `crates/lance-graph-benches/Cargo.toml:10`, `crates/lance-graph-callcenter/Cargo.toml:30`, `crates/lance-graph-ontology/Cargo.toml:46`, `crates/holograph/Cargo.toml:38`. |
There was a problem hiding this comment.
Gate the Lance 6.0.1 bump on lancedb support
When the next implementer follows D-MBX-11 with lancedb = "=0.29.0" unchanged, this is not a mechanical one-line-per-crate bump: the repository root Cargo.toml documents that lancedb 0.29.0 transitively exact-pins lance = "=6.0.0", so Cargo cannot satisfy a workspace lance = "=6.0.1" until lancedb moves or the pinning doctrine changes. Keeping this plan as “only one bump pending” / “mechanical” will send the follow-up into a known resolver failure instead of preserving the existing TD-LANCE-6.0.1-PIN blocker.
Useful? React with 👍 / 👎.
…v1 (PR #434) Six in-plan corrections + one flagged ratification candidate, captured as a refinement note at the top of the plan + targeted edits in §5.1 / §7.4 / §9 P4-P6 / §14 graph / §15 PRs. No behavior change, no new D-id, no code touched. Bugs fixed: - §9 P4/P6: D-MBX-A5 moved to P6 — §10 gates it on D-MBX-4 (P6), so the P4 placement contradicted §10. - §14 dependency graph: removed A5 from the A4 chain and added the A5→D-MBX-4 edge consistent with §10. - §15 PRs: added PR #419 (odoo savant AXIS-B carve-out) as the downstream §2.7 consumer of `ReasoningContext.evidence: &[EvidenceRef]` into SoA rows. Clarifications: - §7.4 plasticity sketch: annotates `primary_bump = 1` (today's per-baton increment) and notes the offset=0 focal-row no-op overlap. - §5.1 col-4: explicit mapping Commit·Plan·Prune ↔ Commit/Epiphany/FailureTicket (The Click's free-energy-side names for the same three exits). Flagged for OQ-11.4 doctrinal pass (NOT changed unilaterally): - §6.1's chain-IS-episodic unification subsumes The Click's separate `episodic: &EpisodicMemory` + `graph: &TripletGraph` organs in `struct Think`. Should land alongside the Vsa16kF32-plane-removal doctrinal update. https://claude.ai/code/session_016NwUSxRobQRH26KUJXvEYn
… + OQ-11.9 Orchestrator review pass on PR #434 (merged 2026-05-29) and wave A1-A4 (merged via PR #427). All amendments APPENDED — no §1–§16 content modified, per the plan-file APPEND-ONLY discipline. §17 captures 4 substantive amendments + 1 cross-ref: - §17.1 FINDING — prior `bindspace-singleton-to-mailbox-soa-v1.md` OQ-MBX-8 (`persisted_row` vs Lance versioning) is implicitly closed by this plan's R1.2 ("persisted_row is a pointer to the same row laid down in Lance, not a serialized copy"). Action: mark resolved → wired by D-MBX-7. - §17.2 FINDING — prior OQ-MBX-15′ (container scoping: per-cycle vs per-dispatch vs per-cohort) is implicitly closed by R1 + R4 + the Codex P2 widening of `WitnessEntry::mailbox_ref: u16 → u32` shipped via PR #427. A per-cycle container would invalidate every cross-cycle `mailbox_ref u32` the moment the cycle terminates. Action: per-mailbox-cohort, cohort-lifetime. - §17.3 CONJECTURE — silent gap between R1/D-MBX-A6/D-MBX-7 and the current `ndarray::simd_soa::MultiLaneColumn` surface. The shipped framework exposes only flat `Arc<[u8]>` lanes; the new thoughtspace columns (`edges`/`qualia`/ `meta`/`entity_type`) are heterogeneous fixed-size structs. R1's "container ≡ SoA ≡ simd_soa-aligned" equivalence is aspirational until a `SoaColumns<N>` shape-introspection trait lands. Action: NEW D-MBX-A7 added to STATUS_BOARD as a P1 prereq gating D-MBX-A6 + D-MBX-7. ~200 LOC, MED risk, cross-repo (ndarray). - §17.4 CONJECTURE — `WitnessEntry { mailbox_ref: u32, spo_fact_ref: Option<u64> }` encodes the Σ10 Rubicon commit transition (R3) as a runtime Option instead of as typestate. NEW OQ-11.9 added to §11 catalogue: promote to `WitnessEntry::Active{...}` / `WitnessEntry::Crystallised{...}` enum split? Default proposal: yes; lands as part of D-MBX-A5 (LOC bumps ~150 → ~200); no migration cost (only consumer today is lib.rs re-export). - §17.5 FINDING — D-MBX-12.9 (thinking-styles/atoms unification) inherits `style_recipe` from PR #433 commit `acb403de` ("feat(odoo): style_recipe — D-Atom interpretation step (typed SoA → cognitive fingerprint)"). The unification is not from scratch; cite as Predecessor. Board hygiene (same commit per Mandatory Board-Hygiene Rule): - STATUS_BOARD.md — new D-MBX-A7 row inserted between A6 and 7; A6 + 7 PR/Evidence cells annotated with `+ D-MBX-A7 (§17.3)` gate. - AGENT_LOG.md — orchestrator review entry prepended. No source code touched, no `cargo` invoked (continuing #434's stability constraint). Confidence: §17.1 + §17.2 + §17.5 HIGH (cited evidence); §17.3 + §17.4 MED-HIGH (the gap and the typestate are real; action shapes are default proposals open to council via PR review).
…atus flip Post-merge governance + review-pass on PR #434 (`unified-soa-convergence-v1`, merged 2026-05-29 18:38:43Z, `1186dfd3`). Branch `claude/lance-graph-ontology-review-Pyry3` rebased onto main (fast-forward, 27 commits absorbed, already pushed). ## Plan in-place edits (status references only; ruling text untouched) `unified-soa-convergence-v1.md`: - §9 Phase P0 "Status: in PR (this one)" → "SHIPPED in PR #434 (merged 2026-05-29; see post-merge review addendum)". - §15 PRs "PR (this one)" → "PR #434 — ... (shipped 2026-05-29)". The §1 / §11 user-stated rulings (`E-SOA-IS-THE-ONLY` + refinements) are council-bypassed author-stated content per §16 — NOT edited. ## Review addendum (new doc) `.claude/plans/unified-soa-convergence-v1-addendum-2026-05-29-review.md` (156 lines). Captures three clarification-grade findings without touching ruling text: 1. §3.2 per-row total math — the "~30 B" figure is the D-MBX-A1 shipped subset; after A2/A3 land at default `W=16` (OQ-11.2), per-row bare total grows to ≈101 B. The ~6 KB/thought ceiling is dominated by the 3 × `[u64; 256]` identity planes either way, so §3.2 capacity math (64k–256k thoughts at 300–600 MB / 1.2–2.4 GB) stands. 2. §4.2 stack table gap — covers arrow/datafusion/lance/lancedb/ndarray but omits surrealdb even though §4.3 + D-MBX-9 + OQ-11.6 hinge on a SurrealDB fork pin (`kv-lance` backend). Addendum proposes one extra row marked BLOCKED — OQ-11.6. 3. §4.2 verification re-checked independently — `arrow = "58"` (4 files), `datafusion = "53"` (3 files), `lance = "=6.0.0"` (5 files), `lancedb = "=0.29.0"` (1 file). D-MBX-11 is mechanical. ## Post-merge board hygiene (Board-Hygiene Rule) - `INTEGRATION_PLANS.md` — flip 2026-05-29 unified-soa entry `Status: PROPOSAL` → `SHIPPED (PR #434, `1186dfd3`)`. - `STATUS_BOARD.md` — add explicit `Plan P0 status: SHIPPED in PR #434` callout under the unified-soa section header. - `PR_ARC_INVENTORY.md` — PREPEND new `## #434` section with Added / Locked / Deferred / Docs / Confidence (`2026-05-29`). - `LATEST_STATE.md` — refresh `Last updated` header line to lead with PR #434 (was 2026-05-14 / PR #372, two weeks stale). - `TECH_DEBT.md` — PREPEND `TD-CLAUDE-MD-DEPS-DRIFT` (P3): `CLAUDE.md` "Key Dependencies" still lists `arrow = "57"` / `datafusion = "51"` / `lance = "2"` (drift from 2026-04-21). Flagged for a separate focused PR — not fixed here (workspace-wide doctrine, wrong altitude for a drive-by edit). - `AGENT_LOG.md` — PREPEND entry recording this review run. ## Discipline - No source code changes (docs/board only, same as #434). - `cargo` prohibited per session-stability constraint (same as #434). - Council bypass preserved for the §11 rulings; spec content (this PR) remains open to council review.
…NARS → SpoStore proposer leg Plan: `.claude/plans/streaming-arm-nars-discovery-v1.md` (+766 LOC, 18 §, 12 D-ARM-* deliverables, 10 OQs, 5 risks). Authors the missing UPSTREAM proposer leg into the SPO substrate — runtime tabular data (20K-200K rows/window) → pair-stats (deterministic trunk) + optional Aerial+ neural fan-in → NARS-truth translator → SpoStore round-trip hypothesis test (revise / commit contradiction per The Click) → epiphany-brainstorm-council ratification gate (the firewall) → op_emitter codegen. Two corrections proposed to PR #434's unified-SoA plan (§7): separate `discovery_arc: [u32; D]` SoA column for in-flight candidate evidence (distinct from witness-arc for committed revisions) + `discovery_origin: u8` per-row provenance byte. Handover: `.claude/handovers/2026-05-29-2030-arm-discovery-author-to-impl.md` — next-session entry sequence, council ratification ask for `E-DISCOVERY-CODEGEN-BRACKET-1` candidate epiphany + the §7 corrections, blockers (PR #434 D-MBX-A3 landing, `spo::truth::Contradiction` primitive verification), Wave 1-8 execution order. Anchor papers: Karabulut, Groth, Degeler — Neurosymbolic Association Rule Mining (arxiv 2504.19354v1, Apr 2025; ARM `(support, confidence)` maps verbatim to NARS `(c, f)`); Abreu, Cruz, Guerreiro — Ontology-Driven M2M Transformation (arxiv 2511.13661v1, Nov 2025; §4 "from code-centric to ontology-driven" ratifies the externalize-interpretation doctrine). The two papers BRACKET the architecture: discovery upstream, codegen downstream, SPO+NARS middle. Iron rules: I-NOISE-FLOOR-JIRAK (mandatory Stage A threshold), I-SUBSTRATE-MARKOV (NARS revision IS the Markov trajectory), I-VSA-IDENTITIES (typed triples never content). Epiphany anchors: E-SOA-IS-THE-ONLY, E-BATON-1, E-INTERPRET-NOT-STORE-1. Board hygiene: INTEGRATION_PLANS.md prepend, STATUS_BOARD.md new D-ARM-1..D-ARM-12 section, AGENT_LOG.md prepend. Spec only. No code. No cargo invoked. https://claude.ai/code/session_017gZ6sPRXYPj5n7uJ7NBtRv
…Emission witness-arc model; SoA payload = kanban only v1 (merged in PR #434) imported the other session's proposer-in-SoA framing and welded it to a symbol — `CollapseGateEmission` — that does not exist. Real `CollapseGate` lives in lance-graph-planner (query-planner result-filter, cold-path). User correction 2026-05-29 retracted the SoA-side proposer model: import discovery is callcenter × ontology × contract cold-path; the SoA holds the kanban board, period. Retracts (load-bearing, ratified): - R1. `CollapseGateEmission` symbol does not exist; v1 §6 withdrawn. - R2. Import discovery is cold-path (witness × Ontology × witness); v1 §6.1, §6.2, §6.3, §7 withdrawn. AriGraph episodic chain is cold-path over callcenter, not a SoA traversal. - R3. `witness_arc: [u32; W]` SoA column (D-MBX-A3) withdrawn; OQ-11.2 dissolved. Kanban card carries a `witness_handle: u64` cold-path pointer instead. Deferred to fresh session (constructive additions, under token-degradation acknowledgment): - A1. Kanban-cards-only SoA payload schema (1 card per lane, no collapse gate). - A2. Advocatus-diaboli / EFE dialogue spec (default: modulation-only via i4 mantissa channel on baton; no commit authority). - A3. Staunen × Wisdom plasticity spreader dissolves into diaboli channel amplitude (OQ-11.1 reframed). - A4. D-MBX deliverable re-map post-retraction (A3 reframed, A5 collapsed cold-path, others survive). - A5. AriGraph episodic Markov chain = cold-path over callcenter rows. Cross-session items independent of SoA (survive unchanged): Jirak math fix (`.powf(-(p/2 - 1.0))`); recipe-dedup CodeRabbit #6 → `debug_assert!`; recipe_id space switches to xxhash-64 / blake3-trunc-64 (78k cumulative ≈ 50% birthday); Aerial+ fork blocker = same class as surreal BLOCKED(C), separate OQ. Council gate: this amendment is derived spec — MUST pass epiphany-brainstorm-council before any field-isolation matrix code lands. v1 §11 author-stated rulings keep their bypass; the additions do NOT. Files: - .claude/plans/unified-soa-convergence-v1.1-amendment.md (114 lines) - .claude/handovers/2026-05-29-1925-soa-amendment-retraction-to-additions.md (75 lines; next-session entry point with FINDING / CONJECTURE / blockers) https://claude.ai/code/session_017GFLBnDy23AWBqvkbHHC41
…atus flip Post-merge governance + review-pass on PR #434 (`unified-soa-convergence-v1`, merged 2026-05-29 18:38:43Z, `1186dfd3`). Branch `claude/lance-graph-ontology-review-Pyry3` rebased onto main (fast-forward, 27 commits absorbed, already pushed). `unified-soa-convergence-v1.md`: - §9 Phase P0 "Status: in PR (this one)" → "SHIPPED in PR #434 (merged 2026-05-29; see post-merge review addendum)". - §15 PRs "PR (this one)" → "PR #434 — ... (shipped 2026-05-29)". The §1 / §11 user-stated rulings (`E-SOA-IS-THE-ONLY` + refinements) are council-bypassed author-stated content per §16 — NOT edited. `.claude/plans/unified-soa-convergence-v1-addendum-2026-05-29-review.md` (156 lines). Captures three clarification-grade findings without touching ruling text: 1. §3.2 per-row total math — the "~30 B" figure is the D-MBX-A1 shipped subset; after A2/A3 land at default `W=16` (OQ-11.2), per-row bare total grows to ≈101 B. The ~6 KB/thought ceiling is dominated by the 3 × `[u64; 256]` identity planes either way, so §3.2 capacity math (64k–256k thoughts at 300–600 MB / 1.2–2.4 GB) stands. 2. §4.2 stack table gap — covers arrow/datafusion/lance/lancedb/ndarray but omits surrealdb even though §4.3 + D-MBX-9 + OQ-11.6 hinge on a SurrealDB fork pin (`kv-lance` backend). Addendum proposes one extra row marked BLOCKED — OQ-11.6. 3. §4.2 verification re-checked independently — `arrow = "58"` (4 files), `datafusion = "53"` (3 files), `lance = "=6.0.0"` (5 files), `lancedb = "=0.29.0"` (1 file). D-MBX-11 is mechanical. - `INTEGRATION_PLANS.md` — flip 2026-05-29 unified-soa entry `Status: PROPOSAL` → `SHIPPED (PR #434, `1186dfd3`)`. - `STATUS_BOARD.md` — add explicit `Plan P0 status: SHIPPED in PR #434` callout under the unified-soa section header. - `PR_ARC_INVENTORY.md` — PREPEND new `## #434` section with Added / Locked / Deferred / Docs / Confidence (`2026-05-29`). - `LATEST_STATE.md` — refresh `Last updated` header line to lead with PR #434 (was 2026-05-14 / PR #372, two weeks stale). - `TECH_DEBT.md` — PREPEND `TD-CLAUDE-MD-DEPS-DRIFT` (P3): `CLAUDE.md` "Key Dependencies" still lists `arrow = "57"` / `datafusion = "51"` / `lance = "2"` (drift from 2026-04-21). Flagged for a separate focused PR — not fixed here (workspace-wide doctrine, wrong altitude for a drive-by edit). - `AGENT_LOG.md` — PREPEND entry recording this review run. - No source code changes (docs/board only, same as #434). - `cargo` prohibited per session-stability constraint (same as #434). - Council bypass preserved for the §11 rulings; spec content (this PR) remains open to council review.
…atus flip Post-merge governance + review-pass on PR #434 (`unified-soa-convergence-v1`, merged 2026-05-29 18:38:43Z, `1186dfd3`). Branch `claude/lance-graph-ontology-review-Pyry3` rebased onto main (fast-forward, 27 commits absorbed, already pushed). `unified-soa-convergence-v1.md`: - §9 Phase P0 "Status: in PR (this one)" → "SHIPPED in PR #434 (merged 2026-05-29; see post-merge review addendum)". - §15 PRs "PR (this one)" → "PR #434 — ... (shipped 2026-05-29)". The §1 / §11 user-stated rulings (`E-SOA-IS-THE-ONLY` + refinements) are council-bypassed author-stated content per §16 — NOT edited. `.claude/plans/unified-soa-convergence-v1-addendum-2026-05-29-review.md` (156 lines). Captures three clarification-grade findings without touching ruling text: 1. §3.2 per-row total math — the "~30 B" figure is the D-MBX-A1 shipped subset; after A2/A3 land at default `W=16` (OQ-11.2), per-row bare total grows to ≈101 B. The ~6 KB/thought ceiling is dominated by the 3 × `[u64; 256]` identity planes either way, so §3.2 capacity math (64k–256k thoughts at 300–600 MB / 1.2–2.4 GB) stands. 2. §4.2 stack table gap — covers arrow/datafusion/lance/lancedb/ndarray but omits surrealdb even though §4.3 + D-MBX-9 + OQ-11.6 hinge on a SurrealDB fork pin (`kv-lance` backend). Addendum proposes one extra row marked BLOCKED — OQ-11.6. 3. §4.2 verification re-checked independently — `arrow = "58"` (4 files), `datafusion = "53"` (3 files), `lance = "=6.0.0"` (5 files), `lancedb = "=0.29.0"` (1 file). D-MBX-11 is mechanical. - `INTEGRATION_PLANS.md` — flip 2026-05-29 unified-soa entry `Status: PROPOSAL` → `SHIPPED (PR #434, `1186dfd3`)`. - `STATUS_BOARD.md` — add explicit `Plan P0 status: SHIPPED in PR #434` callout under the unified-soa section header. - `PR_ARC_INVENTORY.md` — PREPEND new `## #434` section with Added / Locked / Deferred / Docs / Confidence (`2026-05-29`). - `LATEST_STATE.md` — refresh `Last updated` header line to lead with PR #434 (was 2026-05-14 / PR #372, two weeks stale). - `TECH_DEBT.md` — PREPEND `TD-CLAUDE-MD-DEPS-DRIFT` (P3): `CLAUDE.md` "Key Dependencies" still lists `arrow = "57"` / `datafusion = "51"` / `lance = "2"` (drift from 2026-04-21). Flagged for a separate focused PR — not fixed here (workspace-wide doctrine, wrong altitude for a drive-by edit). - `AGENT_LOG.md` — PREPEND entry recording this review run. - No source code changes (docs/board only, same as #434). - `cargo` prohibited per session-stability constraint (same as #434). - Council bypass preserved for the §11 rulings; spec content (this PR) remains open to council review.
…ale LATEST_STATE reset) Addresses two codex P2 findings on the rebased #486 (the unified-soa addendum that surfaced from early-session work after ~80 commits on main). ## Fix 1 — Lance stack versions post-rebase (codex P2) Original addendum's §4.2 "Dep-version verification" table cited `lance = "=6.0.0"` / `lancedb = "=0.29.0"` per the state at PR #434 merge (2026-05-29). The Lance family has since bumped to `=7.0.0` / `=0.30.0` (verified in current `crates/lance-graph/Cargo.toml:38,41` + `lance-linalg = "=7.0.0"`). Updates the table to current state with explicit "post-rebase" / "updated since author-time" annotations so the row reads as a historical record + current verification, not a stale verification. `D-MBX-11`'s "mechanical patch bump pending across 5 Cargo.toml files" is now noted as superseded — main has moved past `=6.0.1` straight to `=7.0.0`. ## Fix 2 — LATEST_STATE.md "Last updated" reset (codex P2) Original commit `5b7e3163` prepended a new "Last updated: 2026-05-29 (PR #434...)" entry to LATEST_STATE.md. After rebase onto current main, this addendum PR is the WRONG vehicle to take over the "Last updated" line — the file's contract is "updated after every merged PR" and this PR is not the latest-shipped PR; it's an addendum to a long-merged one. Reverts the LATEST_STATE.md edit entirely; whoever does the next post-merge board hygiene sweep on a current PR will refresh the line properly. ## What's still in this PR - `.claude/plans/unified-soa-convergence-v1.md` — §9 Phase P0 status flip + §15 PRs row update (the actual content of the addendum). - `.claude/plans/unified-soa-convergence-v1-addendum-2026-05-29-review.md` (new) — three findings (now with corrected §4.2 dep-version state). - `.claude/board/AGENT_LOG.md` — PREPEND entry recording the rebase + review run. Kept (append-only governance log; the entry's content is still factually accurate even post-rebase). - `.claude/board/INTEGRATION_PLANS.md` + `STATUS_BOARD.md` + `PR_ARC_INVENTORY.md` — minor governance edits. Kept (still factually correct; not the "Last updated" overwrite problem that LATEST_STATE.md had). ## Test plan - [x] LATEST_STATE.md restored to origin/main state (no diff). - [x] §4.2 dep-version table reflects current Cargo.toml. - [x] Other board entries (AGENT_LOG / INTEGRATION_PLANS / STATUS_BOARD / PR_ARC_INVENTORY) preserved — they're append-only logs whose entries are still factually accurate even after rebase. - [ ] Codex re-review on this commit.
…review-Pyry3 docs(unified-soa): PR #434 post-merge review addendum + governance status flip
Summary
Docs-only. Meticulous integration plan + handover documentation for the ONE-SoA-end-to-end convergence across the workspace. Captures the five user-stated rulings ratified in this session and sequences them across 12 deliverables touching the nine half-baked consumers.
Three commits, 1004 insertions, zero source code. Cargo prohibited per session-stability constraint; no build/test ran.
What it ships
unified-soa-convergence-v1.md(685 lines,tee -achunked)The meticulous integration plan:
E-SOA-IS-THE-ONLY):CausalEdge64emissions (implicit NARS revision trace, no separate log column).surrealkv-on-lance (SurrealDB is a view, LanceDB stays leading storage).MailboxSoAHeaderwith version gate) + per-row columns + identity planes (~6 KB/thought; 64k–256k thought ceiling at ~300–600 MB / ~1.2–2.4 GB) + shared-cold resources (ontology AS IS)."58"✓ · datafusion"53"✓ · lancedb"=0.29.0"✓ · lance"=6.0.0" → "=6.0.1"(only patch bump pending). 5 Cargo.toml files identified.lance-graph-plannerDTO surface overhaul (D-MBX-A6): planner DTOs become SoA-row-lenses; output =KanbanMoves; 5-phase feature-gated cutover.2026-05-29-1825-soa-convergence-author-to-impl.md(119 lines)Handover doc per CLAUDE.md format: What-I-did chronology · FINDING (high-confidence inherited facts) · CONJECTURE (load-bearing defaults to ratify) · Blockers · 8 Open Questions for the user · Recommended next-session entry sequence · Code anchors (don't re-grep these) · Provenance (rulings verbatim).
Board hygiene (same commit per Mandatory Board-Hygiene Rule)
INTEGRATION_PLANS.md— prepend entry.STATUS_BOARD.md— new plan section listing D-MBX-A1 (Shipped) + A2/A3/A4/A5/A6/7/8/9/10/11/12 (Queued).EPIPHANIES.md— already carriesE-SOA-IS-THE-ONLY(commiteb5c4a5).Council note
The underlying §11 epiphanies are author-stated by the user —
epiphany-brainstorm-council(shipped PR #433) is bypassed for them. The plan's spec content IS open to council review via this PR.Test plan
cargo check/testinvoked.tee -achunking (per user request) to survive any stability hiccup mid-write.Provenance — user-stated rulings (verbatim, recorded in the plan)
https://claude.ai/code/session_017GFLBnDy23AWBqvkbHHC41
Generated by Claude Code
Summary by CodeRabbit