Skip to content

vocab: 0xC0 is Panama FFM alone — Valhalla is a property of the concepts, not a concept - #277

Merged
AdaWorldAPI merged 3 commits into
mainfrom
claude/lance-graph-java-panama-valhalla-sus9w8
Aug 18, 2026
Merged

vocab: 0xC0 is Panama FFM alone — Valhalla is a property of the concepts, not a concept#277
AdaWorldAPI merged 3 commits into
mainfrom
claude/lance-graph-java-panama-valhalla-sus9w8

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

Doc-comment-only follow-up to #276. Zero code, zero id moves.

The ruling

Cross-session (lance-graph-java × ruff/R2IL, 2026-08-18): a ConceptDomain is a vocabulary of addressable things. Panama's crossing concepts — downcalls, segments, lanes, arenas, masks — are addressable; Valhalla flatness is a property of a representation. 0xC0's doc comment and the layout-doc band table bundled the two as "Panama + Valhalla" as if both named crossing surfaces; corrected to Panama FFM alone.

The precision that almost got lost — and is now the point of the text

The first draft of this correction read as "Valhalla was just a lab, so it gets no slot." An operator double-check caught that before it calcified, and the verified state is the opposite premise leading to the same conclusion:

Valhalla IS integrated in lance-graph-java, in two real senses. The shipping descriptor vocabulary (LaneId / Ordinal / MaskId / RowRange / FacetId) is designed so the same source compiles as value record under JEP 401 — migration is one word per type, a load-bearing constraint on the production API. And a real Valhalla EA build (27-jep401ea3) ran the A/B with measured results: array-flattening cliff at 8-byte payload; the 4–8-byte descriptors 5.5× smaller / up to 8.3× faster where flattening applies; bulk data stays native, winning 38–57× on both platforms.

Precisely because that integration is a designed property OF the 0xC0 concepts' vocabulary rather than a concept itself, it mints no address. Properties of concepts do not get domains. A genuine Valhalla concept, if one is ever needed, is argued fresh on its own merits — it does not inherit squatting rights in 0xC0.

Files

  • crates/ogar-vocab/src/lib.rsJavaRuntime doc comment corrected (canonical text of the ruling).
  • docs/APP-CLASS-CODEBOOK-LAYOUT.md — §0 band-table row updated to match.
  • docs/DISCOVERY-MAP.md — dated correction appended to D-CBAND-ALTITUDE; the original parenthetical stays, per append-only.

Gates: ogar-vocab 157/157 + 6 doctests, clippy --all-targets clean, fmt clean.


Generated by Claude Code

claude added 3 commits August 18, 2026 03:04
… BinaryLifting

Operator ruling, 2026-08-18: "Java is an entire different layer that's why
I chose another higher level." The classid domain byte carries ALTITUDE, not
just identity -- a slot's magnitude encodes how high the thing sits, so
placement is neither mnemonic nor next-free. 0x00-0x0F is the canonical
business/reference ontology, 0x17 is the substrate's own orchestration tier
(ogar-loco), and 0xC0+ is the C-band: strata ABOVE the Rust substrate,
foreign host layers the substrate reaches into rather than owns.

  0xC0 JavaRuntime    Panama + Valhalla -- the managed-runtime membrane over
                      the SoA substrate, and the FLOOR of the band: the door
                      every other tenant of that layer arrives through.
  0xC1 Analytics      the analyst estate -- addressable tabular units plus
                      the catalog ontology around them.
  0xC4 BinaryLifting  bolted onto 0xC0 (Ghidra is itself a JVM application),
                      so a TENANT of that layer rather than a peer of C0 --
                      and the slot number is the blast radius of turning any
                      binary into addressable rows.

All three are RESERVED-EMPTY -- zero concept rows, the same posture as
Osint / Genetics / Blocks -- so canonical_concept_domain returns a stable
tag before anything mints. No concept was invented; the 5+3 gate on actual
mints is untouched.

Why altitude earns the space: the domain byte is the first two nibbles of
the classid, so its top nibble is a 16-way altitude selector -- one mask
separates "substrate ontology" from "host layer" with no lookup and no value
decode, which is the canon's "the key prerenders nodes with zero value
decode" applied to layering. A first-nibble split is the most expensive
split the 16-ary cascade has; spending it on altitude is what makes it worth
spending.

Three fences carried in the variant docs, two of them reapplied from
D-BLOCKS-DOMAIN: (1) each domain names the shared CONCEPT, never a vendor --
ogar-bricks and a lakehouse consumer are two app prefixes over ONE Analytics
vocabulary, Ghidra and r2sleigh two consumers of the same SLEIGH specs over
ONE BinaryLifting vocabulary; (2) provenance, load-bearing for 0xC4 -- mints
must derive from permissively-licensed or specification sources (Ghidra core
is Apache-2.0), never by transcribing a GPL/AGPL or LGPL implementation, so
this public codebook stays unencumbered while a GPL consumer links it freely;
(3) no speculative widening -- 0xC0 is deliberately JavaRuntime rather than a
vendor-neutral HostRuntime, and another managed runtime would get its own
slot rather than dilute this one.

0xC2-0xC3 stay Unassigned BY INTENT, pinned by test exactly as the 0x10-0x16
gap below Blocks is. Two disable-runs confirm the guards are load-bearing:
dropping the 0xC4 arm turns the BinaryLifting assertions red; minting into
0xC2 turns the gap assertion red. Also pinned two-sided: 0x0C Automation is
not 0xC0 JavaRuntime -- a digit swap of each other, the one real legibility
hazard here, recorded rather than left to be rediscovered.

Gates: ogar-vocab 157/157 + 6 doctests, workspace 0 failures, cargo fmt
clean, clippy -p ogar-vocab --all-targets clean.

Ledger: docs/DISCOVERY-MAP.md D-CBAND-ALTITUDE (append-only, includes the
storno for three superseded slot proposals and their root cause: clustering
by shape where the axis is altitude). Layout doc updated with the band table
and the structural note.
…epts, not a concept

Cross-session ruling (lance-graph-java x ruff/R2IL, 2026-08-18): a
ConceptDomain is a vocabulary of ADDRESSABLE things. Panama's crossing
concepts -- downcalls, segments, lanes, arenas, masks -- are addressable;
Valhalla flatness is a property of a representation. The 0xC0 doc comment
and the layout-doc band table previously bundled the two as "Panama +
Valhalla" as if both named crossing surfaces; corrected.

Stated precisely so the ruling cannot be misread as "Valhalla is
unintegrated" -- a misreading the first draft of this very correction
invited, caught by an operator double-check before it calcified. Valhalla
IS integrated in lance-graph-java, in two real senses: the shipping
descriptor vocabulary (LaneId / Ordinal / MaskId / RowRange / FacetId) is
designed so the same source compiles as `value record` under JEP 401 --
migration is one word per type -- and a real Valhalla EA build
(27-jep401ea3) ran the A/B with measured results (array-flattening cliff
at 8-byte payload; 4-8-byte descriptors 5.5x smaller / up to 8.3x faster
where flattening applies; bulk data stays native, winning 38-57x on both
platforms). Precisely BECAUSE that integration is a designed property OF
the 0xC0 concepts' vocabulary rather than a concept itself, it mints no
address: properties of concepts do not get domains. A genuine Valhalla
concept, if ever needed, is argued fresh -- no squatting rights in 0xC0.

DISCOVERY-MAP gets a dated correction APPENDED to D-CBAND-ALTITUDE (the
original parenthetical stays, per append-only); the canonical text is the
JavaRuntime doc comment in ogar-vocab. Doc-comment-only change: zero code,
zero id moves. Gates: ogar-vocab 157/157 + doctests, clippy clean, fmt
clean.
@AdaWorldAPI
AdaWorldAPI marked this pull request as ready for review August 18, 2026 07:09
@cursor

cursor Bot commented Aug 18, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_519d958e-1364-41df-afcb-f26e2adebdee)

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@AdaWorldAPI
AdaWorldAPI merged commit 386a6fd into main Aug 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants