papperrollinggery Checkpoint
Required Knowledge
Read only the reference needed for the active task, not this entire list. The root v2 route owns scope and authorization; legacy records do not add gates.
docs/film-preproduction/phase-contracts.yamldocs/film-preproduction/chat-inline-visualization-interface.mddocs/film-preproduction/schemas/skill-orchestration.yaml.dircreative/checkpoints/.dircreative/timeline.jsonl
Inputs
- current phase
- git status
- recent skill_run_receipt
- unresolved questions
Outputs
- checkpoint markdown
- timeline entry
- next exact action
Visual Decision Contract
When visualization adds clarity, use skills/dircreative/assets/visualizations/stage-surface-registry.json#checkpoint-current-state. Show current stage, locks, stale artifacts, unresolved decision, and next action from the audited current-state projection; resume intent must re-enter the active gate and preserve the Markdown fallback.
Rules
- Save current active phase, completed artifacts, verification status, blockers, and next command.
- Do not delete old checkpoints automatically.
- Keep checkpoint text actionable for another worker.
skill_run_receipt
Persist the following only for a requested formal handoff, pause/resume or actual execution record. Ordinary work returns its result without a separate receipt. The next skill is advisory; the controller continues only the requested scope.
Record checkpoint file path, active phase, unresolved questions, and next_recommended_skill.