Roadmap

The implementation order is fixed by the specification. Each wave ends in a milestone gate that must pass before dependent work is accepted.

1. Wave 0 Evidence and metering contracts: schemas, fake authority services, Law-negative test registry, injection corpus, No-AI harness, CI.
2. Wave 1 r8q AOSP baseline: pinned source set, pristine build, boot evidence, hardware smoke, UID/domain, network and listener inventories.
3. Wave 2 Security kernel and egress enforcement through existing netd/eBPF facilities. The fatal-risk enforcement test runs before the kernel is built out.
4. Wave 2.5 R0 inference infrastructure: runtime contract, compute backend, restricted metering, call-cap enforcement.
5. Wave 3 Trusted shell: separate authorisation process, typed fields from L2, fresh authentication, anti-spoof surface, No-AI navigation.
6. Wave 4 Mayor, Workers, Auditor, remote proof-of-concept provider and the exit proof on the development device.
7. Wave 5 Local model and R1 residency/batching, compared against R0-Local.
8. Wave 5.5 R2 accelerator placement, verified by real backend execution, never silent CPU fallback.
9. Wave 6 R3 energy-aware scheduling and hardening.
10. v1 Outbound-polling connectivity, remote lock/locate/wipe, admin policy layer, scheduled encrypted backups, project-controlled verified boot.

Proof-of-concept exit criterion

The project's exit proof, end to end on the development device:

1. A Z3 Worker is fed content containing an injected instruction to read Z2 data.
2. The Worker forwards a capability request as a result.
3. The Registrar denies it with a full L6 audit record.
4. The R0-PoC harness has recorded all L10 fields for that intent.

Hardware holds

The development device is an open-bootloader prototype target. Real verified boot, rollback-resistant storage and the v1 release gate require a relockable target and are held until that hardware exists. Those holds are stated on the status page; they are never reported as passed.