Quick CRAFT cycle intro (C→R→A→F→T). Then the stakes: your students are already using AI — here's what we know about how often it's wrong.
8:45
You DoContextualize8 min
Self-Assessment: AI in Your Classroom
In the shared doc, answer honestly: How are your students using AI right now? (Not at all / Secretly / With my guidance / I have no idea.) Then: What's your biggest worry about student AI use?
When a student uses AI: (a) plagiarism, (b) they didn't learn, (c) it might be wrong, (d) I can't tell. Vote honestly.
8:56
ListenReframe5 min
The Real Problem Isn't AI Use — It's Unverified AI Use
Poll results + the key reframe: banning AI teaches avoidance. Teaching verification teaches engineering thinking. We don't ban calculators — we teach when and how to use them.
9:01
You DoReframe14 min
Breakout: Rewriting the AI Policy
Your group is an AI policy committee. Draft 3 classroom norms for AI use that assume students WILL use AI but must VERIFY outputs. Think: what does "acceptable AI use" look like in your subject? Write your norms in the shared doc.
9:15
Break10 min
Break #1
Check chat for a deliberately wrong AI "fun fact." Can you spot the error before we're back?
9:25
ListenAssemble8 min
I Do: Catching a Code Bug (Live)
Watch: we ask an LLM to write a Python function. The code looks correct. It compiles. But it's wrong. Follow along as we debug it step by step.
9:33
You DoAssemble22 min
Breakout: Code Error Hunt
Your group gets 3 AI-generated code snippets (math/science problems). For each one: (1) Read it. (2) Predict what it does. (3) Find the error. (4) Fix it. Document your findings in the shared doc. First group to catch all 3 errors gets bragging rights.
Ask any LLM to solve a code or math problem from your subject area. Then try to break it. Document one error you found (or if it's correct, explain exactly how you verified it). Add to the shared doc.
10:10
ListenAssemble5 min
I Do: When AI Sounds Right but Isn't
Watch: an LLM explains a STEM concept. It sounds confident. It uses the right vocabulary. And it's subtly, dangerously wrong.
10:15
You DoAssemble20 min
Breakout: Content Error Hunt
Your group gets AI-generated science/math explanations. Use the Content Audit Checklist: check claims, verify facts, assess grade-appropriateness, spot misleading simplifications. Flag the sneakiest error for share-out.
The 4-step protocol: Task → Before → After → Takeaway. Here's how it works.
10:48
You DoFortify10 min
Watch & Follow Along: Live CtM Cycle
Facilitator runs a complete CtM on screen. Follow along on your own device — run the same prompt, write your own "Before" prediction, compare your "After" to ours.
10:58
You DoFortify15 min
Partner Practice: Run Your Own CtM
Pair up. Each person picks a prompt relevant to their subject. Run a full CtM cycle: Task → Before → After → Takeaway. Partner reviews and asks: "Did you actually verify, or did you just skim?"
Open the editable CtM template. Adapt it for your students: adjust the language for grade level, pick a sample task from your subject, write the student-facing instructions. This is yours to take home.
11:25
ListenTransfer5 min
CRAFT Debrief: Naming the Phases
Walk through today's session — every activity mapped to C→R→A→F→T. You just lived it (twice, actually — the code and content cycles were nested CRAFT loops).
11:30
You DoTransfer10 min
Pair-Share: Building a Verification Culture
With a partner: What's one concrete step you'll take to build a verification-first culture in your classroom this semester? Write it in the shared doc. Be specific — "I will..." not "I might..." Quick whole-group share of the boldest commitments.
11:40
You Do10 min
Explore: Your Verification Toolkit
Browse the resources: CtM template, Content Audit Checklist, AI Error Gallery with annotated examples, prompt library. Bookmark what you need.