memai-checkpointslisted

# memai-checkpoints — the lifecycle of a checkpoint A `checkpoint` is a **bearing summary** — where the work stands — transient and replaced as the work moves on ([[memai-memory]] §5). The durable knowledge lives in `note`/`reasoning`/`anti_pattern`. This skill keeps **only the bearing still needed** and retires the rest **without losing knowledge**: if the durable part is not in a `note` yet, it goes there first ([[memai-distill]]). > **This skill does not curate `note`.** Only `type=checkpoint` records enter > here. > **It proposes; it does not apply.** Everything below is staged through > `optimize_stage` and applied or rejected by the human in the dashboard. The > destructive kinds it can stage — `archive` and `distill` — are **rejected > without a non-empty `verified`** describing the live-facts check behind them. --- ## 1. The state of the work is declared by the project Every decision below turns on whether the work a checkpoint is the bearing for is **live**, **paused** or **closed**. That state is not in the store: MemAI records where the work stood, not whether it is still open. So read it from whatever the host project **declares** as its source of truth for the state of work — a section of its own `CLAUDE.md`, an issue tracker, the branch and the git log, a status file the project keeps. This skill reads that source; it never infers the state from a checkpoint's own wording, from its age, or from a domain having gone quiet. Establish what the source is befo