Under the hood

State: Booting
Build: –
Events routed: –
Audit entries: –

Installed capsules

Rust capsules (astrid-sdk, compiled to WebAssembly) running the page's behaviour. Uninstall one and the part of the page it powers stops. Install and uninstall mint and revoke capability tokens on the audit chain. Native installs additionally verify publisher signatures.

Audit tail

This page is static: GitHub Pages, no backend, no demo server. The embedded AOS engine is not simulated: open devtools, choose Network, and find kernel_web_bg.wasm, the same astrid-kernel crate the daemon ships, booted in this tab. Every check and every audit entry here is the runtime enforcing its own rules. That is the point. The security model is not a cloud promise; it holds wherever the runtime runs, including here.

playground

Build a capsule. Install it. Right here.

This page runs Astrid Runtime, the engine beneath Unicity AOS, in your tab. Write a small capsule below, tick the powers you want it to have, and install it. Every power it uses goes through a real capability check, and every decision lands on this tab's runtime-local audit chain. Untick a box and watch the kernel say no.

Honest framing: real capsules ship as sandboxed WebAssembly. This editor lets you author one in JavaScript against the same capability gate. The checks, grants, denials, and audit entries are the real thing.

manifest

namesubscribes to

capabilities it may hold read its own storage write its own storage publish to site.v1.guest.out

Untick one, install, and the code below still tries to use it. The denial you see is the kernel's, not the page's.

capsule source

live rig nothing installed

bus · site.v1.guest.*

audit ledger

Run it.

One daemon. Every frontend is an uplink; every ability is a capsule.

$ curl -fsSL https://aos.unicity.ai/install.sh | sh