The Agentic Bank

Limit Breach Monitor

⬡ Redline Watches every trading and risk limit in real time and triages breaches.
◆ Always-on Monitor

Sits across the desks and watches VaR, sensitivity, notional and concentration limits as they move intraday. On a breach it pulls the contributing positions, attributes the cause, and hands the desk-head agent a breach packet with the driver already identified.

Memory

Working Live limit utilisations and the positions driving the nearest limits.
Episodic Prior breaches on the desk and how they were resolved.
Semantic The limit framework, escalation matrix, and risk-appetite thresholds.
Store Time-series limit store + breach-event log

Orchestration

router-fanout MCPA2A

Harness · Managed Agents … always-on, low-latency loop; context editing clears stale position snapshots on long intraday sessions.

Tools

{ } Risk engine (VaR / sensitivities) API { } Limit framework API ›_ Position attribution Code exec Desk-head agent escalation A2A

Evals & guardrails

  • Zero missed breaches vs. the official end-of-day batch … any miss is a Sev-1.
  • Breach packets sampled by agent-as-judge for attribution accuracy.
  • Immutable breach ledger for regulatory and internal-audit review.
  • The agent never re-sizes a position … it monitors and escalates only.

Frontier edge

  • Formal action-gating: the monitor/escalate-only boundary is enforced in policy, so it provably cannot touch a position; every escalation is cryptographically signed and replayable.
  • Edge inference on the intraday tick stream detects a breach in milliseconds without round-tripping to a central model.
  • Anticipatory: projects utilisation forward on the live curve and warns a desk it is minutes from a limit, not just after it trips.

A sample run

Trigger Rates desk VaR limit utilisation crosses 100% intraday after a curve move.
  1. 1Snapshot the contributing positions; attribute the VaR increase by risk factor.
  2. 2Check whether it's a genuine breach or a transient mark.
  3. 3Pull the desk's prior breaches and the escalation matrix.
  4. 4Assemble a breach packet with the driver and recommended escalation tier.
Output Escalates to the desk-head agent and the market-risk oversight agent with the breach cause (2y rates steepening) pre-attributed and logged immutably.

In numbers

100%
Limits monitored intraday
< 5s
Avg. breach detection
same-day vs. T+1
Breach explanation lead time

Handoffs

Across ⇢ Markets … trading desk-head agents (breach escalation)

More on the Market Risk desk