gnomonlearn
Docs/RFC-0007 diagnostic collision proposal

RFC-0007 diagnostic collision proposal

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.

Status: proposed first-release correction. Owners: Runtime and Semantic Core. Nothing is deployed, so no diagnostic consumer migration is required.

Conflict

RFC-0007 §7.1 requires M07622 when a query predicate cannot be statically typed. Section 8 also requires M07622 when mode: sync uses a nondeterministic derivation method such as llm or embedding_model. The Lean diagnostic catalog assigns M07622 only to the derivation error, while Lean normative statement b50 and its generated reference assign the same code to the query error. The RDF claim for M07622 describes the derivation case. A client receiving the code cannot identify the failed contract from the code alone.

Recommended first-release split: retain M07622 for the synchronous derivation error, as already defined in the structured diagnostic catalog, and assign M07640 to an untypable query predicate. M07640 is unused in the checked-in RFC corpus. Update the §7.1 prose, Lean normative statement, diagnostic catalog, generated reference, proof-link review, diagnostic occurrence inventory, and compiler tests together. The existing b50 theorem does not prove the diagnostic behavior and should retain its mismatch verdict until a faithful theorem is provided.

The alternative is to keep M07622 for query typing and allocate a new derivation code. That would change the existing catalog entry and RDF claim instead of the uncataloged query use.

Acceptance

  1. Each trigger has one unique code and severity in authored prose, Lean, generated references, and RDF; the diagnostic inventory shows no same-code semantic collision.
  2. The .gnm checker emits the query code for an untypable predicate and the derivation code for mode: sync with llm or embedding_model. Negative fixtures assert the exact code and source location.
  3. Refresh source-bound proof and projection reviews, regenerate artifacts, and verify site links and downstream diagnostic consumers before release.