The water cycle in a jar

An illustrative example made with a simulated family — not a real family's record. A way, never the way.

Guide: Carmen · Learner: Felix · Age band: 10–12 · Subject: Science

Where the learner was stuck

Felix, who is ten and working at about a grade five level, could reel off the words — evaporation, condensation, precipitation — and label a diagram with arrows. But asked what the water was actually doing, or why a cloud forms at all, he went quiet. The words sat on top of nothing. He could match the term to the picture in a workbook and still believe, when pressed, that the water in a puddle simply "disappears." The vocabulary had been learned as a list to return on a test, not as a description of something real happening to real water.

The approach (built through what they love)

Felix loves watching things change state — ice going to water, water going to steam on the stove. So instead of starting from the words, the session starts from a change he can watch for himself. A sealed jar with a little warm water and a lid goes on a sunny windowsill. Over an hour, water climbs the inside of the glass as vapour, beads on the lid, and runs back down. That is the whole cycle, small enough to hold. Only after Felix has watched it and described it in his own words does the session attach a term to each thing he saw: the water that left the pool is evaporation, the drops on the lid are condensation, the run-back-down is precipitation. The word lands on an event he has already witnessed, not the other way round.

For the guide: the shape of a session

Set the jar up together first, warm water and a tight lid, and put it where the sun hits. Then leave it and do something else — the waiting is part of it, and checking back every fifteen minutes keeps the attention fresh rather than forced. Carmen's job while they wait is to ask, not tell: "Where did the water on the lid come from? It was at the bottom a minute ago." Let Felix reason it out loud, even when the first answer is wrong, before naming anything. Keep a single printed page with the jar drawn on it and blank lines where the words will go, and fill them in only once Felix has described each step without the term. Stop while he is still curious — one clean run of the cycle understood beats three terms memorised.

What only a person can do

Carmen can hear the difference between Felix reciting "condensation" and Felix actually explaining that the vapour cooled against the glass and turned back to drops — the same word, two completely different states of understanding, and only a listener in the room can tell which one is happening. She can follow the unexpected question ("what if the jar were cold instead of warm?") into a second, better experiment, where a page would simply mark the first answer and move on. She can decide that today the jar is enough and the rain part waits for next time. And she can catch the moment the idea clicks — the look up from the glass — and let him teach it back to her while it is fresh.

Where the learner leads

Felix leads the watching. He decides how often to check the jar, he is the one who first notices the beads on the lid, and he narrates what is changing before any term is offered. When he gets to explain, unprompted, that the water "went up invisible and came back as drops," he is doing the real science — observing, describing, reasoning from what he saw — and the words are just labels for work he has already done. Carmen's part is to ask the question that makes him look again, and to name the thing once he has seen it. The learner supplies the understanding; the guide supplies the vocabulary that pins it down.

The game on the learner's side

The game is a build-the-cycle screen, one step at a time rather than a whole diagram at once. It shows the sunny pool and asks: the water is leaving — is it disappearing, moving as invisible vapour, or sinking into the ground? A wrong choice names the specific slip ("it feels like disappearing, but the water is still there — it is just spread out as vapour you cannot see") rather than just marking it wrong. The next screen shows vapour meeting the cool lid and asks what happens; the next, the drops growing heavy and falling. Three levels: level one labels the steps Felix just watched in the jar, level two asks him to predict what changes if the air is colder or the water warmer, level three runs the cycle outward from a jar to a cloud and back. It steps up after three right in a row and eases back after a miss, and every mistake it logs is a reasoning slip the guide can pick up next time — not a score.

When to seek an evaluation

Plenty of children can recite science vocabulary long before the ideas underneath settle, and the gap between the words and the understanding is ordinary at this age — it is exactly what hands-on work is for. But if, across many topics and many months, a learner keeps returning memorised words with nothing underneath them, cannot hold a two-step cause and effect ("this happened, which made that happen") even after watching it directly, or tires sharply from any task that asks him to explain rather than recall, it may be worth describing what you see to someone whose work is how young people learn. A family doctor or a learning specialist can observe and tell you what they notice. You do not need a label to ask, and what you learn is yours to use as you choose.

A way, never the way

A jar on a windowsill is one way into the water cycle, chosen because this learner loves watching things change state. Another child would get there through a puddle measured on the driveway over three dry days, a kettle and a cold spoon, or a drawing that animates. The thing worth keeping is the order — watch the real change first, reason about it out loud, attach the word last — not the jar itself. Use what fits your learner and your week; leave the rest.

The learning record for this session

A Meta DAX session can close by writing one entry to a learning record — a single dated JSON object, readable by a person and a program, append-only, kept privately on the guide's machine and published only if the family ever chooses to. Here is the entry this simulated session would write, in the metadax-record v1 shape (nickname only, no real name, no location, behaviour never a diagnosis):

{
  "format": "metadax-record",
  "v": 1,
  "entry_id": "hs-sc52-s1",
  "package": {
    "ref": "HS-SC52",
    "session": 1,
    "title": "The Water Cycle in a Jar",
    "subject": "Science",
    "age_band": "10-12"
  },
  "date": "2026-10-09",
  "attempted": [
    { "game": "Build the Cycle", "answered": 9, "right": 6 }
  ],
  "reached": [
    { "game": "Build the Cycle", "level": 2, "of": 3 }
  ],
  "mistakes": [
    { "name": "said the water disappeared rather than turned to vapour", "count": 2 },
    { "name": "named the term correctly but could not say what was happening", "count": 1 }
  ],
  "learner_words": "Felix watched the lid for ages and then said: the water went up invisible and came back as drops, so it never actually left. He wanted to know what would happen if the jar were cold instead of warm.",
  "guide_note": "The hardest moment was before the jar fogged up, when Felix still thought the puddle water just vanishes. Waiting and asking where the lid drops came from worked better than telling him. The click came when he said it never actually left. Next time I would like to try his own question — a cold jar — and get to the rain part. What only I could do: I could hear the difference between him reciting the word and him actually explaining it, and we stopped while he was still curious.",
  "links": {
    "sample": "https://daxfoundation.org/metadax/samples/#science-water-cycle-jar",
    "package": "",
    "play": "https://daxfoundation.org/metadax/play/"
  },
  "generated_by": "metadax-homeschool skill"
}

The entry stays on the guide's machine by default. Keeping a record over time is what the learning-record template is for; producing one entry, as above, needs nothing but the session. A way, never the way.