mirror of
https://github.com/saymrwulf/ltl-accumulator-verified.git
synced 2026-09-03 19:53:48 +00:00
- STATEMENT-MAP.md: the review surface — every paper §6/§10 item mapped to its Lean name, file, and cone; the named-extractor design invariant and the anti-pigeonhole guards explained; the audit surface stated. - KNOWN-GAPS.md: eight honest scope boundaries, including the process- history candor item (the guessed-pins/false-green episode and its fix). - README: frozen banner. Final sweeps: button EXIT 0 + ALL GREEN + FIDELITY GREEN; zero sorry; the only ∃-conclusions are content-bearing (kbelow_pow2) or hypothesis-guarded helpers — no collision existentials anywhere. Corpus: 54 pinned cones over a defined surface, single sha256 boundary, Lemma 1 axiom-free, Theorems 1-3 + Prop 1(1) + whole-tree Lemma 2 + fidelity 164,479/164,224. Frozen at this commit pending external review. LTL untouched (12 leaves, bcd15f9d). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
44 lines
3 KiB
Markdown
44 lines
3 KiB
Markdown
# ltl-accumulator-verified
|
|
|
|
Lean 4 mechanization of the security analysis (§6) of the paper
|
|
"The Lean Transparency Log" (https://ltl.zkdefi.org/paper): the Merkle
|
|
accumulator's own correctness and soundness theorems, kernel-checked, in
|
|
the same discipline as the four `*-ed25519-verified` subject corpora.
|
|
|
|
## Status: **FROZEN for external review** (corpus complete)
|
|
|
|
All paper-§10 mechanization targets are kernel-checked; the audit surface
|
|
is defined and green (`verification/check.sh`, exit 0). See
|
|
[STATEMENT-MAP.md](STATEMENT-MAP.md) for the paper↔Lean review surface and
|
|
[KNOWN-GAPS.md](KNOWN-GAPS.md) for the honest scope ledger. No changes
|
|
until the external review round (second model instance + GPT + author)
|
|
completes. The finished certificates' attestation into the LTL is a
|
|
separate, explicitly-authorized operator decision.
|
|
|
|
| layer | content | status |
|
|
|---|---|---|
|
|
| L1 | bytes, hleaf/hnode, domain separation (Lemma 1) | **done** (domsep: axiom-free) |
|
|
| L2 | MTH, Root, ConsRec definitions + termination | **done** (cones: propext, LTLAcc.sha256, Quot.sound) |
|
|
| L3 | inclusion completeness (Theorem 1) | **done** (incl_complete: propext, Classical.choice, LTLAcc.sha256, Quot.sound) |
|
|
| L4 | frontier binding content (Lemma 2) | **inlined in the extractor walk** (extractIncl); standalone receipt-uniqueness theorem queued for S4 restoration in extractor form |
|
|
| L5 | inclusion soundness = EXPLICIT extractor `extractIncl` (Theorem 2) **done, non-vacuous** |
|
|
| L6a | descent extractor `extractMTH` (Theorem 3 step 3 = Lemma 2, WHOLE-TREE instance) **done, non-vacuous** |
|
|
| — | Lemma 2, PATH instance (receipt-uniqueness of `Root`): deleted with the vacuous `root_binding` in S3.5 and **not yet restored**; optional, not needed for Theorem 3 |
|
|
| L6b | ConsRec binding + Theorem 3 assembly (extractCons) | in progress (S5): stage-1 arithmetic/list infrastructure done (kbelow_prefix_eq, take surgery); stage-1 infra + extractConsNode extractor DEFINED (faithful to ConsRec by inspection — NOT yet machine-checked); **consRecBinding PROVEN** (Theorem 3 steps 1-2, kernel-checked, no sorry); extractCons assembly (step 3 join) = S5.4 |
|
|
| L6 | pin-store state machine safety (Proposition 1) | pending |
|
|
|
|
## Discipline (identical to the subject corpora)
|
|
|
|
- `verification/Proofs/` contains ZERO `axiom` declarations; the single
|
|
sanctioned axiom site is `verification/gen/` — here, one opaque
|
|
function: SHA-256. The theorems are constructive collision extractors,
|
|
so collision resistance is never assumed, only interpreted.
|
|
- `verification/check.sh` is THE button: compiles every file through
|
|
`lean-guard` (memory cap, core pinning, timeout, single-flight lock)
|
|
and axiom-audits every certificate against its documented exact cone.
|
|
- Expected boundary: `propext, Classical.choice, Quot.sound` plus
|
|
`LTLAcc.sha256` for hash-touching certificates — documented per
|
|
certificate in `check.sh`, audited both directions.
|
|
|
|
The finished certificates are destined for the LTL itself as attestation
|
|
leaves: the log carrying kernel-checked proofs of its own machinery.
|