Approval policy
Approval boundary policy
OperatorLoop is built to move routine post-checkout work faster without hiding the edge where human approval is still required.
Actions that may run automatically
- Queueing paid orders into the workflow.
- Chasing missing client inputs inside the agreed template and cadence.
- Normalizing scope into a work packet for delivery.
- Writing status changes and review notes into the agreed systems.
Actions that pause for approval
- Refunds, credits, payment changes, or anything that changes money movement.
- Public or customer-facing promises outside the approved script.
- Spending decisions, vendor actions, or tool purchases.
- Legal-sensitive, destructive, identity-shaping, or otherwise irreversible actions.
Exceptions and rollback
When the workflow hits an unclear edge case, OperatorLoop should pause, surface the exception, and preserve the written trail.
Rollback and correction paths are part of the operating model for the bounded workflow in scope.
Scope-specific overrides
The final approval matrix is agreed in writing for each client workflow. This page is the public baseline, not a substitute for client-specific scope.