Part 7 of 12 · 1 min read
How to build it so it holds up
- Keep signing keys and nonce storage outside the agent, in a service the model cannot call arbitrarily.
- Bind everything: action, canonical arguments, session, requester, approver, expiry, nonce, and the state version where it matters.
- Single use, short expiry (minutes, not days).
- Requester not equal to approver; two distinct approvers for high risk or high value.
- Render from the arguments: never show model-written summaries as the authority; escape control characters; call out new recipients, unexpected fields, lookalike domains, and large or irreversible effects.
- State the impact plainly (amount, recipient, whether it can be undone).
- Re-verify state at execution and deny if it changed.
- Log every issue, use and denial with the trace id (Level 9 module 8).
- Prefer asymmetric signatures or a separate approval service so the executor cannot mint approvals.
- Keep the approval rate meaningful: if nearly everything is approved, the gate is over-flagging (Level 8 module 8).