NGT Exception Framework
Run controls, generate events, and surface investigation reports. The framework that sits between a detected anomaly and the analyst who resolves it.
The NGT Exception Framework runs the controls, generates the events, and does the work between the event and the person. It is designed around one constraint: detection is cheap, but analyst attention is finite.
How it works
A control runs. When its trigger condition is met, it generates an event: the smallest unit in the system. Events accumulate and are correlated with contextual signals (subscriptions, redemptions, corporate actions, large market moves) until they form an investigation report: the thing an analyst is actually asked to open.
Two axes govern the path from event to report:
- Axis 1: trigger methodology. Controls use statistical time series methods rather than fixed thresholds, so each event that fires is more likely to reflect a real anomaly.
- Axis 2: contextual events. High event volume is a feature. Contextual events explain anomalies before anyone looks at them, because they record what changed about the normal baseline that day.
Pattern recognition
A case is a pattern. The framework compares that pattern against the history of the same vehicle (has this configuration occurred before, and what did it resolve to?) and across the universe of other vehicles at the same point in time (is this signature appearing on twenty funds simultaneously, pointing to an upstream cause?).
Similarity search across history and across the universe requires your data. No general model has the comparison set.
Agent access
The Exception Framework is an NGT Tool, callable by agents through MCP and APIs. An agent investigating a NAV movement starts where an experienced analyst would: with a case that already has correlated events, a proposed root cause, and comparable situations attached. From there it can check dozens of hypotheses across every case, not just the ones someone had time for.
Agents write back into the framework: enrich the case, record the root cause and evidence, attach precedents, draft the client communication, open the workflow, assign the owner.
Agents own progress. People own decisions.
Further reading
The full methodology is covered in the NGT insights article: NGT Tools: The Exception Framework.