Most schools are still arguing about whether students should be allowed to touch AI. We think that argument is already over. The tools are in every pocket, woven into search engines, homework apps, and writing software your child already uses. Pretending otherwise doesn’t protect anyone — it just leaves students to figure it out alone, in secret, with no one teaching them the difference between using a tool well and laundering its output as their own work.
So our posture is simple, and it has two halves. First, we teach AI literacy — how to prompt, how to interrogate, how to catch the machine when it lies. Second, we assess in ways AI can’t fake. A student demonstrates understanding out loud, in person, defending a real lab notebook and performing a measurement or an experiment in front of a person. There is no prompt that reads a graduated cylinder or runs a controlled test for you. When the assessment is honest, the studying becomes honest too, and AI turns back into what it should have been all along: a tutor that never gets tired, not a ghostwriter.
The course’s AI posture
We treat AI the way a good science teacher treats any sharp tool. It is genuinely useful and genuinely capable of doing damage, and the answer to both facts is the same: instruction, not prohibition. A student who has never been taught how AI fails — how it invents citations, gets a simple calculation wrong with total confidence, mislabels the variables in an experiment, and tells you what you want to hear — is far more dangerous to their own learning than one who has been shown exactly where the tool breaks.
Our aim is a student who can sit down with an AI assistant and treat it like a sharp, fast, slightly unreliable study partner: useful for drilling the parts of a controlled experiment, useful for re-explaining what a variable is three ways, never trusted on a numerical answer without checking the arithmetic, and never — not once — allowed to stand in for the thinking the student is supposed to be doing. The line we draw is not about the tool. It is about whose understanding ends up in the work.
Encouraged vs. off-limits
Here is the bright line, stated plainly. The left column is AI used to build your understanding. The right column is AI used to replace it. The difference is not subtle, and your child will learn to feel it.
| ✓ Encouraged | ✗ Off-limits |
|---|---|
| Drilling facts you must know cold — ask AI to quiz you on the steps of the scientific method, the difference between a variable and a control, or how to round to the right number of digits, until you can recite them without it. | Submitting AI text as your own lab notebook. The notebook is a record of what you measured and observed. Borrowed words describing an experiment you didn’t run are a falsified record. |
| Re-explaining hard concepts — have AI explain what makes an experiment “controlled,” or why uncertainty matters, three different ways until one lands. | Having AI compute your lab results for you. Pasting your stopwatch times in and copying out the average, without doing — and understanding — the calculation yourself. |
| Checking your own work after you’ve done it — design an experiment yourself, then ask AI to spot a variable you forgot to control and explain why it matters. | Copying an answer without verifying. Pasting an AI result into your work without checking the arithmetic or whether the units actually make sense — they often don’t. |
| Summarizing your own notes — paste in your notes on reading graphs and ask AI to summarize, then check whether the summary matches what you meant. | Outsourcing the reasoning. Asking AI for the conclusion of a data-analysis problem you were assigned to reason through yourself. |
| Debugging your reasoning — show AI your line of thinking about why one paper airplane flew farther and ask where the logic breaks, then judge whether it’s right. | Disguising the source. Editing AI output just enough to hide where it came from, then presenting it as original thought. |
Notice the pattern. Everything on the left ends with you doing the understanding. Everything on the right ends with the machine doing it for you and you taking the credit. When you’re unsure which column you’re in, ask one question: if the AI vanished right now, could I still design this experiment and explain the result? If yes, you’re studying. If no, you’re cheating — mostly cheating yourself.
What AI simply cannot do
There is a hard floor under this whole course, and it is the lab. AI cannot line up a ruler and read a length, cannot watch a bean seedling lean toward the light over three days, cannot time an ice cube melting with a stopwatch in its hand. It cannot do the in-person demonstrations. No model can measure a volume of water in a graduated cylinder to the nearest milliliter, record it honestly, and defend each reading to an examiner asking follow-up questions.
That is the quiet genius of the model: when the finish line is a live demonstration, AI stops being a shortcut and becomes a training partner, because the only way it helps you is by getting you genuinely ready to stand in the lab yourself. We walk through exactly how this works in AI-proof by design — the design principle that lets us welcome the tool instead of fearing it.
An assessment you can fake with AI was probably an assessment that wasn’t measuring much to begin with. The live skill demonstration doesn’t beat AI by being harder — it beats AI by being real.
Curated prompt library
Here are concrete prompts students can copy and paste to turn an AI assistant into an honest study partner for lab skills. The trick is to make the AI ask you things rather than tell you things. Notice that every one of these ends with you doing the work.
Save the ones that work for you. Over a semester, a student who studies this way builds something no AI can hand them: the reflex of explaining and computing out loud, which is exactly the reflex every demonstration rewards.
Checking the machine
Here is the single most important habit we teach: AI is confidently wrong, and in science it is wrong in specific, dangerous ways. It will hand you an average that doesn’t match the numbers you gave it, mislabel which variable was the control, drop a unit, or assert a lab step is safe when it isn’t. It states all of this in the same calm, authoritative tone it uses for facts, and that tone is engineered to be persuasive. A student who trusts it blindly will absorb errors that sound right — and, in the lab, a wrong claim about what is safe to do is not just an academic error.
So treat every AI claim as a hypothesis, not a verdict. When the machine gives you a number, do three things: redo the arithmetic yourself, check that the units make sense, and never — ever — act on an AI safety claim about a lab step without checking with your guide first.
- Redo the math. Before trusting any average or calculation, work it out yourself from your own numbers. AI gets this wrong often.
- Check the units. Carry units through every calculation by hand — a confident answer in the wrong units is a wrong answer.
- Never take a safety claim on faith. If AI says a lab step is safe, verify with your guide before you do it. This is the one place a check is non-negotiable.
A student who leaves this course able to catch the machine has learned something more durable than any single lab skill: how to think clearly in a world full of fluent, fast, confident voices that are sometimes simply wrong. That’s AI literacy. And it’s why we teach the tool instead of banning it.