A team implemented an approval step for high-value contract amendments: the agent drafts the amendment and a manager approves it in a review UI. Later, an incident shows the agent sent an amendment with a changed payment term after approval had been granted on an earlier draft. What design flaw does this reveal?

Answer: A — Approval wasn't bound to the exact version, so the executor could send altered content

An enforced gate ties the approval record to the exact parameters or content version, and the executor refuses anything that doesn't match. (b) relies on the prompt to uphold a control. (c) may be a real capacity issue, but it didn't cause content to change after approval. (d) explains why drafts vary, not why an unapproved version could be sent.