JURISDICTION MODULE · UK
United Kingdom AI Governance
Regulator-led, sector-based, rights, safety, and assurance landscape
Review United Kingdom AI governance through the regulator, statute, sector, public-law duty, data-protection obligation, safety expectation, procurement condition, and assurance mechanism that actually governs the activity. Keep principles and guidance distinct from enforceable duties.
AUTHORITY BOUNDARY
Preserve legal force before mapping governance.
A cross-sector principle does not automatically carry the same force as legislation, regulator rules, a statutory code, an enforcement notice, or a contractual requirement. The legal basis and responsible regulator must remain visible throughout the route.
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.
01Primary and secondary legislation
02Data-protection and information-rights requirements
03Sector-regulator rules, guidance, and enforcement
04Equality, employment, consumer, competition, and public-law duties
05Product safety, cybersecurity, and online-safety requirements
06Central and local government procurement controls
07Assurance, testing, audit, and technical standards
08Government policy, consultations, and regulator coordination
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.
United Kingdom nation, regulator, sector, market, and affected person
Developer, supplier, deployer, employer, public authority, or regulated firm
Personal-data processing, automated decision, safety function, or public service
Binding statute, regulator rule, statutory guidance, policy, or voluntary assurance
Territorial reach, market placement, establishment, targeting, and cross-border activity
Authorization, notice, fairness, accountability, contestability, and oversight conditions
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
Purpose, role, regulator, sector, and lawful-basis records
Preserve source, owner, date, scope, continuity, and review status.
02
Data-protection, equality, safety, and impact assessments
Preserve source, owner, date, scope, continuity, and review status.
03
Testing, validation, assurance, monitoring, and audit evidence
Preserve source, owner, date, scope, continuity, and review status.
04
Human authority, review, escalation, and contestability records
Preserve source, owner, date, scope, continuity, and review status.
05
Supplier claims, procurement conditions, and allocation of responsibility
Preserve source, owner, date, scope, continuity, and review status.
06
Incident, complaint, regulator-contact, correction, and outcome histories
Preserve source, owner, date, scope, continuity, and review status.
GOVERNANCE LIBRARY RECORDS
Available sources for United Kingdom.
UK
RECORD DEVELOPMENT
The jurisdiction architecture is active.
Source records are being added through the Governance Library. The module remains usable now for applicability analysis, evidence planning, and route construction without presenting unfinished research as legal authority.
ROUTE QUESTIONS
Questions that must be resolved before execution.
01Which regulator or statutory authority governs the activity?
02Is the source legally binding, regulator guidance, policy, assurance practice, or consultation material?
03Which existing data, equality, safety, employment, consumer, or sector duty applies?
04What territorial and market connection brings the system within scope?
05What evidence supports accountability, fairness, safety, and meaningful human authority?
06What issue remains unsettled and requires legal or regulator review?
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.