Skip to main content
Orchestration is the part that decides. A policy reads the data layer and writes a decision. Policies chain into a graph, so one policy’s output is the next one’s input. A decision is the record of what was chosen for one person and why. An action is the decision carried out — an email sent, a field written, a record pushed to your CRM. The payoff of writing it down this way is that every outcome is explainable after the fact. “Why did this person get this email?” has an answer you can read. Start with Policies, plans and motions for how the layers fit together.

​
Pages in this section

Being written. Each page below will land as its own file in this tree.
  • Policies — what a policy is, its declared inputs and outputs, and how gates work
  • Policy graph — how policies chain, and how to read the dataflow map
  • Decisions — the decision log: what was decided, for whom, and why
  • Actions — how a decision becomes something that actually happens
  • Plans — the state machine underneath a running motion

Data Layer

What policies read from — people, companies, activity and records.

Motions

The campaign layer that sits on top of plans and policies.
Questions? Reach out to support@allgoodhq.com.