trajectory / status tokens reflect repository state, not commitments
No dates. Only states.
A thing is proven when hardware evidence exists, in build when code exists without hardware proof, and planned when only decisions and documents exist. Nothing below pretends to be further along than the repository can show.
proven
MVP0 - the verified media baseline: exact serial gate, refusals, raw post-write hash, validated on a real disposable stick.
hardware evidence
shipping
MVP1 - the Windows guided installer on this site: preflight, staging, gated write, boot handoff.
cli proven / gui written
planned
MVP2 - assistant surfaces on the installed system: tray app, local action logging, a dedicated AI browsing profile, lab-only voice.
not built
planned
MVP3 - the OutOS image itself: signed Fedora Atomic / bootc base, atomic updates, always-bootable rollback. The installer repoints through its target manifest.
direction chosen - build not started
vision
MVP4 - the permission broker: deny-by-default approval for every privileged AI action, and a ledger of what really changed. Cannot start before action logging and rollback are proven.
hard-gated
When OutOS itself ships, these pages will say so. Until then they say this.