Session Registry

The session registry is the gateway's record of live LISA sessions across every shell. It is what makes simultaneous sessions inter-aware rather than mutually blind.

Heartbeats

Each session maintains its own working state and, on every state update, sends a heartbeat to the registry carrying its current mission namespaces, active dispatches, and a prose working-state snapshot. Because both shells report to the same registry, each can see what the other is doing.

Stale detection

A background detector auto-ends sessions whose heartbeat is older than a fixed threshold, so a crashed or abandoned session does not linger as "active" forever. Heartbeats are best-effort: if the gateway is offline, the write fails silently and the session continues.

Session lifecycle

A session that closes cleanly commits its memory before deregistering; one that goes silent is reaped by the stale detector. Either way it leaves the registry — no session lingers as "active" indefinitely.

Simultaneous sessions

When multiple shells are active at once, each keeps its own context independently, but cache writes from either are immediately available to the other via context assembly. Before re-dispatching work that may already be running on the other channel, LISA checks the dispatch list rather than duplicating it. See Interchangeability.