# Stage 10: Postmortem

## Purpose

Board reviews the completed run. Learns from it. Feeds back into future runs.

## Input

- Memos from all stages (Board, ADR, specs, task breakdown, review reports, test results, deploy record)
- Original brief and PRD

## Composition — STATIC (same as Board)

| Role | Model  |
| ---- | ------ |
| CEO  | Opus   |
| CTO  | Opus   |
| CFO  | Sonnet |
| COO  | Sonnet |

## Process

1. Compile run summary from all stage memos
2. Board reviews for:
   - Conflicts between stage outputs
   - Scope drift from original brief
   - Cost/timeline variance from estimates (estimated rounds vs actual)
   - Quality of planning (did Review catch things Planning should have caught?)
   - Strategic alignment (did we build the right thing?)
3. Board produces postmortem memo:
   - What went well
   - What went wrong
   - What to change for next run
   - Specialist memory updates (lessons learned per domain)
4. Specialist memory is updated with relevant lessons

## Output

- Postmortem memo
- Specialist memory updates
- Orchestrator heuristic updates (e.g., "tasks of type X consistently underestimated by 40%")

## Gate

No gate — this is the terminal state. Pipeline run is complete.
