Formal project manifest name 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: prepared for the owner’s public-contract decision. The patch in
proposals/fastverk-spec-project-gnm.patch (repository access required)
has not been applied to the external fastverk/spec repository.
Current contradiction
Gnomon’s authored RFC-0001, RFC-0008, and RFC-0017 require the manifest name
project.gnm. The pinned external formal model at
3725bd9f6d2711aa9bb179deea84f51e4424382a defines
projectManifestOf with project.aion, and its AX-034 theorem and kernel
field state that same older name. Ten Gnomon derivation bodies attempted to
derive project.gnm from AX-034 and failed Lean compilation. Those bodies
are now explicit deferred obligations; the current catalog compiles with
--allow-deferred, while the strict proof gate remains red. A name alias
cannot equate two distinct string literals without changing the assertion.
Proposed change and consequence
If Gnomon’s manifest name remains project.gnm, update the pinned formal
model’s ProjectManifest documentation, projectManifestOf definition,
kernel AX-034 field, and AX-034 theorem with the attached patch. This changes
the proposition of formal AX-034 and any consumer that cites its old
project.aion conclusion. It does not itself rename an on-disk manifest,
rewrite persisted data, or change a wire namespace. Update the external
framework commit pin only after its owners accept the patch and its full
tests pass. Any Aion consumer of the old formal AX-034 needs a compatibility
strategy or must stay on the old framework commit.
Local verification
git apply --checkaccepts the patch against the pinned clean framework commit. Its SHA-256 is15b8f84a582c4ca08ebb0ce2c9deffaf9c027fa2f3f9376e1f8a1c4db914267e.- In a disposable directory, the four patched formal sources and two
unmodified formal dependencies compiled with Lean
v4.30.0-rc2. The Gnomon compatibility module compiled, followed by the original generated proof text with only its staged compatibility import. The result was zero Lean compilation errors for 723 theorem entries. - That test used an earlier catalog with 477 deferred entries. The current catalog has 719, including the ten manifest-name obligations, and the separate RFC-0049 structural theorem is accounted for by the inventory gate. The strict normative proof and release gates remain red.
If the owner chooses to keep project.aion as the formal contract, the
Gnomon RFCs and implementation would instead need a reviewed filename
migration or a distinct Gnomon formal model. Do not replace the generated
proof strings with project.aion merely to pass compilation: that would
prove a different manifest contract than the authored RFCs require.
Rollback of an approved upstream change is an upstream revert plus restoring
the prior external commit pin. The original savvifi/* repositories remain
readable throughout this proposal.