Skip to content
Français

A map of the landscape

  • Lesson 4
  • 25 min
  • Module 2: Laws and standards in plain words

Where we are

In Module 1, we found Larkfield's eight AI systems and gave each one an owner. The next question is which rules those owners must follow, and the words are confusing: law, standard, framework, contract. In this lesson, we draw a map of the landscape, starting with something many people know: renting a car in another country.

Plays from YouTube. Nothing loads from YouTube until you press play. Privacy

What you will be able to do

Before you can follow a rule, you must know what kind of rule it is. You sort the texts around AI into six kinds, see which ones bind an organisation, and list the rules for one Larkfield system.

Before you startWhat to know and to have readyAbout 25 minutes

What you need to know

What you need

This course is not legal advice. It explains what each rule is for, so that you know what to ask a lawyer. The official texts quoted on this page: PIPEDA, the EU AI Act, Regulation (EU) 2024/1689, the Directive on Automated Decision-Making, the NIST AI Risk Management Framework and NIST’s crosswalks (each checked 22 October 2026).

You fly to another country and rent a car. Several kinds of rule now apply to you, and they are not the same kind.

The traffic law of that country binds you. It does not matter where you live: you drive there, so its law applies. You signed a rental contract. It binds you and the rental company, and nobody else. The car passed a safety test that its maker chose; a test centre checked it against a written standard. Your friend gave you a driving guide with good advice for mountain roads. You may follow it or not. And the radio says that the government plans a new speed limit. Today it is only a plan.

When the police stop you, only the law and your licence count. When you return the car with a scratch, the contract counts. The guide helps you drive well, but it protects you from neither.

Farida, Larkfield’s first risk and compliance lead, asks the team a simple question in her first week: “Which rules do our AI systems follow?” Larkfield, its people and its systems are constructed for this course.

The answers mix every kind of rule:

  • Omar: “We follow the NIST framework, so we are covered.”
  • Tomás: “We use AI from big vendors. The rules are their problem.”
  • Mei: “Is ISO/IEC 42001 a law? A customer asked about it.”
  • Sam: “What about the weekly digest script? It is not an AI law thing, is it?”

Sam’s question shows the failure. The weekly digest script sends a week of customer messages, with names and order numbers, to an AI service. Larkfield has no contract with that service. Nobody checked it, because everybody looked for “AI rules”. But Canada’s federal privacy law already makes an organisation responsible for the personal information it controls. That stays true when another company processes the information for it (PIPEDA, Schedule 1, principle 4.1.3). The oldest rules apply first, and nobody had listed them.

The idea: six kinds of rule, and who each one binds

Section titled “The idea: six kinds of rule, and who each one binds”

A rule here is any text that says what an organisation should do. The map of this course sorts them into six kinds. For each kind, ask two questions: does it bind, and whom does it bind?

  • A law binds everyone it applies to, whether they agree or not. The EU AI Act and Canada’s federal privacy law (PIPEDA) are laws.
  • A bill is a proposed law. It binds nobody yet, and it may change or never pass.
  • A government policy binds only the government bodies that it names. Canada’s Directive on Automated Decision-Making is one. It applies to federal institutions, not to private companies.
  • A standard is a document written by a standards body, such as ISO. It binds you only if you choose it, or if a contract or a law asks for it. Some standards set requirements that an outside body can check and certify; others only give guidance.
  • A framework is voluntary guidance. The NIST AI Risk Management Framework says itself that it is voluntary.
  • A contract binds the parties who sign it, and only them: your vendors’ terms, your customers’ contracts.
Six kinds of rule point to 'your organisation'. Three are binding: a law (the EU AI Act, the GDPR, PIPEDA, Quebec's privacy act): must follow, if it applies to you; a contract (a vendor's terms, a customer's contract): must follow, because you signed; a government policy (Canada's Directive on Automated Decision-Making): binds only the government bodies it names. Three are not binding by themselves: a standard (ISO/IEC 42001 and 42005): follow if you choose, or if a contract asks; a framework (the NIST AI RMF): follow if you choose; a bill (Canada's C-34 and C-36): a dotted line, watch, it may become law.
The landscape map. The label on each arrow says why a rule binds you, or why it does not.
Text description of the diagram

The map has six boxes, in two groups, with an arrow from each box to your organisation. The first group is binding. A law, such as the EU AI Act, the GDPR, PIPEDA or Quebec’s privacy act: you must follow it, if it applies to you. A contract, such as a vendor’s terms or a customer’s contract: you must follow it, because you signed it. A government policy, such as Canada’s Directive on Automated Decision-Making: it binds only the government bodies that it names. The second group is not binding by itself. A standard, such as ISO/IEC 42001 or 42005: you follow it if you choose to, or if a contract asks for it. A framework, such as the NIST AI RMF: you follow it if you choose to. A bill, such as Canada’s C-34 and C-36: a dotted arrow, because you only watch it; it may become law.

The kinds also connect. A contract can make a standard required: a large customer can ask its suppliers for a certificate. A framework can be mapped to a standard: NIST lists a crosswalk between its framework and ISO/IEC 42005. A bill can become a law. But the connections go one way only. Following a voluntary framework does not, by itself, show that you meet a law. So Omar’s “we follow NIST, so we are covered” mixes two kinds.

The same organisation can be inside one law and outside another. Like the driver, the answer depends on where the system is used, whose data it uses, what you signed and what you chose.

A flow for one system with four questions. One: where is its output used, and whose data is in it? Answer: the laws of those places. Two: what did we sign? Answer: the contracts with the vendor, customers or partners. Three: what did we choose? Answer: the standards and frameworks that we adopted. Four: what is proposed? Answer: bills to watch. The four answers make one row of the table: the rules, our role, the reason, and what we are not sure of. The row leads to the questions for a lawyer.
Four questions find the rules for one system. The last box is always the questions for a lawyer.
Text description of the diagram

The flow starts with one system and asks four questions. First: where is its output used, and whose data is in it? That gives the laws of those places. Second: what did we sign? That gives the contracts, with the vendor, with customers or with partners. Third: what did we choose? That gives the standards and frameworks that we adopted. Fourth: what is proposed? That gives the bills to watch. The four answers fill one row of a table: the rules, our role, the reason, and what we are not sure of. From that row, we write the questions for a lawyer.

The last box matters most. You do not decide whether a law applies to your organisation; a lawyer does. Your job is to bring the facts that the lawyer needs and the questions that you cannot answer.

A tiny example: the rules for the document assistant

Section titled “A tiny example: the rules for the document assistant”

Farida starts with the simplest system, the document assistant. Its card says: it answers staff questions from Larkfield’s documents, with citations. Staff in Canada use it, and so do the staff of one partner shop. Larkfield sells to customers in Canada and in the European Union (constructed for this course).

She asks the four questions, one at a time, and writes each answer down:

Question Farida’s answer Kind of rule
1. Where is the output used? Staff in Canada read the answers. The partner shop’s staff too, but where are they? Unknown. law (Canada); the EU AI Act only if the output is used in the EU
1. Whose data is in it? Internal documents, some with personal information law: Canada’s privacy law (PIPEDA)
2. What did we sign? The model provider’s contract; an agreement with the partner shop contract
3. What did we choose? Nothing yet no standard or framework is required
4. What is proposed? Canada’s privacy bill C-36 bill: watch only
Not sure where the partner shop’s staff are —
Question for a lawyer Does serving another company’s staff change Larkfield’s role under the EU AI Act? —

One row of the EU AI Act is still empty: the system’s category and Larkfield’s role. That needs the law itself, which comes next. Notice what the row already shows. The document assistant is bound by a law and two contracts today. It is bound by no standard, because Larkfield chose none.

Farida opens the map of laws and standards and marks each entry for Larkfield as a whole:

Entry Kind Does it bind Larkfield?
EU AI Act law It can apply to a company outside the EU when the output of its AI system is used in the EU (Article 2(1)(c)). A question for the lawyer, system by system.
GDPR law It may matter for EU customers’ data. A question for the lawyer.
PIPEDA law Canada’s federal privacy law for private companies: most likely, as Larkfield reads it. The lawyer confirms.
Quebec’s private-sector privacy act law It may matter for customers in Quebec. A question for the lawyer.
Directive on Automated Decision-Making government policy No: it is for federal institutions. It is still a good model to learn from.
Bills C-34 and C-36 bill No: they are not law. Watch them.
ISO/IEC 42001 and 42005, NIST AI RMF standard, framework Only if Larkfield chooses them, or a customer’s contract asks for them.
Model provider’s terms, TicketHarbor’s terms (made up for this course) contract Yes, because Larkfield signed them.
The weekly digest script’s AI service — No contract at all: the gap that Sam found.

Two lines are surprising. The script, which looks like the smallest system, has the biggest gap, and it is a contract gap, not an AI-law gap. And the Directive does not bind Larkfield at all, but it shows how a careful organisation assesses an automated decision. A later case study reads published assessments made under it.

Discuss: “We follow NIST, so we are covered”

Section titled “Discuss: “We follow NIST, so we are covered””

Omar wants to tell a large EU customer that Larkfield “follows the NIST framework, so it complies with the AI rules”.

  • Omar: “NIST is the best-known AI framework. Saying we follow it answers the customer.”
  • Tomás: “And our model comes from a big vendor. The AI Act is their job.”
  • Mei: “The customer asked about the EU AI Act and about ISO/IEC 42001. Neither is NIST.”

Before you read on, answer these:

  1. What kind of rule is each text in this discussion?
  2. Can following a framework show that Larkfield meets a law?
  3. What should Larkfield send the customer instead?

The course’s answer. The NIST framework is voluntary. The EU AI Act is a law. ISO/IEC 42001 is a standard. Following a framework is useful, but it does not show that a law’s duties are met. Tomás’s point is also too quick. The Act gives duties both to the company that provides a system and to the company that uses it (Article 3(3) and (4); for high-risk systems, Article 26). So Larkfield cannot hand the question to its vendor. Larkfield should send the customer facts: which systems touch the customer’s data, what each one does, and which rules Larkfield applies. If the customer’s contract asks for something specific, such as a certificate, the contract decides.

What would change the answer: if the customer only asked about a risk process, the framework would be a fair part of the reply. If the customer’s contract required ISO/IEC 42001 certification, the standard would bind Larkfield through the contract.

Use the map each time a new system arrives or a vendor changes its terms. Use it also when a system moves to a new country or a new kind of customer. Keep one row per system, not one row for the whole company. The rules differ by system, as the document assistant and the script show.

Do not use the map to decide whether a law applies to you. It tells you what to ask. The cost is a few hours to fill the table, and later some of a lawyer’s time. That time is shorter and cheaper when you arrive with the rows filled in.

Common mistake

A list of rules with no contracts in it

Symptom: the company’s list of “rules we follow” names the EU AI Act, a framework and a standard. It names no contract. A script sends customer data to a service that nobody signed with.

Cause: the team looked only for rules with “AI” in their name. Privacy laws and contracts already applied, and nobody listed them.

Fix: ask the four questions for every system, including “what did we sign?”. An empty answer to that question is a finding, not a blank. Give it to the system’s owner and to the person who owns privacy, Mei at Larkfield.

Check your understanding

Sort each text into one of the six kinds, and say whom it binds: (a) the EU AI Act; (b) Canada's Bill C-36; (c) the NIST AI Risk Management Framework; (d) TicketHarbor's terms of service (made up for this course); (e) Canada's Directive on Automated Decision-Making; (f) ISO/IEC 42001.

Show the answer

(a) A law: it binds the people it applies to, including some companies outside the EU when their AI output is used in the EU. (b) A bill: it binds nobody, because it is not law and may change. (c) A framework: voluntary, it binds nobody unless they choose it. (d) A contract: it binds Larkfield and TicketHarbor, because they signed it. (e) A government policy: it binds the federal institutions that it names, not private companies such as Larkfield. (f) A standard: it binds an organisation only if it chooses it, or if a contract or a law asks for it.

Check your understanding

Omar says: 'We follow the NIST framework, so we comply with the AI rules.' Explain in two or three sentences what is wrong with this, and what Larkfield should do instead.

Show the answer

A framework is voluntary guidance, and following it does not show that a law’s duties are met: they are different kinds of rule. Larkfield should list the rules system by system, with the four questions. Where is the output used, and whose data? What did we sign? What did we choose? What is proposed? It should then ask a lawyer the questions that it cannot answer itself.

Check your understanding

The weekly digest script is the smallest of Larkfield's systems. Why does it have the biggest gap on the map?

Show the answer

It sends customer messages with names and order numbers to an AI service, and Larkfield has no contract with that service. Canada’s privacy law makes Larkfield responsible for personal information under its control, also when another company processes it. So the gap is in the oldest kinds of rule, a privacy law and a contract, not in a new AI law.

Recap

  • Six kinds of rule: a law binds everyone it applies to; a bill binds nobody yet; a government policy binds the bodies it names; a standard binds you if you choose it or a contract asks; a framework is voluntary; a contract binds the parties who signed.
  • Which rules apply depends on where the output is used, whose data it uses, what you signed and what you chose. Fill one row per system.
  • Following a framework does not show that you meet a law. The oldest rules, privacy law and contracts, often hold the biggest gaps.
  • The last box is always the questions for a lawyer.

You can now tell a law from a standard or a framework, and list the rules for one system. But the document assistant’s row still has an empty cell: its category and Larkfield’s role under the EU AI Act. Next, you read that law in plain words.

Next: The EU AI Act