Skill: write-lesson → write-video-script, write-mcqs, vault-sync @ 2ea2930
James's notes on Topic 25 — triage (30 September 2026)
Source: reviews/james/NOTES_G3T25_2026-09-30.md (one note, on the summary script, from the skim page) and his chat ruling of ~16:30 (reviews/james/RULINGS_2026-09-30.md). None of Topic 25's videos exists, so every change is a wording edit in the content module.
In plain words
The topic no longer says "harm". Dangerous weather causes damage: it brings flood water, strong wind, lightning or deep snow, and each kind does its own damage. A defense is something people build so that dangerous weather does less damage, and it works when it holds back what is coming (strong wind is coming; a levee holds back flood water, not wind). L01's script closes "So, here's what we've seen." and L02's "Here's the pattern. Nobody can stop the weather…", in his words.
The table
| his note (verbatim) | action | where |
|---|---|---|
| "here's the rule isn't the best usage for lessons 1 and 2, I think lesson 2 would be better to say, 'Here's the pattern. Nobody can stop the weather.' Lesson 1: 'Here's what we've seen.'" | applied: L01 rule beat → "So, here's what we've seen. Dangerous weather causes damage: it brings flood water, strong wind, lightning or deep snow. Each kind of dangerous weather does its own damage."; L02 rule beat → "Here's the pattern. Nobody can stop the weather, but a defense can hold back what it brings."; L03 (not named by him) → "So, the best explanation is the one that fits everything you observed…" under the same ruling | content/G3T25_lessons.py scripts L01, L02, L03 |
| "Also, 'harm' is a weird thing to say. It would just be better to say 'dangerous weather does damage' or 'causes damage' would be the best thing to say there." | applied throughout the topic: lexicon lines 1–4; L01 rule ("Dangerous weather causes damage: it brings flood water, strong wind, lightning or deep snow. Each kind of dangerous weather does its own damage."); L02 rule ("Nobody can stop the weather, but a defense can hold back what it brings. A defense works when it holds back what is coming."); the term "defense" = "something people build so that dangerous weather does less damage"; L02's title → "A defense holds back what the weather brings"; every item stem, option, fb and why that said "harm" (L01 ×13, L02 ×14, L03 ×1, practice ×9, PP100 ×8) — "Which harm does it bring?" → "What does it bring?", "Type the harm a levee holds back" → "Type what a levee holds back", "The harm coming is strong wind" → "Strong wind is coming"; the recognition item's distractor "a harm" → "a flood"; the summary's four rule beats; the blurb; the hazard table's middle column "The harm it brings" → "What it brings"; both rule cards' text, alt and briefs; the figure key harm_pr_roof → wind_pr_roof; the option list HARMS3 → BRINGS3 | content/G3T25.py, content/G3T25_lessons.py, content/figures.py |
| (S36 readability line, James's Topic 27 principle) PP-5 "the creek behind a school in Iowa" | applied: "the river behind a school in Iowa" (the scene stays a school, not L02's river town) | content/G3T25.py PP-5 |
Judgements
- "hold back what it brings" / "holds back what is coming" is the plainest true replacement for the hazard noun: a sandbag wall holds back the water, shutters the wind; "hold back the damage" would be figurative. The word "damage" sits where James put it — dangerous weather causes damage; a defense means less damage.
- The items keep their moves and keys; only the noun changed. Two-option and three-option key strings are unchanged (no reorder), so no recount was needed.
- Grep for the old word:
grep -i harm content/*.py→ only the comments that record the ruling. Records underrecords/(BUILD_RECORD, REVIEW, TYPES, FIGURES) keep their historical "harm" wording; the TYPES sheet's exemplar text is superseded by the module. - Checker: 0 FAIL. L01's script was 152 words after the longer opener and is 150 after two trims ("the river's high"; "when it thunders"); L02 149; L03 146.