Phronesis detects doctrine drift before it becomes regulatory exposure.
Phronesis monitors execution against encoded doctrine continuously — not only when an incident is declared. 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. CROS 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 — identified across your operational record, invisible to any individual or team reviewing data manually.
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.
Because every CROS client instantiates the same ontological framework, operational data is structurally comparable. CROS can benchmark CAPA closure rates, near-miss frequency, and notification window compliance across the entire client base.
Every new client added increases the resolution of the benchmark for every existing client. This is structurally unavailable to any system that negotiated bespoke schemas.