context-savelisted

> Inherits references/kernel.md (the provenance contract). Reads references/wiki-spec.md for schema. ## What this is A checkpoint of **working memory** — the volatile state of an in-flight session — so the next session can resume cold. It is deliberately NOT the brain: a snapshot is ephemeral scaffolding, not a sourced note. Anything in it that is a durable fact must go through `/capture` (into `wiki/` with provenance) before or alongside the save — otherwise that fact dies with the snapshot. ## What goes in a snapshot (and what doesn't) - **IN:** open threads, the current goal, decisions pending your approval, the next concrete action, file paths in flight, and a pointer to the current `context/state.md`. - **NOT IN:** any claim that belongs in `wiki/` (capture it instead), secrets / keys / PII (see `references/blocklist.md`), or raw transcript dumps. ## Execution ### 1 — Sweep durable facts out first Before snapshotting, scan the session for anything that is actually a fact or a decision (not just "where we are"). Route those through `/capture` or `/review` so they land in `wiki/` / `decisions/log.md` with provenance. The snapshot is for the *remainder* — the volatile thread state. ### 2 — Write the snapshot Timestamp `ts=$(date +%Y-%m-%dT%H-%M-%S)`. Write `runtime/checkpoints/<ts>.snapshot.md`: ``` --- kind: checkpoint created: <date-time> state_ref: context/state.md @ <date> # what state.md said at save time origin: agent-generated --- # Where we are <2–4