◆ Supervised Router
Watches incidents, GL adjustments, customer complaints and reconciliation breaks for the signature of an operational loss, captures it, maps it to the Basel event category, and links it to the failed control. Books the event into the loss database directly from the source feeds.
Memory
Working The candidate loss event and its supporting evidence.
Episodic Prior loss events and their final categorisation.
Semantic The Basel event-type taxonomy and loss-data standards.
Store Loss-event warehouse + control-mapping graph
Orchestration
router-fanout MCP
Harness · Managed Agents … event-driven, always-on across incident and finance feeds.
Tools
{ } Incident management API { } General-ledger adjustments feed API { } Complaints + reconciliation breaks API { } Loss database API
Evals & guardrails
- Captured events vs. an audited loss-reconciliation gold set; under-capture is a finding.
- Material losses above a threshold route to the op-risk oversight agent for confirmation before booking.
- Immutable capture trail for internal audit and regulatory exam.
Frontier edge
- ▲Causal linkage: reasons backward from a GL adjustment or reconciliation break to the failed control that caused it, not just the symptom in the feed.
- ▲Continual learning: each reviewer-confirmed categorisation feeds an eval-gated update, so the long tail of ambiguous Basel mappings keeps shrinking.
- ▲Confidential compute: scans complaint and incident text inside a secure enclave so customer PII never sits in clear while losses are detected.
In numbers
~98%
Detectable loss events captured
< 5 min
Avg. capture latency
Handoffs
Fed by ← RCSA Facilitation Agent
Across ⇢ Operations & Technology (incident source)