vocab: reserve the C-band — 0xC0 JavaRuntime / 0xC1 Analytics / 0xC4 BinaryLifting

[AdaWorldAPI]

Operator ruling, 2026-08-18: "Java is an entire different layer that's why I chose another higher level."

The ruling

The classid domain byte carries altitude, not just identity — a slot's magnitude encodes how high the thing sits in the stack, 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.

slot	domain	why there
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, so the 5+3 gate on actual mints is untouched — reserving is the part that "costs nothing" per APP-CLASS-CODEBOOK-LAYOUT.md §2.

Why altitude earns the space it takes

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. That is §3.5'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.

Fences carried in the variant docs

1. Naming — each domain names the shared concept, never a vendor or renderer. ogar-bricks and a lakehouse consumer are two app prefixes over ONE Analytics vocabulary; Ghidra and r2sleigh are two consumers of the same SLEIGH specs over ONE BinaryLifting vocabulary. (D-BLOCKS-DOMAIN's fence, reapplied.)
2. Provenance, load-bearing for 0xC4 — mints must derive from permissively-licensed or specification sources (Ghidra core is Apache-2.0; its opcodes.hh and the SLEIGH processor specs are usable, the GPL/ subtree is not needed for lifting), never by transcribing a GPL/AGPL or LGPL implementation. That keeps this public codebook unencumbered while a GPL consumer links it freely, and lets the GPL boundary sit entirely in the consumer repo.
3. No speculative widening — 0xC0 is deliberately JavaRuntime rather than a vendor-neutral HostRuntime. No second managed runtime is in scope, and another one would get its own C-band slot rather than dilute this one.

The gap, and the disable-runs that prove the guards

0xC2–0xC3 stay Unassigned by intent, pinned by test exactly as the 0x10–0x16 gap below Blocks is — the slots were chosen deliberately, not consecutively, so a later pass cannot "tidy" a C-band domain downward into the hole.

assertion	disable	observed
the 0xC4 domain resolves	drop the 0xC4 => BinaryLifting arm	red: left: Unassigned, right: BinaryLifting
the C2–C3 gap holds	add a 0xC2 => BinaryLifting arm	red: left: BinaryLifting, right: Unassigned

Also pinned two-sided: 0x0C Automation is not 0xC0 JavaRuntime — they are a digit swap of each other, the one real legibility hazard in this allocation, recorded rather than left to be rediscovered.

Storno — three superseded slot proposals

The session that produced this ruling first proposed, and withdrew: seating P-code at 0x1718 as an ogar-loco consumer slot (wrong tier — 0x17 is lance-graph's internal orchestration: elixir-on-rails shaped, rs-graph-llm as executor, Rig marking the replayability boundary between external LLM and internal low-code — not a container for any palette whose ops happen to fit in a byte); putting P-code at 0x18 beside Blocks (same error, one slot over); and a separate substrate/layout-contract domain (not separate — it is 0xC0's content). Root cause: clustering by shape (everything becomes (function : value) calls in a 512-byte node) where the axis is altitude. Shape-similarity is not domain-identity. What survives: reuse ogar-loco's node shape, own your own domain — borrowing the container is not joining the domain.

Gates

ogar-vocab 157/157 + 6 doctests; full workspace 0 failures; cargo fmt clean; cargo clippy -p ogar-vocab --all-targets clean.

Files

• crates/ogar-vocab/src/lib.rs — three variants + three canonical_concept_domain arms + the altitude principle on the enum's own doc + the pinned C-band/gap/transposition assertions.
• docs/DISCOVERY-MAP.md — D-CBAND-ALTITUDE (append-only, prepended above D-BLOCKS-DOMAIN).
• docs/APP-CLASS-CODEBOOK-LAYOUT.md — §0 band table + the structural note + the legibility hazard.

First named consumer, not built and not blocking: lance-graph-java's W6 schema/classid field on LgjResourceInfo/LgjLaneDesc — a 0xC0 concept, the membrane naming itself from inside its own stratum. Cross-ref that repo's E-LGJ-THE-DOMAIN-BYTE-CARRIES-ALTITUDE-1.

---

Generated by Claude Code

[chatgpt-codex-connector]

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.

[cursor]

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_9b47cb6a-5b6f-41fc-adc1-ba1d1aab5ac9)

[coderabbitai]

Important

Review available on request

• 🔍 Trigger review

Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7ede417d-1869-411f-bee1-a098dfb0d903

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}