Why a prompt is not an approval

Prompts are useful for communicating intent to a model. They do not establish that every returned result satisfies policy, or that a proposed tool call has authority to execute.

Separate the intended action, the approved rule and the control that can stop execution. Then record the result. The model can help prepare the work without being the sole judge of whether it may proceed.

A translation workflow makes the distinction concrete: ask for approved terminology, check the returned candidate independently, and withhold release when mandatory checks or human approval remain unresolved.