Muster on the Logos stack

Pick a way of running it; the parts of the stack it leans on light up. Everything below the dark rule is infrastructure you do not run — and every box down there learns something.

Logos stack · Muster
Muster on the Logos stack Three entry points sit above app backends, modules, the network layer and the runtime. Below a dark rule, the store-node fleet, the execution-zone sequencer and the public record are infrastructure the user does not run. HOW YOU RUN IT APP BACKENDS MODULES NETWORK RUNTIME BEYOND YOUR DEVICE the device ends here Logos Basecamp default launcher · loads UI plugins Muster UI muster-ui.lgx Messaging LEZ Wallet Package manager Standalone app one binary · no launcher Muster, bundled its own UI + just the modules it needs Headless CI and P0–P3 · no UI $ logoscore drives the module directly muster-module.lgx — Nim core behind muster.lidl specified, not built (P0) Dex lez_core zone wallet · token ops · labels Files chat_module e2e · MLS groups Swaps Capability Package Manager Blockchain Storage delivery_module embeds a Logos Messaging node P2P · discovery · peering mix routing — not shipped LIP status raw · send-only PoC logos runtime — subprocess isolation, capability-scoped calls Store nodes — logos.test fleet sees subscription shape and timing LEZ sequencer sees that a transfer happened, and when The public record whatever the chosen rail disclosed, forever
ours specified, not built infrastructure you do not run

The stack, whole

The dark band is the point. A stack diagram usually stops at the runtime, which quietly implies the picture is complete — but a client that talks to nobody does nothing. Every box below the rule is a party that learns something from you using this, and naming them in the architecture diagram is the cheapest honesty available: it means you cannot describe the system without describing its observers.