Section node
Zip code as proxy
775 ILCS 5/2-102(L)(2)
- What this page is
- Section node, 775 ILCS 5/2-102(L)(2)
- Checked against the official source
- 2026-08-15Changed
- Responsible publisher
- ExploreWorld Legal, editorial deskLiability position
Short answer
What does 775 ILCS 5/2-102(L)(2) require, and where does it carry an outcome in the rule tree?
775 ILCS 5/2-102(L)(2) is the paragraph the US AI rules decision agent rests on for this question. Use of zip code as a proxy for a protected class. The block was read against the publisher on 2026-08-15 and carries 0 outcomes in the agent's rule tree. The reference can be cited as it stands, with a link to the official text and a content hash.
775 ILCS 5/2-102(L)(2)Checked against the publisher 2026-08-15Official text
A source reference, not legal advice.
- Jurisdiction
- 775 ILCS 5/2-102
- Section node
- proxy
- Read
- 2026-08-15
- Hash
- sha256:9b2a6cf21e3c755a
Outcomes resting on this section
The rules below point to this section in their outcome. The verdict is a machine classification, not a judgment on an individual matter.
No outcome in the tree points to this section yet.
Section nodes
- Developer dutiesColo. Rev. Stat. § 6-1-1702
- Deployer dutiesColo. Rev. Stat. § 6-1-1703
- Impact assessmentColo. Rev. Stat. § 6-1-1703(3)
- Consumer notice and appealColo. Rev. Stat. § 6-1-1703(4)
- Public statementColo. Rev. Stat. § 6-1-1703(5)
- Discriminatory use775 ILCS 5/2-102(L)
- No defence for the systemUtah Code § 13-72-101
- Disclosure on requestUtah Code § 13-72-201
- Regulated occupationsUtah Code § 13-72-202
The verdict is a machine classification of the outcome, not legal advice and not a compliance decision.
Verifiable trust signals
- Six fixed blocks, one source per line
- No sentence written by a language model
- Engine version and read date on every answer
- No customer data, no documents, no advice
- Model card and audit published under the EU AI Act