AdaWorldAPI · AdaWorldAPI · Sep 16, 2026 · Sep 16, 2026 · Sep 16, 2026 · Sep 16, 2026
diff --git a/.claude/board/EPIPHANIES.md b/.claude/board/EPIPHANIES.md
@@ -1,3 +1,145 @@
+## 2026-09-16 (15) — E-THE-SPINE-IS-WHATEVER-THE-READER-ALREADY-HAS-AN-ADDRESS-FOR-1 — the operator's quack redirect, and the four errors of one session that all substituted an address for the thing
+
+**Status:** OPERATOR-RULED (the redirect, verbatim below) + MEASURED (the census
+numbers, re-run over the whole tree after codex's review of #1240).
+**Confidence:** HIGH on the census — the corpus mechanism is now a directory
+walk, so the number is a property of the tree rather than of a file list I
+chose. The spine ruling is the operator's; it is recorded, not derived.
+
+### The redirect, in the operator's own four messages
+
+> *"cypher is just a cheap proof of concept / and an even better proof of
+> concept is quack"* → *"my point is quack is the spine you need to rebuild
+> from"* → *"any graph traversal in the end will be a modified version of it /
+> any SPOG query will be just another flavor / and the benefit is quack /
+> duckdb no AI will ever ask what it is, you can use muscle memory"* →
+> *"everything else is running in circles around whats not in your training"*.
+
+**The argument is muscle memory, not elegance, and reading it as elegance is
+how it gets lost.** `lance_graph_quack::Query { filter, agg }` — filter a
+population, reduce over the survivors — is a shape every reader, every author
+and every model already holds without being taught. A novel IR has to be taught
+to each of them, every time, and the teaching cost recurs on every future
+session. That is the same test the Java surface passes one tier down
+(lance-graph-java `CLAUDE.md` § *THE JAVA SURFACE IS `sql()`*): the boring front
+wins because nobody has to learn it, not because it is nicer.
+
+The last message is the mechanism behind the other three, and it is the one
+worth keeping: **circling is the symptom of building on what is not in
+training.** Work that re-derives its own vocabulary every session does not
+accumulate — each session pays the teaching cost again and mistakes paying it
+for progress.
+
+### What it cancels, stated plainly because I had it queued
+
+The Cypher→mask lowering (`.claude/plans/cypher-mask-lowering-v1.md`, Wave 1)
+would have been a **third** lowering onto one floor — beside quack's `lower`
+and `lgj-abi`'s `plan_eval`, both already pinned equal to `lance-graph-mask-risc`
+by a differential. Three dialects, one evaluator, and two of them novel.
+
+quack's one missing leg is the **hop** (`src_mask → edge lane → dst_mask`). That
+is one brick, and it makes SPOG a *flavour* of a shape that already exists
+rather than a fourth thing to learn. It is now the recommended next brick
+(task #10 / PR5), where before it was gated behind PR1-4.
+
+### The census defect — same shape, and self-inflicted on the day the rule landed
+
+`w0b_corpus_census` was built to answer §7.0's STOP gate: what fraction of the
+Cypher the tree actually contains lowers to a mask. Its first corpus was a
+**hand list of three files**, chosen from a grep — and a grep structurally
+cannot see a query built as a raw string literal. codex flagged it on #1240.
+
+| | corpus | classified | Full (mask-lowerable) |
+|---|---|---|---|
+| as first reported | 3 files, hand-listed | 20 | 15 — **75.0 %** |
+| after a quote-parity fix | same 3 files | 50 | 23 — **46.0 %** |
+| after review: directory walk | **33 files** of 1451 walked | **303** | 113 — **37.3 %** |
+
+The corpus grew **17×** and the headline halved. The root cause is named in
+this repo's own P0 rule — *grep FINDS, reading DECIDES* — which was written
+into `CLAUDE.md` **the same day**. Writing a rule is not the same as being
+immune to it.
+
+**And the file count in that last row was itself wrong when first published —
+`27`, corrected here to `33`.** A second review pass found that the census
+kept only the FIRST source per query literal, so a file whose every query also
+appeared elsewhere vanished from the provenance entirely. The classification is
+untouched by it (342 candidates, 303 classified, 113 Full, 37.3 % — all
+unchanged; dedup by literal was always right, only the attribution was not).
+
+The uncomfortable half is that **the repo already held the right number**: the
+census's own module doc said *33 files* while the program it documents printed
+*27*, in the same commit, and I quoted whichever was nearer to hand — the doc's
+33 into the source, the program's 27 into the plan and into this entry. Nothing
+flagged it, because neither number is wrong-looking on its own. Third instance
+in one session of two values for one quantity (see also G-F, whose summary row
+contradicted its own document's body four sections above it).
+
+Three classifier defects rode in with the fix (inline pattern properties never
+read, 4 maps → 53 hits; `DISTINCT`-over-a-value never firing, 37 hits; and
+`run.sh`'s `|| true`, which let a failed harvest leave stale TSVs to be counted
+while `provenance.txt` already carried the new commits — a clean exit reporting
+old measurements against a new checkout).
+
+### The four errors of this session share ONE shape
+
+| what I substituted | for what |
+|---|---|
+| a grep pattern | the corpus |
+| a section number and a symbol name | the argument (operator: *"reverse grep… pattern matching that doesnt make any context for me"*) |
+| a stale 46 % | a decision I asked the operator to make (withdrawn — 0 of 303 fail to lower, so no ruling was ever needed) |
+| an A/B/C fork I raised as open | a ruling `cypher-mask-lowering-v1` §5.2 had already made |
+
+**An address is not the thing.** Each one is cheap to produce and looks like
+work. And the redirect above is the positive form of the same insight: build on
+the spine the reader already has an address for, because a novel IR is an
+address nobody can resolve.
+
+Operational consequence, and it is the cheap half: **plain words first; the
+symbol, file and section go at the END, as receipts.** A report that opens with
+`§5.2 / TERNLOG 0x86 / D-MAR-2` has told the reader nothing they can act on.
+
+### The three rulings that came with it
+
+**Alpha channel first, and the reason is not sequencing convenience.** Operator:
+the SPOG alpha channel *"affects the underlying storage and table 'multitenant'
+access… writing to alpha split tunnel without changing ontologies itself as
+saccade focus of attention sparse write and meta awareness of simultaneous
+rung"*, where *"before it was 10 rung not talking to each other despite
+kanban_actor.rs or deprecated 'one at a time'"*. Three things are being bought:
+a write path that does not rewrite the shared ontology (which is what makes
+concurrent attention safe); a channel property rather than a consumer
+convention; and **simultaneous rungs** — levels of thinking interact, and
+interaction requires the priors to sit on the same level. So any second consumer
+of `ogar_loco::TERNLOG = 0x86` inherits whatever simultaneity contract the alpha
+channel establishes first. `cypher-mask-lowering-v1` §5.2's OQ-9 said "defer
+rather than race"; this says *why* deferring is correct rather than merely
+polite.
+
+**`RevisionKind` lives beside `belief.rs`.** Operator: *"belief is historically
+correct but needs to be adjusted for proper wiring"* — so the planner, not the
+contract (option A of `mask-algebra-revision-read-v1.md` §5 Q1). The history is
+right; the wiring is the work. The adjustment is that plan's **D-MAR-2**.
+
+**The 46 % question is withdrawn, not answered.** Operator: *"46% negligable how
+do i know what you are talking about"* — a fair hit twice over. I asked for a
+ruling on a word from a plan the operator did not write, without supplying what
+anyone would need to judge it; and the number had already moved to 37.3 % (see
+the table above). Re-reading the census, **0 of 303 queries fail to lower** —
+Split is a two-stage plan, not a failure — so there was never a ruling to make.
+
+### Receipts
+
+- Plan: `.claude/plans/lance-graph-as-the-modelgraph-v1.md` §§14-18 (the mindset
+  check, the census, `LabelDTO` as the answer to OQ-1, the rulings, the redirect).
+- Instrument: `crates/lance-graph/examples/w0b_corpus_census.rs` — the corpus is
+  now `rust_sources()`, a walk, so the denominator is the tree's property.
+- Gate discipline, second measured instance: `SUPERSESSION-INDEX.md` was
+  regenerated BEFORE these board writes and went red at four successive SHAs on
+  #1240 — exactly the failure `CLAUDE.md` § *Regenerate LAST, after the board
+  writes* already records from #1085. The rule is right; it needs to be executed
+  in the order it states.
+
 ## 2026-09-16 (14) — E-THE-NET-ARM-RANKED-ON-A-PARTIAL-SUM-AND-ITS-ONLY-APPARENT-SIGNAL-WAS-THAT-BUG-1 — entry (13)'s NET row is re-measured; the arm is a census on BOTH arms, not one
 
 **Status:** MEASURED — re-run of `D-HXP-8` arm 1 after a one-line ranking fix in

diff --git a/.claude/board/INTEGRATION_PLANS.md b/.claude/board/INTEGRATION_PLANS.md
@@ -1,3 +1,33 @@
+## 2026-09-16 (1) — lance-graph-as-the-modelgraph-v1 — the ModelGraph stops being a transient Rust object and becomes addressed rows in the V3 SoA → `.claude/plans/lance-graph-as-the-modelgraph-v1.md`
+
+**Status:** PROPOSAL (operator-set endgame: *"endgame should be to wire
+lance-graph as ModelGraph"*). No code. The document is a SURVEY whose point is
+that the chain is **already built except one step**: `ruff_cpp_spo::extract_tree`
+→ `ruff_spo_address::mint` (16 B, byte-identical to `FacetCascade`, **no
+dependency edge**) → `ogar-from-ruff::mint` → `lance_sink` → `as_le_bytes()`,
+all live and unstubbed, stopping at a `Dataset::write` that `lance_sink.rs`
+names out of scope in its own words. G-C is that write.
+
+The direction is FORCED, not chosen: no ruff crate may compile against
+lance-graph (verified — `lance.graph` appears in `ruff/crates/*/Cargo.toml`
+only inside two `description =` strings), so the spine can only be the HOME,
+fed across a byte boundary. Matches `assembler-vs-storage-substrate.md`.
+
+Confirms two operator recollections and corrects a third: **two codegen arms**
+are `ruff_cpp_codegen` (→ Rust `MethodSig` source) and `ruff_spo_address` (→ the
+`(part_of:is_a)` rank-mint) — NOT `ruff_python_codegen`, which is upstream
+ruff's `Generator`/`Stylist`. **arm-discovery is the table→SPO arm** exactly as
+described (`translator.rs`: ARM confidence → NARS frequency, evidence `m` →
+`m/(m+k)`, canonical `TruthU8` = the `CausalEdge64` wire), and it already names
+`ruff_spo_triplet::Triple` as its downstream. **JSONML does not exist** in any
+of the five repos.
+
+Carries G-A..G-E and waves W1-W4, each with a falsifier. G-E is the
+uncomfortable one and is independent of the endgame: **quack has no DuckDB in
+its loop at all** — zero dependency, every "DuckDB" in it a doc comment, its
+oracles hand-written Rust. What is called parity today is quack ↔ its own
+oracle; task #8's DuckDB differential fixtures remain unstarted.
+
 ## 2026-09-14 (4) — hexagon-plasticity-v1 — can six learned rails discover local adjacency, and can ARM promote a cue to a path? → `.claude/plans/hexagon-plasticity-v1.md`
 
 **Status:** ACTIVE (W-1 and W0 RUN before landing; §9 carries their results and

diff --git a/.claude/board/SUPERSESSION-INDEX.md b/.claude/board/SUPERSESSION-INDEX.md
@@ -14,7 +14,7 @@
 ## What this table says
 
 **`BindSpace` is the shape of the problem.** Marked RETIRE, and simultaneously the
-most-referenced symbol here: **68 crate files, 47 plans, 41 of them blind.**
+most-referenced symbol here: **68 crate files, 48 plans, 42 of them blind.**
 That is a programme, not a cleanup.
 
 **`GateState` is the sharpest case: 1 plan names it and *every one* is blind.**
@@ -60,11 +60,11 @@ coverage instead.
 | `GateState` | REPURPOSE | — | 14 | 1 | 1 |
 | `MergeMode` | REPURPOSE | — | 8 | 14 | 13 |
 | `ResonanceDto` | REPURPOSE | `PerturbationDto` | 2 | 12 | 7 |
-| `BindSpace` | RETIRE | — | 68 | 47 | 41 |
+| `BindSpace` | RETIRE | — | 68 | 48 | 42 |
 | `CollapseGateEmission` | RETIRE | — | 5 | 14 | 12 |
 | `ThinkingStyle` | RETIRE-toward-contract | — | 52 | 28 | 24 |
 
-## Table 2 — plans naming a ruled symbol without citing the ruling (75)
+## Table 2 — plans naming a ruled symbol without citing the ruling (76)
 
 Route is **mechanical triage, not a verdict**: `ARCHIVE?` = the plan's own status says
 it shipped; `RESCOPE` = it targets a symbol marked RETIRE; `READ` = neither signal fires
@@ -87,7 +87,7 @@ a licence to act on it.
 | **READ** | `graphrag-doc-retrieval-soa-integration-v1` | `GateDecision` | DESIGN + FIRST CODE. **v1.2 (2026-07-17):**  | 7/10 |
 | **READ** | `hexagon-plasticity-v1` | `MergeMode` | ACTIVE — landed 2026-09-14 on operator go. * | 5/10 |
 | **READ** | `integration-actionhandler-rbac-orchestration-v1` | `GateDecision` | HARDENING (5+3 in progress). | 0/0 |
-| **READ** | `mask-algebra-revision-read-v1` | `StepMask` | DRAFT, awaiting operator ruling on §5 | 2/3 |
+| **READ** | `mask-algebra-revision-read-v1` | `StepMask` | DRAFT, awaiting operator ruling on §5 | 3/3 |
 | **READ** | `mul-calibration-not-verdict-v1` | `GateDecision` | PROPOSAL (unbuilt) — 2026-08-26. PLAN/BOARD  | 6/12 |
 | **READ** | `mul-consumer-build-gate-v1` | `GateDecision` | GATE RUN — 2026-08-27. Discharges D-MCAL-6 a | 3/7 |
 | **READ** | `mul-consumer-census-v1` | `GateDecision` | MEASUREMENT COMPLETE — 2026-08-27. Measureme | 1/2 |
@@ -141,6 +141,7 @@ a licence to act on it.
 | **RESCOPE** | `entropy-closure-causal-ground-v1` | `ThinkingStyle` | PROPOSAL (measured, unbuilt) — 2026-08-26. P | 3/8 |
 | **RESCOPE** | `foundry-consumer-parity-v1` | `BindSpace` | Active | 0/0 |
 | **RESCOPE** | `foundry-roadmap-unified-smb-medcare-v1` | `BindSpace` | Active | 0/0 |
+| **RESCOPE** | `lance-graph-as-the-modelgraph-v1` | `BindSpace` | PROPOSAL (operator-set endgame, 2026-09-16). | 6/6 |
 | **RESCOPE** | `lf-integration-mapping-v1` | `BindSpace` | Active (2026-04-25) | 0/0 |
 | **RESCOPE** | `lite-unified-surrealql-lance-v1` | `BindSpace` | CONJECTURE / design. **Test via feature gate | 0/0 |
 | **RESCOPE** | `ogit-cascade-supabase-callcenter-v1` | `BindSpace` | plan, not implementation. | 0/16 |
@@ -156,6 +157,6 @@ a licence to act on it.
 | **RESCOPE** | `unified-soa-rubikon-integration-v1` | `BindSpace` | — | 8/8 |
 
 - **ARCHIVE?**: 0
-- **RESCOPE**: 55
+- **RESCOPE**: 56
 - **READ**: 20
 - ruled symbols tracked: 14
diff --git a/.claude/harvest/duckdb-headers/README.md b/.claude/harvest/duckdb-headers/README.md
@@ -156,3 +156,76 @@ ht_entry_t.SetPointer
 ht_entry_t.SetSalt
 ht_entry_t.ht_entry_t
 ```
+
+---
+
+## ⊘ §6 IS NOW DISCHARGED — the harvest is reproducible, 2026-09-16
+
+The honesty note above says what was missing: *"The TSV is not committed, there
+is no `args.txt` here, and no DuckDB source is in this tree."* All three are
+fixed, and the fix is committed beside this file:
+
+| file | what it is |
+|---|---|
+| `run.sh` | the whole harvest, one command, `DUCKDB_SRC=… ./run.sh` |
+| `headers.txt` | the ten headers, by path |
+| `args.txt.in` | the clang args as a TEMPLATE — `@DUCKDB_SRC@` is substituted at run time, so the include paths are not pinned to one machine |
+| `ore/**` | the 40 TSVs (4 per header), 348 K, committed |
+| `ore/per-header.tsv` | the counts table, regenerated |
+| `ore/provenance.txt` | DuckDB commit + origin + ruff commit + clang version |
+
+**The source is `AdaWorldAPI/duckdb`** (P0: the fork, never upstream —
+`duckdb/duckdb` is correctly out of this session's scope and returns 403).
+Read-clone: `GIT_LFS_SKIP_SMUDGE=1 git clone --depth 1
+https://github.com/AdaWorldAPI/duckdb /home/user/adaworldapi/duckdb`.
+
+### The counts, re-derived rather than quoted
+
+**Methods: 123 — an EXACT match with the table above, on every one of the ten
+rows.** The recorded observation is confirmed reproducibly; it is no longer a
+number quoting an absent TSV.
+
+Events land at **1620** against the recorded 1622, differing on four rows:
+
+| header | events now | recorded | Δ |
+|---|---|---|---|
+| `common_types_selection_vector` | 311 | 310 | +1 |
+| `common_vector_operations_scalar_executor` | 281 | 286 | **−5** |
+| `common_vector_unified_vector_format` | 7 | 6 | +1 |
+| `execution_expression_executor_state` | 12 | 11 | +1 |
+
+**The cause is not determinable, and that is itself the point.** Methods match
+exactly, so no method was added or removed — the deltas are inside bodies,
+which is what source drift between two DuckDB checkouts looks like. The
+2026-09-14 run recorded no commit, so there is nothing to diff against. That
+is precisely the gap `ore/provenance.txt` now closes: every future run carries
+`duckdb_head`, and a count without its commit is an anecdote.
+
+> **⚠ MY OWN HARNESS NEARLY PRODUCED A FALSE FINDING AGAINST THIS FILE.** The
+> first `run.sh` subtracted a header row from each TSV before counting, and
+> reported **115 / 1612** against the recorded 123 / 1622 — a clean, uniform
+> −1 on every non-empty header, which reads exactly like "the earlier numbers
+> were inflated." They were not. **Neither `methods.tsv` nor `events.tsv` has
+> a header row**; line 1 of each is already data
+> (`duckdb::TemplatedValidityData.EntryCount(idx_t)…`), so the raw line count
+> IS the count.
+>
+> What caught it was the SHAPE of the disagreement: −1 on every non-empty
+> header and 0 on the two empty ones is not how source drift behaves, it is
+> how an off-by-one behaves. **A measurement harness is code and gets the same
+> scepticism as the thing it measures** — this workspace's own rule that a
+> null result is a claim about the apparatus until proven otherwise, applied
+> to a counting script. The corrected rule is now stated at the counting site
+> rather than assumed.
+
+### What this does NOT yet do — the structural arm is still unrun
+
+`harvest_events` is the BEHAVIOURAL arm (four TSVs of ordered method-body
+events). `ruff_cpp_spo` also carries a STRUCTURAL arm that has never been
+pointed at DuckDB: `extract_tree(root, args) -> ModelGraph` (`lib.rs:338`),
+yielding `CppClass` / `CppFunction` / `CppEnum` with `has_function` /
+`inherits_from` / `virtually_overrides` — the ClassView method-resolution
+manifest — which then feeds `ruff_spo_triplet::reassemble` and
+`ruff_cpp_codegen::{project, render}`. That is the arm that answers *what
+DuckDB's operator class tree IS*, where this one answers *what one method
+body does*. Running it on DuckDB is the next step, not a claim made here.
diff --git a/.claude/harvest/duckdb-headers/args.txt.in b/.claude/harvest/duckdb-headers/args.txt.in
@@ -0,0 +1,14 @@
+-x
+c++
+-std=c++11
+-I@DUCKDB_SRC@/src/include
+-I@DUCKDB_SRC@/third_party/fmt/include
+-I@DUCKDB_SRC@/third_party/re2
+-I@DUCKDB_SRC@/third_party/fsst
+-I@DUCKDB_SRC@/third_party/fastpforlib
+-I@DUCKDB_SRC@/third_party/utf8proc/include
+-I@DUCKDB_SRC@/third_party/concurrentqueue
+-I@DUCKDB_SRC@/third_party/pcg
+-I@DUCKDB_SRC@/third_party/tdigest
+-I@DUCKDB_SRC@/third_party/mbedtls/include
+-DDUCKDB_BUILD_LIBRARY
diff --git a/.claude/harvest/duckdb-headers/headers.txt b/.claude/harvest/duckdb-headers/headers.txt
@@ -0,0 +1,10 @@
+common/operator/comparison_operators
+common/operator/constant_operators
+common/row_operations/row_matcher
+common/types/selection_vector
+common/types/validity_mask
+common/types/vector
+common/vector_operations/scalar_executor
+common/vector/unified_vector_format
+execution/expression_executor_state
+execution/ht_entry
diff --git a/.claude/harvest/duckdb-headers/ore/args.txt b/.claude/harvest/duckdb-headers/ore/args.txt
@@ -0,0 +1,14 @@
+-x
+c++
+-std=c++11
+-I/home/user/adaworldapi/duckdb/src/include
+-I/home/user/adaworldapi/duckdb/third_party/fmt/include
+-I/home/user/adaworldapi/duckdb/third_party/re2
+-I/home/user/adaworldapi/duckdb/third_party/fsst
+-I/home/user/adaworldapi/duckdb/third_party/fastpforlib
+-I/home/user/adaworldapi/duckdb/third_party/utf8proc/include
+-I/home/user/adaworldapi/duckdb/third_party/concurrentqueue
+-I/home/user/adaworldapi/duckdb/third_party/pcg
+-I/home/user/adaworldapi/duckdb/third_party/tdigest
+-I/home/user/adaworldapi/duckdb/third_party/mbedtls/include
+-DDUCKDB_BUILD_LIBRARY