Save checkpoint

Ask the policy: auto, authored-rest, manual-safe, run-boundary, suspend, hybrid, or existing.

Contract

Publish:

• stable checkpoint_policy_id and revision
• checkpoint/anchor IDs and eligibility predicates
• write trigger and respawn selection policy
• pending/committed checkpoint state
• interaction with run/death policy
• evidence for quit/load/retry behavior

Ownership

This skill decides when and where progression is checkpointed. save-systems owns atomic serialization/migration, save-integrity owns trust/recovery, and cloud-save owns remote revision/conflict behavior.

Rules