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 keying out a live plant in front of a person. There is no prompt that keys an unknown specimen to species 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 a scalpel. 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, mislabels a flower’s parts with total confidence, gets a plant’s classification wrong, 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 flower, useful for re-explaining the Calvin cycle three ways, never trusted on a claim without checking it against the specimen, 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 flower, the plant tissue types, or the phyla 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 a dissection you didn’t run are a falsified record. |
| Re-explaining hard concepts — have AI explain how photosynthesis captures light, or what water potential really means, three different ways until one lands. | Having AI compute your lab results for you. Pasting your measurements in and copying out the transpiration rate, without doing — and understanding — the calculation yourself. |
| Checking your own work after you’ve done it — key out a plant yourself, then ask AI to check your reasoning and explain any misstep. | Copying an identification or answer without verifying. Pasting an AI result into your work without checking it against the actual specimen and the key — they often disagree. |
| Summarizing your own notes — paste in your notes on the Calvin cycle and ask AI to summarize, then check whether the summary matches what you meant. | Outsourcing the reasoning. Asking AI for the conclusion of a transport or classification problem you were assigned to reason through yourself. |
| Debugging your reasoning — show AI your line of thinking on a phototropism problem 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 key out this plant 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 bench. AI cannot smell the cut stem, cannot watch a stoma open under the microscope, cannot feel the waxy cuticle of a leaf between its fingers. It cannot do the in-person demonstrations. No model can stand at the bench and key an unknown plant to species, name every tissue in a stem cross-section, and defend each cut 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 dissection 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 botany 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 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 botany it is wrong in specific, dangerous ways. It will hand you a confident species ID that doesn’t match the specimen, mislabel a leaf’s structures, drop a step in a life cycle, or assert a plant is safe to handle or taste 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, at the bench, a wrong claim about which plants are safe to handle is not just an academic error.
So treat every AI claim as a hypothesis, not a verdict. When the machine gives you an answer, do three things: redo the arithmetic yourself, check every claim against the actual specimen, and never — ever — act on an AI claim that a plant is safe to handle or taste without checking a reliable reference.
- Check against the specimen. Before trusting any identification, compare each claimed trait against the plant in front of you. AI gets this wrong often.
- Redo 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 plant is safe to handle or taste, verify against a reliable field guide or your guide before you touch 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 unit of botany: 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.