Approve
The action runs exactly as proposed. Fast for the routine cases.
Platform
No approval, no action. When an agent wants to change a record, it proposes and a named person decides. Everyone says human in the loop. Spine makes it the rule the runtime enforces.
How a gate works
Writes and escalations queue as proposed actions. Nothing reaches the system of record until someone accountable says yes.
The agent drafts the write, such as a payment plan or a fee waiver. Then it stops.
Guardrails and contact rules run on the proposal before a person ever sees it.
A named approver picks one of four choices and gives a reason.
Only an approved action runs. The decision, who made it and why go on the ledger.
Four choices
Real supervisors fix things, step in and escalate. The gate gives them all four moves and keeps a reason for each.
The action runs exactly as proposed. Fast for the routine cases.
Change the amount or terms, then approve. The change and the reason are recorded.
A person takes the case from the agent and finishes it by hand.
Stop the action and send it up with a reason, such as an open dispute.
Built for real operations
The proposer never decides. Only people with an approver role can decide and each decision carries their verified identity.
Clear a queue of routine items in one go. Each item still runs through the same checks and gets its own ledger entry.
If a check cannot run, for example a rule service times out, the action does not go ahead. Silence is never a yes.
Why it matters to you
Questions
Pick one action your team worries about. We will show it proposed, checked, decided and recorded.