// Z-15 / trace ledger

Trace ledger

Every Z-15 run writes one JSONL record to z15_engine/memory/traces.jsonl in the public repo. Each record carries an input fingerprint, an output fingerprint, source-ledger references, a public-safe summary, the SHA-256 of the NDA-only summary, and a bundle SHA. The public table below shows only public-safe rows. Anything NDA-only travels as a hash.

Public-safe trace rows

RunPublic summaryBundle SHA-256
No proof packets have been signed and published yet. The engine is committed; the first run is queued under Phase B of the benchmark plan.

How to verify a Z-15 trace

# clone the public repo
git clone <repo> bot && cd bot
# inspect the trace ledger
cat z15_engine/memory/traces.jsonl
# recompute the bundle SHA from the five artefacts of any packet
python3 -c "from z15_engine.trace import hash_artifact; import json,sys; print(hash_artifact({p.name:p.read_text() for p in __import__('pathlib').Path(sys.argv[1]).glob('*.md')}))" docs/z15/proof_packet/runs/<run-id>

What gets a bundle SHA

The five artefacts of a proof packet, concatenated as a canonical-JSON map of {filename: contents}, hashed with SHA-256. The hash is written to BUNDLE_SHA256 alongside the artefacts. Anyone with the artefact set can recompute the hash; a mismatch means the packet was modified after signing.