A trustworthy workflow makes each change in authority visible. Oneira can begin with a short request, but a consequential external action needs more structure than a pleasing animation. Intent, preview, confirmation, execution, receipt, and recovery should be distinct stages.
Translate intent into a concrete preview
Before acting, show the account, target, operation, important parameters, cost, and expected side effects. A preview should be specific enough that a person can spot the wrong recipient, date, quantity, permission, or file. Generic phrases such as complete the task are not meaningful confirmations.
Bind confirmation to the exact action
Approval should expire when the target or parameters change. The system should not reuse consent from an earlier request or allow the agent to rewrite the action after approval. High-impact operations may need a second factor or confirmation in the authoritative service rather than only on the companion.
Return a receipt and a recovery route
After execution, show whether the tool succeeded, failed, or is still pending, along with an external identifier when available. Provide the place to review, undo, cancel, or contact support. An expressive face can acknowledge the state, but it should not replace the factual receipt.
The short version
- Preview the exact target, action, cost, and side effects.
- Invalidate approval when the proposed action changes.
- Return a factual receipt and independent recovery path.