Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 63 additions & 0 deletions .claude/board/EPIPHANIES.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,66 @@
## 2026-08-18 — E-PIN-LANCE9-LANCEDB033-DF541-ARROW58-NO-DF53-1

**Status:** RULING `[operator]` + same-day discharge, measured.

**The ruling.** lance 9 / lancedb 0.33 / datafusion 54.1 (**no DF 53**) /
arrow 58 are ALWAYS pinned across AdaWorldAPI forks, usually consumed via
`[patch]` of the upstream repository git. DF 53 existed only for older syntax
in an out-of-scope research crate; all of lance-graph is DF-54-certified,
and single-major DF 54.1 is the discipline ("without DF 53/54 parallelism
it's much better, easier, faster to handle").

**Measured before acting:** the lock carried datafusion 53.1.0 AND 54.1.0;
the ONLY DF-53 source was `deltalake 0.32.4` (`^53.1.0`) behind the `delta`
feature — which was already NON-default and documented BROKEN (0.32 removed
`DeltaTableProvider::try_new`; the reader was never refactored). Checked the
registry: deltalake-core tops out at 0.32.4 / DF ^53.1.0 — no DF-54 deltalake
exists, so a bump could not discharge the ruling; removal could.

**Discharged:** `delta` feature + `deltalake`/`url` optional deps +
`DeltaTableReader` removed (Cargo.toml carries the dated removal note; a
future Delta reader returns only with a DF-54-compatible deltalake, as its
own deliberate PR). `DataSourceFormat::Delta` (a catalog metadata tag) stays.
**Post-removal lock: exactly ONE datafusion = 54.1.0; zero deltalake
entries.** `cargo check -p lance-graph` green (needed `protobuf-compiler`
installed in-sandbox — lance's prost build; the Dockerfiles already install
it). Docker pins surveyed on request: root + avx512 Dockerfiles = Rust
1.97.1 + protobuf-compiler/cmake, no feature references to delta, versions
purely from Cargo.lock — removal is docker-safe. The symbiont
Dockerfile's stale `rust:1.95` pin is MOOT: **symbiont is DEPRECATED**
(operator, same day — superseded by the supervisor/persistence arc,
PRs #879/#911/#912/#913) and is not live surface.

**Same-day scope pivot (operator, BINDING for RP-SEAL):** rustynum is NOT a
source of truth — "no rustynum, everything ndarray"; it is the historical
donor already ported into AdaWorldAPI/ndarray. The RP-SEAL workflow script
was corrected in place (source map + the two cell briefs naming rustynum);
the in-flight independent pass could not be force-stopped in this harness
build, so the ruling additionally binds consolidation as a hard filter
(re-anchor or surgically re-run any finding citing rustynum/symbiont).
Deltalake removal ratified in the same exchange ("we don't need deltalake").

**Same-day factual correction (operator-pointed, verified at source):** the
"no DF-54 deltalake exists" premise holds only for crates.io RELEASES
(deltalake-core <= 0.32.4 / DF ^53). delta-io/delta-rs **main** already pins
`datafusion = 54.0.0` + `arrow = 58` (workspace Cargo.toml, fetched
2026-08-18) — so restoration is available NOW via the house mechanism (git
dep on the upstream repository, pinned rev) + a `DeltaTableReader` refactor
to the current builder API. The removal stands on the NEED ruling, not on
availability; the in-repo notes were corrected so no future session treats
restoration as blocked on a registry release.

**Second discharge — the lotus BLOCKER:** the [patch → upstream-git]
mechanism sanctioned consulting the upstream lance repository as source; the
exact v9.0.0 tag is cloned (`/tmp/sources/lance-9`, matching the Cargo.lock
checksum) plus current upstream (`/tmp/sources/lance-main`) for the RP-SEAL
two-column discipline. D-LOTUS-6's "lance source absent" BLOCKER is LIFTED;
capability findings deliberately enter through the RP-SEAL Domain-A
independent passes, not this entry (independence rule).

**Supersedes in place:** CLAUDE.md's "BOTH MAJORS ARE REQUIRED — do NOT fix
Cargo.lock to one" datafusion note (written when `delta` was default and
load-bearing) — corrected in the same commit.

## 2026-08-18 — E-FORD-REAL-PUBLICATION-IDENTITY-IS-ARRIVAL-DEPENDENT-1

**Status:** FINDING (VERIFIED at file:line) + pre-registered falsifier landed
Expand Down
8 changes: 8 additions & 0 deletions .claude/board/INTEGRATION_PLANS.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
## 2026-08-18 — erasure-seals-compaction-research-v1 (RP-SEAL) — ACTIVE

Operator-delivered 15-researcher program (5 domains x builder/adversary/
scout) on bidirectional erasure-coded seals + locality-aware compaction in
versioned SoA grid stores. `.claude/plans/erasure-seals-compaction-research-v1.md`.
Independent pass dispatched as workflow `wf_ca974718-1b4`; consolidation +
tiered attack follow. Subsumes the lotus charter's phases 2-8.

## 2026-08-13 — weather-soa-bake-v1 (PLAN; the missing Zarr→NodeRow bake)

Plan: `.claude/plans/weather-soa-bake-v1.md`. **Does not supersede
Expand Down
18 changes: 18 additions & 0 deletions .claude/board/LATEST_STATE.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,21 @@
## 2026-08-18 — lance-graph #961 (MERGED 0cc171f) — LOTUS research arc opens: frontier audit + F-ORD-REAL falsifier

### Current Contract Inventory — no new types (docs + tests only)

- `docs/lotus/LOTUS-FRONTIER-AUDIT.md` — Phase 0 archaeology; the verified
F-ORD defect chain (`content_hash` folds arrival-minted `stream_position`,
`persist_sink.rs:414`, contradicting the struct's own doc); seal = 3×
O(bytes) passes with the batch resident up to 3× (descriptor doctrine
unrealized: `BatchWriter<Vec<u8>>`); lance crate source ABSENT from sandbox
(Phase 6 BLOCKED); §6: cycles become THIN not permeable (Regime A
pipelining; rung-qualified frontier; linear-text vs tile split per class).
- `docs/lotus/F-ORD-REAL-FALSIFIER.md` + `cycle_driver.rs` tests: GREEN
defect pin `f_ord_real_defect_pin_arrival_order_leaks_into_batch_hash`
(fails loudly when a fix lands → deliberate re-pin) + `#[ignore]`d RED
`f_ord_real_publication_identity_is_arrival_order_independent`.
- Gates: supervisor suite 28 passed / 1 ignored (`--features cycle-driver`);
RED verified red under `--ignored`; fmt clean; zero new clippy warnings.

## 2026-08-17 — branch `claude/hydrate-staging-merge` — `lance-graph-hydrate`: the deferred staging/publish merge lands (closes `ISS-HYDRATE-DIR-AND-FILE-DUPLICATE-THEIR-STAGING-BODIES`)

### Current Contract Inventory — new private module (`crates/lance-graph-hydrate/src/publish.rs`)
Expand Down
27 changes: 27 additions & 0 deletions .claude/board/PR_ARC_INVENTORY.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,30 @@
## 2026-08-18 — lance-graph #961 (MERGED, squash 0cc171f) — LOTUS Phase 0/1: frontier audit + F-ORD-REAL pre-registered falsifier

- **Added:** `docs/lotus/LOTUS-FRONTIER-AUDIT.md` (Phase 0 archaeology, 4
lenses, graded VERIFIED/INFERENCE/HYPOTHESIS/BLOCKER; §6 answers the
operator's permeability/amortization question: the cycle becomes THIN, not
permeable — trailing-publication pipelining Regime A; rung-qualified
frontier via the shipped `EpistemicMode::for_rung` ladder; the linear-text
vs tile workload split resolved per class); `docs/lotus/
F-ORD-REAL-FALSIFIER.md`; two pre-registered tests in `cycle_driver.rs`
behind the existing `cycle-driver` feature (GREEN two-sided defect pin +
`#[ignore]`d RED falsifier, verified red under `--ignored`: hashes
2604999916736672513 vs 4858955943411201665 for the identical semantic set).
- **Locked:** the falsifier perturbs the process that CREATES the key (cast()
call order), never post-mint slots (the operator's F-ORD sharpening); no
fix mechanism prescribed — four candidates listed, per-workload, Phase 2+
council-gated.
- **Deferred / gated:** D-LOTUS-3..9 (design/comma/temporal-seam/benchmarks/
verdict); D-LOTUS-6 BLOCKED on the absent lance crate source (sandbox has
no registry copy; needs `cargo fetch` or sanctioned consult);
`temporal.rs:396`/`:410` retired-type doc-drift correction owed to the next
phase PR.
- **Docs:** EPIPHANIES `E-FORD-REAL-PUBLICATION-IDENTITY-IS-ARRIVAL-DEPENDENT-1`;
STATUS_BOARD `lotus-seal-fractal-commit-frontier` D-LOTUS-1..9.
- **Confidence:** high on the defect chain (every link read at file:line this
session; the doc-contradiction is quoted); the §6 amortization mechanisms
are INFERENCE until the Phase 5 benchmarks run.

## 2026-08-12 — lance-graph #946 (MERGED) — D-CZ-1 PASSES; D-CZ-0 had NO artifact behind it; + the arc's rated formula matrix

- **The finding that forced the run.** `substrate-comfort-zones-v1` §1's
Expand Down
19 changes: 16 additions & 3 deletions .claude/board/STATUS_BOARD.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
## erasure-seals-compaction-research-v1 — RP-SEAL (operator charter, DISPATCHED 2026-08-18)

Plan: `.claude/plans/erasure-seals-compaction-research-v1.md` (the operator's
15-researcher program; supersedes lotus deliverables 3-9's sequencing).
Independent pass = background workflow `wf_ca974718-1b4`: 5 domains
(A Lance storage / B spatial layout / C erasure coding / D temporal /
E SoA-cache) x 3 roles (builder/adversary/scout); adversaries on the
strongest tier, builders+scouts on the grindwork tier; first pass blind to
docs/lotus/** and all boards (independence rule). Consolidation (evidence
matrix + cross-domain graph) and the tiered attack pass run main-thread
AFTER all 15 reports land. Reports: session scratchpad `rp-seal-v1/`,
committed at consolidation as Appendix H.

## lotus-seal-fractal-commit-frontier — research arc (PRE-REGISTERED 2026-08-18)

Charter: operator, 2026-08-18 (research + architecture; "first audit the
Expand All @@ -7,12 +20,12 @@ metaphor becomes a type name without council approval.

| D-id | Deliverable | Status |
|---|---|---|
| D-LOTUS-1 | LOTUS-FRONTIER-AUDIT.md — Phase 0 archaeology, 4 lenses, VERIFIED/INFERENCE/HYPOTHESIS/BLOCKER graded; §6 answers the permeability/amortization question | **In PR** |
| D-LOTUS-2 | F-ORD-REAL-FALSIFIER.md + the pre-registered tests (GREEN defect pin + `#[ignore]`d RED falsifier, `cycle_driver.rs`) | **In PR** — RED lands BEFORE any fix, per charter |
| D-LOTUS-1 | LOTUS-FRONTIER-AUDIT.md — Phase 0 archaeology, 4 lenses, VERIFIED/INFERENCE/HYPOTHESIS/BLOCKER graded; §6 answers the permeability/amortization question | **Shipped** — PR #961, 0cc171f |
| D-LOTUS-2 | F-ORD-REAL-FALSIFIER.md + the pre-registered tests (GREEN defect pin + `#[ignore]`d RED falsifier, `cycle_driver.rs`) | **Shipped** — PR #961, 0cc171f; RED landed BEFORE any fix, per charter |
| D-LOTUS-3 | LOTUS-SEAL-DESIGN.md (16⁴ tree, petal seal, H(parent)=H(children) — NEW design per audit §2.3) | Queued (post-verdict) |
| D-LOTUS-4 | COMMA-MODULATION-EXPERIMENT.md (petal-index-tier comma; locality-vs-resonance trade; "if it doesn't survive measurement, delete it") | Queued |
| D-LOTUS-5 | TEMPORAL-FRONTIER-SEAM.md (rung-qualified frontier visibility; hindsight-invariance falsifier; audit §6.4) | Queued |
| D-LOTUS-6 | PREPARED-ARTIFACT-PUBLICATION.md | **BLOCKED — lance crate source absent from sandbox** (audit §2.2); needs `cargo fetch` or sanctioned source consult |
| D-LOTUS-6 | PREPARED-ARTIFACT-PUBLICATION.md | **UNBLOCKED 2026-08-18** (operator pin ruling sanctioned the upstream-git source consult; exact v9.0.0 tag + current upstream on disk) — now routed through RP-SEAL Domain A rather than written solo, per the research charter |
| D-LOTUS-7 | BENCHMARK-PLAN.md (seal/append split; cycle-major vs tile-major k∈{1,4,16}; F-AMORT version-range scaling; F-MEM RAM high-water freeze-vs-petal; viewport partial hydration) | Queued |
| D-LOTUS-8 | PRE-REGISTERED-FALSIFIERS.md (the F-* catalogue) | Queued |
| D-LOTUS-9 | Final verdict A-E | Queued — gates all implementation |
Expand Down
Loading
Loading