An orchestration pattern is a work schema
A pattern defines roles, transferred artifacts, responsibility boundaries, verification criteria, and completion conditions. The role may be performed by the main session, a subagent, a fresh session, or a person; the process logic matters more than the label.
A durable workflow can be described as role → artifact → check.
| Pattern | Use when | First artifact |
|---|---|---|
| Planner → Executor → Verifier | The task is understood and needs implementation plus control | PLAN.md |
| Researcher → Implementer → Reviewer | An unfamiliar system needs discovery first | CODEBASE_NOTE.md |
| Reproducer → Fixer → Regression reviewer | A defect needs causal evidence | EVIDENCE_LOG.md |
| Parallel researchers → Synthesizer | Independent questions can be explored concurrently | RESEARCH_DIGEST.md |
Choose the pattern by risk
- Name the decision the workflow must support.
- Split discovery, implementation, and verification.
- Assign one owner to each artifact.
- Define how contradictions return to the owner.
- Set a stop condition before the next handoff.
- Review the final diff and evidence independently.
Handoff contract
Input: <artifact and scope>
Owner: <role>
Output: <artifact or report>
Evidence: <file, command, test, or observation>
Unknowns: <explicit list>
Stop: <condition>
Next owner: <role>Canonical lesson source · JavaRush
Open JavaRush material