Build
Project architecture
Keep UI, long-lived runtime resources, and optional peers in clear boundaries.
Verified 25 September 2026
The primary desktop pattern separates the renderer from a worker. This is a runtime requirement, not just code organization.
- Renderer: UI state, user interactions, and narrow bridge calls.
- Worker: Hyperswarm, Corestore, Hyperbee, Hyperdrive, QVAC, and cleanup.
- Bridge: typed messages with timeouts, errors, and visible status.
- Optional Node: a separate peer for replication or delegated inference; local work must survive its absence.
Shutdown matters
Close swarms, stores, model handles, and worker pipes explicitly. Treat reconnecting and unavailable states as normal.
Public issue reporting will be linked here after the repository and support route are anonymously accessible.