Kernel UI Workbench¶

The Kernel UI Workbench is a consumer corpus for editing application-owned resource state through a bounded browser adapter. It is called a kernel UI example because it demonstrates UI around stable Tokimu meaning, not because DOM controls or application-specific resource fields belong in tokimu-core.

What This Proves¶

browser pointer / keyboard
              ↓
       TypeScript adapter
              ↓
 Rust/WASM ResourceWorkbenchModel
              ↓
 provider-neutral observation
              ↓
       accessible DOM view

Rust owns resource identity, filtering, selection, draft state, command eligibility, and delete confirmation. TypeScript owns browser input and DOM presentation. The two hosts, native ui-tools and browser DOM, consume the same application model without pretending their presentation mechanisms are equal.

Experimental UI consumer evidence / on demand

Resource control room

Activate a Rust/WASM resource editing session. Filter and select stable resource identities, edit draft fields, toggle presentation flags, apply or revert changes, and exercise a model-owned delete confirmation flow.

This is evidence for UI composition and state ownership, not admission of resource-editor policy into the trusted kernel.

Idle No resource editing session loaded

Ownership Boundaries¶

DOM nodes are presentation targets, not authoritative resource state.
TypeScript does not decide whether Apply, Revert, or Delete is legal.
The resource model remains application-owned corpus evidence.
ui-tools provides the native presentation path; the browser provides a separate consumer path over the same state transitions.
Closing the island releases its WASM session.

See the website consumer design and the native resource workbench design for the complete evidence claim.