RFC-0040 template import 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-0040 §4.2 and §12 invariant 6 use M40021 when a template-call
references a template absent from the module’s templates: imports. Section
13.3 instead says templates declared but never imported produce M40021. The
Lean catalog and RDF claim inherited the second statement. These are
different cases: an undeclared call is invalid; an unused import is not a
missing dependency.
For the first release, keep M40021 for a call to a template missing from
templates:. Remove the unused-import M40021 rule from §13.3 and Lean, and
revise the RDF claim to describe the actual access-control check. A separate
unused-import lint can be introduced later with its own code if desired.
No deployed system or migration needs consideration.
Acceptance: compile fixtures must cover a declared call, an undeclared call, and an unused import. The undeclared call alone emits M40021. Narrative, Lean, claim projection, reference catalog, and generated Turtle must agree.