> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comet.rpamis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Continuation and checkpoints

> Understand Native continuation, automatic stop conditions, and cross-session recovery from files instead of chat memory.

Native continuation is neither a background job nor an unconditional loop. Every real transition returns the next phase, routing intent, and a structured continuation. The Skill proceeds only when state permits it.

## Continuation outcomes

| Disposition  | Meaning                                                             | Next action                                               |
| ------------ | ------------------------------------------------------------------- | --------------------------------------------------------- |
| `continue`   | The transition completed and the next action is unambiguous         | Reread the new phase and required artifacts, then proceed |
| `await-user` | A user decision remains                                             | Ask one upstream question and end the turn                |
| `blocked`    | State, evidence, conflict, or recovery conditions are not satisfied | Resolve the finding without guessing around it            |
| `done`       | Archive completed                                                   | End the workflow                                          |

`next: auto` means the Runtime allows continuation; it does not start a daemon. If the caller explicitly asks to stop after a transition, the Skill makes no further tool call after that transition. A later session resumes from disk.

## What a checkpoint stores

For an interruption within one phase:

```bash theme={null}
comet native checkpoint <change-name> \
  --summary <completed-facts> \
  --next-action <next-action> \
  --artifact <project-relative-path> \
  --expect-revision <n>
```

A checkpoint stores a concise factual summary, the next action, and a content-addressed artifact manifest. It does not advance the phase or replace the brief, complete target specifications, or `verification.md`.

On recovery, Runtime checks the checkpoint phase, revision, and manifest. A change to any of them marks the checkpoint stale. The old summary remains historical context but cannot override current state.

## Why Native has no separate handoff document

Classic passes work across phase Skills and external methods, so it needs design context, plans, and compression projections. Native uses one Skill that rereads formal artifacts:

* the brief and target specs retain requirements;
* state and continuation retain phase;
* checkpoints retain in-phase progress;
* verification reports and receipts retain evidence.

Native therefore has no `context_compression` mode and does not generate a handoff solely to transfer context between phase Skills.

<p align="center">
  <img src="https://mintcdn.com/comet-bb5f5294/A7fDsLoRlesBiCJd/assets/native-illustrations/06-continuation-checkpoints.png?fit=max&auto=format&n=A7fDsLoRlesBiCJd&q=85&s=b58415db9f5a168f6c67d196294c11e0" alt="Xiaoyu places a next-action bookmark into a transparent record box of formal artifacts while another Xiaoyu receives it to continue work" width="1672" height="941" data-path="assets/native-illustrations/06-continuation-checkpoints.png" />
</p>

Continue with [Artifacts and state](/en/native/artifacts-and-state), [Verification and repair](/en/native/verification-and-repair), and [Recovery and troubleshooting](/en/native/recovery-playbook).