TRACK A
Designing
Product contract
Freeze schemas, threat models, canonicalization, verifier images, and evidence formats.
Product roadmap · contracts before code
Build the trust boundary in public.
The machine already proves that real Linux can live in a browser. The next product layer adds private state, verified delivery, and a market where useful software work earns payment only after evidence.
North star
One URL, one user-owned computer, inspectable work.
A user boots Linux, unlocks an encrypted overlay, receives verified blocks from the best available source, and can publish a reproducible optimization task to a network of builders and critics.
TRACK B
Next proof
Local builder/critic loop
Run one builder and three critics against a real `wasm-vm` workload with no token and replayable settlement.
TRACK C
Planned
Passkey-owned volumes
Add multiple credentials, recovery slots, encrypted overlay generations, rotation, and revocation.
TRACK D
Planned
Verified block distribution
Unify HTTP, cache, WebRTC, and torrent-like sources behind demand-first, hash-before-cache semantics.
TRACK E
Planned
Critic network
Assign diverse critics, commit/reveal reports, quorum, challenge windows, bonds, and proof bundles.
TRACK F
Planned
Public marketplace
Introduce auctions, bounties, accounting, private tickets, quotas, and abuse controls.
TRACK G
Long term
Distributed operating environment
Only after storage and evidence are solid: replicate state, discover services, and place work across browser nodes.
Principles
What will not change.
Verifier before token
Settlement starts with deterministic acceptance. A coin is optional infrastructure, not a correctness mechanism.
Private by default
User overlays stay local until a user explicitly publishes an encrypted generation.
AI proposes, code decides
AI can draft a task, test suite, or critic report. Only hashed executable policy can settle it.
Scope language: distributed delivery and encrypted storage come first. We will not call this a fully distributed operating system until processes and coordinated services actually span browser nodes.