Repeated term definition drift
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
The regenerated RFC catalogs fail tools/check_semantic_consistency.py on
11 repeated term names. This is a preexisting corpus conflict: the RFC-0000
and RFC-0049 catalog files are byte-identical to the earlier archived preview.
The checker requires every repeated term name to have one identical definition
string. The direct normative release command now runs this gate and reports
all drifting names in stable order.
An inventory of the current emitted rfc:Term nodes finds 11 names with
multiple definitions: Aspect, Command, Facet, Install plan, Kind, Module,
Presentation facet, Principal, Query, Semantic facet, and View. Several are
shorter and longer descriptions of the same concept. At least three require
substantive review before changing public terms:
| Name | Source RFCs | Review classification |
|---|---|---|
| Aspect | 0000, 0004 | RFC-0004 adds selectors, merge modes, and cross-cutting cardinality. Likely compatible refinement. |
| Command | 0000, 0010 | RFC-0000 aliases an authored action; RFC-0010 defines a runtime state-change request. The declaration and invocation layers need an explicit relationship. |
| Facet | 0000, 0006 | RFC-0000 is a collective term for semantic and presentation facets; RFC-0006 uses it for a reusable meaning module. Likely distinct concepts sharing a name. |
| Install plan | 0000, 0041 | RFC-0000 calls it a state diff; RFC-0041 calls it a build artifact listing modules and order. The artifact’s contents and lifecycle stage need reconciliation. |
| Kind | 0000, 0036 | RFC-0036 narrows the general classifier to a Resource string label with an ltree convention. Likely compatible specialization. |
| Module | 0000, 0040 | RFC-0040 adds versioned graph contribution and identity to the general declaration unit. Likely compatible refinement. |
| Presentation facet | 0000, 0004 | RFC-0004 adds syntax and the explicit no-structure rule. Likely compatible refinement. |
| Principal | 0000, 0048 | RFC-0048 gives the caller identity and enumerates examples of RFC-0000’s operation initiator. Likely compatible refinement. |
| Query | 0000, 0049 | RFC-0000 requires composition of compute declarations; RFC-0049’s query body has a projection expression and lowers to an operation. The authored syntax and compilation relationship need reconciliation. |
| Semantic facet | 0000, 0004 | RFC-0004 adds .gnm declaration syntax and additive composition. Likely compatible refinement. |
| View | 0000, 0003 | Both describe Layer 0 authoring; RFC-0003 adds entity or scope syntax. Likely compatible refinement. |
The classifications are source-reading hypotheses, not approved equivalences. The gate compares exact emitted definitions, so even a compatible refinement needs a canonical shared definition or a distinct qualified term name.
Command: RFC-0000 calls it a synonym for an authorizableaction; another catalog calls it a request to change state that cannot commit state.Install plan: RFC-0000 describes a computed diff; another catalog calls it a build artifact describing modules and installation order.Query: RFC-0000 says it composescomputedeclarations; RFC-0049 says it exposes a parameterized projection. RFC-0049 §11 specifies projection lowering to an operation.
Owner: spec. Review each source RFC and identify whether the repeated name has one shared meaning, a narrower subtype, or two distinct concepts. Then align authored prose, Lean terms, generated reference catalogs, and RDF term identities together. Keep the semantic consistency gate red until all 11 are resolved. Do not weaken the gate to conceal conflicting definitions.
Recommended resolution sequence: use the RFC-0000 glossary as the shared
definition for the seven compatible refinements and retain the RFC-specific
detail in those RFCs’ prose and normative statements. For Command, Facet,
and Install plan, distinguish declaration, runtime request, category, and
artifact concepts before choosing stable names or identities. For Query,
decide whether the RFC-0049 projection syntax is a lowering of RFC-0000’s
compute composition or a successor language form. A name-only RDF repair
before that decision would hide an unresolved implementation contract.
TERM_DEFINITION_PROPOSAL.md gives the recommended decisions, migration
effects, and acceptance checks for owner review.