Approvals
An approval authorizes an exact effect within a run. It identifies the operation, destination, material inputs, acting account, and applicable policy. The approval belongs with the run and the proposal the person reviewed.
Bind approval to the reviewed effect
Section titled “Bind approval to the reviewed effect”Proposal fields
Section titled “Proposal fields”For a protected action, the draft requires the proposal to identify the run and step, operation, target, material inputs, acting account and applicable policy, with rehearsal evidence when available. Show those values to the assigned approver. An approval to send covers the reviewed sender, recipient, subject and body. A later edit changes what would be sent and requires a new decision.
Example approval sequence
Section titled “Example approval sequence”Propose draft → show exact sender, recipient and message → wait for approver → compare approved details with dispatch request → consume approval → dispatch → record result or reconcile uncertaintyDecide whether to dispatch
Section titled “Decide whether to dispatch”| Condition | Runtime behavior |
|---|---|
| Matching proposal and current grant | Dispatch the reviewed effect within its policy |
| Rejection or expiry | Hold the action and record the decision |
| Input, target, account, or required rehearsal changed | Present an updated proposal for review |
| Dispatch outcome uncertain | Reconcile the existing attempt before allowing a retry |
The behavior above is the draft contract. In Studio, a reason or read step marked requiresApproval can ask for a decision. Connector write and process operations have their own exact-effect gate. Where a shared publication needs a human decision, add an explicit review step and configure the destination’s grant and field allow-list.
See human review, rehearsal, and the exact-effect contract.