TA-14United StatesAI Governance Jurisdiction

JURISDICTION MODULE · US

United States AI Governance

Federal, state, local, sector, procurement, and enforcement landscape

Review United States AI governance without converting a distributed legal landscape into a single national rule. Preserve the issuing authority, jurisdiction, sector, regulated activity, effective date, enforcement basis, and relationship between federal, state, local, and voluntary sources.

5Library records
2Source types
4Issuing bodies
6Applicability gates

AUTHORITY BOUNDARY

Preserve legal force before mapping governance.

A federal framework, agency action, state statute, municipal rule, procurement condition, sector obligation, and voluntary standard do not carry the same legal force. Each source must remain attached to the authority that issued it and the activity it can actually govern.

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.

01Federal statutes and agency regulations
02Executive and administrative instruments
03State statutes, regulations, and enforcement actions
04Municipal and local automated-decision requirements
05Civil-rights, employment, consumer-protection, and sector law
06Government procurement and contractual controls
07Standards, frameworks, and voluntary guidance
08Court decisions, regulator interpretations, and official notices

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.

01

Federal, state, local, tribal, or multi-jurisdiction activity

02

Developer, provider, deployer, operator, purchaser, or affected party

03

Public-sector, employment, credit, housing, health, education, or consumer use

04

Automated decision, consequential decision, generative output, or supporting tool

05

Existing sector law, civil-rights duty, procurement term, or AI-specific rule

06

Effective date, transition period, exemption, threshold, and enforcement authority

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

System purpose, role assignment, and jurisdictional nexus

Preserve source, owner, date, scope, continuity, and review status.

02

Impact, risk, testing, validation, and monitoring records

Preserve source, owner, date, scope, continuity, and review status.

03

Notices, explanations, appeal pathways, and human-review records

Preserve source, owner, date, scope, continuity, and review status.

04

Data provenance, evaluation boundaries, and material-change history

Preserve source, owner, date, scope, continuity, and review status.

05

Procurement terms, vendor representations, and allocation of responsibility

Preserve source, owner, date, scope, continuity, and review status.

06

Incident, complaint, correction, enforcement, and outcome records

Preserve source, owner, date, scope, continuity, and review status.

GOVERNANCE LIBRARY RECORDS

Available sources for United States.

Browse full library →

ROUTE QUESTIONS

Questions that must be resolved before execution.

01Which authority can bind this actor and this activity?
02Is the source enacted law, enforceable regulation, official guidance, or voluntary practice?
03Does an existing sector or civil-rights obligation govern before an AI-specific rule is considered?
04Which state or local requirements attach to the system's use or affected population?
05What evidence supports each bounded duty without overstating national applicability?
06What unresolved issue requires counsel, regulator guidance, or further factual development?

TA-14 LEGAL IMPLEMENTATION METHOD

From official source to governed determination.

01

Source

Preserve the official instrument, issuing authority, version, date, language, and publication record.

02

Applicability

Determine jurisdiction, actor, role, system, sector, exclusions, thresholds, and timing conditions.

03

Requirement

Separate each obligation, prohibition, exception, responsible actor, and triggering condition.

04

Evidence

Identify the records, authority, controls, continuity, and outcomes needed to support the requirement.

05

Route

Compile the bounded requirement into bindings, commitments, execution limits, and decision gates.

06

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.

Build a Route

TA-14 Exchange Activity

Public activity recorded across the Exchange

Visitors

Page Views

TA-14 Authority Governance Institution