⌘K
ENES
GitHub
phase~1 min readUpdated 2026-07-16#phase#wasi#components#sandboxing

Phase 06 — Beyond the Browser

The browser is the primary host of the Workbench, not the limit of portable execution. This phase packages deterministic pipeline capabilities as typed components and then uses the same boundary to host least-authority tools outside the browser.

Branches

  • WASI, Components & WASI-NN — WIT, worlds, interfaces, resources, Canonical ABI, composition, WASI host capabilities, and optional host-provided inference.
  • Sandboxed AI Tools & Plugins — typed tool contracts, capability policy, fuel, deadlines, memory, state, provenance, approval, and audit.

Workbench milestones

v7 — Portable inference component: package a deterministic pipeline slice behind a versioned WIT world, run it in a WASI runtime, and compare its output with browser and native golden references. WASI 0.3.0, released 2026-06-11, is the pinned study baseline.

v8 — Sandboxed AI tools: host each tool as a component with typed input/output, explicit imports, memory and compute budgets, timeouts, provenance, and no implicit filesystem or network. The model interprets and chooses; deterministic code calculates and verifies.

WASI-NN remains a Phase 2 proposal as consulted 2026-07-16. Support must be measured per runtime and backend; absence is an explicit unsupported result, not proof of universal portability failure.

What this phase establishes

  • Portable typed interfaces separated from host-specific capabilities.
  • A clear core-module, component, WIT, Canonical ABI, and WASI mental model.
  • Contract tests shared across browser, WASI, and native reference paths.
  • Least-authority tool policies plus resource and lifecycle enforcement.
  • Audit records that separate model choice from deterministic execution.

Exit criteria

  • Component imports and exports match the reviewed WIT world and version.
  • The portable pipeline matches its golden reference within documented tolerances.
  • Unavailable WASI or WASI-NN capabilities are reported without silent substitution.
  • Tool tests cover denied capabilities, malformed input, traps, budgets, timeout, replay, and revocation.

Keep Always Active attached to release and portability claims.

Related notes

Wasm AIAlways Active — Performance, Security & VerificationApply benchmarking, numerical regression, compatibility, security, integrity, and reproducibility to every WasmAI Workbench milestone.Wasm AIPhase 00 — OrientationEstablish prerequisites, platform boundaries, reading routes, compatibility honesty, and the verification contract for WebAssembly AI Atlas.Wasm AIPhase 01 — WebAssembly FoundationsLearn modules, WAT, validation, toolchains, linear memory, ABI, and host interop before building inference kernels.Wasm AIPhase 02 — Inference from First PrinciplesBuild tensor operations and a tiny forward pass, then measure scalar, SIMD, and threaded Wasm without surrendering numerical correctness.