JURISDICTION MODULE · CA
Canada AI Governance
Federal, provincial, privacy, automated-decision, and sector governance
Review Canadian AI governance through the correct federal, provincial, territorial, public-sector, private-sector, privacy, human-rights, consumer, and sector authority. Preserve the status of proposed instruments separately from enacted and enforceable obligations.
AUTHORITY BOUNDARY
Preserve legal force before mapping governance.
Canadian governance may arise from federal law, provincial or territorial law, public-sector directives, privacy requirements, human-rights duties, sector regulation, procurement conditions, or voluntary standards. Proposed legislation must never be represented as enacted law.
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, regulations, and parliamentary instruments
02Provincial and territorial statutes and regulations
03Public-sector automated-decision directives and policy
04Federal and provincial privacy requirements
05Human-rights, employment, consumer, and sector obligations
06Regulator findings, guidance, and official interpretations
07Government procurement and contractual controls
08National and international standards used in Canadian practice
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.
Federal, provincial, territorial, municipal, or cross-border activity
Public institution, private organization, service provider, or regulated professional
Personal information, automated decision, high-impact use, or public service delivery
Commercial, employment, health, finance, education, or government context
Enacted requirement, directive, policy, proposed bill, or voluntary framework
Consent, notice, explanation, assessment, retention, access, and correction 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
Organizational role, lawful authority, and jurisdictional basis
Preserve source, owner, date, scope, continuity, and review status.
02
Privacy, impact, algorithmic, and risk-assessment records
Preserve source, owner, date, scope, continuity, and review status.
03
Data collection, use, disclosure, retention, and access records
Preserve source, owner, date, scope, continuity, and review status.
04
System testing, validation, monitoring, and human-oversight evidence
Preserve source, owner, date, scope, continuity, and review status.
05
Public notice, explanation, recourse, and correction mechanisms
Preserve source, owner, date, scope, continuity, and review status.
06
Version, change, incident, complaint, and outcome histories
Preserve source, owner, date, scope, continuity, and review status.
GOVERNANCE LIBRARY RECORDS
Available sources for Canada.
ROUTE QUESTIONS
Questions that must be resolved before execution.
01Which federal, provincial, or territorial authority applies?
02Is the actor a public body, private organization, contractor, or regulated entity?
03Is the cited instrument enacted, in force, proposed, advisory, or contractual?
04What privacy, human-rights, consumer, or sector duty already governs the use?
05What assessment and explanation evidence is required for the bounded activity?
06What remains unresolved because the legal instrument or facts are still developing?
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.