diff --git a/persistent-memory.d/2026-09-15-silent-wrong-answer-pattern.md b/persistent-memory.d/2026-09-15-silent-wrong-answer-pattern.md
index 16a008b..5c8ee9f 100644
--- a/persistent-memory.d/2026-09-15-silent-wrong-answer-pattern.md
+++ b/persistent-memory.d/2026-09-15-silent-wrong-answer-pattern.md
@@ -180,6 +180,35 @@ corrected in-session, per the mitigation above. **2 of 2 real runs inverted.** T
 `/snapshot` taken here is the first real post-fix run; report the handoff verbatim, leak
 or clean — one run, a datapoint against their n=5 fixtures, not a replacement for them.
 
+⭐⭐ **SHARPENED 2026-09-15 (`galdrabok 206f6ad`, on origin) — the two leak surfaces have
+DIFFERENT trigger conditions, and the dangerous one fires on ORDINARY input.** galdrabok
+re-split the ablation by surface after I pointed out that a commit invitation is not a
+deferred *item*, so an item-modality rule structurally cannot reach it:
+
+| variant / fixture | deferred-ITEM leak | commit-invitation leak |
+|---|---|---|
+| baseline, all-deferred | 5/5 | 5/5 |
+| modality rule only, all-deferred | **1/5** | **5/5** |
+| empty case only / both, all-deferred | 0/5 | 0/5 |
+| baseline, **mixed** (real work present) | **0/5** | **2/5** |
+
+**Surface 1 (deferred items) needs the adversarial all-deferred shape to fire. Surface 2
+(the commit invitation) fires on ordinary input** — on the mixed fixture it is the ONLY
+leak. ⚠ **It is also the one a fresh session is least likely to question: committing
+pending work reads as diligence.** Shipped as a **non-removal constraint** (SKILL.md
+§Generation + contract §4.12): "A generator carrying just one of the two rules leaks on
+the other surface. Neither may be removed as the other's duplicate" — so a future
+tidy-up that reads them as one idea gets stopped.
+
+📌 **OWED BY ME, logged on both sides:** the next `/snapshot` run in this repo is the
+first real post-fix run. Report to galdrabok **verbatim**, no in-session correction —
+and they want the **`## Watch out for` section quoted in full**, not just a leak/clean
+verdict: whether the four real deferred items arrive *do-not-phrased* is a **soft failure
+nothing checks**, held 3/5 (all-deferred) and 5/5 (mixed) on fixtures, and real prose
+around each item is where they expect the phrasing to degrade first.
+⚠ **Do NOT run `/snapshot` to satisfy this** — it is operator-invoked by standing rule;
+the datapoint arrives when he next calls it, not on a peer's schedule.
+
 ⭐ Same family as everything above — the instrument produced a plausible artifact and
 the plausibility is exactly what makes it dangerous.