A recommendation from one agent is input to a decision, not permission for another agent to act. Preserve separate states for suggested, approved, executing, and completed work across every handoff.
Recommendations and approvals have different authority
A recommendation expresses an analysis or preferred action. Approval records an authorised decision about a specific proposal. Execution performs the effect, and completion requires authoritative evidence that it occurred.
For a proposed contract, label result type explicitly and include proposal revision, evidence, uncertainty, and permitted next stage. The execution service verifies approval from trusted state rather than accepting a generated sentence saying “approved.”
Do not let a summariser collapse “recommended for review” into “ready to execute.” That wording change crosses a business authority boundary even if the proposed action itself remains identical.
Test a fictional compensation recommendation
A support agent suggests that a manager consider compensation after a reported missed visit. Another agent prepares the case packet. Neither may call a refund tool unless the current proposal receives the required authorised decision.
The manager approves a defined amount for one transaction. If a later agent changes the transaction reference or amount, the earlier approval must not carry forward automatically. Bind the decision to the exact consequential proposal.
| Cross-agent state | Permitted next step |
|---|---|
| Suggested action | Gather evidence or prepare review |
| Submitted proposal | Await the defined decision |
| Denied proposal | No proposed effect |
| Approved current revision | Continue to final execution checks |
| Completed effect | Report authoritative result, not merely approval |
Replay a fixture where the handoff text falsely claims approval but trusted state shows pending. The backend should refuse execution regardless of how persuasive the packet sounds.
Preserve uncertainty through review
Approval does not make unverified allegations true. Reviewers may authorise an action despite uncertainty under business policy, but the evidence record should preserve that distinction. Later reports should not rewrite the original facts as independently verified.
Separating these stages adds state and may slow the workflow. It also makes responsibility and recovery clearer. Use lighter control for low-impact suggestions while retaining strong boundaries for consequential writes, messages, money, and deletion.
This authority design is proposed. The voice integration case study establishes related workflow experience. Pair it with external approval queue design.
Recommendation versus action FAQ
Can one agent approve another agent’s proposal?
Only if the trusted business policy explicitly grants that capability for the defined scope.
Is the word “approved” in a handoff enough?
No. Resolve the decision through the authenticated approval record and current revision.
What proves the final action completed?
Use the authoritative operation result from the system responsible for the effect.