# Plan to Production Workflow

**Status:** Approved target-state baseline  
**Realized progressively:** I1 through I6.

## Target State

This is the end-to-end software-delivery spine AWP owns.

```text
Project
  -> Planning / PlanRevision
  -> Task graph
  -> FactoryRun / AgentRun / Attempt
  -> ChangeSet
  -> Verification + Review
  -> trusted Merge
  -> Artifact
  -> Release
  -> Environment promotion
  -> Deployment
  -> health / rollback / Incident
```

Every transition has one authoritative AWP primitive, policy/gate owner and provider boundary.

## Stage Ownership

| Stage | AWP owns | Provider owns |
|---|---|---|
| Planning | intent/Decisions/readiness | planner model mechanics only |
| Factory | Task/Run identity/progression | Fabro graph execution |
| Agent | AgentRun/Attempt/provenance | agent protocol/model execution |
| Change | ChangeSet/fidelity | Git mechanics via ForgeProvider |
| Verification | evidence/gates | CI/check execution |
| Merge | policy/authority/result | forge merge mechanics |
| Artifact | digest/provenance | build/registry mechanics |
| Release | immutable release intent | tags/package publication mechanics |
| Deployment | environment progression/rollback policy | K8s apply/rollout mechanics |

## Core Invariants

- later stages never infer identity solely from provider object;
- source/candidate/artifact/release/deployment identities are exact and immutable where required;
- no coding/review/CI workload gains downstream publication/deployment authority;
- gate decisions consume admitted current evidence and policy;
- failures preserve upstream outputs so correction/retry does not restart unrelated work;
- every stage is observable and linked back to Project/Plan/Task.

## Increment Realization

```text
I1  Project -> Plan -> Task -> Factory -> Agent -> ChangeSet -> Review -> Merge
I2  rich Planning + delivery/execution recommendation
I3  generic policy/Decision/Approval
I4  Factory observability depth
I5  full verification/CI
I6  Artifact -> Release -> Environment -> Deployment
```

I7–I9 deepen infrastructure/resolution/productization but do not replace the lifecycle spine.

## Failure / Recovery

Failures route to the owning stage: execution retry/checkpoint, change correction, verification/CI resolution, deployment rollback, or Incident/Resolver. Upstream accepted artifacts/evidence are reused until invalidated.

## Acceptance

A user can traverse breadcrumbs from any final outcome back through Deployment/Release/ChangeSet/AgentRun/Task/Plan/Project and understand why progression happened or stopped.