Skip to content

feat: machine-readable namespace registry generator (single source for CIRISPersist#425) - #31

Merged
emooreatx merged 1 commit into
mainfrom
feat-namespace-registry-generator
Jul 11, 2026
Merged

feat: machine-readable namespace registry generator (single source for CIRISPersist#425)#31
emooreatx merged 1 commit into
mainfrom
feat-namespace-registry-generator

Conversation

@emooreatx

Copy link
Copy Markdown
Contributor

Adds tools/build_cc_namespace.py + manifests/namespace_registry.json — the deterministic, machine-readable enumeration of the CC 3.1 dimension namespace that CIRISPersist#425 vendors (generate-from-CC, so persist/edge never transcribe CC prose). Surfaced the stale 83/8 summary (#30 — actual is 95/9). Wiring the generator into CI would keep the summary honest.

🤖 Generated with Claude Code

…amespace.py)

Deterministic extraction of the CC 3.1 dimension-namespace catalog from
part_3_the_namespace.md into manifests/namespace_registry.json — every distinct
backtick prefix family at leaf granularity (the granularity a consuming crate
matches a concrete `dimension` against), with owning_component, polarity, and
the CC 3.4 reserved-emit rule per family. Single source of truth: downstream
crates (CIRISPersist#425) vendor this rather than transcribing CC prose.

Surfaced that the CC 3.1 / 3.1.7 "83 families / 8 components" summary is stale —
actual enumeration is 95 / 9 (see #30). stdlib only, HERE-relative, deterministic
(byte-identical on rerun); _meta carries cc_version + source_sha256 + the
discrepancy note.

Refs #30.
@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.

@emooreatx
emooreatx merged commit 5818a75 into main Jul 11, 2026
1 check passed
@emooreatx
emooreatx deleted the feat-namespace-registry-generator branch July 11, 2026 19:48
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.

1 participant