Assess whether monitoring detects drift or only outages (24a682)

SITUATION After two production models recommending opposite actions on the same file, committee charter that does not define escalation is what model-deprecation manager can touch in a bank running three models on the same credit file. AI Governance Layer will live with Monitoring detects drift versus Only outages on this Lifecycle and Accountability file.

DECISION Model-deprecation manager in a bank running three models on the same credit file must choose Monitoring detects drift / Only outages using committee charter that does not define escalation after two production models recommending opposite actions on the same file.

HYPOTHESES TO TEST 1. The population in committee charter that does not define escalation is the one two production models recommending opposite actions on the same file named, so Monitoring detects drift follows for this Lifecycle and Accountability file. 2. The population in committee charter that does not define escalation is adjacent only to two production models recommending opposite actions on the same file; Only outages is the honest AI Governance Layer call. 3. A bank running three models on the same credit file already contained two production models recommending opposite actions on the same file before committee charter that does not define escalation arrived; no new Lifecycle and Accountability path. 4. Provenance on committee charter that does not define escalation after two production models recommending opposite actions on the same file is broken; do not pick Monitoring detects drift or Only outages yet.

ANALYSIS REQUIRED 1. Confirm the inventory line still matches the running configuration in a bank running three models on the same credit file. 2. Map the control-plane score in committee charter that does not define escalation to the policy gate model-deprecation manager can enforce. 3. Name the override that would let monitoring detects drift or proceed without a silent bypass. 4. For this AI Governance Layer Lifecycle and Accountability file, read committee charter that does not define escalation against two production models recommending opposite actions on the same file and write the one fact that would move monitoring detects drift or for model-deprecation manager.

RECOMMENDATION Choose Monitoring detects drift / Only outages on this AI Governance Layer / Lifecycle and Accountability packet (committee charter that does not define escalation after two production models recommending opposite actions on the same file). If committee charter that does not define escalation cannot force a AI Governance Layer label under Lifecycle and Accountability, stop. If committee charter that does not define escalation after two production models recommending opposite actions on the same file cannot support Monitoring detects drift versus Only outages on this AI Governance Layer Lifecycle and Accountability close, model-deprecation manager must leave the classification unresolved and name the missing control or provenance fact.