gnomonlearn
Docs/Claim support RDF range proposal

Claim support RDF range 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 decision requested. Owner: spec/RDF contract. Nothing is deployed, so no persisted RDF migration is required.

Evidence

The claims ontology declares claims:supportsRule with range rfc:NormativeStatement. All six current uses are RFC-0022 claim nodes and target domain:Invariant nodes instead. Those invariants are typed in the domain projection and correspond to the Lean invariant catalog. The emitted RFC normative statements are blank nodes, so there is no stable statement IRI to substitute while preserving this relationship. The checked-in rule-supporting-claims.rq query joins supportsRule targets to normative statement properties and currently returns no rows for these six links.

Claim section/topicCurrent target invariant
§5 compile-time data flowworkflow-static-data-flow
§6 complete error policyworkflow-complete-error-policy
§7 transition event loggingworkflow-event-log-coverage
§8 no capability escalationworkflow-no-capability-escalation
§8 trigger authorizationworkflow-trigger-authorization
§8 workflow variable isolationworkflow-no-cross-instance-variables

Add claims:supportsInvariant with domain claims:Claim and range domain:Invariant. Change only the predicate on these six triples, preserving claim and invariant IRIs. Keep supportsRule reserved for direct links to stable normative statement identities. Update the JSON-LD context and add a domain-supported-claims query that joins the six claims to their invariants. Leave the rule-supporting query explicitly empty until the normative statement catalog emits stable IRIs and the claims are individually mapped to them.

The alternative is to assign stable IRIs to emitted normative statements and map the six claims to them now. That would change the Lean-to-RDF publication contract across the spec, beyond this six-edge correction. Reinterpreting supportsRule to include domain invariants would erase its precise range and make existing normative-statement queries ambiguous.

Acceptance

Update the ontology, context, protobuf claim sources, emitted Turtle, and source-bound reviews together. Add range checks for supportsRule and supportsInvariant. Verify projection drift, all checked-in queries, and query result differences. Check local RDF consumers before release; external consumer review remains a release gate.