Concern 806 · Working draft · editorial review in progress

Canada's AIDA (proposed and stalled)

Canada's proposed Artificial Intelligence and Data Act illustrates the risk of confusing a debated bill with an enforceable law.

Understanding the concern

AIDA was part of Bill C-27 in the parliamentary session that ended in January 2025. The proposal addressed responsibilities around high-impact AI, but that bill did not complete the process of becoming law. An archived parliamentary page can still display its last stage, which is not evidence that it remains active legislation.

The broader concern is a gap between public expectations and actual legal protection. Think of a draft school policy that was discussed but never adopted: it may influence later work without being the rule in force. Canada's existing laws and federal automated-decision policies must be assessed separately from the old AIDA proposal.

An example

A company says it follows AIDA as though the unpassed bill were a government approval of its product.

Illustrative unless identified as a documented case.

Words in plain English

AI
Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.

Evidence and its limits

The parliamentary source establishes this bill's history. It does not establish that Canada has no other AI-related duties or that a later proposal would be identical.

Explore these sources in the library →
Broader frameworks and background

These resources provide context. They do not establish every claim in this concern.

A question to discuss

Is the document being cited an enacted law, a current proposal or an archived proposal?

Keep track of different views, what needs checking, and any next step in your own discussion notes.

Open discussion notes →
Principles for the conversation

Before you finish · reflect together

Virtues and principles to consider

Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.

Accountability

Accountability means being answerable for decisions and taking responsibility for repair. It requires more than saying that the software made the choice.

Name the person or team responsible, keep useful records, and give them authority to correct problems. Make the route to a complaint clear to the people affected.

Ask together: Who will answer for the outcome and help put things right?

Prudence

Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.

Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.

Ask together: What is a careful next step, and when should we stop or change course?

Unity

Unity means working toward shared purposes while making room for real differences. It does not require everyone to have the same experience, beliefs, or opinion.

Look for a goal people can share, then explore disagreements about how to reach it. Make sure quieter or less powerful voices can influence the result.

Ask together: What purpose can we share while respecting our differences?

Editorial ratings

These are editorial judgments from the register, not measured probabilities or predictions about your situation.

Severity
Serious · 3/5
Likelihood
Widely observed · 4/5
Time horizon
Now
Register risk score
12
About the register and scoring →
More ways to explore

Search for more writing

For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.

Explore a proposed use of AI →