Suggestions and actions carry different responsibilities
A model can summarize a purchasing request and recommend a supplier. Committing an order also involves budget, supplier status, approval authority and duplicate execution. Answer quality cannot replace those boundaries.
Four server responsibilities
- Verify the caller's access to the affected data.
- Validate input against current state.
- Bind required approval to the exact target version.
- Persist the execution result and make it inspectable.
Do not hide uncertainty
A tool timeout does not prove that a change failed. Use an execution identity and persisted result to determine its state. Repeating a request with an unknown outcome can duplicate an order or a message.
Different work needs different autonomy
Retrieval, drafting and approved execution are separate levels. Teams should see which level is active in both the interface and the record. Validate execution conditions and interruption behavior before connecting to production systems.