RFC-0001 module cardinality review evidence
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 maintained implementation record describes the two-summary correction to the existing module cardinality rule. The actual generators compiled 55 structured Lean modules; all twelve invoked generation and integrity commands succeeded. Actual verification proves one domain-summary triple replacement, one reference-sentence replacement, all 57 unchanged emitted Turtle catalogs, unchanged diagnostic definitions, and 138 source-hash review rebindings with one corrected verdict. The ledger retains 2,420 mismatches. Of 38 query result multisets, one governance summary row changes and the other 37, including all sixteen claim queries, are unchanged.
Retained records
source-only.patch: exact maintained source correction.implementation/outcome.{textproto,pb}and twelve sibling.logfiles: actual command arguments, process IDs, statuses, and hashed outputs.implementation/verification.{textproto,pb}: generated delta and repeated 38-query comparison against actual outputs.audit.{textproto,pb}: original counterfactual, including input and query hash bindings and exact changed rows.consumer-scan.{textproto,pb}: five neighboring repository heads and exact tracked-file search results.- Four owning schemas and four corresponding Python sources preserve the original record structure and the code used for the observations.
historical-copy-graph-comparison/: first reader and actual results, retained because copying the RDF store perturbed unrelated LIMIT, SAMPLE, or aggregate query output. The corrected reader compares the same store.original-pending-proposal.md: the proposal before routine implementation was directed under the existing program goal.promotion.{textproto,pb}: exact original-to-copy file mappings, SHA-256 hashes, copied byte extent, and separately identified new documentation.
Provenance and limits
These files are byte-identical copies of observations originally produced in
/Volumes/Workspace/gnomon-sh/.work/rfc0001-module-cardinality-proposal-20261014.
Typed records retain their original absolute paths and hashes. A path in an
observation continues to identify its original input or output; it does not
identify this later copy. Promotion neither rewrites original path fields nor
represents the copied locations as the original execution environment.
Large source preimages, complete RDF inputs, tool/runtime trees, and the whole before-implementation tree are not included. The Python sources are retained for review; this compact record is not a standalone runnable reproduction environment. Source input hashes identify observations at their recorded stage and must not be interpreted as bindings to later edited files.
No Lean compilation or other gate was rerun for promotion. The genuine generation receipt predates the final maintained gap-document update; final committed artifact generation must produce a fresh receipt. This evidence establishes local source/output alignment, not a final clean package, normative release, corrected upstream model, parser conformance, dependency cutover, or public publication.