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 in front of a person. You cannot paste your way through that. 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 chemistry teacher treats a Bunsen burner. 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, smooths over gaps with confident nonsense, 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, useful for explaining, never trusted without checking, 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
The examples below distinguish help with studying from replacing the student’s work. The teacher should explain what assistance is permitted for each task. Students should be able to describe how they used a tool and check its suggestions.
| ✓ Encouraged | ✗ Off-limits |
|---|---|
| Generating practice questions — ask AI to quiz you on a unit so you can find your weak spots before a demonstration. | Submitting AI text as your own lab notebook. The notebook is a record of what you observed and reasoned. Borrowed words are a falsified record. |
| Explaining hard passages — have AI re-explain a dense paragraph three different ways until one of them lands. | Having AI prep your demonstration for you without understanding it — memorizing an answer you can't defend or extend. |
| Quizzing yourself — turn AI into a flashcard partner that asks one question at a time and corrects you. | Copying without verifying. Pasting an AI answer into your work without checking whether it's actually true. |
| Summarizing your own notes — paste in your notes and ask AI to summarize them, then check whether the summary matches what you meant. | Outsourcing the reasoning. Asking AI for the conclusion of a problem you were assigned to reason through yourself. |
| Debugging your reasoning — show AI your line of thinking 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. |
After using AI, put the response aside and try to explain or complete the task yourself. If you cannot, you need more practice or instruction. That difficulty is not itself dishonesty. Presenting someone else’s reasoning or invented observations as your own is a different matter.
Why demonstrations matter
The instructor observes practical work, checks the student's own record, and asks follow-up questions. AI can support conceptual rehearsal but cannot certify what the learner actually did. A polished response or a timed conversation alone does not prove independent work.
Practice with AI; assess the student's science and practical evidence with a person.
Curated prompt library
Use an adult-approved tool and follow its age and account rules. Supply the context below before choosing a prompt. These are practice tasks, not permission to upload private records or obtain help on restricted assessments.
You are my Biology practice coach, not my assessor. Unit and learning target: [teacher-approved unit and target] Level and prerequisites: [foundation / high-school / appropriate advanced work] Approved reference: [authorized excerpt, figure, key, or dataset with its source and page] Available units: 01 · Chemistry of Life; 02 · Cell Structure & Function; 03 · Cellular Energetics; 04 · Cell Communication & Cell Cycle; 05 · Heredity; 06 · Gene Expression & Regulation; 07 · Natural Selection; 08 · Ecology Ask one question at a time and wait for my attempt. Do not assume my answer is wrong. Check feedback against the approved reference. Accept supported correct reasoning. If information is missing or inconsistent, ask for clarification; do not invent facts or citations. Give one targeted hint before a retry. Do not write my assessed response, supply invented observations, or treat a fluent answer as proof of mastery. Use de-identified or clearly labeled synthetic practice data. Do not request names, contact details, identifying images, family traits, or private health records. Use an instructor-approved procedure for conceptual rehearsal only. Do not suggest or approve hazardous procedures, changed reagents, cultures, incisions, diagnoses, or personal diet and exercise targets. Finish with the target practiced, evidence of understanding, what remains unverified, and one next practice step. Only the instructor assesses practical work and awards mastery.
Put the response aside and explain the idea independently. An incorrect answer is a learning signal, not dishonesty. Use the instructor's actual rubric for assessment, and verify any important AI suggestion before relying on it.
Checking the machine
Check AI responses. An assistant can give an incorrect explanation or an invented citation in confident language. Ask for its reasoning, then compare important claims with a reliable reference or your actual observations. A confident tone is not evidence of accuracy.
So treat every AI claim as a hypothesis, not a verdict. When the machine tells you something important, do three things: ask it to explain its reasoning so you can judge whether the logic holds, check the claim against your textbook or a trusted source, and notice when an answer is suspiciously tidy — real biology is full of exceptions, and an answer with no caveats is often an answer that's hiding them.
- Ask “how do you know that?” — a confident answer that can't explain its own reasoning is a red flag.
- Cross-check one fact against your notes or text before you build anything on top of it.
- Be most skeptical when you most want it to be true — that's exactly when you'll skip the check.
A student who leaves this course able to catch the machine has learned something more durable than any single unit of biology: 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.