The web Open Mission surface should follow the daemon-owned Mission and Open Mission app boundaries.
It may provide richer navigation, panels, editing affordances, and live updates. It must still consume daemon-published data and send commands through Entity contracts.
For Impeccable Live, the web host is the public route and script host, not a separate runtime owner. The host proxies live requests through Open Mission routes while the daemon runtime supervisor owns start, adoption, release, and reconciliation. To the operator this should feel like one Open Mission surface, not a web app talking to a separate Impeccable product. See Impeccable Live Supervision.
The web surface should not own:
- Mission lifecycle rules
- Repository setup behavior
- Agent adapter semantics
- persisted Mission runtime data
- compatibility parsing for stale daemon shapes
- Impeccable Live process lifecycle
In browser delivery, .svelte components should be treated as views over the Open Mission application context and its client-side Entity instances. Shared Entity-backed state, reconciliation, save flows, and cross-component semantics belong in the application model layer and client Entity classes, not in individual renderer components.
Better UI is welcome. New domain authority is not.