saymrwulf/proof-aware-crypto-tooling-agent
1
0
Fork 0
mirror of https://github.com/saymrwulf/proof-aware-crypto-tooling-agent.git synced 2026-09-05 20:10:34 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
proof-aware-crypto-tooling-.../evidence
History
mrwulf 71c670527c REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 
The provider ran its full honest replay against the four verified
repositories on this machine - every Lean compile and axiom audit routed
through lean-guard (memory-capped, core-pinned, single-flight, ~30 min
per fork) - and the results are now shipped under evidence/:

- 16/16 certificates proven per fork, every axiom cone boundary-exact
  (the four apex tiers carry their fork's documented SHA-512/wire
  boundary axiom-for-axiom), each attestation pinned to the exact repo
  commit (dalek 8ded7bc, anza 673c15e, risc0 98a13a6, betrusted
  81f614a) and Ed25519-signed.
- All four appended to the persistent transparency log. The log holds
  EIGHT leaves: the first four are the initial run's attestations,
  which honestly recorded an AUDIT FAILURE (the two pacta bugs fixed in
  e87f0e8) - an append-only trust ledger keeps its bad day, and the
  fixed run's leaves sit beside it.
- Every receipt re-verified through the FULL stack: dogfood verifier
  (backend verified-dalek-serial recorded), STH pin store, freshness
  policy. Receipts are freshly issued against the final tree (a stale
  mid-run receipt tripped the pin store's rollback defense exactly as
  designed; the rollback diagnostic now hints at idempotent re-issue).
- The capstone consequence ran for real: pacta agent with trusted
  provider + signature via the proven path + required receipt + pin
  store + --require-verified-verifier built the R4-gated library
  capsule from ATTESTED evidence (no local Lean replay needed by the
  consuming agent).

Docs and teaching updated against the real artifacts: evidence/README
(inventory + re-verify instructions), README "Real Evidence" section,
lecture 5 now re-derives 16/16 verdicts from the REAL dalek attestation
(signature checked on the proven path, provider labels ignored), and
lecture 6 verifies all four REAL receipts and walks a fresh pin store
over them. Every changed notebook cell executed before commit. 49/49
tests green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 14:54:48 +02:00
..
anza-ed25519.attestation.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
anza-ed25519.receipt.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
betrusted-ed25519.attestation.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
betrusted-ed25519.receipt.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
dalek-ed25519.attestation.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
dalek-ed25519.receipt.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
latest-sth.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
log-audit.txt REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
log-metadata.json REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
provider.ed25519.pub REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
README.md REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
risc0-ed25519.attestation.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00
risc0-ed25519.receipt.yaml REAL EVIDENCE: guarded replay of all four repos, attested, logged, dogfooded 2026-07-06 14:54:48 +02:00

README.md

Real Provider Evidence

Signed, transparency-logged attestations from a REAL guarded replay of the four saymrwulf/*-ed25519-verified repositories (2026-07-06/07, ~30 min of Lean re-checking per fork under lean-guard memory caps).

File What it is
<fork>-ed25519.attestation.yaml Signed proof-check attestation: repo commit, environment, machine-protection block, and all 16 certificates with their OBSERVED axiom cones (the four apex tiers carry the fork's exact documented boundary)
<fork>-ed25519.receipt.yaml RFC 9162-style inclusion receipt binding the attestation into the transparency log (tree size 8), with a consistency anchor
provider.ed25519.pub The provider's public key (the PRIVATE key never leaves provider/state/, which is gitignored)
log-metadata.json, latest-sth.yaml Log identity and the latest Signed Tree Head
log-audit.txt Monitor self-check output (recomputed root matches the signed root)

The log holds EIGHT leaves: entries 0-3 are the first run's attestations, which honestly record an AUDIT FAILURE (two bugs in pacta's audit step, since fixed - see the commit history); entries 4-7 are the definitive 16/16-proven attestations. An append-only trust ledger keeps its bad day.

Re-verify everything yourself (signature via the proven-path verifier if built, STH pinning, freshness):

pacta receipt-verify \
  --attestation evidence/dalek-ed25519.attestation.yaml \
  --receipt evidence/dalek-ed25519.receipt.yaml \
  --log-public-key evidence/provider.ed25519.pub \
  --sth-store /tmp/my-pins.json --max-sth-age-seconds 604800