Scope
Use the continuity layer to make slash-command results durable, source-linked, and assimilable across session resume, handoff, agents, server/editor surfaces, and compaction.
Command families in scope:
- Continuity and recall:
/relay, /context, /memory, /anchor, /recall, /cache, /sessions
- Evidence-bearing state:
/status, /tokens, /cost, /system, /diff, /change
- Agent handoff:
/agent, /subagents, /rlm, /review receipts that other agents can re-derive
PEEK framing
Treat command receipts as orientation-cache entries. The Distiller extracts transferable facts, the Cartographer places them in session/workspace/global maps, and the Evictor drops stale or low-rederivability entries before useful source links.
Acceptance
- Command receipts have source, scope, freshness, and detail-handle metadata.
- Resume/handoff surfaces can reconstruct important command state without replaying raw scrollback.
- Cache entries prefer re-derivable, source-linked facts over hindsight summaries.
- Compaction preserves command receipts needed for future agents to understand the current work.
Related: #1881, #1120, #1818, #1842, #722.
Scope
Use the continuity layer to make slash-command results durable, source-linked, and assimilable across session resume, handoff, agents, server/editor surfaces, and compaction.
Command families in scope:
/relay,/context,/memory,/anchor,/recall,/cache,/sessions/status,/tokens,/cost,/system,/diff,/change/agent,/subagents,/rlm,/reviewreceipts that other agents can re-derivePEEK framing
Treat command receipts as orientation-cache entries. The Distiller extracts transferable facts, the Cartographer places them in session/workspace/global maps, and the Evictor drops stale or low-rederivability entries before useful source links.
Acceptance
Related: #1881, #1120, #1818, #1842, #722.