Template: Choreography

Template for the choreography document produced by the Project Decomposition workflow. Placed in the project directory root. Describes the execution sequence, artifact dependencies, and hand-off protocol between runs.

---
title: "Choreography"
tags: [roadmap, plan]
domain: roadmap
maturity: published
author: "Arda Systems"
---

# Choreography: <Project Name>

## Execution Sequence

| Order | Run | Directory | Trigger | Estimated Duration |
|-------|-----|-----------|---------|-------------------|
| 1 | Run 1: <name> | run-1-<name>/ | Manual | ... |
| 2 | Run 2: <name> | run-2-<name>/ | After Run 1 exit gate passes | ... |

## Artifact Dependency Map

| Artifact | Produced By | Consumed By | Path | Format |
|----------|------------|-------------|------|--------|

## Hand-Off Protocol

All hand-offs are **filesystem-only** — no in-memory state is shared between runs.
Each run reads its inputs from files produced by prior runs and writes its
outputs to files for subsequent runs.

### Between Run N and Run N+1

1. Run N completes and its `validate-exit.sh` passes.
2. The team lead verifies the exit gate output.
3. Run N+1's entry criteria are checked (which reference Run N's output files).
4. Run N+1 is launched.

## Recovery Procedures

### Run N fails mid-execution
<Steps to diagnose, fix, and retry. How to identify which tasks completed.>

### Run N exit gate fails
<Steps to diagnose which criteria failed, fix the issues, and re-validate.>

### Run N+1 entry criteria fail
<Steps to return to Run N and address the missing prerequisites.>

## Launch Commands

| Run | Command |
|-----|---------|
| 1 | `/launch-team <project-dir>/run-1-<name>` |
| 2 | `/launch-team <project-dir>/run-2-<name>` |