Proofs
Every published milestone is backed by a hashed, verifiable evidence bundle. The bundle records the exact source revision, commands, test enumeration, artefact hashes and target label, and is checked by a deterministic validator before anything appears here.
| Milestone | Proof | Target | Bundle SHA-256 |
|---|---|---|---|
M0 | M0 gate W0-14 evidence bundle 14 packets accepted; 171/171 tests; Law registry 01b30823cc47…; no skipped proofs. | host | f224d530fca99bf765e397c009976ed7a881e0761b55dbf6353f86778319e2bc |
M1 | M1 gate W1-14 evidence bundle 28 packets accepted; 306/306 tests; Law registry 01b30823cc47…; no skipped proofs. | physical device | 4cc916a56f48b4e99b28b5f99f8ea279ec17130e2832f503ae39f2913920e1aa |
What a proof contains
- Packet, attempt and terminal state.
- Hashes of the frozen specification and derived plan the work was accepted against.
- Source revision, build identity and dependency bundle hashes.
- Every command run, with tool identity and arguments.
- Test enumeration with pass, fail and skip counts; an empty suite is a failure.
- Raw artefact hashes and a target label: host, emulator or physical device.
What is never published
Raw bundles, protected file paths, source code, key material, device identifiers, internal addresses and open findings. A resolved finding may appear as a one-line summary.