Can work continue across sessions?

Agent work rarely fits in one sitting, so continuity is a first-class part of the daemon rather than a convention agents are asked to follow.

Sessions capture a body of work as it happens, and checkpoints pin known-good states you can return to. When one session ends and another begins (tomorrow, on another machine, or in another agent entirely) a cross-session handoff carries the working state forward with its receipts attached, so the next session starts from evidence rather than a summary someone hoped was accurate.

Plans persist too. ExecPlans live on the live work board with milestones and state, so what was planned, what is in progress and what is blocked survives any individual session. Decision records keep the why alongside the what.

For work your fleet repeats, engrams compile a procedure into a reusable form with a provenance hash, so an agent can rerun a proven procedure and you can verify exactly which version ran and where it came from.

All of this rides the same spine as everything else: every checkpoint, handoff and plan update is a receipted, passport-bound mutation. Continuity in CueCrux is not a transcript passed forward; it is a chain of records that survives the participants.