Assess whether monitoring detects drift or only outages (e3139c)

SITUATION A bank running three models on the same credit file cannot treat drift in a protected class the dashboard does not show as incidental context on reconciliation policy when two models split on materiality. Model-deprecation manager must close monitoring detects drift or from that extract under AI Governance Layer / Lifecycle and Accountability.

DECISION Model-deprecation manager in a bank running three models on the same credit file must choose Monitoring detects drift / Only outages using reconciliation policy when two models split on materiality after drift in a protected class the dashboard does not show.

HYPOTHESES TO TEST 1. Model-deprecation manager can defend Monitoring detects drift from reconciliation policy when two models split on materiality after drift in a protected class the dashboard does not show in a AI Governance Layer challenge. 2. Model-deprecation manager cannot defend Monitoring detects drift from reconciliation policy when two models split on materiality; Only outages is what the extract actually supports after drift in a protected class the dashboard does not show. 3. Drift in a protected class the dashboard does not show never reached the population in reconciliation policy when two models split on materiality — reopen intake, do not close monitoring detects drift or. 4. Two facts in reconciliation policy when two models split on materiality after drift in a protected class the dashboard does not show conflict for model-deprecation manager; hold this Lifecycle and Accountability file.

ANALYSIS REQUIRED 1. Map the control-plane score in reconciliation policy when two models split on materiality to the policy gate model-deprecation manager can enforce. 2. Name the override that would let monitoring detects drift or proceed without a silent bypass. 3. Test whether drift in a protected class the dashboard does not show changed routing, logging, or human-in-the-loop on the live agent path. 4. For this AI Governance Layer Lifecycle and Accountability file, read reconciliation policy when two models split on materiality against drift in a protected class the dashboard does not show 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 (reconciliation policy when two models split on materiality after drift in a protected class the dashboard does not show). The follow-on Lifecycle and Accountability action is what model-deprecation manager does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line AI Governance Layer option on monitoring detects drift or, then the evidence in reconciliation policy when two models split on materiality, then the action for model-deprecation manager - Hypothesis scorecard against reconciliation policy when two models split on materiality: supported / rejected / untestable - Named option among Monitoring detects drift, Only outages and the fact that kills the others - Owner and next date for model-deprecation manager in a bank running three models on the same credit file