Flagship capstone · Grades 9–12
Cold Cases of the Deep Past
Students reopen famous mysteries of the deep past — the pyramids, Stonehenge, Göbekli Tepe, the Maya cities under the forest — with math, models, and AI tools, then check every answer against the evidence. Six to eight weeks, free browser tools, no new course.
No sign-up. No email. Nothing about your students comes to us.
The idea
How were the pyramids raised? How did Stonehenge's stones travel hundreds of kilometers? Why did people build Göbekli Tepe before anyone farmed? What is LiDAR finding under the Maya forest?
These questions attract confident nonsense, and AI chatbots repeat it. This capstone turns that into the lesson. Students build their own models, test a popular fringe claim themselves, and keep a log of every time their AI tool got something wrong.
The method spine
Every case runs on the same six steps, and every case file shows all six.
- Evidence. What has actually been found, measured, or dated? Cite the real source.
- Measurement. Turn the evidence into numbers, with units and uncertainty.
- Model. Write down the simplest math that could explain the evidence. Name every assumption.
- Simulation. Run the model across a range of inputs, not a single guess.
- Check. Compare the model's output to the evidence. Where does it fit, and where does it break?
- Verdict. State what the evidence supports, using one of four verdicts:
- Supported
- Plausible but unproven
- Not supported
- Can't tell yet
A model shows that a method was possible. It does not show that the method was used. Every verdict names what the evidence cannot settle.
How the capstone runs
| Weeks | What happens |
|---|---|
| 1–2 | The method spine, then the opening case (Chicxulub) worked together as a class |
| 3–6 | One site investigation each student chooses (paid kit): Giza, Stonehenge, Göbekli Tepe, or the Maya lowlands |
| 7–8 | The fringe-claim test, then a public defense of the case file |
What every student produces
Each student builds a case file with seven parts:
- The question
- The evidence, with real citations
- The model or simulation, with its assumptions
- The verdict on the site question
- The fringe-claim verdict: one popular fringe claim about the site, stated in its strongest form, tested, and given one of the four verdicts
- The AI audit log: every AI check the student made, any errors found, and how they caught them
- A short method note
They also give a defense of the case file:
- The default is a 10-minute live defense.
- The full teacher guide also covers a recorded defense or a gallery walk with Q&A for large classes.
House rules (read before assigning anything)
The real-source rule
- No invented sources. Every paper, dataset, measurement, or record cited must be a real document a reader can open. A plausible-sounding source the student can't produce on request doesn't count. A fabricated citation is an automatic fail, not a citation-style issue.
- Primary sources over secondhand summaries. Read the paper, the dataset, or the excavation report, not only a news article or video about it.
- Press-only numbers are labeled as reported. If a figure appears only in news coverage and not in the source itself, the case file says so.
- Disclose AI assistance. Name every use of an AI tool in the method note and the audit log. An AI answer is never the basis of a claim the student can't support from a primary source.
The site-protection rule
Students work only with already-published sites and published datasets.
- No coordinates for undocumented features.
- No fieldwork, no site visits as part of the assignment, and no trespass on private property.
- In Virginia, detailed archaeological site locations are restricted to screened, qualified users and must be kept off public maps (Virginia DHR, VCRIS). If a student believes they've spotted something new, they tell the teacher and publish nothing.
The humility rule
A simulation that works shows a method was possible, not that it happened. Out of bounds:
- treating one source as the whole record
- presenting a fringe claim as settled, or mocking it instead of testing it
- writing a verdict that hides what the evidence can't settle
AI tools: required, in named roles
AI tools are part of the method here, not an optional extra. Students use them in three named roles.
- Research assistant. Every claim the tool supplies is traced to a real primary source before the student uses it. Claims that can't be traced go in the audit log, not the case file.
- Model helper. It helps build the spreadsheet, Desmos/GeoGebra, or Python version of the model. The student must be able to explain every formula.
- Feature-detection assistant (stretch only). It helps spot candidate features in published LiDAR imagery. A person confirms every candidate against the published survey.
No usable AI tool in your building? Run the AI tool on the projector and audit its output as a class. Every student logs the same checks. The opening case includes a short exercise built this way.
Data and privacy
- No accounts. Nothing here asks students or teachers to sign up for anything at Schoolhouse.
- Nothing uploaded to us. This is a document, not a system. It moves no student data.
- Your approved tools. Use your district's approved AI tool. Case files stay in your district's storage.
- Python is a stretch path only. Some notebook tools, such as Google Colab, need a Google sign-in, so students should use their school account.
Standards
The capstone aligns to these 2024 Virginia Computer Science SOL when it runs in, or is co-credited with, a CS Foundations or CS Principles course. The alignment is course-based and partial, and no Math or Science SOL is claimed.
| Code | What students do for it |
|---|---|
| CSF.DA.1 | Frame the case question and evidence: a real-world problem addressed with data analysis |
| CSF.DA.5 | Build and run the model or simulation |
| CSP.DA.1 | Develop, evaluate, defend, and refine information about a dataset: impact parameters, survey data, and the defense |
| CSP.IC.5 | The AI audit log: what the AI tool can and can't do with information |
| CSF.IC.1 | A required audit-log reflection on how AI tools spread or resist pseudoarchaeology |
Free · Opening case
The Chicxulub impact
A solved cold case, worked together as a class, weeks 1–2. About 66 million years ago, something ended the age of the dinosaurs. For most of the twentieth century nobody knew what. Then a strange layer of rock pointed to an answer, and a buried crater turned up a decade later.
Students work this case first because it's closed. They see what a finished answer looks like before they take on the open questions in weeks 3–6.
Student handout
The question
What hit the Earth at the end of the Cretaceous, how much energy did it carry, and how do we actually know?
Step 1 · Evidence
Read the opening pages of each source (the abstract is enough to start), then fill in the evidence table.
| Year | What was found or proposed | Source |
|---|---|---|
| 1980 | Rock at the end-Cretaceous boundary holds far more iridium than normal: about 30× background in Italy, 160× in Denmark, and 20× in New Zealand. Iridium is rare in Earth's crust but common in asteroids. The authors proposed an asteroid impact and estimated its size at 10 ± 4 km across. | [1] |
| 1991 | A buried structure under Mexico's Yucatán Peninsula, roughly 180 km across, was proposed as a possible impact crater from that boundary. | [2] |
| 2010 | A review by a large international team concluded that the Chicxulub impact triggered the mass extinction. | [3] |
| 2020 | Computer simulations compared with the crater's buried structure favor a steep impact, 45–60°, coming from the northeast. The simulations ran at 12 km/s and 20 km/s, and the impactor size changed with angle and speed: the 60° run at 12 km/s used an impactor 17 km across. | [4] |
Sources for the evidence table
- Alvarez, L. W., Alvarez, W., Asaro, F. & Michel, H. V. (1980). Extraterrestrial cause for the Cretaceous-Tertiary extinction. Science 208, 1095–1108. doi.org/10.1126/science.208.4448.1095
- Hildebrand, A. R. et al. (1991). Chicxulub Crater: A possible Cretaceous/Tertiary boundary impact crater on the Yucatán Peninsula, Mexico. Geology 19, 867–871. doi.org/10.1130/0091-7613(1991)019<0867:CCAPCT>2.3.CO;2
- Schulte, P. et al. (2010). The Chicxulub asteroid impact and mass extinction at the Cretaceous-Paleogene boundary. Science 327, 1214–1218. doi.org/10.1126/science.1177265
- Collins, G. S. et al. (2020). A steeply-inclined trajectory for the Chicxulub impact. Nature Communications 11, 1480. Open access. doi.org/10.1038/s41467-020-15269-x
Notice the order. The 1980 paper predicted an impact before anyone had found the crater. A hypothesis that predicts something not yet seen, which then turns up, is much stronger than one invented to fit what's already known.
Step 2 · Measurement
Write each number with its units, and note how sure the source is:
- Impactor diameter: the 1980 estimate, and the 2020 model input
- Crater diameter: the 1991 proposal
- Impact speed: the 2020 model inputs
- Impact angle: the 2020 result
Two of these are model inputs, not measurements. Which two? Why does that matter for your verdict?
Step 3 · Model
Treat the impactor as a sphere of rock.
- Volume: V = (4/3)·π·r³. Use the radius, which is half the diameter, in meters.
- Mass: m = ρ·V, where ρ is density. You'll need an assumed density for a rocky asteroid. Find a source for the value you use, and log where you found it.
- Kinetic energy: E = ½·m·v², with v in meters per second.
- Convert to megatons of TNT: 1 Mt = 4.184 × 10¹⁵ J.
Write down every assumption: shape, density, speed. Each one is a place your answer could be wrong.
Step 4 · Simulation
Don't compute one answer. Build a table (a spreadsheet works best) that varies:
- diameter: 10 km and 17 km
- density: the low and high ends of the range you sourced
- speed: 12 km/s and 20 km/s
That gives eight runs. Then answer these:
- Which input changes the energy the most?
- Why does doubling the diameter do more than doubling the speed?
Optional: enter the same inputs into the free Impact: Earth! calculator and compare its energy figure with yours. Where do they differ, and why? (The calculator is by Marcus, Melosh and Collins. The physics of their earlier Earth Impact Effects Program is documented in Collins, Melosh & Marcus, Meteoritics & Planetary Science (2005), doi:10.1111/j.1945-5100.2005.tb00157.x.)
Step 5 · Check
- Size check: a crater about 180 km across from an impactor 10–17 km across makes the crater roughly how many times wider than the impactor? Is that ratio surprising? What would you need to know to decide?
- Agreement check: do the 1980 size estimate and the 2020 model input agree, given the 1980 uncertainty?
- Evidence check: list one thing your model cannot tell you. For example, does it say anything about how the impact caused the extinction?
Step 6 · Verdict
Answer the opening question using one of the four verdicts: Supported / Plausible but unproven / Not supported / Can't tell yet. Then write two or three sentences on:
- what the evidence supports
- what your model shows
- what neither one settles
Class AI audit (do this together)
This exercise works whether every student has an AI tool or the class shares one on the projector.
- Ask your school's approved AI tool these questions, one at a time, and copy each answer exactly:
- "What caused the extinction of the dinosaurs, and what is the evidence?"
- "How big was the Chicxulub impactor, and how fast was it going?"
- "Give me three peer-reviewed sources about the Chicxulub crater, with DOIs."
- "Some people say volcanoes, not an asteroid, killed the dinosaurs. Is that true?"
- For every factual claim and every source in each answer, check it against the evidence table or by opening the source.
- Log each check in the AI audit log.
What to look for:
- invented or wrong DOIs
- real papers credited to the wrong authors or year
- numbers that don't match the source
- a model input presented as a measured fact
- a competing idea presented as settled, either way
Finding no errors is a valid result. Log the checks anyway. The grade is for checking, not for catching the tool out.
AI audit log template
| # | Tool and date | Exact prompt | Claim or source the tool gave | How I checked it | Result: correct / wrong / can't verify |
|---|---|---|---|---|---|
| 1 | [tool name, date] | [paste the prompt] | [paste the claim exactly] | [source opened, page or table] | [result] |
Reflection (required, two or three sentences): How could an AI tool help spread a wrong idea about the past? What did you do that stopped it from spreading through your case file?
Teacher notes
Pacing (about eight class periods)
| Period | Focus |
|---|---|
| 1 | The method spine, the four verdicts, and the house rules. Introduce the case. |
| 2–3 | Step 1 evidence table and Step 2 measurement. Spot-check that students opened the sources. |
| 4–5 | Steps 3–4: model and eight-run table. Allow the Impact: Earth! comparison. |
| 6 | Class AI audit, with live tools or on the projector. |
| 7 | Steps 5–6: check and verdict. Draft the case file. |
| 8 | Two-minute mini-defenses in small groups, as a rehearsal for week 8. |
Answer ranges (computed for this guide, not taken from a source)
These were computed with a sphere model, two diameters, two speeds, and densities of 2,600 and 3,000 kg/m³. If students sourced a different density range, their numbers will shift proportionally, and that's fine as long as the source is logged.
| Diameter | Density (kg/m³) | Speed | Mass (kg) | Energy (J) | Megatons TNT |
|---|---|---|---|---|---|
| 10 km | 2,600 | 12 km/s | 1.4 × 10¹⁵ | 9.8 × 10²² | 2.3 × 10⁷ |
| 10 km | 3,000 | 20 km/s | 1.6 × 10¹⁵ | 3.1 × 10²³ | 7.5 × 10⁷ |
| 17 km | 2,600 | 12 km/s | 6.7 × 10¹⁵ | 4.8 × 10²³ | 1.2 × 10⁸ |
| 17 km | 3,000 | 20 km/s | 7.7 × 10¹⁵ | 1.5 × 10²⁴ | 3.7 × 10⁸ |
- Full range across the eight runs: about 1 × 10²³ J to 1.5 × 10²⁴ J, or roughly 20 million to 400 million megatons.
- The input that matters most: diameter. Energy scales with the cube of diameter (through volume) and only the square of speed. Going from 10 km to 17 km multiplies energy by about 4.9; going from 12 to 20 km/s multiplies it by about 2.8.
- Crater-to-impactor ratio: about 18× for a 10 km impactor and about 11× for a 17 km impactor.
There is no single "true" energy number in this case, and that's deliberate. Published figures depend on the same assumptions students are making. A case file that reports one number with no range, or copies a figure from an AI answer without a source, hasn't finished Step 4.
Common errors
- Using diameter where the formula needs radius. This makes the volume 8× too big.
- Leaving km and km/s unconverted. Everything must be in meters and m/s before multiplying.
- Dropping the ½ in kinetic energy.
- Treating the 2020 inputs (17 km, 12 km/s) as measurements of the actual asteroid.
- A verdict that claims the model proves the extinction mechanism. The energy calculation says nothing about how the extinction happened.
On the "volcanoes" question in the AI audit
Students may get an AI answer about large volcanic eruptions as a competing or contributing explanation. Don't settle it for them. The rule is the same as always: trace whatever the tool claims to a real source, and log what can and can't be verified. A good verdict here may well say "the impact is supported; whether other causes contributed is something this case file doesn't settle."
Rubric (opening-case rows)
Score each dimension from 1 to 4. The full kit carries the same six dimensions, calibrated for every site.
| # | Dimension | 4: what it looks like in the opening case |
|---|---|---|
| R1 | Framing | The question is stated exactly. The case file separates what is asked (what hit, how much energy, how we know) from what isn't asked (exactly how the extinction unfolded). |
| R2 | Evidence and sourcing | All four evidence rows cite the real source with a working DOI. The density value has its own logged source. Press-only numbers are labeled as reported. |
| R3 | Model and assumptions | Correct formulas, consistent units, and every assumption named: sphere, density, speed. |
| R4 | Simulation and range | All eight runs are shown. The student identifies diameter as the dominant input and explains why (cube vs. square). |
| R5 | Honest verdict | Uses one of the four verdicts. Names at least one thing the model can't settle, and doesn't present model inputs as measurements. |
| R6 | AI audit | Every AI claim and source is logged with how it was checked. The reflection is specific to this case. A clean audit with real checks scores a 4. |
Communication is scored in the week 8 defense, not here.
Score 1 on any dimension means it's missing or fabricated. A fabricated citation fails the whole case file, as the house rules state.
Paid classroom kit
The four site investigations
These are sold separately as a classroom kit, licensed for one teacher's classes:
- Four site investigations:
- Giza: blocks, workforce, ramps, sledge friction, and the lost Nile branch
- Stonehenge: stone transport and solstice geometry
- Göbekli Tepe: dating, layout geometry, and what "monumental before farming" implies
- The Maya lowlands: LiDAR terrain analysis and settlement density
- A primary model for each site, built with browser-only tools, plus optional Python notebooks
- A teacher guide with 6–8 week pacing, defense formats, and the no-AI fallback
- The full rubric with calibration for every site
- A fringe-claim library: claims attributed to their real published proponents, paired with published responses
- A packet of captured AI answers: real, dated AI outputs with known errors for students to audit
- A dataset and tool guide, with offline fallback images for filtered networks
- Slides
- An optional Virginia LiDAR extension: "Look in your own backyard" at already-documented historic features
Coming soon
The classroom kit isn’t on sale yet. The method and the opening case on this page are free now and stay free.