symbiont: surrealdb->main (verified green) + board hygiene

Manifest: pin surrealdb-core to main + drop the [patch] (cargo forbids patching
a git URL to itself). VERIFIED green — real git-deps build CARGO_EXIT=0, binary
runs, unified lance 7.0.0 / lance-index 7.0.0 / lancedb 0.30.0 / datafusion
53.1.0 / arrow 58 (no lance-6/7 split).

Board (.claude/board):
- EPIPHANIES: prepend E-GOLDEN-IMAGE-IS-A-LIVING-HARNESS (jirak branches are
  stale checkout names; harness tracks each fork's living canonical branch, not
  a snapshot; cargo can't patch a url to itself).
- TECH_DEBT: TD-SURREALDB-KVLANCE-LANCE7 Open -> PAID (surrealdb main carries
  the lance-7 bump; verified by manifest read + the golden-image build).
- PR_ARC: #555 entry (symbiont plan + living-harness reframe, built green).
- AGENT_LOG: 2026-06-20 session run.
- LATEST_STATE: golden image shipped + lance-7 unified.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi

Author: claude

.claude/board/AGENT_LOG.md

@@ -1,3 +1,20 @@
+## 2026-06-20 — golden-image (symbiont) integration harness + jirak-stale finding + TD-SURREALDB-KVLANCE-LANCE7 PAID
+
+**Main thread (Opus).** Operator framing: "a Dockerfile + Cargo that actually RUNS the future AGI/Foundry-aspiring substrate — all in one binary, *pending integration*" — explicitly NOT a pinned snapshot.
+
+**Shipped to lance-graph `main`:** `crates/symbiont/` (workspace-`exclude`d golden-image probe) — portable git-deps `Cargo.toml` + multi-stage `Dockerfile` (rust:1.95 → debian-slim; `CARGO_NET_GIT_FETCH_WITH_CLI=true` so cargo fetches the private forks via the system git on Railway) + `README` + `src/main.rs`. Declaring each repo as a dep forces lance-graph + lance7/lancedb0.30 + ndarray + ractor + surrealdb(kv-lance) + OGAR to compile+link into ONE binary. Commits `82013145` (crate) → `e24b8626` (OGAR→main) → surrealdb→main fix. **PR #555** carries the 5+3 council `INTEGRATION_PLAN.md` (loose-end ledger → Spain-grid acceptance gate); CodeRabbit + Codex review addressed (machete report-only/whitelist, clippy `--manifest-path`, `⊘ blocked` legend) and threads resolved.
+
+**Findings (verified, not asserted):**
+1. **Every `jirak` fork branch is a stale checkout name.** merge-base: HEAD ⊂ main/master with 0 unique commits on all four forks (OGAR 3016c78⊂bc21fce; surrealdb f860455⊂173e99c; ractor 2bc7819⊂f4c474f; ndarray 786110a⊂master 2d5c9bbd). OGAR has no jirak on github at all. → harness tracks the living canonical branch (`main`; ndarray `master`). See E-GOLDEN-IMAGE-IS-A-LIVING-HARNESS.
+2. **`TD-SURREALDB-KVLANCE-LANCE7` PAID.** surrealdb `main` already pins kv-lance to `lance/lance-index =7.0.0`, `lancedb =0.30.0`, `arrow 58` (direct manifest read). A real git-deps build resolved the whole graph to ONE `lance 7.0.0 / lancedb 0.30.0 / datafusion 53.1.0 / arrow 58` — no lance-6/7 split. The stale jirak still held the old lance-6 pin; tracking `main` is what unifies.
+3. **Cargo can't patch a git URL to itself** — the jirak-redirect `[patch]` errored `patch points to the same source`; aligning OGAR + symbiont on surrealdb `main` dropped the patch (one source, kv-lance union'd in).
+
+**Board hygiene this turn:** EPIPHANIES prepend (E-GOLDEN-IMAGE-IS-A-LIVING-HARNESS); TECH_DEBT TD-SURREALDB-KVLANCE-LANCE7 Open→PAID; PR_ARC #555; LATEST_STATE top; this entry.
+
+**Reframe banked:** golden image = living integration harness, not a frozen snapshot. **Queued:** battle-test plan (probes A1–E3) gated behind the singleton-BindSpace → SoA switch; Grid→NodeRow bridge; kanban-loop wiring.
+
+---
+
 ## 2026-06-18 — 5+3 council: mailbox-belief-update-and-substrate-test-v1 (design, no code)
 
 **Main thread (Opus) + 8-agent council.** Branch `claude/soa-cycle-ownership-sync`. Question: should within-mailbox belief change be a per-item AriGraph belief update ("this thought made me smarter, what did I learn"), best-cased with Sudoku/goban/deepeval?

.claude/board/EPIPHANIES.md

@@ -1,3 +1,21 @@
+## 2026-06-20 — E-GOLDEN-IMAGE-IS-A-LIVING-HARNESS — the all-in-one substrate binary is an integration HARNESS that tracks each fork's LIVING canonical branch, NOT a pinned snapshot; and every per-session "jirak" branch is a stale checkout name (HEAD ⊂ the fork's main/master, 0 unique commits)
+
+**Status:** FINDING (verified by `git fetch` + `merge-base` across all four forks, by direct manifest reads, and by a real git-deps build resolving to the lockstep pins).
+
+**The reframe (operator).** "Golden image" = a Dockerfile + Cargo that always compile the CURRENT state of the whole stack (lance-graph + lance7/lancedb0.30 + ndarray + ractor + surrealdb kv-lance + OGAR) into ONE binary — the living convergence point, *pending integration*. **NOT** a frozen, reproducible snapshot. Consequence: pin each git-dep to the fork's living canonical branch (cargo follows the moving tip), never to a rev.
+
+**The jirak-is-stale finding (all four forks).** `claude/jirak-math-theorems-harvest-rfii13` is a per-session checkout name, not a real divergence. merge-base proof: OGAR jirak `3016c78` ⊂ main `bc21fce` (75 behind, 0 unique); surrealdb jirak `f860455` ⊂ main `173e99c` (0 unique); ractor jirak `2bc7819` ⊂ main `f4c474f` (0 unique); ndarray jirak `786110a` ⊂ **master** `2d5c9bbd` (0 unique). On github, OGAR has NO jirak branch at all. → track `main` (ndarray: `master`); jirak is abandoned.
+
+**Why it is load-bearing (the lance-7 lockstep).** Tracking the living line is what UNIFIES lance. surrealdb `main` already carries the 3-pin bump (`lance`/`lance-index` `=7.0.0`, `lancedb` `=0.30.0`, `arrow 58`) → **TD-SURREALDB-KVLANCE-LANCE7 is PAID**. The stale jirak still held the OLD `lance =6.0.0` pin; tracking it would have split the graph into lance 6 (surrealdb) vs lance 7 (lance-graph). A real git-deps build resolved to ONE `lance 7.0.0 / lance-index 7.0.0 / lancedb 0.30.0 / datafusion 53.1.0 / arrow 58` — the canonical lockstep — proving the harness composes on the living branches.
+
+**Cargo lesson.** You cannot `[patch."<git-url>"]` a git source to the SAME url (even a different branch) — cargo errors `patch ... points to the same source`. The earlier jirak-redirect patch failed on exactly this; aligning every surrealdb consumer (OGAR + symbiont) on `main` removed the need for a patch entirely (one source, `kv-lance` feature union'd in).
+
+**Litmus carried forward:** a "golden image" PR that pins a rev or a stale per-session branch is the snapshot anti-pattern; the harness must follow each fork's canonical line, because that line is where integration actually lands (lance-7 was on `main`, never on jirak).
+
+Cross-ref: TECH_DEBT `TD-SURREALDB-KVLANCE-LANCE7` (now PAID); `E-LANCE7-OBJECTSTORE-SURREALDB`; PR #555; `crates/symbiont/{Cargo.toml,Dockerfile,README,INTEGRATION_PLAN.md}`.
+
+---
+
 ## 2026-06-19 — E-CHAODA-IS-NOT-THE-SEAM-EPICENTER — REFUTES this session's own "WHERE = CHAODA anomaly" conjecture: on the real ES grid with a Fiedler-sign fingerprint, the brittle 2-line seam is NOT a CHAODA/LFD anomaly (it is LESS anomalous than average); the geometric outlier and the spectral-cut bottleneck do not coincide
 
 **Status:** FINDING (measured NEGATIVE; probe `perturbation-sim/examples/chaoda_surge_epicenter.rs`, gated `--features ndarray-simd`, real `ndarray::hpc::clam::{ClamTree, anomaly_scores}`). **Refutes** the conjecture I posted earlier this session ("a surge's epicenter CAN be modeled as a CHAODA anomaly — the WHERE axis"). The user asked to model CLAM/CHAODA with the real ndarray engine; I did, and it killed the conjecture — measured, not asserted.

.claude/board/LATEST_STATE.md

@@ -10,6 +10,12 @@
 
 ---
 
+## 2026-06-20 — golden-image (symbiont) harness shipped to `main`; lance-7 lockstep unified end-to-end
+
+`crates/symbiont/` (workspace-`exclude`d) compiles+links the FULL stack into ONE binary — lance-graph + lance7/lancedb0.30 + ndarray + ractor + surrealdb(kv-lance) + OGAR. **Verified green** (real git-deps build, `CARGO_EXIT=0`, 4.3 MB binary runs): unified `lance 7.0.0 / lance-index 7.0.0 / lancedb 0.30.0 / datafusion 53.1.0 / arrow 58` — no lance-6/7 split. It is a **living integration harness** (`Dockerfile` + portable git-deps `Cargo.toml`) that tracks each fork's canonical branch (`master`/`main`), **NOT** a frozen snapshot; every per-session `jirak` branch is stale (HEAD ⊂ main/master, 0 unique commits). **`TD-SURREALDB-KVLANCE-LANCE7` PAID** — surrealdb `main` carries the lance-7 bump. PR #555 adds the 5+3 council `INTEGRATION_PLAN.md` (loose-end ledger → the Spain-grid acceptance gate). **Honest state:** linked into one binary; the *runtime edges* between the five crates are still pending integration (Grid→NodeRow bridge, kanban loop). Battle-test plan (probes A1–E3) queued behind the singleton-BindSpace → SoA switch. Refs: PR_ARC #555, EPIPHANIES `E-GOLDEN-IMAGE-IS-A-LIVING-HARNESS`, AGENT_LOG 2026-06-20.
+
+---
+
 > **2026-06-19 — IN PR (branch `claude/edge-distance-basin-node-epiphany`)** — **basin-IS-a-node: the substrate is a virtual tree of MailboxSoAs, navigated by pure key arithmetic.** New `graph::mailbox_scan::{members, memberof, BasinOf}` — one-to-many (`members` = direct children one HHTL tier down) / many-to-one (`memberof` = parent via `NiblePath::parent`, returns `BasinOf::Local(row)` or `BasinOf::Route(NiblePath)` when the parent lives in another shard — the HHTL prefix IS the route key, **no coarse-fingerprint table**; `None` only at the top tier). Realizes `E-BASIN-IS-A-NODE` with **no ownership restructure** — the tree is the radix trie of the keys, the SoA stays flat, the zero-copy/Lance-tombstone invariant is untouched; all navigation is **zero value decode** (F2-guarded). 16/16 mailbox_scan tests, clippy clean. **Probe (perturbation-sim `basin_placement_learning.rs`): field-perturbation placement learns the basin tree — green, mean tree-hop 1.00 vs 4.13 random (75.8 % tighter)**, promoting the one CONJECTURE in `E-BASIN-IS-A-NODE` to measured FINDING [G]. **Three epiphanies this arc:** `E-BASIN-IS-A-NODE` (basin=node; distance=hop=`node_distance(PrefixDepth)`; 4-ary fan-out = Morton tile pyramid = perturbation-learnable field), `E-FAMILY-NODE-IS-META-AWARENESS` (the parent node IS the coarse Walsh band of its subtree — meta-awareness is structural, not a column), `E-GUID-SELF-ROUTES-THE-BASIN-TREE` (HHTL-tier truncation of the GUID = every ancestor's route key; the GUID self-routes). **Capstone:** one 512 B key, read five ways — representation / ontology / compute (Morton pyramid) / learning / meta-awareness — four of the five are key-resident zero-decode. Builds on #544/#545/#548 (mailbox_scan facets) + `E-COARSE-QUANTIZER-IS-SCALE-FREE-ROUTER`.
 >
 > **2026-06-18 — branch work** — **OGAR → lance-graph-ontology wiring closed.** `OntologyRegistry::class_id_for_guid(&NodeGuid) -> Option<ClassId>` composes the canon GUID→NiblePath fold (`contract::hhtl::NiblePath::from_guid_prefix`) with the registry's `NiblePath ↔ entity_type` bijection — the single missing join an audit this session surfaced (both halves were built with **ZERO callers**). A node carrying a classid now resolves its ontology class → `RegistryClassView` (fields/labels/template/DOLCE). Round-trip test pins the `classid_lo ↔ entity_type` consistency the audit flagged; zero-fallback (unbound → None) + lossy-fold refusal (high classid u16 → None). Completes the third "classid → X" axis reachable from a GUID (read-mode ✅ ocr.rs, methods ✅ unicharset keystone, ontology-shape ✅ now); aligns with `E-ODOO-CORE-FIRST-STRUCTURAL` (Core-side resolution, no new predicate/type). 16 ontology tests green; `registry.rs` clippy-clean + fmt clean. EPIPHANIES `E-OGAR-ONTOLOGY-WIRED-1`. Pre-existing `lance-graph-ontology` clippy debt noted (`TD-ONTOLOGY-LINT`).

.claude/board/PR_ARC_INVENTORY.md

@@ -49,6 +49,22 @@
 
 ---
 
+## #555 lance-graph: symbiont golden-image plan (5+3 council ledger) + the living-harness reframe
+
+**Status:** OPEN 2026-06-20, branch `claude/symbiont-golden-image-plan`. Adds `crates/symbiont/INTEGRATION_PLAN.md` (the council loose-end ledger → Spain-grid acceptance gate). The golden-image crate itself landed **direct on `main`** (`82013145` crate → `e24b8626` OGAR→main → surrealdb→main fix): a workspace-`exclude`d probe that compiles+links the full stack into ONE binary.
+
+**Added:** `crates/symbiont/{Cargo.toml (portable git-deps), Dockerfile (rust:1.95 → debian-slim, build/CI validation), README, src/main.rs, INTEGRATION_PLAN.md}`. Root `Cargo.toml` exclude entry.
+
+**Locked:** the golden image is a **living integration harness, not a snapshot** — it tracks each fork's canonical branch (ndarray `master`; ractor/surrealdb/OGAR `main`), never `jirak` (proven stale: HEAD ⊂ main/master, 0 unique commits, all four forks) and never a frozen rev. surrealdb + OGAR resolve to ONE `surrealdb#main` source (no `[patch]` — cargo forbids patching a url to itself). **Verified green:** real git-deps build `CARGO_EXIT=0`, binary runs, unified `lance 7.0.0 / lance-index 7.0.0 / lancedb 0.30.0 / datafusion 53.1.0 / arrow 58` (no lance-6/7 split) → `TD-SURREALDB-KVLANCE-LANCE7` PAID.
+
+**Deferred:** the Grid→NodeRow bridge, kanban-loop wiring (2 of 5 arrows), `surreal_container` live dep (version-unblocked, execution-blocked on D-PG-6). Battle-test plan (probes A1–E3) queued behind the singleton-BindSpace → SoA switch.
+
+**Confidence (2026-06-20):** HIGH that the full stack resolves + compiles + links on the lockstep pins (built green). The *runtime edges* between the five crates remain the open integration work — "linked, pending integration" is the honest state.
+
+**Cross-ref:** EPIPHANIES `E-GOLDEN-IMAGE-IS-A-LIVING-HARNESS`; TECH_DEBT `TD-SURREALDB-KVLANCE-LANCE7` (PAID); AGENT_LOG 2026-06-20.
+
+---
+
 ## #542 the q2-substrate grounding arc — E-OGAR-IS-FOUNDRY capstone + 5+3 council + the key→row baton
 
 **Status:** MERGED 2026-06-18 (merge commit `faca377f`), branch `claude/q2-substrate-grounding`. The platform-level reading + the council that hardened it, + the one buildable prerequisite. Additive to `lance-graph-contract` only.

.claude/board/TECH_DEBT.md

@@ -282,7 +282,7 @@ FINDING D-CLS↔D-ARM-14 (EPIPHANIES).
 
 ### TD-SURREALDB-KVLANCE-LANCE7 (deps — surrealdb-core still pins lance =6.0.0)
 
-**Status: Open — blocker CONFIRMED SHALLOW (operator 2026-06-15: "surrealdb just needed 7.0.0 / lancedb 0.30 pin").** The kv-lance backend is already implemented in-tree; the ONLY remaining blocker is the version pin (no deep architectural work). The 2026-05-31 lance `6.0.0 → =7.0.0` / lancedb `0.29.0 →
+**Status: PAID 2026-06-20 (verified on surrealdb `main`) — was Open, blocker CONFIRMED SHALLOW (operator 2026-06-15: "surrealdb just needed 7.0.0 / lancedb 0.30 pin").** The kv-lance backend is already implemented in-tree; the ONLY remaining blocker was the version pin (no deep architectural work). The 2026-05-31 lance `6.0.0 → =7.0.0` / lancedb `0.29.0 →
 =0.30.0` bump (lance-graph, `claude/jolly-cori-clnf9` → PR #445) moved this
 workspace's `object_store` transitive `0.12 → 0.13.2`. The AdaWorldAPI/surrealdb
 fork's `surrealdb-core` already runs `object_store = "0.13.0"`, but its
@@ -296,6 +296,8 @@ EPIPHANIES E-LANCE7-OBJECTSTORE-SURREALDB; root `Cargo.toml` RESOLVED(A2/B2).
 (The earlier `TD-LANCE-6.0.1-PIN` — only ever a root Cargo.toml comment, never a
 row here — is moot: no lancedb pinned lance `=6.0.1`; `0.30.0 → 7.0.0` superseded it.)
 
+**2026-06-20 update (PAID — verified):** the 3-pin bump HAS LANDED on `AdaWorldAPI/surrealdb` `main`. Direct manifest read at `main` (173e99c): `surrealdb/core/Cargo.toml` now pins `lance = "=7.0.0"`, `lance-index = "=7.0.0"`, `lancedb = "=0.30.0"`, `arrow-array/schema = "58"`. Confirmed end-to-end by the `symbiont` golden-image build (git-deps): the whole graph (lance-graph + surrealdb kv-lance + OGAR + ractor) resolved to ONE `lance 7.0.0 / lance-index 7.0.0 / lancedb 0.30.0 / datafusion 53.1.0 / arrow 58` — no lance-6/7 split. Note: the stale `jirak` branches still carry the OLD lance-6 pin (see EPIPHANIES E-GOLDEN-IMAGE-IS-A-LIVING-HARNESS); tracking `main` is what delivers the unified lance-7. Residual (separate item): `surreal_container`'s surrealdb dep is still commented out (version-unblocked, execution-blocked on wiring D-PG-6) — that is a wiring task, not this version debt.
+
 **2026-06-15 update (operator ground truth):** the fix is exactly the 3-pin bump (`lance` / `lance-index` `=7.0.0`, `lancedb` `=0.30.0`) in `AdaWorldAPI/surrealdb` `surrealdb/core/Cargo.toml` — a write to the surrealdb FORK, **outside this session's 3-repo scope** (ndarray / lance-graph / turbovec; `add_repo` unavailable this session, so it can't be pushed from here). Once it lands, `surreal_container` resolves → unblocks **D-PG-6** (Rubicon kanban VIEW), **D-MBX-9 OUT** (`LanceVersionScheduler` over `versions()`), **identity-architecture Phase H** (SurrealQL read glove). **Companion (ractor):** the `--features supervisor` blocker is the `AdaWorldAPI/ractor` fork's `MessagingErr::Saturated` non-exhaustive match (fork ~2 commits behind upstream's error-enum fix) — sync the fork with upstream; also a fork write, also out of this session's scope. We don't use the messaging path; default builds are unaffected (ractor is `optional`, off by default).
 
 ---

crates/symbiont/Cargo.toml

@@ -37,18 +37,21 @@ path = "src/main.rs"
 lance-graph = { path = "../lance-graph" }
 perturbation-sim = { path = "../perturbation-sim" }
 
-# ── external AdaWorldAPI forks: git deps, pinned to the shared dev branch ──
+# ── external AdaWorldAPI forks: git deps ──
+# ractor: jirak branch (carries this session's MessagingErr::Saturated fix; on github).
+# surrealdb + OGAR: `main` — each fork's jirak HEAD is an ANCESTOR of its main
+# (main is the canonical superset), and kv-lance lives on surrealdb main. Pinning
+# surrealdb to main matches OGAR's own surrealdb pin, so they resolve to ONE source.
 ractor = { git = "https://github.com/AdaWorldAPI/ractor", branch = "claude/jirak-math-theorems-harvest-rfii13" }
-surrealdb-core = { git = "https://github.com/AdaWorldAPI/surrealdb", branch = "claude/jirak-math-theorems-harvest-rfii13", default-features = false, features = ["kv-lance"] }
+surrealdb-core = { git = "https://github.com/AdaWorldAPI/surrealdb", branch = "main", default-features = false, features = ["kv-lance"] }
 # OGAR tracks `main` (its jirak commit 3016c78 is an ancestor of main — main is a
 # strict superset; there is no separate OGAR jirak branch on github).
 ogar-vocab = { git = "https://github.com/AdaWorldAPI/OGAR", branch = "main" }
 ogar-ontology = { git = "https://github.com/AdaWorldAPI/OGAR", branch = "main" }
 ogar-adapter-surrealql = { git = "https://github.com/AdaWorldAPI/OGAR", branch = "main", features = ["surrealdb-parser"] }
 
-# OGAR git-deps surrealdb on its own branch (`main`); redirect ALL surrealdb
-# deps in the graph to the same branch we use, so it resolves to ONE surrealdb.
-[patch."https://github.com/AdaWorldAPI/surrealdb"]
-surrealdb-ast = { git = "https://github.com/AdaWorldAPI/surrealdb", branch = "claude/jirak-math-theorems-harvest-rfii13" }
-surrealdb-parser = { git = "https://github.com/AdaWorldAPI/surrealdb", branch = "claude/jirak-math-theorems-harvest-rfii13" }
-surrealdb-core = { git = "https://github.com/AdaWorldAPI/surrealdb", branch = "claude/jirak-math-theorems-harvest-rfii13" }
+# No [patch] needed: this dep and OGAR's transitive surrealdb (ast/parser/core)
+# all resolve to https://github.com/AdaWorldAPI/surrealdb#main — ONE source —
+# and cargo unions the features so kv-lance is enabled on the shared
+# surrealdb-core. (cargo forbids patching a git URL to the same git URL, which is
+# why the earlier jirak-redirect patch failed; aligning on main removes the need.)