gnomonlearn
Docs/RDF projection consumer impact

RDF projection consumer impact

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.

On 2026-10-03, the owner-approved RFC-0017 project-manifest correction moved four domain triples to https://gnomon.sh/domain/declaration/file/project.gnm while leaving RFC-0008’s declaration-kind IRI unchanged. A counterfactual full-graph comparison found no changed result list in the 16 checked-in claim queries (550 rows before and after). The corrected generated graph passes all 16 queries and the RDF-link gate. Static search found no executable use of the old exact IRI in the extracted non-spec repositories; the framework’s duplicate Turtle still contains it and awaits artifact cutover. External exact-IRI consumers have not been verified. The new node remains a semantic review mismatch because its NamedDeclaration class describes a manifest file.

The RFC-0017 §3–§4 review corrected two claimText literals to retain the authored rule-compiler availability and project initialization conditions. The claim IRIs and all other triples stay stable. Comparing all 16 checked-in claim-query result lists before and after the two-literal change found no changed list (550 rows each). External literal readers remain unverified; the seven documented RFC-0017 projection mismatches are still open.

Audited against the six extracted local repositories on 2026-10-01. The old framework copy at gnomon/spec/kg/turtle-claims/ and this spec repository each contain 55 claim files. Before the RFC-0035 ClaimStatus reconciliation, their RDF graphs had 33,558 triples on both sides; the new graph removed 32 triples and added 32. Those changes were the 31 reviewed derivedFromSection links and one approved rdf:type :Identity to rdf:type :Claim correction. The 55 domain files were then graph-equivalent (11,626 combined triples). The comparison used the same 55 regenerated RFC Turtle catalogs for both claim graphs. The later owner-approved ClaimStatus change removes four RFC-0035 domain triples and replaces three RFC-0035 claim triples; see CLAIM_STATUS_MIGRATION.md. The query result review below measures only the earlier 32-triple correction; the current 16-query suite still executes with 4,194 typed claims. Comparing all 16 query result sets immediately before and after the ClaimStatus projection edit found no changed rows; this does not test external queries or persisted results. RFC-0003’s later status spelling correction replaces one claim value literal and one domain summary literal without changing their subject IRIs. The 16-query suite passes on the corrected graph, but external consumers of those literal values have not been checked. Four RFC-0006 claim links also now target the emitted core.ClaimStatus declaration rather than two absent domain IRIs. Comparing all 16 local query result sets before and after that change found one changed row in type-assignments: Claim.status now resolves to core.ClaimStatus where the previous query returned an unbound FQN. The other 15 sets were unchanged. Two RFC-0020 gnomon.subscribe claim subjects now target its emitted named declaration rather than a non-emitted operation IRI. Comparing all 16 local query result sets before and after that substitution found no changed rows. External RDF consumers may still observe the two changed object IRIs. Seven RFC-0020 SubscriptionHandle method claim subjects now target emitted method field nodes. A comparison against the preceding spec commit found one changed local query: lifecycle-transitions.rq gained the pause, resume, and close transition rows and lost three RFC-0035 rows at its 40-row limit. The other 15 query result sets were unchanged. The three displaced rows remain in the graph; the query’s ordering and limit explain their absence from this result page. External RDF consumers may observe all seven changed link IRIs.

Two RFC-0002 reproducibility-category claims now link to emitted §11 rather than §6, where the authored RFC contains no such list. The claim IRIs and values are stable; only two derivedFromSection objects changed. An in-memory comparison of all 16 checked-in claim queries against the 88,249-triple local RFC/claim/domain graph found no changed result sets. This does not verify external queries, caches, or persisted RDF. The reviewed section-link map now contains 33 mappings in total.

The proposed correction of eight other RFC-0002 structured claim relationships has not been applied. A local in-memory counterfactual adds nine candidate domain identities and changes three of the 16 checked-in query result sets; thirteen are unchanged. The exact replacements, changed rows, and external-consumer limits are in RFC0002_RDF_MODEL_PROPOSAL.md.

ConsumerObserved behavior and migration effectAcceptance before cutover
site/tools/gen_corpus.pyCounts distinct subjects typed :Claim by parsing the RDF graph for the public corpus index. The inherited files count 4,193; the corrected spec files count 4,194. A fixture with an unrelated :Identity node and a comment containing a :Claim counted only the real claim. The current site build stages the pinned spec and reports 4,194.Keep the site pinned to a released spec artifact and check the staged count and representative RFC pages in destination CI.
spec/kg/queries/claims/*.rqQueries such as section-claim-summary, claim-density, claims-about-entity, cross-rfc-claims, and orphan-claims join derivedFromSection to an emitted RFC section. The old graph resolves 4,163 of 4,194 links; the new graph resolves all 4,194. RFC-0010 rises from 74 to 97 resolvable links, RFC-0015 from 60 to 62, and RFC-0036 from 72 to 78. The local result comparison is recorded below.Re-run the checked-in query suite against the released spec catalog and preserve the new section IRIs in public query results.
spec/kg/lint/semantic/claim-contradiction.rqSelects nodes typed :Claim; the corrected RFC-0006 node becomes eligible for this class of query. No contradiction edge was observed on that node in the current graph.Re-run semantic lint on the emitted graph and review any changed findings.
gnomon/spec/kg/java/SmokeTest.java and WriterTest.javaLoad the framework’s still-checked-in duplicate Turtle tree, so they currently exercise the old 31 section links, old class triple, and withdrawn ClaimStatus variant.Move these tests and their Bazel inputs to a released, pinned spec artifact; compare results with the current spec graph before deleting the duplicate.
gnomon/devdocs/tools/gen_corpus.pyCounts claims from the framework’s duplicate spec tree and still sees the old typed count. The new public site has its own generator using the pinned spec.Retire the old devdocs consumer only after its deployment and route owners use the new site artifact.

Static search found no claim Turtle or claim ontology loads in the extracted expression or brand repositories. The extracted graph repository cites the claim projection as an architectural precedent, not as a runtime input. The owner confirmed that nothing is deployed, so there are no live RDF clients, stored query results, or deployed endpoints to migrate. This local search does not establish that the framework’s duplicate corpus has been cut over or that destination CI and public query results have been verified. Owner: spec for the projection and query behavior, gnomon for its duplicate tree and tests, and site for its public count. Verify those local consumers against the published, pinned artifact before normative release. Reassess external consumers if any are introduced before publication.

RFC-0010’s compiler-index correction changes eleven rdf:type triples to domain:CompilerIndex and removes the KnowledgeIndex kindClass "Meta" triple. Removing eleven unsupported effectIsMutating flags lowers the RFC-0010 domain graph from 339 to 327 triples. The local 16-query claim suite does not select these properties and still passes. Static searches in the extracted repositories found no code query for effectIsMutating or CompilerIndex; external RDF clients and stored results remain unverified. Consumers that group indexes under NamedDeclaration or DeclarationKind, or filter RFC-0010 effects on effectIsMutating, need to use the corrected class or derive the desired effect behavior from a separately specified rule.

The RFC-0010 persistence-adapter correction changes one claim subject and one domain invariant target from the containing runtime module to a named runtime component. The new component has a componentOf link to that module. An in-memory before/after comparison of all sixteen checked-in claim queries found no changed result sets; several queries limit output, and external queries or caches can still observe the new relationships. The claim and invariant subject IRIs themselves are unchanged.

RFC-0011’s three annotation diagnostic claim objects now point to the existing M11800–M11802 identities rather than RFC-0008’s M08780–M08782. Their claim IRIs are unchanged; three object triples and three text literals changed. An in-memory comparison of all sixteen checked-in claim queries against the same current RFC catalog, swapping only the old and new RFC-0011 claim projection, found no changed result sets. External queries joining claimObject to diagnostics, caches, or materialized results may change. No extracted compiler or UI source references these annotation M118 codes yet, so this is source contract alignment rather than verified runtime diagnostic behavior.

The subsequent RFC-0011 identity correction adds annotation-system and AnnotationMap domain nodes and a SyntaxForm ontology class. Existing annotations-block and decorator IRIs remain stable, but their class and kindClass facts change; eight claim properties change targets or wording. The RFC-0011 domain graph gains six triples overall. An in-memory comparison of all sixteen checked-in claim queries before and after this change found no changed result sets. External class-based grouping, relationship queries, and cached RDF may observe the changed triples; no deployed consumers are known.

The later RFC-0011 correction adds a GnomonParser domain node and changes the parser-skip claim subject to that node. The facet/aspect comparison claim now names the annotation system and records the pull/push pair as a value instead of pointing at the RFC-0008 document. The domain projection gains five triples. All sixteen checked-in claim queries returned identical result sets in an in-memory before/after comparison; external clients querying those specific relationships may change. The authored parser and bundle contracts remain under review in RFC0011_ANNOTATION_CONTRACT_PROPOSAL.md.

Local query result review

The approved RFC-0011 older-parser rule replaces the unreleased parser-skip-unknown claim IRI with parser-reject-unsupported, and the inline-body claim moves from inline-block-universal to inline-block-eligible-bodies. Source-bound reviews and generated Turtle were updated together. A static search found no executable reference to either old IRI in the other extracted repositories outside the duplicate framework spec tree. Comparing all 16 checked-in claim-query result lists before and after swapping the two changed RFC claim projections found no changed lists. Exact- IRI external RDF consumers remain unverified; nothing is deployed to migrate.

The subsequent eleven-body grammar integration keeps the inline-block-eligible-bodies claim IRI and updates its text and value to name the RFC-0008 §6.0 scope. Regenerated RDF changes only that claim’s two literals. An in-memory before/after comparison found no changed result lists among the 16 checked-in claim queries. Exact-text and external RDF consumers remain unverified.

python3 tools/check_claim_queries.py --turtle-dir generated/turtle executed all 16 checked-in claim queries against the regenerated catalog and 4,194 typed claims. A second run used the same ontology, regenerated RFC catalogs, and domain projection with the old framework claim Turtle versus the corrected spec claim Turtle. Comparing distinct result rows found one changed query: reservation-claims.rq gained two rows and lost none. The rows are the minted-by → gnomon-kernel reservation in RFC-0010 (its optional subject FQN is unbound) and Resource / direct-write-reserved-for / db.graph in RFC-0036. Both previously disappeared at the section join because their old target IRIs were absent. The other 15 query result sets were identical; several queries are limited or aggregated, so this result does not imply the repaired links have no effect on other query forms or downstream materializations. This is a local query review, not confirmation from external RDF consumers.

RFC-0054 DDL pipeline class correction (2026-10-05)

The owner-approved class map moves 25 RFC-0054 identities to artifact, storage, plan-operation, pipeline-operation, pipeline-value, and risk-value paths. Shared bootstrap.sql, InstallPlan, and InstallPlanEntry identities and their claim links were updated in RFC-0000, RFC-0005, and RFC-0051 as well. Twelve stale kindClass and effectIsMutating assertions were removed because their ontology domains would infer the superseded declaration and effect classes.

An in-memory comparison uses the same current Lean-generated RFC catalogs with the pre-correction projections at 06ba4cbb4 and the corrected source projections. The graphs contain 89,289 and 89,301 triples. All sixteen checked-in claim-query result multisets are identical, with 550 rows on each side. This establishes local query behavior for the checked-in catalog; queries selecting the changed classes or exact IRIs can still observe the correction.

The site stages the canonical spec. An exact-IRI scan found the former identities only in the framework’s duplicate Turtle copies among the other local destination repositories. The spec preview at 55ab96c9a passed the framework’s artifact-fed Loader, Writer, structural-query, SHACL, and reasoner rehearsal before removal of the twelve stale assertions; default framework Bazel inputs and remote publication remain pending. No deployed RDF consumers exist to migrate.

RFC-0001 approved identity and query batch (2026-10-14)

The owner approved the exact thirteen-node batch and its two public query changes in reply call359cf486. Actual regeneration removes 28 triples and adds 71, matching the reviewed 89,301→89,344 triple counterfactual. All 38 actual query deltas match the reviewed results exactly: six query result multisets change and 32 remain identical.

The visible result contract changes from subjectFqn to subject in exclusions.rq, using the existing FQN or exact IRI. The orphan query now recognizes declared domain entities without requiring them to be DSL symbols. Three module-type values acquire the approved FieldChoice identities and four claim references move with them; five precise scope nodes support the corrected subjects. No claim IRI or authored language/diagnostic rule changes.

Source/review/projection and emitted-link gates pass; RFC-0001 has no unresolved claim-to-domain references. Existing Jena SHACL fixtures accept the canonical graph and reject a malformed document. The whole-corpus identity gate remains red on the same 18 FQN and 21 kind-class conflicts as the exact source baseline. Proof and normative-release gaps remain separate.

The implemented batch links actual typed evidence and consumer consequences. The framework duplicate, site pin, released artifact consumers, and publication were not changed. No deployment exists to migrate; future consumers must use the approved identities and output column.

RFC-0003 authored-clause literal alignment (2026-10-14)

The existing sensitive-field-warning claim text now includes the authored by an active policy condition. The widget-stable-identity claim value now states stable identity id; its unchanged text retains the separate typed prop references requirement. These are two RDF literal replacements with stable claim, subject, predicate, kind, and section identities.

The actual full-graph comparison proves exactly two triples removed and two added. All 38 checked-in query result multisets and columns are unchanged. Exact-text consumers can observe both corrected values. No publication, site pin, duplicate-source cutover, or deployment change is implied.

The local implementation record retains the commands, failures, and final typed verification. The widget review now matches its sources; the Sensitive-field whole-node review remains mismatched because its existing View/show subject lacks an authored domain owner. All 42 existing RFC-0003 unresolved references remain visible, and the strict release and formal proof gaps remain open.