Fulfilment SOP.

For each of the eighteen recurring fulfilment situations, the standard action, the data to read and how far an agent may act before a human decides.

You bring:

• the trigger that fired
• the task board and the Slack thread it concerns

The steps, in order. The method itself is served whole through the connector, current on every use.

1. 1

   Find the SOP for the trigger

2. 2

   Read the data it names

3. 3

   Act up to its autonomy rung

4. 4

   Hand the rest to the named approver

• Client, people, money or scope actions without approval
• Regenerating the analysis it was distilled from

Standing reference for the 18 recurring fulfilment SOPs (R1–R18) — trigger, action, data read, and autonomy rung for each — governing how far an ops agent may act before a human must approve. Use when a fulfilment trigger fires: a launch request, a task-tracker mismatch, a handoff, a capacity warning, or a tooling failure.