Drive the governance kernel, live
This isn't a mock-up. Flip the context, toggle which tools exist, or pick a preset — and watch tools rearrange between Allowed, Ask, Denied, and Absent. Every verdict comes from the real compiler and kernel — the same Rust the harness runs on your machine, compiled to WebAssembly. Nothing here is a reimplementation, and CI fails if this build drifts from the kernel it claims to be.
World editor
Untoggle a tool to make it ABSENT — it stops existing in this world, rather than being denied.
View generated manifest (YAML)
Projected reality
Engine … · the real compiler + kernel, compiled to WebAssembly and running entirely in your browser.
Try it: switch to Tainted and watch the network / MCP / memory tools jump to DENIED — the monotonic taint floor, the rule that severs "read something untrusted" from "reach the network". Then untoggle a tool: ABSENT is not a stricter DENIED, it is the tool never being offered at all. A denied tool is one the model can still see and argue about.
What this does not show. Each action is decided here against sample arguments, so the two rules that need a real call are not exercised: path scope (which file a write targets) and command classification (which shell command is being run). Both run in the harness itself, per call. This page answers "what does my manifest project, and what survives taint" — not "what happens to this exact command".