Skip to main content
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

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:
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.

Xiaoyu places a next-action bookmark into a transparent record box of formal artifacts while another Xiaoyu receives it to continue work

Continue with Artifacts and state, Verification and repair, and Recovery and troubleshooting.
Last modified on July 22, 2026