Agent Action Proof — Verify MCP Writes

Illustrative output only; no task provider was contacted.

Target: task T-42 in workspace North. Requested postcondition: status equals Ready. Preflight: confirm the account and task identity from an authoritative read, inspect the current update-tool schema, and record the task's current status and revision. If the status is already Ready, report “already satisfied” and do not write. Otherwise make one authorized update and retain the provider's request ID.

The completion receipt should include the write response, the exact readback source and time, and the observed status. If the readback proves T-42 is Ready, label the action completed. If a documented operation result conclusively says no change took effect, label it not completed. If the call timed out and the readback could be stale, label outcome unknown and name the next safe check. Do not issue a second update merely because the first response is missing. A retry is allowed only after verified idempotency or conclusive no-effect evidence, within the original authorization. This sample demonstrates the decision format; it is not evidence that T-42 or a provider exists.