Export the reason, not just the verdict
Anomaly provenance should preserve threshold breach, counterparty drift, unusual velocity or behavioral change as part of the packet.
NORNRKeep anomaly context in exported proof and finance packets.NORNR / Anomaly provenance
Depth packageKeep anomaly context in exported packets instead of stripping it away at close.
An anomaly status alone is not enough. Exports should preserve what triggered review, which counterparty or behavior changed, and whether the lane still needs tighter posture later.
Approval and anomaly context stay on the same record
The packet should show what the reviewer saw at decision time, not a flattened after-the-fact summary.
Anomaly provenance should inform the next policy move
The export becomes more valuable when it tells finance, ops or risk what still needs tightening later.