ogar-vocab: take back the 0x03XX double-mint — the Ontology domain is plug-and-play - #290
Merged
Merged
Conversation
… plug-and-play Operator ruling 2026-08-31: "A, den Doppel-Mint zuruecknehmen — was ich meinte ist via plug and play." This supersedes the 2026-08-22 ruling that ddd51f4 acted on ("the domains should be minted in ogar-vocab"): the 14 OBO concepts are reachable through the PRODUCER, not through the shared zero-dep vocabulary. Reversed exactly the ogar-vocab half of ddd51f4 (14 consts, 14 Class constructors, the CODEBOOK and class_ids::ALL rows, the count pins). The ogar-obo half STAYS: Namespace::ALL remains public with its precise scope doc, because that is the plug-and-play enumeration the ruling points at — a consumer that deps ogar-obo gets the OBO concepts, one that does not never pulls them into its concept space. What the mint's three reasons rest on, unchanged: the cross-site collision guard lives in ogar-ro (concept_id_collision_guard, reading ogar-obo's OBO_CORE + META_STUDY_SPINE) and is untouched by this revert — it is the side that can see both tables, which is why it was put there; and Namespace::ALL is what stops a consumer computing ids arithmetically. Consequence downstream: lance-graph's contract ogar_codebook mirror carries no 0x03XX rows, which is now correct again, and its "ZERO vocabulary rows BY DESIGN" posture is true rather than four days stale — the lance-graph-ogar codebook-parity job goes green with no lance-graph change. ogar-vocab 164, ogar-obo 48, ogar-ro 10; clippy 0, fmt clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PFnYKqw6d7TTiB9cT8eFdK
AdaWorldAPI
pushed a commit
that referenced
this pull request
Aug 31, 2026
…quired Follow-up to the double-mint revert (PR #290): ogar-class-view imported the 14 removed ogar-vocab constructors and registered them, because a CODEBOOK promotion without a registry entry is what every_codebook_id_appears_in_ class_ids_all catches. With the mint taken back there is nothing to register — the gate is satisfied again by both sides being empty. Found by the downstream gate, not by review: reverting only the ogar-vocab half left this crate importing names that no longer exist, and the OGAR workspace build is where that surfaced. The comment block is replaced rather than deleted: it now states the plug-and-play posture and records that the brief 2026-08-22 mint is what put rows here. OGAR workspace green (ogar-class-view 12, ogar-vocab 165, ogar-obo 48, ogar-ro 10, and the rest); clippy 0, fmt clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PFnYKqw6d7TTiB9cT8eFdK
This was referenced Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Operator ruling 2026-08-31: "A, den Doppel-Mint zurücknehmen — was ich meinte ist via plug and play." This supersedes the 2026-08-22 ruling that
ddd51f4acted on ("the domains should be minted in ogar-vocab"): the 14 OBO concepts are reachable through the producer, not through the shared zero-dep vocabulary.What is reversed, and what deliberately is not
Reversed: exactly the
ogar-vocabhalf ofddd51f4— 14 consts, 14Classconstructors, theCODEBOOKandclass_ids::ALLrows, the count pins.Kept: the
ogar-obohalf.Namespace::ALLstays public with its precise scope doc, because that is the plug-and-play enumeration the ruling points at — a consumer that depsogar-obogets the OBO concepts; one that does not never pulls them into its concept space.The mint's three reasons, and where they rest now
META_STUDY_SPINEonce minted over0x0306with nothing failing): the guard lives inogar-ro(concept_id_collision_guard, readingogar-obo'sOBO_CORE+META_STUDY_SPINE) and is untouched here — it is the side that can see both tables, which is why it was put there.0x0300 | (ns + 1)):Namespace::ALLis what stops that, and it stays.concepts_in_domain(Ontology)answering empty: under plug-and-play that is the correct, documented reading — a reserved domain that carries no shared rows.Downstream
lance-graph's contractogar_codebookmirror carries no0x03XXrows, which is correct again, and its "ZERO vocabulary rows BY DESIGN" posture becomes true rather than four days stale. Thelance-graph-ogarcodebook-parity CI job goes green with no lance-graph change — that job has been red on lance-graph main since 2026-08-22, when the mint landed and its paired mirror half never did.Gates
ogar-vocab164,ogar-obo48,ogar-ro10; clippy 0 findings, fmt clean.🤖 Generated with Claude Code
https://claude.ai/code/session_01PFnYKqw6d7TTiB9cT8eFdK
Generated by Claude Code