saymrwulf/dalek-ed25519-verified
1
0
Fork 0
mirror of https://github.com/saymrwulf/dalek-ed25519-verified.git synced 2026-09-03 20:13:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

TRUSTED-BASE: record the kernel-side axiom gate and its residue

Browse source 
Adds one item naming what check.sh Phase 2b binds — every compiled
Proofs/*.olean, kernel-side, membership self-derived, fail-closed on a
missing module — and, more importantly, what it still does not bind:
declarations, not statements. A theorem gutted to a tautology with the same
axiom cone passes every phase. Reading the statements remains a human act,
and this document is where that has to be said rather than left for a
reviewer to discover.

Verified green at this commit's parent across all eight buttons on
2026-07-28; see formal-verification-control/RECORDED-RUN-2026-07-28.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
mrwulf 2026-07-28 21:18:44 +02:00
parent 9eb3beabc4
commit 93d62703f3
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
TRUSTED-BASE.md
View file

@ -38,3 +38,19 @@ running Rust code. Everything else is machine-checked.
6. **Compilation of Rust to machine code** (rustc backend) is out of scope,
as is side-channel behaviour (timing, speculation). The proofs are about
functional correctness at the MIR/LLBC level.
7. **What the axiom gate binds, and what it does not.** `check.sh` Phase 2b
reads every compiled `Proofs/*.olean` and fails the build if any
declaration there is an axiom. It asks the kernel rather than parsing
source text, because the source-text check in Phase 1 is evadable four
ways — an indented `axiom`, `@[simp] axiom`, `unsafe axiom`, and `axiom`
with the name on the following line all compile and all miss its pattern.
Membership self-derives from the filesystem, so `Scalar*` and `AxiomCheck`
are covered as well, and the count of compiled modules must equal the
count of shipped sources, so a deleted `.olean` cannot make the scan pass
vacuously. `selftest-axgate.sh` attacks the shipping gate rather than a
copy of it, and was itself negative-tested by removing the gate's error.
**The residue you must still supply yourself:** this binds *declarations*,
not *statements*. Nothing in the button establishes that a certificate's
theorem says what its name — or this document — suggests it says. A
theorem gutted to a tautology with the same axiom cone would pass every
phase. Reading the statements remains a human act.