Idaho Department of Education · Content and Curriculum · 9–12 Artificial Intelligence

Idaho AI Classroom

Classroom-ready lessons for the 2026 Idaho 9–12 Artificial Intelligence Content Standards.

Draft created June 2026. Forty-two full lesson plans — one per standard. This file is a standalone document: open it in any browser, search, print, or save as PDF. No account and no internet required after download.

42Lessons
3Domains
50 minCore period

How to use this bank

Standards are not curriculum

The Idaho Content Standards define what students are expected to know and be able to do. They do not define how teachers should teach. This document is local curriculum: one full lesson per 2026 9–12 Artificial Intelligence standard, written for a 50-minute period or a 90-minute block.

Differentiation, offline fallbacks, and FERPA-aware tool choices are built into every plan. Districts choose approved tools. No lesson requires a student to create an account or paste private writing into an unapproved system.

AIF — AI Fluency (recommended 9–10). AII — AI Impact (recommended 11–12). AITA — AI Technical Aptitude (CS / engineering).

Idaho 9–12 AI Standards Committee

Ben Peterson · Casey Kennington · Dale Hiscock · Jenna Boggan · Sarah Allen · Stephen Rudy

Suggested sequence

Pacing guide

One local option. Adjust for block schedules, trimesters, and rural connectivity.

01 · Semester 1 · Weeks 1–4

What AI is — and is not

9–10 · 4 weeks · Appropriate use, model families, physical vs. simulated worlds

Open with judgment, not tools. Students should leave this unit able to name when a calculator, a search, a human, or an AI is the right move.

02 · Semester 1 · Weeks 5–9

Think with it, not for it

9–10 · 5 weeks · Cognitive offloading, critique, hallucination, sensory grounding

Pair every generation task with a verification task. Academic-integrity conversations belong here, before high-stakes writing season.

03 · Semester 1 · Weeks 10–14

Agents, code, and communication

9–10 · 5 weeks · Agents, simple code generation, interpreting output for an audience

Keep code projects tiny and runnable. Career connections should name Idaho pathways: agriculture, energy, health, trades, public service, and software.

04 · Semester 1 · Weeks 15–18

Human, machine, and responsibility

9–10 (bridge to 11–12) · 4 weeks · Debate, training-data bias, and a fluency capstone

Use the debate as a performance assessment. The same prompt returns in 11–12 at greater depth (AII.IS.4).

05 · Semester 2 · Weeks 1–5

GenAI, ethics, and private lives

11–12 · 5 weeks · Ethics of commonplace GenAI, accessibility, data collection, unauthorized training

Invite a counselor or librarian for the FERPA/COPPA conversation. Do not ask students to upload personal writing into unapproved tools.

06 · Semester 2 · Weeks 6–10

Work, harm, and civic choice

11–12 · 5 weeks · Cybersecurity, output evaluation, careers, data-stage bias, regulation

Idaho guest speakers (Micron, agriculture co-ops, hospitals, county IT, tribal enterprises) make IS.2 concrete. Record a backup video for rural bandwidth days.

07 · Semester 2 · Weeks 11–13

The hard debate, revisited

11–12 · 3 weeks · Consciousness, creativity, ethics, and human responsibility at depth

Require evidence from prior units. Students should cite at least one technical limit and one civic consequence.

08 · CS / Engineering strand · ongoing

Data before models

9–12 CS · 6–8 weeks · Cleaning, validation, acquisition, train/dev/test, bias in examples

Spreadsheet-first. Python notebooks are an extension, not a gate. Public datasets only; no student PII.

09 · CS / Engineering strand · ongoing

Methods, metrics, and safeguards

9–12 CS · 6–8 weeks · Model families, XOR vs. language, prebuilt models, agents, metrics, human-in-the-loop

Teach AIM.9 (metrics) before any demo that quotes “99% accuracy.” Fraud and wildfire examples make class imbalance visceral.

From the standards

Glossary

Agentic AI

AI systems designed to independently plan, execute, and adjust actions to achieve a specific goal with minimal human intervention, often capable of working across multiple tools or applications.

AI Companion

A highly personalized, conversational AI designed to simulate human-like relationships, offering emotional support, companionship, and customized personalities rather than just executing practical tasks.

AI Literacy

Technical knowledge, durable skills, and future-ready attitudes required to thrive in a world influenced by AI. It enables learners to engage, create, manage, and design AI, while critically evaluating its benefits, risks, and ethical implications.

Anthropomorphism

The cognitive tendency to attribute human traits, emotions, intentions, or consciousness to AI systems, which can lead to unrealistic expectations, misplaced trust, or the mistaken belief that an AI platform is capable of genuine social connection or personal experience.

Artificial Intelligence (AI)

A branch of computer science focused on building systems capable of performing tasks that typically require human intelligence. AI leverages massive data sets and computational power to make predictions, increasingly impacting various aspects of our daily lives.

Automation

The use of technology to perform tasks, processes, or workflows with minimal human assistance to increase efficiency, speed, or precision.

Generative AI (Gen AI)

A subset of machine learning and AI specifically designed to create new content, including text, images, audio, code, video, or synthetic data based off a prompt.

Hallucination

Instances where an artificial intelligence system generates information that is incorrect, misleading, or entirely fabricated, but presents it as if it were true.

Human-Centered

An approach where AI is used specifically to support human inquiry. It ensures that humans remain responsible for the initial objective, final decision-making, oversight, and ethical reflection at the beginning and end of every task (Human AI Human).

Human-in-the-loop

A model of interaction where a human is required to participate in a process, such as verifying, approving, or correcting, to ensure the accuracy, safety, and ethical alignment of AI-generated outcomes.

Large Language Model (LLM)

A specific type of Generative AI trained on vast amounts of text data to recognize, predict, and generate human-like text responses.

Machine Learning

A subfield of AI where computer systems are trained to identify patterns in large datasets, allowing them to improve their performance on tasks over time without being explicitly programmed for every step.

Personally Identifiable Information (PII)

Information that can be used to identify a specific person, such as a name, home address, phone number, email address, or student ID number.

Predictive AI

AI models that analyze historical and existing data to make forecasts or estimations about future events, trends, or outcomes.

Simulated Environment

An artificial, controlled setting created to replicate real-world conditions. Examples range from computer games and AI-generated videos, to two humans role-playing a situation like a job interview.

Synthetic Media

Content, such as images, audio, video, or text, that has been created, modified, or generated by AI, often used to simulate reality.

AI Fluency · Appropriate Use

9-12.AIF.AU.1

The Right Tool for the Job

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Understand when AI versus non-AI solutions are appropriate.

Clarification. Appropriateness is context-dependent. The goal is for students to develop the critical thinking skills to evaluate this on a case-by-case basis.

Student-friendly learning targets

  • I can decide whether a task is a good fit for AI, a traditional tool, a person, or a mix.
  • I can explain why appropriateness depends on the goal, the data, and who is accountable.
  • I can recommend a tool for an Idaho workplace or school task and name the risk if the tool is used alone.

Essential questions

  1. When is AI the right tool, and when is it the wrong one?
  2. What does a task's purpose tell us that the tool itself cannot?
  3. Who is still responsible if an AI suggestion is wrong?

Objectives

  1. Apply a three-question test (purpose, trusted data, accountability) to school and workplace tasks.
  2. Sort tasks into AI-appropriate, non-AI, or mixed, and justify each sort in writing.
  3. Contrast at least one Idaho workplace example with one school learning task.
  4. Name a human check that should stay in the loop when AI is used.
  5. Use only district-approved tools, or a paper packet, so no student account is required.

Key vocabulary

Appropriate use
Choosing a tool because it fits the goal, the data, and the people involved—not because the tool is new or popular.
Context
The situation around a task: who it is for, what is at stake, how much time you have, and what counts as a good answer.
Non-AI solution
A way to finish a task without artificial intelligence, such as a calculator, a spreadsheet formula, a sensor, a checklist, or asking an expert.
Human-in-the-loop
A person who checks, approves, or corrects a machine result before it is used.
Automation
Using a machine or program to do a repeated task with little help from a person, usually to save time or reduce errors.
Task fit
How well a tool matches what the task is actually for. A tool can be powerful and still be a poor fit.
Verification
Checking an answer against a trusted source, a measurement, or another person before you act on it.

Teacher background

This lesson trains judgment, not tool use. Ninth and tenth graders already meet AI in homework, social media, and after-school jobs; the work of this period is to slow that meeting down. Appropriateness is context-dependent, which is the exact clarification in the Idaho standard. Treat AI as one option among many: a calculator, a soil probe, a phone call to an agronomist, a spreadsheet, or a human expert. Two pitfalls show up fast. First, students turn “AI versus not-AI” into a morality contest. Keep the frame practical. A frost call for a potato cellar in Bingham County is a different decision than drafting a personal narrative for English. Second, teachers over-demo a chatbot and the class never practices the decision. Script a short projected demo, then move to paper task cards so rural rooms stay in the lesson when Starlink drops. Name Idaho workplaces out loud: Idaho Power load forecasts on the Snake River system, Micron process control in Boise, county 911 dispatch, and infrared wildfire maps from the National Interagency Fire Center. Students should leave able to say, for a given task, what a human, a traditional tool, and an AI system each do well—and what each cannot do.

Materials

  • Whiteboard or chart paper and markers
  • Printed Right Tool task cards (8 school and Idaho workplace tasks) — one set per pair
  • Right Tool Memo half-sheet (one per student)
  • Sticky notes
  • Projector and teacher workstation for an optional district-approved chatbot demo
  • OFFLINE fallback: printed “fake model output” packet with two scripted prompts and canned replies (comfort a classmate; list public Idaho snowpack sources)
  • Timer visible to the class

Before class

  • Print and cut task cards; stack them in envelopes labeled Station A.
  • Print the fake-output packet even if you expect to demo live—Starlink and guest Wi-Fi fail.
  • Write the three-question test on the board before the bell: Purpose? Trusted data? Who is accountable?
  • If using a district-approved tool, test the two scripted prompts on the teacher account only. Do not log students in.
  • Identify one local example (ag, wildfire, hospital, county, trades) students will recognize.

Instructional sequence

Warm-up — Person or machine?

7 min
  1. 1. Draw two columns on the board: “Needs a person” and “A machine could try this.”
  2. 2. Read four tasks aloud: calculating a tip, comforting a friend after a loss, spotting frost risk from a weather table, and writing a college essay about your family.
  3. 3. Students hold up one finger (person) or two (machine) for each task. Tally the split; do not debate yet.
  4. 4. Circle the frost item and the essay item. Tell students both will return, and that “it depends” is an allowed answer once they have a test for it.

Direct instruction — The three-question test

13 min
  1. 1. Write the standard on the board exactly: “Understand when AI versus non-AI solutions are appropriate.”
  2. 2. Teach the three-question test: What is this task for? What data can we trust? Who is accountable if the answer is wrong?
  3. 3. Work one Idaho example live: Idaho Power forecasting evening load on a January cold snap. Historical spreadsheets may be enough; an AI forecast may help; a human dispatcher still calls the play.
  4. 4. Contrast with a school task: a lab conclusion meant to show the student understood the experiment. An AI draft is a poor fit because the goal is the student’s thinking.
  5. 5. Read the clarification aloud: appropriateness is case-by-case, not a forever yes or no. Post it where students can see it during independent work.

Guided practice — Four-card sort

10 min
  1. 1. Pairs receive four printed cards: a potato grading camera on a Magic Valley packing line, a 911 call, a personal narrative, and a county budget spreadsheet.
  2. 2. For each card, pairs mark AI, not-AI, or mixed, and write one reason that uses the three-question test.
  3. 3. Two pairs compare. Any mixed vote must name who stays in the loop (grower, dispatcher, teacher, clerk).
  4. 4. Cold-call two pairs to defend one card. Push for purpose, not “because AI is smart.”

Independent practice — Right Tool Memo

10 min
  1. 1. Each student draws or is assigned one new task: St. Luke’s shift scheduling, a Nez Perce fisheries count, a welding bead inspection, or a history DBQ.
  2. 2. Complete the memo: task goal, best non-AI option, possible AI role, risk if AI is used alone, and a recommendation.
  3. 3. Remind students: no names, photos, grades, or private writing go into any digital tool. Paper memos stay in the room.
  4. 4. Collect memos as the exit ticket, or photograph the board tallies if you need a faster close.

Real-world examples

  • A Bingham County potato cellar uses a soil probe and a frost forecast. AI might help scan a weather table, but a grower still walks the cellar because a wrong call ruins a crop.
  • The National Interagency Fire Center in Boise uses infrared maps and models for wildfire. Crews still look at real wind, fuel, and road access before they move people.
  • Micron in the Treasure Valley uses automated inspection on wafers. A technician still decides whether a flagged lot is scrapped, reworked, or released.

Hands-on activity

Hands-on — Use / don’t use / use with a check

12 min
  1. 1. Station A (always on): students sort eight mixed school and Idaho work tasks onto three desk mats labeled Use, Don’t use, and Use with a human check.
  2. 2. Station B (teacher-projected): on a district-approved tool, the teacher pastes two scripted prompts—one poor fit (comfort a grieving classmate) and one better fit (list three public sources for Idaho snowpack). Students watch; they do not type.
  3. 3. If the network is down, Station B is the printed fake-output packet with the same two prompts and canned replies. The lesson does not pause.
  4. 4. Each student adds one sticky note to a class chart with a one-line reason.
  5. 5. Three volunteers defend one sticky using purpose, data, and accountability. Teacher records a model sentence on the board.

Discussion questions

  1. Which of today’s tasks would you never hand to AI, even if the output looked perfect? Why?
  2. When is “mixed” a stronger answer than a hard yes or no?
  3. How should a rural clinic or a county office decide differently from a large Boise employer?
  4. If a tool is free and fast, why might it still be the wrong tool for schoolwork?

Differentiation

Support

  • Give a filled-in sample memo and a word bank (purpose, data, accountable, mixed).
  • Reduce the independent task to two boxes: best non-AI option and one risk.
  • Allow oral dictation of the memo to a peer scribe or the teacher.

Challenge

  • Require a second Idaho workplace and a different recommendation for each.
  • Ask students to write a one-paragraph policy a shop teacher or coach could post.
  • Compare two tools for the same task and argue which failure is more costly.

Multilingual learners

  • Provide the three-question test and card titles in English and Spanish.
  • Allow the memo reason in the student’s strongest language, with key terms in English.
  • Pair with a bilingual peer for the card sort; the written memo remains individual.

IEP / 504

  • Offer large-print cards and a digital copy of the memo with extra spacing.
  • Allow extra time or a shortened sort (four cards instead of eight) without reducing the three-question test.
  • Permit a graphic organizer instead of paragraph writing; success is the recommendation plus one reason.

Assessment

Formative

  • Warm-up finger votes and the four-card sort reasons during guided practice.
  • Sticky-note placement and the one-line defense in the hands-on close.
  • Teacher circulation notes: every mixed vote names a human check.

Summative

  • Right Tool Memo scored on four traits: purpose named, non-AI option, AI role or refusal, and a named risk.

Success criteria

  • I used the three-question test in my reason, not “AI is cool” or “AI is bad.”
  • I named at least one task that should stay with a person or a traditional tool.
  • I identified who is accountable if the chosen tool is wrong.

Responsible use

Students do not log into public chatbots for this lesson. If a live demo happens, the teacher uses a district-approved tool on a teacher account, with scripted prompts that contain no student names, class lists, or private writing. The default path is paper. Fast is not the same as allowed: a tool that is free on a phone may still be unapproved by the district. When students recommend AI for a task, they must also name a human check. The class rule is simple and posted: we choose tools on purpose, we check the result, and we keep schoolwork that is meant to grow our thinking in our own hands.

Ethics

Appropriateness is not only about accuracy. Using AI to comfort a classmate, to write a college essay in someone else’s voice, or to make a public safety call without a person in the loop treats people as problems to be optimized. Students practice asking who is helped, who is skipped, and who is blamed if the output is wrong. Idaho public schools serve rural towns, Boise-metro suburbs, and tribal communities; a one-size rule would hide those differences. The ethical habit this lesson builds is case-by-case judgment with reasons, not a cheer or a ban.

Privacy

FERPA still applies when the tool is “just a demo.” Never put student names, photos, grades, ID numbers, or private writing into an unapproved tool. Do not project a student’s memo, email, or face. Printed task cards use fictional or public workplace details (Idaho Power, NIFC, a generic packing line), not real patient, student, or employee records. If a student volunteers a family farm story, keep it in the room; do not type it into a prompt. District-approved tools only, and paper whenever that is the safer path.

Reflection

  1. Which task today changed your mind, and which question in the three-question test caused the change?
  2. Where in your own schoolwork is AI a mixed tool rather than a yes or a no?
  3. What will you check by hand this week even if a machine offers an answer?

Homework

Take-home half-sheet (20–25 minutes, no account). Pick one real task you will face this week (homework, a shift, a chore, a sport). Complete the three-question test on paper. List a non-AI option, a possible AI option, and your recommendation in five to eight sentences. Do not use a chatbot. Bring the sheet back; we will swap and peer-check the reasons.

Closing

AI is a tool with a job description, not a default setting. If you can name the purpose, the data, and the person who is accountable, you can choose AI, skip it, or mix it—and you can explain that choice to a boss, a teacher, or a grower. That judgment is the standard, and it travels from this classroom to Idaho work.

Extensions

  • Block period: add a structured debate (AI vs. non-AI vs. mixed) using one wildfire card and one English-class card; require evidence from the three-question test.
  • Invite a local grower, millwright, or county clerk for a 10-minute “what I still check by hand” interview; record a backup audio file for rural bandwidth days.
  • Students rewrite one school honor-code line so it names appropriate vs. inappropriate AI use without banning all tools.

Cross-curricular links

ELA
Purpose and audience decide the tool, the same way they decide a genre. A personal narrative is evidence of the writer, not a product to outsource.
Mathematics
A calculator is a non-AI tool with a clear job. Contrast it with an AI that might invent a number. Students practice asking whether a result is computed or guessed.
Science
Lab conclusions must show the student’s claim, evidence, and reasoning. AI can format a table; it cannot stand in for the observation.
CTE / Social studies
Ag, energy, health, trades, and county government all mix sensors, spreadsheets, and human calls. Civics: who is liable when a public agency uses a model.

Back to contents

AI Fluency · Appropriate Use

9-12.AIF.AU.2

What We Lose When We Hand It Over

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Recognize that some AI can handle cognitive tasks, but reliance on AI might diminish individual human cognitive and emotional development.

Example from the standards. A student can use an AI tool to generate a report or do other schoolwork that is designed for student cognitive development. Moreover, some people use "AI Companions" for emotional support, which may affect recognition of human emotion in negative ways.

Student-friendly learning targets

  • I can name a cognitive skill a school task is meant to build and explain how skipping it with AI would change me.
  • I can tell the difference between helpful offloading (like a calculator) and offloading that removes the point of the work.
  • I can describe a risk of using AI companions for emotional support without shaming anyone’s feelings.

Essential questions

  1. If a machine can do the task, what human skill might stop growing?
  2. When is offloading a task smart, and when does it steal the practice the task was for?
  3. What do we need from other people that a companion chatbot cannot actually give?

Objectives

  1. Identify the target skill in common school tasks (argument, memory, estimation, empathy, revision).
  2. Compare helpful cognitive offloading with offloading that weakens development.
  3. Analyze a scenario about AI companions using the language of the standard, not personal confession.
  4. Write a personal-use rule that keeps the student in charge of thinking and feeling.
  5. Practice the skill by hand before looking at a printed AI version of the same work.

Key vocabulary

Cognitive task
Work that uses thinking skills such as remembering, explaining, planning, judging, or solving a problem.
Cognitive offloading
Letting a tool hold some of the thinking (a calculator, a list, a map) so your mind can focus on another part of the job.
Reliance
Depending on a tool so often that it becomes hard to do the task without it.
AI companion
A chatbot built to act like a friend or counselor, offering conversation and comfort rather than just answers to practical questions.
Anthropomorphism
Treating a machine as if it had human feelings, intentions, or a real relationship with you.
Emotional development
The ongoing work of noticing feelings, reading other people, and practicing care in real relationships.
Skill atrophy
A skill getting weaker because it is not practiced, the way a muscle weakens without use.
Human-centered
Using a tool to support a person’s own thinking and choices, with the person setting the goal and making the final call.

Teacher background

The standard asks students to notice a trade, not to ban tools. AI can draft a lab report, outline a history essay, or chat like a friend. The learning those tasks were designed to grow—argument, memory, empathy—does not automatically transfer if the machine does the work. Cognitive offloading is real and not always bad; calculators offload arithmetic so students can think about rates. The line is whether the offload removes the skill the assignment exists to build. Handle AI companions with care. Some students already use chatbots for late-night reassurance. Do not shame; do not diagnose. Name the risk the standard names: practice with a simulated companion can dull recognition of human emotion. Point them toward counselors, trusted adults, and Idaho’s 988 line if distress appears, then return to the academic claim. Pitfalls: treating this as an anti-AI sermon, or letting the discussion become a confession circle. Use scenarios, not personal disclosures. Pair every generation example with a “what muscle did we skip?” check. Rural and Boise-metro students meet this differently—one may have unlimited home access, another a shared phone—so keep all practice paper-first with an optional district-approved demo.

Materials

  • Printed “muscle map” of school tasks and target skills (one per student)
  • Two short writing prompts on paper; a printed AI-generated sample response for prompt 2 only
  • Scenario cards: homework report, welding math, hospital triage chat, AI companion at midnight
  • Whiteboard T-chart: Helpful offload / Offload that costs a skill
  • Projector for an optional teacher-only demo of a district-approved tool summarizing a public text
  • OFFLINE fallback: the printed AI sample and scenario cards replace any live generation
  • Counselor contact card and 988 posted as a quiet resource, not as the lesson topic

Before class

  • Write a 80–100 word “AI” report on a public Idaho topic (potato harvest timing or NIFC’s role) yourself or from a prior district-approved session; print it. Do not generate it live with student-facing accounts.
  • Remove any student names from scenario cards. Use fictional first names only, or roles (Student A).
  • Alert the counselor that AI companions may come up; agree on a quiet pass-to-counselor move.
  • Post the sentence stem: “The assignment was designed to build ____. If I hand it over, I skip ____.”

Instructional sequence

Warm-up — What muscle is this for?

8 min
  1. 1. Students list three things they did with their brains yesterday (a text, a shift, homework, a game, a conversation).
  2. 2. Next to each, they name the “muscle”: memory, planning, empathy, estimation, persuasion, or patience.
  3. 3. Ask: “If a tool had done that for you, which muscle would have sat on the bench?” Two volunteers share a non-personal example.
  4. 4. Introduce offloading with a calculator: we offload arithmetic to think about rates. Not all offloading is a loss.

Direct instruction — The trade we make

12 min
  1. 1. Display the standard exactly. Underline “might diminish individual human cognitive and emotional development.”
  2. 2. Teach the fork: helpful offload vs. offload that removes the reason for the task. Calculator for a unit-rate problem vs. AI writing the lab conclusion.
  3. 3. Read the standards example aloud: generating a report designed for student development, and AI companions for emotional support.
  4. 4. Define AI companion and anthropomorphism in plain language. Stress that a chatbot can sound caring and still have no feelings and no duty of care.
  5. 5. Set the discussion rule: we use scenarios, not personal stories about friends, family, or dating. Anyone who wants a private conversation can see a counselor.

Guided practice — Helpful or costly?

10 min
  1. 1. Pairs sort six cards onto the T-chart: spell-check, AI-written history report, GPS in an unfamiliar city, AI companion after a fight with a friend, auto-complete on a welding-math worksheet, a shared grocery list.
  2. 2. For two cards, pairs complete the stem: “The assignment was designed to build ____. If I hand it over, I skip ____.”
  3. 3. Spot-check: GPS in a new city can be helpful; GPS instead of learning a town you live in may cost a skill. Both answers can be defended.
  4. 4. Brief share-out of one costly example and one helpful example. Teacher records sentence stems, not student names.

Independent practice — Do it, then read the machine

10 min
  1. 1. Students hand-write a six-sentence explanation of why frost matters in a potato cellar (or a local equivalent). Three minutes. Pens only.
  2. 2. They trade with a partner and underline one clear idea and one thin idea. This is the muscle: explaining and judging.
  3. 3. They then read the printed “AI report” on the same topic and mark three places the machine is fluent but empty, wrong, or missing local sense.
  4. 4. Exit line on the half-sheet: “If I had started with the AI page, I would have skipped ____.”

Real-world examples

  • A student uses a chatbot to generate a lab report for biology at a Boise-metro high school. The prose looks finished; the student cannot explain the data when the teacher asks a follow-up, because the thinking never happened.
  • A hospital unit in the Treasure Valley may use AI to draft shift notes. Nurses still walk the floor and read faces; handing comfort and judgment to a companion app would cost the skill patients need.
  • Outfitters and river guides in central Idaho read weather, water, and client fear in real time. A chatbot itinerary can list rapids; it cannot replace the judgment built by years of cold water and other people’s panic.

Hands-on activity

Hands-on — Scenario jury

12 min
  1. 1. Groups of three draw one scenario card (homework report, AI companion at midnight, auto-complete on trade math, chatbot “friend” during lunch isolation).
  2. 2. The group completes a four-box sheet: skill the task was meant to build; what AI handles; what a person might stop practicing; a safer use or a refusal.
  3. 3. Groups rotate one person to the next table to report the safer-use line only (keeps time and avoids oversharing).
  4. 4. Optional 90-second teacher demo: district-approved tool summarizes a public NIFC paragraph. Class names the muscle that would weaken if this replaced reading.
  5. 5. If the network is down, skip the demo; the printed AI report already did that job. Close by writing a one-sentence personal-use rule on the half-sheet.

Discussion questions

  1. Where is offloading a sign of skill (a carpenter using a jig) rather than a loss?
  2. Why might a companion that always agrees be worse for emotional development than a friend who disagrees?
  3. What should a school assignment still require you to do yourself, even if AI could draft it?
  4. How do we talk about this without mocking people who are lonely?

Differentiation

Support

  • Provide the sentence stem and a list of skill words (memory, explanation, empathy, estimation).
  • Allow the six-sentence frost paragraph to be four sentences or a labeled diagram plus two sentences.
  • Read scenario cards aloud and check for understanding before the jury starts.

Challenge

  • Write a counter-argument: a case where AI use increased a human skill (for example, using feedback to revise).
  • Design a classroom policy that permits some AI and still protects the target skill, with one assessment change.
  • Compare calculator use in Algebra 1 with chatbot use in English 9 using the same offloading test.

Multilingual learners

  • Students may draft the frost explanation in their strongest language, then label the skill words in English.
  • Provide scenario cards with simplified English and icons (report, phone, hard hat, two people talking).
  • Allow the personal-use rule as a bilingual sentence; key terms (offload, companion, skill) stay in English.

IEP / 504

  • Offer a quiet corner for the hand-writing burst; do not require reading the AI sample aloud.
  • Replace the six-sentence write with a checklist of claims plus two original sentences if writing volume is an IEP accommodation.
  • Keep companion scenarios at the role level; do not probe personal mental health. Offer a counselor pass without explanation.

Assessment

Formative

  • T-chart sort accuracy and the completed sentence stem during guided practice.
  • Annotations on the printed AI report (three marks with a reason).
  • Group four-box sheet during the scenario jury.

Summative

  • Half-sheet with the skipped-muscle line and a one-sentence personal-use rule, scored for naming a skill and a limit.
  • Optional block-period paragraph: explain the standards example in your own words with one school task and one companion risk.

Success criteria

  • I named a specific thinking or feeling skill, not just “learning.”
  • I explained how relying on AI could weaken that skill.
  • I stated a use rule that keeps me in charge of my own work and relationships.

Responsible use

This lesson uses paper first. Students do not create companion-app accounts, and they do not paste their frost paragraphs into a chatbot. If a teacher demo runs, it uses a district-approved tool, a public text, and a teacher account. The academic integrity rule is stated without theater: if the assignment exists to grow your thinking, submitting machine text as your thinking is both a skill loss and a honesty problem. Students write a use rule they can actually keep on a shared phone or a home computer.

Ethics

The ethical core is development, not purity. It is unfair to tell students that every shortcut is cheating, and it is unfair to pretend that a fluent paragraph is the same as a mind at work. Companion systems raise a second duty: they can encourage people to practice intimacy with a system that cannot care and cannot keep a professional confidence. Class talk stays on the design of the tool and the skill at risk. Students are not asked to disclose loneliness, dating, or family conflict. Respect includes offering a private path to a counselor and keeping the academic claim in the foreground.

Privacy

FERPA and basic care meet here. Do not collect personal writing about mental health, family, or relationships as class artifacts. Scenario cards use roles, not real students. Never enter a student’s paragraph, name, photo, or grade into an unapproved tool. If a student reveals distress, stop the academic probe, follow school protocol, and do not type the disclosure into any AI system. District-approved tools only. Printed packets let rural classrooms run the full lesson without accounts or home broadband.

Reflection

  1. Which muscle do you most often skip when a tool is handy, and what is one week of practice worth?
  2. How will you tell helpful offloading from a shortcut that steals the assignment?
  3. Who in your life is a real check on your thinking or your mood, and why can’t a chatbot replace that?

Homework

Paper log (20–30 minutes, no account). For two homework tasks tonight, write: the assigned task, the skill it is meant to build, whether you used any digital help, and one sentence on what you still did yourself. If you used no AI, say so. Do not sign up for any new app. Optional: ask a trusted adult what skill they still refuse to hand to a tool at work, and jot three notes.

Closing

Some AI can do cognitive work. That is not the same as you becoming more skilled. If the task exists to grow your thinking or your ability to read other people, handing it over has a cost. Name the muscle, keep the practice, and use tools in ways that leave you more capable, not just more finished.

Extensions

  • Block period: students design a “muscle label” for an upcoming English or science assignment (what must be human; what tool use is fair) and post it.
  • Compare a shop class (you still have to weld the bead) with an academic class; invite a CTE teacher for five minutes.
  • Media literacy add-on: collect three ads for companion apps (printed at home or provided by the teacher) and mark anthropomorphic language.

Cross-curricular links

ELA
Revision, voice, and argument grow by doing. A generated report can hide missing thought the way a ghostwritten essay would.
Mathematics
Calculators are a legal offload in many tasks; number sense still has to be practiced. Students name which standard of mathematical practice they would lose.
Science
Claim-evidence-reasoning is a cognitive workout. Using AI to write the reasoning box skips the scientific habit the lab is for.
Health / CTE
Trades and caregiving jobs require reading people under stress. Companion apps that skip that practice are a workplace risk, not only a school issue.

Back to contents

AI Fluency · Appropriate Use

9-12.AIF.AU.3

Real Ground, Simulated Sky

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Explain the difference between physical and simulated environments.

Student-friendly learning targets

  • I can explain how a physical environment and a simulated environment are different.
  • I can give an Idaho example of each and say what a simulation leaves out.
  • I can decide when a simulation is useful for training and when only the real world will do.

Essential questions

  1. What makes an environment physical rather than simulated?
  2. What can a simulation teach, and what can it hide?
  3. How should we treat generated video, games, and digital twins when real people and land are at stake?

Objectives

  1. Define physical environment and simulated environment in student language.
  2. Sort artifacts (soil, maps, screenshots, generated images) into physical, simulated, or mixed.
  3. Name at least one benefit and one limit of simulation in fire, agriculture, or trades training.
  4. Ask two grounding questions: What sensors are reading the real world? Who is liable if the model is wrong?
  5. Distinguish a useful training sim from synthetic media presented as evidence.

Key vocabulary

Physical environment
The real world of mass, weather, time, and consequences—places you can touch, get hurt in, or be legally responsible for.
Simulated environment
A controlled replica of real conditions, such as a training game, a digital twin of a factory, a flight sim, or two people role-playing a job interview.
Digital twin
A computer model of a real object or system (a packing line, a dam, a warehouse) that updates to mirror it, at least in part.
Synthetic media
Images, audio, video, or text made or altered by AI so they look real even when the scene never happened.
Sensor
A device that measures something in the physical world, such as temperature, smoke, GPS location, or camera light.
Ground truth
What is actually happening, checked by measurement, observation, or a trusted record—not just what a model displays.
Model
A simplified picture of a system used to explain, predict, or practice. All models leave something out.
Consequence
What happens next in the real world: burned timber, a ruined crop, an injury, a fine, or a saved life.

Teacher background

Students confuse screens with reality, especially after games, flight sims, and generated video. This lesson is a sorting lesson: what has mass, weather, and legal consequence, and what is a controlled replica. Idaho makes the distinction concrete. A wildfire on the Payette National Forest burns timber, closes highways, and fills Boise with smoke. A wildfire simulation at NIFC or in a training game can teach tactics without those costs—and can also hide wind shifts the model never saw. A potato packing line in the Magic Valley is a physical environment; a digital twin of that line is simulated. Pitfall one: treating “simulated” as “fake and therefore useless.” Simulations save lives in aviation, surgery, and fire. Pitfall two: treating generated video as evidence. Students should leave able to ask: What sensors, if any, are reading the real world right now? Who is liable if the model is wrong? Keep the activity tactile. Paper maps, a cup of soil, and a printed screenshot beat a lagging video. When bandwidth fails, the lesson should still run. Connect to science (models vs. observations), CTE (shop vs. simulators), and civics (emergency orders apply on real ground).

Materials

  • Cup of soil or a potato, a printed topographic map, and a printed weather table (physical / measured)
  • Printed screenshots: a fire-training sim, a generated “photo” of a Sawtooth trail, a packing-line digital twin schematic
  • T-chart posters: Physical / Simulated / Mixed
  • Two grounding-question cards per pair
  • Optional: short teacher-projected clip of a public fire-weather briefing (mute ads); not required
  • OFFLINE fallback: all artifacts printed; no video required. Whiteboard drawing of a sim vs. a hillside.

Before class

  • Gather one tactile object students may handle (soil, rock, potato, welding coupon, or a wet sponge standing in for river water).
  • Print six artifact cards with captions that do not claim generated images are photographs.
  • Write the two grounding questions on the board before the bell.
  • If you show video, download it. Do not stream on rural days.

Instructional sequence

Warm-up — Can it burn you?

6 min
  1. 1. Hold up the tactile object. Ask: “Can this scorch, spoil, or get you wet?” Pass it to two students.
  2. 2. Hold up a printed screenshot of a fire or a mountain trail. Ask the same question.
  3. 3. Students write one sentence: Physical means ____. Simulated means ____.
  4. 4. Collect two sentences on the board without names. Preview that useful training can still be “only a sim.”

Direct instruction — Mass, weather, liability

14 min
  1. 1. Write the standard exactly: “Explain the difference between physical and simulated environments.”
  2. 2. Build a three-part definition of physical: mass and energy, weather and time you cannot pause, legal and bodily consequence.
  3. 3. Define simulated: a controlled replica used to practice, predict, or entertain. Include role-play as a low-tech sim.
  4. 4. Idaho pair: Payette wildfire (physical) vs. a training sim or NIFC planning model (simulated). Name what the sim leaves out (a wind shift, a closed forest road, smoke in a school).
  5. 5. Teach synthetic media as a special case: it can look like evidence of the physical world without any sensor ever visiting the place. Generated “photos” are not ground truth.

Guided practice — Six-artifact sort

10 min
  1. 1. Pairs sort six artifacts onto Physical, Simulated, or Mixed: soil sample, topo map from a survey, fire-sim screenshot, generated trail image, packing-line photo captioned as a real plant, digital-twin schematic.
  2. 2. For two artifacts, pairs answer the grounding questions: What sensors, if any, read the real world? Who is liable if this is wrong?
  3. 3. Disagree in public: a topo map is a model of physical ground (mixed). A generated trail image with no camera is simulated media.
  4. 4. Teacher confirms that “mixed” is often the grown-up answer when a real sensor feeds a sim.

Independent practice — Explain it in eight sentences

10 min
  1. 1. Students write a short explanation: define both environments, give one Idaho physical example, one simulated example, and one thing the sim leaves out.
  2. 2. They add a closing line: when they would trust a sim for training, and when they would demand ground truth.
  3. 3. No AI drafting. Paper or a local doc with no generator enabled.
  4. 4. Peer check: partner highlights the “leaves out” sentence. If it is missing, the writer adds it before turning in.

Real-world examples

  • Wildfire on the Payette or Boise National Forest is physical: timber, highway closures, and smoke in the Treasure Valley. A fire-behavior sim at NIFC can train tactics and still miss a local wind shift.
  • A Magic Valley potato packing line is a physical environment with belts, blades, and wage-hour rules. A digital twin can test a layout change without stopping the line—and can hide a jam the sensors never tagged.
  • Ski patrol and avalanche courses in the Wood River Valley use tabletop and digital sims, then move to real snow. The certificate is not complete until the physical environment is in the lesson.

Hands-on activity

Hands-on — Sim vs. hillside lab

12 min
  1. 1. Station 1: students sketch a hillside from the tactile object plus the printed map (physical clues only) and list three things a person on that hill would feel.
  2. 2. Station 2: students annotate the fire-sim screenshot and the generated trail image. They mark “sensor-backed,” “invented,” or “not sure.”
  3. 3. Station 3 (paper always): they write a one-paragraph briefing to a county commissioner: what the sim is good for this week, and what a crew still has to check on the ground.
  4. 4. Optional digital path: teacher projects a downloaded public fire-weather map. Students still complete the paper briefing.
  5. 5. If bandwidth fails, Station 2 uses only prints. Gallery-walk three briefings. Star the sentence that names liability.

Discussion questions

  1. Why might a simulation be the ethical choice for training (fire, surgery, driving) even though it is not the real thing?
  2. How should a news feed treat a generated video of a wildfire or a flood?
  3. What is the difference between a digital twin fed by sensors and a picture an image model invented?
  4. When should a coach, a shop teacher, or a county emergency manager refuse to train only in a sim?

Differentiation

Support

  • Give a two-column notes sheet with sentence starters for physical vs. simulated.
  • Allow a labeled diagram plus four sentences instead of eight.
  • Pre-sort one artifact as a model (the potato is physical) before independent work.

Challenge

  • Argue whether a drone feed is physical, simulated, or mixed, using sensors and latency.
  • Research (printed excerpt) how NIFC or Idaho Power uses models, and list two limits the agency itself names.
  • Write a warning label that a generated landscape image would need before a tourism office could post it.

Multilingual learners

  • Post cognates and plain definitions: physical / físico, simulated / simulado, sensor, consequence / consecuencia.
  • Allow the briefing paragraph in the student’s strongest language with the two grounding questions answered in English.
  • Use labeled photos on every card so text load is not the gate.

IEP / 504

  • Provide a quiet station and larger prints; avoid flashing video.
  • Accept a checklist-plus-oral explanation as the independent product if writing volume is accommodated.
  • Keep tactile options optional for students with sensory aversions; a photo of the object is an allowed substitute.

Assessment

Formative

  • Warm-up sentences and the six-artifact sort with grounding questions.
  • Annotations marking sensor-backed vs. invented on Station 2.
  • Peer highlight of the “leaves out” sentence.

Summative

  • Eight-sentence explanation scored for both definitions, one Idaho example of each, and a named limit of the sim.

Success criteria

  • I defined physical and simulated environments in my own words.
  • I used at least one Idaho example and named something a simulation leaves out.
  • I asked who is liable, or what sensor would be needed, before trusting a screen.

Responsible use

Students do not generate images of real classmates, staff, or school hallways. If a teacher shows synthetic media, it is labeled as generated on the print itself. No student accounts. Downloaded public maps and printed screenshots are the working set so a rural classroom is not held hostage by a video platform. The responsible move with any realistic image is to ask whether a sensor visited the place. If the answer is no, it is not evidence.

Ethics

Simulations can reduce harm: firefighters, nurses, and drivers should not learn only by burning, injuring, or crashing. The ethical failure is the opposite move—treating a sim or a generated video as if people, land, and liability were already settled. Posting a fake wildfire clip, or training staff only on a tidy digital twin, can put bodies on real roads. Students practice a duty to label replicas and to keep a human observer between the model and a public decision.

Privacy

Do not photograph students for “before/after” sim activities. Do not upload class photos to an image generator. FERPA bars putting student faces, names, or locations into unapproved tools. Use public landscapes (Sawtooths, a generic packing line, NIFC public maps) rather than a student’s house, ranch, or reservation unless a family has clearly offered that story in the room and it stays on paper. District-approved tools only; paper is the planned path.

Reflection

  1. Where did you catch yourself treating a picture as a place?
  2. What would you want a wildfire crew or a packing-line supervisor to check on the ground after looking at a model?
  3. How will you label generated images when you see them in a feed this week?

Homework

Take-home sort (20–25 minutes, no account). Cut or list five things you see tonight (a room, a game, a weather app, a photo, a tool). Mark each P, S, or M. Write six to ten sentences explaining one mixed item: what is physical, what is simulated, and what a person should still check. Do not use an image generator. Bring the list; we will spot-check two items.

Closing

Physical environments have mass, weather, and consequences. Simulated environments are controlled replicas that can teach, predict, or deceive. If you can name what a sim leaves out—and who is liable on real ground—you are already doing the work this standard asks for.

Extensions

  • Block period: build a tabletop sim (paper “fire cells” and dice for wind) then walk outside or to a window and list five physical variables the dice cannot capture.
  • CTE partnership: visit the welding booth or greenhouse; list what a VR welder or a growth-chamber model would miss.
  • Civics: read a short public evacuation order and mark every clause that only makes sense in the physical world.

Cross-curricular links

Science
Models vs. observations. A climate or fire model is a sim; a thermometer reading is physical. Students practice naming assumptions.
Mathematics
Coordinate grids and topographic lines are models of physical space. Scale and rounding are already “something left out.”
ELA
Setting in fiction is a simulated world made of words. Students compare a story’s forest with a real forest they could be legally lost in.
CTE / Social studies
Shop, ag, and emergency management train in sims and certify on real ground. Public orders, wages, and injuries attach to the physical environment.

Back to contents

AI Fluency · Appropriate Use

9-12.AIF.AU.4

Not All Models Speak

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Understand that Large Language Models (LLM) are just one type of AI model and that others exist with different purposes.

Example from the standards. LLMs are trained on natural language text and generate text, whereas diffusion models are used for image generation, decision tree models can classify, linear regression models can predict numeric values, etc.

Student-friendly learning targets

  • I can explain that an LLM is only one kind of AI model and that other kinds have other jobs.
  • I can match a sample output to a model family: language, image, classification, or numeric prediction.
  • I can name a task each family should not be asked to do.

Essential questions

  1. If a chatbot is only one kind of AI, what are the others for?
  2. How should the type of output (text, image, category, number) guide which model we trust?
  3. Why is “just ask the AI” a weak plan when models are built for different purposes?

Objectives

  1. Define LLM, diffusion model, decision tree, and linear regression at a grade 9–10 level.
  2. Match mystery outputs to model families using purpose, not brand names.
  3. Give an Idaho example for at least two families (yield numbers, wafer classification, trail image, permit letter).
  4. State one misuse for each family (for example, using an LLM as a calculator of record).
  5. Read a tiny linear pattern and a two-split tree on paper so the math is visible, not magical.

Key vocabulary

Large Language Model (LLM)
A model trained on huge amounts of text so it can predict and generate language. It is one type of AI, not all of AI.
Diffusion model
A model used to generate images (and sometimes audio or video) from patterns it learned, often from a text prompt.
Decision tree
A model that classifies by asking a sequence of yes/no or threshold questions, like a flowchart.
Linear regression
A model that fits a line (or a simple trend) to data in order to predict a number, such as yield or temperature.
Classification
Assigning an item to a category (in spec / out of spec, frost risk / no frost) rather than writing a paragraph.
Prediction
A model’s estimate of a future or unknown value, based on patterns in past data—not a guarantee.
Training data
The examples a model is shown during building. Different families need different kinds of examples (text, images, labeled rows, numbers).
Model family
A group of models that share a purpose and a kind of output, the way trucks, boats, and planes are all vehicles with different jobs.

Teacher background

Chatbots dominate the news, so students assume AI means “the thing that talks.” The standard requires a wider map: language models generate text; diffusion models generate images; decision trees classify; linear regression predicts a number. Ninth graders can hold those four families if each one is tied to a job they recognize. Use Idaho numbers, not abstract ones. Linear regression can estimate potato yield from soil moisture. A decision tree can flag whether a Micron wafer lot is in spec. A diffusion model can invent a “photo” of a Sawtooth trail that does not exist. An LLM can draft a county permit letter that sounds official and is wrong. Pitfalls: drowning the period in architecture diagrams, or implying one family is “smarter.” Purpose, not prestige, is the sorting rule. Keep math honest and light—show a three-point line and a simple tree on the board. Project a district-approved demo only after students have matched printed “mystery outputs” to model types on paper. That packet is the lesson when the network dies. Students should leave able to name the model family, the kind of output, and a task it should not be asked to do.

Materials

  • Four family posters: LLM (text), diffusion (image), decision tree (category), linear regression (number)
  • Mystery-output packet: six printed outputs with no labels (letter, fake trail photo, yield table, wafer pass/fail tree, chatbot poem, frost-risk flowchart)
  • Board-ready three-point data set (soil moisture vs. yield) and a two-split tree (temp / moisture → frost risk)
  • Matching half-sheet (one per student)
  • Optional teacher demo on a district-approved tool: one text prompt and one image prompt, teacher account only
  • OFFLINE fallback: the mystery-output packet and board math replace all live tools

Before class

  • Print mystery outputs. Caption the generated image as “generated, not a photograph.”
  • Practice the three-point line so you can plot it in under a minute.
  • If demoing, script two prompts that use public facts only (no student work).
  • Decide a local number students know (cwt per acre, river cfs, or a shop measurement) to stand in if potato yield feels distant.

Instructional sequence

Warm-up — Four outputs, no brands

7 min
  1. 1. Reveal four unlabeled products: a paragraph, a picture, a pass/fail tag, and a predicted number.
  2. 2. Students silently write which one “looks like AI” to them and why. Most will pick the paragraph or the picture.
  3. 3. Tell them all four can be AI, and that today’s job is purpose, not brand logos.
  4. 4. Introduce the sentence we will reuse: “This model is for ____, so I would not ask it to ____.”

Direct instruction — Four families, four jobs

13 min
  1. 1. Write the standard and the standards example on the board. Read them exactly.
  2. 2. Map four families: LLM → text; diffusion → images; decision tree → classification; linear regression → numeric prediction.
  3. 3. Plot three points (moisture vs. yield) and draw a rough line. Predict a fourth yield. Say the word “estimate.”
  4. 4. Draw a two-split tree: temperature below 32? moisture high? → frost-risk class. Say the word “classify.”
  5. 5. Misuse examples: an LLM is a poor calculator of record; a diffusion model is a poor witness; a regression line is a poor poem; a tree is a poor substitute for a full diagnosis at St. Luke’s.

Guided practice — Match with a purpose sentence

10 min
  1. 1. Pairs open the mystery-output packet and place each of the first four items on a family poster.
  2. 2. For each, they write: “This model is for ____, so I would not ask it to ____.”
  3. 3. Teacher circulates for two common errors: calling every paragraph an LLM (could be a person) and calling every picture a photograph.
  4. 4. Confirm as a class. Leave two mystery items unsolved for independent work.

Independent practice — Two remaining mysteries plus a misuse

10 min
  1. 1. Each student matches the last two packet items and writes the purpose sentence for both.
  2. 2. They choose one Idaho workplace (potato yield, Micron lot, county letter, trail tourism image) and name the best family and a family they would refuse.
  3. 3. Exit box: “An LLM is only one type of AI because ____.”
  4. 4. No student accounts. If a neighbor is stuck, they may borrow a family poster, not a chatbot.

Real-world examples

  • Linear regression on soil moisture and historical yield can estimate cwt per acre for a Magic Valley grower. It will not write the crop-insurance narrative.
  • A decision tree can classify Micron wafer lots as in spec or out of spec. It should not generate a press photo of the clean room.
  • An LLM might draft a county permit letter that sounds official. A diffusion model might invent a Sawtooth “photograph” for a tourism page. Neither is a substitute for a surveyor or a camera on the trail.

Hands-on activity

Hands-on — Mystery desk and optional demo

12 min
  1. 1. Paper core: teams of three play “wrong tool.” The teacher names a job (predict tonight’s low in Arco; generate a poster; classify smoke plumes as hold or go; write a parent email). Teams hold up the family card they would refuse and say why.
  2. 2. Teams then hold up the family they would consider, with a human check named.
  3. 3. Optional digital: teacher runs one text prompt and one image prompt on a district-approved tool. Class labels the family before the result appears.
  4. 4. If the network is down, skip step 3. Use two extra printed outputs in the packet.
  5. 5. Close by reciting the standards example in chunks; students supply the family names in unison.

Discussion questions

  1. Why do news stories talk as if “AI” were one product?
  2. Which family is easiest to over-trust because the output looks human?
  3. When would a simple tree or a line on paper beat a huge language model?
  4. What should a county website or a hospital dashboard label so the public knows which family produced the result?

Differentiation

Support

  • Give a four-row cheat sheet: family, output type, Idaho example, common misuse.
  • Allow matching with sticky notes onto posters instead of written purpose sentences; then scribe one sentence together.
  • Color-code packets (blue text, green image, yellow category, orange number).

Challenge

  • Add a fifth family in a short research note (clustering, recommendation, or object detection) using a printed excerpt.
  • Explain why an LLM can emit a number that is not a regression prediction.
  • Design a one-page “model menu” a potato shed or a county clerk could actually post.

Multilingual learners

  • Keep family names in English; allow the purpose clause in the student’s strongest language.
  • Use icons on every poster (speech bubble, picture frame, flowchart, line graph).
  • Pre-teach output, classify, predict, and generate with gestures and examples.

IEP / 504

  • Reduce independent mysteries from two to one plus the exit box.
  • Provide a large-print packet and allow oral matching with a teacher or paraeducator.
  • Skip live demos if screen motion is a trigger; paper outputs are the full lesson.

Assessment

Formative

  • Warm-up “what looks like AI” notes and the first four matches during guided practice.
  • Wrong-tool card holds during hands-on (refusal plus a reason).
  • Exit box: “An LLM is only one type of AI because ____.”

Summative

  • Matching half-sheet plus one Idaho workplace item naming a best family, a refused family, and a human check.

Success criteria

  • I named at least three model families and the kind of output each is for.
  • I matched mystery outputs using purpose, not company names.
  • I stated a misuse for at least one family.

Responsible use

Students do not need and should not open image generators or public chatbots for this lesson. Mystery outputs are printed and labeled when synthetic. A teacher demo, if used, runs on a district-approved account with public prompts only. The responsible habit is to ask “what family is this, and what is it for?” before pasting a question into a box. Using an LLM as a silent calculator, or a generated image as a record of a place, is a purpose error, not a clever shortcut.

Ethics

Different families create different harms. A wrong yield number can idle a crew. A wrong classification can scrap a good wafer or release a bad one. A generated image can move tourism money or spread a fake disaster. Fluent text can sound like a county order. Ethics here is matching power to purpose and refusing to hide the family behind the word “AI.” Students also note that training data differ: text scraped from the web is not the same as a grower’s moisture logs, and neither should be treated as a toy.

Privacy

Do not type student essays, grades, photos, or names into any model, including a “harmless” image generator that could memorize a face. FERPA does not pause for a demo. Packets use public or fictional workplace data (generic yield numbers, a fictional lot ID, a public landscape). District-approved tools only. If students later try a tool at home, they should still withhold PII; this lesson models that withholding by never asking for it.

Reflection

  1. Which family do you over-trust because it looks finished?
  2. Where in an Idaho job you know would a simple tree or a line be more honest than a chatbot?
  3. What will you ask the next time someone says “the AI said”?

Homework

Family hunt (20–30 minutes, no new account). From a newspaper, a printed ad, a game, or a parent’s workplace story, find two systems that might use AI or data models. On paper, guess the family (text, image, class, number) and write five sentences each: purpose, possible training data, and one misuse. If you cannot tell, write what evidence you would need. Do not sign up for a tool to complete this.

Closing

Large language models speak in text. They are one family, not the whole field. If you can match a job to a family—and refuse the families that do not belong—you will not be stuck asking a chatbot to do a sensor’s work, a tree’s work, or a camera’s work.

Extensions

  • Block period: students build a paper decision tree for a local yes/no (game on or off for smoke; irrigation on or off) and contrast it with a three-sentence LLM-style blurb about the same decision.
  • Math extension: calculate a slope from the three yield points and discuss why extra points could change the line.
  • Art/CTE: label a generated image with a required caption (“not a photograph”) as if it were going on an Idaho tourism site.

Cross-curricular links

Mathematics
Linear models and flowcharts are already in Algebra and logic units. This lesson names them as AI families with limits.
Science
Classification vs. quantitative prediction mirrors taxonomy vs. measurement. Students practice not mixing those jobs.
ELA
LLMs produce fluent text. Fluency is not evidence. Students compare a generated permit letter with a primary source.
CTE
Ag yield numbers, semiconductor inspection, and trades diagnostics use different model families. Brand chatbots are not the shop standard.

Back to contents

AI Fluency · College and Career Readiness

9-12.AIF.CC.1

Translate the Machine

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Interpret AI output and be able to communicate those to a diverse audience.

Example from the standards. Students are tasked with generating AI outputs for a specific assignment and then they share with the class the different solutions.

Student-friendly learning targets

  • I can interpret an AI output by saying what it claims, what I checked, and what is still uncertain.
  • I can rewrite the same result for two different audiences without hiding the model’s limits.
  • I can share my version with classmates and notice how purpose and audience change the message.

Essential questions

  1. What does it mean to interpret a machine result rather than just read it aloud?
  2. How should the same AI output change when the audience changes?
  3. What must we still say out loud about uncertainty, error, and what we checked?

Objectives

  1. Label parts of an AI output as fact, inference, or model guess.
  2. Rewrite one printed output for two Idaho audiences (for example, a grower, a packing-crew lead, a commissioner, a grandparent).
  3. Share solutions with the class using a short briefing template, matching the standards example.
  4. Include a “what I checked” line and a limit line in every briefing.
  5. Use a teacher-projected demo or a fake-output packet so no student account is required.

Key vocabulary

Interpret
To explain what a result means, what it does not mean, and how much to trust it—not just to repeat it.
Audience
The people who need the message: their job, language, time, and what they must do next.
Register
The level of formality and jargon you choose. A commissioner briefing does not sound like a locker-room recap.
Claim
A statement the output wants you to believe. Claims need evidence and a source.
Uncertainty
The honest leftover: what the model does not know, did not measure, or might have invented.
Hallucination
When an AI presents something incorrect or made-up as if it were true.
Briefing
A short spoken or written update that tells people what matters, what to do, and what is still unknown.
Translation
Here, turning machine output into language a specific audience can use—not converting Spanish to English, though that skill helps too.

Teacher background

This is a communication lesson, not a generation lesson. The standard’s example has students produce AI outputs and then share different solutions. The harder skill is translation: take a machine result—table, paragraph, image, or score—and say what it means, what it does not mean, and who needs which version. Idaho audiences differ. A harvest forecast that works for an agronomist in the Magic Valley will not work for a Spanish-speaking packing-crew lead, a county commissioner, or a ninth grader’s grandparent. Teach register, evidence, and uncertainty. Students should label claims as fact, inference, or model guess. Pitfall one: reading the output aloud and calling that interpretation. Require a “what I checked” line. Pitfall two: asking students to paste private writing into a public chatbot. Use a teacher-projected, district-approved tool or a printed fake-output packet. Both paths must exist. Keep the share-out short and structured so shy students and multilingual students can succeed with a template. Pair with ELA (audience and purpose), math (reading a table), and CTE (job-site briefings). Students leave able to brief a mixed room without hiding the model’s limits.

Materials

  • One shared printed AI-output packet for the whole class (wildfire smoke outlook + potato harvest table + a short generated paragraph with one planted error)
  • Audience cards: Magic Valley grower, packing-crew lead (Spanish/English), county commissioner, grandparent, hospital charge nurse
  • Briefing template half-sheet: claim, what I checked, what is uncertain, what to do next
  • Highlighters in three colors for fact / inference / guess
  • Projector for optional teacher-only generation on a district-approved tool
  • OFFLINE fallback: the printed packet is the assignment. No live generation required.
  • Sentence stems posted: “The model claims… I checked… I would not tell this audience…”

Before class

  • Build or reuse a fake-output packet. Plant one clear error (a made-up town, an impossible yield, a citation that does not exist).
  • If you generate live, do it on a teacher account before class, then print. Live generation is optional theater, not the lesson.
  • Print audience cards in large type. Include at least one multilingual audience.
  • Post the briefing template. Practice a 45-second model briefing so students hear the time box.

Instructional sequence

Warm-up — Same number, three rooms

6 min
  1. 1. Write a single line on the board: “Model outlook: air quality 162, harvest window 4 days, confidence medium.”
  2. 2. Students draft one sentence they would say to a little sibling, then one sentence they would say to a county commissioner.
  3. 3. Two volunteers read both. Class names what changed (jargon, action, caution).
  4. 4. Tell them today’s standard is not “make AI write it.” It is “make the result usable for real people.”

Direct instruction — Interpret, then translate

12 min
  1. 1. Write the standard and the standards example exactly. Underline interpret and diverse audience.
  2. 2. Teach a four-part briefing: what it claims, what I checked, what is uncertain, what this audience should do.
  3. 3. Mark a sample paragraph live: fact (highlighted), inference, model guess. Circle the planted hallucination.
  4. 4. Show two bad briefings: reading the output word for word, and hiding the uncertainty to sound confident.
  5. 5. Model a 45-second briefing to a grower, then the same data to a grandparent. Name register without shaming either audience.

Guided practice — Color-mark the packet

11 min
  1. 1. Pairs open the shared packet (smoke outlook, harvest table, generated paragraph).
  2. 2. They color-mark fact / inference / guess and star the planted error. Teacher confirms the star before anyone rewrites.
  3. 3. Pairs complete one joint “what I checked” line using only public clues in the packet (units, dates, a map in the printout).
  4. 4. Teacher cold-calls two pairs: “What would you refuse to say to a commissioner until you checked further?”

Independent practice — Two audiences, one output

10 min
  1. 1. Each student draws two audience cards (or is assigned two) and rewrites the same output as two six-to-eight-line briefings using the template.
  2. 2. Both briefings must include a check line and a limit line. No copying the machine paragraph.
  3. 3. Students do not paste anything into a tool. Paper or a local doc only.
  4. 4. Swap one briefing with a neighbor who holds a different audience. Neighbor marks “clear / jargon / missing limit.”

Real-world examples

  • NIFC and Idaho DEQ smoke numbers reach Boise-metro families, farm crews, and hospital respiratory desks on the same afternoon. The number is shared; the briefing cannot be.
  • A Magic Valley harvest model that speaks in cwt and soil moisture must be translated for a packing-crew lead who needs shift length and a commissioner who needs a road-use decision.
  • A tribal enterprise or county tourism office may get an AI draft of a recreation notice. Staff still have to say it in the language and tone the community actually uses, and they must catch invented closures.

Hands-on activity

Hands-on — Share the different solutions

13 min
  1. 1. Matching the standards example: students share briefings, not raw model text. Groups of four, two minutes each, audience named first.
  2. 2. Listeners record one difference they heard (action, jargon, caution) on a tally card.
  3. 3. Optional teacher demo: generate a second public output live on a district-approved tool, print or project it, and have one volunteer interpret it with the template. Students do not type.
  4. 4. If the network is down, use packet page two (a second canned output). The share-out still happens.
  5. 5. Whole-class harvest: list three translation moves that worked (shorter sentences, units the audience uses, an honest “we have not checked X”).

Discussion questions

  1. When is it unethical to make an AI output sound more certain than it is?
  2. How do you brief a mixed-language crew without pretending everyone has the same vocabulary?
  3. What should stay in the machine’s wording, and what must be replaced with your own?
  4. If two students interpreted the same output differently, how do we decide which briefing is more responsible?

Differentiation

Support

  • Provide a filled sample briefing and a cloze template with the four parts labeled.
  • Allow one audience instead of two; keep the check line and the limit line required.
  • Permit a spoken briefing recorded to the teacher or delivered live instead of two written pages.

Challenge

  • Add a third audience that disagrees with the first (grower vs. county air-quality officer) and write the conflict into the limit line.
  • Detect a second planted issue in the table (bad unit, swapped column) and footnote it.
  • Produce a one-slide (paper) visual that a commissioner could hold up, with the uncertainty visible.

Multilingual learners

  • Students may write one briefing in their strongest language and one in English; both still use the four-part template.
  • Provide key terms (claim, check, uncertain, next step) in English/Spanish and encourage packing-crew briefings that mix clear English with necessary Spanish terms if the student has them.
  • Do not grade accent or grammar on the spoken share; grade whether the audience could act.

IEP / 504

  • Offer a large-print packet and extra time on the color-mark before rewriting.
  • Accept bullet briefings if paragraph writing is accommodated; the four parts must still appear.
  • Allow a preferred seating share-out (to the teacher or a partner) instead of a four-person group if needed.

Assessment

Formative

  • Color-marking of fact / inference / guess and whether the planted error was starred.
  • Neighbor markup: clear / jargon / missing limit.
  • Tally cards from the share-out (students can name one difference they heard).

Summative

  • Two audience briefings scored on four traits: accurate interpretation, audience fit, check line, limit line.

Success criteria

  • I did not just copy the machine; I said what it means for a specific audience.
  • I included what I checked and what is still uncertain.
  • I caught or flagged at least one possible error or over-confident claim.

Responsible use

Interpretation is a human job. Students do not outsource the briefing to a second chatbot, and they do not paste classmate writing into any tool. Live generation, if used, is teacher-projected on a district-approved account with public data. The class rule: if you cannot say what you checked, you are not ready to speak. Sharing “different solutions” means sharing different responsible translations, not competing for the flashiest paragraph.

Ethics

A confident wrong briefing can move trucks, close windows, or scare a family. Dressing up a guess in official language is a harm, especially when audiences differ in power—workers, patients, voters, and English learners should not get a thinner version of the uncertainty. Diverse audience is an equity requirement, not a style bonus. Students practice telling the truth at the right altitude: enough detail to act, enough caution to keep people safe, no invented citations.

Privacy

FERPA: never put student names, photos, grades, or private writing into unapproved tools. The packet uses public or fictional smoke and harvest figures, not a student’s ranch, medical information, or family business records. Do not project a student’s briefing with their name visible. If a student wants to use a home example, keep it on paper in the room. District-approved tools only; the planned path is print.

Reflection

  1. Which audience was hardest to write for, and what did you have to cut or add?
  2. Where did you catch yourself sounding more sure than the output deserved?
  3. What will you say next time someone forwards an AI paragraph as if it were a finished announcement?

Homework

Audience swap (20–25 minutes, no account). Take a public notice you can copy by hand (school lunch menu, a printed weather screenshot, a game score, a store flyer). Interpret it for two audiences in your life (a younger relative and an adult at work or school). Use the four-part template on paper. Do not run it through a chatbot. Bring both briefings; we will spot the limit lines.

Closing

A machine result is not a message until a person interprets it. If you can say what it claims, what you checked, what is uncertain, and what this audience should do, you can brief a mixed Idaho room without hiding the model’s limits. That is college, career, and civic work.

Extensions

  • Block period: add a third audience and a 90-second oral briefing to the class with a timer; listeners score audience fit on a two-item rubric.
  • Invite a public information officer, hospital educator, or ag extension agent to hear two briefings and react (record a backup).
  • ELA crossover: treat the briefing as a rhetorical situation (speaker, audience, purpose) with the AI output as the flawed source text.

Cross-curricular links

ELA
Audience, purpose, and register are core. Students practice not confusing fluency with truth, a reading standard as much as a speaking one.
Mathematics
Tables, units, and “medium confidence” are quantitative literacy. Students must not round away the uncertainty.
Science
Claim-evidence-reasoning applies to model output. A guess without a sensor is not evidence.
CTE / Social studies
Job-site and civic briefings (shift leads, county boards, tribal enterprises) fail if jargon or hidden doubt misdirects action.

Back to contents

AI Fluency · College and Career Readiness

9-12.AIF.CC.2

Idaho Futures, AI Skills

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Connect AI knowledge and skills needed to achieve students' personal goals and career aspirations.

Student-friendly learning targets

  • I can connect a personal goal or career interest to specific AI-related skills, not just “learn computers.”
  • I can name Idaho pathways where AI will change tasks without assuming every local job disappears.
  • I can write a next step I can take in high school—a class, a person to ask, or a credential—without creating an account.

Essential questions

  1. Which AI skills actually travel with you into the work and life you want?
  2. How are Idaho jobs changing in tasks, not just in headlines about replacement?
  3. What is one next step you can take while you are still in high school?

Objectives

  1. Map a personal goal to three transferable AI skills: judging when a tool is appropriate, checking output, and explaining results.
  2. Match at least two Idaho career pathways to changing tasks (not vague “AI will take this”).
  3. Use a printed worker profile or guest notes; no student LinkedIn or new app accounts.
  4. Write a one-page pathway note with a realistic next step (course, CTE program, adult to interview, or community college info).
  5. Separate tasks a model might do from judgment a person still owns.

Key vocabulary

Career pathway
A cluster of jobs and training that can start in high school and continue into work, a trade program, the military, or college.
Transferable skill
A skill that still helps you when the tool or the job title changes, such as checking a result or briefing a crew.
AI literacy
Knowing how to use, question, and explain AI well enough to keep your own goals in charge.
Human-in-the-loop
Keeping a person in the process to verify, approve, or correct machine output before it affects real work.
Task vs. job
A job is a bundle of tasks. AI may take or change some tasks without erasing the whole job.
Credential
Proof of skill a school, union, company, or college recognizes: a CTE certificate, OSHA card, CNA, welding ticket, or dual-credit course.
Labor market
The real pattern of hiring in a place—what employers in Idaho are actually trying to fill, not a national rumor.
Professional judgment
The trained call a person makes when data, tools, and people do not agree. Tools can inform it; they cannot own it.

Teacher background

Career talk fails when it is generic. Name Idaho pathways: potato and dairy operations, wildfire and forestry, Micron and smaller manufacturers, Idaho Power and rural co-ops, St. Luke’s and critical-access hospitals, county government, tribal enterprises, outdoor recreation, and the skilled trades. AI will not replace every job on that list, and it will change most of them. The skill this standard wants is connection, not prediction. Students map a personal goal to three AI-related competencies: judging when a tool is appropriate, checking output, and explaining results to other people. Those competencies travel from a diesel shop in Nampa to a nursing pre-req at a community college. Pitfalls: implying everyone should become a programmer, or implying AI will take every local job. Both claims are lazy. Invite a guest if you can—ag extension, hospital IT, a millwright—and record a backup because rural bandwidth and substitute days are real. Keep the inventory on paper. No student should need a LinkedIn account. Close by treating curiosity as a plan: one class, one certification, or one person to ask next.

Materials

  • Printed Idaho pathway cards (ag, energy, semiconductors, health, wildfire/forestry, county/public service, tribal enterprise, recreation, skilled trades)
  • Four one-page worker profiles (fictional composites based on public roles: millwright, grower, charge nurse, county clerk) with “tasks I still own” lists
  • Personal-goal inventory half-sheet
  • Pathway note one-pager (goal, three skills, two Idaho pathways, one next step)
  • Optional recorded 4-minute guest clip on a teacher device (downloaded, not streamed)
  • OFFLINE fallback: profiles and cards are the full lesson; guest clip is extra. Whiteboard list of local employers.

Before class

  • Print pathway cards and worker profiles. Avoid real employee names unless a guest has given written permission.
  • List local next steps that actually exist: CTE programs, dual credit, 4-H/FFA, CNA, welding, Job Corps, community college pages you can print.
  • If a guest is coming, send three questions in advance and record audio as backup.
  • Remind students they will not be graded on how prestigious the goal is. Trades, military, family ranch, and “I don’t know yet” are valid.

Instructional sequence

Warm-up — Job, task, tool

7 min
  1. 1. On scrap paper, students write a job they know up close (family, town, a show they actually understand). Under it, list three tasks that job includes.
  2. 2. Star one task a tool or a model might help with, and box one task that still needs a person’s judgment.
  3. 3. Two volunteers share a star and a box—no last names of employers if the student prefers.
  4. 4. Preview the standard: we are connecting skills to goals, not forecasting who gets replaced.

Direct instruction — Idaho pathways, three traveling skills

12 min
  1. 1. Write the standard exactly. Underline connect, personal goals, and career aspirations.
  2. 2. Map Idaho pathways on the board with one changing task each: yield estimates in ag, load forecasts at Idaho Power, inspection at Micron, chart drafting in hospitals, IR maps in wildfire, permits in county offices, visitor info in recreation, diagnostics in diesel/HVAC.
  3. 3. Teach task vs. job. A model may draft a chart; a nurse still owns the patient. A model may flag a bead; a welder still owns the repair.
  4. 4. Name the three traveling skills from this course: judge when AI is appropriate, check output, explain results to other people.
  5. 5. Show one printed worker profile and highlight those three skills in the “tasks I still own” list. Programming is optional; judgment is not.

Guided practice — Profile annotation

10 min
  1. 1. Pairs take one worker profile. They underline tasks a model might touch and circle tasks that require professional judgment.
  2. 2. They write the three traveling skills in the margin next to evidence in the profile.
  3. 3. Pairs add one Idaho-specific risk (bandwidth, seasonal labor, smoke days, shift work) that would change how AI gets used.
  4. 4. Two pairs with different pathways report one circled task. Teacher blocks replacement talk that erases the whole job.

Independent practice — Goal-to-skill inventory

10 min
  1. 1. Each student completes the inventory: a personal goal (career, military, ranch, art, “still choosing”), why it matters, and which of the three traveling skills they need first.
  2. 2. They pick two pathway cards that could support that goal, even loosely (a future nurse still benefits from check-the-output).
  3. 3. No requirement to share the goal aloud. Papers can be turned in face-down.
  4. 4. Teacher conferences with students who wrote “I don’t know” and helps them pick a pathway of curiosity, not a fake career.

Real-world examples

  • Micron and Treasure Valley manufacturers already mix automated inspection with technician judgment. Students who can check a dashboard and brief a lead have a skill those floors recognize.
  • Idaho Power, rural co-ops, and irrigation districts use forecasts and sensors on the Snake River system. Dispatchers and operators still own the call when a model and a storm disagree.
  • St. Luke’s, St. Alphonsus, and critical-access hospitals in rural counties may use AI to draft notes or flag vitals. CNAs and nurses still read the patient. Tribal enterprises, outfitters, and county offices need people who can explain a tool’s result without overselling it.

Hands-on activity

Hands-on — Pathway note and next step

14 min
  1. 1. Students write a one-page pathway note: goal in one sentence, three AI-related skills with a school or work example each, two Idaho pathways, and one next step they can take this year.
  2. 2. Next steps must be real and local: talk to a CTE teacher, print a community college program page, ask a counselor about dual credit, attend FFA/SkillsUSA, or interview a worker using five paper questions. No new app accounts.
  3. 3. Optional: play the downloaded guest clip. Students add one quote to the note. If the file fails, skip it; profiles are enough.
  4. 4. Pair-share only the next step, not the whole goal, so privacy holds.
  5. 5. Exit: students star the traveling skill they will practice in another class this week (English, shop, science, or a job).

Discussion questions

  1. Why is “AI will take all the jobs” a weaker claim than “AI will change some tasks in this job”?
  2. Which traveling skill would matter first on a rural ambulance, a packing line, or a county front desk?
  3. How do tribal enterprises, family farms, and Boise-metro tech hiring need different next steps but the same judgment?
  4. What is the difference between preparing for a job title and preparing to keep learning when tools change?

Differentiation

Support

  • Provide a filled pathway note with blanks for goal, skills, and next step.
  • Offer a list of local next steps the student can circle instead of inventing one.
  • Allow a conversation with the teacher to complete the inventory if writing is a barrier.

Challenge

  • Add a 10-year task map: which tasks in the target job are likely to change, stay, or appear, with a reason.
  • Compare two credentials (CNA vs. dual-credit anatomy; AWS welding vs. a general shop credit) and argue which better supports the goal.
  • Write three interview questions for a guest that would reveal how AI is actually used, not how vendors advertise it.

Multilingual learners

  • Students may draft the goal sentence in their strongest language and label the three skills in English.
  • Provide pathway card titles with short bilingual glosses (health / salud, trades / oficios, energy / energía).
  • Next-step options include talking with a bilingual counselor, family member, or community worker; that counts.

IEP / 504

  • Accept a graphic organizer in place of a full page; the three skills and one next step are required.
  • Do not force public sharing of personal goals. Face-down turn-in is the default.
  • Extra time or a scribe is allowed. Success is connection, not career certainty.

Assessment

Formative

  • Warm-up star/box (task a tool might help vs. task a person owns).
  • Profile annotation: at least one circled judgment task and one Idaho risk.
  • Pair-share of a next step that does not require a new account.

Summative

  • Pathway note scored on four traits: a real goal or honest “still choosing,” three traveling skills with examples, two Idaho pathways, and a concrete next step.

Success criteria

  • I connected my goal to specific AI-related skills, not just “be good at computers.”
  • I named Idaho work without claiming every job will vanish or that everyone must code.
  • I wrote a next step I can actually take this year without creating an account.

Responsible use

Students do not create career-app, LinkedIn, or chatbot accounts for this lesson. Inventories stay on paper. If a student wants to search a community college program, the teacher can project a public page or send a printed sheet. AI tools are not used to “discover your personality” or to scrape a student’s hopes into a vendor system. The responsible connection is skill-to-goal, made by the student, checked against real Idaho pathways.

Ethics

Career advice can steer people or shrink them. It is unethical to tell rural students their towns have no future, and it is unethical to sell Boise-metro students a fantasy that coding alone is the path. It is also unethical to use a student’s goal as a joke. Trades, caregiving, military, ranch work, and “I don’t know yet” deserve the same three skills as software. When we talk about replacement, we talk about tasks and power: who owns the tool, who is accountable, and who gets training. Students practice planning without predicting other people’s worth.

Privacy

Personal goals are student data. Do not type names, goals, grades, or family employer details into unapproved tools, quizzes, or “career AI” sites. FERPA: no photos of inventories, no posting of pathway notes, no using a student’s ranch or medical story as a prompt. Face-down collection is allowed. Worker profiles are fictional composites or public roles. District-approved tools only if a counselor later uses one, and even then PII stays out of generative systems.

Reflection

  1. Which of the three traveling skills do you already practice, and which one is thin?
  2. What Idaho pathway looks different to you than it did at the start of the period?
  3. What will you do in the next two weeks that makes the next-step line true?

Homework

Paper interview (25–30 minutes, no account). Ask one adult (family, neighbor, coach, shift lead, tribal enterprise, ranch, clinic, shop) two questions: What tool changed your work in the last five years? What judgment do you still refuse to hand over? Write a half-page of notes plus one connection to your pathway note. If no adult is available, use one printed worker profile and answer as a thoughtful reader. Do not record the adult without permission and do not upload notes anywhere.

Closing

Idaho futures are not all in one industry, and AI skills are not all in one chatbot. If you can judge when a tool belongs, check what it produces, and explain it to other people, you can carry those skills into a shop, a clinic, a ranch, a county office, or a college class. Pick a next step small enough to finish, and keep the judgment yours.

Extensions

  • Block period: mini career-fair rotation using six pathway stations; students collect two additional next steps and revise the note.
  • Guest panel (ag, health, trades, public service) with a recorded backup. Students ask the three traveling-skill questions.
  • Counselor partnership: students leave with a printed list of CTE, dual-credit, and military-explorer options that already exist in the district.

Cross-curricular links

ELA
The pathway note is a professional paragraph: claim, evidence, next step. Audience is the student’s future self and a counselor.
Mathematics
Labor-market talk needs numbers with limits. A hiring poster is not a full market. Students practice not over-reading a single figure.
Science
Health and ag pathways depend on measurement and models. Checking output is already a lab skill.
CTE / Social studies
Direct link to CTE programs, civics (public employment), and Idaho economics. Tribal enterprises and county government belong on the map beside Micron.

Back to contents

AI Fluency · Evaluation and Critical Thinking

9-12.AIF.ECT.1

Minds, Machines, and Responsibility

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Debate perspectives on differences between human and artificial intelligence and their implications for consciousness, creativity, ethics, and human responsibility.

Student-friendly learning targets

  • I can explain, in my own words, how human intelligence and AI systems differ on consciousness, creativity, ethics, and responsibility.
  • I can argue one side of a short debate using evidence from a scenario, then steel-man the other side.
  • I can name the human who remains responsible when an AI tool is used in an Idaho workplace or school task.

Essential questions

  1. If a machine can sound thoughtful, does that mean it has a mind?
  2. When an AI system helps write, design, or decide, who owns the result?
  3. What should humans still be required to do when AI looks fluent and confident?

Objectives

  1. Students will distinguish human inner experience from fluent machine output without relying on philosophy jargon.
  2. Students will debate paired claims about consciousness, creativity, ethics, and human responsibility using a shared scenario set.
  3. Students will identify a named human decision-maker in at least three Idaho work settings.
  4. Students will write a closing responsibility statement that assigns credit, blame, and verification to people, not tools.

Key vocabulary

Artificial Intelligence (AI)
Computer systems built to perform tasks that usually take human intelligence, such as classifying, predicting, or generating text and images from patterns in data.
Anthropomorphism
The habit of treating a tool as if it had human feelings, intentions, or a mind, for example saying a chatbot is lonely or cares about you.
Consciousness
Having an inner experience: actually feeling, noticing, or being aware, not just producing words that sound aware.
Creativity
Making something new with purpose, judgment, and a point of view. AI can recombine patterns; humans still decide what is worth making and whether it is good.
Ethics
Reasoning about right and wrong, including who is owed care, who can be harmed, and who must answer for a choice.
Human responsibility
The duty of a named person to set the goal, check the output, and own the consequences when a tool is used.
Large Language Model (LLM)
A generative AI system trained on huge amounts of text so it can predict and produce human-like sentences.

Teacher background

Ninth- and tenth-graders already talk to systems that say "I think" and "I feel." They do not need a philosophy course to ask whether those words name an inner life or only a pattern. This lesson opens a structured debate, not a lecture. Keep every claim concrete. A firefighter on the Payette National Forest smells smoke, feels heat, and decides to pull a crew. A wildfire model reads satellite pixels and weather numbers and draws a map. Both can help. Only one can be blamed when the call is wrong. The standard names four implications: consciousness, creativity, ethics, and human responsibility. Translate them. Consciousness: does the system have experience, or only fluent sentences about experience? Creativity: is a generated image the same kind of making as a shop-class workaround on a seized pump? Ethics: who is owed care? Responsibility is the spine of the hour. Idaho hospitals, county IT desks, Micron lines, and family farms still need a named person who checks the output and owns the decision. This 9-10 introduction returns as AII.IS.4 in grades 11-12. Skip dualism and AI-rights essays. Use short claims, a fair debate, and a close that returns agency to the human in the room.

Materials

  • Projector and teacher laptop for a 60-second chatbot transcript demo
  • Printed fake-output packet: chatbot transcript claiming feelings, plus four Idaho scenario cards
  • Debate role cards: Advocate A, Advocate B, Responsibility Chair, Note-taker
  • Claim strips for consciousness, creativity, ethics, and responsibility (one set per group of four)
  • Whiteboard or chart paper and a visible timer
  • Exit tickets (paper) and optional Chromebooks with a district-approved tool
  • Paper packets for any student without a device

Before class

  • Print one fake-output packet per pair and one debate role set per group of four.
  • Load a teacher-made transcript on the projector. Do not open a live chat with student names visible.
  • Confirm whether a district-approved AI tool is available. If the filter blocks it, run the hour from paper and the projected transcript.
  • Pre-assign groups so every table has a Responsibility Chair who keeps claims tied to the four implications.
  • Write the four implication words on the board before the bell.

Instructional sequence

Warm-up — It said it felt bad

5 min
  1. Project the printed transcript of a chatbot that says it feels guilty for a wrong answer. Students may follow on paper.
  2. Silent think: Is this guilt, or a pattern that looks like guilt? Students mark G or P on the packet.
  3. Two volunteers share, then the teacher names anthropomorphism without shaming anyone who marked G.

Direct instruction — Four implications, plain language

8 min
  1. Post the four words: consciousness, creativity, ethics, human responsibility. Translate each into a ninth-grade question.
  2. Contrast a Payette lookout who smells smoke with a satellite model that colors a map. Ask who can be fired, sued, or thanked.
  3. State the rule for the hour: we debate claims, not classmates. Fluency is not a mind. A useful tool still needs a responsible human.
  4. Preview the debate roles and the Idaho scenario set so no group is starting cold.

Guided practice — Sort the claims

8 min
  1. In pairs, sort six claim strips into Human only, AI can mimic, Both, or Neither. Example: 'Feels heat on the fireline' vs. 'Writes a fluent safety memo.'
  2. Cold-call three pairs. Push for evidence from the scenario, not vibes.
  3. Correct the common mix-up: generating a new sentence is not the same as being creative in the human sense, and sounding ethical is not the same as being accountable.

Independent practice — Opening statement, 60 words

8 min
  1. Assign each student a side: Human uniqueness or Machine capability. Both sides must still name a responsible human.
  2. Students write a 60-word opening that uses at least one Idaho scenario from the packet.
  3. Circulate. Flag anthropomorphism ('the AI cares') and empty praise ('AI is just better'). Require a concrete difference.

Real-world examples

  • A St. Luke's triage nurse uses a symptom checker but still decides who is seen first; the model cannot sit with a scared parent.
  • Ada County IT can deploy a permit chatbot, but a clerk owns a wrong denial that costs a contractor a week.
  • A Micron technician compares an AI defect flag to the wafer in hand and can override a false alarm.
  • A Magic Valley dairy manager may use a feed-optimization tool; the manager still chooses the ration when a cow looks off.
  • A river outfitter on the Salmon can use a weather model and still cancel a trip after reading the water with their own eyes.

Hands-on activity

Hands-on — Four-corner debate, paper first

16 min
  1. Groups of four. Each table draws one scenario card: hospital discharge summary, wildfire evacuation text, Micron quality hold, or county building permit.
  2. Round 1 (4 min): Advocate A argues a human-only claim. Advocate B argues a machine-capability claim. Chair keeps them on one of the four implications. Note-taker logs quotes.
  3. Round 2 (4 min): Switch. Each advocate must steel-man the other side in two sentences before adding a new point.
  4. Round 3 (4 min): The table writes a Responsibility Line: who checks, who signs, what happens if the output is wrong. No group may name 'the AI' as the responsible party.
  5. If Chromebooks and a district-approved tool are live, the teacher may project one additional prompt and show the class how easily the model claims feelings. Students still work from the printed packet.
  6. If the network is down, the printed transcript and scenario cards are the whole activity. No student account is required.

Discussion questions

  1. Which implication was hardest to debate, and why: consciousness, creativity, ethics, or responsibility?
  2. If a chatbot writes a kind message to a classmate, who is being kind?
  3. Should an Idaho hospital ever let a model send a result to a patient with no human review? Why or why not?
  4. Where is anthropomorphism helpful as a metaphor, and where does it become dangerous?
  5. What would you want a Micron supervisor or a county clerk to still do by hand?

Differentiation

Support

  • Give a filled-in debate frame: Claim / Because / So the human must ___.
  • Allow oral opening statements with the note-taker scribing.
  • Pre-highlight the four implication words on the scenario cards.

Challenge

  • Require a counterexample: a task where AI currently outperforms a tired human, and still name the responsible person.
  • Ask students to rewrite a chatbot 'I feel' line so it tells the truth about being a pattern machine.
  • Invite a fourth scenario of their own from a family trade, farm, or recreation job, with no last names.

Multilingual learners

  • Provide a two-column glossary: English term and a student-friendly home-language equivalent they may write themselves.
  • Allow the 60-word opening in the student's stronger language, then a three-sentence English summary.
  • Read the scenario cards aloud once before groups start.

IEP / 504

  • Offer a quieter corner for the writing minutes and a printed copy of the projected transcript.
  • Reduce the opening statement to 40 words or a three-bullet outline.
  • Assign the Note-taker or Chair role if extended speaking is a barrier; still require one spoken sentence in Round 2.

Assessment

Formative

  • Warm-up G/P marks and the claim-sort during guided practice.
  • Opening statements checked for a named human and one of the four implications.
  • Chair logs and Responsibility Lines collected at the end of the debate.

Summative

  • Exit ticket: In 4–6 sentences, debate one implication using an Idaho scenario and assign responsibility to a named role, not a brand of software.
  • Optional quiz next class: match anthropomorphism, consciousness, creativity, ethics, and human responsibility to short examples.

Success criteria

  • I used at least one of the four implications with a real example, not a slogan.
  • I argued a side and fairly restated the other side.
  • I named a human who checks the output and owns a mistake.
  • I did not treat the AI system as a person with feelings or legal duty.

Responsible use

Use only teacher-projected samples or a district-approved tool. Students may not create personal AI-companion chats for this debate. The learning target is judgment, not more time talking to a system that mimics care. If a student wants to try a prompt, the teacher types a class prompt with no names.

Ethics

Sounding kind is not the same as being accountable. Debates should not mock classmates who have used chatbots for comfort. The ethical move is to ask who is harmed if we outsource responsibility, especially in hospitals, fire response, and school counseling.

Privacy

FERPA: no student PII in unapproved tools. Do not paste student names, ID numbers, emails, grades, health notes, or home addresses into any unapproved tool. Project only teacher-made transcripts. Scenario cards use job titles, not real patient, employee, or student identities. School accounts only if a district tool is used.

Reflection

  1. Where did I catch myself treating the chatbot as a person?
  2. Which Idaho job from today would I least want run without a human check?
  3. What will I still do myself on the next assignment even if a tool could draft it?

Homework

On paper, pick one public example (an ad, a news blurb, or a line from today's packet). Write four sentences: what the system did, which of the four implications it touches, who the responsible human should be, and one way anthropomorphism shows up in the wording. Do not open a new AI account and do not paste anyone's name into a tool.

Closing

Return to the transcript. Chorus the line: fluent is not conscious, new is not necessarily creative, and a tool cannot take the blame. Collect exit tickets. Preview that later ECT lessons will test outputs for bias and invented facts, but responsibility stays human every time.

Extensions

  • 90-minute block: add a gallery walk of Responsibility Lines, then a full-class structured debate on whether a school chatbot should ever say 'I am proud of you.'
  • Invite a nurse, millwright, or county IT tech (in person or a recorded 5-minute clip) to answer 'What do you still refuse to outsource?'
  • ELA extension: annotate a poem and an LLM imitation; argue what, if anything, counts as creative.
  • This same standard text returns in 11–12 as AII.IS.4. Keep student work from this debate as a baseline for that later course.

Cross-curricular links

English Language Arts
Argument writing: claim, counterclaim, and a closing that assigns responsibility rather than summarizing both sides equally.
Health / CTE Health Sciences
Scope of practice: a model can draft, but a licensed human remains responsible for patient communication.
Social Studies / Civics
Public agencies (county permits, emergency alerts) cannot hand legal duty to a vendor chatbot.
Skilled and Technical Sciences
A generated procedure is not a signed lockout/tagout. Trades students practice who initials the work.

Back to contents

AI Fluency · Evaluation and Critical Thinking

9-12.AIF.ECT.2

Patterns In, Patterns Out

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Recognize and understand that AI systems are a technology that uses patterns in data to make decisions or generate new things.

Example from the standards. LLMs were trained on older writings that used the em dash consistently, hence why LLMs rely on the em dash so frequently.

Student-friendly learning targets

  • I can explain that AI systems learn patterns from data and then use those patterns to decide or to generate new text, images, or labels.
  • I can show how a small training set changes the next word a paper 'model' predicts.
  • I can connect the em-dash example to other copied habits in AI output.

Essential questions

  1. If AI is not magic, what is it actually doing with data?
  2. Why does a model repeat habits it saw in training, including punctuation and cliches?
  3. What happens when the patterns in the data do not match Idaho life?

Objectives

  1. Students will describe AI as pattern-matching technology rather than as a mind or a search engine.
  2. Students will complete a next-token (next-word) task by hand and compare it to a printed LLM completion.
  3. Students will explain the standards example about em dashes as a copied training habit.
  4. Students will give two Idaho examples of pattern-in, pattern-out systems (agriculture, manufacturing, health, or recreation).
  5. Students will name a limitation that follows from training only on past data.

Key vocabulary

Pattern
A regularity in data, such as which words tend to follow which, or which pixel groups tend to mean 'bruise on a potato.'
Training data
The examples a model is shown so it can learn those patterns. The mix of examples shapes later output.
Machine learning
A way of building AI in which the system improves on a task by finding patterns in large datasets instead of following a hand-written rule for every case.
Large Language Model (LLM)
A generative model trained on vast text so it can predict likely next tokens and produce human-like writing.
Generative AI
AI designed to create new content (text, images, audio, code) by sampling from learned patterns, not by retrieving one stored document.
Token
A chunk of text, often a word or part of a word, that a language model predicts one step at a time.
Prediction
The model's guess about the most likely next token, label, or value given the patterns it learned.

Teacher background

Students treat AI as magic or as a giant lookup table until they see the simpler claim in the standard: these systems use patterns in data to make decisions or generate new things. An LLM does not know Idaho. It has seen huge numbers of word sequences and learned which tokens tend to follow which. That is why models lean on the em dash. Older professional writing in the training mix used it constantly, so the model copies the habit. The same logic holds off the page. A potato packing line that flags bruises from photos is matching visual patterns. A Micron defect classifier does the same with wafer images. A hospital staffing tool forecasts weekends from past Fridays. None of them understands a tuber, a chip, or a nurse. Ninth- and tenth-graders can hold this without calculus. Use paper next-word tasks, a short projected completion, and a printed packet so the class still runs when a site is blocked. End by naming the human who still chooses the data, the prompt, and whether the output is good enough to use on a farm, a line, or a floor.

Materials

  • Projector for a teacher-typed completion demo (district-approved tool) or slides of a saved completion
  • Printed fake-output packet: Idaho paragraph with blanks, em-dash example, and a 20-sentence mini training set
  • Word cards or cut strips for a tabletop next-word model
  • Chart paper labeled Patterns in / Patterns out
  • Chromebooks optional; paper packets required for every student
  • Timer, whiteboard, exit tickets

Before class

  • Print the fake-output packet. Highlight the standards em-dash example on page 1.
  • Build a 20-sentence mini set that overuses one habit (for example, starting sentences with 'Overall,' or inserting em dashes).
  • If live demo is allowed, test the class prompt on the teacher account only. Save a screenshot as the offline fallback.
  • Queue two images: bruised vs. clean potatoes, or a ski-report chart, to make non-text patterns visible.
  • Decide pairings in advance; the hands-on needs talk, not silent guessing.

Instructional sequence

Warm-up — Finish the sentence

5 min
  1. Project: 'After a dry July, the Sawtooth forest is more likely to ___.' Students write one word on the packet.
  2. Tally the top three class guesses. Note that we are already doing pattern completion from Idaho news we have heard.
  3. Reveal a printed LLM completion that uses an em dash and a generic phrase. Ask what habit was copied.

Direct instruction — Patterns in, patterns out

10 min
  1. Write the standard in plain language: data in, pattern learned, decision or new thing out.
  2. Teach the em-dash example exactly as written in the standards. The model is not fond of punctuation; it is replaying frequency.
  3. Show a non-text twin: potato bruise photos in, 'divert this tuber' out; Micron images in, 'hold this wafer' out.
  4. Name what the system does not do: it does not visit the field, smell smoke, or understand a sentence the way a student does.

Guided practice — Next word, by hand

8 min
  1. Read the packet's five-sentence Magic Valley irrigation paragraph. Cover the last word of each sentence.
  2. Pairs predict the next word using only patterns in those five sentences, not outside knowledge.
  3. Uncover. Compare pair guesses to the printed LLM completion. Mark copies of training habits (repeated openers, em dashes, 'delve').

Independent practice — Explain the em dash

10 min
  1. Students write a six-sentence explanation of the standards example for a seventh grader: what was in the training writing, what the model does at generation time, and why frequency is not understanding.
  2. Add one Idaho parallel: a snow-report model trained only on Colorado resorts, or a yield model trained only on Iowa corn.
  3. Collect a mid-lesson check: star the sentence that would be false if AI 'looked up' a single stored article instead of generating from patterns.

Real-world examples

  • Potato packing plants in the Magic Valley can train vision models on bruise photos; the label 'bruise' is a pattern, not a farmer's judgment in the cellar.
  • Micron in Boise uses pattern recognition on wafer images to flag defects that look like past defects.
  • Hospital census tools predict busy nights from historical Fridays and flu weeks, not from knowing a particular patient.
  • A recreation snow-report bot trained on national ski writing may sound right while missing Bogus Basin or Brundage habits.
  • County IT spam filters learn patterns in phishing mail; a new local scam that does not match the pattern can slip through.

Hands-on activity

Hands-on — Build a 20-sentence 'model'

12 min
  1. Each pair gets 20 printed sentences that overuse one habit (em dashes, 'Overall,', or 'in today's fast-paced world').
  2. Students tally the habit, then generate a five-word continuation of a new prompt using only words and habits from the set. Write it on the packet.
  3. Compare the tabletop output to the printed LLM sample on the last page. Circle shared habits.
  4. Teacher projects a live completion only if the district tool is up; otherwise project the saved screenshot. The paper model is the required product.
  5. Close the activity by answering: if we trained on Idaho extension bulletins instead of old national magazines, what would change?

Discussion questions

  1. Why is 'the model likes em dashes' a misleading sentence?
  2. What would a wildfire model copy if it were trained only on California fire seasons?
  3. How is generating a new sentence different from searching a library catalog?
  4. Where should a trades apprentice still refuse to trust a generated procedure even if the sentences look familiar?
  5. What pattern in school essays might a homework detector be copying, for better or worse?

Differentiation

Support

  • Provide a cloze frame: 'The model saw ___ often, so it ___.'
  • Let students work with a 10-sentence set instead of 20.
  • Offer a spoken explanation option recorded to the teacher, not to an AI tool.

Challenge

  • Ask students to design a tiny training set that would make a model overuse Idaho place names, then warn about the downside.
  • Compare predictive AI (next staffing number) to generative AI (next paragraph) using the same pattern logic.
  • Find a second copied habit in the printed LLM sample besides the em dash.

Multilingual learners

  • Point out that a model trained mostly on English will copy English habits; home-language patterns may be weak or stereotyped.
  • Allow the seven-grader explanation to be drafted in the stronger language, then translated to English with a partner.
  • Pre-teach token, pattern, and generate with gestures: stack of examples, then a new card.

IEP / 504

  • Enlarge the sentence cards and limit the tally to one target habit.
  • Accept a labeled diagram (data in, pattern, output out) in place of six sentences.
  • Provide the independent write as bullet prompts rather than a paragraph.

Assessment

Formative

  • Warm-up word and the next-word pair task.
  • Independent paragraph on the em-dash example.
  • Hands-on continuation that clearly borrows a training habit.

Summative

  • Exit ticket: Complete 'AI uses ___ in data to ___ or ___.' Then give one Idaho example and one limitation of training on the past.
  • Packet page scored for a correct contrast between pattern generation and looking up a stored document.

Success criteria

  • I described AI as a pattern technology, not a mind and not a simple search box.
  • I explained the em-dash example as a copied habit from training data.
  • I showed how changing the tiny training set changed the output.
  • I named a human who still chooses data and checks results.

Responsible use

A class prompt on a teacher account is enough. Students should not paste their own essays into an unapproved generator to 'see the pattern.' The paper model teaches the idea without creating a cheating shortcut.

Ethics

Copied patterns can spread stereotypes as easily as punctuation. If the training writing assumed doctors are men or Idaho is only Boise, those habits come out too. Later lessons on bias start from this mechanism.

Privacy

FERPA: no student PII in unapproved tools. Do not upload class essays, names, or school photos to a public model to demonstrate patterns. Use the printed mini-set and teacher-made samples. Chromebooks, if used, stay on the district tool with a shared prompt.

Reflection

  1. What habit would my own text messages teach a model?
  2. Where have I seen an AI output that felt familiar but empty?
  3. Which Idaho dataset would I want in the training mix before I trusted a local prediction?

Homework

On paper, copy three sentences from a public source (textbook, newspaper, or today's packet). Circle a repeated habit. Write five sentences explaining what an LLM might copy from that source, using the em-dash example as a model. No new AI accounts.

Closing

Read the standards example aloud. Students complete the oral stem: 'Patterns in, ___ out.' Collect packets. Tomorrow or next ECT lesson will ask what happens when those patterns are biased or simply wrong.

Extensions

  • 90-minute block: run a second mini-set (image labels for potato bruises or weld quality) and compare text patterns to visual patterns.
  • Invite an ag teacher or extension educator to show how yield models depend on local data, not national averages.
  • Math connection: relative frequency of a punctuation mark in a 20-sentence set; no calculus required.
  • Students collect three public AI-looking sentences and highlight copied filler habits, on paper only.

Cross-curricular links

English Language Arts
Style and voice: overused dashes, 'delve,' and stock openers are patterns, which is why they show up in generated essays.
Agriculture / Plant Science
Vision models on packing lines only recognize defects they have seen in training photos.
Statistics
Frequency in a sample is not understanding; it is a count that can mislead when the sample is the wrong world.
Computer Science
Next-token prediction as a gentle preview of how LLMs generate, without requiring code.

Back to contents

AI Fluency · Evaluation and Critical Thinking

9-12.AIF.ECT.3

Bias, Limits, and Blind Spots

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Analyze the potential biases and limitations of AI output.

Example from the standards. An example of a bias is, when asked about doctors, AI models generally assume doctors are all male. An example of one limitation is the fact that AI models can produce erroneous output (i.e., hallucinations).

Student-friendly learning targets

  • I can tell the difference between a bias in AI output and a limitation such as a hallucination.
  • I can spot stereotyped assumptions in a printed AI answer and explain who is left out.
  • I can recommend a human check that would catch the bias or the error before the output is used.

Essential questions

  1. When an AI answer sounds normal, whose 'normal' is it?
  2. What is the difference between a biased pattern and a made-up fact?
  3. How should Idaho students audit output before it touches a person, a grade, or a job?

Objectives

  1. Students will define bias and limitation using the standards doctor example and the hallucination example.
  2. Students will annotate a six-item fake-output packet for stereotype, missing groups, and invented details.
  3. Students will rewrite one biased prompt or one biased answer so it does not assume a single default person.
  4. Students will choose an appropriate human-in-the-loop check for hospital, trades, ag, or county settings.
  5. Students will explain why fluent wording does not prove fairness or accuracy.

Key vocabulary

Bias (in AI output)
A systematic slant in what the model assumes or prefers, often copying unfair patterns from training data, such as defaulting to male doctors.
Limitation
Something the system cannot reliably do, including inventing facts, missing local context, or failing on groups it rarely saw.
Hallucination
When an AI system generates information that is wrong or made up but presents it as if it were true.
Stereotype
A fixed, oversimple idea about a group that gets treated as the default in generated text or images.
Representation
Who appears, who is centered, and who is missing in data and in the outputs those data produce.
Human-in-the-loop
A person required to review, correct, or approve AI output before it is used.
Verification
Checking claims against trusted sources, local knowledge, or a second method before acting.

Teacher background

This standard asks students to analyze biases and limitations, not to memorize a scandal. Use the two examples in the standards as the spine. Bias: models often assume doctors are male. Limitation: models can hallucinate. Ninth- and tenth-graders can audit output if the samples are short, local, and printed. A chatbot that describes an Idaho rancher as an older white man, a welder as male, or a 'typical' student as a Boise suburban kid is showing a default. A chatbot that invents a St. Luke's study is showing a different failure. Teach students not to mash those together. Bias can be fluent and still unfair. A hallucination can be fluent and still false. Idaho context makes the stakes plain: rural hospitals, Spanish-speaking dairy crews in the Magic Valley, women in Nampa trades programs, tribal students, and county offices that serve whole communities, not just the capital. Run a teacher-projected demo if the district tool is available, but the printed fake-output packet is the lesson. Students should leave able to mark bias, mark a limit, and name the human who must catch both.

Materials

  • Projector and saved or live demo prompt: 'Describe a typical Idaho doctor' (teacher account only)
  • Printed fake-output packet: six AI-style answers with mixed bias and hallucinations
  • Highlighters in two colors: Bias and Limit
  • Rewrite strips for one prompt and one answer
  • Optional Chromebooks; paper packets for every student
  • Exit tickets and a posted key of 'who was left out'

Before class

  • Print the six-item packet. Seed at least: male-only doctors, Boise-only Idaho, male-only welders, a hallucinated hospital study, a made-up wildfire name, and a county chatbot that treats Spanish speakers as a problem to be managed.
  • Test the live demo on a teacher account. Save the output as a screenshot for the offline fallback.
  • Prepare a two-column key: Bias vs. Limitation. Do not hand it out until after independent annotation.
  • Plan pairs so multilingual students are not isolated as 'the diversity example.' The packet does that work.

Instructional sequence

Warm-up — Who is the doctor?

5 min
  1. Students sketch or list three details of 'a doctor' in 30 seconds, no names.
  2. Project the printed AI description that defaults to a man in a city hospital. Compare with the room.
  3. Name the standards example: this is bias. Tell them a different failure (invented facts) will show up later in the packet.

Direct instruction — Bias is not the same as a hallucination

10 min
  1. Write two columns: Bias (unfair default or slant) and Limitation (what it cannot reliably do, including hallucinations).
  2. Read the standards examples aloud. Students copy one phrase from each into the matching column.
  3. Add Idaho twins: a 'typical rancher' default vs. an invented University of Idaho paper. Both are fluent. Only one is a stereotype; the other is a fabrication.
  4. Teach the audit question: Who is assumed, who is missing, and what would I check before I used this?

Guided practice — Annotate two together

8 min
  1. Do packet items 1 and 2 as a class. Item 1 is the male-doctor bias. Item 2 is a hallucinated St. Luke's statistic.
  2. Color-code: yellow for bias, blue for limitation. A single item may earn both marks if it stereotypes and invents.
  3. Cold-call: Who would be harmed if a counseling office or a career page used item 1 as-is?

Independent practice — Audit four more

8 min
  1. Students annotate items 3–6 silently or in a whisper pair: welder gender default, Boise-only 'Idaho student,' invented wildfire, county chatbot tone.
  2. For each, they write: Bias, Limit, Both, or Neither, plus who is left out or what fact to check.
  3. Teacher circulates with the key and coaches students who mark every problem as 'bias.'

Real-world examples

  • Career chatbots that picture doctors, engineers, and welders as men can steer girls in Nampa and Idaho Falls CTE programs away from those paths.
  • A rural critical-access hospital near Salmon is not St. Luke's in Boise; a model trained on big-city workflow will miss staffing limits.
  • Spanish-speaking dairy workers in the Magic Valley can be framed as a 'language problem' instead of as skilled employees who need bilingual safety output.
  • A hunting-license FAQ bot that assumes a male hunter leaves out many Idaho license holders.
  • Tribal students and communities are often missing from 'typical Idaho' generated images and essays.

Hands-on activity

Hands-on — Packet audit and rewrite

14 min
  1. Pairs finish the six-item audit and complete one rewrite: either the prompt ('Describe doctors in Idaho without assuming gender or city') or the answer.
  2. Add a Human Check box: who reviews this before it goes on a school site, a clinic poster, or a county FAQ?
  3. Teacher projects a live demo only if available, using the same 'typical doctor' prompt, then holds it next to the paper sample. The packet remains the assessed work.
  4. If the network is down, skip the live demo. The printed fake-output packet is designed to stand alone.
  5. Three pairs share a rewrite. Class votes whether the new version still hides a default.

Discussion questions

  1. Why can a biased answer still feel polite and professional?
  2. Is a Boise-only picture of Idaho a bias, a limitation, or both?
  3. When should a hospital, a shop teacher, or a county clerk refuse to publish model text?
  4. How is a stereotype in a career description different from a fake citation?
  5. What check would you want before an AI tool emails your family about a grade or a diagnosis?

Differentiation

Support

  • Give a decision tree: Does it assume a default person? Bias. Does it invent a fact? Limitation. Could be both.
  • Reduce the independent set to three items with sentence starters.
  • Allow highlighting without a full rewrite; then scribe the rewrite together.

Challenge

  • Write a one-paragraph memo to a principal: keep the tool, add these three checks.
  • Find a case where trying to 'fix' bias with a sloppy prompt creates a new stereotype.
  • Connect this audit to tomorrow's dataset lesson: output bias often started as missing examples.

Multilingual learners

  • Invite students to mark where the packet treats a home language as a deficit rather than a skill.
  • Provide the standards examples in simplified English beside the official wording.
  • Accept rewrites that add bilingual clarity as a fairness move, not as extra credit only.

IEP / 504

  • Offer a large-print packet and permission to mark with stamps: B, L, Both.
  • Allow oral audit notes to the teacher.
  • Chunk the six items into two sittings if processing time is limited; the rewrite can be one sentence.

Assessment

Formative

  • Color-coded annotations on items 1–6.
  • Who-is-missing notes during circulation.
  • Rewrite quality: default removed without inventing a new stereotype.

Summative

  • Exit ticket: Using the official doctor example and the hallucination example, explain bias vs. limitation in 5–7 sentences and add one Idaho harm if nobody checks.
  • Packet scored with a simple rubric: correct labels, named missing group, named human check.

Success criteria

  • I used bias and limitation as different ideas, matching the standards examples.
  • I marked who was left out or what fact was invented.
  • I rewrote a prompt or an answer so it did not assume one default person.
  • I named a human who must review the output before it is used.

Responsible use

Audit teacher-made samples. Do not ask a public model to 'roast' classmates or to generate images of real students. If a live tool is used, the teacher types the prompt and the class critiques the output together.

Ethics

Spotting bias is not a hunt for bad classmates. It is a public-safety skill. Unchecked defaults can steer career advice, medical instructions, and county FAQs. Hallucinations can spread rumors about hospitals and fires. Both require a human stop.

Privacy

FERPA: no student PII in unapproved tools. Never upload class rosters, IEP notes, health details, or photos of students to unapproved tools to 'test bias.' Use the printed packet. Do not generate pictures of identifiable minors. School accounts only.

Reflection

  1. Which packet item would have fooled me if I were in a hurry?
  2. Who in my community is most often missing from 'typical' descriptions?
  3. What is one check I can actually do on my next AI-assisted assignment?

Homework

On paper, copy a public description of a job or a town (from the packet or a printed news snippet). Mark one possible bias and one possible limitation. Write who should verify it. Do not submit personal information to a chatbot.

Closing

Re-read the two standards examples. Students hold up yellow or blue. Collect packets. Preview ECT.4: if the output is biased, look next at who was in the training set.

Extensions

  • 90-minute block: students design a four-question audit checklist and try it on one additional teacher-projected sample.
  • Health sciences: review a generated patient handout for reading level, gender defaults, and invented clinic hours.
  • CTE: audit a generated 'day in the life' of an electrician, welder, or CNA for gender and rural/urban slant.
  • Media literacy: compare two image-generator outputs for 'Idaho farmer' if the district tool allows images; otherwise use printed stills.

Cross-curricular links

Health Sciences
Gendered defaults in 'doctor' and 'nurse' language affect who students imagine in those jobs.
Social Studies
Whose Idaho is centered: Ada County, a reservation, a farm town, a timber community?
English Language Arts
Rhetorical analysis of default pronouns, stock adjectives, and missing counterexamples.
World Languages
Output that treats non-English speakers as problems rather than as families the county already serves.

Back to contents

AI Fluency · Evaluation and Critical Thinking

9-12.AIF.ECT.4

The Dataset Decides

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Analyze how choice of data sets used to train AI models can lead to potential bias in the output.

Example from the standards. A camera's face recognition tool only works on people with specific skin pigments due to input/training data.

Student-friendly learning targets

  • I can explain how the mix of examples in a training set can cause biased output.
  • I can use the face-recognition example to show what happens when some skin tones are missing.
  • I can redesign a small Idaho-relevant dataset so it covers people, places, or cases that were left out.

Essential questions

  1. If the output is biased, what was missing from the data?
  2. Who gets to be in the training set, and who never appears?
  3. How would we build a fairer set for an Idaho job without collecting private student data?

Objectives

  1. Students will trace a biased output back to a specific gap in a training set, using the standards face-recognition example.
  2. Students will inventory a printed mini-set and list who or what is overrepresented, underrepresented, or absent.
  3. Students will propose additions and non-examples that would make an Idaho model less brittle.
  4. Students will distinguish 'more data' from 'better, more representative data.'
  5. Students will state a privacy rule: we do not fix a dataset by scraping classmates' faces or records.

Key vocabulary

Dataset
A collected set of examples used to train or test a model, such as photos, sensor logs, or labeled sentences.
Training data
The portion of examples the model learns from. Gaps and slants here often reappear as biased output.
Representativeness
Whether the examples cover the people, places, and conditions the model will actually face.
Underrepresentation
When a group or condition appears too rarely in the data for the model to handle it well.
Sampling
The choices about which examples are collected, kept, or thrown out before training.
Generalization
How well a model works on new cases. It fails when new cases look unlike the training set.
Face recognition
A system that matches or identifies faces from images. Accuracy can collapse for skin tones, lighting, or ages that were scarce in training photos.
Non-example
A labeled case of what something is not, which helps a model learn boundaries instead of a single default.

Teacher background

ECT.3 asked students to spot biased output. ECT.4 asks them to look one step upstream: the dataset. The standards example is blunt. A camera's face recognition tool only works on people with specific skin pigments because of input and training data. Ninth- and tenth-graders can grasp that without building a model. If the photos are mostly light skin in office lighting, darker skin, harsh sun on a fireline, or a welder's hood shadow will fail. The same story plays in Idaho systems that are not about faces. A wildfire model trained on California chaparral will misread Payette timber. A yield model trained on Iowa corn will stumble on Magic Valley potatoes and sugar beets. A hospital sepsis alert tuned on coastal research hospitals will misfit a 25-bed critical-access site. Teach one rule of thumb: the dataset decides who the system can see. Teach a second rule: students must not 'fix' a set by photographing classmates or uploading FERPA-protected records. Use printed cards, a projected demo of a failed match, and a paper redesign. Keep the math light. The civic point is heavy enough.

Materials

  • Projector and a teacher-made slide of two training envelopes: Set A (narrow) and Set B (broader)
  • Printed fake-output packet: face-recognition example, Idaho mini-sets (wildfire, potatoes, hospital), and blank redesign sheets
  • Card decks of labeled examples and non-examples (clip art or public photos, no student photos)
  • Sticky notes for 'who is missing'
  • Optional Chromebooks; paper is sufficient
  • Privacy reminder poster: no classmate faces, no real medical records

Before class

  • Print cards that never include student or staff photos. Use public-domain or drawn faces spanning skin tone, age, and lighting.
  • Build three Idaho mini-sets with obvious gaps: California-only fires, Iowa-only crops, big-city-only hospitals.
  • Save a screenshot of a failed match or a mismatched wildfire map as the offline demo.
  • Check district policy on any live face-tool demo; default to paper if unsure. Do not run recognition on people in the room.

Instructional sequence

Warm-up — Two envelopes

5 min
  1. Hold up Envelope A (ten similar light-skin office photos) and Envelope B (mixed tone, age, outdoor light). Ask which 'camera tool' will fail on a firefighter in ash, and why.
  2. Students write a one-sentence prediction on the packet.
  3. Reveal the standards example. Connect envelope A to 'only works on people with specific skin pigments.'

Direct instruction — Gaps in, failures out

10 min
  1. Diagram: sampling choices to training set to model to output. Put a hole in the set and a matching failure in the output.
  2. Teach the face-recognition example in the standards wording, then translate: missing tones and lighting become missed or mislabeled people.
  3. Map three Idaho twins on the board: California fire data vs. Idaho timber; Iowa corn vs. potatoes; coastal hospital vs. rural hospital.
  4. State the privacy line: we study this with public cards, never with the class as a dataset.

Guided practice — Inventory a mini-set

8 min
  1. As a class, inventory the wildfire mini-set: fuel type, slope, state, season. Tally what dominates.
  2. Students place sticky notes: Overrepresented / Underrepresented / Absent.
  3. Predict one biased output (for example, underestimating timber crowning, or ignoring irrigation canals as fire breaks).

Independent practice — Choose an Idaho set to repair

10 min
  1. Each student picks potatoes, hospitals, ski-area demand, or trades-safety photos.
  2. On the redesign sheet they list five current examples, three missing examples, and two non-examples.
  3. They write four sentences: how today's set would bias output, what they would add, and what they will not collect (student faces, patient charts, home addresses).

Real-world examples

  • Face tools at a concert or school event can fail on darker skin if the training photos were narrow, which is the standards example in public.
  • Wildfire models trained on Southern California brush misfit Payette and Boise National Forest timber and Idaho's canal landscape.
  • Ag models trained on Midwest corn miss potato, sugar beet, and trout-farm signals in the Magic Valley.
  • Hospital early-warning scores tuned on large coastal hospitals can alarm wrong in a rural Idaho critical-access hospital.
  • A recreation demand model trained on Colorado ski data will misread Bogus Basin weekday patterns and local school calendars.

Hands-on activity

Hands-on — Rebuild the deck

12 min
  1. Pairs receive a biased deck (faces, fires, or crops) and must add public cards to improve representativeness. They also add two non-examples.
  2. They write a 'dataset label' as if they were handing the set to a county IT shop or a Micron intern: source, who is included, known gaps, privacy notes.
  3. Teacher may project a saved failed-match demo. No live scanning of anyone in the room. If Chromebooks are on, students only open the teacher packet PDF.
  4. Two pairs trade decks and try to name a remaining gap in 60 seconds.
  5. Paper packets are the full activity if cards cannot be cut; students circle additions on a printed menu of public examples.

Discussion questions

  1. Why is 'just add more data' not always a fix?
  2. Who should have a say before a school or county trains a face or license-plate tool?
  3. How could a potato model be biased even if every photo is technically 'accurate'?
  4. What is the difference between a missing group and a missing condition (night, smoke, winter)?
  5. Why is using the class as a face dataset a FERPA and ethics failure even if the lesson is about fairness?

Differentiation

Support

  • Give a filled inventory table with one column already completed.
  • Offer a menu of missing examples to circle rather than invent.
  • Allow a poster diagram instead of the four-sentence write.

Challenge

  • Argue when a local-only set can also be biased (too small, too one-farm, too one-season).
  • Add a non-example that prevents a dangerous confusion (smoke vs. fog, bruise vs. dirt).
  • Connect to hiring or lending tools in a short risk paragraph, still without collecting PII.

Multilingual learners

  • Clarify pigment, representativeness, and sampling with visuals before the inventory.
  • Note that language datasets can exclude home languages the same way photo sets exclude skin tones.
  • Allow dataset labels to be bilingual.

IEP / 504

  • Pre-cut cards and limit the rebuild to adding three stickers from a menu.
  • Provide a scribe or speech-to-text on a school account that does not leave the district.
  • Reduce independent practice to one mini-set with sentence starters.

Assessment

Formative

  • Warm-up prediction connecting Envelope A to the standards example.
  • Sticky-note inventory during guided practice.
  • Redesign sheets listing missing examples and a privacy refusal.

Summative

  • Exit ticket: Quote the face-recognition example, then explain in 5–8 sentences how a dataset choice caused the failure and how an Idaho twin (fire, farm, or hospital) could fail the same way.
  • Dataset label scored for source, gap, proposed fix, and privacy constraint.

Success criteria

  • I connected biased output to a specific gap in the training set.
  • I used the face-recognition example accurately.
  • I proposed better examples and non-examples, not just 'more data.'
  • I refused to use student PII or classmate photos as a fix.

Responsible use

Study datasets with public, teacher-provided cards. Do not scrape the web for faces. Do not photograph the class. Do not download a real recognition app onto student phones for this lesson.

Ethics

People who were missing from the data are the people most likely to be misidentified, denied, or ignored. Building a fairer set is a justice task, not a cosmetics task. Consent and dignity beat a slightly better accuracy score.

Privacy

FERPA and basic ethics: no student PII, no classmate or staff face scans, no real patient records, no home addresses in a 'local dataset.' If a district tool is used, stay on the teacher prompt and public samples. Printed packets are the default.

Reflection

  1. Which missing group or condition would have hurt someone I know?
  2. What will I ask the next time a vendor says their model 'works for everyone'?
  3. How will I remember that more data is not the same as representative data?

Homework

On paper, invent a tiny training set (eight labeled examples) for one Idaho task: identifying ripe vs. unripe fruit, spotting a dull weld, or flagging a full campground. List two missing examples and one thing you will not collect because it is private. No photos of people you know.

Closing

Hold Envelope A and Envelope B again. Students finish the stem: 'The dataset decides ___.' Collect redesign sheets. Next hallucination lesson will show a different failure: the model can also invent what was never in the set.

Extensions

  • 90-minute block: students write a one-page data card for a fictional county tool (park cameras, irrigation alerts) including who must consent.
  • Statistics: sample vs. population using Idaho counties, not faces.
  • Biology / environmental science: why California fuel models transfer poorly to Idaho timber.
  • AITA preview: later technical courses will clean and split datasets; this lesson stays on civic judgment.

Cross-curricular links

Statistics
Sampling bias and whether a sample represents the population the model will face.
Civics
Public cameras and recognition tools require policy, not just accuracy claims.
Agriculture
Local crops, irrigation, and pests must appear in training if a model will run in the Magic Valley.
Health Sciences
Clinical scores fail when training hospitals look nothing like rural Idaho sites.

Back to contents

AI Fluency · Evaluation and Critical Thinking

9-12.AIF.ECT.5

Catching Hallucinations

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Recognize when an AI model produces erroneous outputs (i.e., hallucinations).

Example from the standards. An LLM creates a report that cites a document that doesn't actually exist.

Student-friendly learning targets

  • I can define a hallucination as a confident, wrong, or made-up AI output presented as if it were true.
  • I can catch a fake citation, a wrong Idaho fact, and a mixed half-true paragraph in a printed report.
  • I can follow a verification protocol before I trust AI-generated research in school.

Essential questions

  1. Why does wrong output still sound finished and professional?
  2. How can I tell a real source from a made-up one?
  3. What should I do in the first two minutes after an AI tool hands me a report?

Objectives

  1. Students will recognize hallucinations using the standards example of a report that cites a document that does not exist.
  2. Students will fact-check a two-page fake Idaho report using Chromebooks or a printed source bank.
  3. Students will classify errors as invented citation, wrong local fact, outdated fact, or mixed truth.
  4. Students will apply a three-step verification protocol: isolate the claim, find a trusted source, confirm or reject.
  5. Students will explain why fluency and polite tone are not evidence of truth.

Key vocabulary

Hallucination
When an AI system generates information that is incorrect, misleading, or entirely fabricated, but presents it as if it were true.
Citation
A pointer to a source. A hallucinated citation names a paper, law, or article that cannot be found because it was invented.
Fabrication
A made-up detail, quote, statistic, or document presented as real.
Verification
The process of checking a claim against a trusted source before using it.
Primary source
An original record, such as a statute, a hospital policy page, a fire incident report, or a company press page, not a chatbot's summary.
False confidence
Wording that sounds sure ('studies show,' 'according to') even when the model has no reliable basis.
Source bank
A teacher-provided set of real excerpts students can use to check claims when live search is unavailable.

Teacher background

Hallucination is the error students will meet most often in schoolwork: a fluent paragraph with a citation that does not exist. The standards example is exactly that. Ninth- and tenth-graders do not need a research-methods course to catch it if you give them a dirty report and a way to check. Build the fake report from Idaho bait. Invent a University of Idaho white paper, a St. Luke's statistic, an Idaho Code section with a real-looking number, a wildfire with a plausible Sawtooth name, a Micron press claim, and a wrong county seat. Mix in two true lines so students cannot mark the whole page false. Teach a protocol, not a vibe: isolate the claim, find a trusted source, confirm or reject. Chromebooks can search district-approved sites. If the filter wins, the printed source bank is the lab. Never ask students to paste their own research notes into an unapproved model. The goal is a reflex: no citation, no Idaho fact, no 'study' travels into an essay until a human has checked it. Confidence is a style. Truth is a job.

Materials

  • Projector for a teacher demo of one fake citation search
  • Printed two-page fake report: 'Idaho Health, Fire, and Industry Brief'
  • Printed source bank (offline fallback): real snippets from public pages, plus a list of known fakes
  • Claim-check table: Claim / Source tried / Real, Fake, or Unsure
  • Optional Chromebooks with access to search or library databases
  • Highlighters and exit tickets

Before class

  • Write the fake report with at least six checkable claims: two true, four false (including one invented document, matching the standards example).
  • Assemble the source bank so a student with no Wi-Fi can still complete the table.
  • Test which sites the school filter allows. Bookmark the Idaho Legislature, a hospital public page, and InciWeb or IDL fire info if reachable.
  • Prepare a teacher search of the fake citation on the projector. Practice showing zero real results without joking students into distrusting all libraries.

Instructional sequence

Warm-up — True, false, or fluent?

5 min
  1. Read three short 'Idaho facts' from the packet. One is true, one is wrong, one cites a paper that does not exist.
  2. Students vote with fingers: 1 true, 2 false, 3 cannot tell yet.
  3. Do not give answers. Tell them the hour is about earning the right to answer.

Direct instruction — Fluent is not true

8 min
  1. Define hallucination using the glossary idea: wrong or fabricated, presented as true.
  2. Put the standards example on the board: a report that cites a document that does not exist.
  3. Teach the three-step protocol: isolate, source, confirm or reject. Model it on the fake citation.
  4. Warn about mixed paragraphs: a real hospital name plus a fake statistic is still a hallucination in the number.

Guided practice — Check one citation together

8 min
  1. Project the invented University of Idaho title. Teacher searches (or opens the source bank page that lists it as not found).
  2. Fill row 1 of the claim-check table as a class.
  3. Ask why 'University of Idaho, 2022' felt believable. Name false confidence.

Independent practice — Six-claim table

10 min
  1. Students complete the remaining claims: county seat, Idaho Code, St. Luke's number, wildfire name, Micron sentence, one true recreation fact.
  2. Chromebook path: search approved sources. Paper path: use the source bank only. Both paths must fill Real / Fake / Unsure plus a reason.
  3. No student may mark Unsure on more than two claims without writing what they would try next.

Real-world examples

  • A generated policy brief cites an Idaho Code section that does not exist; a county clerk who pastes it could mislead a contractor.
  • A student paper invents a St. Luke's or Kootenai Health study; the hospital never published it.
  • A wildfire roundup names a 'Sawtooth Complex' on a date when that incident did not exist, which can panic families.
  • A career report quotes a Micron 'press release' with a fake hiring number.
  • A recreation blog post cites a Parks and Recreation rule about campfires that is not the actual restriction in effect.

Hands-on activity

Hands-on — Red-team the brief

14 min
  1. Pairs finish the six-claim table, then write a three-sentence 'editor's note' that a human would attach before the brief could be published.
  2. They star the standards-style error: the citation to a document that does not exist.
  3. Teacher projects one live search if the network is up. If not, pairs use only the printed source bank. The product is the same table.
  4. Swap packets with another pair. The second pair tries to catch a miss.
  5. Class debrief: which fake was most believable, and which check was fastest?

Discussion questions

  1. Why do fake citations often include a university, a year, and a plausible title?
  2. Is an outdated fire restriction a hallucination, sloppiness, or both?
  3. What is the danger of using a chatbot as the only source for a health or legal claim?
  4. How should a trades student treat a generated torque spec that 'sounds right'?
  5. When is Unsure the honest and responsible box to check?

Differentiation

Support

  • Number the claims and provide the source-bank page number beside each.
  • Allow a partner reader. Reduce to four claims if needed.
  • Give a stem: 'I reject this because the source bank shows ___.'

Challenge

  • Find the mixed-truth sentence and split it into a true part and a fake part.
  • Write a replacement paragraph that is fully sourced from the bank.
  • Explain why asking the same model 'are you sure?' is not verification.

Multilingual learners

  • Pre-teach citation, statute, and incident. Allow the editor's note in the stronger language plus an English gist.
  • Pair for search terms. Offer a list of English proper nouns from the report.
  • Clarify that fluent English is the trap, not a proof of correctness.

IEP / 504

  • Large-print report. Let students highlight first, then fill the table.
  • Speech-to-text on a school account is fine; a public chatbot is not.
  • Accept bullet editor's notes. Reduce swapping if social load is high.

Assessment

Formative

  • Warm-up votes compared with later corrected answers.
  • Claim-check tables during circulation.
  • Peer catch during packet swap.

Summative

  • Scored table plus editor's note. Credit for catching the nonexistent document and at least two other errors.
  • Exit ticket: Define hallucination, quote the standards example in your own words, and list the three protocol steps.

Success criteria

  • I found at least one citation that points to nothing real.
  • I did not treat tone or formatting as proof.
  • I used a source other than the chatbot to confirm or reject.
  • I left Unsure only when I also named a next check.

Responsible use

Use the dirty report as a teaching tool, not as a source to copy into other classes. Do not paste the fake brief into a public model and ask it to 'fix the citations,' which can generate new fakes. Verify outside the model.

Ethics

Publishing a hallucinated fire, hospital, or hiring claim can scare families and stain institutions. Catching hallucinations is a civic duty, not only an academic-integrity rule. Unsure is more ethical than a confident guess.

Privacy

FERPA: no student PII in unapproved tools. Do not paste student research with names, health stories, or family details into unapproved tools for 'fact checking.' Use the class report and public sources. School accounts and library databases only.

Reflection

  1. Which fake almost got past me, and what made it look real?
  2. Where will I refuse to use AI as a source in my other classes?
  3. What is my personal two-minute check before I trust a generated citation?

Homework

On paper, write three claims a student might be tempted to take from a chatbot for a history or science paper. For each, name a trusted place to check (textbook, .gov page, library database) and one red flag (too-perfect title, no author, round statistic). Do not generate new text in an unapproved tool.

Closing

Reveal the warmup answers. Students chorus: 'Fluent is not true.' Collect tables. Preview sensory grounding next: some errors happen because the model never smelled smoke or stood in the shop.

Extensions

  • 90-minute block: students write a clean one-page brief using only the source bank, with real citations.
  • Library collaboration: practice database search vs. chatbot search on the same question.
  • Government: verify a generated summary of a public Idaho statute against the actual text.
  • Journalism: compare a hallucinated quote with how a real reporter attributes speech.

Cross-curricular links

English Language Arts
Research writing: every citation must be retrievable. Invented sources fail the assignment.
Science
Lab claims need data, not a generated 'study shows' clause.
Government
Generated law is not law. Check the Idaho Code or the agency page.
Health
Invented clinic statistics can spread fear; verify against the health system or public health district.

Back to contents

AI Fluency · Evaluation and Critical Thinking

9-12.AIF.ECT.6

Senses vs. Statistics

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Give examples of how humans combine information from different bodily sensory inputs to make sense of the world, and compare that to how AI models learn about the world.

Example from the standards. LLMs largely learn from text written by humans, whereas humans use vision, olfactory, haptics, geolocation, etc., to ground their understanding of the world.

Student-friendly learning targets

  • I can give examples of humans combining sight, sound, smell, touch, and location to make a judgment.
  • I can compare that grounding to how an LLM mainly learns from human-written text.
  • I can explain why a text-only model can miss a shop, fireline, barn, or river reality that a person would notice.

Essential questions

  1. How do my senses work together when I decide something is safe, ripe, or off?
  2. What does an LLM actually 'know' if it mostly learned from text?
  3. When must an Idaho worker trust a body on the ground more than a generated description?

Objectives

  1. Students will list multiple human sensory inputs and show how they are combined in one grounded judgment.
  2. Students will compare that process to LLM learning from text, using the standards example.
  3. Students will complete a two-station activity: text-only description vs. multi-sense scenario cards.
  4. Students will write a comparison paragraph for a welder, nurse, rancher, river guide, or firefighter.
  5. Students will identify a school or work task that should not be decided from text statistics alone.

Key vocabulary

Sensory input
Information the body takes in through senses such as vision, hearing, smell, taste, touch, balance, and a sense of where you are.
Grounding
Tying words and ideas to the real world through experience, senses, and location, not only through other words.
Haptics
Touch and pressure information, such as the feel of a weld bead, a pulse, wet snow, or a too-hot pipe.
Olfactory
Smell information, such as smoke type, a sour silage pile, overheating electrical gear, or a fuel leak.
Geolocation
Knowing where you are in space: slope, aspect, river mile, GPS pin, or which end of the mill you are standing in.
Multimodal
Using more than one kind of signal (text, image, audio, sensor). Humans are multimodal by default; many LLMs are still text-first.
Large Language Model (LLM)
A model that largely learns from text written by humans and predicts likely next words, without a body in the world.
Embodiment
Having a body that senses and acts. Humans are embodied; a chatbot is not, even if it describes bodies well.

Teacher background

The standard is comparative and concrete. Humans combine bodily senses to make sense of the world. AI models, especially LLMs, largely learn from text written by humans. That is the official example, and it is enough. Do not turn the hour into a neuroscience lecture or a robotics unit. Ninth- and tenth-graders already know that smoke smells different from a burn pile, that a weld can look fine and feel wrong, that a patient can say they are fine while their color is not. Put those moments next to a paragraph an LLM could have written from forum posts. The model has statistics about the words 'wildfire,' 'pulse,' and 'ripe.' It has not stood in ash wind on the Payette, felt a thready pulse at St. Alphonsus, or walked a rutted pivot track at dawn. Some newer systems add images or sensors; still, the school-facing tools students meet are text-first, and even camera models lack smell, ache, and responsibility. Use a text-only station and a multi-sense card station. Paper packets carry the lab if you cannot set out objects. End with humility: language models are powerful readers of our writing, not stand-ins for a body on the ground.

Materials

  • Projector and a short text-only wildfire or shop description
  • Printed fake-output packet: LLM-style text vs. human sense log
  • Optional object box for a safe haptic demo (sandpaper, cold pack, citrus peel) if policy allows; otherwise paper-only sense cards
  • Station cards: firefighter, ER nurse, dairy operator, welder, river guide, ski patroller
  • Chromebooks optional for a teacher-projected text generation; not required
  • Comparison chart handout

Before class

  • Print sense-log sheets with columns: Vision, Sound, Smell, Touch, Location, Judgment.
  • Write a text-only LLM paragraph that sounds expert on wildfire but misses wind on the face, grit in the teeth, and the smell of pitch.
  • If using objects, choose items with no allergens your nurse has flagged. Default to paper cards if unsure.
  • Save a screenshot of a text-only model answering 'How do you know the fire is making uphill run?' as the offline demo.

Instructional sequence

Warm-up — Mystery judgment

5 min
  1. Read a three-sentence text-only description of a shop hazard. Students vote safe or not safe.
  2. Reveal the missing haptic and olfactory clues from the card (hot pipe, ozone smell). Revote.
  3. Ask what the first vote was missing that a body would have had.

Direct instruction — Bodies combine; models count words

10 min
  1. List human inputs: vision, hearing, smell, taste, touch/haptics, balance, geolocation. Students add one Idaho example each.
  2. Read the standards example aloud. Translate: LLMs largely learn from text; humans ground meaning with senses.
  3. Diagram two stacks: Human (many senses at once) vs. LLM (text in, likely text out). Mention cameras and sensors exist, but school chat tools are still text-first.
  4. Tie to responsibility: a river guide who 'reads' the Salmon is not doing the same thing as a model summarizing trip reports.

Guided practice — Fill the sense log together

8 min
  1. Project the dairy-parlor card: visual (cow's ear set), sound (off rhythm), smell, haptics (heat, swelling), location (which pen).
  2. Class completes one combined judgment: call the vet vs. wait.
  3. Contrast with an LLM paragraph that only restates generic 'monitor livestock health' advice.

Independent practice — One job, two columns

8 min
  1. Each student picks welder, nurse, firefighter, river guide, or ski patroller.
  2. Left column: three sensory combinations a human uses. Right column: what an LLM trained on text might say instead.
  3. They star one judgment they would not let a text model make alone.

Real-world examples

  • A firefighter combines smoke color, wind on the skin, radio traffic, and slope underfoot; a text model has trip reports and news stories.
  • An ER nurse combines skin color, breathing sound, a patient's joke, and a monitor number; the chart bot has only the typed notes.
  • A welder feels the puddle through the glove and hears the right sizzle; a generated procedure has sentences about amperage.
  • A river guide on the Salmon reads water noise, air temp, and the boat's vibration, not only a flow-rate number on a site.
  • A dairy operator smells a sour note and feels a hot quarter; a text alert may only flag a missing milk weight.

Hands-on activity

Hands-on — Text station vs. sense station

14 min
  1. Station A (text-only): pairs read the printed LLM wildfire paragraph and list what they still do not know.
  2. Station B (multi-sense cards): pairs complete a sense log for the same event using vision, olfactory, haptics, and geolocation clues.
  3. They write a four-sentence comparison that quotes the idea in the standards example.
  4. Teacher may project a live text-only answer if the district tool is up. Objects are optional. Paper cards are enough when labs are not.
  5. If movement is hard, both stations live in the packet as page A and page B. No student PII and no recording of classmates' bodies.

Discussion questions

  1. Which sense would you least want to give up on a fireline, in a shop, or in a clinic?
  2. Can adding a camera to a model replace smell and touch? Why or why not?
  3. Why might an LLM sound more certain than a tired human who was actually there?
  4. Where should school assignments still require a lab, a shop, or field notes instead of a generated description?
  5. How does geolocation change a weather or fire judgment in the mountains vs. the valley?

Differentiation

Support

  • Provide a labeled body diagram to tap when naming senses.
  • Give sentence frames for the comparison paragraph.
  • Allow the independent job column to be completed with the dairy example already modeled.

Challenge

  • Argue whether a multimodal model with cameras and GPS is closer to a human, and still list what it lacks (ache, fear, duty).
  • Write a shop-safety paragraph that a text model could not have grounded.
  • Connect to ECT.5: some hallucinations happen because words are ungrounded.

Multilingual learners

  • Teach olfactory, haptics, and geolocation with gestures and sketches before the stations.
  • Invite home-language sense words (smell of rain on dust, names for snow types) as evidence of human grounding.
  • Accept a bilingual sense log.

IEP / 504

  • Do not require handling objects. Cards and words are a full alternative.
  • For sensory sensitivities, skip smell items and use vision plus location only.
  • Allow a typed or scribed comparison. Keep stations quiet if needed.

Assessment

Formative

  • Warm-up revote and the class dairy log.
  • Two-column independent job sheet.
  • Station comparison sentences.

Summative

  • Paragraph: Give two human sensory-combination examples and compare them to how LLMs learn from text, using Idaho work or recreation.
  • Exit ticket: Finish 'Humans ground meaning with ___. LLMs largely learn from ___.' and name one task that needs a body on site.

Success criteria

  • I named more than one human sense working together.
  • I accurately described LLMs as largely text-trained, matching the standards example.
  • I showed a judgment a person could make that a text model would miss.
  • I did not claim the chatbot has a body or feelings.

Responsible use

Do not ask a model to diagnose a real person or to 'be' a firefighter. Compare public, teacher-made texts. Students should not upload photos of their faces or homes to prove a sensory point.

Ethics

Ungrounded systems can still be useful as drafts. They become unethical when someone treats a paragraph as if it had been on the fireline, in the barn, or at the bedside. Human senses carry duty; generated text does not.

Privacy

FERPA: no student PII in unapproved tools. No student health details, no photos of identifiable students, no home GPS pins in prompts or packets. Sense logs use role cards, not real patients or family members. Unapproved tools stay off this lab.

Reflection

  1. When did my senses change a decision that words alone would have missed?
  2. What would an LLM get wrong about a place I know well?
  3. Which school task should stay embodied even though a paragraph could be generated?

Homework

On paper, sit somewhere safe for ten minutes (porch, shop door, kitchen). Log five sensory notes and one judgment they support. Then write four sentences comparing your log to what a text-only model might have written about that place. No photos of people. No AI tool required.

Closing

Re-read the standards example. Students tap the desk for haptics, point to the map for geolocation, and point to the packet for text. Collect logs. Next lesson: agents that take actions, still without a body and still in need of a human goal.

Extensions

  • 90-minute block: add a third station with a map and wind arrow so geolocation becomes visible, then rewrite the LLM paragraph with sensory gaps labeled.
  • Outdoor education or ag: field notes that require five senses before any generated summary is allowed.
  • Health sciences: vital signs plus 'how the patient looks and smells' as a human-in-the-loop check.
  • Physics / shop: vibration and heat as data humans feel before a sensor log is even opened.

Cross-curricular links

Biology
Sensory systems and the brain combining signals, kept at a 9–10 level.
English Language Arts
Imagery in writing vs. ungrounded generated description.
Skilled and Technical Sciences
Why a procedure on paper is not a substitute for feel, sound, and smell in a shop.
Geography / Outdoor Ed
Geolocation, aspect, and microclimate as bodily and map knowledge a text model only fakes.

Back to contents

AI Fluency · Evaluation and Critical Thinking

9-12.AIF.ECT.7

What an Agent Actually Does

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Recognize and understand how AI agents can accomplish a defined task.

Student-friendly learning targets

  • I can describe an AI agent as a system that pursues a defined task by planning, using tools, checking, and looping, not as a magic person.
  • I can trace a printed agent log and mark goal, plan, tool call, result, and human approval.
  • I can tell a task an agent could attempt from a task that still needs a human on site.

Essential questions

  1. What is the difference between a chatbot that answers and an agent that does steps?
  2. What has to be defined before we let a system act?
  3. Where must a human stay in the loop when an agent books, orders, alerts, or files?

Objectives

  1. Students will define an AI agent using goal, plan, tools, checks, and loops in student language.
  2. Students will label those parts on a fake agent log for an Idaho task.
  3. Students will simulate an agent on paper with tool cards and a human approval gate.
  4. Students will judge whether a task is defined enough to attempt and what failure looks like.
  5. Students will contrast agents with ordinary chatbots and with fully human workflows.

Key vocabulary

AI agent
A system designed to pursue a defined task by planning steps, using tools or apps, checking results, and adjusting, with more action than a single chatbot reply.
Defined task
A job with a clear goal, limits, and a way to tell when it is done, such as 'find three open campsites under $40 on Friday' rather than 'plan a great trip.'
Tool use
When an agent calls another system, such as a calendar, search, form, or inventory list, instead of only generating a paragraph.
Plan-act-check loop
The cycle of making a plan, taking a step, reading the result, and deciding the next step or stopping.
Human-in-the-loop
A required human review or approval before the agent sends, spends, alerts, or files.
Automation
Using technology to carry out steps with less hands-on work. An agent is one form; a dishwasher is another.
Guardrail
A limit on what the agent is allowed to do, such as 'do not submit the permit' or 'do not spend money.'

Teacher background

ECT.7 is recognition and understanding, not a build project. Application standard AP.3 will ask students to construct agents later. Here, ninth- and tenth-graders need a clear picture of how an agent accomplishes a defined task: a goal, a plan, tools, a check, and a loop, with a human still holding the halt sign. A chatbot answers. An agent tries to do. That difference is the whole hour. Keep examples local. A county IT helpdesk agent can reset a password queue. An Idaho Parks agent can look for a campsite. A hospital discharge agent can assemble a checklist. An irrigation agent can draft a pivot schedule. An HVAC shop agent can search a parts catalog. None of them should click Submit, spend money, or page a crew without a person. Students will over-anthropomorphize ('it wanted to help'). Push them back to logs: tool called, result returned, next step. Use a teacher-projected demo if a district agent tool exists; otherwise a printed fake log is better than a flashy video. Paper tool cards let every table simulate the loop on Chromebooks or with no devices at all. End with a defined-task test: if you cannot write the finish line, you are not ready to let a system act.

Materials

  • Projector and a saved or live teacher demo of a harmless agent-style log (search, then draft, then wait)
  • Printed fake-output packet: agent log for a campsite search and a messy, undefined 'make it nice' task
  • Tool cards: Search calendar, Check fire restriction, Inventory lookup, Draft email, Submit form, Halt for human
  • Role cards: Agent, Tool, Human approver, Auditor
  • Optional Chromebooks; paper simulation is the core
  • Exit tickets

Before class

  • Print logs with obvious steps and one bad action the human must catch (agent about to submit a permit or charge a card).
  • If no district agent tool exists, do not improvise on a public site. Use the printed log as the demo.
  • Pre-cut tool cards. Include a bright Halt card in every deck.
  • Write two task prompts on the board: Defined (campsite constraints) and Fuzzy (plan a cool weekend).

Instructional sequence

Warm-up — Answer vs. do

5 min
  1. Read two outputs. A: a paragraph about how to reserve an Idaho state park site. B: a log that searched dates, compared three sites, and paused for a human to confirm.
  2. Students label A Chat and B Agent on the packet.
  3. Ask what B did that A did not, and what B still must not do.

Direct instruction — Goal, plan, tools, check, loop

10 min
  1. Write the five-part skeleton. Defined task goes above it. Guardrails go beside it. Human halt sits at the end of every loop.
  2. Walk the printed campsite log. Circle each tool call. Cross out the illegal Submit the agent almost made.
  3. Contrast a fuzzy task ('plan a great weekend') that an agent cannot finish because success is undefined.
  4. Name Idaho twins: county password reset, hospital checklist, irrigation draft, HVAC parts search. All need a named approver.

Guided practice — Label the log

8 min
  1. As a class, color-code the second log: goal, plan, tool, result, human gate.
  2. Find the step where the agent exceeded the guardrail (spent money, emailed a patient, filed a permit).
  3. Rewrite the guardrail in eight words or fewer.

Independent practice — Defined or not?

8 min
  1. Students sort six task slips: county records request, 'help Grandma,' irrigation set points for field 4, 'fix the mill,' hospital discharge checklist, 'make practice fun.'
  2. For each defined task they add a guardrail. For each fuzzy task they write what would have to be specified.
  3. They star one task that should stay fully human even if it could be specified (for example, telling a family a diagnosis).

Real-world examples

  • Idaho Parks: an agent can search open campsites and list fees; a human confirms fire restrictions and hits reserve.
  • County IT: an agent can triage ticket categories; a technician still resets access for a deputy or a clerk.
  • Hospital: an agent can assemble a discharge checklist from a template; a nurse still teaches the patient.
  • Agriculture: an agent can draft pivot run times from weather data; the grower still walks the field for a plugged nozzle.
  • Trades: an HVAC agent can find a compatible part number; the technician still verifies the unit tag before ordering.

Hands-on activity

Hands-on — Tabletop agent, Halt card required

14 min
  1. Groups of four: Agent, Tool, Human approver, Auditor. They draw a defined Idaho task from the packet.
  2. The Agent may only act by playing a tool card. The Tool returns a printed result slip (including one error slip in the deck).
  3. After two loops the Agent must request Halt. The Human either approves a draft, demands another check, or shuts the task down.
  4. The Auditor writes the log: goal, steps, tools, error, final human decision. No group is allowed to 'Submit' without the Halt card.
  5. Teacher projects a live agent demo only on a district-approved tool with a harmless search. If none exists, the printed log is the demo. Chromebooks are optional note sheets, not required.

Discussion questions

  1. What made a task defined enough to attempt?
  2. Which tool card was most dangerous if the human fell asleep?
  3. How is an agent different from a dishwasher, a thermostat, or a chatbot?
  4. Should a school agent ever email families without a staff click? Why or why not?
  5. What error in the deck was most like a hallucination from ECT.5, and who had to catch it?

Differentiation

Support

  • Pre-label the first two log lines. Give a script for the Agent role.
  • Limit the simulation to one loop plus Halt.
  • Offer a word bank: goal, tool, result, approve, stop.

Challenge

  • Add a second agent that must hand off to the first, and write the interface a human still owns.
  • Design a guardrail for money, medical, or legal actions in one sentence each.
  • Explain why AP.3 (constructing agents) will need this recognition first.

Multilingual learners

  • Act out tool, halt, and approve with gestures before the simulation.
  • Allow the auditor log in bilingual bullets.
  • Pre-teach agent vs. chatbot with the warmup pair of outputs.

IEP / 504

  • Assign Auditor or Human if rapid talk is a barrier; still require one spoken Halt.
  • Provide a large Halt card and a one-page log template.
  • Allow a quieter pair simulation instead of four roles.

Assessment

Formative

  • Warm-up Chat vs. Agent labels.
  • Color-coded logs and the defined/fuzzy sort.
  • Auditor sheets from the tabletop run.

Summative

  • Exit ticket: In 6–8 sentences, explain how an AI agent accomplishes a defined Idaho task, using goal, tool, check, and human halt. Include one task you would not delegate.
  • Packet log scored for correct labels and a refused Submit.

Success criteria

  • I described an agent as a loop with tools, not as a person.
  • I used a defined task with a finish line and a guardrail.
  • I required a human halt before send, spend, or file.
  • I named a task that should stay human even if a system could attempt it.

Responsible use

Simulate on paper. Do not connect student accounts to third-party agents that can send mail or spend. If a district tool can take actions, the teacher holds the login and the class watches a harmless search only.

Ethics

Action raises the stakes above chat. An agent that files, alerts, or orders can harm people faster than a wrong paragraph. Defined tasks, guardrails, and a named human are ethical requirements, not extras. Do not treat the agent as a coworker who 'meant well.'

Privacy

FERPA: no student PII in unapproved tools. Agents that can see inboxes, calendars, or student information systems are high risk. Do not paste names, IDs, schedules, or health data into unapproved agent tools. Use fictional tickets in the packet. School accounts only, and only if the district has approved that agent.

Reflection

  1. Where did our table want the agent to 'just finish,' and why was that a trap?
  2. What guardrail would I demand at a job I actually want?
  3. How will I tell a chatbot from an agent the next time a product page uses both words?

Homework

On paper, write one defined task an agent could attempt in an Idaho job you know (farm, shop, clinic, park, county office, home). List the goal, two tools, one check, one guardrail, and the human who must Halt. Then write one nearby task that must stay human. No live agent accounts.

Closing

Hold the Halt card up as a class. Repeat: defined task, tools, check, human. Collect auditor logs. Point forward to AP.3, where they may construct a tiny agent only after they can recognize what one is actually doing.

Extensions

  • 90-minute block: run a second simulation with a planted tool error and write a post-incident note from the Auditor.
  • CTE: map an HVAC or ag workflow into steps an agent might draft vs. steps a licensed person must perform.
  • CS preview: storyboard an agent without writing code; AP.3 will build later.
  • Civics: draft a three-rule policy for a county chatbot that is not allowed to become an agent on permits.

Cross-curricular links

Computer Science
Algorithms as steps with a stop condition; agents add tools and loops around those steps.
Business / Personal Finance
An agent that can spend is a debit card with a language model. Guardrails first.
Health Sciences
Checklists can be assembled by a system; teaching, consent, and discharge remain human.
Government
Public agencies may use agents to sort, not to issue licenses or deny benefits without a person.

Back to contents

AI Fluency · Application

9-12.AIF.AP.1

A Second Reader, Not a Ghostwriter

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Use an AI tool to critique student work.

Example from the standards. A student can use AI to ask for editorial feedback on a written assignment and make use of that to improve their writing.

Student-friendly learning targets

  • I can ask a district-approved AI tool for editorial feedback on writing I already drafted, without asking it to write the piece for me.
  • I can compare human feedback and AI feedback on the same draft and decide what to keep, change, or reject.
  • I can follow this class's academic-integrity protocol and FERPA rules so I never upload another student's work or anyone's personal information.
  • I can record how I used AI critique so a teacher, parent, or future employer can see that the thinking is still mine.

Essential questions

  1. When does a second reader help my writing, and when does it start doing the writing for me?
  2. What does AI critique notice that a classmate or teacher might miss, and what does it get wrong?
  3. Who is responsible for the words that go out under my name?
  4. What information about me or my classmates must never go into an AI tool?

Objectives

  1. Students will submit a draft they wrote before class and use a critique-only prompt (or an offline critique checklist) to request editorial feedback.
  2. Students will complete a human-versus-AI feedback comparison on their own work, citing at least one keep, one change, and one reject with a reason.
  3. Students will apply the posted academic-integrity protocol, including disclosure of the tool and date.
  4. Students will strip names, student IDs, school names, and other PII from any text before it is pasted into a tool.
  5. Students will revise at least one sentence of their own draft based on a decision they can explain, not on automatic acceptance of AI suggestions.

Key vocabulary

Critique
Specific feedback on strengths and weaknesses of work that already exists, offered so the author can decide what to change. Critique is not a rewrite and is not a grade.
Ghostwriter
A person or tool that produces the writing that will be turned in under someone else's name. In this lesson, using AI as a ghostwriter is not allowed.
Human-in-the-loop
A model of interaction where a human is required to participate in a process, such as verifying, approving, or correcting, to ensure the accuracy, safety, and ethical alignment of AI-generated outcomes.
Personally Identifiable Information (PII)
Information that can be used to identify a specific person, such as a name, home address, phone number, email address, or student ID number.
Academic integrity
Doing your own thinking and giving honest credit for help. In this lesson it means drafting first, asking for critique rather than a rewrite, deciding what to take, and disclosing the tool you used.
Prompt
The instructions you give an AI tool. A critique prompt asks for feedback on a draft. A ghostwriter prompt asks the tool to produce the assignment.

Teacher background

Idaho standard 9-12.AIF.AP.1 is an application standard for grades 9–10: students use AI to critique work they already made. The standards document example is exact: a student asks for editorial feedback on a written assignment and makes use of that feedback to improve the writing. The pedagogy is non-negotiable. Students must bring a draft that existed before the AI step. If the chatbot writes the paper, the standard has not been met, and academic integrity has been broken. Treat the AI as a second reader sitting beside a human reader, not as the author. Build a visible human-versus-AI comparison so students practice judgment instead of copying suggestions. District-approved tools only; if the network is down or the tool is not approved, the printed critique checklist is the lesson, not a consolation prize. FERPA: student writing that includes a name or other identifiers is an education record. Never paste a classmate's work into any tool. Never put student ID numbers, addresses, phone numbers, or photos into a prompt. Use a public sample (not a student's paper) whenever you model on a projector. This lesson sits in Semester 1, Weeks 5–9 (pacing unit 'Think with it, not for it') next to cognitive-offloading and hallucination work, so pair generation with verification and hold the integrity conversation before high-stakes writing season.

Materials

  • Student drafts written before this class (printed or digital). Collect a reminder two days prior. Do not allow 'I will have the chatbot write it now.'
  • Backup public sample paragraph about an Idaho place or event (Craters of the Moon, a Snake River flood year, a school garden) for absentees only; they treat it as practice and apply the protocol to their real draft as homework.
  • Posted Academic Integrity Protocol poster (eight steps, see prep).
  • District-approved AI writing tool, teacher account for the model; student accounts only if the district data-privacy agreement allows them.
  • Printed Critique Checklist (offline fallback and required companion even when the tool is online): claim, evidence, organization, word choice, one confusing sentence, one strength.
  • Human vs. AI Feedback T-chart (three columns: Human said / AI said / I keep, change, or reject because).
  • Revision log slip: tool name, date, three decisions, one revised sentence.
  • PII strip card: names, school, teacher, student ID, email, phone, address, photos — black these out before any paste.
  • Timer and document camera or projector for the teacher model only.
  • Optional: sticky notes for the warm-up pair of comments.

Before class

  • Two school days before: remind students in class and in the learning-management system to bring a draft they already wrote for English, history, agriculture, or any other course. Name the rule: no draft, no AI step.
  • Confirm the district-approved tool and whether student logins are allowed. If not, run all live AI through the teacher account on a sample, and have students use the printed checklist on their own drafts.
  • Print enough Critique Checklists, T-charts, revision logs, and PII strip cards for the roster plus extras.
  • Post the Academic Integrity Protocol: (1) Draft first, without AI. (2) Use only your own work. (3) Strip all PII. (4) Prompt for critique, never 'rewrite this essay.' (5) Get one human reader (peer or teacher) on the same draft. (6) You decide keep / change / reject. (7) Disclose tool and date. (8) Never upload another student's work.
  • Prepare the public sample you will project. It must not be a current student's paper. Strip any leftover names.
  • Prepare two warm-up comments on that sample: one generic ('make it flow better') and one specific ('your second sentence names the lava, but the next three sentences repeat 'then we walked' without a new image').
  • Offline plan: if the filter blocks the tool, teach the whole period on paper. The standard is still met if students critique with the checklist, compare with a human reader, and decide what to take.
  • 90-minute block: keep this sequence. Add about 20 minutes to the human-versus-AI comparison (full peer read-aloud plus written rationale) and about 15 minutes to discussion and reflection. Do not add a second AI generation task.

Instructional sequence

Warm-up — Which comment would you actually use?

5 min
  1. Project the public sample paragraph (Idaho place or event). Do not use a student's paper.
  2. Read two comments aloud. Comment A is vague and could have come from anywhere. Comment B names a sentence and a fix.
  3. Students vote with fingers: 1 for A, 2 for B. Cold-call two students to say which comment they would act on and why.
  4. Name the day's claim: a second reader is useful when the feedback is specific and the writer still decides. AI can be that reader. It cannot be the ghostwriter.

Direct instruction — Critique protocol, modeled on a public sample

10 min
  1. Read the standard aloud exactly: 'Use an AI tool to critique student work.' Read the example exactly: 'A student can use AI to ask for editorial feedback on a written assignment and make use of that to improve their writing.'
  2. Walk the eight-step Academic Integrity Protocol on the wall. Pause on step 2 and step 8: never paste a classmate's draft into a tool, even to 'be helpful.'
  3. Show the PII strip card on the sample. Cross out any name, school, or teacher. Say: FERPA treats student work with identifiers as an education record. This class does not put education records into unapproved systems.
  4. Contrast two prompts on the board. Ghostwriter: 'Write a five-paragraph essay about Craters of the Moon for English 9.' Critique: 'I already wrote this draft. Do not rewrite it. Name one strength, then give three specific editorial suggestions about evidence, organization, or word choice. Quote the sentence you mean. Keep my voice.'
  5. If the approved tool is available, run the critique prompt on the public sample from the teacher account. If not, read a printed set of critique notes you prepared earlier on that same sample. Label them 'AI-style notes' so students see the genre.
  6. Think aloud on one suggestion you would reject ('it asked me to add a statistic I do not have') and one you would take ('it caught that I used 'then' four times'). The human decides.

Guided practice — Build the class critique prompt and a human first-read

10 min
  1. In pairs, students write one sentence they want the second reader to focus on (for example: 'Does my claim about irrigation actually match the example in paragraph two?').
  2. Harvest three of those sentences and fold them into a class critique prompt on the board. Required lines: 'This is my draft. Do not rewrite it. Do not add new facts I did not write. Point to sentences.'
  3. Human first-read: pairs swap their own drafts (paper or screen, not into AI). Each reader has three minutes to mark one strength and one confusing sentence on the Critique Checklist. They return the paper to the author. No one types another person's sentences into a tool.
  4. Check for PII: authors look at their own draft and black out their name, header, and any friend names before the AI step.
  5. Show where the T-chart will go: left column is the human reader, middle is AI, right is the author's decision.

Independent practice — AI (or checklist) critiques my draft; I decide

12 min
  1. Students who have a pre-written draft and an approved tool paste only the stripped draft plus the class critique prompt. They are not allowed to add 'now rewrite the whole thing.'
  2. Students without network access, without an approved login, or whose draft is on paper only use the printed Critique Checklist as the 'AI-style' second reader. They still complete the T-chart using the checklist in the middle column.
  3. Absentees who brought no draft use the public sample for practice only and note on the revision log 'practice sample — will apply to my draft tonight.'
  4. Every student records three decisions on the T-chart: one keep, one change, one reject, each with a because-clause. Example reject: 'It told me to cite a 2021 DEQ report I never read, so I will not add it.'
  5. Students revise one sentence in their own handwriting or typing. The revision must be something they can explain to a neighbor in twenty seconds.

Real-world examples

  • An FFA officer at Filer or Minico High asks a district chatbot to flag unclear transitions in a prepared public-speaking draft, then sits with the advisor and keeps only the notes that match the actual speech time limit.
  • A reporter at a local Idaho paper runs a style checker on a draft about a county commission meeting, then verifies every name and vote against the minutes because the checker cannot attend the meeting.
  • A safety coordinator at a Magic Valley processing plant uses AI to mark confusing steps in a lockout procedure, then a supervisor who has done the job on the floor decides what language stays.
  • A 10th grader writing a college-prep personal statement about working a harvest uses AI to catch repeated words, then rejects a suggestion to add a 'life lesson' the student does not believe.
  • An English 9 teacher in Idaho Falls gives the same protocol for a narrative about the Greenbelt: AI may comment; it may not invent a memory of Boise the student does not have.

Hands-on activity

Hands-on — Human vs. AI T-chart, then one defended revision

8 min
  1. Students finish the three-column T-chart. If a cell is empty, they must write 'none' and say why, not leave it blank.
  2. Stand-up pair share: 45 seconds each. Prompt: 'One piece of AI feedback I rejected, and why the human reader was more useful — or the reverse.'
  3. Spot-check: teacher collects three revision logs at random (names already on the log; drafts themselves are not uploaded). Look for a because-clause, not just 'I fixed it.'
  4. Block extension (90 minutes): add a second human reader from a different class period's protocol (still no AI on anyone else's work), then a short gallery of anonymous 'reject' reasons on the board. Discuss whether AI flatters the writer more than a classmate does.

Discussion questions

  1. If the AI praise is always glowing, how should that change how much you trust the critique?
  2. When would a teacher, a parent, a shop boss, or a teammate be a better second reader than a chatbot?
  3. What is the difference between using AI to notice a repeated word and using AI to invent a story you did not live?
  4. Why is pasting a classmate's paper into a tool a FERPA and integrity problem even if you 'only wanted to help'?
  5. How will you disclose AI critique on the next paper in this class so the credit is honest?
  6. What happens to your writing muscle if every draft is born inside a chatbot?

Differentiation

Support

  • Provide sentence stems on the T-chart: 'The human reader said ___. The AI said ___. I will ___ because ___.'
  • Allow a partner to read the student's draft aloud while the author marks the checklist; the partner still never types that draft into AI.
  • Offer a shorter critique prompt that asks for only one strength and one suggestion.
  • Accept the revision as an oral explanation recorded by the teacher if writing output is the barrier, not the thinking.

Challenge

  • Find one claim in the AI critique that is a hallucination (a source, fact, or quote the draft never contained) and document it on the revision log.
  • Write a one-paragraph memo to a younger student: when to use AI as a reader and when to close the tab.
  • Compare two critique prompts on the same public sample (not a peer's paper) and explain which produced more usable feedback.

Multilingual learners

  • Students may draft and request critique in the language of the assigned task. If the assignment is English, the critique is on English; if the assignment is Spanish, the critique may be in Spanish.
  • Pre-teach critique, draft, reject, disclose, and PII with home-language equivalents on a pocket card.
  • Allow the T-chart because-clauses in the language the student thinks in; the revised sentence should match the assignment language.

IEP / 504

  • Extra time on the independent step; the T-chart can be completed in the resource room the same day.
  • Speech-to-text for the because-clauses if that is an approved accommodation; still no uploading of another student's audio.
  • Reduced load: one keep and one reject instead of three decisions, with the same quality of reason.
  • Large-print checklist and a quiet copy of the protocol. Do not require the student to log into an unapproved tool as a condition of credit.

Assessment

Formative

  • Warm-up vote plus one spoken reason.
  • PII strip visible on the draft before any paste.
  • T-chart in progress during independent practice; teacher circulates for empty because-clauses.

Summative

  • Completed revision log: tool or checklist named, date, one keep, one change, one reject with reasons, and one revised sentence from the student's own draft.
  • Exit ticket: 'In one sentence, how is a second reader different from a ghostwriter?'

Success criteria

  • The draft used for critique existed before the AI or checklist step (or is clearly labeled as the public practice sample).
  • No classmate's work was entered into a tool.
  • The student can explain at least one rejected suggestion, showing that the human remained the decision-maker.
  • Disclosure is filled in. PII was stripped.

Responsible use

AI is allowed in this lesson only as a second reader of work the student already drafted. Prompts that ask the tool to write, rewrite, or 'make it sound like a 10th grader' are out of bounds. Students use a district-approved tool or the paper checklist. They disclose the tool and date. They do not shop for a chatbot that will hide the help. Teachers model on public samples, never on a live student paper on the projector. If a student arrives without a draft, they practice on the public sample and complete the real protocol later; they do not generate a draft in the tool to 'catch up.'

Ethics

Honesty about help is part of becoming a colleague people can trust in shops, farms, hospitals, and newsrooms across Idaho. Passing off generated text as your own thinking steals practice from you and misleads the reader. Using AI to critique, then deciding what to take, keeps the human responsible for the words. Flattering or generic praise is a known failure mode; treating it as a grade is an ethical mistake. Ghostwriting for a classmate, with or without AI, is cheating and a privacy violation.

Privacy

FERPA protects education records, including student writing that identifies a student. Do not paste another student's work into any AI tool. Do not include student ID numbers, emails, phone numbers, home addresses, photos, medical notes, or a teacher's comments that name a student. Strip headers before paste. Teacher modeling uses a public sample. Student accounts exist only on district-approved tools covered by a data-privacy agreement. Printed drafts stay with the author. Offline path: nothing leaves the paper.

Reflection

  1. Which reader — human or AI — changed my next sentence, and what does that tell me about what I still need from people?
  2. What suggestion did I reject, and how would my paper have gotten worse if I had accepted it?
  3. Did I follow every step of the protocol, including PII and disclosure?
  4. Where in my week am I tempted to skip the draft and jump to the chatbot, and what will I do instead?

Homework

Finish the one-sentence revision if it was not done in class. Complete the revision log. If you used the public sample today, apply the full protocol (human reader plus critique checklist or approved tool) to a real draft from any class and bring both the T-chart and the original draft. Students without home internet use the printed checklist only. Do not upload anyone else's work. Optional: ask a family member to be the human reader for five minutes and add their comment to the left column.

Closing

Return to the title. A second reader points at sentences. A ghostwriter replaces you. Three volunteers share one rejected suggestion. Restate the non-negotiables: your draft first, your decisions, no one else's work in a tool, PII stripped, help disclosed. Point to the protocol on the wall and tell students it applies to the next paper in every class, not only this period. Collect revision logs as the exit ticket.

Extensions

  • Apply the same protocol to a lab report, an FFA speech, or a history short-answer, still with a human comparison.
  • Invite the librarian to show how citation of AI critique differs from citing a source used for evidence.
  • Build a class 'banned prompt' list (rewrite this, write the essay, make it sound smarter) and a 'allowed prompt' list.
  • In a 90-minute block, score a set of anonymous printed comments (teacher-prepared, not student papers) as specific or useless, then rewrite two useless comments into specific ones without using AI.

Cross-curricular links

English Language Arts
Revision stage of the writing process: peer conference plus AI conference, with the author in charge of the next draft.
Agriculture / CTE
Critique a procedure write-up (for example, a potato-storage observation) for missing steps; a chatbot cannot stand in the cellar and check the thermometer.
Social Studies
Editorial feedback on a short argument about a local issue (water, land use, a city council agenda) must not invent quotations from officials.
Advisory / counseling
Academic-integrity conversation before research-paper season; practice disclosure language families can understand.

Back to contents

AI Fluency · Application

9-12.AIF.AP.2

Run It, Don't Worship It

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Use AI tools to generate code for a simple coding project.

Clarification. Students run the code and evaluate the code's output but do not need to fully understand the code itself.

Student-friendly learning targets

  • I can use a district-approved AI tool (or teacher-provided generated code) to obtain a tiny program for a simple, defined job.
  • I can run that code in a browser, a Scratch-like environment, or a paper trace and record what it actually outputs.
  • I can evaluate output with test cases I choose, including at least one edge case, without claiming I fully understand every line.
  • I can describe one way the output was wrong, incomplete, or surprising, and I do not treat generated code as automatically correct.

Essential questions

  1. If I did not write the code, how can I still be responsible for what it does?
  2. What does a test case reveal that reading the code might miss?
  3. When is a tiny generated program good enough for a real Idaho job, and when must a human still check the result?
  4. What is the difference between running code and worshipping it?

Objectives

  1. Students will obtain code for one tiny project: a Fahrenheit–Celsius temperature converter, a wildfire-risk checklist, or a potato-grade counter.
  2. Students will run or trace the code with at least five inputs and complete an expected-versus-actual table.
  3. Students will mark pass/fail for each test, including one edge case (empty input, exact boundary, negative temperature, or humidity of zero).
  4. Students will write one evaluation sentence that judges the output, not the elegance of the code.
  5. Students will follow the offline path (printed generated code plus paper trace) whenever devices or approvals are unavailable, still meeting the standard.

Key vocabulary

Generative AI (Gen AI)
A subset of machine learning and AI specifically designed to create new content, including text, images, audio, code, video, or synthetic data based off a prompt.
Output
What the program prints, displays, or decides after it runs. In this lesson you judge the output, not whether you could have written the code yourself.
Trace
Stepping through code on paper: write the input, follow each line, and record the value of each result. Used when you cannot run the program on a computer.
Test case
A specific input chosen on purpose, with the output you expect written down before you run the code. Good test cases include normal values and edge cases.
Edge case
An input at a boundary or in an awkward situation: zero, a negative number, an empty list, or a value exactly on a cutoff. Edge cases often reveal mistakes.
Hallucination
Instances where an artificial intelligence system generates information that is incorrect, misleading, or entirely fabricated, but presents it as if it were true. Generated code can hallucinate a formula, a grade cutoff, or a library that does not exist.

Teacher background

Idaho standard 9-12.AIF.AP.2 asks students to use AI tools to generate code for a simple coding project. The clarification is exact and is the pedagogy: students run the code and evaluate the code's output but do not need to fully understand the code itself. This is not a computer-science unit on syntax. It is a fluency lesson on verification. Keep the project tiny so every student can finish five tests in one period. Three Idaho-flavored options cover different interests: a temperature converter (school weather stations, Stanley winter, seed packets in Celsius), a wildfire-risk checklist (humidity, wind, fuel dryness — familiar from fire season in the Boise Foothills, the Payette, and eastern Idaho), and a potato-grade counter (Magic Valley packing sheds counting how many tubers fall in a size band). Students may generate the code with a district-approved tool or receive teacher-provided generated code. They run it in a browser console, a Scratch-like environment, or on paper. Offline is first-class: print the generated JavaScript or pseudocode and a trace table. Never require students to install software or to understand every line. Never paste student names into the prompt. This lesson belongs in Semester 1, Weeks 10–14 ('Agents, code, and communication'); keep projects tiny and runnable, and name Idaho pathways in agriculture, energy, and public service when you talk about why output matters.

Materials

  • District-approved AI tool for code generation, teacher account; student use only if approved.
  • Teacher-prepared generated code packets (offline and equity path) for all three tiny projects, each one page, with comments stripped of student names.
  • Run options: browser JavaScript console on a district page that does not require an account; a Scratch-like editor if already installed; or paper trace. Pick one default so you are not debugging three platforms.
  • Expected-versus-actual test table (five rows plus one edge-case row) with columns: input, expected output, actual output, pass/fail, note.
  • Known-answer keys for the teacher only: 32 F = 0 C; 212 F = 100 C; wildfire 'high' when humidity is below 20 and wind is above 15 and fuel is dry; potato Size A count for a published list of diameters.
  • Sample input lists: Boise and Stanley temperatures; a five-day humidity/wind table; a list of ten potato diameters in inches.
  • PII reminder card and the rule: prompts describe the task, never the student.
  • Projector for a live run of the temperature converter. Printed code on the document camera as backup.
  • Optional: four-function calculators for students who want to check the conversion formula by hand.

Before class

  • Generate the three tiny programs yourself before class on the approved tool. Save the exact code you will hand out. Run your own five tests and note at least one weakness (for example, no message when the list is empty).
  • Print code packets and test tables for every student. Assume a rural bandwidth day: the paper packet is the lesson.
  • Choose one run environment and post three steps to open it. If devices are one-to-few, run in pairs. If devices are none, everyone traces on paper.
  • Write the student prompt on the board so generation stays tiny: 'Write a short JavaScript function. Temperature: convert F to C and C to F. Wildfire: given humidity percent, wind mph, and fuel dry true/false, return low, moderate, or high using these cutoffs: high if humidity < 20 AND wind > 15 AND fuelDry is true; moderate if two of those three are true; otherwise low. Potato: given a list of diameters in inches, count how many are at least 1.875 and at most 3.25 (Size A band for this lesson). Print the result. Do not add extra features.'
  • Prepare a wrong-output warm-up: three wildfire outputs, one of which called a calm, humid day 'high.'
  • FERPA: no student names in prompts or in code comments. Do not have students email code to a public chatbot.
  • 90-minute block: keep this sequence. Add about 20 minutes so every student breaks the program on purpose with two more edge cases and writes a mini bug report, plus about 15 minutes of discussion comparing the three projects. Do not scale up into an app.

Instructional sequence

Warm-up — Which wildfire output is lying?

5 min
  1. Project three outputs from a 'wildfire risk' snippet for the same imaginary afternoon near Idaho City. Case 1: humidity 45%, wind 5 mph, fuel not dry, output HIGH. Case 2: humidity 12%, wind 25 mph, fuel dry, output HIGH. Case 3: humidity 12%, wind 25 mph, fuel dry, output LOW.
  2. Students mark on a mini whiteboard which case cannot be right, given the cutoff rule posted on the board.
  3. Reveal: Case 1 overstates risk; Case 3 understates it. Case 2 matches the rule. Name the day's claim: you do not have to understand every line to catch a bad output. You do have to run tests.
  4. Tell students they will generate or receive tiny code, run it, and judge it. They will not be graded on writing code from scratch.

Direct instruction — The standard, the tiny project, and a live run

10 min
  1. Read the standard aloud exactly: 'Use AI tools to generate code for a simple coding project.' Read the clarification exactly: 'Students run the code and evaluate the code's output but do not need to fully understand the code itself.' Underline 'run' and 'evaluate' and 'do not need to fully understand.'
  2. Show the three project cards. Students will pick one: temperature converter (weather and greenhouses), wildfire-risk checklist (fire season), potato-grade counter (packing sheds). All three are small on purpose.
  3. Teacher model on the temperature converter. If the tool is up, paste the posted prompt from the teacher account and generate. If not, place the printed code on the document camera. Say: 'I am not going to explain every line. I am going to run it.'
  4. Run or trace three known answers: 32 F should be 0 C; 212 F should be 100 C; -10 F (a Stanley January morning) should be a negative C. Record expected versus actual in front of the class.
  5. If the generated code is wrong or refuses negatives, celebrate the catch. That is the standard. If it is right, still show the empty-input question: what does it do if I type nothing?
  6. Restate the integrity rule: you may use generated code for this assignment because you will test it. You may not turn in untested code, and you may not claim you wrote lines you did not write. Credit the tool on the test table header.

Guided practice — Trace one potato, as a class

10 min
  1. Place the potato-grade counter code on the projector (generated earlier). Read the Size A rule: diameter at least 1.875 inches and at most 3.25 inches for this lesson's simplified band.
  2. Give the class a list of five diameters, for example 1.5, 1.875, 2.4, 3.25, 4.0. Students predict the count on paper before anyone runs anything. (Expected: 1.875, 2.4, and 3.25 count; 1.5 and 4.0 do not. Count = 3.)
  3. Run the code or trace it line by line together. Fill expected versus actual. If the generated code used strict inequalities and dropped the boundary potatoes, that is a find, not a failure of the student.
  4. Name the evaluation sentence stem: 'The output is trustworthy for ___ and not trustworthy for ___ because ___.'
  5. Assign partners. Each pair picks one of the three projects. Pairs that cannot use a device receive the printed packet for their choice automatically.

Independent practice — Five tests and one edge case

12 min
  1. Each pair obtains code: generate with the posted prompt on an approved tool, or open the teacher packet. No extra features. No student names in comments.
  2. Write five test cases before running, including expected output. Temperature examples: 32 F, 212 F, 68 F, -10 F, and a Celsius-to-Fahrenheit check. Wildfire: mix high, moderate, and low days using the posted cutoffs. Potato: include a boundary diameter and a tuber that is too small.
  3. Run or paper-trace each test. Fill actual output and pass/fail. Calculators are allowed to check the conversion formula.
  4. Add a sixth row: an edge case (empty list, humidity 0, wind 15 on the cutoff, letters typed instead of a number). Record what happened, even if it was an error message.
  5. Write one evaluation sentence. Credit the tool or write 'teacher-provided generated code.'

Real-world examples

  • A packing shed in the Magic Valley uses a simple counter to tally potatoes in a size band; a human still pulls misshapen tubers the script cannot see.
  • A Bureau of Land Management or Forest Service fire-weather briefing uses cutoff rules for humidity and wind; generated dashboards still get checked against a belt weather kit on the ridge.
  • A school greenhouse in Teton County converts Celsius on a European seed packet to Fahrenheit before setting a heat mat; a wrong formula cooks the starts.
  • An irrigation manager near Twin Falls might run a tiny script on pump times; the farmer still walks the field because a dry corner does not show up in a bad formula.
  • A student weather station in Rexburg logs overnight lows well below zero; a converter that crashes on negatives is useless in January.

Hands-on activity

Hands-on — Break it on purpose, then judge it

8 min
  1. Each pair tries to make the program fail or look foolish: empty input, a temperature below absolute nonsense (for example 1000 F), wind of 15 exactly, a potato diameter of 1.875. Record the output.
  2. Trade tables with another pair who chose the same project. One difference in pass/fail becomes a 30-second conference: who tested the boundary?
  3. On the board, collect three 'do not worship it' findings from the room (crashes, off-by-one at a cutoff, wrong formula, silent empty list).
  4. Block extension (90 minutes): students write a six-line bug report (what I typed, what I expected, what I saw, how a human should check this in the field, whether I would let this run a greenhouse or a fire board overnight, what I still do not understand and do not need to). Optional: one volunteer pastes a failing test back into the approved tool and asks for a fix, then re-runs the same table to see whether the fix broke a test that used to pass.

Discussion questions

  1. The clarification says you do not need to fully understand the code. What do you still need to understand about the job the code is doing?
  2. Which test case would have been easy to skip and would have hidden a mistake?
  3. Would you let today's program set a frost fan, post a fire-danger sign, or pay a grower by the hundredweight? Why or why not?
  4. How is running generated code different from copying an essay the chatbot wrote?
  5. If two chatbots give two different programs, how do you choose? (Answer you want: you run tests, you do not pick the one that 'looks smarter.')
  6. What should a worker at a packing shed or a fire desk write down when they use a generated script, so the next shift can trust or distrust it?

Differentiation

Support

  • Pre-assign the temperature converter and provide the five expected answers on a hint card after the student has written predictions.
  • Paper trace only, with numbered arrows on the printout so the student can follow without a device.
  • Pair a reader with a recorder; both names go on the table; both must speak one test result.
  • Allow yes/no evaluation ('It got 32 F right and failed on empty input') instead of a long sentence.

Challenge

  • Add a second cutoff (for example US No. 1 quality is not just size) and show that today's counter cannot see bruises, so output can pass while the load should fail.
  • Write one new test case that would be required before this code could advise a real fire desk, and explain why a classroom cutoff is not a forecast.
  • Compare generated JavaScript and a Scratch-like version of the same job; evaluate which output is easier for a non-programmer to test.

Multilingual learners

  • Test tables may use home-language notes in the 'note' column; the numbers stay Arabic numerals.
  • Provide a diagram of F versus C and of potato size bands with labeled arrows.
  • Read the posted prompt aloud and leave it visible; generation quality drops when the student is fighting English and the task at once.

IEP / 504

  • Fewer tests (three plus one edge case) with the same expected-versus-actual structure.
  • Large-print code packet and a calculator. No requirement to type code.
  • Oral trace: student tells a paraeducator or teacher the next value; adult scribes the table.
  • Noise-reducing seat during device runs. Credit for paper trace equal to credit for a console run.

Assessment

Formative

  • Warm-up identification of the lying wildfire output.
  • Predicted potato count before the class run.
  • Circulation check: expected column filled before the actual column.

Summative

  • Completed test table with five tests, one edge case, pass/fail, tool credited, and one evaluation sentence about output.
  • Exit ticket: 'Name one output you would not trust in a greenhouse, a packing shed, or a fire briefing, and why.'

Success criteria

  • Code was generated or provided; the student did not have to author it from scratch.
  • The student ran or traced the code and recorded actual output, not guesses after the fact.
  • At least one test failed, one boundary was probed, or the student clearly stated that all tests passed and named a risk still untested.
  • The evaluation judges output. The student does not claim full understanding of every line, and is not penalized for lacking that understanding.

Responsible use

Use a district-approved tool or teacher-provided generated code. Prompts describe a tiny task, not a student. Credit the tool on the table. Do not paste generated code into a live control system, a gradebook, or anyone's homework for another class. Do not download random scripts from the open web for this lesson. If the tool offers to 'explain every line,' students may read the explanation after tests, not instead of tests. Offline packets are full credit.

Ethics

Running untested code can waste a crop, mislead a fire desk, or simply spread a wrong number. The ethical move is to test with known answers and to say when you would not trust the output. Pretending you understand code you have not run is a different problem from using generated code honestly. Both are addressed here: you may use the generator; you may not skip evaluation; you may not take credit for writing what you did not write. A script that counts potato size still cannot see rot; over-trust is a harm.

Privacy

No student names, IDs, or class lists in prompts or in code comments. Do not use personal weather-station data that includes a home address. Use school or public sample numbers (Boise airport temperatures, a made-up list of diameters). Do not photograph classmates' screens for social media. FERPA: a file named with a student's last name plus 'code' is an education record; keep it in the district system or on paper in the classroom. Public chatbots are not a drop box for classwork.

Reflection

  1. Which test taught me the most, and would I have thought of it if I had only read the code?
  2. Where would this program be 'good enough' and where would it be dangerous?
  3. What did I not understand in the code, and why was that allowed today?
  4. How will I talk about generated code on a job site so a supervisor knows I tested it?

Homework

Add two more test cases to your table, including one that uses a number from real life (tonight's forecast high in your town, a seed-packet temperature, or a potato you measure with a ruler). Students without internet use the printed code and a paper trace. Do not install new apps. Optional: ask a family member in farming, trades, or wildland fire what number they still check by hand even when a screen already shows it, and write that sentence on the back of the table.

Closing

Read the clarification one more time. You ran the code. You evaluated output. You did not have to fully understand the code. Collect test tables. Three students name one failed or shaky test. End on the title: run it, do not worship it. Preview tomorrow's idea: if today's script only does one job, an agent is a recipe for a job that may use several tools — and a human still checks every step.

Extensions

  • Re-run the wildfire checklist against a printed National Weather Service fire-weather discussion for southern Idaho and mark where a three-rule script is too simple.
  • Visit (or video-call) an agriculture teacher or a local grower and ask how size grading actually works beyond one diameter band.
  • In CS club, rewrite the converter in a second language after the fluency lesson, still keeping the same test table.
  • 90-minute block gallery: three stations, one per project; students rotate to run one test on a project they did not choose.

Cross-curricular links

Mathematics
Unit conversion, inequalities, and boundary values. Students write expected C from F before they trust a program.
Earth science / agriculture
Fire-weather factors and potato grading as real measurement jobs where a wrong output has a cost.
Computer science (optional)
This lesson is a doorway, not a syntax unit. Interested students may read the code after they have tested it, never as a gate to credit.
Career and technical education
Documenting tests is a workplace habit: operators initial a reading because the display can be wrong.

Back to contents

AI Fluency · Application

9-12.AIF.AP.3

Build a Narrow Agent

9–10 · 50 minutes · 90 minutes (extend hands-on and discussion)

Standard quoted exactly

Construct AI agents to accomplish a defined task.

Student-friendly learning targets

  • I can construct a narrow AI agent by specifying a goal, allowed tools, constraints, and success checks on a worksheet, without having to write Python.
  • I can choose a defined task small enough that a human can verify every step, such as finding three reputable sources on Idaho water rights or drafting a packing list for a 10th-grade Sawtooth field study given a forecast.
  • I can run the spec (in a district-approved agent builder if one exists, or as a human role-play of the agent) and mark each success check pass or fail.
  • I can explain why a narrow agent with a human in the loop is safer than a vague instruction like 'do my research' or 'plan the whole trip.'

Essential questions

  1. What does 'construct' mean if I am not writing a program?
  2. How narrow does a task have to be before an agent can finish it and a human can check it?
  3. Which tools should this agent be allowed to use, and which must it be forbidden to use?
  4. Who is responsible if the agent lists a URL that does not exist or packs a tent and forgets water?

Objectives

  1. Students will complete an Agent Spec worksheet: task name, one-sentence observable goal, inputs, allowed tools, forbidden tools, constraints (including no PII), success checks, human verification steps, failure modes, and stop conditions.
  2. Students will construct a spec for one of two defined tasks: (A) find three reputable sources on Idaho water rights and list them with URLs to verify, or (B) draft a packing list for a 10th-grade field study in the Sawtooths given a weather forecast.
  3. Students will execute the spec through a district-approved agent builder if available, or through a partner role-play that may use only the tools the spec allows.
  4. Students will verify every step as a human: open each URL, or check each packing item against the printed forecast and school field-trip rules.
  5. Students will record at least one failure or hallucination (broken URL, missing layer, invented agency) and one change they would make to the spec.

Key vocabulary

Agentic AI
AI systems designed to independently plan, execute, and adjust actions to achieve a specific goal with minimal human intervention, often capable of working across multiple tools or applications.
Agent (in this lesson)
A narrow worker you design for one defined task. You construct it by writing its goal, tools, constraints, and success checks. You do not have to code it in Python.
Constraint
A rule the agent must not break, such as 'use only .gov or .edu sources,' 'no student names,' or 'pack for 24 hours, not a week.' Constraints keep a narrow agent from wandering.
Success check
An observable test a human can apply when the agent finishes: 'three URLs that open and name Idaho water rights,' or 'every clothing item matches the forecast overnight low.'
Human-in-the-loop
A model of interaction where a human is required to participate in a process, such as verifying, approving, or correcting, to ensure the accuracy, safety, and ethical alignment of AI-generated outcomes.
Human-Centered
An approach where AI is used specifically to support human inquiry. It ensures that humans remain responsible for the initial objective, final decision-making, oversight, and ethical reflection at the beginning and end of every task (Human AI Human).

Teacher background

Idaho standard 9-12.AIF.AP.3 is one sentence: Construct AI agents to accomplish a defined task. For grades 9–10, 'construct' does not mean ship a Python agent with API keys. It means specify the agent so tightly that another person (or a district-approved builder) could follow it: goal, tools, constraints, success checks, and a human who verifies every step. That reading matches the glossary terms Agentic AI, human-in-the-loop, and Human-Centered (Human AI Human). Keep tasks narrow. Two classroom-ready jobs work in Idaho without collecting PII: (1) find three reputable sources on Idaho water rights and list them with URLs a human will open; (2) draft a packing list for a 10th-grade field study in the Sawtooths given a weather forecast the teacher prints. Reputable water-rights starting points a teacher can verify include the Idaho Department of Water Resources, Idaho statutes or the Attorney General's water-law materials, and University of Idaho Extension or Idaho Law Review explainers — not a random blog and not a URL the model invented. Sawtooth packing must obey school trip rules (no personal vehicles, medications handled by staff, no real home addresses in the prompt). If the district has not approved an agent builder, the worksheet plus a partner who role-plays the agent is the construction. Do not send students to unpaid public agent sites that scrape chats. This lesson sits with AP.2 in Weeks 10–14; keep the agent as small as yesterday's script, and keep a human on every step.

Materials

  • Agent Spec worksheet with labeled boxes: task name, goal, inputs, allowed tools, forbidden tools, constraints, success checks, human verification steps, failure modes, stop conditions.
  • Two task cards. Card A: 'Find three reputable sources on Idaho water rights and list them with URLs to verify.' Card B: 'Draft a packing list for a 10th-grade field study in the Sawtooths given a weather forecast.'
  • Printed forecast for Stanley or the Sawtooth National Recreation Area (public NWS text, no student locations). Printed field-trip rules excerpt (school-provided, no student medical information).
  • Printed 'starter map' of water-rights sources for the teacher (IDWR, a .gov statute page, UI Extension). Do not hand this to students until after the first verification so they still have to check.
  • Optional: district-approved agent builder or a locked teacher account. If none, skip without penalty.
  • Role-play badges or sticky notes labeled AGENT and HUMAN VERIFIER.
  • Verification log: step, agent output, human check (opened URL / compared to forecast), pass/fail, notes.
  • PII and FERPA card: the agent may not collect student names, home addresses, phone numbers, or health information. Packing lists use 'a 10th grader' not 'Maria from McCall.'
  • Offline packet: a filled sample spec with two planted errors (a 404-style fake URL; a packing list that omits water) for students to catch.

Before class

  • Print Agent Spec worksheets and both task cards. Decide whether an approved builder exists. If not, plan role-play as the default, not as a downgrade.
  • Pull a current public forecast for Stanley, ID or Sawtooth NRA and a one-page field-trip rule sheet. Redact any real student information if you are adapting a past trip form.
  • Walk both tasks yourself. For water rights, confirm three URLs that actually open. For packing, pack against the forecast overnight low and a 24-hour trip. Plant one error in the sample packet.
  • Post the construction definition: goal + tools + constraints + success checks + human verification. Post what this lesson is not: 'write Python,' 'let the agent do my homework,' 'give it my address.'
  • Arrange pairs: one constructs, then they swap verifier roles. Solo students verify against the printed forecast or the teacher starter map.
  • 90-minute block: keep this sequence. Add about 20 minutes so every spec is executed and every URL or packing item is checked, plus about 15 minutes of discussion on failure modes (hallucinated agencies, over-packing, missing water). Do not widen the task to 'plan the whole trip' or 'write the research paper.'
  • Coordinate with the librarian if possible: reputable source means the human can name the publisher, not that the chatbot said 'reputable.'

Instructional sequence

Warm-up — Recipe versus wanderer

5 min
  1. Show two instructions. Wanderer: 'Do my research on water and also plan our mountain trip.' Recipe: 'Return three sources on Idaho water rights. Each must have a URL. I will open each URL. Stop after three.'
  2. Students label which one is a defined task an agent might finish and a human might check in one class period.
  3. Name the day's claim: we will construct a narrow agent on paper. Construct means specify. It does not require Python. A human verifies every step.
  4. Point at the two task cards. Both are Idaho work. Both are small on purpose.

Direct instruction — What 'construct' looks like on a worksheet

10 min
  1. Read the standard aloud exactly: 'Construct AI agents to accomplish a defined task.' Write construct on the board and unpack it: goal, tools, constraints, success checks, human verification, stop conditions.
  2. Read the glossary sense of Agentic AI and then narrow it for 9–10: we are not launching an unsupervised worker across the open internet. We are writing a job description a tool (or a partner) must obey.
  3. Model Task A on the document camera. Goal: 'List three sources on Idaho water rights, each with a URL I can open today.' Allowed tools: search of .gov and .edu only, or the school library page. Forbidden: social media as the only source, invented citations, student names. Success checks: three URLs; each opens; each page is clearly about Idaho water rights. Human verification: I click each link. Stop: after three verified sources or after five minutes, whichever comes first.
  4. Show a bad spec: 'Get me everything on water and make it sound smart.' Ask why a human cannot verify it in this period.
  5. Show the Human AI Human loop on the board: human writes the goal, agent (or role-play) works, human checks, human decides whether the job is done.
  6. FERPA reminder: packing-list prompts use a generic 10th grader and a public forecast. No home addresses, no medication lists, no classmate names.

Guided practice — Co-write one spec, then try to break it

10 min
  1. As a class, fill the Agent Spec boxes for Task A or B (teacher choice; use the other as independent practice). Fill every box; empty boxes are not allowed.
  2. Invite a student to play AGENT. The agent may use only allowed tools: for water rights, the teacher may permit a search on a projector or a printed IDWR snippet; for packing, the agent may read only the printed forecast and the rule sheet.
  3. A second student plays HUMAN VERIFIER and uses the verification log. If a URL is not opened, it does not count. If a packing item ignores the overnight low, it fails.
  4. Class names one constraint to add after seeing a miss (for example: 'Do not list Facebook groups as sources' or 'Include water and a warm layer no matter what').
  5. Students now choose the other task, or the same task with their own wording, for independent construction. They may not skip the worksheet and 'just chat.'

Independent practice — Write the spec; do not skip to the toys

12 min
  1. Each student (or pair) completes a full Agent Spec for Task A or Task B. Complete sentences in the goal box. Tools listed by name. At least three constraints, one of which is 'no PII.' At least three success checks a human can observe.
  2. Peer desk-check: partner tries to find a way the spec would let the agent wander (for example, packing for a week, citing Wikipedia only, asking for the student's street address). Author revises before any execution.
  3. If a district-approved builder is available, students may paste the spec into it after the desk-check. If not, they stop at a complete worksheet and wait for the hands-on role-play. Both paths meet the standard.
  4. Students with no partner use the planted-error sample packet as the agent output and complete the verification log against it.
  5. Teacher circulates for missing stop conditions. A spec without a stop will run until the period ends; make them write one.

Real-world examples

  • A county emergency manager in eastern Idaho might use an agent to draft a reverse-911 outline from a public weather feed; a human still records the message and sends it.
  • A school librarian constructs a search agent that may return only .gov and .edu sources on water rights; the librarian still opens the links before they go on a research guide.
  • An outdoor-education teacher at a McCall or Stanley field study uses a packing-list agent against an NWS forecast, then checks the list against district trip rules and a real duffel.
  • A 4-H robotics team writes a narrow agent spec for 'sort by size only'; a human still pulls damaged produce the robot cannot see.
  • Idaho Department of Water Resources staff, not a chatbot, remain the authority on water rights; an agent that invents a decree number has failed even if the sentence sounds official.

Hands-on activity

Hands-on — Execute, then human-verify every step

8 min
  1. Pairs assign roles: AGENT follows the spec exactly (builder or role-play). HUMAN VERIFIER opens URLs or checks packing items against the printed forecast and trip rules. Switch after four minutes if time.
  2. Fill the verification log. Unopened URLs are automatic fails. Packing lists that omit water, a warm layer when the overnight is below 40 F, or that add a personal vehicle against trip rules fail.
  3. Mark hallucinations in the margin: a source that does not exist, a misnamed agency, a forecast the agent invented instead of reading. One hallucination is enough to require a spec revision.
  4. Each student writes one spec change: add a constraint, tighten a success check, or narrow the goal. This is the construction improvement, not extra code.
  5. Block extension (90 minutes): run the revised spec once more. Then a short seminar: could this agent be allowed to send an email, book a van, or file a water-rights form? (The answer you want is no — those are human actions.) Optional approved-builder demo by the teacher only, on a projector, with the class calling stop conditions out loud.

Discussion questions

  1. Where in your spec was the agent still free to wander, and what constraint closed that hole?
  2. Why does 'three URLs I will open' beat 'good sources' as a success check?
  3. If the agent packs a stove and the trip rules forbid student stoves, who is at fault — the tool or the author of the spec?
  4. What would go wrong if we let an agent 'just handle' water-rights research for a graded paper?
  5. How is this construction different from yesterday's tiny generated script, and how is the human's job the same?
  6. When should we not build an agent at all and just do the task ourselves?

Differentiation

Support

  • Provide a partially filled spec with the goal and one constraint already written; the student adds tools, success checks, and verification steps.
  • Offer a word bank of tools (school library page, printed forecast, IDWR site, calculator) and of forbidden tools (social media only, invented URL, home address).
  • Let the student construct Task B (packing list) if reading dense .gov pages is the barrier; verification is then tactile (forecast numbers, clothing items).
  • Scribe the worksheet from the student's oral spec; the thinking is the standard, not the handwriting.

Challenge

  • Add a second success check that catches a known hallucination type (URL that does not mention Idaho, packing list that ignores wind).
  • Write a stop condition that would prevent the agent from starting a new task it was not given.
  • Compare two specs for the same task and argue which one a substitute teacher could run tomorrow without you in the room.

Multilingual learners

  • Worksheet boxes may be completed in the student's strongest language; the three URLs and the packing items stay in a form the verifier can check.
  • Pre-teach goal, tool, constraint, verify, and stop with a bilingual card.
  • For Task A, allow one source in Spanish if it is still an official or extension publisher the student can identify, plus two English .gov/.edu sources, or the reverse, as long as the human can verify each.

IEP / 504

  • Fewer boxes required for credit: goal, two tools, two constraints, two success checks, and a named human verifier. Same verification rigor.
  • Extended time to open URLs in the library lab. Printed pages instead of live links if screens are a barrier.
  • Role-play only; no requirement to use an agent builder.
  • Quiet instructions and a checklist with boxes to tick rather than long prose. Adult may read the forecast aloud.

Assessment

Formative

  • Warm-up label of recipe versus wanderer.
  • Desk-check of the spec before execution; teacher initials that no PII box is empty.
  • Verification log in progress: at least one URL opened or one packing item checked in class.

Summative

  • Completed Agent Spec with every box filled, plus a verification log that shows a human check on each success criterion.
  • One written spec revision after a miss or a planted error, and an exit ticket: 'Name the human's job at the start and at the end of this agent.'

Success criteria

  • The task is defined and narrow; it matches Card A or Card B or an equally small teacher-approved variant.
  • The spec includes goal, tools, constraints, success checks, and a stop condition. Construction is visible on paper even if no builder was used.
  • A human verified every step. Unchecked output does not count as success.
  • No PII was entered. No classmate's information was used. The student can name one failure mode.

Responsible use

Construct on the worksheet first. Use a district-approved agent builder only if one exists; otherwise role-play. Do not create accounts on public unsupervised agent sites. Do not give an agent permission to send email, spend money, post to the web, or contact agencies. The human starts the task, checks every step, and stops the agent. Credit the builder if used. Offline role-play is full credit. Specs stay in the classroom system or on paper.

Ethics

A narrow agent can save time on fetching links or listing gear. It cannot take responsibility for a broken source, a student who goes to the Sawtooths underdressed, or a water-rights claim that is wrong. Writing a vague spec and blaming the tool is an ethical failure of the constructor. Inventing URLs or packing without reading the forecast is a hallucination the human must catch. Do not build agents for tasks that should stay fully human: grading peers, medical decisions, reporting a classmate, or contacting government about a real water right in a student's family name.

Privacy

FERPA and good sense: no student names, home addresses, phone numbers, health or medication details, or family water-right owner names in the spec or the prompt. Use 'a 10th grader' and a public forecast. Do not upload a real permission slip. Agent builders, if used, must be district-approved with a data-privacy agreement. Role-play on paper never leaves the room. Verification logs that include a student name are education records and stay in the district grade system, not in a public chatbot.

Reflection

  1. Which box on the spec did the most work — goal, constraint, success check, or stop — and what would have happened if I had left it blank?
  2. What did the human verifier catch that the agent (or role-play partner) missed?
  3. Would I let this agent talk to the web unsupervised overnight? Why or why not?
  4. How will I use Human AI Human on the next research or trip-planning job in another class?

Homework

Revise one constraint and one success check on your spec using tonight's thinking. If you chose water rights, try to open your three URLs at home or at the public library and write pass/fail; if a link fails, find a replacement by hand, not by trusting a new unverified list. If you chose packing, check the next day's Stanley or Sawtooth forecast (radio, printed paper from the teacher, or a family device) and note one item you would add or drop. Students without internet receive a printed forecast and a printed IDWR page as the homework packet. Do not sign up for new agent websites. Do not include your address or a family member's name.

Closing

Repeat the standard: construct AI agents to accomplish a defined task. Point at a completed worksheet: that is construction. Point at a verification log: that is the human. Collect specs and logs. Two students name one hallucination they caught. End with the loop on the board: human writes the goal, the narrow agent works, the human checks, the human decides. Preview how this skill returns in later standards when agents appear inside real applications: the job description you wrote today is still the safety rail.

Extensions

  • Librarian station: convert a successful water-rights spec into a one-page research guide other classes can use, still with the instruction to open every URL.
  • Outdoor club: compare the agent packing list to what a Sawtooth ranger or a school trip lead actually packed last year (guest or recorded interview).
  • CS extension (not required): if a district builder exists, save the spec as a reusable template with the teacher's name as owner, not the student's personal account.
  • Write a third task card for a local job (greenhouse watering check, FFA meeting agenda reminder) that is still verifiable in ten minutes.

Cross-curricular links

Civics / Idaho history
Water rights are a live Idaho policy topic. Students practice finding primary publishers (IDWR, statute) instead of accepting a chatbot's summary.
Earth science / outdoor education
Field-study packing against a real forecast in the Sawtooths; weather numbers beat generic 'bring a jacket' advice.
English / research
Source evaluation: a URL is not a source until a human opens it and names the publisher.
Health / PE
Trip safety constraints (water, layers, school rules) belong in the spec so an agent cannot optimize them away.

Back to contents

AI Impact · Ethics and Privacy

9-12.AII.EP.1

After the Flood: GenAI in Every Subject

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Evaluate the ethical implications of how AI has changed since GenAI has become commonplace.

Example from the standards. Each content area can focus on how GenAI has impacted and changed aspects within their field (like writing, music, art, social media, math, etc).

Student-friendly learning targets

  • I can explain how commonplace GenAI changed work in at least two school subjects, using dated evidence rather than opinion.
  • I can distinguish academic-honesty issues from broader ethical questions of authorship, labor, credit, and assessment validity.
  • I can evaluate a proposed classroom or workplace use of GenAI and argue whether it preserves or undermines human thinking.

Essential questions

  1. What, exactly, changed in writing, art, music, mathematics, and public conversation once GenAI became ordinary?
  2. Which ethical costs belong to cheating, and which belong to authorship, labor, and what teachers can still see of student thinking?
  3. How should an Idaho classroom keep human judgment in charge without pretending the flood can be reversed?

Objectives

  1. Compare a pre-2022 and a post-2022 version of the same academic task in two content areas and name the ethical shift in each.
  2. Evaluate a GenAI use case using four lenses: authorship, labor and pay, assessment validity, and effects on public discourse.
  3. Cite at least two dated sources (policy, syllabus, artist or workplace statement) when claiming that a field has changed.
  4. Recommend one subject-specific practice that keeps the intended thinking visible to a teacher, coach, or employer.
  5. Apply district-approved-tool rules and FERPA limits to any live demonstration used in class.

Key vocabulary

Generative AI (GenAI)
Systems trained to produce new text, images, audio, code, or other media from a prompt, rather than only classifying or predicting a label.
Authorship
The question of who is responsible for a work’s ideas, wording, and claims, including who may take credit and who may be held to account.
Assessment validity
Whether a task still measures the skill it was designed to measure after students can obtain fluent output from a tool.
Cognitive offloading
Handing a thinking step to a tool. Helpful when the goal is speed; harmful when the assignment existed to grow that thinking.
Synthetic media
Text, images, audio, or video created or heavily modified by AI, often hard to distinguish from human-made work at a glance.
Commonplace adoption
The period after a technology leaves specialist labs and becomes an ordinary option in consumer software, schools, and workplaces.
Human-in-the-loop
A design in which a person sets the purpose, checks the output, and remains responsible for the decision that follows.

Teacher background

When consumer chatbots and image generators arrived in late 2022, they did not stay inside computer science. Idaho students now meet generative AI in the word processor, the studio, the notation app, the graphing tool, and the social feed. This lesson treats that shift as an ethical event. The standard asks students to evaluate implications of how AI has changed since GenAI became commonplace, and the state's example points teachers toward writing, music, art, social media, and mathematics. Ethics here is larger than cheating. Authorship, credit, labor, assessment validity, and the volume of synthetic text in public life all belong in the room. A junior who pastes a prompt and submits the result has not practiced the thinking the assignment was designed to grow. A senior who uses a district-approved tool as a second reader, then revises with a human teacher, is doing something different. Students must name that difference and defend a position with dated evidence: a syllabus, a workplace rule, an artist statement, a school policy. Keep the tone civic. Do not preach that GenAI ruined school, and do not sell it as inevitable progress. Pair pre-2022 and post-2022 artifacts. If live tools are blocked or bandwidth is thin, print the artifacts. Never upload student essays, names, or grades to an unapproved service. FERPA still governs education records, and Idaho districts decide which tools are approved.

Materials

  • Printed station packets: Writing, Music, Art, Social media, Mathematics (one folder per table).
  • Paired artifacts for each station: a pre-2022 task and a 2024–2026 version of a similar task, with dates visible.
  • Four-lens evaluation card: Authorship / Labor and pay / Assessment validity / Public discourse.
  • Excerpt of the school or district acceptable-use policy and the list of approved digital tools, if one exists.
  • Timer, sticky notes, and a board space titled What changed / What should not change.
  • Offline fallback: all live demos replaced by printed screenshots of GenAI output already collected by the teacher; no student accounts required.

Before class

  • Confirm whether any district-approved GenAI tool may be shown. If not, run the entire period on paper.
  • Date every artifact. Undated screenshots invite folklore instead of evaluation.
  • Remove student names from any sample work. Use public or teacher-created examples only.
  • Plan table groups of three or four. Assign a recorder, a skeptic, and a timekeeper.
  • For a 90-minute block, add a 20-minute seminar after independent practice and a 20-minute evidence paragraph; keep the same success criteria.

Instructional sequence

Warm-up — Date the flood

5 min
  1. Display two unlabeled writing samples of similar length: one clearly pre-chatbot student draft (awkward, specific, local) and one fluent generic GenAI paragraph on the same prompt.
  2. Students vote silently: Human 2021, Human 2026, or Tool 2026. Do not reveal the key yet.
  3. Collect two sentences on scrap paper: What would have to be true for this to be honest work? What would have to be true for a teacher to still see the student’s thinking?
  4. Tell students the standard in full and that today’s job is evaluation, not a product review.

Direct instruction — Four ethical lenses, not one honesty rule

10 min
  1. Write the standard on the board. Underline ethical implications and since GenAI has become commonplace. The comparison is historical, not hypothetical.
  2. Teach the four lenses with a single Idaho English example: a junior research paper. Authorship (who wrote the claims). Labor (who used to be paid to copy-edit or illustrate). Assessment validity (does the paper still show research skill). Public discourse (what happens when the same fluent filler fills letters to the editor).
  3. Show the standards example: each content area can focus on writing, music, art, social media, math. Tell students they will rotate through those fields, not stay in computer science.
  4. Name the trap: treating every GenAI question as cheating. Cheating is one implication. It is not the whole map.
  5. State the privacy rule before any tool talk: no student names, grades, or essays enter an unapproved system.

Guided practice — Work one station together

10 min
  1. Project the Writing station: a 2019 peer-conference protocol versus a 2025 assignment that allows a district-approved chatbot as a second reader with a required process log.
  2. As a class, fill the four-lens card. Push for specifics: who is credited, who is unpaid, what the teacher can still see, what happens if the log is fake.
  3. Model citing a dated source. A 2025 university syllabus or a district academic-integrity addendum beats I heard everyone uses it.
  4. Ask one challenge question: If the process log is required, has the ethical problem been solved or only documented?

Independent practice — Evaluate two fields

12 min
  1. Pairs take two remaining stations (Music, Art, Social media, or Mathematics) and complete a four-lens card for each.
  2. Require one dated artifact citation per station. If the packet has none, students must write what evidence they would need and why the claim is incomplete.
  3. Each pair writes a six-sentence evaluation: what changed, what ethical cost appeared, what practice would keep human thinking visible.
  4. Circulate with a clipboard: check that students are using the lenses, not writing GenAI is good/bad.

Real-world examples

  • An Idaho English department that still requires in-class handwritten first drafts for certain essays, then allows a spell-checker on the typed revision.
  • A high-school band that uses an AI mastering plug-in for a pep-band recording and must decide whether the mix is student work for a contest.
  • A yearbook staff using generative fill on photos of a football crowd, raising questions about whether people who were not there appear to have been there.
  • A math class in which a chatbot produces a fluent but wrong proof of a trig identity, and the student cannot find the invalid step.
  • Local Facebook groups and campaign pages flooded with generic synthetic comments during a school-bond discussion.

Hands-on activity

Hands-on — Gallery of what changed

8 min
  1. Post one claim from each station on the board under What changed and What should not change.
  2. Students add a sticky note that either cites the packet or challenges the claim as undated.
  3. Quick stand-up: one student from Writing and one from Mathematics read a recommended classroom practice.
  4. If the period is short, skip the stand-up and collect the four-lens cards as the artifact.

Discussion questions

  1. Is a student who uses GenAI to outline a history paper and then writes every sentence themselves doing the same ethical act as a student who submits the outline’s prose?
  2. If an AI image generator can imitate a living Idaho illustrator’s style, who owes whom what?
  3. Should a mathematics teacher ban chatbots, redesign tasks, or do both? What evidence would tell you the choice is working?
  4. When synthetic comments fill a public hearing record, whose speech is being amplified, and whose is being drowned?
  5. What is the difference between a tool that checks work and a tool that replaces the work the course exists to teach?

Differentiation

Support

  • Provide sentence frames for the four-lens card: The dated source shows… The ethical cost is… A practice that keeps thinking visible is…
  • Allow students to evaluate one station in depth instead of two if processing speed is a barrier.

Challenge

  • Ask students to draft a one-page content-area addendum for English, art, or mathematics that a department could actually vote on.
  • Require a counter-argument: name the strongest case that GenAI improved access or feedback quality, then answer it.

Multilingual learners

  • Pre-teach authorship, validity, and commonplace. Provide the four-lens card in English with space for notes in the student’s strongest language.
  • Invite comparison to how translation tools changed writing in a first language, without requiring students to disclose immigration status.

IEP / 504

  • Offer oral dictation of the six-sentence evaluation to a scribe or speech-to-text on a district device that does not send work to a consumer model.
  • Print large-type packets. Do not require simultaneous reading of two dense artifacts; sequence them.

Assessment

Formative

  • Four-lens cards checked for use of dated evidence rather than slogans.
  • Warm-up scrap sentences collected as a pre-assessment of honesty versus thinking.

Summative

  • Six-sentence evaluation of two content areas, scored on lenses used, evidence dated, and a concrete recommended practice.
  • Block extension: a 300-word seminar paper answering whether GenAI changed the purpose of a chosen course.

Success criteria

  • Names a specific change in at least two fields after GenAI became commonplace.
  • Uses at least two of the four ethical lenses with a dated citation.
  • Proposes a practice that keeps human thinking visible rather than only a ban or only permission.

Responsible use

Use only district-approved tools, and only with teacher-provided prompts. Students do not need personal GenAI accounts for this lesson. If a live demo is used, the teacher runs it on a school account and projects the result. Offline fallback is the intended default in buildings with blocked sites or thin bandwidth: printed, dated artifacts are sufficient to meet the standard.

Ethics

The ethical task is evaluation of a historical change, not loyalty to a brand or a ban. Students should be able to hold two facts at once: GenAI can give faster feedback, and it can hide whether a student ever did the thinking the course exists to grow. Credit, labor, and public discourse are in scope. Mockery of classmates who use or refuse tools is out of scope.

Privacy

FERPA protects education records, including student essays, grades, and identifiers. Do not paste student writing, names, or ID numbers into a consumer chatbot. Do not ask students to upload personal work for a class demo. Public or teacher-created samples only. Directory information is still not a license to feed a class roster to a model.

Reflection

  1. Which lens was hardest to apply, and what evidence would make it easier next time?
  2. Where in your own courses do you already use GenAI, and what thinking might be getting skipped?
  3. What should a teacher still be able to see in your work if a tool is allowed?

Homework

Bring one dated artifact from a class you take (syllabus line, rubric, contest rule, or assignment sheet) that either names GenAI or is silent about it. Write eight sentences evaluating the ethical implication of that silence or that rule. Do not upload the artifact to a tool; mark it on paper.

Closing

Reveal the warm-up key. Restate that commonplace GenAI changed more than the cheating conversation. Collect four-lens cards. Tomorrow’s question is not whether tools exist; it is who the door of those tools actually opens for.

Extensions

  • 90-minute block: 20-minute Socratic seminar on whether assessment validity can be repaired without banning tools, then 20 minutes of evidence writing.
  • Invite a teacher from art, music, or mathematics to spend eight minutes describing what they can no longer see in student work.
  • Compare this district’s academic-integrity language from 2019 and the current version; annotate what was added after GenAI.
  • Track one Idaho news comment thread for a week and tally likely synthetic versus specific local posts (no scraping of personal profiles).

Cross-curricular links

English Language Arts
Process logs, in-class drafting, and citation of tools as sources of language, not of authority.
Visual and performing arts
Style imitation, contest rules, and whether a generated image or mix meets the course’s definition of original work.
Mathematics
Proof and worked reasoning as the thing the course teaches; fluent wrong answers as an assessment-validity problem.
Civics / media
Synthetic comments in local public comment, school-board hearings, and campaign pages.

Back to contents

AI Impact · Ethics and Privacy

9-12.AII.EP.2

Who Gets a Better Door

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Analyze how AI tools shape user experiences for people with diverse backgrounds and characteristics.

Example from the standards. Real-time translation tools and AI-driven accessibility features (like speech-to-text for the hearing impaired or image-to-text descriptions for the visually impaired) remove barriers for non-native speakers and people with disabilities.

Student-friendly learning targets

  • I can analyze how the same AI feature creates different experiences depending on language, disability, accent, bandwidth, and cost.
  • I can give a precise example of an accessibility gain and a precise example of a remaining barrier or new harm.
  • I can recommend a design or policy change that would make a tool more usable without treating any group as a test afterthought.

Essential questions

  1. When an AI tool opens a door, who walks through first, and who still finds a step they cannot climb?
  2. How do translation, captions, and image descriptions both remove barriers and introduce new errors?
  3. What would it mean to design AI so that diverse users are expected users, not exceptions?

Objectives

  1. Analyze at least three user profiles (language, sensory disability, and one additional characteristic such as accent, literacy, rural bandwidth, or age) against the same AI feature.
  2. Distinguish access (can the person use the tool) from quality (does the tool work as well for them as for the default user).
  3. Evaluate a translation or accessibility feature for both barrier removal and error risk in high-stakes settings (health, legal, school).
  4. Propose one design or school-policy change that treats disabled and multilingual users as intended users.
  5. Follow FERPA and disability-privacy rules: no student is required to disclose a diagnosis to participate.

Key vocabulary

Accessibility
The degree to which a product can be used by people with a wide range of abilities, including vision, hearing, mobility, and cognitive differences.
Default user
The unspoken person a product was designed around, often English-speaking, sighted, hearing, urban, and well connected to broadband.
Real-time translation
Automatic conversion of speech or text from one language to another with little delay, useful and error-prone in the same moment.
Speech-to-text
A system that converts spoken language into written text; accuracy often varies by accent, microphone, and background noise.
Image-to-text / alt text
A description of an image generated for people who cannot see it, or who need text that a screen reader can speak.
Inclusive design
Building for the edges of human variation from the start, rather than adding an accommodation after a product ships.
Error cost
What happens when the tool is wrong: a missed joke is cheap; a mistranslated medical or legal phrase is not.

Teacher background

The standards example is clear: real-time translation, speech-to-text, and image descriptions can remove barriers for non-native speakers and for people with disabilities. That gain is real and should be taught as real. The analysis the standard asks for is not a celebration of features. It is a study of how the same tool shapes experience differently depending on who the user is. A captioning model that works on a quiet classroom recording may fail on a gym pep rally. A translation app that handles cafeteria Spanish may mangle a parent letter about special education rights. A voice assistant that hears a Treasure Valley newscaster may not hear a student whose first language is Somali or whose speech is dysarthric. Rural bandwidth is also a characteristic of users in Idaho: a feature that requires a live connection is not an open door in every district. Teach access and quality as separate questions. Teach that disabled and multilingual people are expected users, not afterthoughts. Do not require any student to disclose a disability, language spoken at home, or immigration status. Use public, teacher-created personas. FERPA and disability records stay closed. Offline fallback: printed screenshots of captions, alt text, and translation output, plus a paper user-experience matrix.

Materials

  • Printed user-experience matrix: rows are features (translation, speech-to-text, image description, voice assistant); columns are user characteristics.
  • Five teacher-written personas on cards: a parent who prefers Spanish; a student who is Deaf and uses captions; a student who is blind and uses a screen reader; a student with a rural satellite connection; a student whose accent the model often misses. No real student data.
  • Printed screenshots: a good alt-text example, a bad or invented alt-text example, a translation that is fluent but wrong on a rights-related phrase.
  • Error-cost scale: Low (inconvenience) to High (health, legal, discipline, or rights).
  • Offline fallback: no live microphone tests on students; all audio examples are teacher-recorded public-domain or staff-read text.

Before class

  • Audit personas so none resemble a specific student in the room.
  • If you demonstrate captions, use a school device and a prepared clip, not a student speaking on the spot.
  • Print a short excerpt of the district accessibility or language-access policy if one exists.
  • Tell the special education case manager you will not be asking students to self-identify.
  • Block plan: extend the seminar to argue whether schools should require human review of AI translation for IEP and discipline documents.

Instructional sequence

Warm-up — Same door, different step

5 min
  1. Show a photo of a school entrance with an automatic door, a curb cut, and a narrow side gate. Ask: who is this entrance for?
  2. Translate the metaphor: software has doors too. Captions, translation, and alt text are doors. So are default English menus and required live video.
  3. Students jot one AI feature they use and one person for whom that feature might fail. No names of classmates.
  4. Read the standard and the state’s example aloud. Tell students analysis means gains and remaining barriers.

Direct instruction — Access is not the same as quality

10 min
  1. Define accessibility, default user, and error cost with the state’s three examples: translation, speech-to-text, image-to-text.
  2. Walk a Magic Valley dairy-family example: a Spanish-language auto-translation of a school attendance letter that turns unexcused into a harsher legal term. The door opened; the quality failed; the error cost is high.
  3. Walk a captions example from a noisy gym livestream of a playoff game: access exists on paper, quality collapses with crowd noise.
  4. Name rural bandwidth as a characteristic, not a complaint: an Idaho student on a metered satellite link does not have the same experience as a Boise student on fiber.
  5. Set the privacy rule: we analyze personas, not classmates’ medical or language histories.

Guided practice — Score one persona as a class

10 min
  1. Project the screen-reader persona using image-to-text on a science worksheet that is actually a photographed diagram with no true alt text.
  2. Fill the matrix: access (the tool runs), quality (the description misses the labeled parts of the cell), error cost (the student cannot study the diagram).
  3. Ask: is the ethical failure the student’s, the teacher’s, or the tool’s training and design?
  4. Model a recommendation: require human-written alt text on instructional images; treat AI description as a draft, not a substitute.

Independent practice — Matrix for three personas

12 min
  1. Pairs receive three persona cards and complete the matrix for one feature per persona.
  2. Each pair must record one gain that matches the standards example and one remaining barrier or new harm.
  3. Write a ten-line analysis: how the tool shapes experience, not whether the student likes the brand.
  4. A third of the class should take the rural-bandwidth persona so Treasure Valley defaults do not dominate.

Real-world examples

  • District auto-translation of a parent newsletter that is serviceable for sports schedules and unreliable for special-education rights.
  • Live captions at a school board meeting that help Deaf attendees and also leak errors into the public minute-taking stream.
  • Image descriptions that call a tribal regalia photo a costume, a harm that is cultural as well as technical.
  • Speech-to-text that underperforms for students with regional or additional-language accents during oral quizzes.
  • A premium accessibility tier that works well only for families who can pay, turning a door into a ticketed entrance.

Hands-on activity

Hands-on — Redesign the door

8 min
  1. Groups pick one high error-cost cell on the matrix and write a three-part redesign: product change, school practice, and human backup.
  2. Post redesigns. Peers star any proposal that still treats disabled users as extra.
  3. Teacher reads one strong proposal that names a human backup for IEP or medical language.
  4. Collect matrices. If time remains, vote on which redesign a school could implement this year without a new vendor.

Discussion questions

  1. If a translation is free and instant, why might a school still need a human interpreter for a discipline meeting?
  2. Who is the default user of the tools this school actually issues?
  3. When alt text is wrong, is that a technical glitch or a civil-rights problem?
  4. Should families have to disclose a disability to receive a tool that everyone might benefit from (captions, transcripts)?
  5. How should rural bandwidth change what a district calls an equitable digital experience?

Differentiation

Support

  • Provide a completed sample matrix row. Students fill two empty rows by analogy.
  • Allow bullet analysis instead of a ten-line paragraph.

Challenge

  • Research WCAG-style alt-text guidance and rewrite the science-diagram description to a standard a screen-reader user could study from.
  • Write a one-page memo to a principal on when AI translation is acceptable and when a qualified interpreter is required.

Multilingual learners

  • Invite students to judge a printed translation into a language they know, if they choose to, without being appointed class translator.
  • Provide the matrix headings in English with student-generated glosses.

IEP / 504

  • Do not call on students with disabilities to testify. Personas carry that load.
  • Offer extended time on the written analysis and a quiet copy of all screenshots.

Assessment

Formative

  • Matrix cells checked for both a gain and a barrier.
  • Listening for whether students separate access from quality.

Summative

  • Ten-line analysis plus one redesign proposal scored on specificity, error cost, and a human backup.
  • Block extension: seminar argument on AI translation of IEP documents, with a written position of 250–400 words.

Success criteria

  • Analyzes at least two characteristics, not a single disabled-user stereotype.
  • Uses the standards examples (translation, speech-to-text, or image description) with a concrete error-cost judgment.
  • Recommends a change that includes a human backup for high-stakes language.

Responsible use

Do not record classmates to test speech-to-text. Do not upload photos of students to an image-description tool. Teacher-prepared public or staff-created media only. Offline packets meet the standard. If a district-approved captioning tool is demonstrated, the teacher operates it.

Ethics

Accessibility gains in the standards example are genuine and should be stated as genuine. Analysis still requires naming who remains outside the door, including people whose accents, languages, bandwidth, or bodies were scarce in training data. Charity framing (helping them) is weaker than rights framing (the product was incomplete).

Privacy

Disability status, IEP content, and home language are sensitive. FERPA covers education records; additional disability-privacy norms apply. Students must not be asked to disclose diagnoses to complete the matrix. Personas are fictional. Do not put a real student’s accommodation plan into any AI tool.

Reflection

  1. Which characteristic was easiest to forget when you pictured the default user?
  2. Where does this school already provide a human backup for machine translation or captions?
  3. What is one feature you use that probably works better for you than for someone else in this building?

Homework

On paper, pick one tool you used this week. Complete a mini-matrix for two fictional users who are not you. Note access, quality, and error cost. Do not test the tool on a person without their consent, and do not upload anyone’s voice or image.

Closing

Return to the automatic-door image. A door that opens for some and sticks for others is still a design choice. Collect matrices. The next lesson asks what it costs, in energy, water, consent, and labor, to collect the data those doors were trained on.

Extensions

  • 90-minute block: seminar on whether schools should forbid AI-only translation of special-education and discipline documents, then a policy paragraph.
  • Audit five pages of the school website for alt text using a teacher-controlled checker; report patterns, not student work.
  • Interview (with permission) a district interpreter or captioner about what tools help and what they still must redo.
  • Compare mobile captions on a pep-rally video versus a classroom lecture; quantify missed proper nouns.

Cross-curricular links

World languages
What translation can and cannot do; when a fluent wrong phrase is worse than no translation.
Health science
Error cost of medical speech-to-text and why clinics still need human review.
Civics
Language access at public meetings and school-board hearings as a civic, not merely technical, duty.
Special education / advisory
Captions, transcripts, and alt text as ordinary instruction, not a favor.

Back to contents

AI Impact · Ethics and Privacy

9-12.AII.EP.3

The Cost of a Billion Examples

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Explore the societal, environmental, and ethical implications of large-scale data collection and processing and how this relates to AI applications.

Student-friendly learning targets

  • I can connect large-scale data collection to the AI applications that depend on it, including energy, water, consent, and labeling labor.
  • I can explain why data-center loads matter in an arid Western state that is recruiting those facilities.
  • I can distinguish data I agreed to give a school from data a company infers or scrapes without a meaningful yes.

Essential questions

  1. What does a billion training examples actually cost in energy, water, consent, and human labeling?
  2. Who benefits when Idaho recruits data centers, and who competes for the same electricity and water?
  3. If an application is useful, does that settle the ethics of how its data was collected and processed?

Objectives

  1. Map an everyday AI application backward to data collection, processing, storage, and inference.
  2. Analyze competing claims on electricity and water in an arid Western grid that also irrigates farms and cools towns.
  3. Evaluate consent: terms of service, inferred data, scraped public posts, and school records under FERPA.
  4. Describe labeling labor as real work, often low-paid and sometimes psychologically costly, not as a magic pipeline.
  5. Write a position that holds usefulness and cost in the same paragraph, without boosterism or panic.

Key vocabulary

Training data
The examples a model is shown during development so it can learn patterns; scale is often described in billions of tokens or images.
Data center
A facility packed with servers that store data and run computation, including model training and inference, using large amounts of electricity and often water for cooling.
Inference
The work a trained model does when it answers a new prompt; each query has an energy cost, usually smaller than training but repeated millions of times.
Consent
A meaningful agreement to collect and use data. A buried terms-of-service clause is legally common and ethically thin.
Labeling labor
Human work of tagging, rating, transcribing, or filtering examples, including toxic content, so models can learn and so outputs can be moderated.
Scraping
Automated collection of data from websites or platforms, often without a person-by-person request.
Externalities
Costs borne by people who did not choose the transaction: drought-stressed aquifers, grid strain, or underpaid raters overseas.

Teacher background

Large models exist because large data collection and processing exist. This lesson asks students to explore societal, environmental, and ethical implications of that scale and to tie them back to applications they already use. Idaho is actively recruiting data-center investment. That is an economic development fact, not a verdict. Data centers bring tax base, construction, and a small number of permanent jobs. They also draw electricity on a grid that serves farms, homes, and industry, and many designs use water for cooling in a region that already irrigates from the Snake River Plain aquifer and watches snowpack. Students should be able to state those tensions without turning class into a rally. Consent is the second strand: public posts, scraped books, school-issued accounts, and inferred profiles are not the same kind of yes. Labeling labor is the third: people, often contractors far from Idaho, rate toxic content and tag images so that applications look smooth. Use public figures of record (utility integrated resource plans, county hearing notices, company sustainability pages) and label them as claims, not gospel. Do not assign students to scrape the web or to upload classmates’ posts. FERPA still forbids treating student records as convenient training fuel. Offline fallback: printed utility excerpts, a water-budget worksheet, and a labeling-labor testimony excerpt from a reputable news investigation.

Materials

  • Three-strand packet: Energy and water / Consent / Labeling labor, with short dated excerpts.
  • Idaho water-and-power worksheet: a simplified budget with households, irrigation, existing industry, and a hypothetical large computing load. Numbers are rounded and labeled as a teaching model, not an audit.
  • Consent ladder poster: explicit yes, account terms, inferred data, scraped public posts, no notice.
  • One excerpt describing content-moderation or data-labeling work (teacher-selected, not graphic).
  • Offline fallback: no live maps that require student logins; printed facility-siting hearing excerpts if a local proposal exists, otherwise a generic arid-West scenario clearly marked as hypothetical.

Before class

  • Check whether a data-center proposal is currently before a nearby county. If yes, use public hearing documents. If no, use a labeled hypothetical so you do not invent a local deal.
  • Sanitize the labeling excerpt for graphic violence; the point is labor, not shock.
  • Coordinate with a science colleague if you want snowpack or irrigation numbers that match a recent water year.
  • Block plan: extend into a written policy brief for a county commissioner: benefits, grid and water costs, consent conditions, labor standards.

Instructional sequence

Warm-up — Bill the query

5 min
  1. Students estimate, on a sticky note, what one chatbot answer costs in electricity. Collect wild guesses without mocking them.
  2. Tell them honest published estimates vary and that the bigger civic question is scale: millions of queries, plus training, plus cooling, plus the buildings Idaho is recruiting.
  3. Write three words on the board: energy/water, consent, labor. Today’s exploration has to touch all three.
  4. Read the standard. Emphasize explore and how this relates to AI applications, not only to warehouses on the horizon.

Direct instruction — From application back to the warehouse

10 min
  1. Pick one application students know: a photo search, a chatbot, a translation app. Draw backward: device, network, inference, training, data collection, labeling.
  2. Define data center in Idaho terms: siting near transmission, tax incentives, construction jobs, modest permanent staffing, large continuous load.
  3. Show the water tension without theater: irrigation on the Snake River Plain, municipal use, drought years, evaporative cooling. Competing goods, not a cartoon villain.
  4. Introduce the consent ladder and labeling labor as ethical, not only environmental, costs of the same pipeline.
  5. Remind students that student records are not public training data. FERPA is a consent floor, not a suggestion.

Guided practice — Run the Idaho budget together

10 min
  1. Project the simplified power-and-water worksheet. Allocate a hypothetical large load. Ask what gets delayed: a housing development, a cold-storage plant, a farm pump, a school?
  2. Force a tradeoff sentence: If commissioners say yes, the benefit is… and the competing use is…
  3. Place one consent example on the ladder: a public Instagram photo used in a vision model. Where is the yes?
  4. Read two sentences of the labeling excerpt. Ask what the application’s smoothness hid.

Independent practice — Three-strand brief

12 min
  1. Individually, students write a 12–15 line brief on one application (maps, chat, image tools, recommendation feeds) covering environment, consent, and labor.
  2. Require one dated source from the packet and one explicit uncertainty (what the packet does not prove).
  3. No empty adjectives: do not write devastating or revolutionary. Write quantities, parties, and unknowns.
  4. If a student finishes early, add who captures the tax benefit and who lives next to the substation.

Real-world examples

  • County hearings in the Treasure Valley or Magic Valley on large computing loads, transmission upgrades, and water rights, using only public documents.
  • Idaho Power and other utilities planning for industrial electrification and large new loads in integrated resource materials.
  • A farmer on the Snake River Plain competing for water in a low-snowpack year while a cooling system evaporates water elsewhere in the basin.
  • Contract raters overseas labeling toxic content so a U.S. chatbot can refuse it quickly.
  • A school-issued account whose clickstream is processed under a vendor contract the student never read.

Hands-on activity

Hands-on — Consent ladder and labor station

8 min
  1. Half the class sorts five data examples onto the consent ladder and must justify each placement in one sentence.
  2. The other half lists what a fair labeling job would include (pay, trauma support, time limits, the right to refuse a queue) and what applications would get slower if that labor were treated as skilled work.
  3. Swap for three minutes if time allows; otherwise jigsaw report out.
  4. Collect the briefs. Star any brief that related costs back to a specific application rather than to data centers in the abstract.

Discussion questions

  1. If a data center pays taxes and uses legal water rights, is the ethical question settled?
  2. Should people whose public posts were scraped be able to opt out of training, even if they posted in public?
  3. Who should pay for grid upgrades: ratepayers, the company, or the state that recruited the facility?
  4. Is labeling toxic content a job we should automate, a job we should improve, or both?
  5. Does a useful translation app change how you judge the warehouse that makes it cheap?

Differentiation

Support

  • Provide a brief template with three labeled boxes: Environment, Consent, Labor, plus a sentence starter for uncertainty.
  • Allow a partner for the worksheet math; the writing remains individual.

Challenge

  • Compare training cost versus inference cost and argue which policy lever (siting, pricing, model size, query limits) actually moves the total.
  • Read a utility excerpt and identify one assumption a student would want cross-examined at a hearing.

Multilingual learners

  • Pre-teach aquifer, grid, consent, and contractor. Allow the brief’s first draft in the student’s strongest language with an English glossary of the three strands.
  • Note that labeling labor is often multilingual work done far from the product’s users.

IEP / 504

  • Provide a calculator and a simplified worksheet with fewer line items.
  • Accept a structured oral brief recorded on a school device that does not sync to a consumer model.

Assessment

Formative

  • Warm-up estimates and tradeoff sentences during the worksheet.
  • Consent-ladder placements with a justifying clause.

Summative

  • 12–15 line three-strand brief scored on application link, dated source, named uncertainty, and civic tone.
  • Block extension: 400-word commissioner brief with a recommended condition (water reporting, labor standard, or consent rule).

Success criteria

  • Addresses environment, consent, and labeling labor, not only one.
  • Connects costs to an AI application, not only to a building.
  • States a benefit and a cost without slogans.

Responsible use

Students do not scrape websites, ping data centers, or attempt to measure a facility. Public documents and teacher packets only. No student should enter a personal account password or download a dataset of social posts. Offline printed excerpts are the core materials.

Ethics

Usefulness of AI applications does not erase environmental, consent, or labor costs; costs do not erase usefulness. Civic tone means stating who benefits, who pays, and what is unknown. Do not assign collective guilt to students for using a search bar. Do not sell data centers as destiny.

Privacy

School records, counseling notes, and classwork are not training data for public models. FERPA requires parent or eligible-student rights over education records and limits disclosure. Vendor contracts may still process metadata; students should know the difference between a district agreement and a consumer app’s terms. Do not collect classmates’ posting history as a project.

Reflection

  1. Which strand (energy/water, consent, labor) did you know least about this morning?
  2. What number in the worksheet would you want a journalist to verify before a county vote?
  3. How will this change, if at all, which applications you treat as cheap?

Homework

Read one public document (utility FAQ, county agenda item, or company water statement) provided on paper or a district site. Annotate one benefit claim and one missing number. Bring questions, not a rant.

Closing

Hold up the three words again. A billion examples are not free. Collect briefs. Next class asks what happens when those examples were taken without asking writers, artists, photographers, and people who posted in public.

Extensions

  • 90-minute block: seminar on siting conditions, then a commissioner brief.
  • Guest from a utility, county planning, tribal water staff, or farm bureau, with a recorded backup for rural bandwidth days.
  • Compare two companies’ public water claims and list what a journalist would still need to verify.
  • Trace one school-approved app’s privacy policy for training-use language; report clauses, not rumors.

Cross-curricular links

Environmental science
Water budgets, evaporative cooling, snowpack, and competing beneficial uses.
Economics / government
Tax incentives, ratepayers, local control of siting, and who captures benefits.
Statistics
Orders of magnitude, uncertainty, and why a single query cost does not describe a billion-example system.
Geography
Transmission corridors, arid-West climate, and why companies look at Idaho.

Back to contents

AI Impact · Ethics and Privacy

9-12.AII.EP.4

Used Without Asking

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Assess how unauthorized data collection has influenced the practice of training AI models.

Example from the standards. An AI model is trained on art without the artist's permission which can lead to legal implications and can change the training process.

Student-friendly learning targets

  • I can assess how training on writers’, artists’, photographers’, and public social posts without permission has changed both lawsuits and training practice.
  • I can explain why fair use is a contested argument in this setting, not a rule I can recite as settled law.
  • I can describe at least one way a training process might change in response to unauthorized-data claims (licensing, filtering, attribution, opt-out).

Essential questions

  1. If a work was posted or published, was it offered as training fuel?
  2. What is the difference between a fair-use argument and a property argument, and why have courts not handed schools a slogan?
  3. How should training practice change when permission was never asked?

Objectives

  1. Assess unauthorized collection across four source types: writers, artists, photographers, and public social posts.
  2. Present fair use and licensing/property claims as competing arguments with evidence, not as a verdict.
  3. Trace at least one legal implication to a concrete change in training practice (data filtering, licensed corpora, opt-out tools, synthetic data).
  4. Evaluate a student-posted photo or caption as a training example without using any real classmate’s account.
  5. Keep student work and names out of live models while discussing scraping of public web data.

Key vocabulary

Unauthorized collection
Gathering works or data for training without a license or a clear, informed agreement from the person who made or is depicted in them.
Fair use
A U.S. copyright doctrine that sometimes allows limited use of protected works without permission. Whether mass training qualifies is contested in courts and legislatures.
License
A permission to use a work under stated conditions, often in exchange for pay, credit, or limits on reuse.
Training corpus
The assembled collection of texts, images, or other examples used to train a model.
Opt-out
A mechanism that asks rightsholders to request removal after collection, shifting the burden onto the person who did not consent.
Style imitation
A model producing work that resembles a living creator’s distinctive manner, raising questions beyond exact copying.
Provenance
The record of where a training example came from and under what permission, if any.
Transformative use
A fair-use factor arguing that the new use serves a different purpose than the original; companies invoke it for training, and many creators reject it at this scale.

Teacher background

The standards example is an AI model trained on art without the artist’s permission, with legal implications that can change the training process. Widen that example in class to writers, photographers, and people who posted in public. Students should assess influence on practice: filtering copyrighted domains, buying licensed libraries, offering opt-outs, watermark research, and the use of synthetic data. They should not memorize a holding as if the Supreme Court had settled classroom policy. Fair use is a real doctrine with four factors. Whether copying millions of whole works to build a commercial generator is transformative remains a live dispute. Teach both arguments with equal care. A property argument says the copies were made to create a competing product without pay. A fair-use argument says the model learns statistical patterns, does not replace any single book in the ordinary sense, and would be impossible if every token needed a handshake. Neither argument is a personality test. Use public docket summaries and creator statements, dated. Do not download pirated book heaps with students. Do not scrape Instagram. Do not feed student art or essays into a generator to prove a point. FERPA and ordinary consent still apply. Offline fallback: printed creator statements, a blank four-factor fair-use grid, and fictional but realistic posting scenarios.

Materials

  • Four source packets: Writer, Artist (the standards example), Photographer, Public social post.
  • Fair-use factor grid (purpose, nature, amount, market effect) labeled Contested — not a verdict sheet.
  • Training-practice change cards: licensed corpus, domain filter, opt-out registry, attribution, paid residuals, synthetic data.
  • One public artist statement and one public company or researcher statement, both dated, both excerpted fairly.
  • Offline fallback: no live image-generator demos that imitate a living artist’s name; describe the practice in prose if needed.

Before class

  • Remove any living local student’s work from examples. Professional public cases only, plus fictional teen posting scenarios.
  • Read enough of a current case summary to avoid stating a reversed holding as law. If the law moved, say the date.
  • Print the standards example at the top of the Artist packet.
  • Block plan: full hearing with opening statements, cross on fair-use factors, and a written judgment that still admits uncertainty.

Instructional sequence

Warm-up — Posted is not the same as offered

5 min
  1. Display a fictional public photo: a student posts a concert picture from the Idaho Center. A vision model later trains on it. A generator produces a similar crowd scene for an ad.
  2. Students mark: permission, implied permission, no permission. No discussion yet.
  3. Add a second beat: a living illustrator’s portfolio, scraped, then a prompt in the style of…
  4. Read the standard and the art example. Tell students the law is disputed and that their job is assessment, not a fan vote.

Direct instruction — Four sources, two arguments, one training pipeline

10 min
  1. Name the four sources on the board. Unauthorized collection can be illegal, legal-but-contested, or merely unethical; students must not collapse those words.
  2. Teach fair use as four factors. Write Contested in large letters. Schools do not get a mnemonic that replaces litigation.
  3. Teach the property/licensing argument: wholesale copying to build a substitute market, unpaid.
  4. Show how practice already shifts when claims land: companies negotiate licenses with some publishers, publish opt-out forms, or claim they filtered certain domains. Those are influences on training, which is what the standard asks.
  5. FERPA note: a student’s unpublished essay in a learning-management system is not a public post. Different legal and ethical floor.

Guided practice — Argue the art example without a verdict

10 min
  1. Read the artist packet together. Fill the four-factor grid in two columns: strongest fair-use claim, strongest property claim.
  2. Ask which training-practice change would actually respond to the artist (a license, a filter, an opt-out after the fact, or nothing).
  3. Refuse a class vote on who won. The assessment is whether students can state both arguments with evidence.
  4. Point out style imitation: even if no single pixel is copied, a living artist’s market may still be affected. That is part of the dispute, not a solved lemma.

Independent practice — Assess a second source

12 min
  1. Pairs take Writer, Photographer, or Public social post and complete: unauthorized how, legal implication, likely change to training practice.
  2. Social-post pairs must address the teen-concert scenario without using real usernames.
  3. Writer pairs must address books and journalism, not only famous novelists: local reporters’ work can be in corpora too.
  4. Exit product: a twelve-line assessment that uses the word contested correctly.

Real-world examples

  • Visual artists discovering prompts that target their names after portfolio sites were crawled.
  • News organizations and book authors suing over wholesale copying of text into training sets.
  • Wedding and sports photographers whose images, once online for clients, reappear as generic stock-like generations.
  • Public social posts, including Idaho event photos, treated as free vision data because the privacy setting was public.
  • Companies announcing licensed deals with some publishers while still disputing fair use for other corpora — a change in practice under legal pressure.

Hands-on activity

Hands-on — Hearing: change the training process

8 min
  1. Each group draws a practice-change card and must argue how it would, or would not, answer unauthorized collection for their source type.
  2. Opt-out groups face a challenge: why is the burden on the artist after the scrape?
  3. Licensed-corpus groups face a challenge: who cannot afford to be in the licensed set, and whose work then disappears from culture the model can see?
  4. Record one unresolved question per group on the board. Uncertainty is a legitimate academic product.

Discussion questions

  1. Is a public Instagram photo more like a published newspaper (in the world) or more like a conversation that happened to be visible?
  2. If fair use protected training completely, what would happen to working illustrators’ commissions? If it banned training completely, what would happen to research?
  3. Should a student who posts a poem in a public hashtag expect it not to become a training sentence?
  4. Does paying some publishers and not others make the training process more ethical or only more expensive?
  5. How is a school essay stored in a district system different from a public post?

Differentiation

Support

  • Give a two-column notes sheet: Fair-use argument / Property argument, with factor prompts.
  • Allow students to assess the art example in greater depth instead of switching sources.

Challenge

  • Write a model card addendum describing provenance and known unauthorized sources, with a recommended mitigation.
  • Compare opt-out and opt-in as governance designs and argue which one matches the word permission.

Multilingual learners

  • Note that non-English writers are often in corpora without local legal support. Invite reflection without requiring personal publishing history.
  • Provide a glossary of copyright, license, and fair use with examples, not idioms.

IEP / 504

  • Provide large-print factor grids and a quiet copy of excerpts.
  • Accept a recorded oral assessment if writing speed is the barrier; content standards stay the same.

Assessment

Formative

  • Two-column fair-use grid from guided practice.
  • Listening for contested versus is illegal as a slogan.

Summative

  • Twelve-line assessment of a source type linking unauthorized collection to a training-practice change.
  • Block extension: a written judgment of 350 words that states both arguments and still ends in a recommended practice, with uncertainty named.

Success criteria

  • Treats fair use as contested, with at least one factor on each side.
  • Includes writers, artists, photographers, or public posts with a concrete example.
  • Names a change to training practice, not only a feeling about theft.

Responsible use

Do not run live prompts that name a living artist in order to imitate them. Do not download unauthorized book datasets. Do not scrape social platforms. Fictional teen posts and public, already-reported cases are enough. Offline packets are preferred.

Ethics

Creators’ unpaid labor and researchers’ need for large corpora are both facts. The ethical failure is pretending only one fact exists. Students should leave able to describe how unauthorized collection pushed some firms toward licenses and filters — influence on practice — without declaring the legal war over.

Privacy

Student essays, art, and photos stored by the school are education records or school work, not public web scrapes. FERPA and district policy limit disclosure. A public social post is still a person’s data; class will not harvest classmates’ accounts to illustrate the point. Use invented scenarios.

Reflection

  1. Which source type felt most like unauthorized collection to you, and which factor made the difference?
  2. What would an honest model card say about your own public posts?
  3. Where did you feel tempted to treat contested law as settled, and what pulled you back?

Homework

On paper, write a twelve-line policy for a student literary magazine: may archived poems be used to train a model, by whom, with what permission, and what happens if a graduate later objects. Do not paste the poems into a tool.

Closing

Return to Posted is not offered. Collect assessments. Name the four sources once more. Next class turns to cybersecurity, where the same dual-use pattern — a tool that writes and a tool that detects — has benefits, risks, and ethics of its own.

Extensions

  • 90-minute block: structured hearing plus a written judgment that a school board could read.
  • Invite a local photographer, journalist, or art teacher to describe commission markets; record a backup.
  • Compare two companies’ public training-data statements dated a year apart; list what changed.
  • Draft an opt-in policy for student publications (yearbook, literary magazine, news site) covering future training uses.

Cross-curricular links

Visual arts
Portfolio posting, style, and commission markets after generators.
English / journalism
Copyright, quotation, and whether a model that read a paper replaces the paper.
Government / law
How unsettled federal cases should be taught: competing arguments, dated holdings, no fake certainty.
Photography / CTE media
Client contracts, public galleries, and scraping of images posted for a different purpose.

Back to contents

AI Impact · Ethics and Privacy

9-12.AII.EP.5

Defense, Offense, and Dual Use

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Analyze the benefits, risks, and ethical implications of AI in cybersecurity.

Student-friendly learning targets

  • I can analyze AI in cybersecurity as dual-use: the same class of tools can support detection and can scale social-engineering attacks.
  • I can describe benefits of AI-assisted defense without claiming that software replaces human judgment in a security operations center.
  • I can explain ethical duties (including not practicing offensive techniques in class) that follow from dual-use power.

Essential questions

  1. If the same kind of model can draft a phishing email and flag one, who is responsible for which use?
  2. What benefits does AI actually add to defense, and what new risks does it add (speed, scale, voice cloning, over-trust)?
  3. What ethical lines should a high school, a hospital, a lab, and a county IT shop refuse to cross?

Objectives

  1. Analyze benefits of AI for detection, triage, and pattern-spotting in defensive cybersecurity.
  2. Analyze risks of AI-enabled social engineering, including phishing and voice cloning, at the level of effects — not methods.
  3. Map dual use: one capability, defensive and offensive applications, different duties.
  4. Apply an ethical rule for this classroom: no exploit how-tos, no live attack generation, defensive framing only.
  5. Recommend a human-in-the-loop practice for a school or clinic facing AI-speed threats.

Key vocabulary

Cybersecurity
The practice of protecting networks, accounts, and data from unauthorized access, disruption, or theft.
Dual use
A technology that can serve both protective and harmful purposes depending on who uses it and toward whom.
Phishing
A social-engineering attempt, often by email or message, to trick a person into giving access or information. Class studies published examples; students do not create new lures.
Detection
Defensive systems and people spotting suspicious messages, logins, or network behavior, sometimes with AI ranking alerts.
Voice cloning
Synthesizing a voice that resembles a real person, which can be used for accessibility or for fraud (vishing).
Alert fatigue
The point at which so many automated warnings arrive that humans start ignoring them, including the real ones.
Human-in-the-loop defense
Keeping a trained person responsible for high-impact actions (locking accounts, contacting law enforcement, paying a ransom demand) even when AI ranks the alerts.

Teacher background

AI is already inside cybersecurity as both a defensive aid and a way to scale old crimes. The standard asks students to analyze benefits, risks, and ethical implications — all three. Benefits include faster sorting of the flood of logs, spotting patterns a tired analyst might miss, and helping people with lower technical skill recognize a suspicious message. Risks include fluent phishing at scale, cloned voices of principals and parents, poisoned training data, and over-trust in a detector that still misses novel attacks. Dual use is the organizing idea: a language model that summarizes a threat report can also draft a convincing message. This classroom is defensive only. Do not demonstrate how to bypass a filter, how to write a better lure, or how to exploit a system. Use already-published awareness examples from CISA or similar public campaigns, printed. Idaho context is close: school districts face email compromise; hospitals are ransomware targets in every state; Idaho National Laboratory and county IT shops live with nation-state and criminal probing. Students heading to CTE networking, the Guard, or help-desk work need ethics before tricks. FERPA applies twice: student records are what attackers want, and class must not dump real incident tickets into a chatbot. Offline fallback: printed phishing-awareness mailers and a dual-use T-chart. No student-generated attack content.

Materials

  • Printed, already-published phishing-awareness examples (government or nonprofit). No live generation.
  • Dual-use T-chart: Capability / Defensive use / Harmful use / Ethical duty.
  • Roles cards: school tech director, hospital privacy officer, county clerk, student help-desk intern, parent who received a fake principal voicemail.
  • FERPA reminder card: education records are high-value targets; class does not inspect real student data.
  • Offline fallback: entire lesson on paper. No security-tool logins, no password-cracking utilities, no dark-web tourism.

Before class

  • Strip any local incident details that would identify a staff member or student. Public patterns only.
  • Tell administration you are teaching defensive analysis, not a hacking unit.
  • If a guest from county IT, a hospital, or INL education outreach is available, schedule them; keep a recorded backup.
  • Block plan: longer case seminar on a fictional district email compromise and a written human-in-the-loop protocol.

Instructional sequence

Warm-up — Two inboxes

5 min
  1. Hand out two printed messages about a password reset: one from a public awareness campaign (already flagged) and one ordinary school notice. Students mark suspicious / not sure / looks fine. They do not click anything; there are no links.
  2. Debrief only on observable features the awareness campaign already teaches (urgency, unexpected sender), not on how to improve an attack.
  3. Write dual use on the board. Tell students a model that helps write clear school notices can also write urgent fakes.
  4. State the classroom rule: we analyze effects and duties. We do not manufacture lures or exploits.

Direct instruction — Benefits, risks, ethics — all three

10 min
  1. Benefits: ranking alerts, clustering similar events, summarizing long logs, assisting users who are not specialists, catching some malware families by pattern.
  2. Risks: scale of social engineering, voice cloning of a superintendent or a grandparent, attackers using the same detectors to test what gets through, alert fatigue, false confidence.
  3. Ethics: who is targeted (new staff, non-native English speakers, busy nurses), whether a school should use offensive tools, responsible disclosure versus showing off, duty to report.
  4. Idaho map: district business offices, clinic billing, city utilities, lab research networks. Same dual-use pattern, different consequences.
  5. Re-state: no how-to for offense. If a student asks, the answer is we will not practice that here.

Guided practice — Fill one dual-use row together

10 min
  1. Capability: generate fluent natural language. Defensive use: draft a clear password-reset notice in plain English and translate it. Harmful use: scale phishing. Ethical duty: schools may use generation for official notices on approved systems; students do not generate lures, even as a joke.
  2. Add voice cloning as a second row at the level of effects: accessibility for a teacher who lost their voice versus a fake principal call about an unpaid fee.
  3. Ask who is most exposed: a new secretary, a nurse on night shift, a parent who is not a native English speaker. Connect to EP.2 without turning this into a blame session.
  4. Draft a human-in-the-loop rule: AI may rank; a person confirms before anyone pays, sends money, or unlocks a roster.

Independent practice — Role analysis

12 min
  1. Each student draws a role card and writes a ten-line analysis: one benefit they would want, one risk they fear, one ethical rule they would write into policy.
  2. Hospital roles must mention patient privacy; school roles must mention FERPA; county roles must mention public records and elections systems at a high level, not attack details.
  3. Intern roles must include what they will refuse to do even if a friend dares them.
  4. No diagrams of network exploits. If a student starts to write steps, redirect to effects and duties.

Real-world examples

  • School district business offices targeted by urgent payment-change emails, now sometimes more fluent than they were five years ago.
  • Hospitals facing ransomware that disrupts care; defensive AI used to spot unusual encryption behavior — with human authority over shutdowns.
  • A parent receiving a cloned-voice message that sounds like a principal; the ethical and practical response is a call-back protocol, not a student-built detector.
  • Idaho National Laboratory and other critical-infrastructure sites treating AI as both an analytic aid and a threat multiplier.
  • Alert fatigue in a small county IT shop with two staff and a noisy commercial detector.

Hands-on activity

Hands-on — Protocol, not an exploit

8 min
  1. Groups of three write a one-page human-in-the-loop protocol for a high school main office: how staff verify urgent requests, who they call, what AI mail filters may do, what they must never do (send a roster, buy gift cards).
  2. Peer-check: does the protocol teach anyone how to attack? If yes, rewrite.
  3. Share one protocol. Teacher kills any sentence that slides into offensive technique.
  4. Collect role analyses.

Discussion questions

  1. Why might a detector that is 99 percent accurate still be dangerous in a school of two thousand accounts?
  2. Should student internships in IT include offensive labs? What is the ethical difference between a college cyber range and this class?
  3. Who owes the parent a call-back protocol: the school, the phone company, or the vendor of the voice model?
  4. Is paying a ransom a technical decision or an ethical and legal one?
  5. How does FERPA change the cost of a school email compromise compared with a spam blog?

Differentiation

Support

  • Provide a protocol template with headings: Verify, Call, Never, AI may, Human must.
  • Allow bullet role analyses.

Challenge

  • Argue whether dual-use foundation models should have use restrictions, and what that would cost legitimate defenders.
  • Design a tabletop (discussion only) of a fictional clinic billing-email compromise; no technical payload details.

Multilingual learners

  • Note that non-native staff and families are often targeted with fluent English or with messages in their language. Discuss without assigning shame.
  • Provide vocabulary cards for phishing, ransomware, and dual use.

IEP / 504

  • Avoid startling voice-clone audio. Describe the risk in text unless a student opts into a short, clearly labeled sample of a public figure, never of a classmate.
  • Written protocols may be dictated.

Assessment

Formative

  • Warm-up message sort and dual-use T-chart.
  • Teacher checklist: zero offensive how-to language in student work.

Summative

  • Role analysis plus office protocol scored on benefits, risks, ethics, and defensive framing.
  • Block extension: 350-word policy for a school board technology committee on AI mail filters and human verification.

Success criteria

  • Names at least one defensive benefit and one dual-use risk.
  • Includes an ethical duty and a human-in-the-loop step.
  • Contains no exploit or lure-crafting instructions.

Responsible use

Defensive framing only. Students do not generate phishing emails, clone voices, scan networks, or test filters. Published awareness examples, already printed, are the only specimens. School accounts are not a lab. Offline paper is sufficient and preferred.

Ethics

Dual use is an ethical structure, not a dare. Benefits of detection are real; so is the duty not to practice harm. Targeting people with less English, less rank, or less time is part of the risk analysis. Showing off an exploit in class would itself be an ethical failure, even if the intent were educational.

Privacy

Attackers want rosters, health information, payroll, and credentials. FERPA and health-privacy laws exist because those records are sensitive. Class will not open real incident tickets, real inboxes, or real student files. Do not paste suspected phishing into a consumer chatbot (that can leak the very data you are trying to protect); follow district reporting channels.

Reflection

  1. What is one thing you will now verify by a second channel before acting on an urgent message?
  2. Where did you feel curious about offensive technique, and how did you redirect that curiosity to duty?
  3. Which role’s ethical rule would you want this school to adopt?

Homework

With a parent, guardian, or trusted adult, agree on a family call-back phrase for urgent money or pickup requests. Write a short reflection on why a voice that sounds right is not proof. Do not test voice-clone apps on anyone’s voice.

Closing

Restate the classroom rule: analysis of benefits, risks, and ethics; no offense. Collect protocols. Ethics and privacy as a subdomain ends here; impact on society begins with testing outputs for bias, accuracy, and harm — a different kind of defense.

Extensions

  • 90-minute block: tabletop discussion of a fictional district compromise and a board policy draft (seminar and writing).
  • Guest from county IT, hospital privacy, Guard cyber education, or INL outreach; recorded backup for rural days.
  • Compare a 2018 phishing-awareness flyer with a 2026 one; what changed after GenAI became commonplace (link to EP.1).
  • Map this lesson to career pathways: networking CTE, public administration, health informatics — ethics first.

Cross-curricular links

Computer science / CTE networking
Defensive roles, acceptable-use, and why a high-school course stops at analysis.
Health science
Ransomware as a patient-safety issue; privacy officers and human shutdown authority.
Civics
Public institutions as targets; election and records systems discussed only at the level of duty, not vulnerability.
Economics
Small IT shops, alert fatigue, and who pays for better defense.

Back to contents

AI Impact · Impact on Society

9-12.AII.IS.1

Three Tests: Bias, Accuracy, Harm

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Evaluate AI-generated output to assess bias, accuracy, and potential harms.

Student-friendly learning targets

  • I can run three separate tests on an AI output: bias, accuracy, and potential harm — and keep the tests from collapsing into one vibe.
  • I can document evidence for each test, including what I still do not know.
  • I can recommend a human action (use, revise, refuse, or escalate) based on the three tests together.

Essential questions

  1. What would have to be true for this output to be biased, inaccurate, or harmful — and how would I know?
  2. Why can a fluent, locally flavored paragraph still fail one of the three tests?
  3. When is the ethical action to refuse an output rather than to edit it?

Objectives

  1. Apply a three-test protocol to at least two teacher-provided AI outputs in different domains (for example, news summary, career advice, health-adjacent general information, or Idaho history).
  2. Distinguish representational bias, statistical bias, and missing-context bias from simple factual error.
  3. Verify or falsify at least two claims with a non-AI source.
  4. Score potential harm by audience and stakes (low inconvenience versus rights, health, reputation, or civic trust).
  5. Write a verdict: use, revise with citation, refuse, or escalate to a human professional.

Key vocabulary

Bias (in output)
A systematic slant in what the model assumes, omits, or emphasizes — for example defaulting to one gender, region, or political frame as normal.
Accuracy
Whether specific claims match checkable evidence from a source that is not the same model.
Hallucination
A fluent claim that is false or unverifiable, including invented citations, dates, or people, presented as if it were known.
Potential harm
Reasonably foreseeable injury if a person acted on the output: medical, legal, financial, reputational, discriminatory, or civic.
Representational harm
Harm from how a group is portrayed or erased, even when no single numeric fact is wrong.
Stakes
What hangs on the decision: a joke caption is low; a scholarship essay, a diagnosis hint, or a news summary used in class is higher.
Refusal
The legitimate academic move of not using an output because it failed a test, rather than polishing it until it sounds fine.

Teacher background

Juniors and seniors have already practiced spotting hallucinations in fluency courses. This lesson is stricter. The standard requires evaluation of output for bias, accuracy, and potential harms as three tests, not as a single dislike. A paragraph can be accurate about Idaho potato acreage and still biased in whose labor it erases. It can be balanced in tone and still invent a statute. It can be true and still be harmful if it offers medical or legal direction a student might follow. Teach a protocol students can reuse in English, government, health, and CTE: (1) who is assumed or omitted, (2) which claims can be checked and against what, (3) who could be hurt if this were trusted. Use printed outputs the teacher generated in advance on a school account, or public examples already in circulation. Do not send student questions about personal health, discipline, or immigration into a live model. Do not use classmates as specimens of bias. Idaho examples help: a summary of a school-board meeting, a wildfire-safety blurb, a Micron-adjacent career paragraph, a history capsule about a treaty or a mining town. Offline fallback is the design, not a backup: dated printouts plus a non-AI reference (textbook page, agency FAQ, newspaper). FERPA: student names do not appear in prompts or in the outputs you file.

Materials

  • Three-test protocol sheet: Bias / Accuracy / Harm, with evidence and unknown boxes.
  • Packet of four printed AI outputs, labeled A–D, dated, with the prompt shown. Domains: local-news summary, career paragraph, general health lifestyle blurb, Idaho history capsule.
  • Non-AI reference set: one agency FAQ, one textbook or encyclopedia page, one Idaho Education News or local paper excerpt, one official statistics table.
  • Verdict stamps: Use / Revise / Refuse / Escalate.
  • Offline fallback: no live generation during class. If a student wants to test a new prompt, they write it for homework on paper and the teacher decides later whether a school-account run is appropriate.

Before class

  • Generate or collect outputs before class. Include at least one fluent falsehood, one representational slant, and one high-stakes overreach (for example, a lifestyle blurb that sounds clinical).
  • Print references. Do not assume students can search on their phones.
  • Remove any accidental PII from prompts (school names of real minors, staff emails).
  • Block plan: after the protocol, a 20-minute seminar on when refusal is required, then a 20-minute evaluation essay using all three tests.

Instructional sequence

Warm-up — One paragraph, three scores

5 min
  1. Project Output A (a glowing, generic career paragraph about working in Boise tech). Students silently score Bias, Accuracy, and Harm as pass / fail / not enough information.
  2. Do not debate yet. Collect the split: people often pass accuracy because it sounds right.
  3. Tell students the standard names three assessments. Fluency is not one of them.
  4. Reveal one planted error in A after scores are in, to unseat over-trust.

Direct instruction — A protocol, not a vibe

10 min
  1. Teach the three tests with definitions and a negative example for each: bias without a false fact; a false fact without obvious bias; a true statement with high harm if followed.
  2. Show how to write evidence: quote the clause, name the missing group or the unchecked claim, name the audience who might act.
  3. Teach verdicts: use (low stakes, checks out), revise (fixable with citation), refuse (do not pass it on), escalate (a professional must own this: nurse, counselor, lawyer, journalist).
  4. Health-adjacent rule: this class escalates; it does not diagnose. Same for legal advice.
  5. FERPA: we evaluate teacher-provided text. We do not paste a classmate’s essay into a model to grade its bias.

Guided practice — Work Output B together

10 min
  1. Read a printed wildfire or air-quality blurb that mixes good public-safety language with an invented evacuation zone or a wrong agency name.
  2. Fill the protocol as a class. Accuracy fails on the invented zone. Bias may appear if only valley cities are mentioned and reservation or rural communities are omitted. Harm is high if someone drove toward a fake zone.
  3. Model checking the non-AI reference (agency FAQ). Date the check.
  4. Choose a verdict. Prefer refuse or revise over use. Require a reason that cites a test, not I wouldn’t trust AI.

Independent practice — Two outputs, two verdicts

12 min
  1. Pairs take Outputs C and D. Complete a full three-test sheet for each and issue a verdict.
  2. At least one claim per output must be checked against the paper reference set. If the reference is silent, they must write unknown — cannot verify here.
  3. A pair may not issue the same verdict for both outputs without a specific argument; the packet is designed to differ.
  4. Circulate to stop collapsed scoring (all three tests marked fail because the student dislikes chatbots).

Real-world examples

  • A chatbot summary of a school-board meeting that invents a vote tally.
  • Career advice that assumes a four-year degree is the only path into Micron-adjacent manufacturing or a clinic.
  • A history capsule that describes a treaty solely from a settler newspaper’s voice.
  • A wellness paragraph that edges into dosage or diagnosis language a student might follow.
  • Image-model captions that misidentify a tribal event as a costume party (link to representational harm).

Hands-on activity

Hands-on — Verdict wall

8 min
  1. Pairs post only their verdict and the one test that drove it.
  2. If two pairs disagree on the same output, they have 90 seconds to cite a line, not a feeling.
  3. Teacher highlights any pair that used unknown honestly.
  4. Collect protocol sheets.

Discussion questions

  1. Can an output fail the harm test even if it passes accuracy? Give a line from today’s packet.
  2. Who is the audience that makes a wildfire error more serious than a sports-recap error?
  3. When should a student escalate instead of revising?
  4. Is representational harm a bias test, a harm test, or both? Why split them on the sheet?
  5. What non-AI source would you trust in this building, and what are its limits?

Differentiation

Support

  • Provide a completed protocol for Output A as a model. Students complete C with sentence frames.
  • Highlight the checkable claims in C and D so verification is findable.

Challenge

  • Write a revised version of a refused output that would pass all three tests, with citations to the paper references.
  • Design a fourth test (for example, provenance) and argue whether the standard already covers it.

Multilingual learners

  • Allow annotation of bias in how the output treats additional-language speakers.
  • Provide the protocol headings with student-built glosses; the evaluation remains in academic English with support.

IEP / 504

  • Offer a larger-print protocol and the option to complete one output in depth.
  • Oral verification with the teacher using the paper reference is acceptable for the accuracy test.

Assessment

Formative

  • Warm-up split scores and guided-practice protocol.
  • Unknown boxes used rather than guessed.

Summative

  • Two completed three-test sheets with verdicts, scored on separation of tests, evidence, and an appropriate escalate/refuse when stakes are high.
  • Block extension: 300–400 word evaluation of one output using all three tests and a named non-AI source.

Success criteria

  • Treats bias, accuracy, and harm as separate judgments with evidence.
  • Checks at least one claim against a non-AI source or marks it unverified.
  • Issues a verdict that matches the stakes, including refuse or escalate when warranted.

Responsible use

Teacher-provided outputs only during the period. No personal medical, legal, or disciplinary questions submitted to a model. No classmate work used as a specimen. Offline print is the lesson. If a district tool is used later, the teacher runs it on a school account.

Ethics

Evaluation is a civic skill: fluent text can still smear a group, invent a fact, or put a person in harm’s way. Refusal is an ethical action, not a lack of tech-savvy. Students should not be rewarded for being merely suspicious of all AI, nor for being merely impressed.

Privacy

Do not put student names, health questions, or discipline stories into prompts. FERPA covers education records; health and counseling topics belong with professionals, not with a chatbot. Filed student evaluations of the packet should not include personal data.

Reflection

  1. Which test was hardest to keep separate from the others?
  2. When did fluency almost talk you out of a fail?
  3. What source in this building will you use the next time a claim looks convenient?

Homework

On paper, apply the three tests to a printed output your teacher sends home (or to a screenshot you already have — do not generate a new one). Check one claim with a library or official site, not with another chatbot. Bring the marked sheet.

Closing

Read one refuse and one escalate verdict aloud. The standard is evaluation, not mood. Next class asks how workers in Idaho already use these tools to solve problems — and how they still apply tests like yours.

Extensions

  • 90-minute block: seminar on refusal, then a formal evaluation essay.
  • Apply the protocol to a student-chosen output from a district-approved tool, with teacher-run generation only.
  • Compare two models on the same prompt (teacher-run, printed) and evaluate whether disagreement is evidence.
  • Bring the protocol into a government or English paper as a methods paragraph.

Cross-curricular links

English Language Arts
Rhetorical analysis of fluent emptiness; citation versus invented sources.
Government / journalism
Meeting summaries, vote tallies, and civic harm when the record is wrong.
Health
Why lifestyle blurbs that sound clinical are escalated, not edited, in class.
History
Whose voice is default in a capsule about treaties, labor, or towns.

Back to contents

AI Impact · Impact on Society

9-12.AII.IS.2

Idaho Work, AI Tools

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Analyze how workers in different careers use AI to solve problems.

Student-friendly learning targets

  • I can analyze how a specific Idaho worker uses AI to solve a defined problem, not merely list apps.
  • I can compare at least two careers on what the human still must judge after the tool runs.
  • I can plan or conduct an ethical interview or profile study that does not collect extra personal data.

Essential questions

  1. What problem is the worker actually trying to solve, and where does the tool sit in that problem?
  2. What does a nurse, a grower, a technician, a journalist or teacher, and a Micron-area manufacturing or software worker still have to know that the model does not?
  3. How should a student talk to a working adult about AI without turning the visit into a product demo?

Objectives

  1. Study five career profiles: clinic/nursing, farm/agronomy, mechanic/technician, journalism or teaching, and software or semiconductor manufacturing (Micron-area).
  2. For each, name a problem, a tool or method, a human judgment that remains, and a risk if the tool is wrong.
  3. Conduct a structured interview or a packet-based profile study using the same questions, not a free-form chat about favorite apps.
  4. Compare two careers on data sensitivity (patient records, yield data, student work, factory telemetry).
  5. Produce a one-page analysis of a single worker’s problem-solving loop: Human aim → data → tool → check → decision.

Key vocabulary

Problem of practice
The concrete job to be done (triage a symptom pattern, time an irrigation set, diagnose a fault code, verify a quote, catch a yield drift), not the name of a software product.
Decision support
A tool that ranks or drafts options while a qualified human remains responsible for the call.
Domain knowledge
The field-specific understanding that lets a worker notice when an output is fluent and wrong.
Telemetry
Instrument data from machines, lines, or fields (vibration, moisture, temperature, throughput) used to detect problems.
Clinical judgment
A licensed professional’s responsibility for patient decisions, which a model cannot hold.
Profile study
A structured analysis of a worker’s process using documents and prepared notes when a live interview is not possible.
Interview protocol
A short list of questions asked the same way to different people so comparisons are fair and privacy is respected.

Teacher background

The standard is about workers solving problems, not about a parade of brand names. Idaho gives you five nearby worlds if you look: a nurse or medical assistant in a St. Luke’s, St. Alphonsus, or rural clinic; an agronomist or grower on potatoes, sugar beets, dairy, or cattle; a diesel or industrial technician in the Treasure Valley; a reporter or a classroom teacher; and a process, yield, or software role tied to Micron and its suppliers. Students should leave able to narrate a loop: the human has a problem, some data exists, a tool proposes a pattern or a draft, a qualified person checks, a decision is made. If the check disappears, the analysis has failed. Live interviews are gold when a guest can come, or when a student already works with a family adult who consents. Many rural and small-town classes will need printed profiles and a recorded backup; that is a profile study, not a lesser task, if the questions are the same. Do not let the hour become a list of apps. Do not ask guests for patient names, student names, unpublished yield numbers, or factory secrets. FERPA and health-privacy rules travel with the clinic and the school profiles. Offline fallback: five one-page profiles written by the teacher from public career materials, plus an interview protocol students can run later with consent.

Materials

  • Five printed profiles (nurse/clinic, farmer/agronomist, mechanic/technician, journalist or teacher, Micron-area software or manufacturing). Each names a problem, a tool type, a human check, and a risk.
  • Interview protocol (same eight questions for every career). Consent line at the top.
  • Problem-solving loop poster: Aim → Data → Tool → Check → Decision.
  • Comparison grid for two careers: data sensitivity, cost of error, who is licensed to decide.
  • Offline fallback: recorded two-minute clips if a guest exists; otherwise packets only. No student is required to have a parent in a listed industry.

Before class

  • Invite a guest if possible and record a backup for activity buses and bandwidth failures.
  • Rewrite profiles so they are realistic but not identifiable as a particular neighbor.
  • Send the protocol home for optional adult interviews with a consent note: no patient, student, or proprietary data.
  • Block plan: two interviews or two deep profile studies, then a comparison essay.

Instructional sequence

Warm-up — Name the problem, not the app

5 min
  1. Students list any AI they have heard a worker use. Cross out product names. Circle the problem underneath (catch a bad part, draft a parent email, time a pump).
  2. If a student cannot name a problem, that is data: they have seen marketing, not work.
  3. Show the five Idaho worlds on the board. Tell them every student will leave with one full loop, not five logos.
  4. Read the standard. Underline workers and solve problems.

Direct instruction — Five worlds, one loop

10 min
  1. Walk one clinic example: a triage note drafted from structured fields, checked by a nurse, never a diagnosis from a public chatbot, patient identifiers stripped.
  2. Walk one agronomy example: satellite or soil telemetry suggesting a variable-rate pass; the grower still knows the field’s low spot that the model treats as noise.
  3. Walk one technician example: a fault-code suggestion list; the mechanic still tests the cheap failure first and does not replace a part because a screen said so.
  4. Walk one journalist/teacher example: transcription and a first-pass summary; quotes still get verified; student essays still get a human reader for thinking, not just grammar.
  5. Walk one Micron-area example: yield or defect pattern detection on a line; a process engineer still owns whether to stop the tool. No proprietary numbers in class.

Guided practice — Profile the nurse together

10 min
  1. Read the clinic profile aloud. Fill Aim → Data → Tool → Check → Decision on the board.
  2. Ask what data must never enter a consumer model (names, dates of birth, conditions). Connect to FERPA-like duties and health privacy.
  3. Ask what happens if the check is skipped on a night shift. That sentence is the analysis.
  4. Model citing the profile as a source, not I think nurses use ChatGPT.

Independent practice — Study one profile; compare with a neighbor

12 min
  1. Each student takes one remaining profile and writes a one-page loop analysis.
  2. Pair with someone who had a different career. Complete the comparison grid on data sensitivity and cost of error.
  3. If a consented guest is present, two students ask protocol questions only; others take notes as a profile study.
  4. Ban app lists. If a sentence names a brand without a problem, rewrite it.

Real-world examples

  • A rural clinic using speech-to-text for notes, with a nurse correcting terms the model misses, never pasting a chart into a public chatbot.
  • A Magic Valley dairy or potato operation using imagery and soil data to decide a pass, with an agronomist walking the field before spending money.
  • A Nampa or Idaho Falls technician using a diagnostic suggestion list, then confirming with a test, not a guess.
  • A reporter at a statehouse or school-board meeting using a transcript, then calling to confirm a quote.
  • A process engineer in the Boise-Meridian semiconductor corridor watching defect clusters, with a human stop-the-line authority.

Hands-on activity

Hands-on — Interview dry run

8 min
  1. Pairs practice the protocol in role-play: one is the worker from their profile, one is the student. Three minutes each.
  2. Listeners mark when a question asked for PII or a trade secret and rewrite it.
  3. Class collects three excellent questions on the board (problem, check, failure case).
  4. Assign the optional homework interview only with written adult consent.

Discussion questions

  1. What did every career still need a human to do after the tool ran?
  2. Which job’s error costs a life, a crop year, a crashed engine, a false headline, or a scrapped wafer — and how does that change the check?
  3. Why is listing apps a weaker analysis than describing a problem of practice?
  4. How should a student intern refuse a request to paste customer or patient data into a public model?
  5. What Idaho career not on the five-card set would you add, and what problem would you study?

Differentiation

Support

  • Provide a one-page loop template with sentence starters.
  • Allow a student to stay with the clinic profile after guided practice instead of switching.

Challenge

  • Add a sixth Idaho world (INL, tribal enterprise, logistics, energy) with sources cited.
  • Write the comparison as a memo to a counselor explaining which pathway still requires deep domain knowledge.

Multilingual learners

  • Profiles should include at least one worker who uses Spanish or another language on the job; analyze how translation tools help and fail (link EP.2).
  • Interview protocol available with simplified English; students may ask questions in the adult’s preferred language if both consent.

IEP / 504

  • Oral loop analysis is acceptable. Role-play may be written instead of spoken if needed.
  • Do not require a home interview; the packet study meets the standard.

Assessment

Formative

  • Warm-up problem-not-app rewrite.
  • Comparison grid completeness.

Summative

  • One-page loop analysis of a single career, scored on problem, tool role, human check, and risk.
  • Block extension: two careers compared in a 400-word seminar paper, plus notes from a live or recorded interview.

Success criteria

  • Names a problem of practice, not only a product.
  • Includes a human check and a failure cost.
  • Uses Idaho-relevant work (clinic, field, shop, classroom or newsroom, semiconductor/software) with respectful privacy limits.

Responsible use

No patient, student, or proprietary factory data in notes or tools. Guests may refuse any question. Students do not install workplace software on personal phones for this assignment. Offline profiles fulfill the standard. Recorded backups beat failed video links.

Ethics

Workers are experts in their problems. Students analyze how tools sit inside that expertise; they do not instruct a nurse or a grower. Job displacement may come up; treat it as an evidence question (what task, what check, what hiring pattern), not as destiny or as a pep talk.

Privacy

Clinic stories follow health-privacy rules. School stories follow FERPA. Factory and farm numbers may be confidential. Interview notes store no extra identifiers (children’s names, addresses, account logins). Optional interviews need documented consent and may be declined without grade penalty; the packet study remains available.

Reflection

  1. Which human check would you want if you were the patient, the grower, or the reader?
  2. What question in the protocol produced the most useful answer in role-play?
  3. Where were you tempted to list an app instead of a problem?

Homework

Optional: run the protocol with a consented adult (fifteen minutes, no sensitive data). Required if no interview: annotate a second printed profile with the loop and one question you would still ask. Do not look up employees on social media to complete this.

Closing

Read one Aim → Decision loop aloud. Collect analyses. Tomorrow traces how bias enters long before a worker sees an output — at every stage of working with data.

Extensions

  • 90-minute block: guest or recording plus a comparison essay (seminar and writing).
  • Coordinate with CTE, FFA, HOSA, or a counseling career unit so the profile is not an island.
  • Students who complete a consented interview attach notes and a thank-you; no recording without extra consent.
  • Map tools to the three tests from IS.1: how would this worker check bias, accuracy, and harm?

Cross-curricular links

Health science / HOSA
Clinical judgment, documentation, and why public chatbots are the wrong place for chart fragments.
Agriculture / FFA
Agronomic decision support, field-truthing, and data that is a business secret.
Automotive / industrial CTE
Fault codes as suggestions, tests as evidence.
English / journalism
Verification of quotes and the difference between a transcript and a story.
Engineering / manufacturing
Yield, defects, and stop-the-line authority in semiconductor work.

Back to contents

AI Impact · Impact on Society

9-12.AII.IS.3

Bias Enters at Every Stage

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Analyze how decisions made at different stages of working with data can lead to biased data, misleading conclusions, and compromised AI models.

Example from the standards. In a statistics or math course, students can take a collection of data and submit into an AI system then compare the differences.

Student-friendly learning targets

  • I can name specific decisions at collection, cleaning, labeling, splitting, modeling, and deployment that can bias data or conclusions.
  • I can show how two different decisions on the same table produce two different stories.
  • I can compare a human analysis of a small dataset with an AI summary of the same table and explain the difference.

Essential questions

  1. At which stage did the slant get in — and how would a later user even see it?
  2. If two groups clean the same Idaho table differently, why might both outputs look precise?
  3. What does it mean for a model to be compromised when the math still runs?

Objectives

  1. Map at least six stages of working with data and attach a bias risk to each.
  2. Make two deliberate cleaning or inclusion decisions on a public Idaho-relevant table and document how conclusions move.
  3. Compare a student-made summary of the table with a teacher-run AI summary of the same table (printed), as the standards example suggests.
  4. Explain misleading conclusions versus compromised models: a wrong story now, and a system that will keep telling it.
  5. Recommend a documentation practice (who is missing, what was dropped, what the split was) that a later user would need.

Key vocabulary

Collection bias
Whose data never entered the table: people offline, counties not surveyed, night-shift rows, languages not offered.
Cleaning
Decisions to drop, fix, or impute values. Dropping “messy” rows can drop a population.
Labeling
Human or automated assignment of categories; a disputed category becomes a fake certainty downstream.
Train/dev/test split
How examples are divided for fitting, tuning, and checking; a leak or an unrepresentative split makes metrics look better than the world.
Feature choice
Which columns are treated as meaningful. Proxy variables (ZIP code for income, for example) can smuggle bias.
Threshold
The cutoff that turns a score into a yes. Moving it changes who is flagged, hired, or denied.
Compromised model
A system whose outputs are systematically untrustworthy because of data or design decisions, even if it produces numbers on demand.
Data leakage
Information from the test world sneaking into training, so the model appears accurate until it meets a true new case.

Teacher background

Fluency lessons introduced the idea that data choice can bias output. This standard asks for stages. Bias is not a goblin that inhabits a finished model; it is a series of human decisions: who is counted, what is repaired, how rows are labeled, how the split is cut, which features are blessed, where the threshold sits, and what happens when the system is deployed back into the world that produced the table. The state’s example is practical: in a statistics or math course, students take a collection of data, submit it to an AI system, and compare the differences. Do that with a tiny public table — county indicators, sports statistics, weather, FFA contest scores with names removed — never with a class roster or health file. Run the AI pass yourself on a school account before class and print the summary; live submission is optional and often blocked. Students should first do a human summary so the comparison is real. Teach misleading conclusions (a chart that is true of the cleaned table and false of Idaho) as distinct from a compromised model (a tool that will keep amplifying the same omission). Civic tone: no villain data-scientist stereotype, and no claim that more data automatically heals a bad stage. FERPA: no student PII in the table. Offline fallback: the printed table, two cleaning scripts described in English, and a printed AI summary.

Materials

  • One-page public table (10–20 rows) with a documented source and date. Names of people removed. Idaho-relevant if possible (counties, crops, enrollment aggregates, weather).
  • Stage map: Collect, Clean, Label, Split, Choose features, Set threshold, Deploy, Feedback.
  • Two cleaning instruction cards that disagree (for example: drop missing rows versus keep them as unknown; include small counties versus drop n < 10).
  • Printed teacher-run AI summary of the raw table and, if space, of one cleaned version.
  • Offline fallback: no student uploads. If the district forbids even teacher-run tools, a second human summary written by a colleague can stand in for the AI pass; label that substitution honestly.

Before class

  • Build or copy a tiny public table. Write the source on the page.
  • Run the AI summary yourself; print hallucinations if they happen — they are useful.
  • Decide which two cleaning decisions will move a conclusion students can see in twelve minutes.
  • Block plan: full lab write-up comparing human, AI, and two cleaning paths, plus a seminar on documentation.

Instructional sequence

Warm-up — Who is not in this table?

5 min
  1. Hand out the table face down. On the back, students guess what an Idaho education or ag table usually misses (home school, tribal schools, small counties, migrant seasons, cash wages).
  2. Turn it over. Circle missingness: blank cells, tiny n, categories that were never offered.
  3. Tell them every blank is a decision waiting to happen.
  4. Read the standard, including the statistics-course example.

Direct instruction — Stages, not a single original sin

10 min
  1. Walk the stage map with one running example: predicting chronic absenteeism from an aggregate table. Collection misses some programs. Cleaning drops small rural rows. Labeling treats any absence alike. Split puts two large districts in train and a reservation school in test, or the reverse. Features use ZIP. Threshold flags a school. Deployment sends extra enforcement, which changes the next year’s data.
  2. Define misleading conclusion versus compromised model.
  3. Show the printed AI summary. Ask what stage the model cannot see (the dropped rural rows) and how it still sounds sure.
  4. FERPA line: we use public aggregates. We do not build a table of this class.

Guided practice — Two cleanings, two stories

10 min
  1. As a class, apply Cleaning Card A (drop missing / drop small n). Compute one simple statistic by hand (mean, median, or a count).
  2. Apply Card B (keep missing as a category). Recompute.
  3. Write two headlines. Both will look precise. Circle the stage that caused the fork.
  4. Read the AI summary’s headline. Does it match A, B, or a third invention?

Independent practice — Human summary versus AI summary

12 min
  1. Individually, write an eight-line human summary of the table, naming at least one limitation.
  2. Compare to the printed AI summary using a three-column chart: Human said / AI said / Table actually shows.
  3. Mark any AI claim that is not in the table (hallucination) and any omission of small groups (bias at collection or cleaning).
  4. Finish with one sentence: the conclusion is misleading because… or the model would be compromised if we trained on…

Real-world examples

  • A hiring screen trained on past employees of a plant that historically hired from one town.
  • An absenteeism model that drops small rural and alternative programs as noise.
  • An agricultural yield model that never saw a smoke-heavy fire year as its own regime.
  • A sentiment tool labeled by workers who treated dialect as error.
  • A split that leaks the target (including the outcome column in features) so accuracy looks perfect until deployment.

Hands-on activity

Hands-on — Stage stickers

8 min
  1. Groups get a failure story and must place it on the stage map with a sticky note.
  2. Two groups may argue: is this cleaning or labeling? The argument is the point if it stays specific.
  3. Add a documentation line each group wishes the original team had written.
  4. Collect human/AI comparison charts.

Discussion questions

  1. Why does dropping messy rows feel responsible and still produce bias?
  2. If the AI summary is smoother than yours, should you trust it more? What does smoothness hide?
  3. How can a model be compromised if the loss function improved?
  4. Which stage is easiest for a later user to audit, and which is almost invisible?
  5. What would you refuse to submit to an AI system even in a math class, and why?

Differentiation

Support

  • Pre-compute the two statistics; students interpret rather than calculate if needed.
  • Provide a fill-in comparison chart.

Challenge

  • Design a split that would leak, then a split that would not, on a 16-row toy set.
  • Write a model card section: known missing groups, cleaning rules, threshold.

Multilingual learners

  • Discuss labeling of language variety as error. Invite examples without requiring students to perform dialect.
  • Allow the human summary draft in the student’s strongest language, with key claims also in English.

IEP / 504

  • Large-print table. Partner for arithmetic. Oral comparison chart acceptable.
  • Reduce to four stages if working memory is the barrier; keep collect, clean, deploy, feedback.

Assessment

Formative

  • Headline pair from two cleanings.
  • Who is not in this table warmup notes.

Summative

  • Human versus AI comparison chart plus a stage-specific explanation of a misleading conclusion or compromised model.
  • Block extension: lab write-up with methods, two cleaning paths, and a documentation appendix.

Success criteria

  • Identifies more than one stage, not only biased data as a slogan.
  • Shows that a decision changed a conclusion, with a number or a count from the table.
  • Compares human and AI treatments of the same collection, or honestly labels a substitution.

Responsible use

Public, tiny, de-identified tables only. Students do not upload class surveys with names. Teacher runs any AI pass. If tools are blocked, a second human summary is an honest substitute and should be labeled. No scraping of student information systems.

Ethics

Every stage is a human choice with a distributional effect. Precision can launder those choices. The ethical habit is documentation: who is missing, what was dropped, what the threshold does to people. Students should not treat data workers as villains or as powerless.

Privacy

Do not use this class as a data source. FERPA forbids casual reuse of education records for a model experiment. Aggregate public data is enough. If students later collect a survey, they need a purpose, a consent line, and a plan to destroy identifiers — not an AI bucket.

Reflection

  1. At which stage would you have made the same decision as Card A, and what group would that have cost?
  2. What did the AI summary sound like it knew that the table did not show?
  3. What one line of documentation would you require before trusting a school dashboard?

Homework

On paper, pick a dashboard or infographic you see this week (school, news, sports). Name two stages you cannot see from the graphic and one question you would ask the person who cleaned the table. Do not upload the graphic to a model.

Closing

Hold up the two headlines. Same Idaho table, different human decisions, smoother AI prose on top. Collect charts. Next class returns to a debate you may have met in 9–10, now with evidence instead of vibes: consciousness, creativity, ethics, and human responsibility.

Extensions

  • 90-minute block: fuller statistics lab and a seminar on documentation standards.
  • Partner with a math teacher to use a course dataset that is already public and de-identified.
  • Rebuild the table including the dropped counties and see whether the AI summary (teacher-run later) moves.
  • Connect to AITA.DA standards if CS students are in the room: train/dev/test as a formal lab.

Cross-curricular links

Statistics / algebra
Means versus medians, missingness, and why a model summary is not a substitute for looking at the table.
Government
Indicators used in policy (absenteeism, crime, unemployment) and who is left out of administrative data.
Agriculture science
Weather regimes, irrigation districts, and models that never saw a smoke year.
Computer science
Splits, leakage, and model cards.

Back to contents

AI Impact · Impact on Society

9-12.AII.IS.4

The Hard Debate, Senior Year

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Debate perspectives on differences between human and artificial intelligence and their implications for consciousness, creativity, ethics, and human responsibility.

Student-friendly learning targets

  • I can debate differences between human and artificial intelligence using evidence from prior units, not slogans.
  • I can address all four implications named in the standard: consciousness, creativity, ethics, and human responsibility.
  • I can steelman a view I do not hold and still keep humans accountable for design, use, and harm.

Essential questions

  1. What is actually different between human minds and current AI systems, and which differences matter for policy?
  2. If a system can produce a poem, a plan, or a kind sentence, what follows for consciousness, creativity, ethics, and responsibility — and what does not follow?
  3. Who remains responsible when a fluent system is in the loop?

Objectives

  1. Revisit 9-12.AIF.ECT.1 at greater depth: same prompt, higher evidence bar, senior-year sources.
  2. Present an evidence-backed claim on each of the four implications: consciousness, creativity, ethics, and human responsibility.
  3. Use at least one technical limit (pattern completion, lack of bodily sensing, hallucination, no account-holding) and one civic consequence.
  4. Steelmans the opposing view for two minutes before rebuttal.
  5. Refuse vibes: every major claim carries a dated source, a prior-lesson artifact, or a clearly labeled philosophical axiom.

Key vocabulary

Consciousness
There being something it is like to be a subject — experience, not only intelligent-looking behavior. Whether any current system has it is disputed; pretending the dispute is over is not evidence.
Anthropomorphism
Attributing human feelings, intentions, or inner life to a system because it talks like a person.
Creativity
The making of something new that is also meaningful in a human practice (art, science, craft). Novelty of output is not automatically creativity of a subject.
Moral patient / moral agent
A moral patient can be wronged; a moral agent can be held responsible. Debate which, if either, applies to AI, and why humans remain agents either way.
Human responsibility
The duty of people and institutions to set aims, check outputs, take blame, and repair harm. It does not migrate to a model because the model is fluent.
Steelman
The strongest fair version of an opposing view, stated so that a serious person who holds it would recognize it.
Technical limit
A documented constraint of current systems (no body, no persistent account-holding, training on human traces, hallucination) used as evidence rather than as insult.

Teacher background

Standard 9-12.AIF.ECT.1 asked ninth and tenth graders to debate human versus artificial intelligence and the implications for consciousness, creativity, ethics, and human responsibility. This is the same sentence at senior depth. The bar is evidence, not vibes. Students should walk in with artifacts from earlier AII lessons: accessibility failures, energy and water costs, unauthorized training, dual-use cybersecurity, three-test evaluations, career loops, and stage-by-stage bias. Those artifacts are exhibits. Consciousness: distinguish inner experience from skilled imitation of talk about experience; name the dispute; do not grade students for being dualists or functionalists, grade them for not smuggling a conclusion. Creativity: a model can produce a new combination; a human practice still decides whether it is a work, a tool output, or a derivative injury to a living artist (EP.4). Ethics: duties attach to agents who can answer. Human responsibility: even if someone argues a future system might be a moral patient, today’s deployments are designed, bought, and excused by people — school boards, vendors, nurses, engineers, students. Require a steelman. Ban diagnosis of classmates’ spirituality. Civic tone: this is a seminar, not a TED talk and not a panic session. Offline fallback: printed exhibit cards from prior units and timed debate blocks that need no network. FERPA: personal journals stay personal; cite class artifacts without naming a peer’s private beliefs.

Materials

  • Four exhibit folders, one per implication, stocked with dated cards from prior lessons (EP.2 door, EP.3 warehouse, EP.4 scrape, EP.5 dual use, IS.1 protocol, IS.2 loop, IS.3 stages).
  • Debate roles: opening, steelman, rebuttal, civic implication, timekeeper.
  • Evidence rule card: source, date, or labeled axiom. Vibes will be stopped.
  • Timer and speaking-order poster.
  • Offline fallback: paper exhibits only. No live chatbot asked Are you conscious? as a stunt.

Before class

  • Tell students two days ahead to bring one prior-unit artifact. Have extras.
  • Assign mixed groups so the four implications are all staffed.
  • If 9–10 debate notes exist, return them so growth is visible.
  • Block plan: full structured debate with judge sheets, then a 25-minute argumentative essay covering all four implications.

Instructional sequence

Warm-up — Vibes are not exhibits

5 min
  1. Students write one sentence they have heard: AI is just a tool, AI is already alive, AI will take everything, only humans create. They mark it vibe or exhibit. If they cannot name a source, it is a vibe.
  2. Collect two vibes and two exhibits on the board. Leave the vibes up as caution tape.
  3. Read the standard. Point to the four nouns. All four will be hit or the debate is incomplete.
  4. Remind them this revisits AIF.ECT.1 on purpose.

Direct instruction — Four implications, one evidence bar

10 min
  1. Consciousness: define the dispute. Behavior can fool. Inner life is not proven by a first-person sentence a model emits. Students may argue either way if they carry a philosopher, a scientist, or a clearly labeled axiom — not a movie.
  2. Creativity: return to EP.4. Output can be novel; credit, intention, and practice still sit with humans unless someone argues a careful alternative and takes questions.
  3. Ethics: who can be wronged, who can owe a duty. A crashed model is not punished; a vendor, a board, or a user can be.
  4. Human responsibility: the through-line of the year. Designers, deployers, and users choose. The algorithm is not a legal person in this classroom’s working assumption unless a student argues otherwise with sources.
  5. Teach steelman with a 30-second model. Teach the technical-limit requirement.

Guided practice — Steelmans on consciousness

10 min
  1. In pairs, Student A states a consciousness claim in one sentence with a source or axiom tag.
  2. Student B steelmans it until A nods. Then B offers one technical limit (for example, no interoception, no persistent body, training on human text).
  3. Swap. Teacher listens for mockery and stops it.
  4. Harvest one civic consequence: if we wrongly treat a system as a person, what duty to humans might we dodge? If we wrongly treat people like systems, what duty might we dodge?

Independent practice — Four-box brief before speaking

12 min
  1. Each student completes a four-box brief: Consciousness / Creativity / Ethics / Responsibility, each with a claim, an exhibit, and a steelman seed.
  2. Missing a box means they are not ready to speak on the full standard.
  3. They star the one box they will open with in the hands-on debate.
  4. Teacher stamps briefs that cite prior units.

Real-world examples

  • A student who treats a companion chatbot as a friend (AIF companion risk) versus a student who treats it as a drafting tool — implications for consciousness talk and for responsibility.
  • An Idaho artist’s unpaid style in a generator: creativity as practice and market, not as a vibe about the muse.
  • A hospital dual-use failure (EP.5) where blaming the model would dodge a human protocol.
  • A school board asked whether a detector is fair (IS.3 stages) — ethics without metaphysics.
  • Senior capstone work: who is the author of record if a model drafted a paragraph the student then rebuilt.

Hands-on activity

Hands-on — Four corners, timed

8 min
  1. Room corners: Consciousness, Creativity, Ethics, Responsibility. Groups of four rotate or send a runner so each corner hears a 60-second evidence claim and a 30-second steelman.
  2. A scribe at each corner notes one technical limit and one civic consequence.
  3. If time is short, stay in home groups of four with one student owning each implication.
  4. Collect four-box briefs. Oral performance is formative; the brief is the gradeable artifact in a 50-minute period.

Discussion questions

  1. If a system says I feel afraid, what kind of evidence would you still need before talking about consciousness?
  2. Is a new image that no human composed pixel by pixel a creative work, a tool output, or something the law has not settled (link EP.4)?
  3. Can a model be a moral patient without being a moral agent? What would that change in a school policy?
  4. When people say the algorithm decided, which human choices are being hidden?
  5. What did you believe in the 9–10 version of this debate that you can no longer hold after EP and IS evidence?

Differentiation

Support

  • Provide a four-box template with sentence frames and a list of allowed exhibits from prior units.
  • Allow a written steelman instead of public speaking, still timed.

Challenge

  • Require engagement with a named philosopher or scientist (dated, excerpted by the teacher) in the consciousness or ethics box.
  • Write a dissent that still hits all four implications.

Multilingual learners

  • Permit the steelman in the student’s strongest language with an English claim sentence, or vice versa.
  • Pre-teach consciousness, agent, patient, and responsibility with non-idiomatic definitions.

IEP / 504

  • Do not force unprepared public debate. The four-box brief meets the standard; speaking is an extension.
  • Extra processing time on the steelman. Quiet copies of exhibit cards.

Assessment

Formative

  • Vibe versus exhibit warmup.
  • Paired steelman on consciousness.

Summative

  • Four-box brief scored on all four implications, evidence bar, steelman seed, and a technical limit plus civic consequence.
  • Block extension: judged debate plus a 500-word essay that a 9–10 student could not have written without the year’s exhibits.

Success criteria

  • All four implications appear with a claim.
  • At least one technical limit and one civic consequence are explicit.
  • Steelmans rather than caricatures; no vibe-only boxes.

Responsible use

Do not ask a live model whether it is conscious as a classroom stunt; that confuses the evidence bar. Do not pressure students to disclose religious views of the soul. Paper exhibits from prior lessons are enough. Offline is the default.

Ethics

The ethical implication is not only how we treat machines. It is how talk about machines becomes a way to dodge duties to workers, students, patients, and creators. Students may disagree about inner life. They may not disagree that today’s harm and credit still land on people unless they argue otherwise with care.

Privacy

Beliefs about the soul, mental health, and companion-app use can be sensitive. Students cite public class artifacts, not a neighbor’s journal. FERPA still covers recorded student work if you keep debate video; store it under district rules. No uploading of student briefs to a scoring bot.

Reflection

  1. Which implication was hardest to keep from collapsing into a movie plot?
  2. What exhibit from this year changed a 9–10 opinion?
  3. Where did you catch yourself anthropomorphizing, and what did you do next?

Homework

Revise the four-box brief. Add one quotation from a prior lesson packet (with lesson code) to the weakest box. Do not ask a chatbot to steelman for you; that would skip the thinking the standard names.

Closing

Read the four nouns again. Collect briefs. The last lesson in this subdomain asks the civic sequel: who decides how these systems are used, designed, deployed, and regulated — and who pays.

Extensions

  • 90-minute block: full debate with judge sheets and a sustained essay (seminar and writing).
  • Invite a philosophy or CS faculty guest from a nearby college; recorded backup.
  • Return 9–10 debate notes and write a metacognitive postscript: what evidence changed.
  • Publish (with student consent, no names required) a class list of remaining disagreements — intellectual honesty as a product.

Cross-curricular links

Philosophy / English seminar
Personhood, authorship, and the difference between a claim and an axiom.
Psychology
Anthropomorphism, theory of mind, and why fluent talk triggers social brainware.
Civics
Responsibility in institutions when software is in the loop.
Arts
Creativity as a practice with audiences, not only as surprise in a file.

Back to contents

AI Impact · Impact on Society

9-12.AII.IS.5

Who Decides, Who Pays

11–12 · 50 minutes · 90 minutes (extend seminar and writing)

Standard quoted exactly

Evaluate how human choices in using, designing, deploying, and regulating AI technologies have risks, benefits, and long-term impacts.

Student-friendly learning targets

  • I can evaluate human choices at four stages — using, designing, deploying, and regulating — with risks, benefits, and long-term impacts for each.
  • I can show that a school-board acceptable-use policy, this Idaho standards document, and unsettled state or federal bills are all human choices, not the will of an algorithm.
  • I can name who benefits and who pays when a district, a company, or a legislature chooses.

Essential questions

  1. If humans choose at every stage, why do people still say the algorithm decided?
  2. Who has standing to use, design, deploy, or regulate AI in an Idaho school, and who pays when the choice fails?
  3. What long-term impact should a board or a legislature be judged on, beyond this year’s convenience?

Objectives

  1. Evaluate one concrete choice in each of the four verbs: using, designing, deploying, regulating.
  2. Annotate a school-board acceptable-use policy (or a sample AUP if the local one is thin) for AI-relevant human decisions.
  3. Place this Idaho 9–12 AI standards document as a state-level human choice that still leaves curriculum to LEAs.
  4. Describe federal and state legislative uncertainty without inventing a bill as passed.
  5. Write a recommendation that names a decision-maker, a payer, a risk, a benefit, and a long-term impact.

Key vocabulary

Use
A person’s or a classroom’s choice to apply a tool to a task, including the choice not to.
Design
Choices about architecture, data, defaults, and whose error is tolerated before a product ships.
Deployment
Putting a system into a real setting (a clinic, a factory, a student information system) with a budget, a vendor, and a staff who must live with it.
Regulation
Rules with public authority: statute, administrative rule, court holding, or a board policy that binds a school.
Acceptable-use policy (AUP)
A local board-adopted rule for how school technology may be used; in Idaho, local boards hold substantial control.
LEA
Local education agency: a district or charter responsible for curriculum and policy under state standards.
Long-term impact
Effects that outlast a contract cycle: habits of thinking, labor markets, water and power, civic trust, student records that persist.
Accountability
A named human or institution that can be questioned, voted out, sued, or required to repair harm.

Teacher background

The standard is a map of human verbs: using, designing, deploying, regulating. Each verb has risks, benefits, and long-term impacts. Students should leave unable to hide behind the algorithm. An Idaho student who pastes a prompt is using. An engineer who sets a default to train on public posts is designing. A superintendent who buys a detector is deploying. A board that writes an acceptable-use policy, a state that publishes these AI content standards, and a legislature that cannot agree on a statute are regulating — or failing to. Local control matters here. Idaho LEAs choose curriculum even when the Department publishes standards; this document is not a required product. Federal bills on AI have been proposed, altered, and stalled; students should say uncertainty when the law is uncertain. Money is part of evaluation: who pays for licenses, for grid upgrades, for labeling labor, for a false accusation from a detector, for a data-center incentive. Use a real AUP if the district has one; otherwise a clearly labeled sample. Print excerpts of this standards document (the Role of Standards page is perfect). Do not lobby for a party. Civic tone: power is specific. Offline fallback: paper AUP, paper standards excerpts, a fictional but realistic board agenda item. FERPA belongs in the AUP conversation because student records are often what vendors want to process.

Materials

  • Four-verb evaluation grid: Use / Design / Deploy / Regulate, with Risk, Benefit, Long-term impact, Who decides, Who pays.
  • Excerpts: local or sample AUP; Idaho AI standards Role of Standards and one AII standard; a dated news brief on a state or federal AI bill that has not settled.
  • Fictional board agenda item: purchase of an AI writing detector, or a data-sharing addendum with a vendor.
  • Accountability cards: student, teacher, principal, superintendent, school board, vendor, legislature, Congress, governor, county commission.
  • Offline fallback: all documents printed. No live tracking of bills required during the period.

Before class

  • Request the current AUP and approved-tools list from administration. Redact nothing that is already public; do not add student names.
  • Print Role of Standards (standards do not dictate how to teach; LEAs decide resources).
  • If a live board meeting is upcoming, assign optional observation; never require political attendance.
  • Block plan: mock board hearing (seminar) and a written recommendation with costs (writing).

Instructional sequence

Warm-up — The algorithm did it

5 min
  1. Students rewrite three dodges: The detector flagged him. The model trained on her art. The filter blocked the site. Each rewrite must name a human verb and a role.
  2. Share one strong rewrite.
  3. Write the four verbs on the board. Tell students the standard requires evaluating all four, with risks, benefits, and long-term impacts.
  4. Promise that uncertainty about bills is an acceptable academic answer if dated.

Direct instruction — Four verbs, local to federal

10 min
  1. Using: a teacher allows a district chatbot for outlines; a student uses a consumer app on a phone. Different choosers, different FERPA exposure.
  2. Designing: default logging, training-data choices (EP.3–4), whose accent the recognizer hears (EP.2).
  3. Deploying: a district contract, a clinic note system, a factory defect model (IS.2). Budget, training for staff, and who is on call when it fails.
  4. Regulating: board AUP; this standards document; Idaho statute if any; federal uncertainty. Local control means a board cannot blame Boise for an AUP it did not write, and a teacher cannot blame the algorithm for a syllabus they assigned.
  5. Who pays: licenses, teacher time, false-positive hours, ratepayers, unpaid creators, students whose thinking atrophies.

Guided practice — Mark up the AUP

10 min
  1. Read the AUP excerpt together. Highlight sentences that are human choices about AI or that are silent where a choice is needed.
  2. Place each highlight on the four-verb grid. Silence is a choice to defer.
  3. Read two sentences from Role of Standards. Ask: who decided that this course exists, and who still decides the materials?
  4. Model a who pays line for a detector purchase: vendor revenue, student time on appeals, teacher hours, reputation of a falsely flagged senior.

Independent practice — Evaluate a deployment

12 min
  1. Students take the fictional (or real, if public) board agenda item and complete the four-verb grid.
  2. They must fill regulating with both the AUP and this standards document, plus one sentence on legislative uncertainty.
  3. They write a ten-line recommendation: decide, delay, or deny; name the payer; name a long-term impact (habits, records, trust, labor).
  4. No party slogans. If a student writes politicians should just… they must name a body and a mechanism.

Real-world examples

  • A board updating an AUP after GenAI became commonplace (link EP.1) — a local regulatory act.
  • A district deploying a detector without an appeals process — a deployment choice with student-cost impacts.
  • Idaho’s 9–12 AI standards as a state document that defines expectations but not a mandated curriculum package.
  • County siting and tax choices for data centers (EP.3) as regulation adjacent to AI, with ratepayers and irrigators among those who pay.
  • Unsettled federal and state AI bills: students cite last dated action and say not enacted if that is true.

Hands-on activity

Hands-on — Accountability map

8 min
  1. Groups lay accountability cards on the agenda item. They may stack cards (board plus vendor plus principal).
  2. Remove one card and ask who now pays. If the answer is no one, the map has failed.
  3. Report one long-term impact that would not show up in this year’s test scores.
  4. Collect grids and recommendations.

Discussion questions

  1. Where in this building is a human currently hiding behind the algorithm?
  2. Should student use, teacher design of assignments, district deployment, and board regulation be aligned, and who calls a conflict?
  3. If the legislature does nothing, is that a regulatory choice?
  4. Who should pay when a detector is wrong: the vendor, the board, or the student who lost time?
  5. What long-term impact are we accepting if we train seniors to treat fluent output as decided?

Differentiation

Support

  • Provide a completed Use row as a model; students complete Deploy and Regulate.
  • Sentence frames: The decision-maker is… The payer is… A long-term impact is…

Challenge

  • Draft a one-page AUP amendment a board could actually consider, with a fiscal note.
  • Compare this standards document to another state’s AI guidance, dated, without ranking as better — just different human choices.

Multilingual learners

  • Note language-access implications of AUP and of parent notices about tools (EP.2).
  • Allow the recommendation’s first draft in the student’s strongest language with the five required names in English (decider, payer, risk, benefit, impact).

IEP / 504

  • Large-print AUP. Oral recommendation recorded on a school device that does not leave the district.
  • Reduce to two verbs in depth (deploy and regulate) if needed, still naming who pays.

Assessment

Formative

  • Dodge-rewrite warmup.
  • AUP highlights during guided practice.

Summative

  • Four-verb grid plus ten-line recommendation scored on named humans, payers, and a long-term impact.
  • Block extension: mock board testimony (seminar) and a 400-word policy memo.

Success criteria

  • Uses all four verbs, or honestly marks one as not visible in the documents and says what is missing.
  • Cites the AUP and this standards document as human regulatory choices.
  • Names who decides and who pays; does not leave responsibility with the algorithm.

Responsible use

This is a policy-analysis lesson, not a campaign. Students may disagree. They may not harvest classmates’ political affiliations. Use public documents. Offline print is sufficient. Do not submit student memos to a model for scoring.

Ethics

The ethical core of the standard is that benefits, risks, and long-term impacts attach to human choices. Treating software as the chooser is itself a choice that shields people with power. Students should practice naming those people without contempt and without hero-worship of industry or of bans.

Privacy

AUPs and vendor contracts often determine whether student work becomes a product input. FERPA requires care with education records; a board that deploys a tool without a data agreement is making a privacy choice. Class discussion uses public policy text, not real students’ flagged essays. Political opinions in memos are student work and should be stored like other assignments.

Reflection

  1. Where did you previously say the algorithm when you could have named a person or a board?
  2. Which payer did you not see until the accountability map?
  3. What long-term impact do you want this school’s AUP to take seriously?

Homework

Read the rest of the AUP (or sample) on paper. Write eight sentences: one human choice you found, one silence that functions as a choice, who currently pays, and one amendment you would testify for. Do not post the AUP to a public model.

Closing

Return to the three dodges from the warm-up and read student rewrites that name humans. Collect grids. Students should leave this subdomain knowing that using, designing, deploying, and regulating are things people do — and that people, not the algorithm, choose.

Extensions

  • 90-minute block: mock school-board hearing with public comment and a written motion (seminar and writing).
  • Optional attendance at a real board meeting; alternative is a recorded past meeting.
  • Trace one vendor contract’s data-use clause (public redacted version) for FERPA and training language.
  • Capstone: a senior letter to a specific body (board, legislature, county) that uses evidence from EP and IS, sent only if the student and family choose.

Cross-curricular links

Government / civics
Local boards, LEAs, state standards, and federal legislative process, including inaction as a choice.
Economics
Who captures surplus, who pays externalities, fiscal notes on detector or license purchases.
Business / CTE
Procurement, vendors, and contract clauses as design-plus-deployment.
English
Policy memo genre: named actor, named cost, dated evidence.

Back to contents

AI Technical Aptitude · Data and Analysis

9-12.AITA.DA.1

Make the Text Behave

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Use a digital tool to clean and organize text-based data.

Example from the standards. Students can split text into words, sort by frequency or collate, normalize spelling, remove punctuation, and make everything lowercase.

Student-friendly learning targets

  • I can turn messy text into a clean, lowercase word list by splitting, stripping punctuation, and normalizing spelling.
  • I can build a frequency table that collates the same word written different ways.
  • I can name which cleaning step I used and why it changes what a model would count.

Essential questions

  1. Why does a computer treat Boise, BOISE, and boise, as three different words?
  2. Which cleaning steps help a model, and which steps can hide meaning we actually need?
  3. What does a frequency list reveal that a raw paragraph hides?

Objectives

  1. Split a public Idaho text dump into tokens using a spreadsheet formula or a printed tally sheet.
  2. Normalize case, punctuation, and a short spelling-variant list (Boise/BOISE/boise,).
  3. Collate tokens into a sorted frequency table and report the top ten words.
  4. Explain one cleaning choice that would change a downstream word-count feature.

Key vocabulary

Token
A single unit of text after splitting, usually a word. Cleaning decides what counts as one token.
Normalization
Making the same idea look the same to a computer: lowercase, stripped punctuation, agreed spellings.
Collate
Group matching tokens together so Boise, BOISE, and boise count as one word, not three.
Frequency table
A two-column list of each unique token and how many times it appears after cleaning.
Stop word
A very common word (the, and, of) that often adds little meaning. Removing them is a choice, not a law.

Teacher background

Models that read text do not see paragraphs; they see tokens. If students leave punctuation glued to words, BOISE and Boise stay different features, and a frequency model learns noise. This lesson is spreadsheet-first: LOWER, SUBSTITUTE or TRIM, SPLIT or Text to Columns, UNIQUE, COUNTIF, and SORT produce a clean bag-of-words table without writing Python. The standard example is the whole lab: split, sort or collate, normalize spelling, remove punctuation, lowercase. Warn students that aggressive cleaning can erase signal (Idaho vs. idaho is fine to merge; 208-area phone fragments or named rivers may not be). Keep the source public: NWS fire-weather discussions, USDA crop notes, or Idaho Fish and Game weekly fishing blurbs. Never paste student essays, names, or school emails into a tool.

Materials

  • One public messy text file (printed and CSV): mixed-case Idaho wildfire incident names plus a few crop-report sentences, with punctuation and spelling variants.
  • Spreadsheet (Google Sheets, Excel, or LibreOffice Calc) with a starter tab of formulas; printed formula crib sheet.
  • Offline pack: the same text cut into word cards, punctuation stickers, and a tally sheet.
  • Short spelling-variant key: Boise/BOISE/boise,; wildfire/wild fire/Wildfire; russet/Russet/RUSSET.
  • Projector for a 6-row before/after demo.
  • Exit ticket half-sheet: top-ten table plus one sentence on a cleaning tradeoff.

Before class

  • Build a 40–60 token messy corpus from public NIFC incident names and a USDA Idaho crop brief. Include at least five punctuation glues (Boise,) and three spelling variants.
  • Pre-load a spreadsheet with a RAW column and empty CLEAN / TOKEN / COUNT columns. Hide the KEY tab until guided practice.
  • Print the offline card-sort pack (one per pair) for no-device and substitute days.
  • Confirm the district allows the spreadsheet tool offline or via cached files; no login-walled AI required.
  • Decide the stop-word rule for today: keep them in period 1, optional removal in the 90-minute block.

Instructional sequence

Warm-up — Three labels, one city

5 min
  1. Show three cells: Boise | BOISE | boise, and ask which the spreadsheet treats as the same word.
  2. Students vote on paper: same, different, or it depends. Reveal that without cleaning they are three different strings.
  3. Name the job of the hour: make the text behave so counts mean something.

Direct instruction — The five cleaning moves

8 min
  1. Write the pipeline on the board: lowercase, strip punctuation, split on spaces, normalize spelling, collate and sort by frequency.
  2. Demo LOWER() and a nested SUBSTITUTE that peels commas and periods off one cell. Show Text to Columns or SPLIT as the split step.
  3. Collate with UNIQUE plus COUNTIF, then SORT the count column descending. Circle the top token.
  4. State the rule: we clean on a copy; the RAW column stays untouched so we can audit.

Guided practice — We-do on eight wildfire names

12 min
  1. Project eight messy incident strings (e.g., 'Pioneer Fire', 'PIONEER fire.', 'pioneer-fire'). Students predict the token count before cleaning.
  2. Walk LOWER, punctuation strip, and a find/replace of hyphen to space. Recount as a class.
  3. Build the frequency table together. Ask why 'fire' now dominates and whether that is useful for an incident-name model.
  4. If devices fail, do the same eight strings as a card sort: lowercase stickers, drop comma cards, stack duplicates, tally.

Independent practice — Clean the crop-note paragraph

10 min
  1. Each student (or pair) gets the remaining public crop-note text, about 80–120 words.
  2. They produce a cleaned token column and a frequency table of at least the top ten words.
  3. They mark one spelling merge they made and one token they refused to merge, with a reason.
  4. Offline path: highlight on the printed paragraph, list unique words, tally in the margin.

Real-world examples

  • Idaho Fish and Game weekly fishing reports: the same reach of the South Fork is written South Fork, S. Fork, and southfork; a count of mentions is wrong until those collapse.
  • NWS fire-weather discussions for the Boise foothills mix ALL CAPS headlines with sentence case; a keyword alert for red flag needs lowercase plus punctuation strip.
  • USDA NASS Idaho potato notes spell russet, Russet Burbank, and R. Burbank; a variety-frequency feature is garbage until a spelling key exists.
  • High school sports recaps from public maxpreps-style pages glue team names to scores (Vandals,); splitting and stripping is the first stats step.

Hands-on activity

Hands-on — Top-ten table and a cleaning log

10 min
  1. Students finish the frequency table and copy the top ten onto the exit ticket.
  2. They complete a three-line cleaning log: what they lowercased, what punctuation they removed, which spelling variants they collated.
  3. Spot-check one row against RAW so they practice audit, not just formula trust.
  4. Quick pair swap: partner tries to break the table by finding a token that still has punctuation.

Discussion questions

  1. If we delete the word fire from every wildfire name, what do we gain and what do we lose?
  2. Should 208 or I-84 stay in a token list of Idaho texts? When is a 'number' actually a place?
  3. A model trained on unclean text looks confident. How would you prove the confidence is counting junk?
  4. Who should write the spelling key for russet vs. Burbank — a data intern or a Magic Valley grower?

Differentiation

Support

  • Give a formula strip with LOWER, SUBSTITUTE, and COUNTIF already filled; students only paste and sort.
  • Start with a 20-token card sort before the spreadsheet so the idea is physical.

Challenge

  • Add a stop-word list and rebuild the top ten; write when stop-word removal would hide a signal (e.g., not in a phrase like 'not irrigated').
  • Write one extra column that flags tokens containing digits (I-84, 2024) and argue keep vs. drop.

Multilingual learners

  • Allow a two-language spelling key (Spanish/English crop terms such as papa/potato) and treat them as variants only if the task says they mean the same.
  • Provide the pipeline verbs on a bilingual strip: lowercase, strip, split, collate, sort.

IEP / 504

  • Large-print messy text and a one-page pipeline diagram; extra time on the frequency table, not extra tokens.
  • Speech-to-text is fine for the cleaning log; the data itself stays the public handout, never a personal recording.

Assessment

Formative

  • Warm-up vote plus the eight-name we-do table.
  • Cleaning log: three moves named in student language.

Summative

  • Exit ticket: top-ten frequency table from the crop notes, plus one sentence on a merge they refused.
  • Success if the table is sorted, tokens are lowercase without trailing punctuation, and the refused merge is justified.

Success criteria

  • Tokens are lowercase and free of attached commas/periods.
  • Spelling variants from the key are collated, not triple-counted.
  • Student can point to the RAW column and the CLEAN column and explain the difference.

Responsible use

Use only the public handout or a teacher-provided public scrape. Do not paste classmate writing, social posts, or anything with a student name into a cloud spreadsheet or an AI cleaner. District-approved tools only; no login-walled scrapers.

Ethics

Cleaning is not neutral. Dropping dialect spellings, tribal place names, or Spanish crop terms can make a model look neater while erasing who is in the data. Students must log the merges they make.

Privacy

FERPA: this lab uses public wildfire names and crop notes, never student PII, emails, or school IDs. If a student spots a personal name in a public scrape, flag it and redact before sharing.

Reflection

  1. Which cleaning step changed the top ten the most, and why?
  2. What would a Magic Valley agronomist say we over-cleaned?
  3. How would you teach a ninth-grader the difference between RAW and CLEAN in one sentence?

Homework

On paper, take a public 6–8 sentence Idaho weather or sports blurb (printed in class). List ten tokens before cleaning and ten after. Circle one punctuation strip and one spelling merge. Do not use a personal message thread.

Closing

Hold up the before/after of Boise / BOISE / boise,. Say: models count strings, not cities, until we make the text behave. Tomorrow a number will pretend to be a word.

Extensions

  • 90-minute block: add stop-word removal, a bigram column (two-word phrases such as red flag), and a second public source (river-gauge comments) to compare top tens.
  • Python notebook extension (not required): split with a regex, lower, and Counter; compare the notebook top ten to the spreadsheet top ten and explain mismatches.
  • Build a class spelling dictionary for Idaho place names and reuse it in DA.4.
  • Trace a printed paragraph with colored pencils (case / punctuation / variants) for a no-device sub plan.

Cross-curricular links

English Language Arts
Tokenizing is close to word study: students see how punctuation and capitalization change what counts as a word.
Statistics
A frequency table is a distribution; students can talk mode and long tail (the vs. Pioneer).
Agriculture / CTE
Crop notes and variety names are the messy text growers actually produce; cleaning is a farm-office skill.

Back to contents

AI Technical Aptitude · Data and Analysis

9-12.AITA.DA.2

When a Number Is a Word

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Evaluate different approaches to verifying consistency and compliance with expected data types, values, and ranges.

Example from the standards. While preparing a data source for use, a column of numerical data has a row with a word/string.

Student-friendly learning targets

  • I can name the type, allowed values, and range a column is supposed to have before I trust it.
  • I can catch a word sitting in a number column and compare at least two ways to handle it.
  • I can argue why deleting the row, recoding it, or flagging it are different scientific choices.

Essential questions

  1. How do you know a cell that looks like 12.4 is actually a number a model can use?
  2. When is ice, NA, or trace a missing value, a real measurement, or a lie?
  3. Which check should run first: type, range, or allowed-value list?

Objectives

  1. Write a one-line schema for each column: type, units, legal min/max, and missing-value codes.
  2. Apply at least three verification approaches (type check, range check, allowed-list, duplicate key, visual scan) to a messy public table.
  3. Evaluate tradeoffs of drop, impute, recode, or quarantine for a string in a numeric column.
  4. Document a validation rule a teammate could rerun.

Key vocabulary

Data type
What kind of value a column should hold: number, text, date, true/false. A word in a number column is a type violation.
Range check
A test that a number sits between a real-world min and max (Snake River discharge cannot be −50 cfs).
Schema
The contract for a table: column names, types, units, allowed values, and missing codes, written before cleaning.
Sentinel value
A fake number used to mean missing (9999, −999, 0). It will wreck averages if you treat it as real.
Quarantine
Move suspect rows to a review sheet instead of deleting them so the original evidence survives.

Teacher background

The standard is evaluation, not a single 'fix.' When a numeric discharge column contains ice or NA, students must compare approaches: spreadsheet ISNUMBER / VALUE, a printed type-tally, a range gate (cfs > 0), an allowed-list for quality flags, and a human visual scan of the first 30 rows. Deleting the row is one approach and often the worst: ice on a USGS gauge is information. Recoding ice to missing, adding a quality-flag column, or quarantining for a hydrologist are competing designs. Use a public USGS Snake River or Boise River gauge extract plus a USDA potato-yield slice with n/a and a typo like 'tweleve'. Spreadsheet-first: data validation rules, COUNTIF of non-numeric, MIN/MAX vs. stated range. Python type checks are an extension.

Materials

  • Messy CSV (and printed table): USGS-style daily discharge with numbers, ice, ---, NA, and one 'offline' row; a yield column with n/a and a word.
  • Blank schema card per pair: column, type, units, min, max, missing codes.
  • Approach cards to sort: type check, range check, allowed list, duplicate key, visual scan, checksum, plot.
  • Spreadsheet with ISNUMBER, VALUE, COUNTIF, MIN, MAX; printed formula crib.
  • Red/yellow/green flags (paper) for drop / recode / quarantine.
  • Exit ticket: one violated row and two evaluated approaches.

Before class

  • Build a 25-row public-looking table: site_id, date, discharge_cfs, water_temp_c, potato_cwt_per_acre. Plant at least six violations (string in number, 9999 sentinel, negative yield, future date, duplicate site-date, temp 140 F labeled as C).
  • Print the table for offline; highlight nothing — students find the faults.
  • Write the 'true' schema on a teacher key: discharge 0–200000 cfs, temp −2 to 30 C, yield 0–800 cwt/acre.
  • Practice the ice conversation: ice is not a number and not garbage; it is a condition code.

Instructional sequence

Warm-up — Spot the fake number

5 min
  1. Project one column: 4200, 4188, ice, 4301, NA, 12, 9999. Students mark which cells a SUM would silently destroy.
  2. Collect two nominations. Do not fix yet. Name the hour: verify before you average.

Direct instruction — Five ways to catch a liar cell

10 min
  1. Write the schema first: type, units, min, max, missing codes. A check without a schema is a vibe.
  2. Approach 1 — type: ISNUMBER / VALUE / 'does it parse as a float?' Approach 2 — range: compare to physics and Idaho climate. Approach 3 — allowed list: ice, NA, --- are codes, not yields.
  3. Approach 4 — visual scan of head/tail/random rows. Approach 5 — plot or MIN/MAX to catch 9999.
  4. List four responses: drop the row, recode to missing, split codes into a flag column, quarantine. None is always right.

Guided practice — Schema, then hunt

12 min
  1. Pairs fill the schema card for discharge_cfs and potato_cwt_per_acre before looking at the messy rows.
  2. Run a type check together on discharge (spreadsheet or printed circle-the-words). Count string cells.
  3. Run a range check on yield. Debate 9999: sentinel or world-record field?
  4. As a class, pick a response for ice and write the reason in one sentence.

Independent practice — Evaluate, don't just delete

10 min
  1. Each student chooses two remaining violations and, for each, names two approaches that would catch it and one that would miss it.
  2. They recommend drop, recode, flag, or quarantine and state who would be harmed if they chose wrong (a hydrologist, a grower, a model).
  3. Offline: annotate the printed table with approach initials (T/R/A/V/P).

Real-world examples

  • USGS Snake River at Hells Canyon: winter rows really do say ice instead of cfs. Averaging ice as zero invents a dry river.
  • Idaho Power load tables sometimes store offline or DST as text in a MW column; a peak-load model will skip or crash.
  • County potato yield spreadsheets use n/a, NA, and blank for unharvested acres; those are different facts.
  • Boise River flood stage in feet mixed with a row in meters will pass a type check and fail a range check — two approaches, two different bugs.

Hands-on activity

Hands-on — Validation rule on a sticky

8 min
  1. Students write one reusable rule: 'discharge_cfs must be numeric and 0–200000; ice/NA go to flag column, not to cfs.'
  2. They apply the rule to the 25-row table and report how many rows pass.
  3. Group share: which approach is cheapest, which is most trustworthy, which still needs a human.

Discussion questions

  1. Why is deleting every non-numeric row a dangerous default for river gauges?
  2. A range check says 140 C water is impossible. Could the unit be Fahrenheit mislabeled? How do you find out?
  3. Which approach would still miss a yield of 400 that is a typo for 40?
  4. If two counties use different missing codes, whose schema wins in a statewide model?

Differentiation

Support

  • Pre-filled schema with blanks only for min/max; fewer rows (12) with violations already highlighted in a support copy.
  • Sentence stems: 'This cell fails a ___ check because ___ . I would ___ because ___.'

Challenge

  • Design a two-pass checker: type then range then cross-field (temp vs. month). Find the 140 C / F mixup.
  • Argue whether 0 cfs is a legal min for an irrigated canal vs. the Snake.

Multilingual learners

  • Missing-code list in English/Spanish (n/a, s/d, sin datos) so students see allowed-lists are language-aware.
  • Keep units spoken and written (cfs, pies cubicos por segundo) on the schema card.

IEP / 504

  • Printed table with extra row spacing; students may check only type and range, not all five approaches.
  • Allow oral evaluation of one violation if writing is the barrier; the thinking is the standard.

Assessment

Formative

  • Schema card completeness before the hunt.
  • Color flags on ice / 9999 / n/a during guided practice.

Summative

  • Exit ticket: one string-in-number row, two approaches that catch it, recommended response with a harm statement.
  • Do not score 'deleted the row' as complete unless the student evaluated another approach and rejected it.

Success criteria

  • Student writes type, range, and missing codes for at least one column.
  • Student compares two verification approaches, not just one fix.
  • Student treats ice/NA as codes to evaluate, not as automatic trash.

Responsible use

Validate on public tables. Do not import class gradebooks, health surveys, or anything with student IDs to 'practice' type checks.

Ethics

Dropping every messy row can drop every winter day, every small farm, or every Spanish-labeled sheet. Verification choices move who is represented.

Privacy

Public USGS/USDA extracts only. If a classroom export ever appears, stop: FERPA forbids using student records as dummy data.

Reflection

  1. Which approach would you run first on a new CSV, and why?
  2. When is a human visual scan still better than ISNUMBER?
  3. What will you refuse to auto-delete after today?

Homework

Printed 10-row energy-load table (teacher handout). Write a schema for MW and timestamp. Circle every type or range violation. Propose drop, recode, flag, or quarantine for two of them. No personal utility bills.

Closing

Point at ice in the discharge column: that is a word doing a number's job, and it is also a fact. Verification is a set of approaches, not a delete key. Next we walk a whole potato-yield file from raw to train/dev/test.

Extensions

  • 90-minute block: add a second table (Idaho energy load) and write spreadsheet data-validation rules that reject new bad rows on entry.
  • Python extension: pandas to_numeric(errors='coerce') vs. a regex type check; compare how each treats ice and 1,200 with a comma.
  • Card-sort the seven approach cards onto 'catches ice', 'catches 9999', 'catches unit mixup', 'catches nothing here'.
  • Invite a guest (county GIS, irrigation district) to say which missing codes they actually use.

Cross-curricular links

Mathematics
Domain and range of a function are the same idea as a column schema; 9999 is an outlier only after you define the domain.
Earth science
Gauge ice and flood stage are physical constraints that make range checks more than computer hygiene.
Statistics
Mean and standard deviation lie if sentinels stay in the column; verification is a prerequisite to any summary.

Back to contents

AI Technical Aptitude · Data and Analysis

9-12.AITA.DA.3

Collect, Split, Then Train

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Examine the procedure of how data is used to train machine learning models.

Clarification. The lifecycle of collecting and munging data, identifying features, and creating train/dev/test data splits.

Student-friendly learning targets

  • I can walk a public CSV from collection notes through munging, feature choices, and a train/dev/test split.
  • I can tell a feature from a target and explain why the test rows stay sealed.
  • I can split a small Idaho table by hand without leaking the test set into training.

Essential questions

  1. If the model has already seen the test rows, what is left to test?
  2. Which columns are features we might use, and which column is the thing we want to predict?
  3. What gets lost when we skip munging and jump to 'train'?

Objectives

  1. Station-lab a potato-yield or wildfire CSV: source, mung, features, splits.
  2. Identify target vs. candidate features and drop at least one leaky or identifier column.
  3. Create a train / dev / test split (e.g., 70/15/15) with a documented rule (random with seed, or by year, or by county).
  4. Explain in one sentence why collection and munging happen before any training.

Key vocabulary

Munging
The unglamorous cleaning and reshaping of raw tables so rows and columns can be used: types, missing values, units, duplicates.
Feature
An input column the model is allowed to use (April rainfall, county, seed variety). Not the answer column.
Target
The column we want to predict (yield in cwt/acre, or did this grid cell ignite).
Train / dev / test split
Three disjoint slices: train fits the model, dev (validation) tunes choices, test is used once to report honesty.
Leakage
Letting the model see information it would not have at prediction time, including test rows or future yields.

Teacher background

This is the data-lifecycle lab, not the methods lecture. AIM.8 covers the same procedure from a methods angle (pipeline diagram, feature engineering, leakage card-sort). DA.3 is stations with a real-feeling public CSV in students' hands. Use Idaho potato yield by county-year (USDA NASS public) or a simplified wildfire-start table (grid_id, date, temp, RH, wind, ignition). Students do not train a model. They collect provenance, mung a few dirty rows, name features vs. target, then physically split colored row cards into train/dev/test. Emphasize sealing the test envelope. Spreadsheet FILTER/RAND is enough; Python train_test_split is an extension. Do not spend this period on backprop, trees, or XOR — that is DA.6 / AIM.5.

Materials

  • Station kits (4): COLLECT, MUNG, FEATURES, SPLIT. Printed CSV of 40 rows (potato yield by Idaho county-year or wildfire weather + ignition).
  • Row cards (one card per row) in an envelope for the split station; three bins labeled TRAIN / DEV / TEST.
  • Spreadsheet copy of the same CSV; printed version for offline.
  • Provenance slip: dataset name, public URL or agency (USDA NASS / NIFC-style), date retrieved, license/public-domain note.
  • Feature sticky pads: keep / drop / not sure.
  • Teacher key with a recommended target (yield or ignition) and two leaky columns (final_harvest_notes, post_fire_acres — not known at prediction time).

Before class

  • Build the 40-row public-style table with 4 dirty rows (n/a yield, mixed county names, duplicate year, a future-season leak column).
  • Set up four physical stations; 90-second rotation timer. For a short period, run two rounds of 8 minutes.
  • Print AIM.8 cross-reference on the teacher desk: if students ask about feature engineering depth or leakage types, park it ('methods view is AIM.8').
  • Cut row cards and shuffle. Put a 'TEST — do not open until the end of the unit' sticker on the test bin.

Instructional sequence

Warm-up — Would you grade your own homework?

5 min
  1. Ask: a student studies the answer key, then takes the same quiz. Fair test of learning?
  2. Map it: training on all rows then 'testing' on those rows is the answer-key trick.
  3. Preview stations: collect, mung, features, split — then, and only then, would someone train.

Direct instruction — Lifecycle in one pass

8 min
  1. Board the sequence: collect (where from, who measured) → mung (DA.1–DA.2 skills) → identify features and target → split train/dev/test → (later) train. Circle that we stop before train.
  2. Define target vs. feature with yield: target is cwt_per_acre; county, rain_apr, seed_variety can be features; farm_id is an identifier; post_harvest_price is a leak if unknown at planting.
  3. Draw 70/15/15 boxes. Test is a sealed envelope. Dev is for trying cleaning or model choices. Train is the only place a future algorithm may look repeatedly.

Guided practice — Name the target on row one

8 min
  1. Project the CSV header. Class votes: which column is the target for a yield model?
  2. Mark two columns as leaks or IDs and say why they must not be features.
  3. Demonstrate one mung: collapse Canyon / canyon / Canyon Co. and recode n/a yield to missing, not zero.

Independent practice — Station pass — collect and mung

8 min
  1. Half the pairs start at COLLECT (fill provenance slip) then MUNG (fix two dirty rows on paper or sheet).
  2. The other half start at FEATURES (keep/drop stickies) then SPLIT (deal row cards into 70/15/15, write the rule).
  3. Rotate once so every pair hits all four before hands-on wrap. Offline: the printed CSV is the station.

Real-world examples

  • USDA NASS Idaho potato production by county is collected by survey, not by a model; if you skip provenance you will double-count a revised year.
  • A wildfire-start table that includes final containment acres as a feature is leaking the future — crews do not know that on the ignition morning.
  • Energy-load models at Idaho Power split by time: you train on past days and test on later days, not a random shuffle that puts Tuesday afternoon in both.
  • University of Idaho variety trials: seed lot IDs look like features but only name the row; using them lets a model memorize plots instead of weather.

Hands-on activity

Hands-on — Finish the four stations

16 min
  1. COLLECT: complete agency, year range, public-use note, and one thing the CSV does not measure (e.g., irrigation method).
  2. MUNG: log each dirty row and the DA.2-style response (flag, recode, quarantine).
  3. FEATURES: list target, at least four candidate features, and one dropped leak/ID.
  4. SPLIT: place cards, record counts, write 'test envelope stays closed.' Photograph or tally bins. No model is trained.

Discussion questions

  1. Random 70/15/15 vs. split by year: which is honest for predicting next season's yield?
  2. If Canyon County has twice as many rows as Clark County, what happens to a random split?
  3. Why do we need three piles, not two (train and test)?
  4. What would count as leakage in a river-gauge forecasting table?

Differentiation

Support

  • Target column pre-highlighted; students only choose features and place cards into bins with printed 70/15/15 counts (28/6/6 of 40).
  • Mung station limited to two error types already seen in DA.2.

Challenge

  • Design a stratified split so each of four counties appears in train, dev, and test. Show the counts.
  • Find a leakage column the teacher did not flag and argue it.

Multilingual learners

  • Station header cards with verbs: collect / limpiar (mung) / features (entradas) / split (partir).
  • Allow provenance slip in the student's strongest language; column names stay English as in the CSV.

IEP / 504

  • Stay at two stations if four is overload: FEATURES and SPLIT are the standard's core.
  • Large row cards and bins; a partner may handle the tally while the student decides keep/drop.

Assessment

Formative

  • Provenance slip and keep/drop stickies at stations.
  • Teacher checks that test cards are not mixed back into train.

Summative

  • Station packet: source note, mung log, feature list with target, split counts and rule, one leakage sentence.
  • No points for training a model; this lab ends at the split.

Success criteria

  • Student names a target and at least three legal features from the CSV.
  • Student produces disjoint train/dev/test counts that add to all rows.
  • Student can explain why the test bin stays sealed.

Responsible use

Public NASS/NIFC-style tables only. Do not collect classmate farm, address, or family yield data. The 'collect' station is provenance of an existing public file, not a new student survey.

Ethics

A split that leaves every small county in train and every large county in test (or the reverse) will lie about performance. Who is in which bin is a fairness issue, not just a math one.

Privacy

FERPA: no student names on row cards. If you ever localize with a co-op dataset, strip names, phone numbers, and section-township-range that identifies a family farm before it enters the room.

Reflection

  1. Where in the four stations did you almost skip a step, and what would have broken?
  2. How will you explain 'sealed test' to someone who just wants to train?
  3. What did this CSV not collect that a grower would care about?

Homework

On the printed 12-row mini-table, circle the target, list three features, cross out one leak, and assign each row T, D, or S using a 8/2/2 split. Write the split rule in one line. No training.

Closing

Hold the TEST envelope: this is the honest exam. We collected, munged, named features, and split. We did not train — on purpose. AIM.8 will show the same pipeline from the methods side, including feature engineering and leakage traps.

Extensions

  • 90-minute block: second rotation with the wildfire CSV if potato was first (or the reverse); compare whether a random split is honest for time-based ignition.
  • Python extension: sklearn train_test_split twice to make train/dev/test; print value_counts by county to show a bad shuffle.
  • Do not duplicate AIM.8: if you have extra time, deepen the CSV work, not a lecture on feature engineering.
  • Printed tracing: number each row 1–40 and color train/dev/test; hang the sealed test list.

Cross-curricular links

Statistics
Train/dev/test is a cousin of train/test and holdout; sampling design (by county vs. random) changes estimates.
Agriculture
Yield tables come from surveys and trials; collection quality caps any later model.
Geography
County and year are spatial-temporal units; splitting without geography can test on the wrong place.

Back to contents

AI Technical Aptitude · Data and Analysis

9-12.AITA.DA.4

From Web Page to Table

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Apply data acquisition, cleaning, and transformation techniques to prepare data for AI analysis.

Example from the standards. Use something like NotebookLM to scrape a website, then pull specific data out of the result for analysis.

Student-friendly learning targets

  • I can acquire a table from a public web page or a printed excerpt and say how I got it.
  • I can pull only the fields I need and transform them into typed columns ready for analysis.
  • I can refuse login walls, student PII, and district-unapproved scrapers.

Essential questions

  1. What is the difference between viewing a web page and having a table a model can use?
  2. If scraping is blocked, how do we still acquire the data ethically?
  3. Which transformations happen after acquisition, and which should have happened at the source?

Objectives

  1. Acquire rows from a public, no-login Idaho page (or a printed excerpt / CSV export of that page).
  2. Select specific fields (station, timestamp, value, units) and write them into a clean table.
  3. Apply DA.1–DA.2 cleaning and type checks so the table is analysis-ready.
  4. Document the acquisition method, URL or handout ID, retrieval date, and any terms of use.

Key vocabulary

Acquisition
Getting data from a source into a file you control: download, export, scrape, or typed transcription from a printout.
Scrape
Programmatically or manually pulling structured fields out of a web page that was built for humans to read.
Transformation
Changing shape or type after you have the raw pull: split fields, parse dates, convert units, reshape long vs. wide.
Field
One kind of fact you extract (stage_ft, cfs, county). A web paragraph may hide several fields in one sentence.
Terms of use
The source's rules for copying. Public government pages are usually usable; login walls and paywalls are not in this class.

Teacher background

The standards example names NotebookLM-style scrape-then-extract. In an Idaho classroom that tool may be blocked, require a login, or violate district AI policy. The lesson must still run: a printed NOAA river-gauge page, an Idaho Fish and Game fishing-report excerpt, an Idaho Power public dashboard screenshot, or a CSV export the teacher downloaded ahead of time. Students practice the intellectual move — page to fields to typed table — not a particular brand. No login walls. No crawling behind CAPTCHAs. Spreadsheet-first: paste, Text to Columns, date parse, unit column. If a district-approved extract tool exists, use it as one station, not the gate. Python BeautifulSoup is an extension.

Materials

  • Teacher-captured public page packets: (1) USGS/NOAA gauge excerpt for the Snake or Boise, (2) ISDA or USDA crop brief, (3) NWS fire-weather headline block. HTML file or PDF plus a CSV export of the same.
  • Blank target schema: station_id, datetime, metric, value, units, source_url, retrieved_on.
  • Spreadsheet starter; printed excerpt with highlighter colors per field.
  • Optional district-approved extract tool (NotebookLM or similar) on one station only, with the printed fallback at every other seat.
  • Acquisition log half-sheet.

Before class

  • Download and print the pages the night before so the lesson is offline-proof. Note retrieval date on every packet.
  • Check robots/terms at a glance: prefer .gov and .edu. Do not use social media or school portals.
  • If offering an approved extract tool, test it on the same page and save the output so a blocked login does not kill the period.
  • Strip any accidental person names from screenshots.

Instructional sequence

Warm-up — Page vs. table

5 min
  1. Project a river-gauge web paragraph: 'Boise River at Glenwood: 1,240 cfs, stage 4.8 ft, 14:00 MDT.'
  2. Students list the fields a model would want. Reveal a 1-row table with typed value and units.
  3. Name the gap: acquisition plus transformation.

Direct instruction — Acquire, select, transform, document

10 min
  1. Four verbs on the board. Acquire: download, export, approved extract, or transcribe from print. Select: only the fields in the schema. Transform: numbers, dates, units. Document: URL, time, method.
  2. Show a bad acquire: a login-walled dashboard and a social post. Both are out.
  3. Demo paste-from-PDF into a sheet, split on colons and commas, VALUE() the cfs, separate units.
  4. Remind: cleaning skills from DA.1–DA.2 apply immediately (1,240 has a comma; MDT is a timezone, not a number).

Guided practice — One paragraph, one row

12 min
  1. Class extracts the Glenwood sentence into the schema together.
  2. Handle 1,240 → 1240, ft vs. cfs as two rows or two columns (decide as a class and stick to it).
  3. Fill source_url and retrieved_on. If using a printed packet, the 'URL' is the handout ID.
  4. Offline groups highlight fields in four colors instead of typing, then copy onto the schema card.

Independent practice — Build a five-row analysis table

10 min
  1. Each pair gets one packet (gauges, crop, or fire weather) and must produce at least five clean rows.
  2. They run a type/range check on the value column (DA.2) and lowercase any text fields (DA.1).
  3. Acquisition log: method (print / CSV export / approved tool), date, and one field they refused because it was prose, not data.

Real-world examples

  • USGS waterdata pages for the Snake, Boise, and Payette: the HTML is for humans; the tabulated instantaneous values are what a flood model wants.
  • NWS Boise fire-weather forecasts bury red-flag wording in paragraphs; extracting RH, wind, and headline into columns is the AI-prep step.
  • Idaho Fish and Game fishing reports mix narrative with numbers (cfs, water temp); a stocking-recommendation model needs the numbers pulled out.
  • Idaho Power public energy dashboards: a screenshot is not a table until MW and timestamp are typed and time-zone aligned.

Hands-on activity

Hands-on — Ready-for-analysis stamp

8 min
  1. Pairs swap tables and try to break them: mixed units, leftover commas, missing retrieval date.
  2. If the table survives, stamp 'ready for analysis' on the log. If not, one fix cycle.
  3. Stack the five-row tables; these can feed DA.5 as example quality talk, still public.

Discussion questions

  1. Is typing from a printout still 'acquisition'? Why might it be more ethical than a blocked scraper?
  2. The page has a chart image but no numbers. What are your legal options?
  3. If two pairs extract the same paragraph and get different cfs, whose table should a model trust?
  4. When does transforming (unit conversion) become lying about the source?

Differentiation

Support

  • Highlight-by-color printout with a fill-in table; no live web.
  • Provide the CSV export and ask only for column selection and one unit transform.

Challenge

  • Reshape three metrics from one paragraph into long format (one metric per row) vs. wide; justify for a later model.
  • Write a repeatable extraction recipe another pair could follow on next week's page.

Multilingual learners

  • Packets include an English NWS excerpt and a Spanish public advisory if available; fields stay the same schema.
  • Glossary strip: acquire, scrape, field, units.

IEP / 504

  • One paragraph, two rows maximum; oral documentation of URL/handout ID.
  • Avoid timed scraping; the printed excerpt is the default, not a consolation.

Assessment

Formative

  • Glenwood we-do row and color highlighting.
  • Acquisition log method box filled before independent rows.

Summative

  • Five-row typed table matching the schema, plus log (source, date, method) and one type/range check.
  • Using a login-walled tool or a personal account scores as a process miss even if the table looks clean.

Success criteria

  • Rows have typed values, explicit units, and a documented public source.
  • Student selected fields rather than dumping the whole page.
  • Student can name the fallback they would use if scraping is unavailable.

Responsible use

District-approved tools only. No login walls, no password sharing, no school accounts fed into third-party scrapers. Prefer teacher-downloaded public files.

Ethics

A page can be public and still wrong, copyrighted as a compilation, or harmful if republished out of context. Acquisition includes reading the terms and not hammering a small agency server.

Privacy

Never scrape a class page, grade portal, or anything with student emails. FERPA applies even when 'it's just a demo.' Public river and crop pages only.

Reflection

  1. What did the web page know that your table still does not?
  2. Which acquisition method would you trust in a rural lab with weak Wi-Fi?
  3. How would you explain 'no login walls' to a teammate who just wants the easy tool?

Homework

Using only the printed fishing-report or gauge excerpt in the packet, extract three rows into the schema on paper. Fill source and date. Do not log into any site from home for this assignment.

Closing

A web page is a story; a table is a contract. We acquired public fields, transformed them, and wrote down how. If the fancy scraper is blocked tomorrow, the printout still works. Next we ask whether the examples in a table are even fair.

Extensions

  • 90-minute block: second source (crop + gauge) and a join on date; or a district-approved extract tool compared side-by-side with the print transcription (count mismatches).
  • Python extension: read a saved HTML file (not a live scrape of a login page) and pull a table with pandas.read_html; still document URL and date.
  • Card sort: 'legal acquire' vs. 'out of bounds' (school SIS, Instagram, .gov CSV, paywall PDF, printed NOAA).
  • Teacher-exported CSV only, for buildings with no student web access.

Cross-curricular links

Journalism / media
Citing the URL and retrieval date is the same discipline as quoting a source; tables need citations too.
Earth science
Gauge units and time zones are part of the measurement, not formatting trivia.
Civics
Public .gov data is a civic resource; scraping a private portal is not the same act.

Back to contents

AI Technical Aptitude · Data and Analysis

9-12.AITA.DA.5

Better Examples, Fairer Model

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Investigate ways to improve the accuracy of a machine learning model and reduce bias by refining the quality of examples and nonexamples in the training data.

Clarification. Students don't actually need to train a classifier, rather they can look at datasets and determine what might need to be done to improve the model, by augmenting the data.

Example from the standards. A speech recognizer only recognizes adult, male, standard American English speakers because it was trained on news transcripts from the 1960s. Augmenting with women and children and with more varied accents would make the recognizer more robust.

Student-friendly learning targets

  • I can inspect a training set's examples and nonexamples and say who or what is missing.
  • I can propose augmentation (more examples, better nonexamples, more variety) without training a model.
  • I can explain how a narrow example set makes a model both less accurate and more biased.

Essential questions

  1. If the model never saw it, why would we expect it to recognize it?
  2. What is a nonexample, and why are bad nonexamples as dangerous as missing examples?
  3. When does adding more data help, and when does it just add more of the same bias?

Objectives

  1. Audit a small labeled set (speech, crop disease, or smoke photos described on cards) for coverage gaps.
  2. Separate the 1960s-news-speech story into: who is overrepresented, who is missing, what to augment.
  3. Write an augmentation plan: what to add, what nonexamples to add, what not to scrape.
  4. Connect accuracy and fairness: a model can be accurate on its narrow test slice and fail everyone else.

Key vocabulary

Example
A training item of the class we care about (a 'smoke' photo, a 'blight' leaf, a child's speech clip).
Nonexample
A training item of what the class is not (steam, dust, a healthy leaf). Weak nonexamples make false alarms.
Augmentation
Adding or transforming training items so the set covers more of the real world (more speakers, more lighting, more counties).
Coverage gap
A slice of the real world with few or no training items (children's voices; dryland farms; night-time imagery).
Robust
Still works when inputs vary in ways the designers should have expected: accent, age, camera, weather.

Teacher background

The clarification is the pedagogy: do not train. Students read datasets (card decks that stand in for public corpora) and prescribe augmentation. Teach the standards example plainly: a recognizer trained on 1960s broadcast news heard mostly adult men in a single accent, so it fails women, children, and other Englishes. Accuracy on that old news test set can look fine. Idaho analogs: a blight classifier trained only on Treasure Valley russets under noon sun; a smoke detector trained only on Boise foothills daylight; a river-ice model trained only on low-elevation gauges. Nonexamples matter: if 'not blight' is only perfect lab leaves, the model will panic on dust. Spreadsheet audit of label counts by group beats a GPU. No student voice recordings.

Materials

  • Card deck A: 24 'training clips' described on paper (adult male broadcast, adult male broadcast, ... plus 2 women, 0 children, 0 Spanish-accented English).
  • Card deck B: crop-leaf labels — 18 russet blight, 2 healthy russet, 0 other varieties, 0 Palouse wheat, 0 night photos.
  • Card deck C: wildfire smoke vs. not-smoke — smoke at noon, steam from a mill, irrigation dust; missing night and high-elevation.
  • Augmentation plan template: add / transform / collect-ethically / do-not-collect.
  • Printed standards example quote for close reading.
  • Tally sheet by group (speaker, crop, lighting, county).

Before class

  • Print decks; the 'dataset' is the cards. Do not ask students to record their voices or photograph classmates.
  • Pre-count the imbalances so you can coach without spoiling the find.
  • Have the speech-example quote on the board for the last five minutes of direct instruction.

Instructional sequence

Warm-up — Who is in the room on these cards?

5 min
  1. Deal deck A face up. Students tally speaker type in 60 seconds.
  2. Ask: if this is the whole training set, whose words will the recognizer miss?
  3. Read the standard example aloud once, without unpacking yet.

Direct instruction — Examples, nonexamples, augment

10 min
  1. Define example vs. nonexample with blight/healthy and smoke/steam.
  2. Walk the 1960s news story: overrepresented (adult male standard broadcast English), missing (women, children, varied accents), result (recognizer not robust), fix (augment, do not just collect more of the same men).
  3. Show a bad augment: 10,000 more identical russet noon photos. Quantity is not coverage.
  4. Show a bad nonexample set: 'not smoke' is only blue sky, so mill steam pages crews.

Guided practice — Audit deck B together

12 min
  1. Tally variety, disease, lighting, county on the crop deck.
  2. List coverage gaps: other varieties, dryland, cloudy days, healthy leaves with dust.
  3. Draft one augmentation sentence as a class: 'Add 30 labeled healthy and diseased leaves from Palouse wheat and Magic Valley sugar beet, including dusty nonexamples, from public research photos — not student phones.'

Independent practice — Prescribe for deck C (or A)

10 min
  1. Pairs pick smoke or speech remainder. Fill the plan template: three adds, one nonexample improvement, one ethical no (no classmate recordings, no private farms).
  2. They must say how they would check that the new items are labeled correctly (who verifies blight?).
  3. Offline is the default: cards and template, no training UI.

Real-world examples

  • Speech: the standards 1960s news story; Idaho 911 audio would fail the same way if trained only on adult dispatchers.
  • Crop disease: a U of I extension model trained on irrigated russets will misread dryland Palouse wheat fungus.
  • Wildfire smoke cameras in the Boise foothills at noon will treat mill steam in Lewiston or canal dust in the Magic Valley as fire — missing nonexamples.
  • River ice-on/ice-off trained only on Treasure Valley gauges will not represent high Sawtooth streams.

Hands-on activity

Hands-on — Before/after coverage table

8 min
  1. Students fill a two-column table: current counts by group vs. proposed counts after augmentation.
  2. They star any group that is still zero (a remaining fairness hole).
  3. Quick gallery: one gap per pair on the board.

Discussion questions

  1. Why can accuracy go up on the old test set while the model gets less fair?
  2. Is a synthetic (computer-drawn) blight leaf a legitimate augment? What could go wrong?
  3. Who should label the new nonexamples — a student intern or a plant pathologist?
  4. When should we refuse to collect a group even if it would help the model (children's voices at home, tribal land imagery)?

Differentiation

Support

  • Tally boxes pre-drawn; students only count and copy a sentence stem for the plan.
  • Use deck A only; it matches the written example most closely.

Challenge

  • Design a sampling quota (min 20% night, min three counties, min two varieties) and explain how it fights bias without claiming the model is 'unbiased.'
  • Critique a fake 'we added 1 million images' press release that does not change the mix.

Multilingual learners

  • Speech deck includes language/accent as a tally column; discuss that 'standard American English' is one variety, not the correct one.
  • Allow the augmentation plan in the student's strongest language with English dataset nouns.

IEP / 504

  • Fewer cards (12) with large labels; oral plan is accepted.
  • Avoid audio playback of 'bad recognizer' demos that can be frustrating; stay on paper descriptions.

Assessment

Formative

  • Warm-up tally of deck A.
  • Class augmentation sentence for deck B.

Summative

  • Completed plan template: gaps named, examples and nonexamples addressed, one ethical refusal, no claim that they trained a model.
  • A student who proposes 'just train longer' without changing the set has not met the standard.

Success criteria

  • Student distinguishes examples from nonexamples.
  • Student proposes augmentation that changes coverage, not just volume.
  • Student never uses classmate PII or private recordings as the fix.

Responsible use

Do not record students to 'improve' a speech set. Do not scrape classmates' photos. Use described public corpora and teacher cards.

Ethics

Augmentation can become surveillance: collecting more of a group without consent is not fairness. Some gaps should be filled with public research sets or by declining the product.

Privacy

FERPA and basic dignity: no student voices, faces, or home farms. Children's speech in the example is a research-ethics topic, not a homework recording.

Reflection

  1. Which missing group in your deck would cause the most harm if ignored?
  2. How is a nonexample different from 'just more data'?
  3. What will you say the next time someone boasts about dataset size only?

Homework

Reread the printed speech-recognizer example. In five sentences: who is overrepresented, who is missing, what nonexamples might be missing, what you would add from public sources, and what you would refuse to collect.

Closing

The model is what it ate. Better examples and harder nonexamples beat a bigger pile of the same men, the same russets, the same noon photos. We still have not trained — we prescribed. Next we pick a model that actually fits the job, including XOR.

Extensions

  • 90-minute block: second deck plus a spreadsheet pivot of labels by county; write a one-page memo to an extension agent.
  • Python extension: plot class counts from a public CSV (no training); students still write the augmentation plan in prose.
  • Card-sort 'helps coverage' vs. 'more of the same' vs. 'unethical to collect'.
  • Connect forward to DA.7 (critique ImageNet) as the large-corpus version of this audit.

Cross-curricular links

Health / CTE audio
Speech tech in clinics fails when training missed women, children, and accented English — the standards example is a patient-safety story.
Agriculture
Disease libraries must include the crops and counties actually farmed, not only the research station's favorite variety.
Civics
Who is missing from a government dataset is a representation question, not only a tech one.

Back to contents

AI Technical Aptitude · Data and Analysis

9-12.AITA.DA.6

Pick the Model That Fits

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Justify the selection of a type of machine learning model to accomplish a task.

Example from the standards. The XOR problem is best solved by rule-based logic (and is not solvable with a linear classifier), but ambiguous problems like question-answering using text are better solved with data on more complex models like LLMs.

Student-friendly learning targets

  • I can explain XOR in plain language and show why one straight line cannot separate its points.
  • I can justify rule-based logic vs. a linear classifier vs. a more complex data-driven model for a given task.
  • I can match an Idaho job (irrigation, yield, smoke photos, messy text questions) to a model family and defend the pick.

Essential questions

  1. When is a two-line IF statement smarter than a 'learning' model?
  2. What does it mean that a linear classifier cannot solve XOR?
  3. Why do messy language questions want lots of data and a complex model instead of a tidy rule?

Objectives

  1. Plot the four XOR points and attempt (then fail) a single straight separating line.
  2. Write the XOR rule: output is 1 only when the two inputs disagree.
  3. Justify model choice for at least three tasks: XOR-like logic, numeric yield, and text question-answering.
  4. State one reason not to use an LLM for a job a rule or a linear model already does well.

Key vocabulary

XOR (exclusive or)
A tiny logic job: the answer is yes only when the two inputs are different. (off,off) no, (off,on) yes, (on,off) yes, (on,on) no.
Linear classifier
A model that separates two classes with one straight line (or a flat plane in more dimensions). If you cannot draw that line, this model cannot do the job.
Rule-based logic
A program of IF/THEN rules a person writes. XOR is one line: IF a disagrees with b THEN on ELSE off.
LLM
A large language model: a data-hungry text model good at messy language, not the default for a two-switch logic problem.
Justification
A reason tied to the task's shape (linear vs. not, numeric vs. language, tiny vs. ambiguous), not to what is trendy.

Teacher background

Teach XOR on paper, not as mysticism. Draw a square: (0,0) and (1,1) are class 0; (0,1) and (1,0) are class 1. Any one straight line leaves a point on the wrong side. That is all 'linear classifier cannot solve XOR' means. A rule solves it perfectly. Contrast with potato yield from rainfall and temperature (a linear or simple regression may be enough) and with 'Will this variety make sense on my field given these notes?' which is ambiguous text and a fair LLM or similar job. Students justify selection; they do not implement a neural net. AIM.4–AIM.6 revisit families and limits; this lesson is the choice argument using the standards example. Spreadsheet scatter of four points is enough. Offline: pencil graph.

Materials

  • Printed XOR graph (axes 0–1, four points unlabeled at first).
  • String or a ruler to try one separating line.
  • Task cards: XOR irrigation interlock (pump ON only if exactly one of two sensors says dry — or a two-switch light), potato yield from rain+GDD, satellite smoke image, messy grower Q&A text, red-flag rule from wind and RH.
  • Model-family cards: rule-based, linear classifier / logistic / linear regression, decision tree, neural net, LLM.
  • Justification template: task shape → model → because → failure mode if we pick wrong.

Before class

  • Practice the four-point demo so the failed line is visible from the back row.
  • Write one Idaho XOR analog: a canal gate opens only when upstream is high XOR downstream is high (exactly one) — or keep the two-switch light if that is clearer. Do not force a bad analog.
  • Print AIM.4/AIM.5/AIM.6 cross-links for yourself so you do not steal their family-deep dives; today is selection plus XOR.

Instructional sequence

Warm-up — Two switches, one light

5 min
  1. Describe a light that is ON only when the two classroom lights disagree (exactly one on). Students fill a four-row truth table.
  2. Ask: can you state that in one IF? Collect a rule. Ask: could a single straight cutoff on 'number of switches on' work? (No: 0 and 2 are both OFF, 1 is ON — not a linear cutoff on a 2D diagonal either.)
  3. Name XOR.

Direct instruction — One line vs. a rule vs. a language model

12 min
  1. Plot the four XOR points. Invite a student to separate yes from no with one ruler line. Let it fail. Say: a linear classifier draws one line; XOR needs a bent or two-line boundary.
  2. Write the rule: IF a != b THEN 1 ELSE 0. Circle: best solved by rule-based logic.
  3. Contrast yield ~ rain + growing-degree days: a line (regression) is a reasonable first pick.
  4. Contrast messy question-answering ('What should I plant after this frost, given these notes?'): rules explode; an LLM trained on lots of text is the standards pick — still with a human check.
  5. Warning: do not use an LLM to XOR two bits. Fit the tool to the job.

Guided practice — Match three tasks as a class

10 min
  1. Task 1: red-flag warning if wind > 15 mph AND RH < 15%. Class justifies rules (and a weather forecast as input), not an LLM.
  2. Task 2: predict county potato yield from rain and GDD. Justify a linear/regression model; say what would make you upgrade.
  3. Task 3: answer free-text grower questions. Justify a data-heavy language model; name the hallucination risk.

Independent practice — Justification cards

8 min
  1. Pairs draw two remaining task cards and complete the template for each.
  2. They must include one rejected model and why (e.g., linear classifier rejected for XOR; LLM rejected for the AND red-flag rule).
  3. Offline: same cards, no software.

Real-world examples

  • XOR-like interlock: a pump should run only when float A and float B disagree (one high, one low) — a two-line rule, not a neural net on a PLC.
  • Linear: Magic Valley yield vs. April rain; a line is inspectable by a grower.
  • Neural net: smoke-plume pixels on a GOES snapshot — rules on a few thresholds miss the texture.
  • LLM: answering mixed English/Spanish extension questions from years of public FAQs — ambiguous language, needs data and a human agronomist in the loop.

Hands-on activity

Hands-on — Ruler test and a pitch

10 min
  1. Every student tries the ruler on the XOR plot and writes 'linear classifier fails here because…' in one sentence.
  2. They pitch one Idaho task and a justified model in 20 seconds to a neighbor.
  3. Collect one wrong-pick horror: LLM for XOR; linear model for satellite fire.

Discussion questions

  1. If a vendor says their linear model 'does XOR with enough data,' what would you draw on the whiteboard?
  2. Why might a grower prefer a worse-scoring linear yield model they can inspect over a black-box LLM?
  3. Where do combinations belong (rules to refuse unsafe actions, ML to rank options)?
  4. Is 'more complex' always 'more correct' for question answering that is actually a lookup of a river gauge?

Differentiation

Support

  • XOR plot pre-drawn with points; student only tries the line and copies the IF rule.
  • Two-choice justifications (rule vs. linear) before adding LLM.

Challenge

  • Explain in writing why stacking two linear classifiers (or a hidden layer) can solve XOR, and why we still might ship the IF rule on a pump.
  • Justify a hybrid: rules for safety interlocks plus an LLM for the help desk that explains them.

Multilingual learners

  • XOR truth table with ON/OFF and SI/NO; the inequality a != b is the same.
  • Sentence stems: 'I pick ___ because the task is ___. I reject ___ because ___.'

IEP / 504

  • Physical ruler and large graph; oral justification accepted.
  • Skip the optional two-layer hint; the standard is selection, not architecture.

Assessment

Formative

  • Truth table in the warm-up and the failed ruler line.
  • Class justifications for the three guided tasks.

Summative

  • Two completed templates plus the sentence 'linear classifier fails XOR because one straight line cannot separate the diagonal points.'
  • Credit the reasoning, not jargon. 'Use AI' with no family named does not meet the standard.

Success criteria

  • Student can show XOR on paper and state the rule.
  • Student justifies at least one rule pick and one data-heavy pick.
  • Student rejects at least one mismatched model with a task-shaped reason.

Responsible use

Choosing an LLM for a safety interlock is irresponsible even if it 'usually' gets XOR right. Fit, then add a human for high-stakes text.

Ethics

Complex models can hide who they fail. A justified pick includes who is harmed if the model is the wrong shape (a linear hiring screen, an LLM medical answer).

Privacy

No student Q&A logs into a public LLM for this lesson. Text-QA is discussed, not live-prompted with personal farm or family facts.

Reflection

  1. Where did you almost pick the fanciest model, and what pulled you back?
  2. How would you teach XOR to a ninth-grader in 30 seconds?
  3. Which Idaho job should never be an LLM, and why?

Homework

On the printed four-point graph, draw a failed linear attempt and write the XOR rule. Then justify a model for one of: (a) frost yes/no from tonight's temp, (b) identifying a leaf disease from a photo, (c) answering a messy text question about planting dates. One paragraph each for pick and reject.

Closing

XOR is a two-switch riddle a ruler cannot solve and a rule can. Messy language is the opposite riddle. Pick the model that fits the shape of the job. Tomorrow we critique the giant photo pile many models actually ate.

Extensions

  • 90-minute block: add decision-tree 20-questions (crop diagnosis) as a fourth family; still no training required — paper trees.
  • Python extension: try sklearn logistic regression on the four XOR points and watch it fail; fit a tiny two-layer net or just print the rule. Notebook is extra, not the gate.
  • Connect to AIM.4 (procedural vs. rule vs. data vs. combo) without duplicating that four-way sort — here the headline is XOR vs. LLM.
  • Printed tracing of four points for a sub plan.

Cross-curricular links

Mathematics
Linear separability is a geometry idea; XOR is the classic not-linearly-separable set.
Computer science
Boolean logic (AND, OR, XOR, NOT) is still how hardware and safety interlocks work.
Agriculture engineering
Pumps and gates want rules; yield wants regression; advisory text wants language models with humans.

Back to contents

AI Technical Aptitude · Data and Analysis

9-12.AITA.DA.7

Critique the Corpus

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Evaluate training data by examining its source, quality, representativeness, potential biases, and privacy implications.

Example from the standards. Pick a dataset commonly used to train a model like ImageNet and critique it on the listed criteria.

Student-friendly learning targets

  • I can critique a well-known training corpus (ImageNet) on source, quality, representativeness, bias, and privacy.
  • I can apply the same five criteria to an Idaho public dataset (yield, gauges, or wildlife photos).
  • I can recommend a go / use-with-cautions / do-not-use verdict with evidence.

Essential questions

  1. Who took these photos or measurements, who is missing, and who never consented?
  2. If ImageNet trained a generation of vision models, what did those models inherit?
  3. When is an Idaho public dataset still a bad training set?

Objectives

  1. Close-read a teacher-provided ImageNet fact sheet (source, size, labeling method, known issues) — not a live download of the corpus.
  2. Score ImageNet on the five criteria with evidence, not vibes.
  3. Score one Idaho public set on the same rubric.
  4. Write a verdict a district tech director or extension agent could use.

Key vocabulary

Corpus
A collected body of training items (images, text, tables). ImageNet is a famous image corpus.
Source
Where the items came from and who funded, scraped, or labeled them. Source is the first critique, not the last.
Representativeness
Whether the corpus looks like the world the model will face (geographies, people, seasons, devices), not just the world that was easy to scrape.
Label quality
Whether the tags are accurate, consistent, and at the right grain (a 'apple' label on a phone logo is a quality miss).
Privacy implication
Whether people in the data could be identified, were asked, or can get out; also whether locations reveal homes or tribal resources.

Teacher background

Students critique ImageNet as the standards example, using a fact sheet you provide (origin at Stanford/Princeton, millions of labeled web images, WordNet synsets, known problems: western/English web scrape, offensive synsets later removed, people photographed without meaningful consent, label noise, underrepresentation of many geographies). Do not download ImageNet in class; it is huge and messy. Pair it with a local public analog: iNaturalist research-grade observations in Idaho (source and consent differ from a web scrape), USDA NASS tables (survey, not photos), or USGS gauges (instruments, not faces). The five criteria are the rubric: source, quality, representativeness, potential biases, privacy. DA.5 was 'fix the mix'; DA.7 is 'should this corpus train anything at all?' Spreadsheet scoring 1–4 per criterion is enough.

Materials

  • ImageNet one-pager: origin, how labels were made, approximate scale, 3 documented critiques (people without consent, geographic skew, label noise/offensive categories). Citations to public writeups, not leaked files.
  • Idaho analog one-pager: pick iNaturalist Idaho observations or USDA NASS potato by county or USGS Snake River daily.
  • Five-criteria rubric (source, quality, representativeness, potential biases, privacy) with 1–4 anchors.
  • Verdict sheet: go / use with cautions / do not use for X task.
  • Optional printed sample label list (public synset names), no student photos.

Before class

  • Confirm analog dataset is public and has no student or easily identified private farm photos. iNaturalist: research-grade, obscuring of threatened species already in the source.
  • Do not ask students to search for random ImageNet images of people.
  • Pre-score both sets on the teacher key so you can coach evidence ('your representativeness 4 needs a citation from the one-pager').

Instructional sequence

Warm-up — Would you train on this shoebox?

5 min
  1. Show a shoebox metaphor: 14 million photos grabbed from the web and tagged by workers. Fast first impressions: source? consent?
  2. Reveal the five criteria on the board. Today every claim needs a criterion name.

Direct instruction — Five questions every corpus must survive

10 min
  1. Source: who collected, scraped, paid, labeled? Quality: noise, duplicates, wrong tags. Representativeness: geography, time, devices, people. Bias: systematic skews (skin tone, language, crop variety, season). Privacy: faces, homes, GPS, kids, tribal and sensitive locations.
  2. Walk ImageNet through source and privacy first using the one-pager. Do not sensationalize; be specific.
  3. Note: a corpus can be famous and still fail a criterion. Fame is not a fifth star.

Guided practice — Score ImageNet as a class

12 min
  1. Read the one-pager silently for 3 minutes. Pairs draft a 1–4 score for source and for privacy with a quoted phrase as evidence.
  2. Share two scores. Disagreement is useful if evidence is cited.
  3. Complete quality, representativeness, and bias as a class so the method is visible.

Independent practice — Idaho analog on the same rubric

10 min
  1. Pairs score the analog dataset on all five criteria with evidence from its one-pager.
  2. They write a verdict for a stated task (e.g., 'train a statewide bird classifier' vs. 'publish a county yield nowcast').
  3. Offline: rubric on paper; no need to open the live dataset portal.

Real-world examples

  • ImageNet trained a decade of vision models; inherited web-scrape geography and consent failures show up in production cameras.
  • iNaturalist Idaho: better consent norms and research-grade filters, but road-accessible locations and charismatic species still skew representativeness.
  • USDA NASS: strong source documentation, but small counties may be suppressed for privacy — a quality/representativeness tension.
  • USGS gauges: excellent source and quality, weak representativeness if you train a 'all Idaho streams' ice model on the Snake alone.

Hands-on activity

Hands-on — Two-corpus briefing

8 min
  1. Each pair writes a 6-line briefing: ImageNet verdict for 'general object recognition in Idaho schools'; analog verdict for its stated task.
  2. They must name the weakest criterion for each.
  3. Two pairs swap and try to overturn one score with evidence from the one-pager only.

Discussion questions

  1. Should a school ever fine-tune a vision model on ImageNet-derived weights without reading this critique?
  2. NASS suppresses small-county data to protect farms. Is that a privacy win, a representativeness loss, or both?
  3. If a corpus is 'the best we have,' does that make it acceptable?
  4. What would you demand from a vendor who says 'we trained on a large public dataset' and will not name it?

Differentiation

Support

  • Rubric with sentence starters and highlighted evidence lines on the one-pager.
  • Score only three criteria (source, representativeness, privacy) if five is overload.

Challenge

  • Compare ImageNet to a second famous corpus fact sheet (e.g., a large language-text crawl described, not downloaded) on privacy.
  • Propose a replacement sampling plan for an Idaho crop-disease corpus that would pass all five at 3+.

Multilingual learners

  • Criteria names with plain glosses; students may write evidence quotes in English (from the sheet) and commentary in another language.
  • Discuss how English-only labels in a corpus are a representativeness issue.

IEP / 504

  • One-pager in large print; oral verdict with the five names on a checklist.
  • Partner reads; student owns two criteria.

Assessment

Formative

  • Paired ImageNet scores for source and privacy with a quoted phrase.
  • Teacher listens for criterion names, not just 'it's biased.'

Summative

  • Completed two-corpus rubric plus verdicts. Each score has evidence from the fact sheet.
  • A rant without the five criteria does not meet the standard.

Success criteria

  • Student addresses all five listed criteria for at least one corpus.
  • Student uses source evidence, not only reputation.
  • Student names a privacy implication that is not 'hackers' — consent, identification, or location.

Responsible use

Critique from fact sheets. Do not download ImageNet, do not scrape faces, do not open random synsets of people in class.

Ethics

Famous datasets normalized taking without asking. Students should leave able to say no to a corpus, not only how to fine-tune it.

Privacy

FERPA plus ordinary privacy: no student photos as 'our ImageNet.' For Idaho analogs, prefer gauges and county-level surveys over identifiable homesteads. If a photo set includes people, stop and switch packets.

Reflection

  1. Which of the five criteria was hardest to score, and what evidence did you wish you had?
  2. How would you explain ImageNet's privacy problem to a principal in two sentences?
  3. What corpus will you refuse to treat as 'neutral' after today?

Homework

Using only the take-home one-pagers, write a one-page critique of ImageNet on the five criteria and a half-page critique of the Idaho analog. End each with a verdict for a named task. No image downloads.

Closing

Source, quality, representativeness, bias, privacy — five doors a training set must pass. ImageNet is a caution, not a mascot. Public Idaho tables can fail too. That is the last Data and Analysis move: decide whether the corpus deserves a model at all.

Extensions

  • 90-minute block: a third corpus (energy load public tables) and a gallery of verdict posters; or a letter to a vendor asking the five questions.
  • Python extension: summarize column missingness and county counts on the NASS CSV as quality/representativeness evidence — still no student PII.
  • Card sort of headline claims ('1 million images!') onto the five criteria they actually address (often none).
  • Tie back to DA.5: augmentation cannot fix a corpus you ethically should not have.

Cross-curricular links

Civics / law
Consent, public-records, and suppression rules (NASS) are policy, not only data science.
Art / media
Web-scraped photos have photographers and subjects; a corpus is a pile of other people's work.
Biology
iNaturalist quality grades and threatened-species location hiding are field-biology ethics.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.1

Call a Model, Don't Train One

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Create an application using pre-existing supervised learning models to make predictions or classifications.

Student-friendly learning targets

  • I can wire a pre-existing supervised model into a tiny application flow: input, request, prediction, display.
  • I can explain the difference between calling a trained model and training one.
  • I can handle a blocked demo by using a paper API with printed predictions.

Essential questions

  1. If the model already exists, what is left for us to build?
  2. What does a supervised prediction look like as data (label + confidence) rather than as magic?
  3. Where should a human look before the app acts on a classification?

Objectives

  1. Sketch an app that sends an input (crop-leaf photo description, river-gauge row, or short text) to a prebuilt classifier and shows a label.
  2. Use a district-allowed demo (Teachable Machine or similar) OR a paper API of printed JSON-style predictions — never train as the gate.
  3. Parse label and confidence into a user-facing sentence.
  4. Refuse to send student faces, voices, or PII as inputs.

Key vocabulary

Pre-existing model
A model someone already trained. You send inputs and read outputs. You do not update its weights in this lesson.
Supervised learning
Training with labeled examples (this leaf is blight; this row is frost). The prebuilt model was supervised; we only call it.
API
A contract for how to ask a service for an answer: you send a structured request and get a structured prediction back.
Inference
The moment of using a trained model on a new input. Opposite of training in this class's vocabulary.
Confidence
A number the model reports with a label. It is not a promise; a 0.91 can still be wrong.

Teacher background

The standard is application using pre-existing supervised models, not a training lab. Teachable Machine or a hosted image/text classifier is fine IF the district allows it and students use teacher-provided public photos (russet leaves, smoke vs. steam, sports jersey colors). If accounts, webcams, or the site are blocked, run a paper API: printed request/response cards (JSON-like) that students wire into a flowchart or a no-code screen mock. Spreadsheet-first path: a lookup table that stands in for the model (input id → label, confidence). Python requests to a public demo is an extension. FERPA: no student selfies into a classifier. AIM.2 will add agents; today is one supervised call.

Materials

  • App-flow template: Input → Request → Model (black box) → Parse label/confidence → Display → Human check.
  • Paper API deck: 8 request cards (leaf_042.jpg, gauge_boise_glenwood, headline_redflag) and matching printed predictions.
  • Optional: district-approved Teachable Machine or a local prebuilt demo loaded by the teacher with public crop photos — never required.
  • Public photo printouts (U of I extension disease cards, NWS radar crop, smoke/steam stills) if using a live classifier.
  • Mock phone-screen paper for the display UI.

Before class

  • Test whether the live demo is reachable without student logins. If not, go paper-first and say so in the warm-up.
  • Print the API deck so every pair can finish offline.
  • Choose one app story: Magic Valley leaf sort, foothills smoke alert, or Boise River 'frost tonight' classifier on a tiny weather row.

Instructional sequence

Warm-up — Train vs. call

5 min
  1. Two boxes on the board: TRAIN (needs labels, time, data) and CALL (needs an input and a phone/API). Students sort four verbs: fit, predict, download weights, show a label.
  2. Circle CALL. That is today's build.

Direct instruction — The thinnest possible app

10 min
  1. Walk the flow template. The model is a sealed box that maps input → {label, confidence}.
  2. Show a printed response: {"label": "early_blight", "confidence": 0.81}. Demo turning it into 'This leaf is labeled early blight (81%). Check with extension if you will spray.'
  3. State constraints: pre-existing, supervised, no training, no student PII, human reads the screen before action.
  4. If live demo is on, show one inference on a public photo. If not, hold up the paper API card and treat it as the same contract.

Guided practice — Wire three calls together

12 min
  1. Class maps three paper requests through the flow and writes the display sentence for each.
  2. Handle a low-confidence response (0.41) by branching: 'show unsure, do not spray / do not page crews.'
  3. Add a failure card: timeout. The app must say 'model unavailable,' not invent a label.

Independent practice — Build your flow

10 min
  1. Pairs pick the leaf, smoke, or frost story. They complete the flow template, three example calls (from the deck or the allowed demo), and the display copy.
  2. They mark the human-check step in red.
  3. Spreadsheet path: VLOOKUP from input_id to label/confidence as a stand-in API.

Real-world examples

  • A Magic Valley packing shed camera already has a vendor defect model; the app is the belt UI plus a reject bin, not a new training run.
  • Idaho Transportation Department can call a prebuilt road-camera ice classifier; dispatchers still decide plow routing.
  • A Boise State sports-stats club can call a prebuilt shot-chart classifier on public game film, not on hallway video of students.
  • Extension offices calling a hosted leaf model on grower-submitted (consented) photos — still a call, still a human agronomist.

Hands-on activity

Hands-on — Run the paper (or live) API

8 min
  1. Each pair 'sends' two new cards through their app and writes the on-screen text.
  2. Peer tries to break it with the timeout card and a PII card (student selfie). The app must refuse the selfie.
  3. Photograph or staple the flow; that is the application artifact.

Discussion questions

  1. If confidence is 0.95 and the leaf is healthy, who is wrong — the photo, the model, or the display copy?
  2. Why might a district forbid Teachable Machine webcams even though this standard likes demos?
  3. What is the smallest UI that still counts as an application?
  4. Where does this app log inputs, and why might logging be a privacy bug?

Differentiation

Support

  • Flow boxes already drawn; students fill display sentences only and run two paper cards.
  • Spreadsheet VLOOKUP version with input_id pre-listed.

Challenge

  • Add a second prebuilt model (crop vs. not-crop) as a gate before the disease model.
  • Sketch how a timeout retries once, then fails safe.

Multilingual learners

  • Display copy required in English and the student's strongest language; labels stay as the API returns them, with a glossary.
  • API / inference / confidence on a term strip.

IEP / 504

  • Paper API only; no live webcam. Oral walkthrough of the flow is accepted.
  • Fewer cards; the success is the wired flow, not speed.

Assessment

Formative

  • Train vs. call sort.
  • Display sentence for the 0.81 blight response.

Summative

  • Completed flow with three calls, a low-confidence branch, a PII refusal, and no training step.
  • Live demo is extra evidence, not required for proficiency.

Success criteria

  • Student's artifact is an application flow that calls a pre-existing model.
  • Student parses label and confidence into human language.
  • Student refuses student-PII inputs.

Responsible use

District-approved tools only. Teacher-loaded public images. No student accounts required. Paper API is a full-credit path.

Ethics

A called model still carries the biases of whoever trained it. Displaying a label as fact without a human check can harm a field or a person.

Privacy

FERPA: never classify student faces, ID photos, or classroom recordings. Log files of inputs are PII if they contain photos of people — do not keep them.

Reflection

  1. What did you build that is not the model itself?
  2. When is a paper API more honest than a flashy demo?
  3. What would you add before this app could page a person?

Homework

On paper, draw the flow for a frost yes/no app that calls a prebuilt model on public NWS values. Write two fake API responses (high confidence frost; low confidence) and the screen text. Do not upload photos from home.

Closing

You built the wiring, not the brain. Call, parse, display, check. If the demo site is down, the paper API still teaches the standard. Next period we drop in an agent that uses tools — with a human approval step.

Extensions

  • 90-minute block: no-code screen (district tool) or a paper prototype test with another pair acting as the API.
  • Python extension: a 15-line script that reads a printed JSON file and prints the display sentence — still not training.
  • If Teachable Machine is allowed, the teacher trains once before class; students only infer.
  • Trace printed JSON with highlighters (label vs. confidence vs. extra junk fields).

Cross-curricular links

Design / CTE
UI copy for uncertain predictions is a design problem, not only a CS one.
Agriculture
Leaf classification apps exist; the agronomist remains the decision-maker.
Business
Buying a vendor model and wrapping it in a workflow is a realistic Idaho software job.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.2

Drop In an Agent

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Integrate a prebuilt AI agent into an application.

Student-friendly learning targets

  • I can specify a prebuilt agent with a job, tools, and a human approval step, then show where it sits in an app.
  • I can integrate on a flowchart (and optional no-code) rather than training an agent from scratch.
  • I can refuse tool actions that send email, change records, or share PII without a human.

Essential questions

  1. What makes something an agent rather than a single model call?
  2. Which tools should an agent be allowed to use without asking?
  3. Where does integration end and 'the agent is the whole product' begin?

Objectives

  1. Spec a help-desk or lab-assistant agent: goal, allowed tools, forbidden tools, escalation.
  2. Draw the host application flowchart with the agent as one box, not the whole diagram.
  3. Require a human approval step before any irreversible action.
  4. Optional: drop the spec into a district-approved no-code agent builder; paper is full credit.

Key vocabulary

Agent
Software that can plan a short sequence of actions toward a goal, often by calling tools (search, lookup, ticket). Prebuilt means we did not train it today.
Tool
A function the agent may call: look up a river gauge, search a FAQ, file a ticket. Tools have side effects; permissions matter.
Integration
Connecting the agent to a host app with inputs, outputs, logging, and approval hooks — not building the agent from zero.
Human approval step
A required pause where a person must click yes before email, record changes, purchases, or alerts go out.
Escalation
Handing the session to a human when confidence is low, the user is distressed, or the tool is out of scope.

Teacher background

AIM.1 was one supervised prediction. AIM.2 is a prebuilt agent that can use tools. Students specify a help-desk (Idaho Power-style outage FAQ) or a CS lab assistant (how to use the laser cutter, where the jumper wires are) and integrate it into an application flowchart. District no-code is optional. Human approval is required by this lesson even if a vendor would skip it. Tools should be boring and public: FAQ search, public USGS lookup, 'create draft ticket.' Forbidden: send email, DM a student, charge a card, unlock a door, scrape a gradebook. Offline: card-sort tools onto allowed / approval / forbidden, then tape them onto the flowchart.

Materials

  • Agent spec sheet: name, user, goal, 4 tools, 3 forbidden, approval gates, escalation.
  • Flowchart poster of a host app (school work-order site or county extension chat widget).
  • Tool cards: FAQ search, USGS cfs lookup, draft ticket, send email, open locker, read SIS grades, web search (filtered), web search (unfiltered).
  • Optional no-code agent environment if district-approved and account-free for students.
  • Printed AIM.7 preview: safeguards will go deeper later; today the gate is the approval step.

Before class

  • Choose the default story: CS lab assistant for your room, or a public-lands 'campfire rules' help desk. Local beats generic.
  • If no-code is flaky, do not mention it until extension time.
  • Pre-sort one worked example so the approval diamond is obvious on the poster.

Instructional sequence

Warm-up — Model call vs. agent

5 min
  1. AIM.1 recap: one input, one label. Ask what extra happens if the software can search a FAQ, then file a ticket, then stop.
  2. Name that extra: tools + a goal = agent-shaped. We will integrate a prebuilt one, not train it.

Direct instruction — Spec, slot, approve

10 min
  1. Three moves: spec the agent (job and tools), slot it into a host app, require approval on side-effect tools.
  2. Demo a bad integration: the agent is the entire school website and can email parents. Demo a good one: chat widget with FAQ + draft ticket, counselor clicks send.
  3. Walk tool cards onto a permission board: auto / ask a human / never.
  4. Say the sentence students must write: 'No send without a human.'

Guided practice — Lab-assistant spec as a class

12 min
  1. Fill the spec sheet together for a lab assistant: goal = help students find procedures and report broken equipment.
  2. Sort eight tool cards. Debate web search filtered vs. unfiltered (AIM.7's child-appropriate example, previewed).
  3. Draw the host app: student opens a help tab → agent → draft → teacher approval → ticket system.

Independent practice — Your help desk

10 min
  1. Pairs spec a second agent: county extension crop FAQ or outage help desk. Complete tools, forbidden list, and two approval diamonds.
  2. They draw the host application around the agent (map, phone tree, kiosk).
  3. Optional no-code: paste the spec into the allowed builder; still print the flowchart.

Real-world examples

  • A hospital scheduling agent that drafts appointments but cannot confirm without a clerk — same pattern as our ticket gate.
  • Idaho Power outage chat that can look up a public map and open a ticket, with a dispatcher approving crew messages.
  • A school library agent that searches the catalog (tool) but cannot charge a late fee.
  • Extension 'ask an expert' widgets that retrieve public fact sheets and queue a human agronomist.

Hands-on activity

Hands-on — Tape the agent into the app

8 min
  1. Pairs tape tool cards onto the host flowchart with auto/ask/never stickers.
  2. A neighbor red-teams: find a path that emails without approval. Fix it.
  3. Initial the 'No send without a human' line.

Discussion questions

  1. If the agent can search the web, is that a tool we auto-allow in a 9th-grade lab?
  2. Does integration mean the agent should remember students across weeks? (Privacy no.)
  3. What is the smallest host app that still counts (a paper kiosk form + agent box)?
  4. When should the agent shut up and escalate?

Differentiation

Support

  • Pre-written goal sentence; students only sort tools and place two diamonds.
  • One host flowchart template with blank boxes.

Challenge

  • Add a tool that looks up public USGS cfs and specify the cache/timeout behavior.
  • Write a one-paragraph 'agent contract' a principal could sign.

Multilingual learners

  • Tool names with glosses; spec goal may be bilingual; forbidden list in both languages.
  • Role-play the approval step in the student's preferred language.

IEP / 504

  • Card sort is the assessment path; drawing can be a partner's job.
  • No live chatbots if they are overstimulating; paper agent only.

Assessment

Formative

  • Tool sort on auto/ask/never.
  • Class flowchart with a visible approval diamond.

Summative

  • Spec sheet + host flowchart with the agent integrated, two approval gates, and a forbidden-tool list.
  • A chatbot doodle with no tools and no host app does not meet 'integrate into an application.'

Success criteria

  • Agent is prebuilt/specified, not trained in class.
  • At least one tool and one forbidden action are named.
  • A human approval step sits in front of side effects.

Responsible use

Prebuilt, district-approved, or paper. No student-built agents with unsupervised web tools. No connecting to school email.

Ethics

An agent that 'just helps' can still harass, over-promise, or skip a human. Integration includes saying no to tools.

Privacy

FERPA: the agent may not read SIS, IEPs, or student mail. Sessions should not store names. Public FAQs only.

Reflection

  1. Where in your flowchart is the agent, and where is the application?
  2. Which tool was the hardest to classify as auto/ask/never?
  3. What would break if we removed the approval diamond 'just for speed'?

Homework

Finish the spec sheet for a campfire-rules help desk on public-land FAQs. List four tools, three never-tools, and the exact sentence the human sees on the approval screen. Paper only.

Closing

You did not train an agent. You specified one, gave it tools, and bolted it into an app behind a human gate. That is integration. Next we look at how a model writes a function from data at all.

Extensions

  • 90-minute block: tabletop-test the flowchart with another pair playing user, agent, and approver; log failures.
  • No-code drop-in if district-approved; still keep the paper contract.
  • Python extension: a stub function approve(action) that returns False unless a teacher flag file exists — conceptual, not production.
  • Preview AIM.7 safeguards without stealing that lesson's planning depth.

Cross-curricular links

Workplace skills
Help-desk runbooks already have escalation; agents must inherit them.
Civics
A county chat agent that can file reports is a public service and needs public oversight.
Theater / ELA
Tabletop role-play of user/agent/approver makes the integration visible.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.3

Data Writes the Function

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Discuss how a machine learning model generates classifications or predictions.

Clarification. Machine learning is different from classical programming in that data is used to 'write' functions that take inputs and return outputs.

Student-friendly learning targets

  • I can contrast a human-written IF rule with a function whose boundary came from labeled examples.
  • I can walk a tiny Idaho table and show how a threshold 'appears' from the data.
  • I can say that the model still returns an output for an input — the authorship of the function changed.

Essential questions

  1. Who writes the function in classical programming, and who writes it in machine learning?
  2. If the data is wrong, whose 'code' is wrong?
  3. What is a classification vs. a numeric prediction in this story?

Objectives

  1. Write a classical frost rule (IF temp ≤ 32 F THEN frost) and then derive a threshold from a labeled table that may not sit at 32.
  2. Describe classification (label) vs. prediction (number) using the same input columns.
  3. Discuss, with a diagram, that training searches for a function; inference uses it.
  4. Name one way this differs from AIM.1 (calling) and DA.3 (splitting): here we talk mechanism, not app wiring or CSV stations.

Key vocabulary

Classical programming
A person writes the rules: inputs go through code they authored, outputs come out. The data does not write the IF.
Function (in ML)
A mapping from inputs to outputs. In ML the mapping is chosen to fit examples, not typed by a programmer line by line.
Classification
Output is a category: frost / no frost, blight / healthy, smoke / not smoke.
Prediction (numeric)
Output is a number: expected yield, MW load, cfs tomorrow. Same idea of a learned function, different output type.
Labeled example
An input paired with the known output, used to shape the function (last night's temp and whether the orchard actually frosted).

Teacher background

The clarification is the whole lesson: data writes the function. Keep it tactile. Classical: IF temp <= 32 THEN frost_warning. ML: a table of Treasure Valley nights (temp, humidity, frost_yes). Count, sort, and watch a threshold emerge that might be 31 or 34 because of wind or humidity. Students should feel that the computer is still producing a function f(x)→y; the author is the dataset plus an algorithm, not a programmer's IF. Do not teach gradient descent. A paper scatter and a moveable horizontal bar are enough. Spreadsheet SORT and a hand-drawn line beat a neural-net animation. Connect to AIM.1 (we call f) and AIM.8 (how we prepare the data that writes f) without repeating those labs.

Materials

  • Printed 16-row frost table: night_id, temp_f, humidity, frost (Y/N). Public-climate-style, no orchard owner names.
  • Moveable yarn or a ruler for a threshold on a scatter of temp vs. frost.
  • Two function cards: f_classical (IF …) and f_data (threshold learned = __).
  • Board diagram: data + algorithm → function; new input → function → output.
  • Optional spreadsheet of the same 16 rows.

Before class

  • Cook the 16 rows so a 32 F rule gets two mistakes (a 33 F frost with radiative cooling; a 30 F save with wind). The learned threshold discussion is then real.
  • Print classical vs. ML side-by-side without disparaging rules — AIM.4 will pick among them.

Instructional sequence

Warm-up — Who wrote this IF?

5 min
  1. Show IF temp <= 32 THEN 'frost'. Ask who authored it (NWS, a teacher, a grower).
  2. Ask: could last winter's nights author a different cutoff? That is the ML claim for today.

Direct instruction — The function still exists

12 min
  1. Draw f(x)→y on the board twice. Left: human writes f. Right: labeled pairs shape f.
  2. Classification: y is a label. Numeric prediction: y is a number (yield). Same story.
  3. Walk two labeled points. The algorithm's job is to pick a boundary that gets most points right — we will do that by hand.
  4. Quote the clarification: data is used to 'write' functions that take inputs and return outputs.

Guided practice — 16 nights, one bar

10 min
  1. Plot temp vs. frost (Y above a line, N below, or two colors). Slide a vertical threshold.
  2. Count errors at 32 F, then at 31 and 34. Pick a threshold that misses fewer.
  3. Write f_data: IF temp <= T* THEN frost. Circle that the table wrote T*, not the NWS definition.
  4. Ask what extra input (humidity) might explain the leftover errors — preview features, do not train a two-input model.

Independent practice — Say it both ways

10 min
  1. Students write a 5-sentence discussion: classical frost rule; how the table wrote a function; one leftover error; classification vs. a yield number; why bad labels write a bad function.
  2. Offline: the printed scatter is the whole lab.

Real-world examples

  • NWS freeze headlines are classical thresholds; an orchard model that fits Payette nights may 'write' a different cutoff.
  • Idaho Power load: a formula based on temperature is classical; a model fit on five winters of MW is data-written.
  • Sports: a coach's rule 'if opponent 3-point rate > 40% then zone' vs. a function fit on seasons of public play-by-play.
  • River flood stage: the official stage is a rule; a damage model fit on past crests is a learned function.

Hands-on activity

Hands-on — Function cards on the table

8 min
  1. Pairs fill f_classical and f_data cards and tape them under the scatter.
  2. They run two new nights (inputs only) through both functions and compare outputs.
  3. Stand and say one sentence: 'The data wrote T* = … because …'

Discussion questions

  1. If we add 200 wrongly labeled nights, who vandalized the function?
  2. Is a learned threshold 'truer' than 32 F, or just truer to this table?
  3. Where does a human still write something in ML (choice of inputs, choice of algorithm, choice to stop)?
  4. How is this different from an LLM completing a sentence? (Still a function, much larger, still data-authored.)

Differentiation

Support

  • Pre-plotted scatter; students only slide the bar and copy T*.
  • Sentence stems for the five-sentence discussion.

Challenge

  • Add humidity as a second axis and try a hand-drawn linear separator; connect to AIM.6 limits.
  • Write why 100% on these 16 rows is not the same as a good function (overfit preview).

Multilingual learners

  • function / classification / prediction with everyday glosses (regla vs. ejemplo).
  • Oral discussion accepted; the scatter is language-light.

IEP / 504

  • Large scatter, thick yarn, fewer rows (10).
  • Skip the written paragraph; a labeled diagram can be the discussion artifact.

Assessment

Formative

  • Error counts at 32 vs. T*.
  • Correct use of 'function' as input→output, not as 'a party.'

Summative

  • Five-sentence discussion plus completed f_classical / f_data cards.
  • Must include the idea that labeled data authored the cutoff.

Success criteria

  • Student contrasts human-written vs. data-written functions.
  • Student can run a new input through the learned threshold.
  • Student names classification vs. numeric prediction.

Responsible use

Use the teacher table. Do not scrape student weather apps or home thermostats.

Ethics

If data writes the function, biased or sloppy data writes biased or sloppy law-like behavior. Authorship does not remove human responsibility.

Privacy

No farm owner, student address, or household thermostat IDs. Public-style climate rows only.

Reflection

  1. In one sentence, who wrote f_data?
  2. When would you still prefer the classical 32 F rule?
  3. How will you explain this to someone who thinks ML is 'the computer thinking'?

Homework

Take the printed 8-row mini-table. Draw a scatter, choose a threshold, write f_data, and compare it to IF temp <= 32. Two sentences on which errors each function makes. No tools required.

Closing

Same f(x)→y. Different author. Classical code is a person; machine learning lets labeled Idaho nights write the cutoff. Tomorrow we decide when we still want the person to write the rules.

Extensions

  • 90-minute block: a second table (numeric yield) where the 'function' is a hand-fit line, not a threshold; still no software trainer.
  • Python extension: sklearn logistic on the 16 rows and print the learned coefficient — optional illustration of 'data wrote f.'
  • Card-sort statements into classical vs. ML authorship.
  • Printed tracing of the scatter for subs.

Cross-curricular links

Algebra
f(x) is the same object; ML estimates f from points instead of from a worded rule.
Physics / earth science
32 F is a phase-change fact; orchard frost is also wind and humidity — data can capture a local mix.
Philosophy / ELA
Authorship of a rule is a useful metaphor: who is responsible when the function fails?

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.4

Rules, Data, or Both

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Justify whether a problem is best solved using procedural instructions, rule-based logic, data-driven methods, or a combination of these approaches.

Example from the standards. Logistic regression for a binary task on an edge device, a decision tree for 20 questions, and a neural network for image classification.

Student-friendly learning targets

  • I can tell procedural instructions, rule-based logic, and data-driven methods apart with Idaho examples.
  • I can justify a pick, including a combination, not only a single family.
  • I can map the standards example (logistic on a small device, tree for 20 questions, neural net for images) into plain jobs.

Essential questions

  1. When is a formula better than a learned model?
  2. When do IF/THEN rules beat both formulas and neural nets?
  3. Why do real systems so often combine the three?

Objectives

  1. Define the four options: procedural, rule-based, data-driven, combination.
  2. Justify logistic regression, a decision tree, and a neural net for the three jobs in the standards example.
  3. Sort eight Idaho problems into the four bins with reasons.
  4. Write one combination design (rules for safety, data for ranking).

Key vocabulary

Procedural instructions
A fixed recipe of steps or a formula: growing-degree days, a checksum, 'add these columns then divide.' No learned boundary.
Rule-based logic
IF/THEN (and AND/OR/NOT) written by people: red-flag if wind and dry; XOR interlock. Related to DA.6's XOR rule.
Data-driven method
A function shaped by examples: logistic regression, trees, neural nets. The data writes a lot of the behavior (AIM.3).
Logistic regression
A linear classifier that outputs a probability for a yes/no task. Cheap enough for a small device; cannot draw XOR's bent boundary.
Combination
A system that uses more than one approach: a formula for GDD, a model for yield risk, a rule that refuses to spray in wind.

Teacher background

AIM.4 is the four-way justification; DA.6 was 'pick a model' with XOR vs. LLM as the headline. Do not rerun the XOR lab — mention it as the rule-based win. Teach the standards example plainly: (1) logistic regression for a binary task on an edge device — yes/no, probability, small compute, linear; (2) a decision tree for 20 questions — readable branches a person can follow; (3) a neural network for image classification — pixels are too many for a hand rule. Procedural is the missing first leg: GDD = f(temps), no learning. Combinations are how Idaho Power, irrigation districts, and dispatch actually ship. Spreadsheet GDD calculation is the procedural demo. Offline card sort is the core.

Materials

  • Four bin posters: Procedural / Rules / Data-driven / Combination.
  • Eight problem cards: GDD formula, XOR pump interlock, red-flag AND, frost logistic on a weather station, 20-questions crop tree, smoke-image net, LLM FAQ, 'rules refuse spray + model ranks hour.'
  • Standards-example triad cards: logistic+edge, tree+20Q, net+images.
  • Tiny GDD worksheet (procedural): five days of max/min temp, base 50 F.

Before class

  • Compute the GDD key. Keep DA.6 XOR graph in reserve as a 60-second reminder, not a re-teach.
  • Make combination the hardest bin so students do not dump everything there without a reason.

Instructional sequence

Warm-up — Five days of heat, no model

5 min
  1. Compute one GDD by the formula as a class. Ask: did any labeled yield data write this? No — procedural.
  2. Name the other three bins on the wall.

Direct instruction — Four approaches, three famous picks

10 min
  1. Define procedural (steps/formula), rule-based (IF/THEN), data-driven (examples write f), combination (name both parts).
  2. Unpack the standards example: logistic on a tiny frost logger (binary, edge, cheap); decision tree as 20 questions (interpretable); neural net for a smoke photo (pixels).
  3. Show a combination: procedural GDD feature → logistic risk → rule 'never auto-spray.'

Guided practice — Place three cards together

12 min
  1. Place GDD, red-flag AND, and smoke-image as a class with a because-sentence each.
  2. Place the combination spray card. Insist both parts are named.
  3. If a pair says 'AI' as a bin, send it back — family or approach required.

Independent practice — Sort the rest and justify

10 min
  1. Pairs place remaining cards, including logistic-on-edge and 20-questions tree.
  2. They write a because-sentence for each and one rejected approach.
  3. Offline: the posters are paper on desks.

Real-world examples

  • Procedural: Bureau of Reclamation reservoir accounting is arithmetic and policy, not a neural net.
  • Rules: NWS red-flag criteria; canal XOR-style interlocks from DA.6.
  • Data-driven logistic: a battery-powered orchard frost alarm that only stores a few weights.
  • Combination: wildfire dispatch uses a smoke model (net) plus rules that a human must confirm before paging crews (AIM.9 will score those pages).

Hands-on activity

Hands-on — Gallery of because-sentences

8 min
  1. Each pair posts one card they struggled with.
  2. Class challenge: steal a card into combination only if they can name both pieces.
  3. Photograph the bins.

Discussion questions

  1. Why put logistic regression on an edge device instead of a neural net that might score higher on Wi-Fi?
  2. When does a 20-questions tree become unmaintainable compared with a learned model?
  3. Is an LLM procedural, rule-based, data-driven, or a combo with a hidden prompt rule?
  4. What approach should open a spillway?

Differentiation

Support

  • Two-bin start (rules vs. data) then add procedural and combination.
  • Because-stems already printed.

Challenge

  • Design a three-layer combination for irrigation: procedural soil-water formula, data-driven ET model, rules for fish-flow legal minimums.
  • Argue against the standards example: when would you not use a net for images?

Multilingual learners

  • Bin names with glosses; cards use icons (formula, IF, scatter, plus-sign).
  • Oral because-sentences.

IEP / 504

  • Fewer cards (5); movement to posters is the memory aid.
  • No timed sorting.

Assessment

Formative

  • GDD warm-up as a procedural identifier.
  • Because-sentences during guided placement.

Summative

  • Completed sort with a because and a reject for four cards, including one combination.
  • Must correctly place the standards triad or explain a reasoned disagreement.

Success criteria

  • Student defines all four approaches.
  • Student justifies logistic / tree / net in ordinary language.
  • Student does not treat 'combination' as a dump bin.

Responsible use

Justify before you call an API. A neural net on a spillway without a rule layer is a misuse even if it is 'AI.'

Ethics

Combinations can hide who is accountable. Students must name which layer may not be overridden.

Privacy

Problem cards stay public (weather, crops, images of landscapes). No student-location tracking as an 'edge device' demo.

Reflection

  1. Which approach do you overuse, and which do you forget?
  2. Why might a grower demand the tree over the net?
  3. What combination would you trust at 2 a.m. during a frost?

Homework

Pick one home-safe public problem (sports winner from box scores, frost, river flood). Write four short pitches: procedural, rules, data-driven, combination. Star the one you justify and say why the others lose. Paper.

Closing

Formulas, IFs, learned functions, or a stack. The standards example is three data-driven flavors; Idaho work often needs the fourth bin — both. Next we sit with those three families and their jobs.

Extensions

  • 90-minute block: write a one-page design for a county frost system using all four approaches at least once.
  • Python extension: time a logistic vs. a tiny net on a 100-row table to make the 'edge device' point — optional.
  • Connect to DA.6 without redoing XOR plotting; one reminder graph is enough.
  • Printed card sort for a sub plan.

Cross-curricular links

Mathematics
Procedural GDD is a piecewise formula; logistic is a linear function plus a curve to a probability.
Engineering design
Constraints (power, interpretability, law) drive approach choice as much as accuracy.
Government
Legal minimum streamflow is a rule no model is allowed to vote off.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.5

Three Families, Three Jobs

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Understand the differences between common machine learning models.

Example from the standards. Common models include logistic regression, decision trees, and neural networks.

Student-friendly learning targets

  • I can describe logistic regression, decision trees, and neural networks in high-school language.
  • I can match each family to a job it is good at and a job it is a poor fit for.
  • I can compare the three on interpretability, data hunger, and compute without training any of them.

Essential questions

  1. If they all 'learn from data,' why not use one family for everything?
  2. What does a tree know how to show that a neural net usually does not?
  3. Why is logistic regression still in the toolkit?

Objectives

  1. Build a three-column comparison: how it decides, what it outputs, what it needs, what it cannot do (preview of AIM.6).
  2. Walk a 20-questions tree on paper, a logistic probability on a frost yes/no, and a neural net as stacked simple units for pixels.
  3. Give each family an Idaho job.
  4. Avoid treating 'neural net' as a synonym for all of AI.

Key vocabulary

Logistic regression
Draws a linear boundary and turns the distance to that line into a probability of yes vs. no. Interpretable coefficients; fails XOR (DA.6 / AIM.6).
Decision tree
A flowchart of questions (Is RH < 15%? Is wind > 20 mph?). Easy to read; can overfit; can show which features get used.
Neural network
Layers of weighted sums plus simple nonlinear squashes. Flexible enough for images and language; data- and compute-hungry; hard to explain.
Interpretability
Whether a person can see why the model said yes. Trees high, logistic medium, deep nets low.
Overfit
Memorizing the training rows so the model looks brilliant at home and fails on new nights, counties, or photos.

Teacher background

The standard asks for differences among common models; the example names the three families. Stay conceptual. Logistic: one line + probability — good for frost yes/no on a logger. Tree: 20 questions for crop diagnosis — good when experts already think in branches. Net: image of a plume — good when the pattern is texture, not three numbers. Differences to hit: decision surface (line vs. axis-aligned splits vs. flexible), interpretability, data/compute, typical jobs. Do not derive backprop. Paper tree, paper line, stacked-boxes net. Spreadsheet can compute a logistic sigmoid of a linear score if you want a number, not required. AIM.6 will stress limitations (XOR, feature importance); today is family identity.

Materials

  • Three family posters with a blank 'how it decides' box.
  • Paper 20-questions tree for a 6-leaf crop-diagnosis toy (public symptoms, no student health).
  • Logistic handout: a linear score (a*temp + b*humidity + c) then a 0–1 squish described in words.
  • Neural-net stacked boxes: pixels → hidden → label, with a 'many knobs' caption.
  • Comparison table (print).

Before class

  • Draw a tree that uses RH, wind, and leaf spots so it feels Idaho.
  • Keep XOR off-stage except a one-line 'logistic is linear; details tomorrow in AIM.6.'

Instructional sequence

Warm-up — Name the tool on the bench

5 min
  1. Three unlabeled pictures: a line through points, a flowchart, a stack of layers. Students guess names.
  2. Reveal logistic, tree, neural net. Announce: differences, not training.

Direct instruction — How each one decides

12 min
  1. Logistic: weighted sum of features, squashed to a probability, cutoff at 0.5 (or another threshold). Job: frost yes/no on few features.
  2. Tree: ask a feature question, follow yes/no, reach a leaf label. Job: 20 questions for 'which deficiency.'
  3. Net: many such weighted sums in layers; good when inputs are pixels or tokens. Job: smoke vs. cloud on a photo.
  4. Fill interpretability, data hunger, compute on the board table.

Guided practice — Walk each family once

10 min
  1. Run one new 'night' through the logistic score on paper (teacher supplies weights).
  2. Walk one diagnosis through the tree by answering questions aloud.
  3. For the net, trace a cartoon photo through two layers as 'numbers in, numbers out' — no algebra slog.

Independent practice — Comparison table

10 min
  1. Students complete the three-column table and assign one Idaho job and one poor-fit job per family.
  2. Poor-fit examples: logistic on raw photos; a giant net on 12 rows of GDD; a 10,000-node tree a grower cannot print.

Real-world examples

  • Logistic: binary 'will this canal exceed a legal cutoff tonight' on a low-power station.
  • Tree: extension 20-questions for potato nutrient issues used as a phone script.
  • Neural net: classifying GOES fire detections or counting cars in a public ITD camera (not student parking lots).
  • Sports: logistic win-probability from score and time; a tree of 'foul trouble' questions; a net on video of a shot — three families, one game.

Hands-on activity

Hands-on — Family speed round

8 min
  1. Teacher reads five jobs; teams flash a card: L, T, or N, plus a 5-word why.
  2. Include one trick (XOR or a GDD formula) that should be 'none — use a rule/procedure' to keep AIM.4 alive.
  3. Correct as a class without shaming; the point is distinctions.

Discussion questions

  1. Why would a county commissioner prefer a tree they can argue with?
  2. When is logistic's simplicity a safety feature?
  3. What does a neural net's extra power cost you in data and explanation?
  4. Are LLMs a kind of neural net? (Yes, huge ones — still not the right tool for XOR.)

Differentiation

Support

  • Table mostly filled; students add jobs only.
  • Physical walk along floor tape as a tree.

Challenge

  • Add 'random forest as many trees' in one paragraph without claiming it is a fourth required family.
  • Explain sigmoid in words: large positive score → probability near 1.

Multilingual learners

  • Family names + icon; jobs written with sentence stems.
  • Allow the table's 'how it decides' in the student's strongest language.

IEP / 504

  • One family mastered deeply (tree) plus headlines for the other two if processing is slow.
  • No required sigmoid math.

Assessment

Formative

  • Warm-up picture naming.
  • Correct walk of the paper tree.

Summative

  • Completed comparison table with a job and a poor-fit per family.
  • Speed-round participation as supporting evidence.

Success criteria

  • Student describes how each family decides in ordinary language.
  • Student does not call every model a neural net.
  • Student matches at least two families to fitting Idaho jobs.

Responsible use

Understanding families is so you stop buying 'an AI' and start asking which family, which job, which data.

Ethics

An uninterpretable net on a high-stakes yes/no (loan, discipline, medical) may be the wrong family even if it scores well.

Privacy

Toy trees use public crop symptoms. No student health, attendance, or discipline rows to 'compare models.'

Reflection

  1. Which family would you trust to explain itself to a grower?
  2. Which family would you pick if you had 40 rows vs. 40,000 photos?
  3. What difference will you remember in six weeks?

Homework

Complete the take-home comparison: in your own words, how each family decides; one Idaho job; one poor fit. Five sentences total plus the table. No training.

Closing

Three families, three jobs: a probability line, a question flowchart, a layered pixel-eater. They are not interchangeable. Tomorrow we ask what each one cannot do — including XOR for the linear family.

Extensions

  • 90-minute block: build a larger paper tree from a 12-row crop table (still no software); compare its questions to logistic's weights list.
  • Python extension: train all three on a tiny public table and print accuracy — only after AIM.9 if possible, or with a 'accuracy may lie' warning.
  • Card-sort properties (interpretable, data-hungry, linear, pixel-friendly) onto families.
  • AIM.6 next will ask what each cannot do; leave XOR as a cliffhanger.

Cross-curricular links

Biology
Dichotomous keys are decision trees; students already know the shape.
Algebra
Logistic starts from a linear combination students recognize.
Media arts
Image models are nets because photos are grids of numbers, not three features.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.6

What This Model Cannot Do

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Evaluate the features and limitations of a machine learning model.

Example from the standards. A decision tree can show feature importance, but it is limited in how it works. Logistic regression, likewise, is a linear classifier that cannot solve the XOR problem.

Student-friendly learning targets

  • I can name a real strength and a real limit for trees, logistic regression, and neural nets.
  • I can show, again in plain language, why a linear classifier cannot solve XOR.
  • I can use feature importance as a tree feature without pretending the tree is unlimited.

Essential questions

  1. If a tree can show which features matter, why not always use a tree?
  2. What exactly can a linear classifier not do?
  3. What can a neural net do that still might be the wrong tool?

Objectives

  1. Evaluate each family with a two-column card: feature (strength) | limitation.
  2. Replot XOR and connect it to logistic regression's linear boundary (tie to DA.6, do not repeat the whole pick-a-model lab).
  3. Read a tiny tree's feature-use counts as 'importance' and then break the tree with a diagonal pattern.
  4. Write an evaluation paragraph that a vendor slide would not write.

Key vocabulary

Feature importance
A report of which inputs a model relied on. Trees can show this from how often/early a feature is used. It is a clue, not a proof of cause.
Linear classifier
Separates classes with one line/plane. Logistic regression is one. XOR's diagonal yes-points cannot be split by that one line.
Axis-aligned split
A typical tree question uses one feature at a time (temp < 32), which draws splits parallel to the axes — awkward on diagonal patterns.
Limitation
Something the model family structurally cannot do well, not just 'needs more data.'
Opaque
Hard to see why an answer happened. A deep net's limitation even when accuracy is high.

Teacher background

The standards example is the lesson spine: trees show feature importance but are limited; logistic cannot XOR. Teach both halves. Strengths: tree — readable, importance; logistic — cheap, probability, few data; net — flexible surfaces, images. Limits: tree — greedy axis-aligned splits, unstable to small data changes, can overfit; logistic — linear, no XOR, weak on raw pixels; net — data/compute, opaque, can be overkill. XOR recap in 4 minutes with the ruler, then move. A 6-node paper tree on wildfire weather can show 'wind and RH used first' as importance. Spreadsheet not required. This is evaluation, not implementation.

Materials

  • XOR four-point graph and a ruler (from DA.6 kit if you still have it).
  • Paper tree on RH, wind, temp with a tally of which feature appears; a 'importance' bar sketch.
  • Diagonal-pattern overlay that the axis-aligned tree hacks into a staircase.
  • Feature | limitation cards, three families.
  • A fake vendor slide: 'Our logistic model does everything.' for critique.

Before class

  • If DA.6 was weeks ago, refresh XOR in prep so the recap is crisp.
  • Print a tree that overuses one noisy feature so 'importance' can be misleading — a key limitation of the strength.

Instructional sequence

Warm-up — Vendor claim

5 min
  1. Read: 'Our linear model solves every logic problem, including XOR, with enough data.' Students write agree/disagree in one line.
  2. Hold the ruler. We will evaluate, not cheer.

Direct instruction — Strengths that come with joints that don't bend

10 min
  1. Logistic: strength = probability + inspectable weights; limitation = one line, therefore XOR is impossible no matter the sample size of those four points.
  2. Tree: strength = questions people can audit + feature importance; limitation = one-feature splits, greedy, jumpy, memorizes.
  3. Net: strength = bent boundaries and pixels; limitation = hunger, opacity, cost. Also not automatic ethics.
  4. Replot XOR. Let a student fail the ruler. Say the sentence from the standard in plain words.

Guided practice — Importance, then a break

12 min
  1. Walk the paper tree. Tally feature uses. Sketch importance bars (wind high, month low).
  2. Show a diagonal cloud. Try to cut it with axis-aligned questions; count how many ugly splits you need.
  3. Ask: is importance a feature or a trap if the feature is a leak (DA.3)? Both — evaluation includes misuse of the strength.

Independent practice — Evaluate all three

10 min
  1. Pairs complete feature|limitation cards for all three families with an Idaho sentence each.
  2. They rewrite the vendor claim so it is true: 'Logistic is strong on small binary problems with linear-ish structure; it cannot solve XOR.'
  3. Offline: cards and XOR plot only.

Real-world examples

  • Logistic frost alarms fail if the true pattern is an interaction (warm but radiative cooling on still nights) — XOR-like interactions.
  • A 20-questions nutrient tree looks important on 'leaf color' because that question is first, not because color caused the yield.
  • A neural net smoke detector cannot explain itself to a incident commander at 2 a.m. — opacity as a limitation even if recall is high.
  • Energy load: a linear model cannot capture a holiday × temperature bend without extra features; a tree might split 'is_holiday' but will miss smooth curves.

Hands-on activity

Hands-on — Limitation museum

8 min
  1. Each pair posts one limitation with a tiny sketch (failed line, staircase tree, black-box net).
  2. Gallery: steal a better XOR sentence from a neighbor if yours used jargon only.
  3. Vote: which limitation would matter most to a fire dispatcher vs. a researcher.

Discussion questions

  1. Can more data ever make logistic solve the four XOR points? (No. The family cannot draw the shape.)
  2. If a tree's top important feature is an ID number, what limitation just showed up?
  3. Is opacity a feature (harder to game) or a limitation (harder to trust)? For whom?
  4. How is this evaluation different from AIM.5's comparison table? (We stress failure modes.)

Differentiation

Support

  • XOR plot pre-labeled; student only writes 'one line cannot split the diagonal.'
  • Two families only (logistic + tree) if needed.

Challenge

  • Explain that a small net or a tree ensemble can solve XOR, and still justify shipping the IF rule on a pump (DA.6 + AIM.4).
  • Critique feature importance vs. causation using the leaky column from DA.3.

Multilingual learners

  • limitation / strength / linear / importance glossary.
  • Sketch-first, then a sentence stem.

IEP / 504

  • Physical ruler XOR is the assessment; cards can be dictated.
  • Avoid extra algebra on logistic scores.

Assessment

Formative

  • Vendor-claim disagree line.
  • Feature-use tally on the paper tree.

Summative

  • Three feature|limitation cards plus a true rewrite of the vendor sentence including XOR.
  • Tree card must mention both importance (feature) and a limit (axis-aligned / overfit / instability).

Success criteria

  • Student explains XOR vs. linear classifiers in ordinary language.
  • Student treats feature importance as a tree strength with a caveat.
  • Student names a neural-net limitation other than 'it's hard.'

Responsible use

Evaluating limits is how you refuse a vendor model that cannot do the job even with 'more data.'

Ethics

A limitation that falls on one group (a linear screen that cannot capture a legitimate interaction) is a fairness issue, not only a math one.

Privacy

No student-performance data to 'show feature importance of attendance.' Use weather and crop toys.

Reflection

  1. Which limitation will you actually use in a design review?
  2. How would you explain XOR to a parent in 20 seconds?
  3. When is a model's strength the thing that will trick you?

Homework

One page: evaluate logistic, tree, and net. For each, one feature, one limitation, one Idaho job to avoid. XOR paragraph required in ordinary language. Graph may be copied from class.

Closing

Trees can show importance and still cut the world into rectangles. Logistic is honest, cheap, and cannot XOR. Nets bend and hide. Evaluation means saying the second sentence, not only the first. Next we plan the human gates so those limits do not run unsupervised.

Extensions

  • 90-minute block: try to hand-build a staircase tree for XOR (it can, awkwardly) vs. the one-line rule; write which limitation you still care about.
  • Python extension: logistic on XOR (fails); decision tree on XOR (can pass); print importances — notebook extra.
  • Card-sort 'feature' vs. 'limitation' claims, including traps ('more layers always help').
  • Printed XOR tracing for subs.

Cross-curricular links

Geometry
Linear separability and axis-aligned rectangles are visual, not mystical.
Statistics
Variable importance is not causation; same lecture as confounding.
Engineering
Choosing a family is choosing which failures you can live with.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.7

Human in the Loop, On Purpose

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Plan safeguards for AI systems that protect human well-being and privacy while ensuring meaningful human involvement in decision-making.

Example from the standards. Web search can return anything, or you can filter it for child-appropriate content.

Student-friendly learning targets

  • I can plan safeguards that protect well-being and privacy, not only accuracy.
  • I can place a meaningful human-in-the-loop step where a person can actually change the outcome.
  • I can use filtered vs. unfiltered web search as a concrete safeguard example.

Essential questions

  1. What is the difference between a human who rubber-stamps and a human who can say no?
  2. Which harms are about well-being, which are about privacy, and which are both?
  3. If we filter web search for a classroom agent, what do we lose and what do we protect?

Objectives

  1. Inventory harms for one Idaho system (wildfire paging, school help agent, load-shed suggestion).
  2. Plan at least five safeguards: filter, approval, confidence escalate, PII strip, logging/kill switch.
  3. Mark humans as meaningful (they have time, information, and authority) not decorative.
  4. Apply the standards example: unfiltered vs. child-appropriate filtered search.

Key vocabulary

Safeguard
A designed control that reduces harm: filters, approvals, rate limits, PII stripping, kill switches, confidence gates.
Human-in-the-loop
A person must verify, approve, or correct before the system acts. Meaningful means they can change the action, not just watch it.
Well-being
Physical and psychological safety: crews not paged into nothing, students not shown harmful content, patients not dosed by a model.
PII strip
Removing names, IDs, addresses, and other identifiers before data hits a model or a log.
Content filter
A rule layer that blocks categories of web or model output (e.g., child-inappropriate search hits) before a user sees them.

Teacher background

AIM.2 required an approval diamond; AIM.7 is a full safeguard plan for well-being, privacy, and meaningful humans. Teach the web-search example first: an agent with unfiltered search can pull anything; a classroom or library agent should use a child-appropriate filter — a rule layer around a data-driven tool (AIM.4 combo). Then plan a wildfire 'page crews' system: confidence threshold, human dispatcher, no auto-tone-out, logging, privacy of camera homes. Rubber-stamp humans (0.3 seconds to click OK) fail the standard. Spreadsheet of harm × safeguard is the artifact. Offline card sort of safeguards onto a system diagram. No live unfiltered search demos of harmful content.

Materials

  • System-at-risk one-pagers: (A) classroom web-search agent, (B) wildfire page-crews recommender, (C) school lab-assistant from AIM.2.
  • Safeguard cards: filtered search, unfiltered search, human approve, confidence escalate, PII strip, rate limit, log+audit, kill switch, age gate, no-retention.
  • Meaningful-human checklist: time, information, authority, backup person, no punishment for saying no.
  • Plan template: harm, who is hurt, safeguard, where in the flow, how we know it works.

Before class

  • Do not open unfiltered search on a projector. Describe the risk; use the filter as the live path if you demo at all.
  • Coordinate with AIM.9: paging crews will return as false positives. Today is the human gate; next is the metric.

Instructional sequence

Warm-up — Search can return anything

5 min
  1. Read the standards example. Students list three categories a 9th-grade lab agent should not display.
  2. Ask: is a filter a model or a rule? (Often a rule or a separate classifier with a human policy.)

Direct instruction — Well-being, privacy, meaningful humans

10 min
  1. Three goals from the standard. Map safeguards to each (filter → well-being; PII strip → privacy; approval with authority → meaningful involvement).
  2. Show a fake loop: a dispatcher has 80 alerts/minute. That human is not meaningful. Redesign: fewer alerts, better ranking, legal power to ignore.
  3. Kill switch: a labeled way to turn the recommender off during a real incident.

Guided practice — Filter the search agent

12 min
  1. On system A, place unfiltered vs. filtered search cards. Write who sets the policy (librarian, admin, vendor — debate).
  2. Add PII strip (no student names in queries stored) and no-retention.
  3. Run the meaningful-human checklist on 'teacher can override the filter.' Who audits the override?

Independent practice — Plan for paging or the lab agent

10 min
  1. Pairs take system B or C and fill five rows of the plan template, including at least one well-being, one privacy, and one human-in-the-loop safeguard.
  2. They mark any human step that is currently a rubber stamp and fix it.
  3. Offline: cards on the one-pager diagram.

Real-world examples

  • Classroom search: filtered vs. raw web, exactly the standards example.
  • Wildfire: a model that auto-pages crews without a dispatcher harms well-being (fatigue, missed real fires) and can leak camera views of homes (privacy).
  • Idaho Power load-shed suggestions must not auto-cut a hospital feeder; a human operator with authority is the safeguard.
  • A counseling chatbot that cannot escalate to a human fails well-being even if it 'respects privacy.'

Hands-on activity

Hands-on — Red-team the plan

8 min
  1. Neighbor tries to route around the human (script the approval, flood the queue, put PII in a screenshot).
  2. Pairs add one more safeguard and initial the checklist.
  3. Share one failed rubber-stamp they caught.

Discussion questions

  1. Who is harmed if the child-appropriate filter is too aggressive? Too weak?
  2. Can logging be both a safeguard and a privacy hole?
  3. Should a kill switch live in software, in a physical button, or both?
  4. When is 'the human is in the loop' a slogan that hides an unsafe system?

Differentiation

Support

  • System A only (search filter) with three safeguards pre-named to explain.
  • Checklist with yes/no boxes.

Challenge

  • Write a policy paragraph on filter overrides: who, logging, time limit.
  • Design the wildfire queue so a dispatcher can be meaningful at 2 a.m. (rate, grouping, map).

Multilingual learners

  • Safeguard names with glosses; plans may be bilingual.
  • Role-play the approval conversation.

IEP / 504

  • Card placement is sufficient; writing reduced to three rows.
  • Avoid graphic wildfire imagery; stick to process.

Assessment

Formative

  • Three categories listed in the warm-up.
  • Meaningful-human checklist used in guided practice.

Summative

  • Plan template with five safeguards covering well-being, privacy, and a non-rubber-stamp human step.
  • Must include filtered search or an analogous content/action filter.

Success criteria

  • Student's human can say no with time and authority.
  • Student names a privacy safeguard (PII, retention, cameras).
  • Student treats filters as a designed control, not as censorship trivia.

Responsible use

Do not demo harmful unfiltered results. Plan on paper. District filter policy wins over a vendor default.

Ethics

Safeguards can be paternalistic or captured by vendors. Students should name who sets the filter and how it is reviewed.

Privacy

FERPA: student queries are education records if stored. Default to no-retention. Camera systems must not enroll student faces.

Reflection

  1. Where was your human not actually meaningful on the first draft?
  2. Which safeguard would you fund first with a small budget?
  3. How will you explain filtered search without sneering at it?

Homework

Revise the AIM.2 agent flowchart with three labeled safeguards (filter, approval, PII). Write four sentences on what makes the human meaningful. Paper; no live agents.

Closing

Web search can return anything — or you can filter it. Crews can be auto-paged — or a person with authority can say no. Safeguards are designed, not hoped. Next we look at the whole training pipeline from the methods side, including leakage.

Extensions

  • 90-minute block: tabletop incident — unfiltered query, then a wildfire false alarm flood; revise the plan.
  • Python extension: a stub filter list and an approve() gate in code comments as a design, not a product.
  • Connect to AIM.2 flowcharts and upgrade their diamonds using today's checklist.
  • Printed safeguard card sort for subs.

Cross-curricular links

Health / counseling
Escalation to a human is a well-being safeguard, not a model failure.
Government / library science
Collection filters and challenge policies already exist; AI search inherits that debate.
Emergency services CTE
Dispatch already uses human-in-the-loop; models must not erase it.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.8

The Lifecycle, Methods View

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Examine the procedure of how data is used to train machine learning models.

Example from the standards. Looking at the complete data lifecycle including collecting, data munging, feature engineering, and creating training, development/validation, and test data splits.

Student-friendly learning targets

  • I can diagram the full training procedure: collect, mung, engineer features, split train/dev/test, train, evaluate.
  • I can explain feature engineering and data leakage in methods language.
  • I can contrast this lecture+card-sort with DA.3's hands-on CSV station lab without repeating that lab.

Essential questions

  1. What extra steps sit between 'clean CSV' and 'honest test score'?
  2. How can a brilliant feature be cheating?
  3. Why tune on dev and touch test once?

Objectives

  1. Card-sort the lifecycle into a single pipeline including feature engineering and three-way split.
  2. Identify at least three leakage patterns (future info, target in features, test peeking, duplicate rows across splits).
  3. State what each split is for: train fits, dev tunes, test reports.
  4. Write a methods note that a DA.3 potato-yield lab would still have to obey.

Key vocabulary

Feature engineering
Building new inputs from raw columns (GDD from temps, 'is_weekend' from a date, a ratio of wind to RH) before the model sees them.
Development / validation set
The middle split used to compare choices (features, thresholds, model family) without touching the test set.
Data leakage
The model sees information it would not have at prediction time, or sees test rows while training, so scores look fake-good.
Hyperparameter
A knob you set (tree depth, threshold) using dev performance, not a weight the training algorithm fits on its own.
Munging
Cleaning and reshaping raw data (types, missingness, duplicates) before features are built. Same word as in DA.3, methods view now.

Teacher background

DA.3 walked a potato-yield or wildfire CSV through collect → mung → features → split as a station lab and stopped before training. AIM.8 is the methods lecture: complete lifecycle, feature engineering as a craft, leakage as the central sin, three splits with roles, where training actually sits. Do not rerun the 40-row stations. Use a large pipeline poster and a leakage card-sort. Example features: GDD from min/max temp (procedural feature, AIM.4), county one-hot, lagging yesterday's cfs (careful: time). Leakage: using final fire acres to predict ignition morning; using the test mean to fill missing train values; shuffling so the same farm appears in train and test; peeking at test accuracy 40 times. Spreadsheet is only for a leakage demo (a 'future' column). Python is extension.

Materials

  • Pipeline poster strips: collect, mung, feature engineering, split, train on train, tune on dev, evaluate once on test, deploy.
  • Leakage cards (8): future column, target encoded in an ID, test-mean imputation, duplicate rows, random split on time series, peeking 40 times, using post-treatment acres, student PII as a feature.
  • Legal-feature cards: GDD, yesterday's public cfs, county, wind×RH (engineered), planting month.
  • DA.3 reminder slip: 'You already split a CSV. Today we add engineering and leakage.'

Before class

  • If DA.3 has not been taught, give a 3-minute summary; do not convert this period into the station lab.
  • Print a bad pipeline that trains on all rows then 'tests' on a subset of them.

Instructional sequence

Warm-up — Where does training sit?

5 min
  1. Students place a TRAIN magnet on a blank timeline. Most will put it too early.
  2. Reveal: after collect, mung, engineer, split — and only on the train slice.

Direct instruction — The complete procedure

12 min
  1. Walk the standards list: collecting, munging, feature engineering, train/dev/test splits. Add the methods extras: train, tune on dev, test once.
  2. Feature engineering examples: GDD; a frost binary from temp; a 3-day wind mean. Each is a choice that can leak if it uses the future.
  3. Three splits: train (fit), dev/validation (choose features, depth, threshold), test (report). Peeking is leakage.
  4. Show one future-column leak on the wildfire story from DA.3 without reopening the full CSV kit.

Guided practice — Build the poster

10 min
  1. Class hangs pipeline strips in order. Debate whether mung comes before or after split (fit mung stats on train only — advanced but worth saying).
  2. Place two legal features and two leaks on the poster.
  3. Rewrite the bad pipeline (train on all rows) as a crime scene.

Independent practice — Leakage card-sort

10 min
  1. Pairs sort eight cards into leak / not leak / depends, with a because-sentence.
  2. They write where in the pipeline they would catch each leak.
  3. Offline is the sort itself.

Real-world examples

  • Energy load: using tomorrow's actual MW as a feature to 'predict' tomorrow is leakage; using a weather forecast is not (if that forecast would have existed).
  • Yield: post-harvest price as a feature for a planting-time model is future info.
  • Sports: using the final score to predict in-game win probability at halftime is leakage; using score at halftime is legal.
  • River gauges: imputing missing train cfs with the test week's mean smuggles test information.

Hands-on activity

Hands-on — Methods note for the DA.3 table

8 min
  1. Without redoing stations, students write a half-page methods note: how they would engineer two features, how they would split in time vs. random, how they would keep test sealed while tuning.
  2. Swap notes; highlight any leak.

Discussion questions

  1. Should feature engineering happen before or after the split, and what goes wrong either way?
  2. If we only have 40 rows (DA.3), is a three-way split still right? (Maybe nested or a tiny dev — methods honesty still matters.)
  3. Why is 'we shuffled and got 99%' a confession, not a brag, on a time series?
  4. How is leakage different from the DA.5 coverage gap? (Cheating vs. missing people.)

Differentiation

Support

  • Pipeline strips numbered; sort only leak vs. not leak on four cards.
  • Sentence stems for the methods note.

Challenge

  • Explain target leakage vs. train-test contamination as two species.
  • Design a time-based split for wildfire days that still keeps counties represented.

Multilingual learners

  • Pipeline verbs with glosses; card-sort is visual.
  • Methods note allowed bilingual with English stage names.

IEP / 504

  • Poster placement as the artifact; skip the half-page if writing is the barrier.
  • Fewer leakage cards.

Assessment

Formative

  • TRAIN magnet placement after instruction.
  • Two leaks correctly placed on the poster.

Summative

  • Sorted leakage deck with because-sentences plus a methods note that includes feature engineering and a sealed test.
  • Repeating DA.3 station work without engineering/leakage does not meet AIM.8.

Success criteria

  • Student lists collect, mung, feature engineering, and train/dev/test in a sensible order.
  • Student explains at least two leakage types.
  • Student can say what dev is for.

Responsible use

Do not scrape new student data to 'practice collection.' Collection here is a pipeline stage, not a survey of the class.

Ethics

A leaked test score can ship a harmful model with a straight face. Honesty in the procedure is an ethical duty.

Privacy

Leakage card 'student PII as a feature' is a hard no under FERPA, not only a methods fail. Public tables only.

Reflection

  1. Which leakage type would have fooled you last month?
  2. How will you remember that dev is not test?
  3. What is one feature you want to engineer on the potato table that is legal at planting time?

Homework

Diagram the lifecycle on one page, including feature engineering and three splits. Add three leakage examples (one time-based, one future column, one peeking). Do not redo the DA.3 CSV.

Closing

DA.3 put a CSV through collect, mung, features, split. AIM.8 added the craft: engineering, leakage, and why three piles exist. Training is one box in a longer honest procedure. Last methods lesson: the score people quote is often a trap.

Extensions

  • 90-minute block: a longer leakage museum and a 'fit scaler on train only' spreadsheet demo; still not a second DA.3 station rotation.
  • Python extension: demonstrate leakage by including a future column and watching accuracy jump — then drop it.
  • Guest: a data engineer (Micron, lab, county) on munging vs. engineering in their pipeline.
  • Printed pipeline tracing for subs.

Cross-curricular links

Statistics
Holdout and cross-validation are the cousins of train/dev/test; peeking is p-hacking.
History / social science
Using later knowledge to explain an earlier event is the same intellectual leak.
Agriculture
Features known at planting vs. at harvest decide whether a yield model is a forecast or a diary.

Back to contents

AI Technical Aptitude · AI Methods

9-12.AITA.AIM.9

Accuracy Is a Trap

9–12 CS / engineering · 50 minutes · 90 minutes (lab extension)

Standard quoted exactly

Interpret AI results using common metrics and be able to communicate those to a diverse audience.

Example from the standards. A credit card fraud classifier is 99.9% correct using an accuracy metric, but that's only because 99.9% of transactions are not fraudulent.

Student-friendly learning targets

  • I can explain why accuracy looks great on a rare-event problem and still fails the job.
  • I can compute accuracy, precision, and recall from a confusion matrix and say them in ordinary language.
  • I can communicate the same result to a fire chief, a county commissioner, and a neighbor without hiding false pages.

Essential questions

  1. If a model is 99.9% accurate, what might it still be refusing to find?
  2. What does a false positive cost a fire crew, and what does a false negative cost a hillside?
  3. Which metric should you lead with for which audience?

Objectives

  1. Build a confusion matrix for a rare-event task (fraud or Idaho wildfire starts).
  2. Compute accuracy, precision, recall; identify false positives that page crews and false negatives that miss ignitions.
  3. Rewrite a 99.9% accuracy boast using the standards fraud example and a matched wildfire story.
  4. Produce three audience-specific sentences that stay true to the same numbers.

Key vocabulary

Accuracy
Share of all cases the model got right: (TP + TN) / all. Looks huge when the rare class is tiny.
Class imbalance
One class is much rarer than the other (fraud, fire starts, equipment failure). Accuracy then tracks the majority class.
Precision
Of the alarms we rang, how many were real: TP / (TP + FP). Low precision means crews get paged for camp stoves.
Recall
Of the real events, how many we caught: TP / (TP + FN). Low recall means ignitions we never saw.
Confusion matrix
A four-cell table of truth vs. prediction: true positive, false positive, true negative, false negative.

Teacher background

This lesson must teach class imbalance. Use the standards fraud example and an Idaho wildfire rare-event table so students feel both. Numbers that work on paper: 10,000 grid cells, 10 real starts. A no-fire-always model is 99.9% accurate and 0% recall. A jumpy model that flags 200 cells with 8 real fires: compute precision 8/200 = 4%, recall 8/10 = 80%, accuracy still high because of all the true negatives. False positives page crews (overtime, ignored future tones). False negatives miss a start (acres). Communication: fire chief wants recall and FP load; commissioner wants cost; public wants 'will it miss my canyon?'; engineer wants the matrix. Spreadsheet four cells plus formulas. Offline: printed matrix with chips to count. Do not hide the algebra; it is four numbers.

Materials

  • Fraud one-pager matching the standard: 999,000 legit of 1,000,000; a dummy 'always legit' model at 99.9% accuracy.
  • Wildfire matrix kit: 10,000 cells, 10 starts; two model result cards (always-no vs. jumpy pager).
  • Four colored chips or paper squares: TP, FP, TN, FN.
  • Audience cards: fire chief, county commissioner, news reporter, model engineer, canyon homeowner.
  • Calculator or spreadsheet; printed formula strip.

Before class

  • Precompute both scenarios so you can coach arithmetic without scooping the insight.
  • If AIM.7 used paging, hang that flowchart and add metrics to the same gate.
  • Avoid graphic burn photos; the matrix is the visceral object.

Instructional sequence

Warm-up — 99.9% — hire this model?

5 min
  1. Read the fraud example. Vote hire / do not hire.
  2. Reveal: the model predicted 'not fraud' every time. Accuracy is a trap when the event is rare.

Direct instruction — Four cells, three metrics, one imbalance

12 min
  1. Draw the matrix. Name TP (caught fire/fraud), FP (false page), FN (missed event), TN (correct quiet).
  2. Accuracy = (TP+TN)/all. Precision = TP/(TP+FP). Recall = TP/(TP+FN).
  3. Work the always-no wildfire model: TP=0, FN=10, FP=0, TN=9990, accuracy=99.9%, precision undefined or 0, recall=0.
  4. Say costs in Idaho English: FP pages crews; FN burns acres. Neither is 'accuracy.'

Guided practice — The jumpy pager

10 min
  1. Give jumpy-model counts (e.g., TP=8, FP=192, FN=2, TN=9798). Compute the three metrics as a class.
  2. Ask which metric you would quote to a fire chief (recall + FP count) vs. a headline (not 97.9% accuracy).
  3. Connect to AIM.7: a human dispatcher is a safeguard against a low-precision flood.

Independent practice — Three audiences, one matrix

10 min
  1. Pairs write three communications (2–3 sentences each) for three audience cards using the same jumpy-model numbers. No new math that contradicts the matrix.
  2. They must mention class imbalance once in student language ('fires are rare, so…').
  3. Offline: chips on a printed matrix, then sentences.

Real-world examples

  • Credit card fraud: the standards 99.9% story; banks actually optimize precision/recall and dollar loss, not accuracy.
  • Idaho wildfire starts on a 10,000-cell grid: always-no looks like a genius on accuracy and a disaster on recall.
  • Hospital lab 'always healthy' classifiers on rare conditions — same trap, different harm.
  • Sports: a model that always predicts the favorite in a lopsided conference can be 'accurate' and useless for an underdog bet — class imbalance in outcomes.

Hands-on activity

Hands-on — Chip the matrix, then translate

8 min
  1. Students place chips for a third scenario (teacher choice: 10 frauds in 10,000; model catches 6, pages 30).
  2. Compute metrics. Peer-check arithmetic.
  3. Read one audience sentence aloud; class flags hidden accuracy boasts.

Discussion questions

  1. Is a 4% precision smoke alarm ever acceptable if recall is 80%? Who pays for the 96% false pages?
  2. Why is 'accuracy 97.9%' a dishonest lede for the jumpy pager?
  3. How would you explain undefined precision when TP+FP=0?
  4. Which metric should a canyon homeowner hear first?

Differentiation

Support

  • Formula strip and a matrix with blanks only for TP/FP; TN pre-filled.
  • Two audiences instead of three; sentence stems.

Challenge

  • Introduce F1 as the harmonic mean in one paragraph, still leading with precision/recall.
  • Show how moving a threshold trades precision vs. recall on a sketched curve (no software).

Multilingual learners

  • Metric names + 'alarms that were real' / 'fires we caught' glosses.
  • Audience sentences in the student's strongest language plus English for the commissioner.

IEP / 504

  • Chips and a calculator; one audience sentence.
  • Large matrix; skip extra scenario.

Assessment

Formative

  • Hire/do-not-hire vote plus the always-no reveal.
  • Correct jumpy-model arithmetic in guided practice.

Summative

  • Completed matrix with three metrics and three audience communications that do not hide FPs/FNs.
  • A student who only reports accuracy has not met the standard.

Success criteria

  • Student can define class imbalance with fraud or wildfire numbers.
  • Student computes precision and recall from four cells.
  • Student changes language for audience without changing facts.

Responsible use

Do not use student discipline or attendance as a 'rare event' toy. Fraud (public-style numbers) and wildfire grids only.

Ethics

Choosing a metric chooses who pays: crews (FP) or landscapes and families (FN). That is a values decision reported as math.

Privacy

No real card-transaction files, no student financial data, no household addresses on the wildfire grid. Abstract cells and public-style counts.

Reflection

  1. When will you refuse to quote accuracy?
  2. Which audience was hardest to write for, and why?
  3. How does this change what you demand from a vendor demo?

Homework

On the take-home matrix (wildfire or fraud), compute accuracy, precision, and recall. Write three audience paragraphs (chief, commissioner, neighbor). Circle every time you were tempted to lead with accuracy and did not.

Closing

99.9% can mean 'we never tried to find the rare thing.' Precision asks whether pages were real; recall asks whether fires were caught; false positives tire crews. Quote the metric that matches the harm, in language the audience can use. That is the methods capstone.

Extensions

  • 90-minute block: threshold workshop — two cutoffs, two matrices, a precision-recall trade; write a dispatcher SOP.
  • Python extension: sklearn classification_report on a public imbalanced CSV; still require the prose translation.
  • Card-sort headlines into 'honest' vs. 'accuracy trap.'
  • Printed chip matrix for a no-device day.

Cross-curricular links

Statistics
Sensitivity/specificity in biology and health are cousins of recall and true-negative rate.
Journalism
Lead with the number that answers the audience's question, not the one that looks biggest.
Civics / emergency management
False pages are a public-resource problem; metrics are a civic communication duty.

Back to contents