Teacher material · Page · Unpublished in Canvas

Facilitator's Guide: AIR Unit 0 — Intro to AI

Canvas state
Unpublished

FACILITATOR GUIDE · AIR UNIT 0

Mission: Build a Smart Ocean System

A five-day, teacher-led introduction to robots, algorithms, machine-learning models, and human judgment.

5 DAYS25 CORE POINTSTEACHER-LED

The core experience

Teach the full sequence whole group with the AIR teacher deck. Students use one four-page Mission Log across the week. Canvas pages are the accessible review, absence, and submission route. They are not a second competing curriculum.

Download teacher PowerPoint · Make a Google copyDownload Mission Log · Word · Make a Google copyDownload Mission Log · PDF

Five-day teaching map

DayLearningStudent evidenceDeck
Day 1Robot, algorithm, and model are different parts of one system.Classify + system trace1–8; leave 8
Day 2Start with a user, job, and constraint.Robot design brief · 59–14; leave 14
Day 3Algorithms need ordered, testable directions.Algorithm + trace + revision · 1015–21; leave 21
Day 4Models learn patterns from varied examples.Model tests + improvement · 1022–28; leave 28
Day 5A smart system connects robot, algorithm, model, and human judgment.Final system brief + DOL29–36; leave 35

Topic, objective, and demonstration of learning

Topic: Robots, algorithms, and machine-learning models as connected systems.

Objective: Students will classify system parts, design a robot for a user need, write and test an algorithm, and improve a model using evidence.

DOL: “In our system, the robot ___, the algorithm ___, and the model ___. A human should step in when ___.”

Before Day 1

  • Print one Mission Log per student or provide the editable Word copy.
  • Test the four core videos, the Teachable Machine site, and any optional video you plan to use.
  • Ask students to bring or choose two visually different classroom objects for Day 4.
  • Decide whether partners will share a device during the model lab.
  • Keep the optional video checks and extensions unpublished unless you plan to use them.

Daily facilitation moves

  1. Notice: begin with the deck hook before defining terms.
  2. Name: give the term only after students identify the pattern.
  3. Model: trace one complete example aloud.
  4. Build: leave the work slide projected while students create evidence.
  5. Check: require a partner trace or test before submission.

Point-of-use support

The deck and Mission Log supply word banks, complete stems, labeled examples, and leave-up success criteria where students use them. Students may sketch, dictate to a partner, or type their evidence. Do not require polished art.

Watch for: confusing a rule with a learned model; writing vague algorithm steps; testing with training examples; treating confidence as certainty; or letting the robot act in a high-consequence situation without a human check.

Optional routes

  • Edpuzzle: YouTube is the default. If you want embedded questions or Live Mode, copy the public Edpuzzle lessons into your account, connect them as External Tool assignments, save unpublished, and test in Student View.
  • Ocean sustainability PSA: use the longer Scratch + research extension only when you have additional days. Download the optional PSA packet
  • Xello Education Experiences: use after district access is tested. It is not required for the technical AIR sequence.

Official tools and references: