framework-checkpointlisted

# Framework Checkpoint ## Purpose Make project work resumable from versioned repository evidence rather than hidden chat or Agent memory. ## Trigger Run after a major Artifact/Gate result, before a blocking question or Target Stage pause, after escalation/replanning/integration, and before session end or expected context loss. ## Inputs - Current State, Artifact Registry, Component states, active task, and Gate evidence. - Repository revision, branch/worktree identity, and working-tree status. - Current/Target Stage, Project/Task Workflow Levels, Execution Mode, and Current Minimum Necessary Path. - Decisions, assumptions, open questions, risks, blockers, and next ready action. ## Prerequisites - Reconcile obvious State/repository discrepancies before declaring a clean snapshot. - Reference persisted Artifact paths and exact revisions rather than copying chat claims. ## Procedure 1. Assign a Checkpoint ID and timestamp/repository reference. 2. Record repository revision, branch/worktree, dirty paths, and any uncommitted dependency relevant to recovery. 3. Record Current Stage, Target Stage, Project Workflow Level, Task Workflow Level, and Execution Mode. 4. Record Active Task, owner capability, status, dependencies, scope, and DoD. 5. Record Artifact IDs/revisions/states and Component IDs/contracts/states with latest evidence. 6. Record decisions, assumptions, Open Questions/Clarifications, risks, accepted deviations, and blockers. 7. Record work completed since the