gate-recovery-and-resume

To resume a workflow after an MCP timeout or Copilot failure, re-validate partial artifacts and re-invoke agents with preserved context to overwrite incomplete outputs and securely continue gate work.

Recovering partial artifacts from a stalled gate progression involves tagging artifact status to prevent unintended advancement, followed by strict artifact handling to evaluate if recovery rules allow the workflow to safely resume.

You should escalate a mid-gate failure to the Product Owner when recovery cannot proceed due to strict artifact validation failures, or when policy explicitly blocks gate progression and requires human intervention.

Gate recovery workflows apply specifically to Gate 3 and above, targeting mid-gate failures and resume scenarios that require strict artifact handling and prerequisite validation before continuing.

Gate recovery requires strict artifact handling to prevent unintended progression by validating partial artifacts, ensuring that incomplete outputs are safely overwritten and do not compromise the workflow state.