gnomonlearn
Docs/RFC-0037 read-only write diagnostic

RFC-0037 read-only write diagnostic

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.

RFC-0037 §3.3 and §7 invariant 1 require read-only services to throw M37020 from write(). Its Lean statements repeat that rule, but the same Lean diagnostic catalog assigns M37020 to an unsupported backend operation and M37021 to a write on a read-only service. The RDF claims for the read-only rule and both diagnostics currently preserve the contradiction.

Use M37021 for write() on a service that exists but is read-only. Keep M37020 for an operation on a missing or unsupported service supplied by createGraphBackend. This keeps the distinct diagnostic descriptions useful to callers and makes the catalog authoritative. Revise §3.3, §7 invariant 1, the corresponding Lean statements and evidence, and the RDF claim together. The alternative is to retire M37021 and give both conditions M37020.

Acceptance criteria

  1. The prose, Lean statements, diagnostic catalog, RDF claims, and emitted reference use one code for each condition.
  2. Each backend and the factory stubs emit the selected code for the matching condition; focused tests cover both conditions and client propagation.
  3. No generated output is edited directly; source regeneration and semantic projection gates pass before release.