proof-aware-crypto-tooling-.../evidence/log-metadata.json

{
  "created_at": "2026-07-06T08:43:00Z",
  "ed25519_public_key_fingerprint_sha256": "874c8a008a607021528b2493fa1caf059f9d5c123d29193dfabc09a6d1e7a56a",
  "hash_algorithm": "RFC9162_SHA256",
  "log_id": "205e4c389cb143e08f0d2d58bdc8e425e47e3cbe7f2108cc58bbe835d2cc41d7",
  "provider": "local-pacta-provider",
  "schema_version": 1,
  "standards": [
    "RFC 9162 Merkle tree hash and inclusion/consistency proof algorithms",
    "RFC 8032 Ed25519 signature verification via OpenSSL",
    "FIPS 204 ML-DSA signature slot; must be required by policy only when a backend is configured"
  ],
  "type": "pacta.transparency.log_metadata.v1"
}
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 12:54:48 +00:00			`{`
			`"created_at": "2026-07-06T08:43:00Z",`
			`"ed25519_public_key_fingerprint_sha256": "874c8a008a607021528b2493fa1caf059f9d5c123d29193dfabc09a6d1e7a56a",`
			`"hash_algorithm": "RFC9162_SHA256",`
			`"log_id": "205e4c389cb143e08f0d2d58bdc8e425e47e3cbe7f2108cc58bbe835d2cc41d7",`
			`"provider": "local-pacta-provider",`
			`"schema_version": 1,`
			`"standards": [`
			`"RFC 9162 Merkle tree hash and inclusion/consistency proof algorithms",`
			`"RFC 8032 Ed25519 signature verification via OpenSSL",`
			`"FIPS 204 ML-DSA signature slot; must be required by policy only when a backend is configured"`
			`],`
			`"type": "pacta.transparency.log_metadata.v1"`
			`}`