JURISDICTION MODULE · JX
Colorado, United States AI Governance
Governance jurisdiction record set
Review the governance sources associated with this jurisdiction while preserving source authority, legal force, regulated role, applicability, version, evidence expectations, and unresolved questions.
AUTHORITY BOUNDARY
Preserve legal force before mapping governance.
Every source must remain attached to its issuing authority, legal status, scope, effective date, and applicability conditions. A library record supports research and route construction; it does not independently establish legal advice or compliance.
SOURCE FAMILIES
Enter through the authority that can govern the activity.
This module separates source families so a route can identify what is binding, what is conditional, what is interpretive, and what remains voluntary.
01law
APPLICABILITY CONTROL
A jurisdiction name alone never establishes applicability.
A bounded legal route must identify the actor, activity, system, sector, geography, timing, authority, and triggering condition before any compliance conclusion is allowed to move toward execution.
Jurisdiction and issuing authority
Regulated actor and organizational role
System, activity, sector, and affected party
Legal force, effective date, and version
Evidence required for a bounded determination
Unresolved questions requiring further review
EVIDENCE EXPECTATIONS
Translate duties into inspectable records.
Evidence must support the exact claim, role, system, version, period, and jurisdiction under review. A policy statement alone does not prove execution.
01
Official source and publication record
Preserve source, owner, date, scope, continuity, and review status.
02
Applicability and role determination
Preserve source, owner, date, scope, continuity, and review status.
03
System and activity scope
Preserve source, owner, date, scope, continuity, and review status.
04
Authority and responsibility records
Preserve source, owner, date, scope, continuity, and review status.
05
Testing, monitoring, and outcome evidence
Preserve source, owner, date, scope, continuity, and review status.
06
Review, challenge, correction, and version history
Preserve source, owner, date, scope, continuity, and review status.
GOVERNANCE LIBRARY RECORDS
Available sources for Colorado, United States.
ROUTE QUESTIONS
Questions that must be resolved before execution.
01What authority issued the source?
02What legal force does it carry?
03Who and what fall within scope?
04When does the obligation apply?
05What evidence supports the determination?
06What remains unresolved?
TA-14 LEGAL IMPLEMENTATION METHOD
From official source to governed determination.
Source
Preserve the official instrument, issuing authority, version, date, language, and publication record.
Applicability
Determine jurisdiction, actor, role, system, sector, exclusions, thresholds, and timing conditions.
Requirement
Separate each obligation, prohibition, exception, responsible actor, and triggering condition.
Evidence
Identify the records, authority, controls, continuity, and outcomes needed to support the requirement.
Route
Compile the bounded requirement into bindings, commitments, execution limits, and decision gates.
Verification
Preserve the determination so another reviewer can inspect, challenge, replay, and correct it.
BUILD THE GOVERNED ROUTE
Do not turn a legal summary into execution permission.
Preserve the official source, map applicability, attach bounded evidence, identify unresolved conditions, and route the result through an inspectable TA-14 determination.