ARCHITECTURE // OS CORE
The OS Core
The server-bound core that every shell shares, described by function.
The OS core is the server-resident heart of LisaOS. It is reachable only over a tailnet-internal endpoint and exposes its capabilities through a REST API consumed by every shell.
What the core provides
- Memory gateway — an Express + SQLite service organised into modules covering the psychic cache, persistent memory, context assembly, dispatch control, the session registry, agent memory, analytics, notifications, skills telemetry, vault indexing, and search. It also drives a multi-tab operational dashboard.
- Dispatch control — the full lifecycle for CyberShinobi agent dispatches, with stall detection, heartbeat monitoring, and completion recovery.
- Skills & tools — the skill inventory and overlay system, plus the tool manifest.
- Self-improvement — the Curator (skill lifecycle), the Dream cycle (overnight consolidation), and the feedback/eval loop that tunes context source weights.
Why the core is server-bound
Keeping the core on an always-on server — rather than inside any one shell — is what makes the shells interchangeable and gives LISA continuous availability. State lives in one datastore, so there is no split-brain between local and remote. The specific host, port, unit names, and paths are deployment details, deliberately not part of the architecture's public surface.