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, at a bench, defending a real lab notebook and finding a living cell under the microscope in front of a person. There is no prompt that focuses the scope and names the cell parts 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 powerful tool in the lab. It is genuinely useful and genuinely capable of leading you astray, 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 facts, mislabels the parts of a cell with total confidence, gets a food chain backwards, and tells you what you want to hear — is far more at risk in 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 cell, useful for re-explaining how a food web works three ways, never trusted on a fact without checking it themselves, 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 parts of a cell, the traits all living things share, or the kingdoms of life until you can recite them without it. | Submitting AI text as your own lab notebook. The notebook is a record of what you observed. Borrowed words describing a pond-water sample you never looked at are a falsified record. |
| Re-explaining hard concepts — have AI explain why plants need sunlight, or what a food web really is, three different ways until one lands. | Having AI write up your observations for you. Pasting your rough notes in and copying out a tidy conclusion, without doing — and understanding — the observing yourself. |
| Checking your own work after you’ve done it — label a cell diagram yourself, then ask AI to check it and explain any mistake. | Copying an answer without checking it. Pasting an AI result into your work without checking whether it actually matches what you observed — it often doesn’t. |
| Summarizing your own notes — paste in your notes on how a food web works and ask AI to summarize, then check whether the summary matches what you meant. | Outsourcing the reasoning. Asking AI for the conclusion of an experiment you were assigned to reason through yourself. |
| Debugging your reasoning — show AI your thinking about why a seedling in a dark closet turned pale 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 label this cell and explain what each part does? 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 bench. AI cannot focus a microscope on a living cell, cannot watch a tiny creature dart across a drop of pond water, cannot feel the pale roots of a seedling or smell the soil it grew in. It cannot do the in-person demonstrations. No model can sit at a microscope, find a cell, name its parts, and defend each one 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 at the bench 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 microscope defense 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 life science study partner. 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 out loud what they see and understand, 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 life science it is wrong in specific ways. It will make up a fact, mislabel the parts of a cell, get a food chain backwards, or state something about a living thing that simply isn’t true. It says all of this in the same calm, authoritative tone it uses for real facts, and that tone is engineered to be persuasive. A student who trusts it blindly will absorb errors that sound right — and a wrong fact that sounds right can quietly settle into their understanding and stay there.
So treat every AI claim as a hypothesis, not a verdict. When the machine tells you something, do three things: check the fact yourself, compare it to what you actually observed, and never take a surprising claim about a living thing on faith without looking it up in a real field guide or asking your guide.
- Check the facts. Before trusting any answer, compare it to your textbook, your field guide, or what you saw with your own eyes. AI gets this wrong often.
- Compare it to your observations. A confident answer that doesn’t match what you saw under the microscope is a wrong answer.
- Never take a surprising claim on faith. If AI tells you something new about a living thing, verify it against a real field guide or your guide before you write it down. 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 unit of life science: 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.