establish-milestone-readiness-from-evidencelisted

# Establish milestone readiness from evidence ## Use Use when a project plan reports a milestone as complete or ready for the next stage. Assess the named milestone at one stated cutoff using supplied records. This is a read-only assessment, not an approval. ## Inputs - Milestone identity, plan version, cutoff, and predecessor links. - The acceptance rule and required deliverable identities for each relevant milestone. - Task states, artifact references, check results, and their observed times. ## Procedure 1. Resolve the target milestone in the supplied plan version. Trace its predecessor graph. Mark a missing predecessor, broken reference, or cycle as unresolved. 2. Separate task closure, deliverable existence, and acceptance. For each required artifact, match its exact identity and version to the acceptance rule and a current check result. 3. Assess predecessors before the target. A predecessor is not ready merely because its successor or parent task is closed. 4. Classify each condition as `satisfied`, `failed`, or `unknown`, with an evidence reference and observation time. Do not turn absence of evidence into a pass. 5. Return a readiness map naming the first blocking predecessor, missing or failed artifact, and the next evidence needed. State `ready` only if every required predecessor and acceptance condition is satisfied at the cutoff. ## Completion check Another reviewer can trace every ready claim to the applicable plan, artifact version, and check. Closed ta