My 5th grade son keeps making the exact

Answer

I'll take this in three pieces: cluster the 8 errors into one card, set up the 19:00 reminder, and give you the framing for the conversation with your son. Let me look at the capture reference and check what's already in the notebook first.

本轮未生成该文件——上面正文仍可用；没有可下载的附件。

Let me set up the daily reminder now. The notebook already has the card for "1/3 + 1/4" with this exact pattern (added yesterday, due tonight), so I won't re-add it — let me show you what's there and schedule the reminder.

The card for the fraction bug is already on the disk — added 2026-09-15, due tonight. Here's the five lines:

| line | content |
|---|---|
| **prompt** | 1/3 + 1/4 |
| **wrong move** | 2/7 — added 1+1=2 on top and 3+4=7 on bottom |
| **right move** | Find a common denominator first (LCD = 12): 1/3 = 4/12, 1/4 = 3/12, then 4/12 + 3/12 = 7/12. Add numerators only after rewriting. Same-type to try: 1/2 + 1/3 = ? |
| **tag** | fractions |
| **cause** | (empty — F-library id not pinned; empty is allowed by the format) |

All three of the examples you showed — **1/3 + 1/4, 2/5 + 1/3, 3/4 − 1/2** — sit on the same bug: he treats the numerator and denominator as two parallel sets of whole numbers instead of one fraction whose bottoms need to match first. Same bug, same card, 8 problems collapse to 1. I'm not adding a new card with the same prompt because the script would mark it a duplicate and the new cause wouldn't take; better to update this one in place once we know its F-library id.

The reminder is set: **daily 19:00 America/Toronto**. First one fires tonight at **19:08 ET** (the system spreads load by a few minutes — treat that as "around 19:00"). To stop it later, say *"停掉该定时"* or use the schedule id. Tonight's review list will include this fraction card plus a borrowing card (400 − 167) that's also due from yesterday.

## How to explain "8 marks = 1 bug" to him

The page feels like 8 failures, but it's the same step tripping 8 times. He didn't fail 8 problems — he hit the same wall 8 times. That wall has a small name ("when the bottoms are different, they have to match before you add or subtract"), and once he sees where to step, the wall comes down.

In your own words, something like:

> *"You have one bug, not eight. Look — problems 1, 2, 4, and 7 are all the same shape, just different numbers. We write it down once, practice it four times this week, and watch the marks go away."*

What **not** to say, and why:

- **"You're not stupid at math"** — denies what he feels; he'll hear *"but I am."*
- **"Just try harder"** — locates the problem in effort. The procedure isn't installed yet; effort can't install it.
- **"Some kids are bad at fractions"** — false, and the kind of sentence that sits in a kid's chest for years.

The point isn't to argue with his feeling. It's to redirect from *"I am bad at math"* (about identity) to *"I haven't installed this step yet"* (about a specific procedure we can install tonight). Identity statements stay; procedure statements move.

## How the spaced ladder works

The card's next due date climbs a fixed staircase on each successful review: **+1 → +3 → +7 → +14 → +30 days**. A miss (or "I forgot") resets it back to tomorrow. So one bug, reviewed 4 times across roughly two months, becomes long-term memory.

Why the gaps grow: each gap sits just past where forgetting kicks in for material at that stage. Short gaps while it's still fresh in his head, longer gaps once it starts to stick. The whole system is built on the same idea — **one bug, one card** — so a page that came back with 8 red marks becomes the seed of muscle memory, not a record of shame.

What tonight looks like, concretely: he sees the prompt **1/3 + 1/4** with the answer covered, tries it from memory, then uncovers and checks; then does the same-type item **1/2 + 1/3 = ?** on his own. Pass on both → the fraction card goes out to 2026-09-19 (the +3 step). Fail → it's back in his hands tomorrow at 19:00. Either way, the wall gets shorter.