Status
Phase 1 — M0 passed
Milestones passed: M0. Every claim is backed by a hashed, verifiable evidence bundle validated before publication.
Milestone states on this page are generated from a validated data file. A milestone turns green only when a hashed, verifiable evidence bundle has passed the deterministic acceptance validator for the required target. Nothing here is written by a model.
| Milestone | Gate | State | Target | Note |
|---|---|---|---|---|
M0 Wave 0 evidence and metering contracts | W0-14 | Passed | host | Gate W0-14 passed: 14 packets, 171 of 171 tests passing, 0 skipped. Evidence target: host. |
M1 Wave 1 r8q AOSP baseline boot | W1-14 | Not started | — | — |
M2-A A77 egress enforcement stop gate | W2-06 | Not started | — | — |
M2 Wave 2 security kernel | W2-23 | Not started | — | — |
M2.5 Wave 2.5 R0 inference infrastructure | W25-13 | Not started | — | — |
M3 Wave 3 trusted shell | W3-12 | Not started | — | — |
M4 Wave 4 Agent City and proof of concept | W4-16 | Not started | — | — |
M5 Wave 5 local model and R1 | W5-12 | Not started | — | — |
M5.5 Wave 5.5 R2 accelerator placement | W55-08 | Not started | — | — |
M6 Wave 6 R3 scheduling and hardening | W6-15 | Not started | — | — |
V1-GO v1 release gate | V1-GO | Held — awaiting hardware | — | Requires a relockable verified-boot target. The current development device is an open-bootloader prototype target, so this gate is held awaiting hardware. |
Labels
- Not started
- No accepted evidence exists.
- In progress
- Work is underway; nothing is claimed.
- Passed
- The gate bundle passed validation for the stated target.
- Held — awaiting hardware
- Software work may continue; the gate cannot be satisfied on present hardware.
- Held — owner action
- A physical or offline owner action is required.
Target labels distinguish host, emulator and physical device evidence. Emulator evidence never satisfies a physical-device gate.