diff --git a/docs/REVIEW_LOG.md b/docs/REVIEW_LOG.md
index 67c98e7..8397643 100644
--- a/docs/REVIEW_LOG.md
+++ b/docs/REVIEW_LOG.md
@@ -4708,3 +4708,59 @@ posting produced STR 17.
 Worth recording as a probe error rather than a defect: my first check compared the two
 sets with `JSON.stringify` and reported a mismatch. Every value was identical — the key
 order was not. The rule was right and the comparison was wrong.
+
+## PAPER MARGIN — a doctor, eleven months in
+
+A farm at the end of a private road in Angus. A person is in two places and both are
+attending work; the town has explained it as twins for eleven days. The team: **Dr
+Anwen Pryce**, probationary, recruited from A&E — and two career officers, a
+Containment Officer and a Pursuit Officer.
+
+The generator handed this case its own best argument for trades. The truth page reads
+*there is no original left; both are copies, and one of them knows*, and it closes by
+one of them being taken into custody. **Telling two identical people apart is a medical
+question**, and on that team Medicine reads 42, 1 and 1.
+
+**The two halves showed up immediately, in both directions.**
+
+*The doctor was the only one who knew what she was looking at.* Anomaly Lore: Pryce 37,
+Kobe 0, Halloran 0. Tradecraft: 31, 5, 5. The career officers train neither, so the
+newest person on the team was the only one carrying the department's own vocabulary —
+which is induction working exactly as intended and reads as true at a table.
+
+*And she was hopeless at the part that closes cases.* Her Persuade is **23**. Offered
+the duplicate the truth, rolled 95, and it read her on 37 against Insight 60. She could
+crack the case and could not talk anyone through it.
+
+**The scene the whole design was for.** The physical examination failed by three — of
+course it did, they are identical — and the bloods came back **critical on 02**. Both
+samples are the same sample. Not twins, not an original and a copy: the same person,
+twice. Neither career officer could have found it and neither would have thought to look.
+
+**R-226 fired, correctly and visibly.** Pryce trained Tradecraft 31; Halloran trained
+Navigate 34. The phase lead went to Navigate — *Tradecraft first, but not when it is
+plainly worse* — and Halloran led all four phases, all four succeeding, with Containment
+producing a special on 06.
+
+**And the shield issued two commits ago turned up unprompted.** Kobe is Containment, so
+she now draws a riot shield; it was slung, she raised it, and went from 7 everywhere to
+10 on torso and arms. The duplicate never touched her. It also never touched anybody —
+three shots, 77, 57, 95 — while Kobe's rifle put 5 through its chest and then 12 into
+its **bare right leg**, because armour coverage applies to the opposition too.
+
+The costs were paid as written: *meeting it costs 2 Coherence, killing it costs 3.*
+Everyone dropped to 8; Kobe, who shot her own duplicate, ended **Loose at 5** and −5%
+to Communication.
+
+The parish had wanted a body back for years and now there was one that would bury.
+Making it into something a family could be given is a doctor's job, and she rolled
+**42 against 42** — a success by nothing at all.
+
+### One probe error, worth recording
+
+`endOfCase` returned an empty array and I nearly wrote it up as a regression of R-210.
+It was not. `skillRoll` ticks experience only when told *which skill* was used, and my
+ad-hoc rolls passed a rating and a category but no `skillFamilyId` — the same omission
+R-222 found in `resolveLegDialog`, reproduced by hand in a test harness. Re-rolled with
+the skill named, the tick appeared and the improvement roll landed: **Medicine 56 vs
+42% → +6 → 48%.** The rule was right; the probe was not naming its skill.