27 Sep 2026 · 0.3.0
AriCodeOS 0.3: sandbox and WebAssembly
Phases 28 and 29: applications receive only what their manifest asks for, and portable modules run in an in-house interpreter.
What changed
- Application manifests and a capability broker in init
- A private directory per application in fsd and a per-process DMA memory quota
- The shell launches through the broker and can no longer create processes itself
- A no_std WebAssembly interpreter and wasm_runner exposing only the Capability API
0.3.1 applies the fixes from the SDK audit.