# Checkpoints and tasks

## Checkpoints

A checkpoint is not a separate Memory type. It is a Note or Task marked with the
**Checkpoint Preset** so it can support startup and resume continuity.

Use a Note checkpoint for a compact project or session summary. Use a Task
checkpoint when structured progress and next actions matter.

### Write a strong checkpoint

Include:

- the goal and current priority;
- completed work and the current state;
- durable decisions and constraints;
- blockers and failed approaches;
- environment or repository references;
- the recommended next action.

Keep the checkpoint summary short and high signal. Full supporting detail can
remain in the Memory body or linked references.

## Task Details

Task Memories can store structured fields for:

- status and progress;
- ordered next steps;
- parent and child tasks;
- dependencies and assignment;
- blockers and completion criteria;
- outputs, results, decisions, questions, and references.

Updates use Memory version history and conflict-safe expected versions so stale
writers do not silently overwrite newer task state.

## Working across AI tools

When resuming:

1. ask the AI to load the latest checkpoint for the known project;
2. let it inspect previews and references;
3. fetch only the full memories needed for the current action;
4. verify live repository or external state before making changes.

The checkpoint transfers continuity. It does not replace current code, current
documents, or the user's latest instruction as the source of truth.