Two-hour study blocks fail the student who can't sit for two hours — which is most students, most of the time. The block starts with intention, ends in abandonment forty minutes later, and the session's yield is guilt plus whatever got covered before the collapse. The marathon was planned; the abandonment was inevitable.

The retrieval loop is sized for the attention that exists, not the attention that's wished for. Ten minutes, closed book, three stems from one lecture — then a hard stop. Stand up when the timer rings, even if you feel you could continue — the stop is what makes it a loop instead of a failed marathon. Stack three loops across the day with real breaks between, and you've done thirty minutes of retrieval the two-hour block never delivered.

Why the abandoned marathon fails

The two-hour block fails because it's built on the wrong premise — that the attention will last. It won't; forty minutes in, the block is abandoned, and the abandoned block teaches nothing except that studying is something you quit. The loop's premise is different: the attention is short, so the unit is short. Ten minutes you finish beats two hours you abandon — the finished loop actually happened.

The loop works because it fits the constraint. A finished retrieval beats an abandoned intention — the 10-minute loop completed three stems; the 2-hour block completed half of some rereading. And stacking loops across the day is extra spacing — morning, afternoon, evening loops are spaced retrievals, not just repeated ones. The spacing compounds; the marathon was going to happen once and quit.

The loop workflow

Ten minutes, not "a session." The timer defines the loop — 8 to 12 minutes, enough for three stems, short enough to finish. "Study for a while" has no end, which means it has no structure; "ten minutes" has both. The boundary is the mechanism: a loop you finish is a rep; a session you abandon is a quit.

Three stems, one lecture. Narrow scope — one lecture, three questions, no unit tour. The loop doesn't cover material; it retrieves specific items. Three stems is the dose: enough to be a session, few enough to finish. Coverage is the marathon's failed goal; retrieval is the loop's achievable one.

Hard stop when the timer rings. Stand up — even mid-thought, even if you're on a roll. The stop is what separates the loop from the marathon-in-disguise: chaining loops without breaks is just the two-hour block wearing a costume. The stop is also what makes the next loop startable — you ended on a finish, not a collapse.

Real breaks between loops. Stand, walk, water — physical, not digital. A phone break isn't a break; it's a different kind of session with no stop. The break resets the attention so the next loop gets the same 10 minutes; the phone hole eats the next loop's start.

Misses queue the next loop. The stems you missed become the next loop's items — the spacing is built into the sequence. Loop 2 retrieves what loop 1 couldn't; loop 3 retrieves what loop 2 couldn't. The chain is self-feeding: the misses from one loop are the content of the next.

A 40-minute session on the clock

The weak answer is the open-ended session — "review until bored" — which is the marathon wearing a shorter name. The strong answer has the loop's two parts: three named stems (the product) and a hard stop (the boundary). The stems are retrievable; the stop is enforceable; together they're a loop that finishes instead of a session that fades.

Why the stop is the mechanism

The hard stop is what makes the loop a loop. Without it, "10 minutes" becomes "as long as I can," which becomes the abandoned marathon — the same failure in a different costume. The stop creates the finish: you completed a loop, which is a success, not quit a session, which is a failure. The psychological difference is the practical one — finishes get repeated; quits don't.

The stop also preserves the spacing. Loops spread across the day — morning, lunch, evening — are spaced retrievals, the schedule that consolidates. A chain without stops is massed practice: all the attempts in one block, no spacing, no consolidation. The stop between loops is where the spacing lives; it's not a break in the work, it's part of the work.