RFC-0001 module type value identity proposal
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.
Status: owner-approved and implemented as part of the complete RFC-0001 batch.
Owner: spec ontology and module contract. Approved 2026-10-14 in reply
call359cf486. No deployment exists.
The exact reviewed patch, actual RDF delta, and consumer effects are consolidated in the approved thirteen-node batch.
Evidence
Authored RFC-0001 §4 defines three permitted values of the module.type field, not three declaration instances. The ontology defines NamedDeclaration as a specific instance of a declaration kind. Before correction, all three domain nodes used that class. Their text agreement did not establish whole-node agreement. They now use the approved FieldChoice class and source-bound matching reviews.
Approved contract
domain:FieldChoice is a subclass of DomainEntity: a named permitted
symbolic value of a declaration field. domain:choiceForField has
FieldChoice domain and Field range. This records the owner directly without
inventing a new DSL declaration or language data type.
| Former domain path | Approved domain path | Claim references |
|---|---|---|
| declaration/module-manifest/backend-only | value/module.type/backend-only | 1 |
| declaration/module-manifest/hybrid | value/module.type/hybrid | 1 |
| declaration/module-manifest/ui-only | value/module.type/ui-only | 2 |
All paths are relative to https://gnomon.sh/domain/. These three nodes now use
FieldChoice and link to the existing field/module/type node through
choiceForField. FQNs, summaries, RFC-0001 provenance, and all claim identities
and predicates are preserved. Four affected claim references point to the new
value identities. There is no deployed-data migration or asserted equivalence
between a declaration and a value.
Consumers and acceptance
Literal searches across staged gnomon, site, graph, and expression found these IRIs only in gnomon’s inherited RFC-0001 claim and domain Turtle. This is a local consumer inventory, not proof about dynamically constructed queries.
The ontology/context/source changes, regenerated Turtle, resolved references, and source-bound reviews are implemented. The full batch’s actual 38-query effects match the reviewed counterfactual. Existing SHACL live/negative fixtures pass. The broader strict domain-identity gate retains its unchanged inherited 18 FQN and 21 kind-class conflicts.
Framework artifact adoption and publication remain pending; the approval did not authorize those steps.
This proposal changes RDF identity and vocabulary. It does not change the accepted module syntax, values, diagnostic codes, or declaration restrictions.