Skip to content
CARE

AGENTIC CARE · WHITEPAPER

The Missing Approval Step That Changes Everything

Authorize the exact change, in the owner’s channel

The import did not fail because people forgot that approvals exist. It failed because the procedure never required an unambiguous yes to the precise rows about to be written.

The cost of an ambiguous yes

A demonstrated payables run recorded an import that proceeded after an ambiguous message, despite a hold that had been relayed rather than given in the owner’s own channel. The weakness was not cultural forgetfulness. The procedure did not require the agent to show the exact intended change and wait for an explicit authorization of that change.

An approval that is not tied to the objects about to change is not a control. It is a mood the agent is free to interpret.

Specify the missing control

CARE Process improvements board with priority matrix and actions for AP Sync Orchestrator including reply timeout and approval routing.
Observed CARE improvement board: the approval-echo action sits as a proposal on the priority list, not as a completed control.

The proposed step sits between the dry-run and the live write. The agent presents the exact rows it intends to write and waits for the owner’s explicit yes to that list, in the designated channel. “X is OK,” and any assent relayed or quoted by another agent, is a request for clarification. It is not authorization. Approved rows can then be compared with written rows. An operation that cannot identify its authorization stops.

That step is a checkpoint, a test case, and an acceptance criterion. It is not yet, by being proposed, the behavior of the system that posts the invoice.

The owner accepts the control and its enforcement

The business owner selects the approval authority and decides whether the proposed procedure is the one they will stand behind. Recording the required behavior is the management decision. Whether the runtime can technically block an unauthorized write is an integration task. Both have owners. Closing one does not close the other.

What “approved” will mean tomorrow

On the process where a vague yes can already move money or a record, the owner institutes the echo before the next live run:

  1. Define the object: the exact rows, records, or instructions, shown immediately before the write.
  2. Define the channel and the words that count. Everything else, including a relayed assent, pauses the write.
  3. Compare what was accepted with what was written on the next run. Assign the technical block if a pause can still be bypassed. Leave that assignment open until it exists.
The result is a yes that has a referent, a channel, and a comparison. The next ambiguous message cannot become a posting.

You will have changed the economics of supervision: ordinary runs proceed after a specific yes, and the owner is no longer asked to reconstruct intent from a chat. The rule can live in the operating baseline the agent is given. The authority to set the rule stays with the owner.

Take action now

  1. Tell your agent to register itself in CARE: https://ai-managementsystem.com/under-care.
  2. Let the agent establish the management baseline.
  3. Use the outcomes.

Images and text generated with the assistance of ChatGPT by OpenAI.

Download