# Incident to Resolution Workflow

**Status:** Approved target-state baseline  
**Generic activation:** I8.

## Target State

```text
meaningful failure detected
  -> open/link Incident
  -> capture affected primitives + impact + evidence
  -> classify/triage
  -> known deterministic ResolutionRecipe?
       yes -> ResolutionAttempt -> verify
       no / failed -> Resolver agent within Policy
           -> diagnose
           -> mechanical action OR proposed code/config change
           -> if source/config product change:
                Task -> ChangeSet -> Review -> Verification -> normal delivery
  -> verify affected lifecycle/health
  -> resolve Incident
  -> optionally propose reviewed reusable ResolutionRecipe
```

## Detection / Deduplication

Failures with same root/resource/correlation may link to an open Incident rather than create spam. Incident identity is not just an alert fingerprint; it preserves lifecycle impact/timeline.

## Triage

Classify domain, severity, affected Project/Plan/Factory/CI/Deployment/Cluster, user impact, current safe state, retryability and authority needed.

## Deterministic Recipe

A recipe declares applicability predicates, required capabilities, steps, idempotency/reconciliation, expected evidence, rollback/cleanup and version. AWP verifies postcondition; successful command exit alone is insufficient.

## Agentic Resolver

Resolver receives structured context and least capabilities. It can propose improvements/recipes but cannot self-authorize privileged/destructive action. Source changes use normal code lifecycle.

## Learning / Reuse

A resolver-generated successful procedure may become a `ResolutionRecipe` only after review/verification and applicable scoping. Preserve provenance to Incident and ResolutionAttempt.

## Failure / Recovery

Each failed attempt remains visible. Control-plane restart resumes durable attempt. External provider outage can put Incident in waiting rather than continuously spawning resolver agents.

## Increment Realization

Earlier increments have domain-specific retries/failure states. I8 unifies generic Incident/Resolver/Recipe product. I9 may integrate external support/on-call/reliability policy.

## Acceptance

User can see what broke, what AWP tried, what changed, whether the fix is verified, and what reusable remedy was learned—without silent self-modifying scripts.