gnomonlearn
Docs/Approved RDF owner and scope adoption

Approved RDF owner and scope adoption

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.

The owner approved the thirteen RFC-0016/RFC-0029 claim-subject mappings and, separately, the two RFC-0004 invariant scopes on 2026-10-16. Each reviewed patch was applied once at clean Spec baseline f4d98a8f4bb9a1b6fda15444c14a426db615e5a1. Duplicate approval replies did not cause duplicate application. The immutable proposals remain in the program workspace under spec-rfc0016-rfc0029-existing-owner-decision-v1-20261016 and spec-rfc0004-two-invariant-scope-proposal-v1-20261016.

Actual result

CheckResult
Owning source/Turtle equalityAll three affected projections match
Complete RDF delta13 removed claim-subject triples; 13 replacement subject triples and 2 added invariant scopes
Complete graph89,349 to 89,351 triples
Review ledger6,962 rows; only 15 related hashes/findings change; 11 verdicts corrected; 2,308 mismatches remain
RFC-0029 semantic holdsBatch-support condition, cache invalidation, canonical JSON, and complete reconstruction remain mismatches
All 38 displayed SELECTsIdentical result multisets and columns
Fourteen complete LIMIT-free relationsTwelve unchanged; exclusions 359 to 359 with one subject replacement; orphan claims 967 to 954 with thirteen rows removed
Domain-link inventory998 unresolved links to 469 targets; RFC-0016 retains 4 references, RFC-0029 retains 13
Nonrelease identity inventoryExisting 18 FQN and 21 kind-class conflicts; no class conflicts

verify_adoption.py (repository access required) performs the actual source, review, RDF, range, and complete query comparison. Its typed effects (repository access required) use the retained query result schema (repository access required) and bind 215 exact current input files. Unchanged RDF documents share one blank-node mapping; the three changed projections contain no blank nodes. All 6,947 unrelated review records are exact protobuf matches. The source comparison is bounded to 300 seconds, 240 seconds of CPU, 250,000 rows per relation, and an 8 MiB effect artifact. It does not claim a complete Python runtime audit.

Commands and terminal results

The exact reviewed patches passed joint git apply --check and were applied once. The owning command tools/check_projections.py --write returned zero. The following existing tools then returned zero; each raw log ends with its direct gate return code:

The independent actual comparison returned zero in tool result 5de372 (launch 60fb76, session 56670); its log (repository access required) records the proved scope. Generator result 93afe3 and final gate result 65e840 were also zero. No owner PID, child PID, native build, or release result is invented for these direct Python checks.

All commands use the existing Python 3.14.7 leaf with -S -E -B -P, adding the previously retained spec-site-approved-projections-preview-links-v1b-20261015/python-runtime and Spec tools directories to the import path. The existing sibling tool-bin supplies protoc; no installation or acquisition ran. The comparison can be repeated on the baseline with these approved changes applied, before making its local commit; it requires that exact HEAD and refuses to overwrite an existing effect record.

The existing Site tools/gen_corpus.py also parsed the current source and projections through its normal --repo, --spec-root, and --out interface; the log (repository access required) and generated data (repository access required) preserve that bounded consumer result. This is a parser check, not a Site build or pin adoption.

Remaining gates

Authored prose, Lean sources, proof ledgers, formal catalogs, ontology, query sources, and existing pinned framework/Site artifacts are unchanged. No new identity, class, FQN, grammar rule, diagnostic, enforcement rule, or query column is added. The two scope edges meet the existing DomainEntity range.

The strict identity, semantic/proof, packaging, published dependency graph, framework Java/SHACL/reasoner consumers, Site build, downstream artifact pin, and release gates remain separate. The existing preview pins were preserved; this source adoption does not relabel their prior acceptance or republish an artifact. No external Git push, merge, tag, registry write, deployment, or domain change ran.