Phronesis detects doctrine drift before it becomes regulatory exposure.
The gap between how your procedures say things should run and how they actually do is where regulatory exposure accumulates silently, long before any declared event. Phronesis surfaces it before it becomes a liability.
A Doctrine Delta finding is what Phronesis surfaces when it detects drift between doctrine and execution. It is not an incident. It is a pattern — one no individual or team reviewing data manually would surface.
Doctrine Delta findings carry a confidence label of Inferred. They have not yet passed through the human review gate. The system never presents inference as fact.
Promote a Doctrine Delta finding to a Metron record and it becomes governed: Confirmed, named owner, timeline, audit trail, closeable. This is the architectural boundary between Phronesis and Metron — the moment inference becomes accountability.
The intelligence CROS accumulates across its client base is structurally comparable — not averaged or generalized. Every client added increases the resolution of the benchmark for every existing client. This is unavailable to any system that solved the problem differently.