FIND THE EXPLANATION
A new interface can hide a familiar borrowing promise—or create a different risk. Identify the obligation, the collateral and the decision maker.
Read the complete guide →This address preserves a dated source document behind the guide. The complete explanation covers the questions, comparisons and next steps for this subject.
If you came here to check a specific citation, open the original archive below. It includes its source dates and recorded qualifications.
The explanation above is written for readers. These original working documents preserve the evidence trail, including technical language, dated passages and known corrections. They have not all received independent professional review. Use the marked limits before relying on a particular rule or figure.
Read the evidence with its boundaries. These are saved research components, including revisions. A scoped coordinator review checks selected evidence; it does not certify every claim, a complete jurisdiction, current law or individual applicability. Dates and access limits remain attached to the records.
The discovery lead does not identify a single unchanged 2024 law. The official 2026 Colorado compilation displays:
Accordingly, neither “the 2024 law is the complete current law” nor “all Part 17 requirements begin in January 2027” is an adequate description of the text examined. The report below separates the displayed current provisions, enacted future provisions, early-effective clauses, and unresolved incorporated authorities.
Actual public-source access: October 28, 2026, America/Los_Angeles. The recorded research began at approximately 03:09 PDT and continued after 03:26 PDT. This is an access date, not a statutory effective date.
Read-completeness finding: Both complete versions of Part 17 displayed in the official 2026 compilation were read, together with the complete principal adoption, delay, replacement, and chatbot acts and the complete selected psychotherapy amendment and application clauses. The investigation remains partial at specified incorporation, rulemaking, constitutional-transition, and later-history boundaries. In particular, several current incorporated Colorado titles could not be retrieved in readable form. Those failures are preserved; their contents are not reconstructed from older statutes, bill amendments, or search snippets.
All findings concern public legal categories. No actual or invented actor, system, consumer, decision, record, protected trait, transaction, agreement, application, or outcome is represented.
All successful and failed accesses below occurred on October 28, 2026 PDT. HTML has no printed-page or PDF-index claim. PDF pagination below comes from parsed document headers; no pixel-level verification is claimed.
| Source ID; issuer and title | Complete literal HTTPS URLs | Exact read bounds | Version, legal status, commencement/application, and limits |
|---|---|---|---|
| R100-P1-S001 — Colorado General Assembly, Office of Legislative Legal Services; 2026 Colorado Revised Statutes, Title 6 | Official delivery index: https://content.leg.colorado.gov/agencies/office-legislative-legal-services/2026-crs-titles-download. Officially linked HTML: https://olls.info/crs/crs2026-title-06.htm. PDF alternative: https://olls.info/crs/crs2026-title-06.pdf. | Complete displayed current and future Part 17, HTML lines 6516–7652, including definitions, operative clauses, source credits, and material editor’s notes. Separately read selected complete clauses of §§6-1-102(18), 6-1-105(1)(hhhh), future (uuuu), 6-1-1303, 1304(2)(k), (n), (o), complete §§1306–1307, §707(1)(b), and §1601(4)(a), as specified below. Title 6 PDF was located but not used for a whole-document or pixel read. | Official index identifies amendments, additions, and repeals of the 2026 Second Regular Session. It links the olls.info delivery files. Current and prospective text are separately marked. This authenticates the examined compilation, not an exhaustive intervening-law or judicial audit. |
| R100-P1-S002 — Colorado General Assembly; SB24-205, original adopted Act | Bill/version page: https://leg.colorado.gov/bills/sb24-205. Signed format: https://leg.colorado.gov/bill_files/47770/download. Session law: https://leg.colorado.gov/laws/session-laws/SB24-205/198/download. | Complete session-law §§1–3, printed pp.1199–1217; zero-based PDF indices 0–18. Signed format was only partially read; the complete reliance is on the session-law format. | Approved May 17, 2024; compiler identifies May 17 effectiveness. Original principal duty dates were February 1, 2026. Those dates were subsequently amended. §3 is the safety clause. Same Act in different formats, not independent corroboration. |
| R100-P1-S003 — Colorado General Assembly; SB25B-004, postponement Act | Bill page: https://leg.colorado.gov/bills/SB25B-004. Signed format: https://leg.colorado.gov/bill_files/90530/download. Session law: https://leg.colorado.gov/laws/session-laws/SB25B-004/3/download. | Complete §§1–4, printed pp.8–11; PDF indices 0–3. Signed-format extraction returned no body text; session law was readable. | Approved August 28, 2025. Replaces material February 1, 2026 dates with June 30, 2026. Compiler reports November 25, 2025 effectiveness. §4 contains a 90-day referendum-petition condition and an alternative post-election trigger; that condition is preserved below. |
| R100-P1-S004 — Colorado General Assembly; SB26-189, repeal and reenactment | Bill page: https://www.leg.colorado.gov/bills/SB26-189. Signed endpoint: https://www.leg.colorado.gov/bill_files/116489/download. Session law: https://www.leg.colorado.gov/laws/session-laws/SB26-189/131/download. | Complete §§1–6, printed pp.569–585; PDF indices 0–16. Signed endpoint failed; complete adopted session law was readable. §4 appropriation was read for the Act’s structure and early-effective treatment; no funding conclusion or allocation is made. | Approved May 14, 2026. §5(1): January 1, 2027 default. §5(2): specified clauses effective upon passage. §5(3): applies to consequential decisions made on or after January 1, 2027. §6 safety clause. |
| R100-P1-S005 — Colorado General Assembly; HB26-1263, conversational AI additions | Bill/version/action page: https://leg.colorado.gov/bills/HB26-1263. Signed format: https://leg.colorado.gov/bill_files/116851/download. Session law: https://leg.colorado.gov/laws/session-laws/HB26-1263/208/download. | Complete §§1–3, printed pp.1197–1203; PDF indices 0–6. Signed-format extraction returned no body text. Bill action and session-law approval line read for date reconciliation. | Approved May 29, 2026. Compiler reports August 12, 2026 effectiveness, subject to §3’s express conditional commencement. Specified operator duties begin January 1, 2027; annual reporting begins on and after July 1, 2027. The signed-document version date June 1 is not approval. |
| R100-P1-S006 — Colorado General Assembly; HB26-1195, selected psychotherapy amendment | https://leg.colorado.gov/laws/session-laws/HB26-1195/358/download | Complete §3, adding §6-1-1705.2, printed pp.2158–2160/PDF 5–7; complete §4, p.2160/PDF 7; narrow §2 definition and relevant cross-reference context, including AI definition p.2154/PDF 1 and §12-245-224.5(5)(a) context pp.2156–2157/PDF 3–4. Not a whole-Act substantive analysis. | Approved June 3, 2026. Conditional August 12, 2026 commencement under §4; application to actions taken on or after applicable effectiveness. Compiler harmonizes §1705.2 with the January 2027 replacement. |
The official compilation and the adopted acts support the current/future distinction; the formats of each Act are grouped above rather than treated as independent corroboration. Colorado General Assembly+7
| Source ID; issuer/title | Complete literal HTTPS URL | Exact read bounds and status | Limits |
|---|---|---|---|
| R100-P1-S007 — Colorado OLLS; 2026 Title 2 | https://olls.info/crs/crs2026-title-02.htm | Complete §2-4-301, multiple amendments; complete §2-4-303, repeal/revision savings. Current 2026 compilation. | No judicial construction or actual accrued liability determined; no whole Title 2 history. |
| R100-P1-S008 — Colorado OLLS; 2026 Title 7 | Readable PDF: https://olls.info/crs/crs2026-title-07.pdf. Failed HTML: https://olls.info/crs/crs2026-title-07.htm. | Complete relevant introductory language and §7-74-102(4), printed p.496/PDF index 495. | Parsed text only. No actual trade-secret qualification; no full trade-secret regime or amendment history. |
| R100-P1-S009 — Colorado OLLS; 2026 Title 11 | https://olls.info/crs/crs2026-title-11.htm | Complete selected definitions in §11-101-401(3.5), (5), (20), (23), (27), (37), (39), (46), (50), (58) and §11-30-101(1)(a). | Federal credit-card-bank incorporation and complete federal/out-of-state credit-union chains remain unexamined. No actual charter, affiliation, supervision, or compliance. |
| R100-P1-S010 — Colorado OLLS; 2026 Title 12 | Readable PDF: https://olls.info/crs/crs2026-title-12.pdf. Failed HTML: https://olls.info/crs/crs2026-title-12.htm. | §12-245-202(10), (14)(a)–(b), printed p.999/PDF 998; §12-245-224.5(1)(b), p.1031/PDF 1030; narrow (5)(a) context p.1033/PDF 1032. | Selected definitions and cross-reference only; no psychotherapy licensure, clinical, or professional-practice determination. |
| R100-P1-S011 — Congress/OLRC; 42 U.S.C. §234 | https://uscode.house.gov/us/usc/119-134/t42/s234/ | Complete (d)(1)–(2), health professional/health-care services. Displayed compilation through P.L.119-134, October 20, 2026. | Broader public-health-emergency liability provisions not adopted into this report. |
| R100-P1-S012 — Congress/OLRC; 42 U.S.C. §2000a | https://uscode.house.gov/us/usc/119-134/t42/s2000a/ | Complete (a)–(e) read for context; reliance narrowly on (e) and its exception concerning facilities made available to customers or patrons of covered establishments. Same displayed federal cutoff. | No actual private-club, establishment, discrimination, or jurisdiction finding. |
| R100-P1-S013 — Congress/OLRC; 18 U.S.C. §2256 | https://uscode.house.gov/us/usc/119-134/t18/s2256/ | Complete introductory language and (5), “visual depiction.” Same displayed federal cutoff. | No other criminal-law elements or actual content classification. |
| R100-P1-S014 — HHS; 45 C.F.R. §160.103, eCFR | https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160/subpart-A/section-160.103 | Complete selected definitions of business associate, covered entity, health care, health care clearinghouse, health care provider, and health plan. Displayed Title 45 currency October 26, 2026; title amendment label October 6, 2026. | Nested statutory/program, PHI, organized-arrangement, and related HIPAA predicates are not all completed. A title-level amendment label is not a definition-specific effective date. |
| R100-P1-S015 — Colorado Attorney General; AI rulemaking explanation | https://coag.gov/ai/ | Complete generic page read. It describes the adopted replacement and a proposed/interim rulemaking process. | Not an adopted rule. Its statement that HB26-1263 was signed July 1, 2026 conflicts with S005’s May 29 approval. No final rule body authenticated here. |
| R100-P1-S016 — Colorado OLLS; Red Book 2026 | https://content.leg.colorado.gov/agencies/office-legislative-legal-services/red-book-2026 | Introductory status explanation and selected Part 17 change entries. Page identifies a final version updated July 2, 2026, 11:35 a.m. MDT. | Legislative change index, not substitute for adopted text or evidence of every later event. |
These narrow sources were read to avoid replacing statutory categories with ordinary-language assumptions. Unfinished nested incorporations remain expressly unfinished. Colorado Revised Statutes 2026+11
| Source ID | Exact attempted original endpoints | Observed result; dependent hold |
|---|---|---|
| R100-P1-S017 — 2026 Title 8 | https://olls.info/crs/crs2026-title-08.htm; https://olls.info/crs/crs2026-title-08.pdf; https://olls.info/crs/crs2026-title-08.docx | HTML exceeded retrieval-size limit; PDF failed with reported content length 10,645,792; DOCX unsupported by retrieval. Current §8-4-101(5)–(6) employee/employer definitions not authenticated. A 2026 amendment search result was discovery only, not substituted. |
| R100-P1-S018 — 2026 Title 10 | https://olls.info/crs/crs2026-title-10.htm; https://olls.info/crs/crs2026-title-10.pdf; https://olls.info/crs/crs2026-title-10.docx | HTML exceeded size limit; PDF parsing failed; DOCX unsupported. Full current §§10-1-102(13), 10-14-102, and 10-3-1104.9 not read. S004’s adopted addition of §10-3-1104.9(3)(e) was read. |
| R100-P1-S019 — 2026 Title 13 | https://olls.info/crs/crs2026-title-13.htm; https://olls.info/crs/crs2026-title-13.pdf; https://olls.info/crs/crs2026-title-13.docx | HTML exceeded size limit; PDF parsing failed; DOCX unsupported. Current §13-21-1502(7), (10) and Article 64 category chain not authenticated. Older adopted-text discovery was not used as proof of current definitions. |
| R100-P1-S020 — Colorado Constitution compilation | https://olls.info/crs/crs2026-title-00.htm; https://olls.info/crs/crs2026-title-00.pdf | HTML exceeded size limit; PDF parsing failed. Independent full constitutional commencement/referendum and speech-clause analysis remains held. The Acts’ own complete effective-date language and compiler dates are reported separately. |
The following is an inventory of the bodies actually displayed, not an inference from the prompt’s section numbers. No reserved section is invented. The added decimal section is retained as displayed. Colorado Revised Statutes 2026+5
| Section | C-current: Artificial Intelligence | F-future: Automated Decision-Making Technology in Consequential Decisions |
|---|---|---|
| 6-1-1701 | Definitions | Definitions |
| 6-1-1702 | Developer duty to avoid algorithmic discrimination—required documentation | Developer responsibilities—documentation |
| 6-1-1703 | Deployer duty to avoid algorithmic discrimination—risk-management policy and program | Deployer record keeping |
| 6-1-1704 | Disclosure of an AI system to consumer | Deployer disclosures—point-of-interaction notice, public posting, post-adverse-outcome disclosures, legislative declaration, trade secrets, other law, accessibility, rules |
| 6-1-1705 | Compliance with other legal obligations—definitions | Consumer rights—correction, human review and reconsideration, rules |
| 6-1-1705.2 | AI systems and psychotherapy services—prohibited practices and definitions | Harmonized psychotherapy provision retained |
| 6-1-1706 | Enforcement by Attorney General | Enforcement, deceptive trade practice, cure, no private right, joinder, reporting, repeal |
| 6-1-1707 | Rules | Liability, fault allocation, joint-and-several-liability limit, indemnification, existing law |
| 6-1-1708 | Conversational AI services—operator duties, minors, disclosures, reports, definitions | Other legal obligations—insurers, covered entities, disclosures |
| 6-1-1709 | No corresponding current body displayed | No new private right; other law |
| 6-1-1710 | No corresponding current body displayed | Conversational AI provision relocated/harmonized by compiler |
| Claim ID | Qualified proposition | Exact source and pinpoint |
|---|---|---|
| R100-P1-C001 | The examined official 2026 compilation is current through the legislative session identified by its publication index; actual access was October 28, 2026 PDT. That does not establish an exhaustive later-law or judicial chain. | S001, official download-index introduction and Title 6 status material. |
| R100-P1-C002 | The compiler displays the complete C-current Part under “Artificial Intelligence,” including §§1701–1708 and §1705.2, with principal existing sections marked effective until January 1, 2027. | S001, current Part heading and section/editorial notes. |
| R100-P1-C003 | The compiler also displays the complete F-future Part under the ADMT title, §§1701–1710 plus §1705.2, including harmonized additions. It is adopted future text, not merely a proposal. | S001, future Part heading/notes; S004 §1; S005–S006. |
| R100-P1-C004 | SB24-205 originally added Part 17 and the associated deceptive-trade-practice entry. Its original February 1, 2026 application language is historical after the adopted delay. | S002 §§1–3; S003 §§1–3. |
| R100-P1-C005 | SB25B-004 changes the specified dates to June 30, 2026. Its §4 uses the day after expiration of 90 days after final adjournment, at 12:01 a.m., subject to a timely referendum-petition alternative. Compiler-reported November 25, 2025 effectiveness is distinct from that conditional enacted formula. | S003 §§1–4; S001 source notes. |
| R100-P1-C006 | SB26-189 generally takes effect January 1, 2027 and applies to consequential decisions made on or after that date. New §§1704(4), 1705(3), 1706(6), the insurance-rulemaking addition, and Act §§4–6 take effect upon passage. | S004 §§1, 3, 5(1)–(3), 6; approval May 14, 2026. |
| R100-P1-C007 | HB26-1263’s approval is May 29, 2026. Its Act-level effective clause is conditional; the compiler reports August 12, 2026. The enacted text separately specifies January 1, 2027 duties and July 1, 2027 reporting applicability. | S005 §§1–3 and approval line; S001 current §1708/future §1710. |
| R100-P1-C008 | HB26-1195’s selected Part 17 amendment is approved June 3, 2026; §4 supplies conditional commencement and application to actions on or after applicable effectiveness. Compiler notes identify August 12, 2026 and future harmonization. | S006 §§3–4; S001 §1705.2 notes. |
| R100-P1-C009 | The compiler expressly harmonizes the 2026 additions. Section 2-4-301 directs harmonization of multiple amendments if possible and supplies effective-date/passage rules if irreconcilable. This report does not adjudicate a conflict. | S001 future §§1701, 1705.2, 1710 notes; S007 §2-4-301. |
| R100-P1-C010 | Repeal, revision, amendment, or consolidation does not release, extinguish, or alter an incurred penalty, forfeiture, or liability unless expressly provided; the former text remains available for the stated enforcement purpose. Actual incurrence and temporal application remain absent. | S007 §2-4-303, complete body. |
| R100-P1-C011 | The AG explanation’s July 1, 2026 signing statement for HB26-1263 conflicts with the adopted Act and bill-action record showing May 29. The adopted source governs the date reported here; the discrepancy remains visible. | S015; S005 approval line and bill action. |
| R100-P1-C012 | No complete final implementing-rule body, exhaustive post-compilation enactment chain, constitutional-transition chain, or judicial history was authenticated. Proposed/interim rulemaking descriptions are not treated as adopted obligations. | S015–S020 and failure log; limits on S001–S014. |
Evidence for this status group comes from the compilation, enacted date clauses, and narrow construction provisions—not from a press summary alone. leg.colorado.gov+7
| Claim ID | Complete material rule or definition, with limits | Exact source/pinpoint |
|---|---|---|
| R100-P1-C013 | Article 1’s “person” includes the listed individual and legal/commercial forms, including persons with a joint or common interest. This definition alone does not determine governmental coverage, actual organizational form, or authority. | S001 §6-1-102 introductory clause and (18). |
| R100-P1-C014 | An AI system is machine-based; for an explicit or implicit objective it infers from inputs how to generate outputs—including content, decisions, predictions, or recommendations—that can influence physical or virtual environments. A commercial AI label is not the statutory test. | S001 C-current §1701(2). |
| R100-P1-C015 | Algorithmic discrimination requires AI use resulting in unlawful differential treatment or impact disfavoring an individual/group based on actual or perceived age, color, disability, ethnicity, genetic information, limited English proficiency, national origin, race, religion, reproductive health, sex, veteran status, or another state/federal protected classification. The definition does not itself complete the underlying unlawfulness test. | S001 C-current §1701(1)(a). |
| R100-P1-C016 | The definition excludes specified high-risk-system offer/license/use solely for self-testing/law compliance or pool expansion/diversity/historical-discrimination redress; it also references nonpublic private-club acts/omissions. Incorporated §2000a(e) itself contains a qualification for facilities made available to patrons of covered establishments. A “private” label alone is insufficient. | S001 §1701(1)(b)(I)–(II); S012 §2000a(e), read with (b)–(d). |
| R100-P1-C017 | A consequential decision must have a material legal or similarly significant effect on provision, denial, cost, or terms in the listed fields: education, employment, financial/lending services, essential government services, health-care services, housing, insurance, or legal services. | S001 C-current §1701(3)(a)–(h). |
| R100-P1-C018 | C-current “consumer” is an individual who is a Colorado resident. Residence and individuality are actual predicates, not findings made here. | S001 C-current §1701(4). |
| R100-P1-C019 | “Deploy” means use of a high-risk AI system. A deployer is a person doing business in Colorado that deploys one; a developer is a person doing business in Colorado that develops or intentionally and substantially modifies an AI system. The developer definition and particular high-risk duties must both be considered. | S001 C-current §1701(5)–(7). |
| R100-P1-C020 | High-risk AI makes or is a substantial factor in making a consequential decision when deployed. “Substantial factor” cumulatively assists the decision, is capable of altering its outcome, and is AI-generated; it includes specified AI output concerning a consumer used as a basis for the decision. | S001 C-current §1701(9)(a), (11)(a)–(b). |
| R100-P1-C021 | The high-risk definition excludes an AI system intended for a narrow procedural task, or for detecting decision patterns/deviations without an intended replacement or influence on a previously completed human assessment absent sufficient human review. | S001 C-current §1701(9)(b)(I). |
| R100-P1-C022 | Listed technologies are excluded unless, when deployed, they make or substantially contribute to a consequential decision: non-facial-recognition antifraud; anti-malware/virus; AI games; calculators; cybersecurity; databases/storage; firewalls; domain registration; website loading; networking; spam/robocall filters; spell-checking; spreadsheets; web caching/hosting or similar technology; and the specified natural-language information/referral/recommendation/question technology with an accepted-use policy prohibiting discriminatory or harmful content. | S001 C-current §1701(9)(b)(II)(A)–(R). |
| R100-P1-C023 | Intentional/substantial modification is a deliberate change producing a new reasonably foreseeable algorithmic-discrimination risk. The learning exception requires all listed conditions: post-availability/deployment learning; change from that learning; predetermination by the deployer/contracted assessor at the initial assessment; and inclusion in technical documentation. | S001 C-current §1701(10)(a)–(b). |
| R100-P1-C024 | Incorporated health-care services concern diagnosis, prevention, treatment, or health assessment/care provided by a health professional or under professional supervision. The incorporated professional is licensed, registered, or certified under federal or state law. No actual provider or service classification is established. | S001 §1701(8); S011 §234(d)(1)–(2). |
| R100-P1-C025 | The incorporated trade-secret definition covers specified secret and valuable business/professional information, with measures taken to prevent general availability except for selected limited-purpose access. Merely calling information proprietary is not a finding that this definition is satisfied. | S001 current §1701(12), future (17); S008 §7-74-102(4). |
The cumulative elements, exceptions, and protected-category wording above are from the complete definition body. Colorado Revised Statutes 2026+3
| Claim ID | Qualified statutory instruction | Exact source/pinpoint |
|---|---|---|
| R100-P1-C026 | On and after June 30, 2026, a high-risk developer must use reasonable care against known or reasonably foreseeable algorithmic-discrimination risks arising from intended and contracted uses. Compliance with the section and applicable AG rules supplies a rebuttable, AG-enforcement-specific presumption—not a finding of no discrimination. | S001 §1702(1); S003 §1. |
| R100-P1-C027 | Subject to §1702(6), the developer must make available to the deployer/other developer: foreseeable and known harmful uses; training-data-type summaries; known/foreseeable limitations and risks; purpose, benefits, uses, and information necessary for §1703; evaluation/mitigation before availability; data governance, suitability, bias and mitigation; outputs; foreseeable-deployment mitigation; appropriate/inappropriate use and human monitoring; and reasonably necessary output/performance-risk documentation. | S001 §1702(2)(a)–(d), including all subclauses. |
| R100-P1-C028 | To the extent feasible, documentation or artifacts must support the deployer/contractor’s impact assessment, subject to the disclosure limitation. A developer that is also the deployer need not generate this documentation unless the system is provided to an unaffiliated deployer. | S001 §1702(3)(a)–(b). |
| R100-P1-C029 | A clear, readily available public website statement must describe currently developed/modified and available high-risk-system types and management of known/foreseeable risks. Update as needed for accuracy and no later than 90 days after an intentional/substantial modification. | S001 §1702(4). |
| R100-P1-C030 | Developer reporting is triggered by testing that discovers a deployed system caused or is reasonably likely to have caused discrimination, or a credible deployer report that it caused discrimination. Notice goes to the AG in the prescribed form and all known deployers/other developers, without unreasonable delay and no later than 90 days after the specified discovery/report. | S001 §1702(5)(a)–(b). |
| R100-P1-C031 | Developer disclosures under (2)–(5) need not disclose a trade secret, legally protected information, or information creating a security risk. The AG may require the (2) statement/documentation within 90 days of request; it is excluded from CORA disclosure, may be designated proprietary/secret, and submission does not waive applicable attorney-client/work-product protection. | S001 §1702(6)–(7). |
| R100-P1-C032 | On and after June 30, a high-risk deployer has a reasonable-care duty against known/foreseeable algorithmic-discrimination risks and a rebuttable presumption conditioned on the section and AG rules. The developer’s “intended and contracted uses” wording is not inserted into this deployer clause. | S001 §1703(1). |
| R100-P1-C033 | Subject to the limited small-deployer exception, the deployer must maintain an iterative risk-management policy/program specifying principles, processes, and personnel; it must identify, document, mitigate, and regularly/systematically review risks across the lifecycle. Reasonableness considers the referenced frameworks or AG-designated framework, size/complexity, systems’ nature/scope/intended uses, and data sensitivity/volume. One program may cover multiple systems. Framework contents/compliance remain unexamined. | S001 §1703(2)(a)–(b). |
| R100-P1-C034 | Subject to (3)(d), (3)(e), and (6), deployment on/after June 30 triggers an impact assessment; deployed systems require assessments at least annually and within 90 days after an intentional/substantial modification is made available. This wording is not converted into an invented universal pre-deployment deadline. | S001 §1703(3)(a). |
| R100-P1-C035 | Assessments must include, at minimum and to the extent reasonably known/available: purpose/use/context/benefits; risk and mitigation analysis; input/output categories; customization data if used; performance metrics/known limitations; transparency measures; and post-deployment monitoring/user safeguards, oversight, use, and learning processes. Post-modification assessments add consistency/variation from developer-intended uses. | S001 §1703(3)(b)–(c). |
| R100-P1-C036 | One assessment may cover a comparable system set. An assessment under another applicable law/regulation suffices only if reasonably similar in scope and effect. These are conditional alternatives, not automatic recognition of any existing assessment. | S001 §1703(3)(d)–(e). |
| R100-P1-C037 | Retain the most recent assessment, associated records, and all prior assessments for at least three years following final deployment. Separately, on or before June 30, 2026 and at least annually thereafter, review each deployment to ensure it is not causing discrimination. | S001 §1703(3)(f)–(g). |
| R100-P1-C038 | By deployment for a consequential decision and before the decision, notify the consumer of high-risk use; give purpose, decision nature, deployer contact information, plain-language system description, and access instructions for the public statement; provide profiling opt-out information if applicable under the specified privacy provision. | S001 §1703(4)(a)(I)–(III); §1306(1)(a)(I)(C). |
| R100-P1-C039 | An adverse decision triggers principal reasons, AI contribution, processed-data types and sources, an opportunity to correct incorrect personal data, and an appeal opportunity. Human review is required if technically feasible, except when an appeal opportunity is not in the consumer’s best interest, including life/safety risk from delay. This is not a guaranteed reversal. | S001 §1703(4)(b). |
| R100-P1-C040 | Required communications must be direct, plain-language, in all languages ordinarily used for the specified consumer business communications, and disability-accessible. If direct provision is not possible, availability must be reasonably calculated to ensure receipt. | S001 §1703(4)(c). |
| R100-P1-C041 | Subject to (6), the deployer’s readily available website statement must identify current high-risk-system types, risk management, and the nature, source, and extent of information collected/used; it must be periodically updated. The clause supplies no fixed update interval. | S001 §1703(5). |
| R100-P1-C042 | The exception covers only (2), (3), and (5) and requires all conditions at deployment and throughout use: fewer than 50 full-time-equivalent employees; no own data used to train; system used for developer-disclosed intended uses and continuing to learn from other data; and consumer availability of a developer-provided assessment containing substantially similar required information. | S001 §1703(6)(a)–(c). |
| R100-P1-C043 | For deployment on/after June 30 followed by discovery that the system caused discrimination, the deployer must notify the AG in the prescribed form without unreasonable delay and within 90 days of discovery. This trigger is distinct from the developer’s credible-report/likely-causation alternatives. | S001 §1703(7). |
| R100-P1-C044 | Listed deployer disclosures need not reveal secrets or legally protected information; withholding under (8) or the text’s actual reference to §1705(5) requires consumer notice and a basis. AG-requested policy, assessment, or records are due within 90 days; CORA exclusion, designation, and privilege nonwaiver are specified. The cross-reference is preserved, not silently “corrected.” | S001 §1703(8)–(9). |
| R100-P1-C045 | From June 30, a deployer or other developer making available an AI system intended to interact with consumers must ensure interaction disclosure, unless interaction with AI would be obvious to a reasonable person. The provision is not limited by its text to high-risk systems. | S001 §1704(1)–(2). |
These duties distinguish initial information, public statements, adverse-decision information, risk discovery, and AG requests. Their different triggers and clocks are not interchangeable. Colorado Revised Statutes 2026+2
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C046 | Part 17 preserves ability to comply with law and governmental process, reasonably and in good faith cooperate with law enforcement, address legal claims, take immediate life/physical-safety steps, undertake specified security/fraud/integrity activities by means other than facial recognition, assist compliance, recall products, and repair functionality errors. These clauses do not establish an actual qualifying purpose. | S001 §1705(1)(a)–(f), (i), (2). |
| R100-P1-C047 | Public/peer-reviewed scientific or statistical research must satisfy public-interest, other ethics/privacy-law, and 45 C.F.R. Part 46 or relevant FDA conditions. Pre-market/deployment research/testing/development is separately preserved except real-world testing. Those external research regimes remain unexamined. | S001 §1705(1)(g)–(h). |
| R100-P1-C048 | Duties do not apply where compliance would violate Colorado evidentiary privilege; the section also preserves stated speech/press freedoms. It does not decide privilege, constitutional validity, or a categorical defense on absent facts. | S001 §1705(3)–(4). |
| R100-P1-C049 | The federal-authority exclusion is limited to the specified high-risk activities involving an authorized/approved/etc. system within federal authority, a qualifying FHFA-regulated entity, or qualifying substantially equivalent/stricter standards. Separate research supporting federal approval/certification/review is covered. No approval or standards equivalence is established. | S001 §1705(5)(a)–(b). |
| R100-P1-C050 | Specified Commerce/Defense/NASA contract work and federally acquired systems have exceptions to their exclusions for high-risk employment or housing decisions. Federal involvement alone is not a universal exclusion. | S001 §1705(5)(c), (6). |
| R100-P1-C051 | The covered-entity health recommendation provision cumulatively requires AI-generated recommendations, provider action to implement them, and recommendations not considered high risk. HIPAA category and risk qualification remain open. | S001 §1705(5)(d)(I)–(III); S014, limited read. |
| R100-P1-C052 | The insurer/fraternal-society/insurer-system-developer compliance treatment requires being subject to §10-3-1104.9 and rules under it. Current incorporated definitions and full regulatory requirements were not authenticated; no insurer-wide exemption is found. | S001 §1705(7); S018 failure. |
| R100-P1-C053 | Listed banking/credit-union categories and their affiliates/subsidiaries receive full-compliance treatment only if subject to prudential examination under published high-risk-AI guidance/regulations that are substantially equivalent or stricter and, at minimum, require regular antidiscrimination audits and mitigation of actual or reasonably foreseeable algorithmic discrimination. | S001 §1705(8)(a)(I)–(II). |
| R100-P1-C054 | The banking clause incorporates specified affiliation, bank, credit-union, and out-of-state-bank definitions. Affiliation concerns control/common control; relevant control includes the statutory voting-security or board-election tests. The bank definition excludes the specified credit-card national bank. Some nested federal/foreign category predicates remain uncompleted. | S001 §1705(8)(b); S009 specified complete definitions; 12 U.S.C. §1841(c)(2)(F) unexamined. |
| R100-P1-C055 | The developer, deployer, or other person relying on a §1705 exemption bears the burden of demonstrating that the action qualifies. | S001 §1705(9). |
| R100-P1-C056 | Current enforcement is exclusive to the AG notwithstanding §6-1-103. Subject to the affirmative-defense provision, violation is the specified unfair trade practice. No penalty amount or complete remedy procedure is established here. | S001 §1706(1)–(2); §6-1-105(1)(hhhh). |
| R100-P1-C057 | The affirmative defense requires discovery and cure through encouraged feedback, NIST-described adversarial/red-team testing, or internal review, and otherwise complying with: latest NIST framework and ISO/IEC 42001; or a qualifying equivalent/stricter recognized framework; or an AG-designated/publicly disseminated framework. The asserting actor bears demonstration. | S001 §1706(3)–(4). |
| R100-P1-C058 | Other rights, claims, remedies, presumptions, and defenses are preserved; Part 17 presumptions/defenses apply only to AG enforcement. The current text says Part 17 does not provide a basis for a private right of action for violations of Part 17 or other law. Read together, these clauses do not establish immunity from independently existing law. | S001 §1706(5)–(6). |
| R100-P1-C059 | The AG may adopt implementing/enforcement rules concerning developer documentation, specified notices, risk programs, assessments, presumptions/defenses, and framework recognition. This authority is not evidence that every contemplated rule has been finally adopted. | S001 §1707(1), complete list; S015 status limit. |
The banking, insurance, federal-system, research, and framework provisions have different predicates. They cannot be collapsed into a general “regulated actor” exemption. Colorado Revised Statutes 2026+2
| Claim ID | Qualified definition or exclusion | Exact source/pinpoint |
|---|---|---|
| R100-P1-C060 | ADMT processes personal data and uses computation to produce information used to make, guide, or assist a decision, judgment, or determination concerning an individual. Listed output forms include predictions, recommendations, classifications, rankings, and scores. | S001 F-future §1701(2)(a); S004 §1. |
| R100-P1-C061 | ADMT excludes the listed anti-malware/virus, calculator, database/storage, firewall, domain/loading/networking, spam/robocall, spell-checking, web-cache/hosting technologies; spreadsheets must require human analysis and not use machine learning/foundation/large-language models. It also excludes solely administrative-processing assistance for human review and the specified understandable information technology only if both no consequential-decision intended/marketed/etc. use and an acceptable-use prohibition are satisfied. | S001 F-future §1701(2)(b)(I)–(III). |
| R100-P1-C062 | Consequential decisions concern provision, access, eligibility, selection, or compensation in a covered domain, or differentiated price/cost-sharing/compensation/material terms reasonably likely materially to limit, delay, deny, or fundamentally alter access, eligibility, or opportunity. “Adverse outcome” separately covers listed denial/reduction/restriction actions or materially less favorable terms compared with similarly situated consumers, with its stated material-effect qualifications. | S001 F-future §1701(1), (3)(a). |
| R100-P1-C063 | Consequential-decision exclusions cover: qualifying low-stakes/routine processes; advertising/marketing/product recommendations/search/moderation; qualifying manual spreadsheets; human-review summaries without materially influential inference; narrow procedural/data functions under the actual “do not … or” wording; cybersecurity/spam/reliability/AML/CTF controls; sanctions compliance with a facial-recognition limitation unless solely identity confirmation; specified fraud/identity/required monitoring/reporting activities; and routine academic support not materially influential. External sanctions/financial regimes are not thereby completed. | S001 F-future §1701(3)(b)(I)–(IX). |
| R100-P1-C064 | Consumer incorporates §1303(6)(a), but expressly includes an employee, a Colorado-resident job applicant, and an individual whose access, eligibility, or opportunity in Colorado is evaluated through a consequential decision by a person doing business in Colorado. It is not simply the old residence-only definition. | S001 F-future §1701(4); §1303(6)(a). |
| R100-P1-C065 | Covered domains are education; employment creating or potentially creating an employer-employee relationship; lease/purchase of Colorado residential real estate; financial/lending services; specified insurance decisions; health-care services; and essential government/public-benefit eligibility/renewal. Legal services are not separately listed in this successor domain definition; that absence does not resolve other law. | S001 F-future §1701(6)(a)–(g). |
| R100-P1-C066 | Covered ADMT is ADMT used to materially influence a consequential decision. Material influence cumulatively requires a non-de-minimis output factor used in making the decision and an effect on its outcome; incidental, trivial, and clerical uses are excluded. Capability alone is not substituted for the successor’s actual-use/effect words. | S001 F-future §1701(5), (13). |
| R100-P1-C067 | Deployer requires doing business in Colorado and deployment of covered ADMT. Developer includes the specified commercial provision of covered ADMT, development of a component designed/marketed/intended/documented/etc. for covered ADMT, or intentional/substantial modification making an ADMT covered. | S001 F-future §1701(7), (8)(a). |
| R100-P1-C068 | Developer exclusions have separate predicates: solely research without consequential use in the research; internal use without making it available to another person for consequential use; a preceding developer after an unaffiliated modifier changes the specified intended/etc. use; or component integration into covered ADMT without the developer’s actual knowledge. | S001 F-future §1701(8)(b). |
| R100-P1-C069 | Employee/employer are expressly incorporated from §8-4-101(5)–(6), and FERPA is identified by statute and implementing regulations. Current employment definitions failed access; the full FERPA regime was not read. No category is filled from an ordinary label. | S001 F-future §1701(9)–(11); S017. |
| R100-P1-C070 | Intentional/substantial modification concerns deliberate material change to the listed intended/documented/etc. uses. “Material update” concerns an update/patch/release/version—including parameters/defaults/documentation—that the developer knows or reasonably should know is likely materially to affect relevant outputs/performance or stated intended use. Nonmaterial routine maintenance, cosmetic changes, and bug fixes are excluded under the stated conditions. | S001 F-future §1701(12), (14). |
| R100-P1-C071 | Meaningful human review requires a designated reviewer with authority to approve, modify, or override; relevant available primary evidence; training; no default to system output; and sufficient information about intended use, material limitations, input categories, and principal factors. It does not require disclosure of proprietary source code, weights, or trade secrets. | S001 F-future §1701(15). |
| R100-P1-C072 | Personal data incorporates §1303(17): linked or reasonably linkable information concerning an identified/identifiable individual, excluding qualifying deidentified and publicly available information. Government-record availability or a reasonable basis concerning lawful public availability supplies the public-information branch; public labeling alone does not. | S001 F-future §1701(16); §1303(11), (16)–(17). |
These are successor definitions, not retroactive substitutions for every current clause. Colorado Revised Statutes 2026+2
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C073 | From January 1, 2027, developers must provide each covered deployer reasonably understandable documentation protecting secrets/legally protected information: intended/harmful uses; known training-data categories including personal data; known limitations/risks/nonuse circumstances; use/monitoring/human-review instructions where applicable; and information reasonably necessary for §1704. Withholding requires notice to the deployer. | S001 F-future §1702(1). |
| R100-P1-C074 | Developers must notify each deployer of material updates, intentional/substantial modifications, and changes in intended use, limitations, or risk mitigation within a reasonable time. Public release notes suffice only with direct notice of the public release to each deployer. | S001 F-future §1702(2). |
| R100-P1-C075 | The (1)–(2) disclosures apply only to deployer uses marketed/advertised/configured/contracted/sold/licensed for material consequential influence. The section’s further scope includes specified intended/documented/etc. consequential use or awareness of consequential use consistent with intended and contracted uses. No different connector is substituted. | S001 F-future §1702(3), (5). |
| R100-P1-C076 | Developer compliance records must be retained at least three years after creation, or longer if other applicable law requires. Included categories are version identifiers, changelogs, and material-update documentation/notices. | S001 F-future §1702(4). |
| R100-P1-C077 | Deployers retain reasonably necessary compliance records at least three years after the consequential decision, or longer under applicable law. Version identifiers, changelogs, and material mitigation documentation are illustrative permitted record categories. | S001 F-future §1703. |
| R100-P1-C078 | Before using covered ADMT to materially influence a consequential decision, a deployer must give clear and conspicuous use notice and instructions for obtaining additional information. A prominent public notice reasonably accessible at the interaction, including a reasonably proximate link/posting, is the expressly permitted route. | S001 F-future §1704(1)–(2). |
| R100-P1-C079 | Within 30 days after making a consequential decision producing an adverse outcome, provide plain-language decision/ADMT-role information; a simple means to request the system name/version if applicable, developer, and input types/categories/sources to the extent received under §1702; and explanation/exercise instructions for §1705 rights. | S001 F-future §1704(3). |
| R100-P1-C080 | The adopted legislative declaration calls for sector-sensitive rules; the AG must adopt implementation/clarification rules on or before January 1, 2027. The permitted subjects include disclosed categories, sector examples, understandable descriptions, and interaction with other notice laws. This rulemaking provision is early-effective, not proof of a completed rule. | S001 F-future §1704(4); S004 §5(2). |
| R100-P1-C081 | Future consumer disclosure need not disclose trade secrets or legally protected information; withholding under §1704(5) requires notifying the consumer. This does not require disclosure of the protected content itself. | S001 F-future §1704(5). |
| R100-P1-C082 | A creditor required to give and actually giving an ECOA/Regulation B and applicable FCRA notice for the specified credit decision may use that notice for the same state decision only if it also satisfies the state requirements. No duplicative notice is required on those conditions; prohibited federal disclosure is not required; an appropriate ADMT statement/instructions may be included. Federal notice compliance itself is unexamined. | S001 F-future §1704(6)(a)–(d). |
| R100-P1-C083 | Disclosure does not require federally prohibited information or compromise the confidentiality/integrity of legally required cybersecurity, fraud, AML, CTF, or sanctions programs. Notices must be reasonably accessible to people with disabilities or limited English proficiency consistently with applicable law; the complete accessibility regimes remain held. | S001 F-future §1704(7)–(8). |
| R100-P1-C084 | For education, a FERPA-subject deployer may use existing FERPA channels, including applicable parent/eligible-student channels; duplicative FERPA notice/disclosure processes are not required. Actual FERPA category and sufficiency are not established. | S001 F-future §1704(9). |
| R100-P1-C085 | After an adverse outcome from a consequential decision materially influenced by covered ADMT, the consumer may request and the deployer must respond with instructions for requesting personal data/correcting factual or material inaccuracies consistently with §1306, and an opportunity for meaningful human review/reconsideration to the extent commercially reasonable. | S001 F-future §1705(1)(a). |
| R100-P1-C086 | The specified employment/commercial-consumer and §1304(2)(k), (n), (o) exceptions do not apply to this correction right. Correction of opinions, predictions, scores, or protected evaluations is not required. These words do not remove every exception from the entire privacy regime. | S001 F-future §1705(1)(b)–(c); selected incorporated clauses. |
| R100-P1-C087 | Existing FERPA inspection/review/amendment and applicable district processes may satisfy the education provision if they offer the stated reasonable correction/reconsideration mechanism; duplicative processes are unnecessary. The AG must adopt §1705 clarification/implementation rules on or before January 1, 2027; that rulemaking clause is early-effective. | S001 F-future §1705(2)–(3); S004 §5(2). |
The successor does not turn an adverse-outcome notice into approval, reversal, credit eligibility, or proof that an underlying federal notice is sufficient. Colorado Revised Statutes 2026+3
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C088 | The AG shall enforce through the Colorado Consumer Protection Act; §§1702–1705 disclosure/consumer-right violations are exclusively AG-enforceable. Part 17 violations are deceptive trade practices; inconsistent CCPA provisions do not apply to those violations. This is not a completed penalty/remedy analysis. | S001 F-future §1706(1)–(2). |
| R100-P1-C089 | Before enforcement, the AG shall issue a violation notice if cure is deemed possible. Failure to cure within 60 days after receipt permits action. A demonstrable knowing or repeated violation removes the requirement to offer a cure period. During an action, cure within 60 days after written notice may be considered in monetary-relief mitigation; it is not guaranteed dismissal. | S001 F-future §1706(3)(a)–(d). |
| R100-P1-C090 | Beginning January 2028 and each January thereafter, the AG’s specified SMART Act presentation must report actions filed/completed, cure periods offered/unmet, and violations for which cure was not deemed possible, separately concerning developers/deployers. The whole subsection (3) is repealed January 1, 2030, including this reporting paragraph—not just the cure clock. | S001 F-future §1706(3)(e)–(f); §2-7-203 context unexamined. |
| R100-P1-C091 | The future Part creates no new private right; existing state/federal rights and remedies are preserved. Compliance does not excuse other-law noncompliance. No independent cause of action, damages, immunity, or standing is found here. | S001 F-future §1706(4), §1709(1)–(2). |
| R100-P1-C092 | The AG may clarify the Part and material-influence definition through rules, including presumptions/examples/indicators. Rulemaking requires public notice, written-comment opportunity, and at least one hearing, subject to §24-4-103. The early-effective joinder clause preserves existing Rules 19/20 abilities in existing-law actions; it does not create a new action. | S001 F-future §1706(5)–(6); S004 §5(2). |
| R100-P1-C093 | In an existing state antidiscrimination action arising from a consequential decision materially influenced by covered ADMT, the section permits developer/deployer liability and directs relative-fault allocation. It does not newly apportion fault to a claimant or create joint-and-several liability where existing law does not permit it. | S001 F-future §1707(1)–(4). |
| R100-P1-C094 | Developer liability under this section requires both the specified intended/documented/marketed/etc. use and material influence on the decision giving rise to an existing-law violation; outside-use violations are excluded under the stated clause. Deployer independent acts/omissions remain separately addressed, including the stated outside-use situation where the developer complied with §1702. | S001 F-future §1707(5)–(6). |
| R100-P1-C095 | A developer/deployer contract provision shifting the indemnitee’s own covered discriminatory-act damages through indemnity/defense/hold-harmless is contrary to public policy and void under the stated scope. The outside-intended-use exception requires developer §1702 compliance. Other business contract terms and insurance are preserved subject to applicable law. No actual term is assessed. | S001 F-future §1707(7)(a)–(d). |
| R100-P1-C096 | Separate state-law liability remains; Part 17 compliance is not a defense to other-law noncompliance; ADMT use does not excuse state/federal obligations, including discrimination and consumer protection. | S001 F-future §1707(8)–(9). |
| R100-P1-C097 | Insurers and affiliated entities subject to §10-3-1104.9 receive compliance treatment in the practice of insurance; otherwise the specified §1704(3) disclosure applies to the extent applicable. Insurer employment uses are not removed. Current insurance-definition/rule predicates remain incomplete. | S001 F-future §1708(1)–(2); S018. |
| R100-P1-C098 | The listed §§1701–1706 exclusion concerns qualifying HIPAA covered entities doing business in Colorado and business associates’ services to them, except employment decisions. A covered entity that is a provider must operate from a Colorado location for this subsection. A general advanced-technology notice to patients remains required and may be combined with other notices. | S001 F-future §1708(3)(a)–(c); S014 limited chain. |
| R100-P1-C099 | Covered-ADMT financial-assistance eligibility decisions, including referenced discounted care, retain specified decision/ADMT-role, information-type, correction, and applicable human-review disclosures. Compliance may use an advance general disclosure or notice within 30 calendar days after an adverse outcome; duplicate process is unnecessary if the required information/review opportunities are provided. Underlying assistance eligibility is not decided. | S001 F-future §1708(3)(d)–(e); §25.5-3-502 unexamined. |
| R100-P1-C100 | The listed §§1701–1706 exclusion also covers FDA-overseen devices and specified manufacturer research/development, including referenced clinical investigations. HIPAA-inconsistent disclosure is not required; applicable federal health privacy controls conflicts. GLBA’s clause concerns prohibited disclosure of nonpublic personal information, not a blanket financial-actor exemption. | S001 F-future §1708(4)–(6). |
The cure provision, relative-fault provision, sector treatment, and no-new-private-action provision perform different legal functions. None supplies a completed liability or remedy finding. Colorado Revised Statutes 2026+2
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C101 | A person may not use advertising/interface/output wording implying AI output is provided/endorsed by or equivalent to specified authorized psychotherapy professionals; representing that AI provides psychotherapy; or representing confidentiality so a reasonable user would believe it comparable to therapist-client protections. No actual representation is examined. | S001 current/future §1705.2(1)(a)–(c); S006 §3. |
| R100-P1-C102 | The section does not impose liability on an authorized psychotherapy professional for AI defects/failures attributable to a developer/deployer; their liability is governed by applicable consumer-protection law. This clause is not general immunity or a complete liability rule. | S001 §1705.2(2). |
| R100-P1-C103 | Accredited/approved education/training use is preserved only under the listed sole-purpose, no-public/client-tool representation, and authorized review or control conditions. Solely research use requires a registered-IRB setting and no consumer offer or psychotherapy outside research. | S001 §1705.2(3)–(4); S006 §3; narrow §12-245-224.5(5)(a) context. |
| R100-P1-C104 | The wellness-tool exclusion lists self-help, homework, navigation, coaching, meditation, journaling/reflections, psychoeducation, goals/progress, session preparation/summaries, mood/mindfulness/breathing, crisis directories, safety planning, and other wellness tools, with no diagnosis/treatment and clear non-substitute-for-clinical-care disclosure. The FDA-authorized/approved/cleared/enforcement-discretion alternative has its own intended-use predicate and the same two conditions. | S001 §1705.2(5)(a)–(b). |
| R100-P1-C105 | This section separately incorporates the AI definition from §12-245-224.5 and psychotherapy from §12-245-202. The latter concerns the described diagnosis/treatment/testing/assessment/counseling in a planned professional relationship, may include regular or single assessment/brief intervention, and directs narrow construction. No clinical classification follows. | S001 §1705.2(6); S010 §12-245-202(10), (14), §12-245-224.5(1)(b). |
These are included because they are present in the selected Part, not because this pass investigates mental-health treatment or professional licensing. Colorado Revised Statutes 2026+3
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C106 | Conversational AI service is publicly accessible AI primarily simulating human conversation/interaction through adaptive text, visual, or aural communication. Operator covers an entity that develops and publicly makes it available, or offers it to a consumer. An app store/search engine is not an operator solely for providing access. | S001 current §1701(4.5), (10.5); future (4.5), (15.5); S005 §1. |
| R100-P1-C107 | Definition exclusions separately cover: primarily developer/researcher tools; primarily commerce/transactional assistance; narrow-topic tools with specified prohibited-output/dialogue limits; primarily business operations/productivity/analysis/research/training/technical-assistance tools; qualifying device assistants with content/dialogue limits; solely internal business tools; game or location-entertainment features confined to their topics; specified HIPAA uses; Article 64 entities; limited school tools not designed for companionship/dependence; and qualifying embedded non-chatbot features, including the referenced social-media category. Each exclusion retains its own purpose/capability conditions. | S001 current/future §1701(4.5)(b)(I)–(XII); S005 §1. |
| R100-P1-C108 | Minor means consumer under 18; self-harm means intentional self-injury with or without intent to cause death. “Visual depiction” incorporates §2256(5). “Explicit sexual conduct” and “intimate digital depiction” incorporate unavailable current Title 13 definitions; the Part expressly excludes evidence-based medical information/factual reproductive-health descriptions from the former. Those missing underlying definitions remain held. | S001 current §1701(7.5), (10.1), (10.3), (10.7), (13), future corresponding definitions; S013; S019. |
| R100-P1-C109 | Account holder, minor account holder, and minor user are defined. Operators must use commercially reasonable or generally accepted age-estimation methods, not willfully disregard clear and convincing minor-age information, and treat estimated age/range as knowledge for this section. The lead age-estimation sentences do not themselves carry the subsequent January 1 introductory limitation. | S001 current §1708(1)–(2) lead; future §1710(1)–(2); S005 §2. |
| R100-P1-C110 | From January 1, 2027, known-minor disclosure must respond to identity prompts and use one specified route: persistent screen disclaimer, intermittent audio for no-screen products, or beginning-of-interaction disclosure repeated at least once every three continuous-interaction hours. | S001 current §1708(2)(a); future §1710(2)(a). |
| R100-P1-C111 | Known-minor duties prohibit unpredictable-interval points/rewards intended to increase engagement; require technically feasible prevention of listed sexual depictions, encouragement, and interactions; require reasonable measures against simulated dependence/isolation, including human/sentience claims and specified romantic simulations; and require the two sexual-conduct response protocols. Underlying incorporated content definitions remain partly unresolved. | S001 current §1708(2)(b)–(f); future §1710(2)(b)–(f). |
| R100-P1-C112 | Known-minor duties incorporate Part 13 privacy/data requirements and require minor and parent/guardian account/privacy tools, including control over retaining earlier interactions for personalization and using personal data for training. Full minor-privacy law is not completed here. | S001 current §1708(2)(g)–(h); future §1710(2)(g)–(h). |
| R100-P1-C113 | From January 1, 2027, general user disclosure is required at the first interaction each day, at least every three continuous-interaction hours or persistently, and in response to identity prompts. This is distinct from the known-minor alternative structure. | S001 current §1708(3); future §1710(3). |
| R100-P1-C114 | From January 1, the service must have the specified suicide/self-harm response protocol, crisis-service referral excluding law enforcement as that referral category, and repeated/severe-indicator escalation. It may not falsely represent outputs as provided/endorsed by or equivalent to the listed licensed health/legal/mental-health professionals or qualified dietitians. This is a source description, not individual crisis or treatment advice. | S001 current §1708(4)–(5); future §1710(4)–(5). |
| R100-P1-C115 | On and after July 1, 2027, annual reports cover preceding-calendar-year referral-notification count, specified implemented protocols, and additional AG-determined efficacy/reliability metrics. Reports exclude user identifiers/personal information; the AG posts report data; evidence-based measurement is required. No specific recurring annual filing day, actual metric, or validated efficacy result is established. | S001 current §1708(6); future §1710(6). |
| R100-P1-C116 | The chatbot section preserves the referenced information-access rights, protects secrets/confidential/proprietary/legally protected information, and does not authorize unconstitutional moderation. The future Part-wide definitions omit the old general AI-system definition while the harmonized chatbot definition still uses the term; §1705.2’s separate incorporation does not automatically resolve that Part-wide construction issue. | S001 current §1708(7), future §1710(7), future §1701, §1705.2(6). |
The conversational-service provisions are not automatically a regime for every recommendation, customer-support interface, or debt-technology product. Their category exclusions and separate temporal clauses matter. Colorado Revised Statutes 2026+5
| Claim ID | Qualified proposition | Exact source/pinpoint |
|---|---|---|
| R100-P1-C117 | Current §1703’s opt-out reference is expressly conditional on applicability. The incorporated profiling category concerns automated evaluation/analysis/prediction of specified personal aspects; §1306 separately addresses profiling producing legal or similarly significant effects. Future §1705’s correction reference is a different incorporation, with express exception overrides. | S001 §1303(20), §1306(1)(a)(I)(C); current §1703(4)(a)(III); future §1705(1). |
| R100-P1-C118 | Section 1306’s complete request framework includes designated secure/reliable methods, normal interaction, authentication, no compelled new account, relevant opt-out/agent provisions, access/correction/deletion/portability, refusal explanation, and internal appeal. Its fee and authentication qualifications and §1307 limitations matter. The report does not silently transplant every Part 13 procedure into every Part 17 review right. | S001 complete §§1306–1307; §1303(2), (7), (11), (17), (20). |
| R100-P1-C119 | Section 1306 supplies a 45-day response period and possible additional 45 days for complexity/number; appeal response has 45 days with a possible additional 60 days and required timely extension notice. Portability has the stated two-times-per-calendar-year condition; fee treatment for a second/subsequent request within 12 months incorporates a separate fee authority not completed here. These are privacy-source periods, not established universal AI appeal deadlines. | S001 §1306(1)(e), (2)(a)–(d), (3). |
| R100-P1-C120 | Deidentified-data treatment requires inability reasonably to infer/link plus specified safeguards, public commitment, and recipient-contract conditions. Section 1307 preserves stated limits on reidentification/association and a pseudonymous-data exception conditioned on separation and effective controls. No actual data provenance or classification is established. | S001 §1303(11), (17), complete §1307. |
| R100-P1-C121 | The incorporated dietitian category requires the specified qualifying degree route and either at least 900 hours of planned continuous supervised preprofessional experience or the specified registered-dietitian certificate. No actual credential is examined. | S001 §6-1-707(1)(b)(I)–(II); current §1708(5)(d)/future §1710(5)(d). |
| R100-P1-C122 | HIPAA’s selected definitions include covered-entity categories and detailed business-associate inclusions/exclusions, but their nested program, PHI, arrangement, and statutory predicates are not all read. Part 17’s cross-reference therefore cannot establish an actual health-sector exclusion here. | S014 §160.103 selected complete definitions; C051, C098–C100, C107. |
| R100-P1-C123 | Current employment, insurance, specified sexual-content, and Article 64 definition chains remain incomplete because the official current bodies failed access; other listed external standards/regimes remain deliberately unexamined. Dependent application is held, not supplied from a label or older text. | S017–S020; dependency table below. |
| R100-P1-C124 | Financial/lending services are express current and future subject categories, but coverage still requires the applicable actor, consumer, system, use, decision, and exception predicates. Future credit-notice coordination and GLBA disclosure preservation do not prove federal compliance or universal financial-sector exclusion. | C017–C023, C053, C060–C075, C082, C100; S001 exact provisions. |
| R100-P1-C125 | Current reasonable-care/program/impact-assessment provisions and future documentation/record/notice/review provisions are materially different. Their textual replacement does not prove that risk assessment or antidiscrimination obligations disappear under every other law, or that incurred liabilities vanish. | S001 current §§1702–1703 versus future §§1702–1705, 1707–1709; S007 §2-4-303. |
| R100-P1-C126 | Defined coverage, an operative duty, an exception, a rebuttable presumption, an affirmative defense, exclusive public enforcement, and an existing-law liability rule are distinct propositions. None independently proves actual classification, compliance, liability, eligibility, relief, or a private remedy. | S001 current §§1701–1707; future §§1701–1709; conditions in the preceding claims. |
| R100-P1-C127 | No examined Part 17 clause supplies a repayment formula, credit-approval probability, financial-return measure, model-performance guarantee, settlement result, or individual suitability finding. This is a bounded observation about the complete selected bodies, not all law or all technology. | S001 complete current/future Part 17; S002–S006 selected adopted bodies. |
Each row supplies a qualified comparison, its authority, the missing predicate, and the inference that must not be drawn.
| Comparison | Supported distinction; claims and exact authority | Missing authority/predicate | Adverse inference to avoid |
|---|---|---|---|
| Commercial AI label versus legal system category | Current machine-inference definition differs from future personal-data/computation ADMT definition. C014, C060–C061; S001 current §1701(2), future §1701(2). | Actual system functions/use; incorporated data classification. | Every product called AI is covered, or every product not called AI is excluded. |
| Definition versus classification | Definitions identify predicates; no real actor/system/decision was examined. C019–C023, C066–C070, C126. | All application facts. | A generic category example proves actual status. |
| Current substantial factor versus future material influence | Current capability/assistance/generated-factor elements differ from future non-de-minimis use and outcome effect. C020, C066; S001 respective §1701 clauses. | Actual use/effect; final interpretive rules. | Capability alone proves future material influence. |
| Inclusion versus exclusion | Domain inclusion does not eliminate procedural, technical, purpose, actor, or sector exclusions. C017, C021–C022, C049–C055, C061–C068. | Complete cumulative exclusion predicates. | Financial involvement alone resolves coverage. |
| Cumulative versus alternative conditions | Small-deployer conditions are cumulative; specified disclosure methods and some research/definition routes are alternatives. C042, C061, C068, C110. | All predicates for the particular route. | Satisfying one small-entity condition satisfies the whole exception. |
| Current consumer versus future consumer | Residence-only wording is replaced by an incorporation plus express employment/Colorado-opportunity extensions. C018, C064, C069. | Current incorporated employee/employer definitions and actual territorial facts. | A single residence rule answers both versions. |
| Current risk governance versus future documentation | Current §1703 prescribes risk programs and assessments; future §1703 concerns records, alongside other future duties. C033–C037, C073–C077, C125. | Other-law obligations and savings application. | No future risk obligation exists anywhere. |
| Duty versus rebuttable presumption | Reasonable care is the duty; specified compliance supports an AG-enforcement presumption. C026, C032, C058. | Actual compliance; applicable adopted rules. | A framework label proves care or absence of discrimination. |
| Defense versus exemption | Current §1706 defense requires discovery/cure plus framework conditions; §1705 exclusions have separate predicates and burden. C055–C057. | Framework contents, qualifying actions, actual cure. | An assessment automatically grants immunity. |
| Predecision versus adverse-outcome notice | Timing, content, and delivery differ; future adverse notice runs from making the decision, not receipt. C038–C040, C078–C079. | Actual trigger and final rules. | One generic notice satisfies every stage. |
| Correction versus change of judgment | Future correction concerns factual/material data inaccuracies; opinions, predictions, scores, and protected evaluations are excluded. C085–C087. | Data category and applicable process. | A correction right guarantees a different decision. |
| Human review versus favorable result | Current technical-feasibility/best-interest wording differs from future commercially reasonable meaningful review. C039, C071, C085. | Complete applicable version and actual predicates. | Human review guarantees approval or reversal. |
| Credit notice coordination versus federal-law satisfaction | Combined notice is permitted only when the federal notice also satisfies the state requirements. C082; S001 future §1704(6). | Complete ECOA/Regulation B/FCRA chain. | A state clause certifies federal compliance. |
| Financial-sector compliance treatment versus universal exemption | Current prudential treatment is conditional; future GLBA language protects against prohibited disclosure. C053–C054, C100. | Qualifying supervision, standards, categories, actual conduct. | Every bank, affiliate, or regulated financial actor is exempt. |
| Health exclusion versus financial-assistance disclosure | Future covered-entity treatment retains specified financial-assistance notices and review information. C098–C100. | HIPAA and discounted-care predicates. | Health-sector status eliminates every notice duty or establishes assistance eligibility. |
| Public authority versus private contract | Statute supplies public duties; future §1707 regulates specified indemnity effects while preserving other terms/insurance. C088, C095–C096. | Actual contract, underlying law, liability predicates. | Any contract can waive the statute, or every indemnity term is void. |
| Enactment versus commencement versus application | Approval, conditional effective date, duty-start date, decision-date application, and reporting start are separate. C004–C008. | Unexamined transition events and later law. | A signature or web-update date is every operative date. |
| Current statute versus agency explanation | Adopted May 29 approval conflicts with the AG’s July 1 summary; proposal descriptions are not adopted rules. C011–C012. | Authenticated final rule and later publication chain. | An agency page silently amends the Act. |
| Public enforcement versus private remedy | Exclusive statutory enforcement and no-new-action clauses coexist with preservation of existing law and future relative-fault rules. C056–C058, C088–C096. | Standing, cause of action, proof, process, remedies. | Either automatic damages or universal immunity. |
| Colorado component versus broader A100 | This selected state framework neither establishes another jurisdiction’s law nor resolves the federal financial/product regimes. C124–C127. | Authorities listed in the parent-gap table. | Component completion equals parent or operational acceptance. |
Scope of this register: quantities relied upon in this report. Section numbers, bill identifiers, page/index locators, and standard identifiers are citations, not financial or performance measurements. Pure publication metadata is separately identified. No deadline is calculated.
For periods described merely as “days,” the selected clause is not silently converted into business days or calendar days. General counting, service, holiday, and tolling rules remain unexamined unless the source itself supplies the convention.
| Measurement ID | Source quantity; actor/object and trigger | Boundary, exceptions, convention, and missing facts | Authority |
|---|---|---|---|
| M001 | October 28, 2026 PDT: actual research access. | Observation date only; not enactment/effectiveness. | Source register and access record; C001. |
| M002 | May 17, 2024 approval; original February 1, 2026 duty dates. | Approval/compiler effect distinguished from original prospective application; later dates amended. | S002 §§1–3; C004. |
| M003 | August 28, 2025 approval; compiler November 25, 2025 effect; amended June 30, 2026 triggers. | Original date formula and referendum alternative remain separate. | S003 §§1–4; C005. |
| M004 | 90-day period after final legislative adjournment; 12:01 a.m. following expiration. | SB25B-004 conditional commencement; timely petition changes route to November 2026 approval and official vote declaration. No event calculation. | S003 §4. |
| M005 | May 14, 2026 passage/approval; January 1, 2027 default effectiveness. | Listed clauses effective upon passage; default not applied to them. | S004 §5(1)–(2); C006. |
| M006 | Consequential decisions made on or after January 1, 2027. | Inclusive application boundary; actual decision event absent. | S004 §5(3). |
| M007 | May 29, 2026 chatbot approval; June 1 signed-format date; agency July 1 signing statement. | Approval and publication/version metadata differ; July 1 statement conflicts and is not adopted. | S005 approval/action; S015; C007, C011. |
| M008 | HB26-1263: 90 days, 12:01 a.m.; August 12, 2026 if adjournment May 13, 2026. | Timely referendum petition invokes November 2026 election/official declaration alternative. Compiler gives August 12; predicate events not independently researched. | S005 §3. |
| M009 | June 3, 2026 psychotherapy approval; same conditional 90-day/12:01 a.m./August 12-if-May 13 formula. | Applies to actions on/after applicable effective date; referendum alternative preserved. | S006 §4; C008. |
| M010 | July 2, 2026, 11:35 a.m. MDT Red Book update. | Compiler-index metadata, not substantive commencement. | S016. |
| M011 | Federal source cutoff October 20, 2026, P.L.119-134; eCFR currency October 26, 2026 and title amendment label October 6. | Compilation/title metadata only; no exhaustive later-law or definition-specific amendment finding. | S011–S014. |
| Measurement ID | Actor/object; source quantity and trigger | Boundary, cumulative conditions/exceptions, counting/delivery, absent facts | Authority |
|---|---|---|---|
| M012 | Current principal duties: on and after June 30, 2026. | Inclusive; relevant section and actor/system predicates required. | C026–C045; S001 §§1702–1704. |
| M013 | Developer public statement: update as necessary and no later than 90 days after intentional/substantial modification. | Accuracy duty can require earlier action; “days” not further defined here. | C029; §1702(4). |
| M014 | Developer discovery/report notice: without unreasonable delay, no later than 90 days after specified trigger. | Alternative discovery/credible-report predicates; AG and all known specified recipients. Not permission to wait 90 days. | C030; §1702(5). |
| M015 | AG developer-document request: no later than 90 days after request. | Prescribed form/manner; disclosure protection preserved. Receipt substitution not invented. | C031; §1702(7). |
| M016 | Current risk program: regular/systematic lifecycle review and updating. | No fixed numerical interval stated in this clause. | C033; §1703(2). |
| M017 | Assessments: at least annually and within 90 days after modification is made available. | Both frequencies matter; statutory alternatives/exemption remain. No calendar conversion. | C034–C036; §1703(3)(a)–(e). |
| M018 | Assessment records: at least three years following final deployment. | Minimum; final-deployment trigger absent. Not creation date. | C037; §1703(3)(f). |
| M019 | Deployment review: on or before June 30, 2026, and at least annually thereafter. | Inclusive initial date; distinct from assessment record retention. | C037; §1703(3)(g). |
| M020 | Current consumer notice: no later than deployment for the decision; before the decision. | Both source timing conditions preserved; no invented number of advance days. | C038; §1703(4)(a). |
| M021 | Small-deployer condition: fewer than 50 FTE employees. | Strict < 50; at deployment and throughout; all additional conditions required; only specified subsections excepted. | C042; §1703(6). |
| M022 | Current deployer discovery notice: no unreasonable delay and within 90 days after discovery. | Requires post-June-30 deployment and discovery of causation; not developer’s broader alternatives. | C043; §1703(7). |
| M023 | AG deployer-record request: no later than 90 days after request. | Prescribed form/manner; protections remain. | C044; §1703(9). |
| M024 | Current public statement: periodic update; prudential audit: regular audit. | No fixed numerical interval supplied by these clauses. External guidance unexamined. | C041, C053; §§1703(5), 1705(8). |
| M025 | Banking control: 25% or more of relevant voting securities, or the stated board-election control route. | Inclusive >= 25% for that branch; exact statutory context and other control branches matter. No actual holdings. | C054; S009 §11-101-401(23). |
| M026 | Future developer records: not less than three years after creation, or longer under applicable law. | >= 3 years; separate longer-law condition. | C076; future §1702(4). |
| M027 | Future deployer records: not less than three years after decision, or longer under applicable law. | Different trigger from developer/current assessment retention. | C077; future §1703. |
| M028 | Future update notice: within a reasonable time. | No fixed days supplied; public notes require direct notice to each deployer. | C074; future §1702(2). |
| M029 | Future initial notice: prior to covered use for material consequential influence. | No numerical lead time; public-notice alternative has accessibility/proximity conditions. | C078; future §1704(1)–(2). |
| M030 | Future adverse notice: within 30 days after making the decision. | Decision, not receipt, triggers; statute here says days, not expressly calendar days. | C079; future §1704(3). |
| M031 | AG notice/correction rules: on or before January 1, 2027. | Inclusive deadline; authority/mandate early-effective; actual adoption not established. | C080, C087; future §§1704(4), 1705(3). |
| M032 | Cure: within 60 days after receipt of violation notice. | Pre-action cure only if deemed possible; knowing/repeated-violation exception. | C089; future §1706(3)(a)–(c). |
| M033 | In-action cure mitigation: within 60 days after receipt of written notice. | Court may consider; no guaranteed result. | C089; future §1706(3)(d). |
| M034 | AG report: beginning January 2028, then each January. | Specified action/cure counts, separated by actor category; no actual count or exact January day supplied. | C090; future §1706(3)(e). |
| M035 | Entire future §1706(3) repealed January 1, 2030. | Applies to whole subsection, including report paragraph; savings/actual liability remain separate. | C090; future §1706(3)(f). |
| M036 | Rulemaking: at least one public hearing. | Minimum count plus public notice, written-comment opportunity, and §24-4-103 compliance. | C092; future §1706(5)(c). |
| M037 | Financial-assistance disclosure: advance general disclosure or within 30 calendar days after adverse outcome. | Express calendar-day unit; either route must supply required information; no actual date calculation. | C099; future §1708(3)(e). |
| M038 | Minor: under 18 years. | Strict < 18; consumer/category and knowledge predicates remain. | C108–C110; current/future §1701. |
| M039 | Known-minor duties: on and after January 1, 2027. | Does not rewrite the separately worded age-estimation lead sentences. | C109–C112; current §1708(2)/future §1710(2). |
| M040 | Minor disclosure alternative: start each interaction and at least once every three hours of continuous interaction. | Alternative to persistent-screen/intermittent-audio route; identity-prompt response also required. No continuous-use event supplied. | C110. |
| M041 | General-user disclosure: first interaction each day, then at least once every three hours continuous use or persistent disclosure, plus identity prompts. | No time zone or interrupted-session counting rule supplied in selected text. | C113. |
| M042 | Other chatbot duties: on and after January 1, 2027. | Crisis protocol and professional-representation rules have their own stated application. | C114. |
| M043 | Chatbot reports: on and after July 1, 2027, annually, covering referral count in the preceding calendar year. | Not converted to a universal “due every July 1” deadline. User identifiers excluded; no count/denominator supplied. | C115. |
| M044 | Dietitian experience branch: not less than 900 hours. | >= 900 hours, planned/continuous/supervised, plus qualifying degree; certificate alternative preserved. | C121; §707(1)(b). |
| M045 | Incorporated privacy response: 45 days after receipt, possible 45 additional days. | Complexity/number necessity and extension notice within initial period; no automatic extension. Scope into Part 17 held. | C119; §1306(2). |
| M046 | Incorporated privacy appeal response: 45 days after receipt, possible 60 additional days. | Stated necessity and initial-period notice; not a universal AI review clock. | C119; §1306(3). |
| M047 | Portability: not more than twice per calendar year; specified fee treatment for second/subsequent request within 12 months. | Different units/windows; fee calculation authority unexamined; no fee amount inferred. | C119; §1306(1)(e), (2)(c). |
| M048 | No source-stated repayment, return, acceptance, or model-accuracy formula in selected Part. | Negative finding limited to complete examined bodies. No invented performance threshold or financial model. | C127. |
These are analytical branches, not operational instructions or individualized decision trees. “Answered boundary” means the statutory condition can be stated; it does not mean an actual application is resolved. This table also supplies branch-level coverage status.
| Branch/status | Supported conditional rule; exact claims/source | Missing authority or predicate | Adverse inference to avoid | Next permissible generic public-law inquiry |
|---|---|---|---|---|
| B01 — Current version: partial | Distinguish current and future bodies and early-effective clauses. C001–C006; S001 headings, S004 §5. | Exhaustive later-law chain. | The 2024 signed Act is the complete October 2026 law. | Check subsequent officially adopted Part 17 changes and their complete commencement clauses. |
| B02 — Conditional commencement: partial | Petition-sensitive Acts use express alternative triggers. C005, C007–C008; S003 §4, S005 §3, S006 §4. | Complete constitutional chain; unexamined predicate events. | Compiler date proves every constitutional predicate. | Read complete Colorado constitutional commencement/referendum provisions from a readable official source. |
| B03 — Failed incorporation: unresolved | Failed current bodies cannot establish incorporated definitions. C123; S017–S020. | Current readable definitions. | Failure means repeal or no obligation. | Obtain ordinary publicly readable official versions of the exact failed clauses. |
| B04 — Person/business nexus: answered boundary | Current/future role definitions require their listed person and Colorado-business predicates. C013, C019, C067; S001 respective §1701. | Actual legal role and territorial facts. | An organizational label proves coverage. | Read only indispensable generic construction of “doing business” if a later component requires it. |
| B05 — AI versus ADMT: answered boundary | Current inference-based AI and future personal-data computational ADMT differ. C014, C060–C061. | Actual functionality; future AI-term construction gap. | All software satisfies both definitions. | Examine adopted generic interpretation of the specific definition without inspecting a product. |
| B06 — Consumer category: partial | Current resident definition differs from future express extensions. C018, C064, C069. | Current employee/employer incorporation. | Every commercial or employment exclusion carries forward unchanged. | Read current §8-4-101(5)–(6) and its material amendments. |
| B07 — Financial domain: answered boundary | Financial/lending services are listed, but other coverage predicates remain cumulative. C017, C065, C124. | System/use/consumer/exception predicates. | Every financial decision or debt tool is covered. | Read final generic domain/material-influence rules once authenticated. |
| B08 — High-risk factor: answered boundary | Current high-risk status requires consequential decision plus making/substantial factor. C020. | Actual use and decision character. | Mere availability or capability proves all elements. | Examine public construction of §1701(9), (11), without actual-system inquiry. |
| B09 — Procedural-task exclusion: answered boundary | Narrow-task and pattern-detection branches retain stated intent/human-review conditions. C021. | Intended function and review predicate. | “Administrative” is a universal exclusion. | Read any adopted generic rule interpreting these exact branches. |
| B10 — Listed technology: answered boundary | Current listed technologies reenter the high-risk category when the specified decision condition is met. C022. | Actual consequential use. | A spreadsheet or hosting label conclusively excludes coverage. | Compare current §1701(9)(b)(II) with future §1701(2)(b), preserving versions. |
| B11 — Modification/learning: answered boundary | Current learning exception needs all four conditions; future modification uses a different material-use definition. C023, C070. | Predetermination, documentation, use-change predicates. | Every update or learning event is exempt or automatically material. | Read final generic update/modification interpretation for the applicable version. |
| B12 — Developer versus deployer: answered boundary | Roles and duty-specific triggers differ; one role definition does not itself establish every duty. C019, C026, C032, C067. | Role/use predicates. | Developer and deployer duties are interchangeable. | Trace only the applicable role definition and duty clause together. |
| B13 — Current documentation: answered boundary | Required categories and feasible-artifact/internal-use conditions govern. C027–C028. | Availability, feasibility, unaffiliated-recipient predicates. | Any model card proves compliance. | Read adopted documentation rules and referenced assessment requirements. |
| B14 — Discovery reporting: answered boundary | Developer alternative triggers differ from deployer causation discovery. C030, C043; §§1702(5), 1703(7). | Discovery/report/cause predicates and prescribed form. | The same event starts every 90-day period. | Read final generic reporting instructions and exact triggering clauses. |
| B15 — Reasonable care/presumption: partial | Presumption requires statutory and applicable-rule compliance; rebuttable and AG-specific. C026, C032, C058. | Final rules and actual compliance. | Presumption means no discrimination occurred. | Authenticate complete adopted presumption rules, not a framework label. |
| B16 — Risk program: partial | Program must satisfy iterative lifecycle and contextual reasonableness requirements. C033. | Referenced framework content and equivalence. | Citation to NIST/ISO establishes compliance. | Read the exact public framework provisions relied upon; keep inaccessible/private-standard content held. |
| B17 — Assessments: answered boundary | Assessment frequency, contents, comparable-set and other-law alternatives are conditional. C034–C037. | Actual system set, similarity, modification/final-deployment triggers. | Any assessment satisfies the statute or grants immunity. | Read adopted generic assessment rules and complete alternative-law conditions. |
| B18 — Small deployer: answered boundary | <50 FTE is only one condition; exception affects only (2), (3), (5). C042. | Every continuing condition. | Small size removes notice, care, or reporting duties. | Examine exact §1703(6) and any adopted counting definition; no actual headcount query. |
| B19 — Current predecision notice: partial | Timing/content apply before decision; opt-out information only if applicable. C038, C117. | Part 13 scope and applicable opt-out predicates. | Every consumer has an unconditional AI opt-out. | Complete the narrow Part 13 applicability/exemption chain if separately authorized. |
| B20 — Current adverse review: answered boundary | Correction and appeal have technical-feasibility and best-interest/life-safety qualifications. C039–C040. | Actual adverse event, feasibility, delivery predicates. | Appeal guarantees reversal or unlimited delay. | Read precise adopted generic appeal/delivery instructions. |
| B21 — Public statements and timing: answered boundary | Developer modification deadline differs from deployer periodic updating. C029, C041; M013, M024. | Actual update/modification facts. | Every public statement has a 90-day update cycle. | Compare exact subsection-specific update duties. |
| B22 — Law/research/privilege: partial | Preserved activities have purpose, facial-recognition, research, and privilege conditions. C046–C048. | External ethics, privacy, privilege, constitutional predicates. | Research or legal-purpose labeling creates immunity. | Read only the exact relied-on public research or privilege incorporation. |
| B23 — Federal involvement: partial | Approval/standards, contract, and acquisition routes differ; employment/housing exceptions remain. C049–C050. | Authority, standards equivalence, intended decision category. | Federal involvement always excludes Part 17. | Read the specific generic federal authority/standard before asserting that route. |
| B24 — Insurance: unresolved application | Current and future insurance treatments have distinct conditions and future employment limitation. C052, C097. | Current Title 10 definitions/rules. | Insurance regulation establishes blanket exemption. | Read complete §§10-1-102(13), 10-14-102, 10-3-1104.9 and indispensable adopted rules. |
| B25 — Banking: partial | Prudential guidance must be equivalent/stricter and require audit/mitigation. C053–C054. | Full nested definitions and qualifying published guidance. | Any charter, regulator, or affiliate relationship is sufficient. | Read complete applicable generic banking-category and guidance clauses. |
| B26 — Future material influence: answered boundary | Non-de-minimis use and outcome effect are cumulative. C066. | Actual use/effect; future adopted clarifications. | Any contact with an output proves material influence. | Authenticate §1706(5) rules on material influence. |
| B27 — Future developer exclusions: answered boundary | Research, internal-use, preceding-developer, and unknown-component-integration branches differ. C068. | Each branch’s intended-use, availability, modification, or knowledge predicates. | Internal development or component status is automatically exempt. | Read precise future §1701(8)(b) plus adopted interpretation. |
| B28 — Data category: partial | Personal/public/deidentified categories depend on linkage and source/safeguard conditions. C072, C120. | Actual provenance and nested privacy applicability. | A “public” or “anonymous” label resolves legal status. | Complete only relevant public definition and deidentification construction. |
| B29 — Future updates/retention: answered boundary | Reasonable-time notices and three-year periods have different actors/triggers. C074, C076–C077. | Actual creation/decision/update event and longer-law duty. | One retention start date governs all records. | Examine complete applicable record-retention and counting authorities generically. |
| B30 — Future notices: answered boundary | Prior-use notice and 30-day post-decision disclosure are separate; public-posting alternative has conditions. C078–C081. | Trigger, required information, final rules. | A public posting necessarily satisfies post-adverse duties. | Read adopted notice-content and delivery rules. |
| B31 — Credit notice coordination: partial | Combined federal/state notice must satisfy both applicable bodies. C082. | Complete federal notice applicability/content. | ECOA notice automatically satisfies Colorado law. | Independently read relevant ECOA/Regulation B/FCRA public clauses in a separate component. |
| B32 — Future correction/review: partial | Adverse outcome, material influence, request, factual/material data, and commercial reasonableness matter. C071, C085–C087. | Incorporated procedure and actual predicates. | Every score must be corrected or every decision reversed. | Read adopted §1705 rules and precise §1306 interaction. |
| B33 — Education: partial | Existing FERPA channels may suffice only under the stated conditions. C084, C087. | Complete FERPA category/procedure chain. | Any school process automatically satisfies Part 17. | Read indispensable FERPA inspection/amendment/channel provisions. |
| B34 — Health/assistance: partial | Employment exception, Colorado provider location, general notice, and financial-assistance disclosures remain. C098–C100. | HIPAA, discounted-care, FDA predicates. | Health exclusion proves assistance eligibility or eliminates all notices. | Read exact HIPAA definitions and §25.5-3-502 relevant clauses. |
| B35 — Secret/security withholding: answered boundary | Withholding protections differ by actor/section; specified notices and bases remain. C031, C044, C073, C081, C083. | Protected status and applicable law. | “Trade secret” excuses every duty without explanation. | Read the exact withholding clause and incorporated protection, without actual records. |
| B36 — Cure: answered boundary | Possibility determination, receipt trigger, knowing/repeated exception, discretionary mitigation, and sunset matter. C089–C090. | Actual predicates and broader procedure. | Every violation gets 60 days or cure guarantees no relief. | Read complete applicable enforcement procedure and savings provisions if separately needed. |
| B37 — Private remedy/fault: partial | No new Part 17 action coexists with preserved existing-law actions and relative-fault rules. C091–C094. | Cause of action, standing, causation, proof, remedies. | Automatic damages or complete immunity. | Examine only an independently authorized existing-law cause and its complete predicates. |
| B38 — Contract indemnity: answered boundary | Own-act discriminatory-liability shift is limited by the precise scope and outside-use exception. C095–C096. | Actual contract and existing-law liability, all absent. | Every commercial indemnity is void. | Read generic contract-construction authority only in a separately scoped component. |
| B39 — Psychotherapy: partial | Representation bans and training/research/wellness/FDA alternatives retain all conditions. C101–C105. | Professional/FDA/IRB predicates. | Wellness labeling establishes exclusion or clinical validity. | Complete only indispensable public definitions; hold clinical and licensing merits. |
| B40 — Conversational category: partial | Public conversation simulation and each distinct exclusion govern. C106–C107. | Content/function/purpose; Article 64/HIPAA chains. | Every customer-service or recommendation interface is covered. | Read unresolved incorporated categories and final generic chatbot definitions. |
| B41 — Minor/knowledge: answered boundary | Under-18 category, reasonable age estimation, knowledge rule, and different duty dates apply. C108–C110. | Actual category/knowledge; counting convention. | No stated age means no duty, or every duty starts on the same date. | Read complete adopted age-estimation interpretation if available. |
| B42 — Incorporated content terms: unresolved | Part 17 contains express content duties but current Title 13 definitions failed access. C108, C111; S019. | Complete current §13-21-1502(7), (10). | A familiar content label substitutes for the statutory definition. | Open those exact current official clauses and their material amendment notes. |
| B43 — Minor controls: partial | Reward-intent, technically feasible prevention, reasonable dependence safeguards, protocols, and privacy tools differ. C111–C112. | Incorporated definitions and full minor-privacy regime. | Any reward is prohibited or any protocol proves compliance. | Read the precise adopted generic implementation and Part 13 minor clauses. |
| B44 — Chatbot disclosures/reporting: answered boundary | Daily/three-hour/persistent disclosure alternatives and annual reporting have different triggers. C113–C115. | Actual events and final reporting format. | A report proves safeguards work or a fixed annual due day is supplied. | Authenticate final generic reporting instructions without requesting reports. |
| B45 — Repeal/savings: partial | Compiler harmonization and §2-4-303 preservation must be distinguished. C009–C010, C125. | Judicial construction and actual incurrence, both held. | Replacement extinguishes every earlier liability. | Read narrow generic savings/application authority if a later legal component requires it. |
| B46 — Rules/frameworks: unresolved | Delegation and references are present; complete adopted rules/standard contents are not authenticated. C012, C033, C057, C059, C080, C092. | Final public rule/adoption and precise framework provisions. | Proposed text or a standard name is operative proof. | Read final adopted public instructions and their effective clauses. |
| B47 — Debt technology: excluded beyond selected boundary | Financial-domain inclusion supplies only a conditional state AI connection. C124, C127. | Federal credit, collection, privacy, digital-asset, product-specific law. | Part 17 proves debt validity, forgiveness, or product legality. | Use the separate parent questions below. |
| B48 — Actual application/parent: excluded by scope | No facts or decisions are supplied; no acceptance follows from public-text analysis. C126–C127. | Every actual application predicate and remaining jurisdiction. | This report is a compliance, eligibility, or financial decision. | Continue only with separately scoped generic public-law research. |
All entry cells below are intentionally empty. This is a public-law reference structure, not an intake, assessment, compliance, eligibility, or decision instrument.
| Analytical field | Authority entry | Evidence entry | Analysis | Result |
|---|---|---|---|---|
| Authority and instrument title | ||||
| Version and compilation boundary | ||||
| Legal status | ||||
| Access date and read bounds | ||||
| Jurisdictional category | ||||
| Generic actor category | ||||
| Generic system category | ||||
| Consumer/category definition | ||||
| Covered domain | ||||
| Scope condition | ||||
| Cumulative predicates | ||||
| Alternative predicates | ||||
| Exception or exclusion | ||||
| Operative verb | ||||
| Duty and recipient category | ||||
| Incorporation and read completeness | ||||
| Quantity, unit, and base | ||||
| Trigger and counting convention | ||||
| Delivery or retention condition | ||||
| Enactment/commencement/application distinction | ||||
| Transition or savings provision | ||||
| Presumption or defense boundary | ||||
| Public enforcement boundary | ||||
| Private-remedy boundary | ||||
| Other-law dependency | ||||
| Currentness/history gap | ||||
| Application hold | ||||
| Exact next generic public-law inquiry |
The branch table supplies individual branch status. This table separately covers each numbered request and its material subquestions.
| Request/material subquestion | Status and finding | Claim/source/branch crosswalk | Missing evidence and exact next permissible inquiry |
|---|---|---|---|
| 1.1 Actual title and organization | Answered within examined compilation. Current and future inventories established. | C001–C003; S001; B01. | Later adopted changes: check exact subsequent official enactments. |
| 1.2 Complete current selected Part | Answered as a body read. All displayed current definitions, duties, exceptions, additions, notes read. | C013–C059, C101–C116; S001–S003, S005–S006. | Incorporated-regime gaps are separate, below. |
| 1.3 Complete successor | Answered as a body read. Entire displayed successor read; no selected-Part remainder omitted. | C060–C116; S001, S004–S006. | Final implementing rules and construction remain partial. |
| 1.4 Operative/future/conditional classification | Partial. Adopted clauses and compiler distinctions established; exhaustive later/constitutional chain not certified. | C004–C012; B01–B03, B45–B46. | Read failed constitutional clauses and any later adopted public law. |
| 2.1 Current AI/risk/roles/consumer | Answered conditional definitions. No actual classification. | C013–C025; B04–B12. | Actual facts remain excluded; generic judicial construction unexamined. |
| 2.2 Future ADMT/material influence/domains | Answered conditional definitions. | C060–C072; B26–B28. | Final generic rules and employee/employer incorporation. |
| 2.3 Every material definition exclusion | Partial overall. Part 17 exclusions read completely; nested current definitions failed in specified titles. | C016, C021–C023, C061–C069, C107–C108, C123; S017–S019. | Read exact current failed clauses; do not substitute amendments/snippets. |
| 2.4 Territorial/resident nexus | Answered text; application held. Current/future difference preserved. | C018–C019, C064–C067; B04, B06. | Generic “doing business” construction only if separately needed. |
| 3.1 Current developer documentation/publication/reporting | Answered text and timing. | C026–C031; M012–M015; B13–B15. | Adopted forms/rules and actual predicates remain open. |
| 3.2 Current risk management/assessments | Partial. Complete statutory program/assessment rules read; external frameworks not completed. | C032–C037; M016–M019; B16–B18. | Exact public framework and adopted rule clauses. |
| 3.3 Current notice/correction/appeal | Answered selected text; incorporated opt-out partial. | C038–C045, C117–C120; B19–B21. | Complete narrow Part 13 applicability and final procedures. |
| 3.4 Future documentation/updates/records | Answered selected text. | C073–C077; M026–M028; B29. | Longer-law retention and adopted interpretation remain unexamined. |
| 3.5 Future notices/correction/review | Partial overall. Statutory duties complete; federal/FERPA/privacy interactions incomplete. | C078–C087; B30–B33. | Exact external clauses and adopted notice/review rules. |
| 3.6 Therapy/chatbot duties | Partial overall. Selected bodies complete; content/HIPAA/Article 64/minor-privacy chains incomplete. | C101–C116; B39–B44. | Exact failed/current incorporated clauses. |
| 4.1 Current exclusions/small-deployer conditions | Answered statutory predicates. | C042, C046–C055; B18, B22–B25. | External qualification and actual facts remain absent. |
| 4.2 Framework defenses/presumptions | Partial. Conditions and limited legal function established; actual standard compliance not. | C026, C032–C033, C057–C059; B15–B16, B46. | Complete relied-on public standards and adopted rules. |
| 4.3 Financial/insurance/health carveouts | Partial. Complete Part text; several incorporated authorities incomplete. | C051–C054, C082, C097–C100, C122–C123; B24–B25, B31, B34. | Current Title 10, HIPAA nested clauses, discounted-care and federal notice law. |
| 4.4 Public enforcement/cure/private-action limits | Answered narrow text; broader remedies held. | C056–C059, C088–C096; B36–B38. | Complete independent cause/process/remedy authority before any positive remedy claim. |
| 5.1 AI credit-underwriting connection | Answered bounded inclusion. Financial/lending domain plus remaining predicates. | C017, C053, C065, C082, C100, C124; B07, B25, B31. | Federal credit/underwriting rules separate. |
| 5.2 Other debt-technology extension | Excluded beyond text-supported category connection. | C107, C124–C127; B40, B47. | Separate collection, negotiation, digital-asset, embedded-credit authorities. |
| 6.1 Original adoption and delay | Answered adopted clauses; constitutional event chain partial. | C004–C005; S002–S003; M002–M004. | Failed constitutional body and unexamined conditional events. |
| 6.2 Repeal/reenactment and early clauses | Answered adopted body/application. | C006; S004 §§1–6; M005–M006. | Exhaustive later enactments/judicial application remain held. |
| 6.3 Added provisions and renumbering | Answered compiler/adopted distinction. | C007–C009; S005–S007; M007–M009. | Judicial reconciliation of any ambiguity remains unexamined. |
| 6.4 Savings | Answered general clause; actual operation unresolved. | C010, C125; S007 §2-4-303; B45. | Actual incurred liability excluded; narrow generic construction could be separate. |
| 6.5 Agency/currentness mismatch | Answered discrepancy; final rule unresolved. | C011–C012; S015–S016; B46. | Authenticate final adopted rule, publication, and effective text. |
| 7. Comparisons | Answered with qualifications. Comparison table covers category, conditions, duties, legal effect, history, and parent boundaries. | C124–C127 plus row-specific claims/sources. | Every listed application/other-law gap retained. |
| 8. Measurements | Answered for every quantity relied upon. No actual calculation or fixed period invented. | M001–M048, exact claims/sources. | General counting/tolling/service rules and actual triggers remain absent. |
| 9. Branches | Answered format and substantive coverage. B01–B48 carry rule, source, missing evidence, adverse inference, next inquiry, and status. | All branch rows. | Branch-level partial/unresolved status retained. |
| 9. Blank worksheet | Answered. All entry/analysis/result cells empty. | Section 7. | No actual record is requested or implied. |
| 10. Remaining parent area | Explicitly open. Separate next inquiries supplied below. | C124–C127; B47–B48; Section 10. | All other jurisdictions, products, actual facts, and operational conclusions. |
| Log entry | What was actually read | What was not claimed |
|---|---|---|
| L01 — S001 | Official 2026 delivery index; complete current and future Part 17 HTML; selected complete incorporated Title 6 clauses listed in S001. | Whole Title 6; every external incorporation; PDF pixel verification; exhaustive later-law audit. |
| L02 — S002 | Complete original session-law §§1–3; partial signed-format comparison. | Independent corroboration from two formats; whole historical policy dossier. |
| L03 — S003 | Complete delay Act §§1–4, including full conditional effective clause. | Referendum or adjournment-event record investigation. |
| L04 — S004 | Complete replacement Act §§1–6, including adopted text, appropriation section, early-effective list, application, and safety clause. | Actual funding use, complete insurance law, or completed rulemaking. |
| L05 — S005 | Complete chatbot Act §§1–3; approval line and bill action/version metadata. | Actual operator conduct, age estimation, report, hearing event, or user data. |
| L06 — S006 | Complete Part 17 amendment and effective/application clauses; narrow definitional cross-reference passages. | Whole professional-practice regime or clinical interpretation. |
| L07 — S007–S010 | Exact construction, trade-secret, banking, and psychotherapy definitions identified in the register. | Whole titles, annotations as judicial holdings, actual categories or qualifications. |
| L08 — S011–S014 | Exact federal definitions/context listed in the register. | Whole federal statutory/regulatory regimes or complete nested HIPAA chain. |
| L09 — S015–S016 | Generic AG explanatory page and selected official change-index material. | Adopted-rule status for drafts, empirical implementation, or independent corroboration of the same Act. |
| Log entry | Exact endpoint or grouped source | Observed failure/limit and treatment |
|---|---|---|
| F01 — Initial statute index | https://leg.colorado.gov/agencies/office-legislative-legal-services/colorado-revised-statutes, redirected to https://content.leg.colorado.gov/agencies/office-legislative-legal-services/colorado-revised-statutes | Verification/JavaScript page rather than statute body. No bypass. The ordinary official 2026 download index in S001 was readable. |
| F02 — S004 signed Act | https://www.leg.colorado.gov/bill_files/116489/download | Retrieval failed, reporting content length 11,791,344. Complete official session-law alternative read. |
| F03 — S003 and S005 signed formats | Exact signed URLs in S003 and S005. | PDF metadata returned but no parsed body lines. Complete session-law alternatives read; no unseen signed-page claim. |
| F04 — Titles 7 and 12 HTML | Exact HTML URLs in S008 and S010. | Retrieval-size failures. Selected clauses read in their ordinary official PDFs. |
| F05 — Titles 8, 10, 13 and Constitution | Every exact format URL in S017–S020. | Size, parsing, or unsupported-format failures as logged. Dependent current definitions/constitutional claims held. |
| F06 — Preliminary OLRC §234 route | https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title42-section234&num=0&edition=prelim | HTTP 500. Ordinary canonical current route later readable as S011. |
| F07 — Preliminary OLRC §2000a route | https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title42-section2000a&num=0&edition=prelim | HTTP 404. A separate ordinary view.xhtml route displayed maintenance; canonical current S012 read. |
| F08 — Preliminary OLRC §2256 route | https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title18-section2256&num=0&edition=prelim | HTTP 404. Canonical current S013 read. |
| F09 — Earlier federal versions encountered | Earlier-version §234 and §2256 routes were encountered before the current canonical pages. | They were not used to represent October 20 compilation currency. Final reliance is S011–S013; same-instrument versions are grouped. |
| F10 — PDF screenshots | Attempts on final pages of S004–S006. | Returned image-display markers without inspectable pixels in the available result. Only parsed-text reading is claimed. Printed pages and zero-based indices remain separately recorded. |
| F11 — Discovery-only material | Generic statutory searches returned bill amendments, older codifications, and other summaries. | No search snippet, proposed amendment, unofficial summary, participant material, or older definition was substituted for a complete current official body. |
| F12 — Final-rule status | S015 and generic official-source discovery. | No complete final adopted rule authenticated. This is an unresolved source-status limit, not a finding that no rule exists. |
Failures do not establish repeal, withdrawal, lack of protection, compliance, or authorization to bypass a gate.
| Open dependency | Precise unresolved proposition | Next permissible generic public-law inquiry |
|---|---|---|
| Current employment definitions | Exact future employee/employer category, including any current amendments and nested exclusions. | Read complete current §8-4-101(5)–(6) and materially applicable adopted amendments. |
| Insurance definitions and rules | Which generic categories and practices satisfy current/future insurance compliance treatment. | Read §§10-1-102(13), 10-14-102, 10-3-1104.9 and indispensable adopted rules in full relevant context. |
| Title 13 sexual-content and health categories | Complete meanings of §13-21-1502(7), (10), and the referenced Article 64 entity category. | Obtain readable official current bodies and exact material amendment clauses. |
| Constitutional commencement | Full independent meaning of the Acts’ referendum/safety/commencement dependencies. | Read the exact current Colorado constitutional clauses from an ordinary official readable source. |
| Final implementing rules | Additional current/future documentation, notice, review, reporting, presumption, and framework conditions. | Read complete adopted rule text, adoption instrument, and effective/application clauses; distinguish proposals. |
| Referenced frameworks | Exact contents and equivalence of NIST, ISO, or AG-designated alternatives. | Read only the public framework clauses indispensable to a later claim; preserve unavailable/private-standard text as unresolved. |
| Privacy incorporation | Full Part 13 applicability, minors’ provisions, fee authority, and exact procedural interaction. | Read complete narrow scope/exemption and minor-privacy clauses; do not assume every Part 13 clock governs every Part 17 right. |
| HIPAA/FDA/health assistance | Nested covered-entity/business-associate/provider definitions, FDA status, and discounted-care rights. | Read exact incorporated generic clauses, including relevant §25.5-3-502 provisions, before a dependent conclusion. |
| Banking category chain | Federal credit-card-bank and complete federal/out-of-state credit-union predicates. | Read the exact incorporated federal and state definitions, including 12 U.S.C. §1841(c)(2)(F), if relied upon. |
| Future AI-term construction | Meaning of “artificial intelligence system” in the harmonized future chatbot definition after omission of the old Part-wide definition. | Read adopted generic construction or amendment addressing that term; do not import §1705.2’s section-specific definition automatically. |
| Savings and temporal liability | Whether any pre-replacement liability survives in a particular setting. | Generic savings/application construction may be separately researched; no actual events or cases are supplied here. |
| Judicial/enforcement/remedy chain | Standing, causes, proof, jurisdiction, penalties, damages, immunity, review, and actual enforcement. | Separately scope a generic public-law inquiry before making any affirmative remedy statement. |
| Parent seed | Exact next generic question; present hold |
|---|---|
| AI credit underwriting and fair lending | What complete federal credit-decision and antidiscrimination provisions apply to the relevant generic activity, independently of Colorado Part 17? No underwriting or applicant assessment. |
| Adverse-action notices | What are the complete ECOA/Regulation B and FCRA triggers, content, timing, and exceptions before using future §1704(6)’s coordination clause? |
| Credit reporting and data accuracy | Which complete federal duties concern source data, disputes, permissible purposes, and correction? Part 17 is not a completed reporting-law analysis. |
| Privacy and security | Which complete federal/Colorado privacy and security provisions govern the generic data category and activity? No actual provenance, collection, disclosure, or security finding. |
| Open banking and consumer financial data | What adopted, effective public rules govern generic access, authorization, use, and revocation? No account or permission inquiry. |
| Automated debt negotiation | Which public consumer-protection, representation, licensing, debt-adjustment, and contract rules apply to the generic activity? No authority to negotiate or settlement entitlement inferred. |
| Automated collection | Which complete federal and relevant jurisdictional collection/communication rules govern the generic conduct? No actual debt, communication, deadline, or collection permission. |
| Digital assets and DeFi | Which public product/activity definitions and regulatory boundaries apply? No asset, protocol, issuer, valuation, or transaction classification. |
| Subscription, embedded, and wage-related credit | Which generic credit/payment/wage definitions, exclusions, and effective rules apply? No product or financial outcome conclusion. |
| Provider contracts and commercial allocation | What public contract and statutory limits apply independently of future §1707’s narrow indemnity provision? No actual or model contract. |
| Federal preemption | Which exact federal provision conflicts with or displaces a specific state requirement, if any? No general preemption conclusion. |
| Other states | What complete adopted and effective public law governs the separately identified generic component? Colorado definitions are not exported. |
| Territorial, tribal, local, and foreign law | What jurisdiction-specific public authority supplies scope, applicable law, and institutional competence? No all-country or all-jurisdiction coverage. |
| Technical capability and model evaluation | What authorized evidence would establish a generic technical property? No testing, dataset, benchmark, output inspection, or actual classification was performed. |
| Economic efficacy and consumer outcomes | What suitable empirical evidence would support any claimed benefit, harm, cost, or effectiveness? Statutory duties and reporting metrics do not supply causal results. |
| Debt validity, payment, settlement, discharge, tax, and credit effects | What independent substantive law governs each question? This component supplies no debt-relief outcome or financial recommendation. |
| Operational or publication acceptance | What separately authorized review would be required before any application or publication decision? No component, parent, jurisdiction-wide, operational, or publication acceptance is supplied. |
| Check | Result |
|---|---|
| Prior reports used as premises? | No. This investigation used freshly opened public sources for R100. |
| Complete selected Part read? | Yes, for both versions displayed in the official 2026 compilation, including the psychotherapy and conversational-service additions. |
| Current versus future separated? | Yes. Current June 30 application language, adopted January 2027 replacement, early-effective clauses, and chatbot-specific dates are distinguished. |
| Complete material main adopted acts read? | Yes for S002–S005; complete selected amendment/application clauses for S006. Read bounds are explicit. |
| All incorporations completed? | No. Exact failures and unexamined nested regimes are identified; dependent findings remain held. |
| Agency summary treated as law? | No. The signing-date conflict is preserved and resolved only to the adopted-source date; draft-rule descriptions remain nonfinal evidence. |
| Parsed text represented as pixels? | No. No visual verification of the PDF pages is claimed. |
| Same-source formats treated as independent corroboration? | No. They are grouped by instrument. |
| Exact connectors and exceptions preserved? | Checked for current/future definitions, small-deployer conditions, framework defense, notice alternatives, sector clauses, cure conditions, and chatbot timing. |
| Quantities converted into invented deadlines or models? | No. Units, triggers, alternatives, and undefined counting conventions are recorded; no actual calculation. |
| Actual or invented identifying records queried or created? | No such substantive inquiry or record is part of this investigation. |
| Blank worksheet genuinely blank? | Yes. Entry, analysis, and result cells contain no facts or findings. |
| Actual classification, compliance, eligibility, liability, or financial result? | None supplied. |
| Independent review or full later-history certification? | Neither claimed. This is the researcher’s own bounded source-and-cross-reference check. |
Final scope disposition: The selected public statutory bodies and principal adopted transition instruments have been investigated and compared. The report expressly retains incomplete incorporations, final-rule authentication, constitutional-transition, judicial-construction, later-history, and all actual-application gaps. The remaining A100 parent area stays open.
END R100 PASS-01.
Captured cells with original header handling and explicitly labeled bounded correction overlays. Downloaded JSON retains original cells. Tables may contain source limitations, historical examples and identified corrections; the complete reading supplies context.
Read the evidence with its boundaries. These are saved research components, including revisions. A scoped coordinator review checks selected evidence; it does not certify every claim, a complete jurisdiction, current law or individual applicability. Dates and access limits remain attached to the records.
Source ID; issuer and title · Complete literal HTTPS URLs · Exact read bounds · 6 data rows
| Source ID; issuer and title | Complete literal HTTPS URLs | Exact read bounds | Version, legal status, commencement/application, and limits |
|---|---|---|---|
| R100-P1-S001 — Colorado General Assembly, Office of Legislative Legal Services; 2026 Colorado Revised Statutes, Title 6 | Official delivery index: https://content.leg.colorado.gov/agencies/office-legislative-legal-services/2026-crs-titles-download. Officially linked HTML: https://olls.info/crs/crs2026-title-06.htm. PDF alternative: https://olls.info/crs/crs2026-title-06.pdf. | Complete displayed current and future Part 17, HTML lines 6516–7652, including definitions, operative clauses, source credits, and material editor’s notes. Separately read selected complete clauses of §§6-1-102(18), 6-1-105(1)(hhhh), future (uuuu), 6-1-1303, 1304(2)(k), (n), (o), complete §§1306–1307, §707(1)(b), and §1601(4)(a), as specified below. Title 6 PDF was located but not used for a whole-document or pixel read. | Official index identifies amendments, additions, and repeals of the 2026 Second Regular Session. It links the olls.info delivery files. Current and prospective text are separately marked. This authenticates the examined compilation, not an exhaustive intervening-law or judicial audit. |
| R100-P1-S002 — Colorado General Assembly; SB24-205, original adopted Act | Bill/version page: https://leg.colorado.gov/bills/sb24-205. Signed format: https://leg.colorado.gov/bill_files/47770/download. Session law: https://leg.colorado.gov/laws/session-laws/SB24-205/198/download. | Complete session-law §§1–3, printed pp.1199–1217; zero-based PDF indices 0–18. Signed format was only partially read; the complete reliance is on the session-law format. | Approved May 17, 2024; compiler identifies May 17 effectiveness. Original principal duty dates were February 1, 2026. Those dates were subsequently amended. §3 is the safety clause. Same Act in different formats, not independent corroboration. |
| R100-P1-S003 — Colorado General Assembly; SB25B-004, postponement Act | Bill page: https://leg.colorado.gov/bills/SB25B-004. Signed format: https://leg.colorado.gov/bill_files/90530/download. Session law: https://leg.colorado.gov/laws/session-laws/SB25B-004/3/download. | Complete §§1–4, printed pp.8–11; PDF indices 0–3. Signed-format extraction returned no body text; session law was readable. | Approved August 28, 2025. Replaces material February 1, 2026 dates with June 30, 2026. Compiler reports November 25, 2025 effectiveness. §4 contains a 90-day referendum-petition condition and an alternative post-election trigger; that condition is preserved below. |
| R100-P1-S004 — Colorado General Assembly; SB26-189, repeal and reenactment | Bill page: https://www.leg.colorado.gov/bills/SB26-189. Signed endpoint: https://www.leg.colorado.gov/bill_files/116489/download. Session law: https://www.leg.colorado.gov/laws/session-laws/SB26-189/131/download. | Complete §§1–6, printed pp.569–585; PDF indices 0–16. Signed endpoint failed; complete adopted session law was readable. §4 appropriation was read for the Act’s structure and early-effective treatment; no funding conclusion or allocation is made. | Approved May 14, 2026. §5(1): January 1, 2027 default. §5(2): specified clauses effective upon passage. §5(3): applies to consequential decisions made on or after January 1, 2027. §6 safety clause. |
| R100-P1-S005 — Colorado General Assembly; HB26-1263, conversational AI additions | Bill/version/action page: https://leg.colorado.gov/bills/HB26-1263. Signed format: https://leg.colorado.gov/bill_files/116851/download. Session law: https://leg.colorado.gov/laws/session-laws/HB26-1263/208/download. | Complete §§1–3, printed pp.1197–1203; PDF indices 0–6. Signed-format extraction returned no body text. Bill action and session-law approval line read for date reconciliation. | Approved May 29, 2026. Compiler reports August 12, 2026 effectiveness, subject to §3’s express conditional commencement. Specified operator duties begin January 1, 2027; annual reporting begins on and after July 1, 2027. The signed-document version date June 1 is not approval. |
| R100-P1-S006 — Colorado General Assembly; HB26-1195, selected psychotherapy amendment | https://leg.colorado.gov/laws/session-laws/HB26-1195/358/download | Complete §3, adding §6-1-1705.2, printed pp.2158–2160/PDF 5–7; complete §4, p.2160/PDF 7; narrow §2 definition and relevant cross-reference context, including AI definition p.2154/PDF 1 and §12-245-224.5(5)(a) context pp.2156–2157/PDF 3–4. Not a whole-Act substantive analysis. | Approved June 3, 2026. Conditional August 12, 2026 commencement under §4; application to actions taken on or after applicable effectiveness. Compiler harmonizes §1705.2 with the January 2027 replacement. |
Source ID; issuer/title · Complete literal HTTPS URL · Exact read bounds and status · 10 data rows
| Source ID; issuer/title | Complete literal HTTPS URL | Exact read bounds and status | Limits |
|---|---|---|---|
| R100-P1-S007 — Colorado OLLS; 2026 Title 2 | https://olls.info/crs/crs2026-title-02.htm | Complete §2-4-301, multiple amendments; complete §2-4-303, repeal/revision savings. Current 2026 compilation. | No judicial construction or actual accrued liability determined; no whole Title 2 history. |
| R100-P1-S008 — Colorado OLLS; 2026 Title 7 | Readable PDF: https://olls.info/crs/crs2026-title-07.pdf. Failed HTML: https://olls.info/crs/crs2026-title-07.htm. | Complete relevant introductory language and §7-74-102(4), printed p.496/PDF index 495. | Parsed text only. No actual trade-secret qualification; no full trade-secret regime or amendment history. |
| R100-P1-S009 — Colorado OLLS; 2026 Title 11 | https://olls.info/crs/crs2026-title-11.htm | Complete selected definitions in §11-101-401(3.5), (5), (20), (23), (27), (37), (39), (46), (50), (58) and §11-30-101(1)(a). | Federal credit-card-bank incorporation and complete federal/out-of-state credit-union chains remain unexamined. No actual charter, affiliation, supervision, or compliance. |
| R100-P1-S010 — Colorado OLLS; 2026 Title 12 | Readable PDF: https://olls.info/crs/crs2026-title-12.pdf. Failed HTML: https://olls.info/crs/crs2026-title-12.htm. | §12-245-202(10), (14)(a)–(b), printed p.999/PDF 998; §12-245-224.5(1)(b), p.1031/PDF 1030; narrow (5)(a) context p.1033/PDF 1032. | Selected definitions and cross-reference only; no psychotherapy licensure, clinical, or professional-practice determination. |
| R100-P1-S011 — Congress/OLRC; 42 U.S.C. §234 | https://uscode.house.gov/us/usc/119-134/t42/s234/ | Complete (d)(1)–(2), health professional/health-care services. Displayed compilation through P.L.119-134, October 20, 2026. | Broader public-health-emergency liability provisions not adopted into this report. |
| R100-P1-S012 — Congress/OLRC; 42 U.S.C. §2000a | https://uscode.house.gov/us/usc/119-134/t42/s2000a/ | Complete (a)–(e) read for context; reliance narrowly on (e) and its exception concerning facilities made available to customers or patrons of covered establishments. Same displayed federal cutoff. | No actual private-club, establishment, discrimination, or jurisdiction finding. |
| R100-P1-S013 — Congress/OLRC; 18 U.S.C. §2256 | https://uscode.house.gov/us/usc/119-134/t18/s2256/ | Complete introductory language and (5), “visual depiction.” Same displayed federal cutoff. | No other criminal-law elements or actual content classification. |
| R100-P1-S014 — HHS; 45 C.F.R. §160.103, eCFR | https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160/subpart-A/section-160.103 | Complete selected definitions of business associate, covered entity, health care, health care clearinghouse, health care provider, and health plan. Displayed Title 45 currency October 26, 2026; title amendment label October 6, 2026. | Nested statutory/program, PHI, organized-arrangement, and related HIPAA predicates are not all completed. A title-level amendment label is not a definition-specific effective date. |
| R100-P1-S015 — Colorado Attorney General; AI rulemaking explanation | https://coag.gov/ai/ | Complete generic page read. It describes the adopted replacement and a proposed/interim rulemaking process. | Not an adopted rule. Its statement that HB26-1263 was signed July 1, 2026 conflicts with S005’s May 29 approval. No final rule body authenticated here. |
| R100-P1-S016 — Colorado OLLS; Red Book 2026 | https://content.leg.colorado.gov/agencies/office-legislative-legal-services/red-book-2026 | Introductory status explanation and selected Part 17 change entries. Page identifies a final version updated July 2, 2026, 11:35 a.m. MDT. | Legislative change index, not substitute for adopted text or evidence of every later event. |
Source ID · Exact attempted original endpoints · Observed result; dependent hold · 4 data rows
| Source ID | Exact attempted original endpoints | Observed result; dependent hold |
|---|---|---|
| R100-P1-S017 — 2026 Title 8 | https://olls.info/crs/crs2026-title-08.htm; https://olls.info/crs/crs2026-title-08.pdf; https://olls.info/crs/crs2026-title-08.docx | HTML exceeded retrieval-size limit; PDF failed with reported content length 10,645,792; DOCX unsupported by retrieval. Current §8-4-101(5)–(6) employee/employer definitions not authenticated. A 2026 amendment search result was discovery only, not substituted. |
| R100-P1-S018 — 2026 Title 10 | https://olls.info/crs/crs2026-title-10.htm; https://olls.info/crs/crs2026-title-10.pdf; https://olls.info/crs/crs2026-title-10.docx | HTML exceeded size limit; PDF parsing failed; DOCX unsupported. Full current §§10-1-102(13), 10-14-102, and 10-3-1104.9 not read. S004’s adopted addition of §10-3-1104.9(3)(e) was read. |
| R100-P1-S019 — 2026 Title 13 | https://olls.info/crs/crs2026-title-13.htm; https://olls.info/crs/crs2026-title-13.pdf; https://olls.info/crs/crs2026-title-13.docx | HTML exceeded size limit; PDF parsing failed; DOCX unsupported. Current §13-21-1502(7), (10) and Article 64 category chain not authenticated. Older adopted-text discovery was not used as proof of current definitions. |
| R100-P1-S020 — Colorado Constitution compilation | https://olls.info/crs/crs2026-title-00.htm; https://olls.info/crs/crs2026-title-00.pdf | HTML exceeded size limit; PDF parsing failed. Independent full constitutional commencement/referendum and speech-clause analysis remains held. The Acts’ own complete effective-date language and compiler dates are reported separately. |
Section · C-current: Artificial Intelligence · F-future: Automated Decision-Making Technology in Consequential Decisions · 11 data rows
| Section | C-current: Artificial Intelligence | F-future: Automated Decision-Making Technology in Consequential Decisions |
|---|---|---|
| 6-1-1701 | Definitions | Definitions |
| 6-1-1702 | Developer duty to avoid algorithmic discrimination—required documentation | Developer responsibilities—documentation |
| 6-1-1703 | Deployer duty to avoid algorithmic discrimination—risk-management policy and program | Deployer record keeping |
| 6-1-1704 | Disclosure of an AI system to consumer | Deployer disclosures—point-of-interaction notice, public posting, post-adverse-outcome disclosures, legislative declaration, trade secrets, other law, accessibility, rules |
| 6-1-1705 | Compliance with other legal obligations—definitions | Consumer rights—correction, human review and reconsideration, rules |
| 6-1-1705.2 | AI systems and psychotherapy services—prohibited practices and definitions | Harmonized psychotherapy provision retained |
| 6-1-1706 | Enforcement by Attorney General | Enforcement, deceptive trade practice, cure, no private right, joinder, reporting, repeal |
| 6-1-1707 | Rules | Liability, fault allocation, joint-and-several-liability limit, indemnification, existing law |
| 6-1-1708 | Conversational AI services—operator duties, minors, disclosures, reports, definitions | Other legal obligations—insurers, covered entities, disclosures |
| 6-1-1709 | No corresponding current body displayed | No new private right; other law |
| 6-1-1710 | No corresponding current body displayed | Conversational AI provision relocated/harmonized by compiler |
Claim ID · Qualified proposition · Exact source and pinpoint · 12 data rows
| Claim ID | Qualified proposition | Exact source and pinpoint |
|---|---|---|
| R100-P1-C001 | The examined official 2026 compilation is current through the legislative session identified by its publication index; actual access was October 28, 2026 PDT. That does not establish an exhaustive later-law or judicial chain. | S001, official download-index introduction and Title 6 status material. |
| R100-P1-C002 | The compiler displays the complete C-current Part under “Artificial Intelligence,” including §§1701–1708 and §1705.2, with principal existing sections marked effective until January 1, 2027. | S001, current Part heading and section/editorial notes. |
| R100-P1-C003 | The compiler also displays the complete F-future Part under the ADMT title, §§1701–1710 plus §1705.2, including harmonized additions. It is adopted future text, not merely a proposal. | S001, future Part heading/notes; S004 §1; S005–S006. |
| R100-P1-C004 | SB24-205 originally added Part 17 and the associated deceptive-trade-practice entry. Its original February 1, 2026 application language is historical after the adopted delay. | S002 §§1–3; S003 §§1–3. |
| R100-P1-C005 | SB25B-004 changes the specified dates to June 30, 2026. Its §4 uses the day after expiration of 90 days after final adjournment, at 12:01 a.m., subject to a timely referendum-petition alternative. Compiler-reported November 25, 2025 effectiveness is distinct from that conditional enacted formula. | S003 §§1–4; S001 source notes. |
| R100-P1-C006 | SB26-189 generally takes effect January 1, 2027 and applies to consequential decisions made on or after that date. New §§1704(4), 1705(3), 1706(6), the insurance-rulemaking addition, and Act §§4–6 take effect upon passage. | S004 §§1, 3, 5(1)–(3), 6; approval May 14, 2026. |
| R100-P1-C007 | HB26-1263’s approval is May 29, 2026. Its Act-level effective clause is conditional; the compiler reports August 12, 2026. The enacted text separately specifies January 1, 2027 duties and July 1, 2027 reporting applicability. | S005 §§1–3 and approval line; S001 current §1708/future §1710. |
| R100-P1-C008 | HB26-1195’s selected Part 17 amendment is approved June 3, 2026; §4 supplies conditional commencement and application to actions on or after applicable effectiveness. Compiler notes identify August 12, 2026 and future harmonization. | S006 §§3–4; S001 §1705.2 notes. |
| R100-P1-C009 | The compiler expressly harmonizes the 2026 additions. Section 2-4-301 directs harmonization of multiple amendments if possible and supplies effective-date/passage rules if irreconcilable. This report does not adjudicate a conflict. | S001 future §§1701, 1705.2, 1710 notes; S007 §2-4-301. |
| R100-P1-C010 | Repeal, revision, amendment, or consolidation does not release, extinguish, or alter an incurred penalty, forfeiture, or liability unless expressly provided; the former text remains available for the stated enforcement purpose. Actual incurrence and temporal application remain absent. | S007 §2-4-303, complete body. |
| R100-P1-C011 | The AG explanation’s July 1, 2026 signing statement for HB26-1263 conflicts with the adopted Act and bill-action record showing May 29. The adopted source governs the date reported here; the discrepancy remains visible. | S015; S005 approval line and bill action. |
| R100-P1-C012 | No complete final implementing-rule body, exhaustive post-compilation enactment chain, constitutional-transition chain, or judicial history was authenticated. Proposed/interim rulemaking descriptions are not treated as adopted obligations. | S015–S020 and failure log; limits on S001–S014. |
Claim ID · Complete material rule or definition, with limits · Exact source/pinpoint · 13 data rows
| Claim ID | Complete material rule or definition, with limits | Exact source/pinpoint |
|---|---|---|
| R100-P1-C013 | Article 1’s “person” includes the listed individual and legal/commercial forms, including persons with a joint or common interest. This definition alone does not determine governmental coverage, actual organizational form, or authority. | S001 §6-1-102 introductory clause and (18). |
| R100-P1-C014 | An AI system is machine-based; for an explicit or implicit objective it infers from inputs how to generate outputs—including content, decisions, predictions, or recommendations—that can influence physical or virtual environments. A commercial AI label is not the statutory test. | S001 C-current §1701(2). |
| R100-P1-C015 | Algorithmic discrimination requires AI use resulting in unlawful differential treatment or impact disfavoring an individual/group based on actual or perceived age, color, disability, ethnicity, genetic information, limited English proficiency, national origin, race, religion, reproductive health, sex, veteran status, or another state/federal protected classification. The definition does not itself complete the underlying unlawfulness test. | S001 C-current §1701(1)(a). |
| R100-P1-C016 | The definition excludes specified high-risk-system offer/license/use solely for self-testing/law compliance or pool expansion/diversity/historical-discrimination redress; it also references nonpublic private-club acts/omissions. Incorporated §2000a(e) itself contains a qualification for facilities made available to patrons of covered establishments. A “private” label alone is insufficient. | S001 §1701(1)(b)(I)–(II); S012 §2000a(e), read with (b)–(d). |
| R100-P1-C017 | A consequential decision must have a material legal or similarly significant effect on provision, denial, cost, or terms in the listed fields: education, employment, financial/lending services, essential government services, health-care services, housing, insurance, or legal services. | S001 C-current §1701(3)(a)–(h). |
| R100-P1-C018 | C-current “consumer” is an individual who is a Colorado resident. Residence and individuality are actual predicates, not findings made here. | S001 C-current §1701(4). |
| R100-P1-C019 | “Deploy” means use of a high-risk AI system. A deployer is a person doing business in Colorado that deploys one; a developer is a person doing business in Colorado that develops or intentionally and substantially modifies an AI system. The developer definition and particular high-risk duties must both be considered. | S001 C-current §1701(5)–(7). |
| R100-P1-C020 | High-risk AI makes or is a substantial factor in making a consequential decision when deployed. “Substantial factor” cumulatively assists the decision, is capable of altering its outcome, and is AI-generated; it includes specified AI output concerning a consumer used as a basis for the decision. | S001 C-current §1701(9)(a), (11)(a)–(b). |
| R100-P1-C021 | The high-risk definition excludes an AI system intended for a narrow procedural task, or for detecting decision patterns/deviations without an intended replacement or influence on a previously completed human assessment absent sufficient human review. | S001 C-current §1701(9)(b)(I). |
| R100-P1-C022 | Listed technologies are excluded unless, when deployed, they make or substantially contribute to a consequential decision: non-facial-recognition antifraud; anti-malware/virus; AI games; calculators; cybersecurity; databases/storage; firewalls; domain registration; website loading; networking; spam/robocall filters; spell-checking; spreadsheets; web caching/hosting or similar technology; and the specified natural-language information/referral/recommendation/question technology with an accepted-use policy prohibiting discriminatory or harmful content. | S001 C-current §1701(9)(b)(II)(A)–(R). |
| R100-P1-C023 | Intentional/substantial modification is a deliberate change producing a new reasonably foreseeable algorithmic-discrimination risk. The learning exception requires all listed conditions: post-availability/deployment learning; change from that learning; predetermination by the deployer/contracted assessor at the initial assessment; and inclusion in technical documentation. | S001 C-current §1701(10)(a)–(b). |
| R100-P1-C024 | Incorporated health-care services concern diagnosis, prevention, treatment, or health assessment/care provided by a health professional or under professional supervision. The incorporated professional is licensed, registered, or certified under federal or state law. No actual provider or service classification is established. | S001 §1701(8); S011 §234(d)(1)–(2). |
| R100-P1-C025 | The incorporated trade-secret definition covers specified secret and valuable business/professional information, with measures taken to prevent general availability except for selected limited-purpose access. Merely calling information proprietary is not a finding that this definition is satisfied. | S001 current §1701(12), future (17); S008 §7-74-102(4). |
Claim ID · Qualified statutory instruction · Exact source/pinpoint · 20 data rows
| Claim ID | Qualified statutory instruction | Exact source/pinpoint |
|---|---|---|
| R100-P1-C026 | On and after June 30, 2026, a high-risk developer must use reasonable care against known or reasonably foreseeable algorithmic-discrimination risks arising from intended and contracted uses. Compliance with the section and applicable AG rules supplies a rebuttable, AG-enforcement-specific presumption—not a finding of no discrimination. | S001 §1702(1); S003 §1. |
| R100-P1-C027 | Subject to §1702(6), the developer must make available to the deployer/other developer: foreseeable and known harmful uses; training-data-type summaries; known/foreseeable limitations and risks; purpose, benefits, uses, and information necessary for §1703; evaluation/mitigation before availability; data governance, suitability, bias and mitigation; outputs; foreseeable-deployment mitigation; appropriate/inappropriate use and human monitoring; and reasonably necessary output/performance-risk documentation. | S001 §1702(2)(a)–(d), including all subclauses. |
| R100-P1-C028 | To the extent feasible, documentation or artifacts must support the deployer/contractor’s impact assessment, subject to the disclosure limitation. A developer that is also the deployer need not generate this documentation unless the system is provided to an unaffiliated deployer. | S001 §1702(3)(a)–(b). |
| R100-P1-C029 | A clear, readily available public website statement must describe currently developed/modified and available high-risk-system types and management of known/foreseeable risks. Update as needed for accuracy and no later than 90 days after an intentional/substantial modification. | S001 §1702(4). |
| R100-P1-C030 | Developer reporting is triggered by testing that discovers a deployed system caused or is reasonably likely to have caused discrimination, or a credible deployer report that it caused discrimination. Notice goes to the AG in the prescribed form and all known deployers/other developers, without unreasonable delay and no later than 90 days after the specified discovery/report. | S001 §1702(5)(a)–(b). |
| R100-P1-C031 | Developer disclosures under (2)–(5) need not disclose a trade secret, legally protected information, or information creating a security risk. The AG may require the (2) statement/documentation within 90 days of request; it is excluded from CORA disclosure, may be designated proprietary/secret, and submission does not waive applicable attorney-client/work-product protection. | S001 §1702(6)–(7). |
| R100-P1-C032 | On and after June 30, a high-risk deployer has a reasonable-care duty against known/foreseeable algorithmic-discrimination risks and a rebuttable presumption conditioned on the section and AG rules. The developer’s “intended and contracted uses” wording is not inserted into this deployer clause. | S001 §1703(1). |
| R100-P1-C033 | Subject to the limited small-deployer exception, the deployer must maintain an iterative risk-management policy/program specifying principles, processes, and personnel; it must identify, document, mitigate, and regularly/systematically review risks across the lifecycle. Reasonableness considers the referenced frameworks or AG-designated framework, size/complexity, systems’ nature/scope/intended uses, and data sensitivity/volume. One program may cover multiple systems. Framework contents/compliance remain unexamined. | S001 §1703(2)(a)–(b). |
| R100-P1-C034 | Subject to (3)(d), (3)(e), and (6), deployment on/after June 30 triggers an impact assessment; deployed systems require assessments at least annually and within 90 days after an intentional/substantial modification is made available. This wording is not converted into an invented universal pre-deployment deadline. | S001 §1703(3)(a). |
| R100-P1-C035 | Assessments must include, at minimum and to the extent reasonably known/available: purpose/use/context/benefits; risk and mitigation analysis; input/output categories; customization data if used; performance metrics/known limitations; transparency measures; and post-deployment monitoring/user safeguards, oversight, use, and learning processes. Post-modification assessments add consistency/variation from developer-intended uses. | S001 §1703(3)(b)–(c). |
| R100-P1-C036 | One assessment may cover a comparable system set. An assessment under another applicable law/regulation suffices only if reasonably similar in scope and effect. These are conditional alternatives, not automatic recognition of any existing assessment. | S001 §1703(3)(d)–(e). |
| R100-P1-C037 | Retain the most recent assessment, associated records, and all prior assessments for at least three years following final deployment. Separately, on or before June 30, 2026 and at least annually thereafter, review each deployment to ensure it is not causing discrimination. | S001 §1703(3)(f)–(g). |
| R100-P1-C038 | By deployment for a consequential decision and before the decision, notify the consumer of high-risk use; give purpose, decision nature, deployer contact information, plain-language system description, and access instructions for the public statement; provide profiling opt-out information if applicable under the specified privacy provision. | S001 §1703(4)(a)(I)–(III); §1306(1)(a)(I)(C). |
| R100-P1-C039 | An adverse decision triggers principal reasons, AI contribution, processed-data types and sources, an opportunity to correct incorrect personal data, and an appeal opportunity. Human review is required if technically feasible, except when an appeal opportunity is not in the consumer’s best interest, including life/safety risk from delay. This is not a guaranteed reversal. | S001 §1703(4)(b). |
| R100-P1-C040 | Required communications must be direct, plain-language, in all languages ordinarily used for the specified consumer business communications, and disability-accessible. If direct provision is not possible, availability must be reasonably calculated to ensure receipt. | S001 §1703(4)(c). |
| R100-P1-C041 | Subject to (6), the deployer’s readily available website statement must identify current high-risk-system types, risk management, and the nature, source, and extent of information collected/used; it must be periodically updated. The clause supplies no fixed update interval. | S001 §1703(5). |
| R100-P1-C042 | The exception covers only (2), (3), and (5) and requires all conditions at deployment and throughout use: fewer than 50 full-time-equivalent employees; no own data used to train; system used for developer-disclosed intended uses and continuing to learn from other data; and consumer availability of a developer-provided assessment containing substantially similar required information. | S001 §1703(6)(a)–(c). |
| R100-P1-C043 | For deployment on/after June 30 followed by discovery that the system caused discrimination, the deployer must notify the AG in the prescribed form without unreasonable delay and within 90 days of discovery. This trigger is distinct from the developer’s credible-report/likely-causation alternatives. | S001 §1703(7). |
| R100-P1-C044 | Listed deployer disclosures need not reveal secrets or legally protected information; withholding under (8) or the text’s actual reference to §1705(5) requires consumer notice and a basis. AG-requested policy, assessment, or records are due within 90 days; CORA exclusion, designation, and privilege nonwaiver are specified. The cross-reference is preserved, not silently “corrected.” | S001 §1703(8)–(9). |
| R100-P1-C045 | From June 30, a deployer or other developer making available an AI system intended to interact with consumers must ensure interaction disclosure, unless interaction with AI would be obvious to a reasonable person. The provision is not limited by its text to high-risk systems. | S001 §1704(1)–(2). |
Claim ID · Qualified rule · Exact source/pinpoint · 14 data rows
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C046 | Part 17 preserves ability to comply with law and governmental process, reasonably and in good faith cooperate with law enforcement, address legal claims, take immediate life/physical-safety steps, undertake specified security/fraud/integrity activities by means other than facial recognition, assist compliance, recall products, and repair functionality errors. These clauses do not establish an actual qualifying purpose. | S001 §1705(1)(a)–(f), (i), (2). |
| R100-P1-C047 | Public/peer-reviewed scientific or statistical research must satisfy public-interest, other ethics/privacy-law, and 45 C.F.R. Part 46 or relevant FDA conditions. Pre-market/deployment research/testing/development is separately preserved except real-world testing. Those external research regimes remain unexamined. | S001 §1705(1)(g)–(h). |
| R100-P1-C048 | Duties do not apply where compliance would violate Colorado evidentiary privilege; the section also preserves stated speech/press freedoms. It does not decide privilege, constitutional validity, or a categorical defense on absent facts. | S001 §1705(3)–(4). |
| R100-P1-C049 | The federal-authority exclusion is limited to the specified high-risk activities involving an authorized/approved/etc. system within federal authority, a qualifying FHFA-regulated entity, or qualifying substantially equivalent/stricter standards. Separate research supporting federal approval/certification/review is covered. No approval or standards equivalence is established. | S001 §1705(5)(a)–(b). |
| R100-P1-C050 | Specified Commerce/Defense/NASA contract work and federally acquired systems have exceptions to their exclusions for high-risk employment or housing decisions. Federal involvement alone is not a universal exclusion. | S001 §1705(5)(c), (6). |
| R100-P1-C051 | The covered-entity health recommendation provision cumulatively requires AI-generated recommendations, provider action to implement them, and recommendations not considered high risk. HIPAA category and risk qualification remain open. | S001 §1705(5)(d)(I)–(III); S014, limited read. |
| R100-P1-C052 | The insurer/fraternal-society/insurer-system-developer compliance treatment requires being subject to §10-3-1104.9 and rules under it. Current incorporated definitions and full regulatory requirements were not authenticated; no insurer-wide exemption is found. | S001 §1705(7); S018 failure. |
| R100-P1-C053 | Listed banking/credit-union categories and their affiliates/subsidiaries receive full-compliance treatment only if subject to prudential examination under published high-risk-AI guidance/regulations that are substantially equivalent or stricter and, at minimum, require regular antidiscrimination audits and mitigation of actual or reasonably foreseeable algorithmic discrimination. | S001 §1705(8)(a)(I)–(II). |
| R100-P1-C054 | The banking clause incorporates specified affiliation, bank, credit-union, and out-of-state-bank definitions. Affiliation concerns control/common control; relevant control includes the statutory voting-security or board-election tests. The bank definition excludes the specified credit-card national bank. Some nested federal/foreign category predicates remain uncompleted. | S001 §1705(8)(b); S009 specified complete definitions; 12 U.S.C. §1841(c)(2)(F) unexamined. |
| R100-P1-C055 | The developer, deployer, or other person relying on a §1705 exemption bears the burden of demonstrating that the action qualifies. | S001 §1705(9). |
| R100-P1-C056 | Current enforcement is exclusive to the AG notwithstanding §6-1-103. Subject to the affirmative-defense provision, violation is the specified unfair trade practice. No penalty amount or complete remedy procedure is established here. | S001 §1706(1)–(2); §6-1-105(1)(hhhh). |
| R100-P1-C057 | The affirmative defense requires discovery and cure through encouraged feedback, NIST-described adversarial/red-team testing, or internal review, and otherwise complying with: latest NIST framework and ISO/IEC 42001; or a qualifying equivalent/stricter recognized framework; or an AG-designated/publicly disseminated framework. The asserting actor bears demonstration. | S001 §1706(3)–(4). |
| R100-P1-C058 | Other rights, claims, remedies, presumptions, and defenses are preserved; Part 17 presumptions/defenses apply only to AG enforcement. The current text says Part 17 does not provide a basis for a private right of action for violations of Part 17 or other law. Read together, these clauses do not establish immunity from independently existing law. | S001 §1706(5)–(6). |
| R100-P1-C059 | The AG may adopt implementing/enforcement rules concerning developer documentation, specified notices, risk programs, assessments, presumptions/defenses, and framework recognition. This authority is not evidence that every contemplated rule has been finally adopted. | S001 §1707(1), complete list; S015 status limit. |
Claim ID · Qualified definition or exclusion · Exact source/pinpoint · 13 data rows
| Claim ID | Qualified definition or exclusion | Exact source/pinpoint |
|---|---|---|
| R100-P1-C060 | ADMT processes personal data and uses computation to produce information used to make, guide, or assist a decision, judgment, or determination concerning an individual. Listed output forms include predictions, recommendations, classifications, rankings, and scores. | S001 F-future §1701(2)(a); S004 §1. |
| R100-P1-C061 | ADMT excludes the listed anti-malware/virus, calculator, database/storage, firewall, domain/loading/networking, spam/robocall, spell-checking, web-cache/hosting technologies; spreadsheets must require human analysis and not use machine learning/foundation/large-language models. It also excludes solely administrative-processing assistance for human review and the specified understandable information technology only if both no consequential-decision intended/marketed/etc. use and an acceptable-use prohibition are satisfied. | S001 F-future §1701(2)(b)(I)–(III). |
| R100-P1-C062 | Consequential decisions concern provision, access, eligibility, selection, or compensation in a covered domain, or differentiated price/cost-sharing/compensation/material terms reasonably likely materially to limit, delay, deny, or fundamentally alter access, eligibility, or opportunity. “Adverse outcome” separately covers listed denial/reduction/restriction actions or materially less favorable terms compared with similarly situated consumers, with its stated material-effect qualifications. | S001 F-future §1701(1), (3)(a). |
| R100-P1-C063 | Consequential-decision exclusions cover: qualifying low-stakes/routine processes; advertising/marketing/product recommendations/search/moderation; qualifying manual spreadsheets; human-review summaries without materially influential inference; narrow procedural/data functions under the actual “do not … or” wording; cybersecurity/spam/reliability/AML/CTF controls; sanctions compliance with a facial-recognition limitation unless solely identity confirmation; specified fraud/identity/required monitoring/reporting activities; and routine academic support not materially influential. External sanctions/financial regimes are not thereby completed. | S001 F-future §1701(3)(b)(I)–(IX). |
| R100-P1-C064 | Consumer incorporates §1303(6)(a), but expressly includes an employee, a Colorado-resident job applicant, and an individual whose access, eligibility, or opportunity in Colorado is evaluated through a consequential decision by a person doing business in Colorado. It is not simply the old residence-only definition. | S001 F-future §1701(4); §1303(6)(a). |
| R100-P1-C065 | Covered domains are education; employment creating or potentially creating an employer-employee relationship; lease/purchase of Colorado residential real estate; financial/lending services; specified insurance decisions; health-care services; and essential government/public-benefit eligibility/renewal. Legal services are not separately listed in this successor domain definition; that absence does not resolve other law. | S001 F-future §1701(6)(a)–(g). |
| R100-P1-C066 | Covered ADMT is ADMT used to materially influence a consequential decision. Material influence cumulatively requires a non-de-minimis output factor used in making the decision and an effect on its outcome; incidental, trivial, and clerical uses are excluded. Capability alone is not substituted for the successor’s actual-use/effect words. | S001 F-future §1701(5), (13). |
| R100-P1-C067 | Deployer requires doing business in Colorado and deployment of covered ADMT. Developer includes the specified commercial provision of covered ADMT, development of a component designed/marketed/intended/documented/etc. for covered ADMT, or intentional/substantial modification making an ADMT covered. | S001 F-future §1701(7), (8)(a). |
| R100-P1-C068 | Developer exclusions have separate predicates: solely research without consequential use in the research; internal use without making it available to another person for consequential use; a preceding developer after an unaffiliated modifier changes the specified intended/etc. use; or component integration into covered ADMT without the developer’s actual knowledge. | S001 F-future §1701(8)(b). |
| R100-P1-C069 | Employee/employer are expressly incorporated from §8-4-101(5)–(6), and FERPA is identified by statute and implementing regulations. Current employment definitions failed access; the full FERPA regime was not read. No category is filled from an ordinary label. | S001 F-future §1701(9)–(11); S017. |
| R100-P1-C070 | Intentional/substantial modification concerns deliberate material change to the listed intended/documented/etc. uses. “Material update” concerns an update/patch/release/version—including parameters/defaults/documentation—that the developer knows or reasonably should know is likely materially to affect relevant outputs/performance or stated intended use. Nonmaterial routine maintenance, cosmetic changes, and bug fixes are excluded under the stated conditions. | S001 F-future §1701(12), (14). |
| R100-P1-C071 | Meaningful human review requires a designated reviewer with authority to approve, modify, or override; relevant available primary evidence; training; no default to system output; and sufficient information about intended use, material limitations, input categories, and principal factors. It does not require disclosure of proprietary source code, weights, or trade secrets. | S001 F-future §1701(15). |
| R100-P1-C072 | Personal data incorporates §1303(17): linked or reasonably linkable information concerning an identified/identifiable individual, excluding qualifying deidentified and publicly available information. Government-record availability or a reasonable basis concerning lawful public availability supplies the public-information branch; public labeling alone does not. | S001 F-future §1701(16); §1303(11), (16)–(17). |
Claim ID · Qualified rule · Exact source/pinpoint · 15 data rows
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C073 | From January 1, 2027, developers must provide each covered deployer reasonably understandable documentation protecting secrets/legally protected information: intended/harmful uses; known training-data categories including personal data; known limitations/risks/nonuse circumstances; use/monitoring/human-review instructions where applicable; and information reasonably necessary for §1704. Withholding requires notice to the deployer. | S001 F-future §1702(1). |
| R100-P1-C074 | Developers must notify each deployer of material updates, intentional/substantial modifications, and changes in intended use, limitations, or risk mitigation within a reasonable time. Public release notes suffice only with direct notice of the public release to each deployer. | S001 F-future §1702(2). |
| R100-P1-C075 | The (1)–(2) disclosures apply only to deployer uses marketed/advertised/configured/contracted/sold/licensed for material consequential influence. The section’s further scope includes specified intended/documented/etc. consequential use or awareness of consequential use consistent with intended and contracted uses. No different connector is substituted. | S001 F-future §1702(3), (5). |
| R100-P1-C076 | Developer compliance records must be retained at least three years after creation, or longer if other applicable law requires. Included categories are version identifiers, changelogs, and material-update documentation/notices. | S001 F-future §1702(4). |
| R100-P1-C077 | Deployers retain reasonably necessary compliance records at least three years after the consequential decision, or longer under applicable law. Version identifiers, changelogs, and material mitigation documentation are illustrative permitted record categories. | S001 F-future §1703. |
| R100-P1-C078 | Before using covered ADMT to materially influence a consequential decision, a deployer must give clear and conspicuous use notice and instructions for obtaining additional information. A prominent public notice reasonably accessible at the interaction, including a reasonably proximate link/posting, is the expressly permitted route. | S001 F-future §1704(1)–(2). |
| R100-P1-C079 | Within 30 days after making a consequential decision producing an adverse outcome, provide plain-language decision/ADMT-role information; a simple means to request the system name/version if applicable, developer, and input types/categories/sources to the extent received under §1702; and explanation/exercise instructions for §1705 rights. | S001 F-future §1704(3). |
| R100-P1-C080 | The adopted legislative declaration calls for sector-sensitive rules; the AG must adopt implementation/clarification rules on or before January 1, 2027. The permitted subjects include disclosed categories, sector examples, understandable descriptions, and interaction with other notice laws. This rulemaking provision is early-effective, not proof of a completed rule. | S001 F-future §1704(4); S004 §5(2). |
| R100-P1-C081 | Future consumer disclosure need not disclose trade secrets or legally protected information; withholding under §1704(5) requires notifying the consumer. This does not require disclosure of the protected content itself. | S001 F-future §1704(5). |
| R100-P1-C082 | A creditor required to give and actually giving an ECOA/Regulation B and applicable FCRA notice for the specified credit decision may use that notice for the same state decision only if it also satisfies the state requirements. No duplicative notice is required on those conditions; prohibited federal disclosure is not required; an appropriate ADMT statement/instructions may be included. Federal notice compliance itself is unexamined. | S001 F-future §1704(6)(a)–(d). |
| R100-P1-C083 | Disclosure does not require federally prohibited information or compromise the confidentiality/integrity of legally required cybersecurity, fraud, AML, CTF, or sanctions programs. Notices must be reasonably accessible to people with disabilities or limited English proficiency consistently with applicable law; the complete accessibility regimes remain held. | S001 F-future §1704(7)–(8). |
| R100-P1-C084 | For education, a FERPA-subject deployer may use existing FERPA channels, including applicable parent/eligible-student channels; duplicative FERPA notice/disclosure processes are not required. Actual FERPA category and sufficiency are not established. | S001 F-future §1704(9). |
| R100-P1-C085 | After an adverse outcome from a consequential decision materially influenced by covered ADMT, the consumer may request and the deployer must respond with instructions for requesting personal data/correcting factual or material inaccuracies consistently with §1306, and an opportunity for meaningful human review/reconsideration to the extent commercially reasonable. | S001 F-future §1705(1)(a). |
| R100-P1-C086 | The specified employment/commercial-consumer and §1304(2)(k), (n), (o) exceptions do not apply to this correction right. Correction of opinions, predictions, scores, or protected evaluations is not required. These words do not remove every exception from the entire privacy regime. | S001 F-future §1705(1)(b)–(c); selected incorporated clauses. |
| R100-P1-C087 | Existing FERPA inspection/review/amendment and applicable district processes may satisfy the education provision if they offer the stated reasonable correction/reconsideration mechanism; duplicative processes are unnecessary. The AG must adopt §1705 clarification/implementation rules on or before January 1, 2027; that rulemaking clause is early-effective. | S001 F-future §1705(2)–(3); S004 §5(2). |
Claim ID · Qualified rule · Exact source/pinpoint · 13 data rows
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C088 | The AG shall enforce through the Colorado Consumer Protection Act; §§1702–1705 disclosure/consumer-right violations are exclusively AG-enforceable. Part 17 violations are deceptive trade practices; inconsistent CCPA provisions do not apply to those violations. This is not a completed penalty/remedy analysis. | S001 F-future §1706(1)–(2). |
| R100-P1-C089 | Before enforcement, the AG shall issue a violation notice if cure is deemed possible. Failure to cure within 60 days after receipt permits action. A demonstrable knowing or repeated violation removes the requirement to offer a cure period. During an action, cure within 60 days after written notice may be considered in monetary-relief mitigation; it is not guaranteed dismissal. | S001 F-future §1706(3)(a)–(d). |
| R100-P1-C090 | Beginning January 2028 and each January thereafter, the AG’s specified SMART Act presentation must report actions filed/completed, cure periods offered/unmet, and violations for which cure was not deemed possible, separately concerning developers/deployers. The whole subsection (3) is repealed January 1, 2030, including this reporting paragraph—not just the cure clock. | S001 F-future §1706(3)(e)–(f); §2-7-203 context unexamined. |
| R100-P1-C091 | The future Part creates no new private right; existing state/federal rights and remedies are preserved. Compliance does not excuse other-law noncompliance. No independent cause of action, damages, immunity, or standing is found here. | S001 F-future §1706(4), §1709(1)–(2). |
| R100-P1-C092 | The AG may clarify the Part and material-influence definition through rules, including presumptions/examples/indicators. Rulemaking requires public notice, written-comment opportunity, and at least one hearing, subject to §24-4-103. The early-effective joinder clause preserves existing Rules 19/20 abilities in existing-law actions; it does not create a new action. | S001 F-future §1706(5)–(6); S004 §5(2). |
| R100-P1-C093 | In an existing state antidiscrimination action arising from a consequential decision materially influenced by covered ADMT, the section permits developer/deployer liability and directs relative-fault allocation. It does not newly apportion fault to a claimant or create joint-and-several liability where existing law does not permit it. | S001 F-future §1707(1)–(4). |
| R100-P1-C094 | Developer liability under this section requires both the specified intended/documented/marketed/etc. use and material influence on the decision giving rise to an existing-law violation; outside-use violations are excluded under the stated clause. Deployer independent acts/omissions remain separately addressed, including the stated outside-use situation where the developer complied with §1702. | S001 F-future §1707(5)–(6). |
| R100-P1-C095 | A developer/deployer contract provision shifting the indemnitee’s own covered discriminatory-act damages through indemnity/defense/hold-harmless is contrary to public policy and void under the stated scope. The outside-intended-use exception requires developer §1702 compliance. Other business contract terms and insurance are preserved subject to applicable law. No actual term is assessed. | S001 F-future §1707(7)(a)–(d). |
| R100-P1-C096 | Separate state-law liability remains; Part 17 compliance is not a defense to other-law noncompliance; ADMT use does not excuse state/federal obligations, including discrimination and consumer protection. | S001 F-future §1707(8)–(9). |
| R100-P1-C097 | Insurers and affiliated entities subject to §10-3-1104.9 receive compliance treatment in the practice of insurance; otherwise the specified §1704(3) disclosure applies to the extent applicable. Insurer employment uses are not removed. Current insurance-definition/rule predicates remain incomplete. | S001 F-future §1708(1)–(2); S018. |
| R100-P1-C098 | The listed §§1701–1706 exclusion concerns qualifying HIPAA covered entities doing business in Colorado and business associates’ services to them, except employment decisions. A covered entity that is a provider must operate from a Colorado location for this subsection. A general advanced-technology notice to patients remains required and may be combined with other notices. | S001 F-future §1708(3)(a)–(c); S014 limited chain. |
| R100-P1-C099 | Covered-ADMT financial-assistance eligibility decisions, including referenced discounted care, retain specified decision/ADMT-role, information-type, correction, and applicable human-review disclosures. Compliance may use an advance general disclosure or notice within 30 calendar days after an adverse outcome; duplicate process is unnecessary if the required information/review opportunities are provided. Underlying assistance eligibility is not decided. | S001 F-future §1708(3)(d)–(e); §25.5-3-502 unexamined. |
| R100-P1-C100 | The listed §§1701–1706 exclusion also covers FDA-overseen devices and specified manufacturer research/development, including referenced clinical investigations. HIPAA-inconsistent disclosure is not required; applicable federal health privacy controls conflicts. GLBA’s clause concerns prohibited disclosure of nonpublic personal information, not a blanket financial-actor exemption. | S001 F-future §1708(4)–(6). |
Claim ID · Qualified rule · Exact source/pinpoint · 5 data rows
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C101 | A person may not use advertising/interface/output wording implying AI output is provided/endorsed by or equivalent to specified authorized psychotherapy professionals; representing that AI provides psychotherapy; or representing confidentiality so a reasonable user would believe it comparable to therapist-client protections. No actual representation is examined. | S001 current/future §1705.2(1)(a)–(c); S006 §3. |
| R100-P1-C102 | The section does not impose liability on an authorized psychotherapy professional for AI defects/failures attributable to a developer/deployer; their liability is governed by applicable consumer-protection law. This clause is not general immunity or a complete liability rule. | S001 §1705.2(2). |
| R100-P1-C103 | Accredited/approved education/training use is preserved only under the listed sole-purpose, no-public/client-tool representation, and authorized review or control conditions. Solely research use requires a registered-IRB setting and no consumer offer or psychotherapy outside research. | S001 §1705.2(3)–(4); S006 §3; narrow §12-245-224.5(5)(a) context. |
| R100-P1-C104 | The wellness-tool exclusion lists self-help, homework, navigation, coaching, meditation, journaling/reflections, psychoeducation, goals/progress, session preparation/summaries, mood/mindfulness/breathing, crisis directories, safety planning, and other wellness tools, with no diagnosis/treatment and clear non-substitute-for-clinical-care disclosure. The FDA-authorized/approved/cleared/enforcement-discretion alternative has its own intended-use predicate and the same two conditions. | S001 §1705.2(5)(a)–(b). |
| R100-P1-C105 | This section separately incorporates the AI definition from §12-245-224.5 and psychotherapy from §12-245-202. The latter concerns the described diagnosis/treatment/testing/assessment/counseling in a planned professional relationship, may include regular or single assessment/brief intervention, and directs narrow construction. No clinical classification follows. | S001 §1705.2(6); S010 §12-245-202(10), (14), §12-245-224.5(1)(b). |
Claim ID · Qualified rule · Exact source/pinpoint · 11 data rows
| Claim ID | Qualified rule | Exact source/pinpoint |
|---|---|---|
| R100-P1-C106 | Conversational AI service is publicly accessible AI primarily simulating human conversation/interaction through adaptive text, visual, or aural communication. Operator covers an entity that develops and publicly makes it available, or offers it to a consumer. An app store/search engine is not an operator solely for providing access. | S001 current §1701(4.5), (10.5); future (4.5), (15.5); S005 §1. |
| R100-P1-C107 | Definition exclusions separately cover: primarily developer/researcher tools; primarily commerce/transactional assistance; narrow-topic tools with specified prohibited-output/dialogue limits; primarily business operations/productivity/analysis/research/training/technical-assistance tools; qualifying device assistants with content/dialogue limits; solely internal business tools; game or location-entertainment features confined to their topics; specified HIPAA uses; Article 64 entities; limited school tools not designed for companionship/dependence; and qualifying embedded non-chatbot features, including the referenced social-media category. Each exclusion retains its own purpose/capability conditions. | S001 current/future §1701(4.5)(b)(I)–(XII); S005 §1. |
| R100-P1-C108 | Minor means consumer under 18; self-harm means intentional self-injury with or without intent to cause death. “Visual depiction” incorporates §2256(5). “Explicit sexual conduct” and “intimate digital depiction” incorporate unavailable current Title 13 definitions; the Part expressly excludes evidence-based medical information/factual reproductive-health descriptions from the former. Those missing underlying definitions remain held. | S001 current §1701(7.5), (10.1), (10.3), (10.7), (13), future corresponding definitions; S013; S019. |
| R100-P1-C109 | Account holder, minor account holder, and minor user are defined. Operators must use commercially reasonable or generally accepted age-estimation methods, not willfully disregard clear and convincing minor-age information, and treat estimated age/range as knowledge for this section. The lead age-estimation sentences do not themselves carry the subsequent January 1 introductory limitation. | S001 current §1708(1)–(2) lead; future §1710(1)–(2); S005 §2. |
| R100-P1-C110 | From January 1, 2027, known-minor disclosure must respond to identity prompts and use one specified route: persistent screen disclaimer, intermittent audio for no-screen products, or beginning-of-interaction disclosure repeated at least once every three continuous-interaction hours. | S001 current §1708(2)(a); future §1710(2)(a). |
| R100-P1-C111 | Known-minor duties prohibit unpredictable-interval points/rewards intended to increase engagement; require technically feasible prevention of listed sexual depictions, encouragement, and interactions; require reasonable measures against simulated dependence/isolation, including human/sentience claims and specified romantic simulations; and require the two sexual-conduct response protocols. Underlying incorporated content definitions remain partly unresolved. | S001 current §1708(2)(b)–(f); future §1710(2)(b)–(f). |
| R100-P1-C112 | Known-minor duties incorporate Part 13 privacy/data requirements and require minor and parent/guardian account/privacy tools, including control over retaining earlier interactions for personalization and using personal data for training. Full minor-privacy law is not completed here. | S001 current §1708(2)(g)–(h); future §1710(2)(g)–(h). |
| R100-P1-C113 | From January 1, 2027, general user disclosure is required at the first interaction each day, at least every three continuous-interaction hours or persistently, and in response to identity prompts. This is distinct from the known-minor alternative structure. | S001 current §1708(3); future §1710(3). |
| R100-P1-C114 | From January 1, the service must have the specified suicide/self-harm response protocol, crisis-service referral excluding law enforcement as that referral category, and repeated/severe-indicator escalation. It may not falsely represent outputs as provided/endorsed by or equivalent to the listed licensed health/legal/mental-health professionals or qualified dietitians. This is a source description, not individual crisis or treatment advice. | S001 current §1708(4)–(5); future §1710(4)–(5). |
| R100-P1-C115 | On and after July 1, 2027, annual reports cover preceding-calendar-year referral-notification count, specified implemented protocols, and additional AG-determined efficacy/reliability metrics. Reports exclude user identifiers/personal information; the AG posts report data; evidence-based measurement is required. No specific recurring annual filing day, actual metric, or validated efficacy result is established. | S001 current §1708(6); future §1710(6). |
| R100-P1-C116 | The chatbot section preserves the referenced information-access rights, protects secrets/confidential/proprietary/legally protected information, and does not authorize unconstitutional moderation. The future Part-wide definitions omit the old general AI-system definition while the harmonized chatbot definition still uses the term; §1705.2’s separate incorporation does not automatically resolve that Part-wide construction issue. | S001 current §1708(7), future §1710(7), future §1701, §1705.2(6). |
Claim ID · Qualified proposition · Exact source/pinpoint · 11 data rows
| Claim ID | Qualified proposition | Exact source/pinpoint |
|---|---|---|
| R100-P1-C117 | Current §1703’s opt-out reference is expressly conditional on applicability. The incorporated profiling category concerns automated evaluation/analysis/prediction of specified personal aspects; §1306 separately addresses profiling producing legal or similarly significant effects. Future §1705’s correction reference is a different incorporation, with express exception overrides. | S001 §1303(20), §1306(1)(a)(I)(C); current §1703(4)(a)(III); future §1705(1). |
| R100-P1-C118 | Section 1306’s complete request framework includes designated secure/reliable methods, normal interaction, authentication, no compelled new account, relevant opt-out/agent provisions, access/correction/deletion/portability, refusal explanation, and internal appeal. Its fee and authentication qualifications and §1307 limitations matter. The report does not silently transplant every Part 13 procedure into every Part 17 review right. | S001 complete §§1306–1307; §1303(2), (7), (11), (17), (20). |
| R100-P1-C119 | Section 1306 supplies a 45-day response period and possible additional 45 days for complexity/number; appeal response has 45 days with a possible additional 60 days and required timely extension notice. Portability has the stated two-times-per-calendar-year condition; fee treatment for a second/subsequent request within 12 months incorporates a separate fee authority not completed here. These are privacy-source periods, not established universal AI appeal deadlines. | S001 §1306(1)(e), (2)(a)–(d), (3). |
| R100-P1-C120 | Deidentified-data treatment requires inability reasonably to infer/link plus specified safeguards, public commitment, and recipient-contract conditions. Section 1307 preserves stated limits on reidentification/association and a pseudonymous-data exception conditioned on separation and effective controls. No actual data provenance or classification is established. | S001 §1303(11), (17), complete §1307. |
| R100-P1-C121 | The incorporated dietitian category requires the specified qualifying degree route and either at least 900 hours of planned continuous supervised preprofessional experience or the specified registered-dietitian certificate. No actual credential is examined. | S001 §6-1-707(1)(b)(I)–(II); current §1708(5)(d)/future §1710(5)(d). |
| R100-P1-C122 | HIPAA’s selected definitions include covered-entity categories and detailed business-associate inclusions/exclusions, but their nested program, PHI, arrangement, and statutory predicates are not all read. Part 17’s cross-reference therefore cannot establish an actual health-sector exclusion here. | S014 §160.103 selected complete definitions; C051, C098–C100, C107. |
| R100-P1-C123 | Current employment, insurance, specified sexual-content, and Article 64 definition chains remain incomplete because the official current bodies failed access; other listed external standards/regimes remain deliberately unexamined. Dependent application is held, not supplied from a label or older text. | S017–S020; dependency table below. |
| R100-P1-C124 | Financial/lending services are express current and future subject categories, but coverage still requires the applicable actor, consumer, system, use, decision, and exception predicates. Future credit-notice coordination and GLBA disclosure preservation do not prove federal compliance or universal financial-sector exclusion. | C017–C023, C053, C060–C075, C082, C100; S001 exact provisions. |
| R100-P1-C125 | Current reasonable-care/program/impact-assessment provisions and future documentation/record/notice/review provisions are materially different. Their textual replacement does not prove that risk assessment or antidiscrimination obligations disappear under every other law, or that incurred liabilities vanish. | S001 current §§1702–1703 versus future §§1702–1705, 1707–1709; S007 §2-4-303. |
| R100-P1-C126 | Defined coverage, an operative duty, an exception, a rebuttable presumption, an affirmative defense, exclusive public enforcement, and an existing-law liability rule are distinct propositions. None independently proves actual classification, compliance, liability, eligibility, relief, or a private remedy. | S001 current §§1701–1707; future §§1701–1709; conditions in the preceding claims. |
| R100-P1-C127 | No examined Part 17 clause supplies a repayment formula, credit-approval probability, financial-return measure, model-performance guarantee, settlement result, or individual suitability finding. This is a bounded observation about the complete selected bodies, not all law or all technology. | S001 complete current/future Part 17; S002–S006 selected adopted bodies. |
Comparison · Supported distinction; claims and exact authority · Missing authority/predicate · 20 data rows
| Comparison | Supported distinction; claims and exact authority | Missing authority/predicate | Adverse inference to avoid |
|---|---|---|---|
| Commercial AI label versus legal system category | Current machine-inference definition differs from future personal-data/computation ADMT definition. C014, C060–C061; S001 current §1701(2), future §1701(2). | Actual system functions/use; incorporated data classification. | Every product called AI is covered, or every product not called AI is excluded. |
| Definition versus classification | Definitions identify predicates; no real actor/system/decision was examined. C019–C023, C066–C070, C126. | All application facts. | A generic category example proves actual status. |
| Current substantial factor versus future material influence | Current capability/assistance/generated-factor elements differ from future non-de-minimis use and outcome effect. C020, C066; S001 respective §1701 clauses. | Actual use/effect; final interpretive rules. | Capability alone proves future material influence. |
| Inclusion versus exclusion | Domain inclusion does not eliminate procedural, technical, purpose, actor, or sector exclusions. C017, C021–C022, C049–C055, C061–C068. | Complete cumulative exclusion predicates. | Financial involvement alone resolves coverage. |
| Cumulative versus alternative conditions | Small-deployer conditions are cumulative; specified disclosure methods and some research/definition routes are alternatives. C042, C061, C068, C110. | All predicates for the particular route. | Satisfying one small-entity condition satisfies the whole exception. |
| Current consumer versus future consumer | Residence-only wording is replaced by an incorporation plus express employment/Colorado-opportunity extensions. C018, C064, C069. | Current incorporated employee/employer definitions and actual territorial facts. | A single residence rule answers both versions. |
| Current risk governance versus future documentation | Current §1703 prescribes risk programs and assessments; future §1703 concerns records, alongside other future duties. C033–C037, C073–C077, C125. | Other-law obligations and savings application. | No future risk obligation exists anywhere. |
| Duty versus rebuttable presumption | Reasonable care is the duty; specified compliance supports an AG-enforcement presumption. C026, C032, C058. | Actual compliance; applicable adopted rules. | A framework label proves care or absence of discrimination. |
| Defense versus exemption | Current §1706 defense requires discovery/cure plus framework conditions; §1705 exclusions have separate predicates and burden. C055–C057. | Framework contents, qualifying actions, actual cure. | An assessment automatically grants immunity. |
| Predecision versus adverse-outcome notice | Timing, content, and delivery differ; future adverse notice runs from making the decision, not receipt. C038–C040, C078–C079. | Actual trigger and final rules. | One generic notice satisfies every stage. |
| Correction versus change of judgment | Future correction concerns factual/material data inaccuracies; opinions, predictions, scores, and protected evaluations are excluded. C085–C087. | Data category and applicable process. | A correction right guarantees a different decision. |
| Human review versus favorable result | Current technical-feasibility/best-interest wording differs from future commercially reasonable meaningful review. C039, C071, C085. | Complete applicable version and actual predicates. | Human review guarantees approval or reversal. |
| Credit notice coordination versus federal-law satisfaction | Combined notice is permitted only when the federal notice also satisfies the state requirements. C082; S001 future §1704(6). | Complete ECOA/Regulation B/FCRA chain. | A state clause certifies federal compliance. |
| Financial-sector compliance treatment versus universal exemption | Current prudential treatment is conditional; future GLBA language protects against prohibited disclosure. C053–C054, C100. | Qualifying supervision, standards, categories, actual conduct. | Every bank, affiliate, or regulated financial actor is exempt. |
| Health exclusion versus financial-assistance disclosure | Future covered-entity treatment retains specified financial-assistance notices and review information. C098–C100. | HIPAA and discounted-care predicates. | Health-sector status eliminates every notice duty or establishes assistance eligibility. |
| Public authority versus private contract | Statute supplies public duties; future §1707 regulates specified indemnity effects while preserving other terms/insurance. C088, C095–C096. | Actual contract, underlying law, liability predicates. | Any contract can waive the statute, or every indemnity term is void. |
| Enactment versus commencement versus application | Approval, conditional effective date, duty-start date, decision-date application, and reporting start are separate. C004–C008. | Unexamined transition events and later law. | A signature or web-update date is every operative date. |
| Current statute versus agency explanation | Adopted May 29 approval conflicts with the AG’s July 1 summary; proposal descriptions are not adopted rules. C011–C012. | Authenticated final rule and later publication chain. | An agency page silently amends the Act. |
| Public enforcement versus private remedy | Exclusive statutory enforcement and no-new-action clauses coexist with preservation of existing law and future relative-fault rules. C056–C058, C088–C096. | Standing, cause of action, proof, process, remedies. | Either automatic damages or universal immunity. |
| Colorado component versus broader A100 | This selected state framework neither establishes another jurisdiction’s law nor resolves the federal financial/product regimes. C124–C127. | Authorities listed in the parent-gap table. | Component completion equals parent or operational acceptance. |
Measurement ID · Source quantity; actor/object and trigger · Boundary, exceptions, convention, and missing facts · 11 data rows
| Measurement ID | Source quantity; actor/object and trigger | Boundary, exceptions, convention, and missing facts | Authority |
|---|---|---|---|
| M001 | October 28, 2026 PDT: actual research access. | Observation date only; not enactment/effectiveness. | Source register and access record; C001. |
| M002 | May 17, 2024 approval; original February 1, 2026 duty dates. | Approval/compiler effect distinguished from original prospective application; later dates amended. | S002 §§1–3; C004. |
| M003 | August 28, 2025 approval; compiler November 25, 2025 effect; amended June 30, 2026 triggers. | Original date formula and referendum alternative remain separate. | S003 §§1–4; C005. |
| M004 | 90-day period after final legislative adjournment; 12:01 a.m. following expiration. | SB25B-004 conditional commencement; timely petition changes route to November 2026 approval and official vote declaration. No event calculation. | S003 §4. |
| M005 | May 14, 2026 passage/approval; January 1, 2027 default effectiveness. | Listed clauses effective upon passage; default not applied to them. | S004 §5(1)–(2); C006. |
| M006 | Consequential decisions made on or after January 1, 2027. | Inclusive application boundary; actual decision event absent. | S004 §5(3). |
| M007 | May 29, 2026 chatbot approval; June 1 signed-format date; agency July 1 signing statement. | Approval and publication/version metadata differ; July 1 statement conflicts and is not adopted. | S005 approval/action; S015; C007, C011. |
| M008 | HB26-1263: 90 days, 12:01 a.m.; August 12, 2026 if adjournment May 13, 2026. | Timely referendum petition invokes November 2026 election/official declaration alternative. Compiler gives August 12; predicate events not independently researched. | S005 §3. |
| M009 | June 3, 2026 psychotherapy approval; same conditional 90-day/12:01 a.m./August 12-if-May 13 formula. | Applies to actions on/after applicable effective date; referendum alternative preserved. | S006 §4; C008. |
| M010 | July 2, 2026, 11:35 a.m. MDT Red Book update. | Compiler-index metadata, not substantive commencement. | S016. |
| M011 | Federal source cutoff October 20, 2026, P.L.119-134; eCFR currency October 26, 2026 and title amendment label October 6. | Compilation/title metadata only; no exhaustive later-law or definition-specific amendment finding. | S011–S014. |
Measurement ID · Actor/object; source quantity and trigger · Boundary, cumulative conditions/exceptions, counting/delivery, absent facts · 37 data rows
| Measurement ID | Actor/object; source quantity and trigger | Boundary, cumulative conditions/exceptions, counting/delivery, absent facts | Authority |
|---|---|---|---|
| M012 | Current principal duties: on and after June 30, 2026. | Inclusive; relevant section and actor/system predicates required. | C026–C045; S001 §§1702–1704. |
| M013 | Developer public statement: update as necessary and no later than 90 days after intentional/substantial modification. | Accuracy duty can require earlier action; “days” not further defined here. | C029; §1702(4). |
| M014 | Developer discovery/report notice: without unreasonable delay, no later than 90 days after specified trigger. | Alternative discovery/credible-report predicates; AG and all known specified recipients. Not permission to wait 90 days. | C030; §1702(5). |
| M015 | AG developer-document request: no later than 90 days after request. | Prescribed form/manner; disclosure protection preserved. Receipt substitution not invented. | C031; §1702(7). |
| M016 | Current risk program: regular/systematic lifecycle review and updating. | No fixed numerical interval stated in this clause. | C033; §1703(2). |
| M017 | Assessments: at least annually and within 90 days after modification is made available. | Both frequencies matter; statutory alternatives/exemption remain. No calendar conversion. | C034–C036; §1703(3)(a)–(e). |
| M018 | Assessment records: at least three years following final deployment. | Minimum; final-deployment trigger absent. Not creation date. | C037; §1703(3)(f). |
| M019 | Deployment review: on or before June 30, 2026, and at least annually thereafter. | Inclusive initial date; distinct from assessment record retention. | C037; §1703(3)(g). |
| M020 | Current consumer notice: no later than deployment for the decision; before the decision. | Both source timing conditions preserved; no invented number of advance days. | C038; §1703(4)(a). |
| M021 | Small-deployer condition: fewer than 50 FTE employees. | Strict < 50; at deployment and throughout; all additional conditions required; only specified subsections excepted. | C042; §1703(6). |
| M022 | Current deployer discovery notice: no unreasonable delay and within 90 days after discovery. | Requires post-June-30 deployment and discovery of causation; not developer’s broader alternatives. | C043; §1703(7). |
| M023 | AG deployer-record request: no later than 90 days after request. | Prescribed form/manner; protections remain. | C044; §1703(9). |
| M024 | Current public statement: periodic update; prudential audit: regular audit. | No fixed numerical interval supplied by these clauses. External guidance unexamined. | C041, C053; §§1703(5), 1705(8). |
| M025 | Banking control: 25% or more of relevant voting securities, or the stated board-election control route. | Inclusive >= 25% for that branch; exact statutory context and other control branches matter. No actual holdings. | C054; S009 §11-101-401(23). |
| M026 | Future developer records: not less than three years after creation, or longer under applicable law. | >= 3 years; separate longer-law condition. | C076; future §1702(4). |
| M027 | Future deployer records: not less than three years after decision, or longer under applicable law. | Different trigger from developer/current assessment retention. | C077; future §1703. |
| M028 | Future update notice: within a reasonable time. | No fixed days supplied; public notes require direct notice to each deployer. | C074; future §1702(2). |
| M029 | Future initial notice: prior to covered use for material consequential influence. | No numerical lead time; public-notice alternative has accessibility/proximity conditions. | C078; future §1704(1)–(2). |
| M030 | Future adverse notice: within 30 days after making the decision. | Decision, not receipt, triggers; statute here says days, not expressly calendar days. | C079; future §1704(3). |
| M031 | AG notice/correction rules: on or before January 1, 2027. | Inclusive deadline; authority/mandate early-effective; actual adoption not established. | C080, C087; future §§1704(4), 1705(3). |
| M032 | Cure: within 60 days after receipt of violation notice. | Pre-action cure only if deemed possible; knowing/repeated-violation exception. | C089; future §1706(3)(a)–(c). |
| M033 | In-action cure mitigation: within 60 days after receipt of written notice. | Court may consider; no guaranteed result. | C089; future §1706(3)(d). |
| M034 | AG report: beginning January 2028, then each January. | Specified action/cure counts, separated by actor category; no actual count or exact January day supplied. | C090; future §1706(3)(e). |
| M035 | Entire future §1706(3) repealed January 1, 2030. | Applies to whole subsection, including report paragraph; savings/actual liability remain separate. | C090; future §1706(3)(f). |
| M036 | Rulemaking: at least one public hearing. | Minimum count plus public notice, written-comment opportunity, and §24-4-103 compliance. | C092; future §1706(5)(c). |
| M037 | Financial-assistance disclosure: advance general disclosure or within 30 calendar days after adverse outcome. | Express calendar-day unit; either route must supply required information; no actual date calculation. | C099; future §1708(3)(e). |
| M038 | Minor: under 18 years. | Strict < 18; consumer/category and knowledge predicates remain. | C108–C110; current/future §1701. |
| M039 | Known-minor duties: on and after January 1, 2027. | Does not rewrite the separately worded age-estimation lead sentences. | C109–C112; current §1708(2)/future §1710(2). |
| M040 | Minor disclosure alternative: start each interaction and at least once every three hours of continuous interaction. | Alternative to persistent-screen/intermittent-audio route; identity-prompt response also required. No continuous-use event supplied. | C110. |
| M041 | General-user disclosure: first interaction each day, then at least once every three hours continuous use or persistent disclosure, plus identity prompts. | No time zone or interrupted-session counting rule supplied in selected text. | C113. |
| M042 | Other chatbot duties: on and after January 1, 2027. | Crisis protocol and professional-representation rules have their own stated application. | C114. |
| M043 | Chatbot reports: on and after July 1, 2027, annually, covering referral count in the preceding calendar year. | Not converted to a universal “due every July 1” deadline. User identifiers excluded; no count/denominator supplied. | C115. |
| M044 | Dietitian experience branch: not less than 900 hours. | >= 900 hours, planned/continuous/supervised, plus qualifying degree; certificate alternative preserved. | C121; §707(1)(b). |
| M045 | Incorporated privacy response: 45 days after receipt, possible 45 additional days. | Complexity/number necessity and extension notice within initial period; no automatic extension. Scope into Part 17 held. | C119; §1306(2). |
| M046 | Incorporated privacy appeal response: 45 days after receipt, possible 60 additional days. | Stated necessity and initial-period notice; not a universal AI review clock. | C119; §1306(3). |
| M047 | Portability: not more than twice per calendar year; specified fee treatment for second/subsequent request within 12 months. | Different units/windows; fee calculation authority unexamined; no fee amount inferred. | C119; §1306(1)(e), (2)(c). |
| M048 | No source-stated repayment, return, acceptance, or model-accuracy formula in selected Part. | Negative finding limited to complete examined bodies. No invented performance threshold or financial model. | C127. |
Branch/status · Supported conditional rule; exact claims/source · Missing authority or predicate · 48 data rows
| Branch/status | Supported conditional rule; exact claims/source | Missing authority or predicate | Adverse inference to avoid | Next permissible generic public-law inquiry |
|---|---|---|---|---|
| B01 — Current version: partial | Distinguish current and future bodies and early-effective clauses. C001–C006; S001 headings, S004 §5. | Exhaustive later-law chain. | The 2024 signed Act is the complete October 2026 law. | Check subsequent officially adopted Part 17 changes and their complete commencement clauses. |
| B02 — Conditional commencement: partial | Petition-sensitive Acts use express alternative triggers. C005, C007–C008; S003 §4, S005 §3, S006 §4. | Complete constitutional chain; unexamined predicate events. | Compiler date proves every constitutional predicate. | Read complete Colorado constitutional commencement/referendum provisions from a readable official source. |
| B03 — Failed incorporation: unresolved | Failed current bodies cannot establish incorporated definitions. C123; S017–S020. | Current readable definitions. | Failure means repeal or no obligation. | Obtain ordinary publicly readable official versions of the exact failed clauses. |
| B04 — Person/business nexus: answered boundary | Current/future role definitions require their listed person and Colorado-business predicates. C013, C019, C067; S001 respective §1701. | Actual legal role and territorial facts. | An organizational label proves coverage. | Read only indispensable generic construction of “doing business” if a later component requires it. |
| B05 — AI versus ADMT: answered boundary | Current inference-based AI and future personal-data computational ADMT differ. C014, C060–C061. | Actual functionality; future AI-term construction gap. | All software satisfies both definitions. | Examine adopted generic interpretation of the specific definition without inspecting a product. |
| B06 — Consumer category: partial | Current resident definition differs from future express extensions. C018, C064, C069. | Current employee/employer incorporation. | Every commercial or employment exclusion carries forward unchanged. | Read current §8-4-101(5)–(6) and its material amendments. |
| B07 — Financial domain: answered boundary | Financial/lending services are listed, but other coverage predicates remain cumulative. C017, C065, C124. | System/use/consumer/exception predicates. | Every financial decision or debt tool is covered. | Read final generic domain/material-influence rules once authenticated. |
| B08 — High-risk factor: answered boundary | Current high-risk status requires consequential decision plus making/substantial factor. C020. | Actual use and decision character. | Mere availability or capability proves all elements. | Examine public construction of §1701(9), (11), without actual-system inquiry. |
| B09 — Procedural-task exclusion: answered boundary | Narrow-task and pattern-detection branches retain stated intent/human-review conditions. C021. | Intended function and review predicate. | “Administrative” is a universal exclusion. | Read any adopted generic rule interpreting these exact branches. |
| B10 — Listed technology: answered boundary | Current listed technologies reenter the high-risk category when the specified decision condition is met. C022. | Actual consequential use. | A spreadsheet or hosting label conclusively excludes coverage. | Compare current §1701(9)(b)(II) with future §1701(2)(b), preserving versions. |
| B11 — Modification/learning: answered boundary | Current learning exception needs all four conditions; future modification uses a different material-use definition. C023, C070. | Predetermination, documentation, use-change predicates. | Every update or learning event is exempt or automatically material. | Read final generic update/modification interpretation for the applicable version. |
| B12 — Developer versus deployer: answered boundary | Roles and duty-specific triggers differ; one role definition does not itself establish every duty. C019, C026, C032, C067. | Role/use predicates. | Developer and deployer duties are interchangeable. | Trace only the applicable role definition and duty clause together. |
| B13 — Current documentation: answered boundary | Required categories and feasible-artifact/internal-use conditions govern. C027–C028. | Availability, feasibility, unaffiliated-recipient predicates. | Any model card proves compliance. | Read adopted documentation rules and referenced assessment requirements. |
| B14 — Discovery reporting: answered boundary | Developer alternative triggers differ from deployer causation discovery. C030, C043; §§1702(5), 1703(7). | Discovery/report/cause predicates and prescribed form. | The same event starts every 90-day period. | Read final generic reporting instructions and exact triggering clauses. |
| B15 — Reasonable care/presumption: partial | Presumption requires statutory and applicable-rule compliance; rebuttable and AG-specific. C026, C032, C058. | Final rules and actual compliance. | Presumption means no discrimination occurred. | Authenticate complete adopted presumption rules, not a framework label. |
| B16 — Risk program: partial | Program must satisfy iterative lifecycle and contextual reasonableness requirements. C033. | Referenced framework content and equivalence. | Citation to NIST/ISO establishes compliance. | Read the exact public framework provisions relied upon; keep inaccessible/private-standard content held. |
| B17 — Assessments: answered boundary | Assessment frequency, contents, comparable-set and other-law alternatives are conditional. C034–C037. | Actual system set, similarity, modification/final-deployment triggers. | Any assessment satisfies the statute or grants immunity. | Read adopted generic assessment rules and complete alternative-law conditions. |
| B18 — Small deployer: answered boundary | <50 FTE is only one condition; exception affects only (2), (3), (5). C042. | Every continuing condition. | Small size removes notice, care, or reporting duties. | Examine exact §1703(6) and any adopted counting definition; no actual headcount query. |
| B19 — Current predecision notice: partial | Timing/content apply before decision; opt-out information only if applicable. C038, C117. | Part 13 scope and applicable opt-out predicates. | Every consumer has an unconditional AI opt-out. | Complete the narrow Part 13 applicability/exemption chain if separately authorized. |
| B20 — Current adverse review: answered boundary | Correction and appeal have technical-feasibility and best-interest/life-safety qualifications. C039–C040. | Actual adverse event, feasibility, delivery predicates. | Appeal guarantees reversal or unlimited delay. | Read precise adopted generic appeal/delivery instructions. |
| B21 — Public statements and timing: answered boundary | Developer modification deadline differs from deployer periodic updating. C029, C041; M013, M024. | Actual update/modification facts. | Every public statement has a 90-day update cycle. | Compare exact subsection-specific update duties. |
| B22 — Law/research/privilege: partial | Preserved activities have purpose, facial-recognition, research, and privilege conditions. C046–C048. | External ethics, privacy, privilege, constitutional predicates. | Research or legal-purpose labeling creates immunity. | Read only the exact relied-on public research or privilege incorporation. |
| B23 — Federal involvement: partial | Approval/standards, contract, and acquisition routes differ; employment/housing exceptions remain. C049–C050. | Authority, standards equivalence, intended decision category. | Federal involvement always excludes Part 17. | Read the specific generic federal authority/standard before asserting that route. |
| B24 — Insurance: unresolved application | Current and future insurance treatments have distinct conditions and future employment limitation. C052, C097. | Current Title 10 definitions/rules. | Insurance regulation establishes blanket exemption. | Read complete §§10-1-102(13), 10-14-102, 10-3-1104.9 and indispensable adopted rules. |
| B25 — Banking: partial | Prudential guidance must be equivalent/stricter and require audit/mitigation. C053–C054. | Full nested definitions and qualifying published guidance. | Any charter, regulator, or affiliate relationship is sufficient. | Read complete applicable generic banking-category and guidance clauses. |
| B26 — Future material influence: answered boundary | Non-de-minimis use and outcome effect are cumulative. C066. | Actual use/effect; future adopted clarifications. | Any contact with an output proves material influence. | Authenticate §1706(5) rules on material influence. |
| B27 — Future developer exclusions: answered boundary | Research, internal-use, preceding-developer, and unknown-component-integration branches differ. C068. | Each branch’s intended-use, availability, modification, or knowledge predicates. | Internal development or component status is automatically exempt. | Read precise future §1701(8)(b) plus adopted interpretation. |
| B28 — Data category: partial | Personal/public/deidentified categories depend on linkage and source/safeguard conditions. C072, C120. | Actual provenance and nested privacy applicability. | A “public” or “anonymous” label resolves legal status. | Complete only relevant public definition and deidentification construction. |
| B29 — Future updates/retention: answered boundary | Reasonable-time notices and three-year periods have different actors/triggers. C074, C076–C077. | Actual creation/decision/update event and longer-law duty. | One retention start date governs all records. | Examine complete applicable record-retention and counting authorities generically. |
| B30 — Future notices: answered boundary | Prior-use notice and 30-day post-decision disclosure are separate; public-posting alternative has conditions. C078–C081. | Trigger, required information, final rules. | A public posting necessarily satisfies post-adverse duties. | Read adopted notice-content and delivery rules. |
| B31 — Credit notice coordination: partial | Combined federal/state notice must satisfy both applicable bodies. C082. | Complete federal notice applicability/content. | ECOA notice automatically satisfies Colorado law. | Independently read relevant ECOA/Regulation B/FCRA public clauses in a separate component. |
| B32 — Future correction/review: partial | Adverse outcome, material influence, request, factual/material data, and commercial reasonableness matter. C071, C085–C087. | Incorporated procedure and actual predicates. | Every score must be corrected or every decision reversed. | Read adopted §1705 rules and precise §1306 interaction. |
| B33 — Education: partial | Existing FERPA channels may suffice only under the stated conditions. C084, C087. | Complete FERPA category/procedure chain. | Any school process automatically satisfies Part 17. | Read indispensable FERPA inspection/amendment/channel provisions. |
| B34 — Health/assistance: partial | Employment exception, Colorado provider location, general notice, and financial-assistance disclosures remain. C098–C100. | HIPAA, discounted-care, FDA predicates. | Health exclusion proves assistance eligibility or eliminates all notices. | Read exact HIPAA definitions and §25.5-3-502 relevant clauses. |
| B35 — Secret/security withholding: answered boundary | Withholding protections differ by actor/section; specified notices and bases remain. C031, C044, C073, C081, C083. | Protected status and applicable law. | “Trade secret” excuses every duty without explanation. | Read the exact withholding clause and incorporated protection, without actual records. |
| B36 — Cure: answered boundary | Possibility determination, receipt trigger, knowing/repeated exception, discretionary mitigation, and sunset matter. C089–C090. | Actual predicates and broader procedure. | Every violation gets 60 days or cure guarantees no relief. | Read complete applicable enforcement procedure and savings provisions if separately needed. |
| B37 — Private remedy/fault: partial | No new Part 17 action coexists with preserved existing-law actions and relative-fault rules. C091–C094. | Cause of action, standing, causation, proof, remedies. | Automatic damages or complete immunity. | Examine only an independently authorized existing-law cause and its complete predicates. |
| B38 — Contract indemnity: answered boundary | Own-act discriminatory-liability shift is limited by the precise scope and outside-use exception. C095–C096. | Actual contract and existing-law liability, all absent. | Every commercial indemnity is void. | Read generic contract-construction authority only in a separately scoped component. |
| B39 — Psychotherapy: partial | Representation bans and training/research/wellness/FDA alternatives retain all conditions. C101–C105. | Professional/FDA/IRB predicates. | Wellness labeling establishes exclusion or clinical validity. | Complete only indispensable public definitions; hold clinical and licensing merits. |
| B40 — Conversational category: partial | Public conversation simulation and each distinct exclusion govern. C106–C107. | Content/function/purpose; Article 64/HIPAA chains. | Every customer-service or recommendation interface is covered. | Read unresolved incorporated categories and final generic chatbot definitions. |
| B41 — Minor/knowledge: answered boundary | Under-18 category, reasonable age estimation, knowledge rule, and different duty dates apply. C108–C110. | Actual category/knowledge; counting convention. | No stated age means no duty, or every duty starts on the same date. | Read complete adopted age-estimation interpretation if available. |
| B42 — Incorporated content terms: unresolved | Part 17 contains express content duties but current Title 13 definitions failed access. C108, C111; S019. | Complete current §13-21-1502(7), (10). | A familiar content label substitutes for the statutory definition. | Open those exact current official clauses and their material amendment notes. |
| B43 — Minor controls: partial | Reward-intent, technically feasible prevention, reasonable dependence safeguards, protocols, and privacy tools differ. C111–C112. | Incorporated definitions and full minor-privacy regime. | Any reward is prohibited or any protocol proves compliance. | Read the precise adopted generic implementation and Part 13 minor clauses. |
| B44 — Chatbot disclosures/reporting: answered boundary | Daily/three-hour/persistent disclosure alternatives and annual reporting have different triggers. C113–C115. | Actual events and final reporting format. | A report proves safeguards work or a fixed annual due day is supplied. | Authenticate final generic reporting instructions without requesting reports. |
| B45 — Repeal/savings: partial | Compiler harmonization and §2-4-303 preservation must be distinguished. C009–C010, C125. | Judicial construction and actual incurrence, both held. | Replacement extinguishes every earlier liability. | Read narrow generic savings/application authority if a later legal component requires it. |
| B46 — Rules/frameworks: unresolved | Delegation and references are present; complete adopted rules/standard contents are not authenticated. C012, C033, C057, C059, C080, C092. | Final public rule/adoption and precise framework provisions. | Proposed text or a standard name is operative proof. | Read final adopted public instructions and their effective clauses. |
| B47 — Debt technology: excluded beyond selected boundary | Financial-domain inclusion supplies only a conditional state AI connection. C124, C127. | Federal credit, collection, privacy, digital-asset, product-specific law. | Part 17 proves debt validity, forgiveness, or product legality. | Use the separate parent questions below. |
| B48 — Actual application/parent: excluded by scope | No facts or decisions are supplied; no acceptance follows from public-text analysis. C126–C127. | Every actual application predicate and remaining jurisdiction. | This report is a compliance, eligibility, or financial decision. | Continue only with separately scoped generic public-law research. |
Analytical field · Authority entry · Evidence entry · 28 data rows
| Analytical field | Authority entry | Evidence entry | Analysis | Result |
|---|---|---|---|---|
| Authority and instrument title | ||||
| Version and compilation boundary | ||||
| Legal status | ||||
| Access date and read bounds | ||||
| Jurisdictional category | ||||
| Generic actor category | ||||
| Generic system category | ||||
| Consumer/category definition | ||||
| Covered domain | ||||
| Scope condition | ||||
| Cumulative predicates | ||||
| Alternative predicates | ||||
| Exception or exclusion | ||||
| Operative verb | ||||
| Duty and recipient category | ||||
| Incorporation and read completeness | ||||
| Quantity, unit, and base | ||||
| Trigger and counting convention | ||||
| Delivery or retention condition | ||||
| Enactment/commencement/application distinction | ||||
| Transition or savings provision | ||||
| Presumption or defense boundary | ||||
| Public enforcement boundary | ||||
| Private-remedy boundary | ||||
| Other-law dependency | ||||
| Currentness/history gap | ||||
| Application hold | ||||
| Exact next generic public-law inquiry |
Request/material subquestion · Status and finding · Claim/source/branch crosswalk · 30 data rows
| Request/material subquestion | Status and finding | Claim/source/branch crosswalk | Missing evidence and exact next permissible inquiry |
|---|---|---|---|
| 1.1 Actual title and organization | Answered within examined compilation. Current and future inventories established. | C001–C003; S001; B01. | Later adopted changes: check exact subsequent official enactments. |
| 1.2 Complete current selected Part | Answered as a body read. All displayed current definitions, duties, exceptions, additions, notes read. | C013–C059, C101–C116; S001–S003, S005–S006. | Incorporated-regime gaps are separate, below. |
| 1.3 Complete successor | Answered as a body read. Entire displayed successor read; no selected-Part remainder omitted. | C060–C116; S001, S004–S006. | Final implementing rules and construction remain partial. |
| 1.4 Operative/future/conditional classification | Partial. Adopted clauses and compiler distinctions established; exhaustive later/constitutional chain not certified. | C004–C012; B01–B03, B45–B46. | Read failed constitutional clauses and any later adopted public law. |
| 2.1 Current AI/risk/roles/consumer | Answered conditional definitions. No actual classification. | C013–C025; B04–B12. | Actual facts remain excluded; generic judicial construction unexamined. |
| 2.2 Future ADMT/material influence/domains | Answered conditional definitions. | C060–C072; B26–B28. | Final generic rules and employee/employer incorporation. |
| 2.3 Every material definition exclusion | Partial overall. Part 17 exclusions read completely; nested current definitions failed in specified titles. | C016, C021–C023, C061–C069, C107–C108, C123; S017–S019. | Read exact current failed clauses; do not substitute amendments/snippets. |
| 2.4 Territorial/resident nexus | Answered text; application held. Current/future difference preserved. | C018–C019, C064–C067; B04, B06. | Generic “doing business” construction only if separately needed. |
| 3.1 Current developer documentation/publication/reporting | Answered text and timing. | C026–C031; M012–M015; B13–B15. | Adopted forms/rules and actual predicates remain open. |
| 3.2 Current risk management/assessments | Partial. Complete statutory program/assessment rules read; external frameworks not completed. | C032–C037; M016–M019; B16–B18. | Exact public framework and adopted rule clauses. |
| 3.3 Current notice/correction/appeal | Answered selected text; incorporated opt-out partial. | C038–C045, C117–C120; B19–B21. | Complete narrow Part 13 applicability and final procedures. |
| 3.4 Future documentation/updates/records | Answered selected text. | C073–C077; M026–M028; B29. | Longer-law retention and adopted interpretation remain unexamined. |
| 3.5 Future notices/correction/review | Partial overall. Statutory duties complete; federal/FERPA/privacy interactions incomplete. | C078–C087; B30–B33. | Exact external clauses and adopted notice/review rules. |
| 3.6 Therapy/chatbot duties | Partial overall. Selected bodies complete; content/HIPAA/Article 64/minor-privacy chains incomplete. | C101–C116; B39–B44. | Exact failed/current incorporated clauses. |
| 4.1 Current exclusions/small-deployer conditions | Answered statutory predicates. | C042, C046–C055; B18, B22–B25. | External qualification and actual facts remain absent. |
| 4.2 Framework defenses/presumptions | Partial. Conditions and limited legal function established; actual standard compliance not. | C026, C032–C033, C057–C059; B15–B16, B46. | Complete relied-on public standards and adopted rules. |
| 4.3 Financial/insurance/health carveouts | Partial. Complete Part text; several incorporated authorities incomplete. | C051–C054, C082, C097–C100, C122–C123; B24–B25, B31, B34. | Current Title 10, HIPAA nested clauses, discounted-care and federal notice law. |
| 4.4 Public enforcement/cure/private-action limits | Answered narrow text; broader remedies held. | C056–C059, C088–C096; B36–B38. | Complete independent cause/process/remedy authority before any positive remedy claim. |
| 5.1 AI credit-underwriting connection | Answered bounded inclusion. Financial/lending domain plus remaining predicates. | C017, C053, C065, C082, C100, C124; B07, B25, B31. | Federal credit/underwriting rules separate. |
| 5.2 Other debt-technology extension | Excluded beyond text-supported category connection. | C107, C124–C127; B40, B47. | Separate collection, negotiation, digital-asset, embedded-credit authorities. |
| 6.1 Original adoption and delay | Answered adopted clauses; constitutional event chain partial. | C004–C005; S002–S003; M002–M004. | Failed constitutional body and unexamined conditional events. |
| 6.2 Repeal/reenactment and early clauses | Answered adopted body/application. | C006; S004 §§1–6; M005–M006. | Exhaustive later enactments/judicial application remain held. |
| 6.3 Added provisions and renumbering | Answered compiler/adopted distinction. | C007–C009; S005–S007; M007–M009. | Judicial reconciliation of any ambiguity remains unexamined. |
| 6.4 Savings | Answered general clause; actual operation unresolved. | C010, C125; S007 §2-4-303; B45. | Actual incurred liability excluded; narrow generic construction could be separate. |
| 6.5 Agency/currentness mismatch | Answered discrepancy; final rule unresolved. | C011–C012; S015–S016; B46. | Authenticate final adopted rule, publication, and effective text. |
| 7. Comparisons | Answered with qualifications. Comparison table covers category, conditions, duties, legal effect, history, and parent boundaries. | C124–C127 plus row-specific claims/sources. | Every listed application/other-law gap retained. |
| 8. Measurements | Answered for every quantity relied upon. No actual calculation or fixed period invented. | M001–M048, exact claims/sources. | General counting/tolling/service rules and actual triggers remain absent. |
| 9. Branches | Answered format and substantive coverage. B01–B48 carry rule, source, missing evidence, adverse inference, next inquiry, and status. | All branch rows. | Branch-level partial/unresolved status retained. |
| 9. Blank worksheet | Answered. All entry/analysis/result cells empty. | Section 7. | No actual record is requested or implied. |
| 10. Remaining parent area | Explicitly open. Separate next inquiries supplied below. | C124–C127; B47–B48; Section 10. | All other jurisdictions, products, actual facts, and operational conclusions. |
Log entry · What was actually read · What was not claimed · 9 data rows
| Log entry | What was actually read | What was not claimed |
|---|---|---|
| L01 — S001 | Official 2026 delivery index; complete current and future Part 17 HTML; selected complete incorporated Title 6 clauses listed in S001. | Whole Title 6; every external incorporation; PDF pixel verification; exhaustive later-law audit. |
| L02 — S002 | Complete original session-law §§1–3; partial signed-format comparison. | Independent corroboration from two formats; whole historical policy dossier. |
| L03 — S003 | Complete delay Act §§1–4, including full conditional effective clause. | Referendum or adjournment-event record investigation. |
| L04 — S004 | Complete replacement Act §§1–6, including adopted text, appropriation section, early-effective list, application, and safety clause. | Actual funding use, complete insurance law, or completed rulemaking. |
| L05 — S005 | Complete chatbot Act §§1–3; approval line and bill action/version metadata. | Actual operator conduct, age estimation, report, hearing event, or user data. |
| L06 — S006 | Complete Part 17 amendment and effective/application clauses; narrow definitional cross-reference passages. | Whole professional-practice regime or clinical interpretation. |
| L07 — S007–S010 | Exact construction, trade-secret, banking, and psychotherapy definitions identified in the register. | Whole titles, annotations as judicial holdings, actual categories or qualifications. |
| L08 — S011–S014 | Exact federal definitions/context listed in the register. | Whole federal statutory/regulatory regimes or complete nested HIPAA chain. |
| L09 — S015–S016 | Generic AG explanatory page and selected official change-index material. | Adopted-rule status for drafts, empirical implementation, or independent corroboration of the same Act. |
Log entry · Exact endpoint or grouped source · Observed failure/limit and treatment · 12 data rows
| Log entry | Exact endpoint or grouped source | Observed failure/limit and treatment |
|---|---|---|
| F01 — Initial statute index | https://leg.colorado.gov/agencies/office-legislative-legal-services/colorado-revised-statutes, redirected to https://content.leg.colorado.gov/agencies/office-legislative-legal-services/colorado-revised-statutes | Verification/JavaScript page rather than statute body. No bypass. The ordinary official 2026 download index in S001 was readable. |
| F02 — S004 signed Act | https://www.leg.colorado.gov/bill_files/116489/download | Retrieval failed, reporting content length 11,791,344. Complete official session-law alternative read. |
| F03 — S003 and S005 signed formats | Exact signed URLs in S003 and S005. | PDF metadata returned but no parsed body lines. Complete session-law alternatives read; no unseen signed-page claim. |
| F04 — Titles 7 and 12 HTML | Exact HTML URLs in S008 and S010. | Retrieval-size failures. Selected clauses read in their ordinary official PDFs. |
| F05 — Titles 8, 10, 13 and Constitution | Every exact format URL in S017–S020. | Size, parsing, or unsupported-format failures as logged. Dependent current definitions/constitutional claims held. |
| F06 — Preliminary OLRC §234 route | https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title42-section234&num=0&edition=prelim | HTTP 500. Ordinary canonical current route later readable as S011. |
| F07 — Preliminary OLRC §2000a route | https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title42-section2000a&num=0&edition=prelim | HTTP 404. A separate ordinary view.xhtml route displayed maintenance; canonical current S012 read. |
| F08 — Preliminary OLRC §2256 route | https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title18-section2256&num=0&edition=prelim | HTTP 404. Canonical current S013 read. |
| F09 — Earlier federal versions encountered | Earlier-version §234 and §2256 routes were encountered before the current canonical pages. | They were not used to represent October 20 compilation currency. Final reliance is S011–S013; same-instrument versions are grouped. |
| F10 — PDF screenshots | Attempts on final pages of S004–S006. | Returned image-display markers without inspectable pixels in the available result. Only parsed-text reading is claimed. Printed pages and zero-based indices remain separately recorded. |
| F11 — Discovery-only material | Generic statutory searches returned bill amendments, older codifications, and other summaries. | No search snippet, proposed amendment, unofficial summary, participant material, or older definition was substituted for a complete current official body. |
| F12 — Final-rule status | S015 and generic official-source discovery. | No complete final adopted rule authenticated. This is an unresolved source-status limit, not a finding that no rule exists. |
Open dependency · Precise unresolved proposition · Next permissible generic public-law inquiry · 12 data rows
| Open dependency | Precise unresolved proposition | Next permissible generic public-law inquiry |
|---|---|---|
| Current employment definitions | Exact future employee/employer category, including any current amendments and nested exclusions. | Read complete current §8-4-101(5)–(6) and materially applicable adopted amendments. |
| Insurance definitions and rules | Which generic categories and practices satisfy current/future insurance compliance treatment. | Read §§10-1-102(13), 10-14-102, 10-3-1104.9 and indispensable adopted rules in full relevant context. |
| Title 13 sexual-content and health categories | Complete meanings of §13-21-1502(7), (10), and the referenced Article 64 entity category. | Obtain readable official current bodies and exact material amendment clauses. |
| Constitutional commencement | Full independent meaning of the Acts’ referendum/safety/commencement dependencies. | Read the exact current Colorado constitutional clauses from an ordinary official readable source. |
| Final implementing rules | Additional current/future documentation, notice, review, reporting, presumption, and framework conditions. | Read complete adopted rule text, adoption instrument, and effective/application clauses; distinguish proposals. |
| Referenced frameworks | Exact contents and equivalence of NIST, ISO, or AG-designated alternatives. | Read only the public framework clauses indispensable to a later claim; preserve unavailable/private-standard text as unresolved. |
| Privacy incorporation | Full Part 13 applicability, minors’ provisions, fee authority, and exact procedural interaction. | Read complete narrow scope/exemption and minor-privacy clauses; do not assume every Part 13 clock governs every Part 17 right. |
| HIPAA/FDA/health assistance | Nested covered-entity/business-associate/provider definitions, FDA status, and discounted-care rights. | Read exact incorporated generic clauses, including relevant §25.5-3-502 provisions, before a dependent conclusion. |
| Banking category chain | Federal credit-card-bank and complete federal/out-of-state credit-union predicates. | Read the exact incorporated federal and state definitions, including 12 U.S.C. §1841(c)(2)(F), if relied upon. |
| Future AI-term construction | Meaning of “artificial intelligence system” in the harmonized future chatbot definition after omission of the old Part-wide definition. | Read adopted generic construction or amendment addressing that term; do not import §1705.2’s section-specific definition automatically. |
| Savings and temporal liability | Whether any pre-replacement liability survives in a particular setting. | Generic savings/application construction may be separately researched; no actual events or cases are supplied here. |
| Judicial/enforcement/remedy chain | Standing, causes, proof, jurisdiction, penalties, damages, immunity, review, and actual enforcement. | Separately scope a generic public-law inquiry before making any affirmative remedy statement. |
Parent seed · Exact next generic question; present hold · 17 data rows
| Parent seed | Exact next generic question; present hold |
|---|---|
| AI credit underwriting and fair lending | What complete federal credit-decision and antidiscrimination provisions apply to the relevant generic activity, independently of Colorado Part 17? No underwriting or applicant assessment. |
| Adverse-action notices | What are the complete ECOA/Regulation B and FCRA triggers, content, timing, and exceptions before using future §1704(6)’s coordination clause? |
| Credit reporting and data accuracy | Which complete federal duties concern source data, disputes, permissible purposes, and correction? Part 17 is not a completed reporting-law analysis. |
| Privacy and security | Which complete federal/Colorado privacy and security provisions govern the generic data category and activity? No actual provenance, collection, disclosure, or security finding. |
| Open banking and consumer financial data | What adopted, effective public rules govern generic access, authorization, use, and revocation? No account or permission inquiry. |
| Automated debt negotiation | Which public consumer-protection, representation, licensing, debt-adjustment, and contract rules apply to the generic activity? No authority to negotiate or settlement entitlement inferred. |
| Automated collection | Which complete federal and relevant jurisdictional collection/communication rules govern the generic conduct? No actual debt, communication, deadline, or collection permission. |
| Digital assets and DeFi | Which public product/activity definitions and regulatory boundaries apply? No asset, protocol, issuer, valuation, or transaction classification. |
| Subscription, embedded, and wage-related credit | Which generic credit/payment/wage definitions, exclusions, and effective rules apply? No product or financial outcome conclusion. |
| Provider contracts and commercial allocation | What public contract and statutory limits apply independently of future §1707’s narrow indemnity provision? No actual or model contract. |
| Federal preemption | Which exact federal provision conflicts with or displaces a specific state requirement, if any? No general preemption conclusion. |
| Other states | What complete adopted and effective public law governs the separately identified generic component? Colorado definitions are not exported. |
| Territorial, tribal, local, and foreign law | What jurisdiction-specific public authority supplies scope, applicable law, and institutional competence? No all-country or all-jurisdiction coverage. |
| Technical capability and model evaluation | What authorized evidence would establish a generic technical property? No testing, dataset, benchmark, output inspection, or actual classification was performed. |
| Economic efficacy and consumer outcomes | What suitable empirical evidence would support any claimed benefit, harm, cost, or effectiveness? Statutory duties and reporting metrics do not supply causal results. |
| Debt validity, payment, settlement, discharge, tax, and credit effects | What independent substantive law governs each question? This component supplies no debt-relief outcome or financial recommendation. |
| Operational or publication acceptance | What separately authorized review would be required before any application or publication decision? No component, parent, jurisdiction-wide, operational, or publication acceptance is supplied. |
Check · Result · 14 data rows
| Check | Result |
|---|---|
| Prior reports used as premises? | No. This investigation used freshly opened public sources for R100. |
| Complete selected Part read? | Yes, for both versions displayed in the official 2026 compilation, including the psychotherapy and conversational-service additions. |
| Current versus future separated? | Yes. Current June 30 application language, adopted January 2027 replacement, early-effective clauses, and chatbot-specific dates are distinguished. |
| Complete material main adopted acts read? | Yes for S002–S005; complete selected amendment/application clauses for S006. Read bounds are explicit. |
| All incorporations completed? | No. Exact failures and unexamined nested regimes are identified; dependent findings remain held. |
| Agency summary treated as law? | No. The signing-date conflict is preserved and resolved only to the adopted-source date; draft-rule descriptions remain nonfinal evidence. |
| Parsed text represented as pixels? | No. No visual verification of the PDF pages is claimed. |
| Same-source formats treated as independent corroboration? | No. They are grouped by instrument. |
| Exact connectors and exceptions preserved? | Checked for current/future definitions, small-deployer conditions, framework defense, notice alternatives, sector clauses, cure conditions, and chatbot timing. |
| Quantities converted into invented deadlines or models? | No. Units, triggers, alternatives, and undefined counting conventions are recorded; no actual calculation. |
| Actual or invented identifying records queried or created? | No such substantive inquiry or record is part of this investigation. |
| Blank worksheet genuinely blank? | Yes. Entry, analysis, and result cells contain no facts or findings. |
| Actual classification, compliance, eligibility, liability, or financial result? | None supplied. |
| Independent review or full later-history certification? | Neither claimed. This is the researcher’s own bounded source-and-cross-reference check. |
Read the evidence with its boundaries. These are saved research components, including revisions. A scoped coordinator review checks selected evidence; it does not certify every claim, a complete jurisdiction, current law or individual applicability. Dates and access limits remain attached to the records.
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Recorded check status: bounded review complete selected checks core primary refresh andall other source application holds
Keep the source version, actual read extent and jurisdiction with the proposition. A link or researcher access claim is not a substitute for an operative primary passage.
Recorded check status: fresh primary refresh failed or gated original claims dated notaccepted
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: selected primary body read with uncompleted currentness crossreferences
Recorded check status: fresh primary refresh failed or gated original claims dated notaccepted
Recorded check status: fresh primary refresh failed or gated original claims dated notaccepted
Recorded check status: selected primary body read with uncompleted currentness crossreferences
Recorded check status: fresh primary refresh failed or gated original claims dated notaccepted
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: fresh official explanatory page only not adopted rule orAct
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
Recorded check status: original record full read unreopened or originalfailed holds retained
The saved component-level coverage record keeps answered, partial, blank and unresolved branches distinct. A coverage label is not acceptance of a whole subject or jurisdiction.
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Recorded check status: recorded; no individual primary acceptance inferred
Read the evidence with its boundaries. These are saved research components, including revisions. A scoped coordinator review checks selected evidence; it does not certify every claim, a complete jurisdiction, current law or individual applicability. Dates and access limits remain attached to the records.
No currently queued material correction is mapped to this component. This does not remove its currentness, access, jurisdiction or application limits.
scoped coordinator selected transition review complete core primary refresh failed all source application parent holds
Original saved Markdown SHA-256: 2f98b470f4d9e49749bd8461990fd386c430f0d1be79a761063a3fc9e85064f7. Public formatting, private-reference removal and correction annotations are separate from that immutable original.