gnomonlearn
Docs/Proof citation publication policy

Proof citation publication policy

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.

Owner: Gnomon spec and formal framework. Status: proposed; no RDF or Lean RFC source fields changed by this document.

Observed contract

  • The 722 live provenBy citations in Lean RFC sources and emitted RDF link normative statements to authored theorem names. The 55 generated reference catalogs label these as proof citations; verification pending.
  • Source-bound review currently finds eight formal theorem-to-claim matches, 714 mismatches, and no unreviewed links. See PROVEN_BY_GAPS.md for the gate and examples.
  • The provenby_sync_test and proof metrics in the original framework inspect these links. The spec emitter and site consume the source and generated citations. A local source search found no direct provenBy consumer in the extracted expression, graph, brand, or site repositories; external RDF, persisted data, and unpublished consumers remain unaudited.

Reserve provenBy for a theorem whose proposition has a source-bound MATCHES_CLAIM review and whose Lean build passes at a pinned framework revision. Preserve proposed or mismatched theorem names in a separate candidate/provenance field and typed review ledger. Public RDF and reference catalogs should distinguish candidate, mismatch, and reviewed formal match. Even a formal match must state its external axioms and must not be presented as runtime implementation evidence.

The immediate migration would withdraw the 714 reviewed mismatched provenBy triples and retain their theorem names in the review ledger. The two external-ID links stay pending the identity-scope decision and would migrate to candidate status before any normative publication. The eight source-reviewed formal matches could keep provenBy only after the emitted RDF and docs identify their assumptions. This is a change to published RDF triples and proof-coverage metrics, so existing consumers need a compatibility review before publication.

Implementation and acceptance

  1. Resolve ownership of the external Spec.Corpus.Schema field and its redistribution terms. Choose a candidate/provenance representation in the canonical Lean and RDF schemas; keep RFC and theorem identities stable.
  2. Add a migration registry for withdrawn links, including RFC statement ID, historical theorem name, source hashes, review verdict, and replacement status. Do not lose the 714 mismatch findings when a citation is removed.
  3. Update Lean RFC source, RDF emitters, reference emitters, metrics, and sync gates together. Regenerate all affected artifacts from source; do not edit Turtle or Markdown by hand. CI must fail when an unreviewed or mismatched candidate is emitted as provenBy.
  4. Audit external and persisted RDF consumers. Verify that source and emitted statement identities survive, and that old queries either tolerate missing provenBy triples or have a documented compatibility route.
  5. Run the Lean corpus, derivation inventory, semantic-review, RDF drift, site-build, and cross-repo consumer gates before changing publication status. Keep the normative release gate red until remaining obligations are resolved.

The alternative is to retain provenBy as a historical citation and publish an explicit review-status property for every link. That preserves triples but requires consumers to interpret provenBy together with status, and leaves the property name easy to misread. This alternative also needs an external consumer audit and drift-gated source generation.