gap-analysislisted

# Gap Analysis ## Purpose Identify exactly what prevents the current Artifact graph from satisfying the user's target. ## Trigger Run after Project Intake, when a target changes, after Change Impact, on resume with repository drift, or when a Gate exposes missing evidence. ## Inputs - Target Artifact or Target Stage and its Definition of Done. - Artifact Inventory, dependency graph, validation records, and current State. - Existing Asset evidence, Project Constraints, Workflow Level, and accepted assumptions/decisions. ## Prerequisites - Normalize the target and stop boundary. - Validate target-relevant existing Artifacts enough to distinguish presence from usability. ## Procedure 1. Start at the target and enumerate only dependencies required for its declared scope and risk. 2. Walk the Artifact dependency graph backward to source evidence. 3. For each required node, compare required revision/quality with current status and evidence. 4. Classify gaps as `MISSING`, `PARTIAL`, `UNVERIFIED`, `STALE`, `INVALID`, incompatible, or blocked by clarification. 5. Explain why each gap blocks or weakens the target and which downstream nodes it affects. 6. Recognize alternative evidence or reusable assets that may satisfy the dependency. 7. Separate required gaps from optional improvements and later-stage work. 8. Record ready gaps whose upstream dependencies are already satisfied. ## Decision Rules - A `VALID` and sufficient Artifact is not a gap. - `PARTIAL` is a gap only f