# PAG · Orchestration

> Orchestration is the part of a document that says how work is ordered and where it runs in parallel, and the grammar does not let that be implied.

Canonical: https://banes-lab.com/pag/orchestration
Page as Markdown: https://banes-lab.com/pag/orchestration.md
Page as JSON: https://banes-lab.com/json/pag/orchestration
This index as JSON: https://banes-lab.com/json/api/pages/pag/orchestration

## Entries

- [Orchestration as declared structure](https://banes-lab.com/pag/orchestration/declared-structure.md): Orchestration is the part of a document that says how work is ordered and where it runs in parallel, and the grammar does not let that be implied.
- [Composing a collaboration](https://banes-lab.com/pag/orchestration/composing-a-workflow.md): This section covers how a collaboration is put together from parties, as shown in parties over a partition].
- [Shared surfaces](https://banes-lab.com/pag/orchestration/shared-surfaces.md): When more than one party writes to one tree, the surfaces they share are shared mutable state.
- [Phase binding](https://banes-lab.com/pag/orchestration/phase-binding.md): This section covers how a run is bound to one of two kinds before it touches anything, as derived in agents as executed contracts and shown in [two kinds].
- [Handoff signals](https://banes-lab.com/pag/orchestration/handoff-signals.md): A handoff is an item addressed to the parties that need it, with an allocated id, a declared kind and a closure the kind selects, as written in [an item] and…
- [Orchestration invariants](https://banes-lab.com/pag/orchestration/orchestration-invariants.md): A collaboration relies on invariants, and what each invariant has to carry is described in stating an invariant: the property in a form that could be false, the…