R

Regulatory Intelligence

Continuous compliance monitoring

1 active Sev-1
AR

Advisory mode

During the pilot, all compliance events require human validation. Legal approval is required to mark an event as resolved or risk accepted.

HIGHCE-0003OPENConfidence HIGH

AI Model Card Out of Date: Credit Scoring

Open response workspace

Days Open

9d

Customers

22,100

Exposure

$5.8M

Business Unit

Consumer Credit

SLA

Ack 240m · Resolve 7d

What Changed

Model v3.4 deployed without updating adverse action notice template

Affected Asset

Last changed 2026-04-20 by ML Platform

What Broke

Regulation

Equal Credit Opportunity Act: AI Model Card Supplement 2025

Section

ECOA-AI-2025 Appendix A

Obligations breached

Owner

AI Risk Specialist / Consumer Credit Compliance

1 SLA breach(es) active

Business Unit

Consumer Credit

Risk score: 87

Remediation Actions (0/5)

System Actions

Compliance event created

6/1/2026, 10:49:24 PM

Draft resolution package generated

6/1/2026, 10:49:24 PM

SLA started

Ack 240m, resolve 7d

Owner notified (Slack and email)

6/1/2026, 10:49:24 PM

Task created in system of record

Simulated ServiceNow or OneTrust ticket

Post-resolution baseline updated

Not applicable

Acknowledgment status

Overdue

Draft Resolution Package

What broke and why

ECOA-AI-2025 Appendix A obligation may no longer be satisfied.

This event was generated because a monitored enterprise asset changed after validation. The obligation-to-asset relationship must be revalidated and evidenced.

Draft compliant version

Draft remediation: restore the last validated compliant state, route for legal review if required, then attach updated evidence and record approvals.

Draft only. Human review and legal sign-off required.

Evidence Checklist

Audit Trail

1.

Compliance Event created: Drift detected

System · 6/1/2026, 10:49:24 PM

2.

Draft resolution package generated

System · 6/1/2026, 10:49:24 PM

3.

SLA countdown started

System · 6/1/2026, 10:49:24 PM

4.

Notifications sent (Slack + email simulated)

System · 6/1/2026, 10:49:24 PM

5.

Ticket created in system of record (simulated)

System · 6/1/2026, 10:49:24 PM

Enforcement Context