Daily Digest
Reuse the same key when a tool retries
Reuse one request ID on retries so payments and deploys run once.
The technique
Agents that retry payments, posts, or deploys after a timeout often mint a new key each try. That creates duplicate side effects. A gate that requires a stable key per logical order blocks release when retries would double-charge.
How it was tested
Offline structural sim (no live model): 5 drop_ack charge episodes. Stable keys: 0 I1 violations (one charge each). Fresh UUID keys: 5 of 5 double-charges; gate blocked release on that pattern.