Defense · Colorado AI Act
Colorado AI Act for defense AI workflows
Colorado AI Act in defense AI workflows: what compliance requires, who asks for evidence, and the records to keep.
01 / The rule
What Colorado AI Act requires
Developers and deployers of automated decision-making technology that materially influences consequential decisions about Colorado consumers in education, employment, housing, lending, insurance, health care or government services.
- 01Developers: give deployers documentation on intended uses, training-data categories, known limitations, and instructions for appropriate use and human review.
- 02Developers: notify deployers of material updates or modifications to covered ADMT.
- 03Deployers: give consumers clear, conspicuous notice at the point of interaction with covered ADMT.
- 04Deployers: within 30 days of an adverse consequential decision, give a plain-language description of the ADMT's role.
- 05Let consumers access and correct personal data used, and request meaningful human review and reconsideration of adverse decisions.
- 06Developers and deployers: keep records needed to show compliance for at least three years.
02 / In this sector
In a defense AI workflow
Targets AI and other computational systems that produce predictions, scores, rankings or recommendations used to make or guide consequential decisions about individuals. It no longer imposes the 2024 Act's general duty of care against algorithmic discrimination.
Program office leads and ATO-package owners.
NIST AI RMF · DoW RAI · OMB M-25-21.
03 / Records
Records to keep
- 01Developer technical documentation package delivered to each deployer
- 02Point-of-interaction consumer notice text and placement records
- 03Adverse-decision explanations sent, with dates within 30 days
- 04Human review and data-correction request logs, kept three years
Optional evidence · where Planisphere fits
Keep a record anyone can check
When your team meets a duty, Planisphere can seal the event it reports as a receipt.
A disclosure shown, a review signed, a model change approved: the event your system reports.
The event becomes a sealed receipt, dated and attributed to whoever is signed in.
Paste the receipt into Verify. No account or key.
A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.
SOURCES
Go back to the source
Colorado General Assembly
Colorado General Assembly
Colorado General Assembly
Colorado Department of Law
RELATED
Related: Colorado AI Act: the full guide · Colorado AI Act for medicine · Colorado AI Act for law · Colorado AI Act for education