skills/orchestrate-projects/references/orchestration-model.md

# Orchestration model

## Project state

- Objective and non-goals
- Deliverables and acceptance tests
- Confirmed facts, assumptions, unknowns
- Constraints, permissions, and approval gates
- Workstreams and dependencies
- Decisions and rationale
- Risks, mitigations, and owners
- Current status and next action

## Workstream card

| Field | Requirement |
|---|---|
| Outcome | Observable contribution to the project |
| Owner/capability | Role or available skill responsible |
| Inputs | Required context or artifacts |
| Output | Exact deliverable and format |
| Dependencies | What must exist first |
| Validation | How correctness is checked |
| Approval | Human decision required, if any |
| Failure path | Retry, fallback, handoff, or stop |

## Integration tests

- All outputs use the same confirmed assumptions and terminology.
- No specialist silently changes scope or exclusions.
- Dependencies are satisfied and artifact versions match.
- Contradictory recommendations have an explicit resolution.
- The combined result meets acceptance criteria, not merely workstream criteria.
- Remaining uncertainty and authority boundaries are visible.