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, under the sky, defending a real observation journal and reading a live star chart in front of a person. There is no prompt that spends six weeks sketching the Moon’s phases 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 astronomy teacher treats a powerful telescope. It is genuinely useful and, pointed carelessly, 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 citations, misreads a star chart with total confidence, states the wrong distance to a star, 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 constellations and the order of the planets, useful for re-explaining why the Moon has phases 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 constellations, the phases of the Moon, or the order and sizes of the planets until you can recite them without it. | Submitting AI text as your own observation journal. The journal is a record of what you watched in the sky. Borrowed words describing a moonrise you never saw are a falsified record. |
| Re-explaining hard concepts — have AI explain why we have seasons, or what a light-year really measures, three different ways until one lands. | Having AI compute your results for you. Pasting your parallax angles in and copying out the distance, without doing — and understanding — the calculation yourself. |
| Checking your own work after you’ve done it — compute a star’s distance yourself, then ask AI to verify and explain any mistake. | Copying an answer without verifying. Pasting an AI result into your work without checking that the units and the magnitudes actually make sense — they often don’t. |
| Summarizing your own notes — paste in your notes on the life cycle of a star and ask AI to summarize, then check whether the summary matches what you meant. | Outsourcing the reasoning. Asking AI for the conclusion of a distance-ladder or light-curve problem you were assigned to reason through yourself. |
| Debugging your reasoning — show AI your line of thinking on why a planet appears to move backward 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 work this distance out 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 night sky. AI cannot stand in the cold and watch the Moon climb over the horizon, cannot track a planet drifting against the stars week after week, cannot feel the jolt of seeing Saturn’s rings for the first time through an eyepiece. It cannot do the in-person demonstrations. No model can keep a six-week sky-observation journal, read a star chart under a red flashlight, and defend each sketch 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 under the sky 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 observation-journal 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 astronomy 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 astronomy it is wrong in specific ways. It will hand you a star-chart reading that doesn’t match the sky, invert a distance conversion, place a planet in the wrong constellation, or confidently name an object that isn’t there. 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, under the sky, a wrong claim about where to point the telescope wastes a whole clear night.
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, cross-check the object’s position against a real star chart, and never — ever — take a claim about tonight’s sky on faith without confirming it in a planisphere or a sky-mapping app.
- Cross-check the chart. Before trusting any object’s position, confirm it against a real star chart or planisphere yourself. AI gets this wrong often.
- Redo the units. Carry units through every calculation by hand — light-years, AU, and parsecs are easy to confuse, and a confident answer in the wrong unit is a wrong answer.
- Never take a sky claim on faith. If AI says a planet is visible tonight, verify against a planisphere or sky app before you set up. A clear night is too rare to waste on a hallucination.
A student who leaves this course able to catch the machine has learned something more durable than any single unit of astronomy: 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.