Report

System Delta's controls are largely verified. Override recording does not match the documented procedure.

5 claims were examined against 96 evidence items. 3 are verified, 1 are contradicted and 1 remain unresolved. 2 require human review.

Claims

5

Verified

3

Contradicted

1

Unresolved

1

• CLM-201

  The underwriting model in production matches the approved release.

  Change management record · 2 supporting, 0 contradicting
  Verified
• CLM-202

  Model drift is monitored weekly with alert thresholds.

  Model risk policy · 1 supporting, 0 contradicting
  Verified
• CLM-205

  Manual fallback activates within five minutes of model failure.

  Continuity plan · 1 supporting, 0 contradicting
  Verified

• CLM-203

  Staff overrides are recorded with a reason code.

  Operating procedure · 0 supporting, 1 contradicting
  Contradicted

• CLM-204

  Input features exclude protected attributes.

  Model card · 1 supporting, 0 contradicting
  Partially verified

• 01Why do 31% of overrides carry no reason code?
• 02Which proxy variables could stand in for protected attributes?

• EV-0204Feature schema export. Integrity check pending.

• CLM-203Explain the evidence that contradicts: “Staff overrides are recorded with a reason code.”

Recommended once the organization authorizes access.

• Enforcement of reason codes in the override workflow
• Feature lineage for proxy variables

• CLM-203

  Staff overrides are recorded with a reason code.

  S. Marlowe
  In review
• CLM-204

  Input features exclude protected attributes.

  A. Okafor
  In review

• EV-0201Release manifest and approval record30fdefaa0f…Intact
• EV-0202Drift monitor alert history69ba8e640e…Intact
• EV-0203Override event log57bc86266b…Intact
• EV-0204Feature schema export38bcc4046a…Pending

Showing 4 of 96 items. The full appendix is included in the exported report.