RFC-0049 claim identity repair 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: proposed, awaiting owner decision. Owners: RDF ontology and Compiler. No normative facts or RDF links changed.
Current inventory
The authored claims contain 28 unresolved subject/object references to 15 internal domain identities. Definitions must come from authored domain nodes; occurrence in a claim does not define an entity. All 128 claims and 68 domain nodes have source-bound reviews in RFC0049_CLAIM_REVIEW.md.
Bounded invariant alias correction
These seven undefined aliases have explicit canonical invariant definitions in RFC-0049. Replace their ten claim references with the following emitted identities, retaining the existing domain definitions and claim IRIs:
| Undefined invariant suffix | Defined invariant suffix | References |
|---|---|---|
| aggregation-exit-boundary | aggregation-closure-exit | 1 |
| mutation-idempotency-required | mutation-idempotency | 1 |
| mutation-template-only | mutation-template-mediated | 3 |
| projection-bitemporal-default | bitemporal-default | 1 |
| projection-empty-stable | empty-stable | 1 |
| projection-pure-expression | projection-purity | 1 |
| source-projection-tenant-isolation | source-projection-tenant-filter | 2 |
Every suffix above uses https://gnomon.sh/domain/invariant/. Correcting a
link does not resolve a conflicting claim: aggregation shape, empty results,
and tenant exceptions remain mismatches until their contracts are repaired.
Regenerate Turtle and refresh only affected source-bound reviews after the
owner approves these exact replacements.
Declaration slots require an ontology decision
Six undefined field identities have fourteen references: projection/auth (4), projection/body (1), projection/materialize (6), query/input (1), mutation/guards (1), and mutation/templates (1). These denote grammar slots on declaration kinds, not fields on a named declaration instance. The current hasField property has domain NamedDeclaration and would infer the wrong class if attached to a DeclarationKind.
Recommend a DeclarationSlot class and hasSlot relation whose domain is DeclarationKind and range is DeclarationSlot. Give slots explicit syntax ownership and requiredness without inventing language DataType identities for projection expressions, input blocks, or template chains. Inventory existing slot projections corpus-wide before adopting this class; a correction confined to these six nodes could leave conflicting conventions elsewhere. Do not reuse fieldType or isRequired unchanged: both currently infer Field.
Remaining identity ownership
Three references to projection-authorization-relative combine §14 result relativity with §4 source policy exclusion. Resolve each use separately: source-policy claims can target source-projection-policy-filter, while result relativity needs its own invariant definition and effective-principal contract. Do not collapse these two semantics into one identity.
The lone teamView reference names an example, whereas its claim describes the whole legacy view-mapping layer. Recommend targeting the projection declaration kind for the generic subset relationship, and representing the example only if examples become explicitly owned catalog entities. This changes the claim’s subject and requires owner approval.
Acceptance after approval
- Apply only the seven bounded alias mappings first; verify ten changed refs.
- Regenerate projection artifacts and check drift, RDF identity consistency, claim-query consumers, and source-bound review currency.
- Confirm unresolved RFC-0049 references decrease from 28 to 18, with eight remaining identities. This is inventory improvement, not release acceptance.
- Keep textual and semantic mismatches open after their links resolve.
- Address the separate slot, authorization, and example ownership proposals before asserting that all claim identities have canonical definitions.
No deployed Gnomon consumer requires a data migration. Exact-IRI query clients still need verification before the first normative artifact is published.
Corpus-wide slot inventory
DECLARATION_SLOT_CANDIDATES.md records 302 Field node occurrences in 50 lexical families whose names also occur as DeclarationKind names. The reproducible inventory includes exact IRIs and RFC owners. This lexical overlap is not proof that each node is a DSL slot: Module, compiled-bundle, and registry-manifest can represent runtime or artifact records. Each candidate needs source-based classification before a corpus-wide rewrite.
No authored domain source currently uses hasField. Therefore the six missing RFC-0049 slots cannot inherit explicit ownership from that relation, and adding it to declaration kinds would introduce a new class inference. The next concrete proposal must identify actual syntax slots, separate runtime/artifact fields, and define class-safe ownership properties before changing RDF facts.
The RFC-0043 field ownership review classifies 31 existing Field nodes as serialized manifest fields, including 19 candidates from the lexical inventory. These must be excluded from a syntax-slot rewrite; operation and nested workflow records are output of lowering, rather than the procedure/query/mutation grammar itself.