board: V1 contiguous-u24 GUID tail forbidden — V3 4+12 facet mandatory (migration marked)

[AdaWorldAPI]

What

Marks the flat V1 GUID key-tail (family(u24) ++ identity(u24)) as forbidden for new units and records the V1→V3 migration of the two live residues as MANDATORY (deferred in timing, not obligation). Docs/board only — no code churn this PR.

Why

The tail bytes 10..16 of the 16-byte NodeGuid have three historical shapes:

• V1 (FORBIDDEN for new): family(u24) ++ identity(u24) — two contiguous flat integer fields, no axis. NodeGuid::new / family() / identity().
• V2: leaf·family·identity — three flat u16s (deprecated integer read).
• V3 (REQUIRED for new): the content-blind 4+12 facet — classid(4) + 12-byte payload. The 12B is a dumb byte register the ClassView projects, holding every sanctioned reading at once: 6×(u8:u8) rails / 4×(u8:u8:u8) SPO / 3×(u8:u8:u8:u8) odoo quads (6·2 = 4·3 = 3·4 = 12). u8:u8 = two separate bytes, never widened to u16/u24.

A flat u24 has no axis — it cannot carry a rail (X:Y) — so it is a structurally retired shape, not a width variant. Operator-locked E-V3-FACET-4-PLUS-12 (2026-07-02) + this session's ruling.

Conformance sweep (3 read-only repo audits)

• ruff: already V3 (ruff_spo_address::Facet = classid(4) + 6×(is_a:part_of)). No V1. No-op.
• OGAR: code already V3; only docs pinned/defended V1 → superseded in the OGAR canon PR (CLAUDE.md P0 regraded, NODEGUID-CANON-AUDIT F-3 inverted, DISCOVERY-MAP D-V1-TAIL-RETIRED).
• lance-graph: exactly two live V1 producers — contract/src/ocr.rs:121 (Integrated cognitive planner reference map + ValueSchema presets + FULL POC default #496 OCR keystone) + contract/src/aiwar.rs:104 — both hardcode NodeGuid::new instead of mint_for. Behaviorally fine today (V1-default classids); MANDATORY to migrate when their output paths move onto a V3-marked classid.

Changes (all append-only / regrade-in-place)

• .claude/board/EPIPHANIES.md — E-V1-TAIL-FORBIDDEN-V3-IS-CONTENT-BLIND-1 (RULING).
• .claude/board/ISSUES.md — ISS-V1-TAIL-RESIDUE (OPEN — MIGRATION MANDATORY), names the two mint sites.
• CLAUDE.md — CANON block gets an append-only ⊘ supersession note marking the u24 tail V1-LEGACY/read-only, pointing to the V3 4+12 facet. The pin is not deleted.

Reads of the u24 tail on existing V1 rows survive unchanged (I-LEGACY-API-FEATURE-GATED); only new mints are forbidden.

🤖 Generated with Claude Code

---

Generated by Claude Code

Summary by CodeRabbit

• Documentation
  • Updated project guidance to clarify the supported tail format for new units and mark the older layout as legacy-only.
  • Added migration notes for existing entries, including required routing for new minting and read behavior.
  • Recorded a new issue-log entry tracking remaining legacy usage and the needed migration guardrails.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15dfb2a3-3342-4a2b-9313-1b757ce2b877

📥 Commits

Reviewing files that changed from the base of the PR and between 7384bc3 and ef6dd16.

📒 Files selected for processing (3)

• .claude/board/EPIPHANIES.md
• .claude/board/ISSUES.md
• CLAUDE.md

---

📝 Walkthrough

Walkthrough

This PR updates project documentation across three markdown files to formally forbid the legacy V1 flat family(u24)+identity(u24) tail for new units, mandate the V3 content-blind classid+payload facet, log a tracked migration issue for two existing mint sites, and update canonical layout comments accordingly.

Changes

Tail-Variant Spec Ruling Documentation

Layer / File(s)	Summary
EPIPHANIES ruling: V1 forbidden, V3 defined .claude/board/EPIPHANIES.md	Documents forbidding the V1 flat tail for new units, defines V3's byte-register semantics, reports a conformance sweep, and lists mandatory follow-ups with cross-references.
DeepNSM convergence finding .claude/board/EPIPHANIES.md	Adds a finding clarifying DeepNSM is an encoder filling V3 tenants rather than a migration onto V3.
Issues log: NodeGuid migration tracking .claude/board/ISSUES.md	Logs a mandatory issue requiring two existing NodeGuid::new mint sites to migrate to mint_for/tail_variant dispatch, plus a grep guard and a feature-gating blocker note.
CLAUDE.md canon layout supersession CLAUDE.md	Adds a SUPERSEDED migration-mandatory directive and revises the key-tail layout comment to distinguish the retired V1 tail from the new V3 content-blind facet.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• AdaWorldAPI/lance-graph#613: Introduces the tail_variant axis and V3 classid wiring that this PR's migration mandate routes new mints through.
• AdaWorldAPI/lance-graph#618: Adds V3 classid/read-mode constants needed to migrate the V1 mint sites flagged in this PR.

Poem

A rabbit scribes with careful paws,
"Forbid the tail with u24 flaws!"
V3 now holds the content-blind crown,
Twelve dumb bytes, rails handed down.
Two old mint sites await their turn,
The board records what we must learn. 🐇📜

---

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.}