The blast radius
A single mistaken tool call can duplicate a wire, post to the wrong account, or bypass dual-control rules encoded in your policies but not in the model. Logs explain what happened after the funds moved; they do not substitute for a deterministic gate on the path to the exchange or core banking API.
The TrigGuard interlock
Each proposed movement is a request to a named execution surface (for example payments.wire or a broker FIX route). guard() or POST /execute evaluates policy and context, then returns PERMIT, DENY, or SILENCE with an Ed25519 receipt bound to a policy fingerprint. Only PERMIT authorizes handoff to the payment client. SILENCE under a fail-closed default means: do not call the money API.
- Regulatory and model-risk framing: map decisions to supervisory expectations (EU AI Act, DORA).
- System design: architecture and deployment modes.
NEXT
Long-form sector analysis: Banking & insurance. Full compliance mapping: /compliance.