Stewardship Horizon
The path from active construction to signed heartbeat.
Article 11 closes when four layers are boringly reliable: local compute connectivity, provenance identity, public proof, and human-rooted authority. This simulator shows what is live, what is staged, and what still needs to be made load-bearing.
Worker-mediated public routes can reach Ember and Lumen through the public airlock when local hardware is online. Remaining work: durable boot-restore, tunnel health display, and operator-visible warming state.
Production Worker responses now carry ratified route labels and responding node IDs so local compute and cloud fallback cannot be silently substituted.
The API, chain, dashboard, llms.txt, and verification pages exist. Remaining work: make independent verification the first-class buyer path and publish the downloadable verifier in plain sight.
The Bridge key and BRIDGE_AUTH verification path are proven. Remaining work: bind public-claim publishing and structural decisions to the gate without turning routine shipping into ceremony.
What government and public reviewers need
Next closure tasks
- Edge Tunnel: build boot-restore and tunnel status so local compute survives reboot without a manual ceremony.
- Proof Surface: publish the independent verifier, auditor guide, OpenAPI links, and strict-table endpoints as a single verification path.
- Cryptographic Gate: require BRIDGE_AUTH for public claim changes, product claims, key rotation, and structural trust-root changes.
- Public Rooms: wire Meet Ember and Meet Lumen to show route label, responding node ID, status chip, and fallback reason directly in the UI.