1# llimphi-wasm-open23Opens a Tier 3 WASM app as a desktop window.
45It closes the distribution loop: the Tier 3 stack already knew how to resolve an
6app by hash, verify its integrity and its Ed25519 grant, and materialize its
7`View<Msg>` into a Llimphi window. What was missing was the **executable** tying
8it all together from the desktop's command line — the host twin of wawa's app
9executor, and the real consumer of `app_bus::Launch::Wasm` (which until now
10returned `Unsupported` because "the chassis resolves it": this binary *is* that
11chassis).
1213Two modes:
1415```text16# 1. A local .wasm — UI-only app, no permissions (the fast path).17llimphi-wasm-open app.wasm
1819# 2. By hash from a local CAS — integrity is verified and, if there is a20# grant, it is validated against the trust ring and run with the21# effective permissions (the bits gate which host imports get linked).22```2324---
2526Part of **llimphi** — see [llimphi](../README.md).
README.md
llimphi-wasm-open
Opens a Tier 3 WASM app as a desktop window.
It closes the distribution loop: the Tier 3 stack already knew how to resolve an
app by hash, verify its integrity and its Ed25519 grant, and materialize its
View<Msg> into a Llimphi window. What was missing was the executable tying
it all together from the desktop's command line — the host twin of wawa's app
executor, and the real consumer of app_bus::Launch::Wasm (which until now
returned Unsupported because "the chassis resolves it": this binary is that
chassis).
Two modes:
# 1. A local .wasm — UI-only app, no permissions (the fast path).
llimphi-wasm-open app.wasm
# 2. By hash from a local CAS — integrity is verified and, if there is a
# grant, it is validated against the trust ring and run with the
# effective permissions (the bits gate which host imports get linked).