gnomonlearn
Docs/RFC-0002 RDF relationship proposal

RFC-0002 RDF relationship 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. Owner: specification, compiler, and runtime maintainers. The protobuf projection sources and generated Turtle remain unchanged. This proposal covers eight source-bound claim relationship mismatches in RFC-0002 §§7–10; the other claim and domain mismatches are tracked in PROJECTION_GAPS.md and BUNDLE_CONTRACT_PROPOSAL.md.

Candidate mapping

Keep each claim IRI, claim text, claim kind, confidence, and section link. Replace only the structured relationship fields shown below. The new domain identities are candidate domain#DataType nodes, except StorageDDLGeneration, which is a candidate domain#Operation. Each needs definedIn: RFC-0002, a stable FQN, and a reviewed definition before publication.

Claim slugCurrent subjectCandidate subjectOther change
sec-7/bitemporal-write-prohibitioninvariant/runtime-only-bitemporal-writestype/StorageBitemporalColumnsPredicate must-not-be-written-by → must-not-be-written-directly-by; object declaration/compiled-bundle → type/ApplicationCode. The authored §7.3 condition is direct writes outside the Gnomon API.
sec-8/authz-artifacts-inspectabledeclaration/policy-envelopetype/AuthorizationPropagationArtifactNo other change. Policy envelopes are narrower than the authored artifact set.
sec-8/no-silent-policy-dropdeclaration/policy-envelopetype/BundleCompilerNo other change. The compiler performs the prohibited action.
sec-9/backcompat-time-boundedtype/BundleFormatVersiontype/BundleCompatibilityModeNo other change. The mode, rather than the version number, is time-bounded.
sec-9/readers-reject-incompatible-majortype/BundleFormatVersiontype/BundleReaderPredicate rejected-when → must-reject. The reader rejects an incompatible major version.
sec-10/ddl-included-in-repro-reportingdeclaration/storage-manifestoperation/StorageDDLGenerationNo other change. §10 requires reporting on DDL generation, rather than the manifest declaration.
sec-10/repro-reporting-includes-categoriesdeclaration/compiled-bundletype/ReproducibilityReportNo other change. The report contains the success rate and categorized counts.
sec-10/repro-target-quality-gatedeclaration/compiled-bundletype/ReleaseReadinessAssessmentNo other change. The 70 percent baseline applies to release-readiness discussion.

The candidate bitemporal type groups two fields under one subject, preserving the current one-subject-per-claim pattern. The new ApplicationCode object names the prohibited writer. The specific ontology class and FQN for each new node need approval with the bundle schema; an IRI cannot be reused later for a different meaning.

Measured local query impact

An in-memory counterfactual loaded the current ontology, generated RFC and formal catalogs, and all claim/domain Turtle files. It changed eight subject triples, two predicate literals, and one object triple, then added three minimal domain facts (rdf:type, fqn, definedIn) for each of the nine candidate identities. The graph had 89,116 triples after those edits. All 16 checked-in claim queries executed. Thirteen distinct result sets were unchanged; three changed as follows:

QueryRemoved resultAdded result
enforcement-claims.rqUnbound subject FQN, rejected-when, incompatible major versionBundleReader, must-reject, incompatible major version
exclusions.rqUnbound subject FQN for compiler policy dropBundleCompiler for compiler policy drop
exclusions.rqUnbound subject FQN, must-not-be-written-by, compiled-bundleStorageBitemporalColumns, must-not-be-written-directly-by, ApplicationCode
orphan-claims.rqRFC-0002 §10 DDL reporting claim on storage-manifestRFC-0002 §3 explicit format-version claim on BundleFormatVersion

The orphan-claims.rq change is a 50-row page displacement under its ordering and limit, not proof that either claim was added to or removed from the graph. This counterfactual checks local query results only. It does not validate the new domain definitions, external RDF queries, cached results, or persisted graphs.

Acceptance and migration

  1. Approve the actor and target identities with RFC-0002’s versioned bundle contract. Verify the nine names do not collide with published RDF identities or represent an existing generic actor or artifact more accurately.
  2. Define the nine domain nodes and eight claim edits in protobuf source, regenerate Turtle, and refresh source-bound review hashes and findings. Preserve claim IRIs and section links. Specify the direct/outside-API bitemporal condition in structured fields rather than text alone.
  3. Run projection drift, graph-link, SHACL, and all 16 claim-query gates. Compare row-level query changes against this counterfactual and inspect limited queries for displaced rows.
  4. Inventory external RDF consumers and stored graphs before publishing the new triples. Ship a versioned graph and rollback path; update the pinned site and framework duplicate only after the released artifact is verified.