gnomonlearn
Docs/RFC0014 CARET WARNING PROPOSAL

RFC0014 CARET WARNING 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: owner decision pending. Owners: Compiler, Platform.

Current contradiction

RFC-0014 §5.1 defines ^0.2.0 as >=0.2.0 <0.3.0: MINOR is the breaking component when MAJOR is zero. §8 and the Lean diagnostic catalog describe M01410 as a warning that caret allows MAJOR upgrades on a 0.x module. No MAJOR upgrade satisfies the specified range. Meanwhile §3 permits any pre-1.0 change to be breaking, including a PATCH within that range.

The authored RDF claim RFC-0014/sec-8/m01410-caret-on-zero-warning repeats the contradictory description. Its IRI and diagnostic code can remain stable if the warning is made a stability advisory rather than an impossible range violation. Nothing is deployed.

Keep the authored caret ranges. Emit M01410, with Warning severity, for each import whose constraint uses caret and whose lower-bound MAJOR is zero. Describe it as: “Caret constraint on a pre-1.0 module may admit breaking changes within the allowed range; consider an exact pin.”

This warning does not expand the range, reject a satisfying version, or make the import a compile error. A prerelease is still subject to the separate opt-in rule. Preserve the current MINOR boundary for ^0.0.PATCH too; changing that edge case to a PATCH boundary would require its own range decision.

Alternative: remove M01410 because it offers an advisory rather than detecting a constraint violation. That removes a published diagnostic and requires updating the catalog and consumers.

Concrete changes after approval

  1. Revise §8’s M01410 row and the Lean diagnostic description.
  2. Correct the existing RDF claim’s text and value while retaining its IRI, subject, predicate, code, and Warning severity; regenerate artifacts.
  3. Add a companion QA answer stating the trigger and nonfatal behavior.
  4. Refresh affected source-bound reviews and check projection/reference drift.

Acceptance fixtures

Import constraintM01410Allowed exampleRejected example
^0.2.0Warning0.2.90.3.0, 1.0.0
^0.0.2Warning0.0.90.1.0, 1.0.0
^1.2.0None1.9.02.0.0
~0.2.0None0.2.90.3.0
0.2.0None0.2.00.2.1

Run these through the actual DSL import compiler and resolver when implemented. A catalog edit or independent range helper alone does not prove conformance. The import syntax and lockfile freshness choices remain covered by their existing proposals.