State law · SB 24-205 · 11 duties · from 30 June 2026
A protected attribute your system never receives is a factor it cannot decide on. Anything else is testing after the fact.
Provenant does it. You can show it before your agent runs.
Where the standard asks you for a plan, a policy or a test, Provenant hands you what it needs.
| Ref | Requirement | How | Mechanism |
|---|---|---|---|
| §1702(1) | Documentation of capabilities, limitations and intended uses | Evidenced | The system description is written for you |
| §1702(2) | Results of bias testing | N/A | |
| §1702(3) | Information deployers need for impact assessments | Evidenced | You start from a complete picture of what the system does and sees |
| §1702(4) | Public statement on high-risk systems and risk management | Evidenced | Written for you |
| §1702(5) | Report discrimination risk to deployers and the Attorney General | Evidenced | The record shows what happened and when |
| §1703(1) | Risk-management policy and reasonable care | Enforced | You choose what data reaches the system |
| §1703(2) | Impact assessment before deployment and annually | Evidenced | The same picture, per deployment |
| §1703(3) | Pre-decision and post-decision consumer notices | Evidenced | You can tell a consumer what the system considered |
| §1703(4) | Opportunity to contest an adverse decision | Evidenced | You can show which values a decision was made from |
| §1703(5) | Notify the Attorney General within 90 days | Evidenced | The record shows what happened and when |
| §1703(6) | Retain records for three years after last deployment | Enforced | Produced by running, kept automatically |