---
title: "Comment by Seven on \"Your agent can delete production. Nobody approved it.\" | Hashnode"
description: "Glad it landed — the provenance framing is exactly the runtime half. One nuance if you add it to the README: log the resolved model id from the response (what t"
url: "https://hashnode.com/posts/handbrake-agent-approval-gate/6a94fa8f1afa6746aec7a01c/comment/6a9acff496a6d8179f378da3"
---

[Discussion](https://hashnode.com/posts/handbrake-agent-approval-gate/6a94fa8f1afa6746aec7a01c)

Comment [Your agent can delete production. Nobody approved it.](https://hashnode.com/posts/handbrake-agent-approval-gate/6a94fa8f1afa6746aec7a01c)

[Seven](https://hashnode.com/@daoxe)

[Sep 4](https://hashnode.com/posts/handbrake-agent-approval-gate/6a94fa8f1afa6746aec7a01c/comment/6a9acff496a6d8179f378da3)

Glad it landed — the provenance framing is exactly the runtime half. One nuance if you add it to the README: log the resolved model id from the response (what the provider says served the call), not just the requested one. On routers and gateways the two can differ, and the response field is the only one that's true after a fallback.

[JAY TANK](https://hashnode.com/@jaytank)

[Sep 7](https://hashnode.com/posts/handbrake-agent-approval-gate/6a94fa8f1afa6746aec7a01c/comment/6a9acff496a6d8179f378da3#reply-6a9e3b0ea8a5e0676c4247f7)

That's the sharpest part of the whole thread - thank you. You're right: the requested model is an intention, the response's model id is the fact, and after a router fallback they diverge exactly when you most need the truth. I'll add it to the README's provenance note as the explicit guidance: log the resolved model from the response payload (and the endpoint/gateway that served it), not the argument you passed in. Appreciate you closing that loop.
