gnomonlearn
Docs/RDF source filename review

RDF source filename review

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 authored Gnomon source-file convention is .gnm. A review of the protobuf-backed claim and domain projections found 17 distinct nodes across nine RFCs and ten projection files whose consumer-visible text literals use .gnomon for a source file. These are inherited projection facts, not alternate filenames established by the authored RFCs. Legitimate names such as .gnomon-cache, .gnomonpkg, and .gnomonignore are outside this finding.

Projection sourceAffected nodesIncorrect filenameAuthored filename
RFC-0001 claims4agents.gnomon, project.gnomon, mutations.gnomon, serve.gnomonagents.gnm, project.gnm, mutations.gnm, serve.gnm
RFC-0001 domain1policies.gnomonpolicies.gnm
RFC-0008 domain1project.gnomonproject.gnm
RFC-0012 claims1project.gnomonproject.gnm
RFC-0014 claims1module.gnomonmodule.gnm
RFC-0017 claims2project.gnomonproject.gnm
RFC-0032 claims3module.gnomon, .gnomon-containing subdirectoriesmodule.gnm, .gnm-containing subdirectories
RFC-0033 claims2module.gnomonmodule.gnm
RFC-0040 claims1module.gnomonmodule.gnm
RFC-0044 claims1<object-name>.gnomon<object-name>.gnm

The individual node IRIs, exact protobuf source hashes, and source-bound findings are in kg/projection-reviews.textproto. The 17 literals are now corrected in protobuf sources and regenerated Turtle; their reviews are MATCHES_SOURCES. The authored clauses use the .gnm forms: RFC-0001 §4’s predefined filenames, RFC-0008 §7’s project manifest, RFC-0012 §4’s formatter root, RFC-0014 §7’s lockfile location, RFC-0017 §§4/5’s project index and code action, RFC-0032 §6’s Gazelle manifest handling, RFC-0033 §§6/8’s API declaration, RFC-0040 §2’s module manifest, and RFC-0044 §5.3’s output path.

The corresponding .gnomon filename mentions in RFC-0008, RFC-0014, RFC-0018, and RFC-0019 Lean catalogs and RFC-0018’s authored example comment are corrected. The RFC-0014 reference was regenerated; the other three reference pages were byte-identical after Lean regeneration. The filename scan deliberately excludes cache directories, package extensions, and ignore files.

Local consumer comparison

The current graph combines the 55 regenerated RFC Turtle catalogs, ontology, claim, and domain projections. A baseline snapshot before the edit and a post-regeneration run of all 16 checked-in claim queries each returned 550 rows, with zero changed result sets. Claim/domain RDF graph comparison against the parent commit found exactly 17 removed and 17 added literal triples, with the same subjects and predicates. The source edit changes exactly one claimText or summary literal on each of the 17 reviewed nodes. This measures local queries only; exact literal searches and external queries can still observe the new values.

Correction and remaining acceptance

The protobuf sources, Turtle, affected Lean sources, RFC-0018 example, and RFC-0014 reference are aligned locally. Bazel built the four affected Lean reference and Turtle targets; projection drift, KG links, grounding, corpus links, 724 provenBy review bindings, and all 16 claim queries passed. The other source-bound projection reviews were rebound only after checking that their authored changes were these filename corrections; their verdicts did not change. Next, repin and rebuild the site against this exact spec commit, then inspect representative affected RFC and evidence pages. Destination CI and external RDF literal consumers remain unverified. The normative release gate remains red on independent projection, proof, term, and draft gaps.