diff --git a/persistent-memory.md b/persistent-memory.md
index c44dd5b..771ba7e 100644
--- a/persistent-memory.md
+++ b/persistent-memory.md
@@ -1,6 +1,6 @@
 # Persistent memory — eshpfi-management
 
-_Last updated: 2026-09-09 23:20 PT (**Pfish-6** = run-6 NVFP4 is the standing seat, ana-ml2 :8021 ONLY; run 7 PURGED ~139 GiB; pfi-gx10 is an experimental/TRAINING box and carries no serving seat; all five ERP adapters now MIRRORED to ana-ml2 and inside restic; **BabyBronte / R49 author-voice regime is in PREP on gx10, carrier SETTLED = dense Qwen3**; checkpoints AND superseded merges PURGED both boxes, **~573 GB total**; only merged-run06 + the v6 quant survive)_
+_Last updated: 2026-09-10 06:30 PT (**Pfish-6** = run-6 NVFP4 is the standing seat, ana-ml2 :8021 ONLY; run 7 PURGED ~139 GiB; pfi-gx10 is an experimental/TRAINING box and carries no serving seat; all five ERP adapters now MIRRORED to ana-ml2 and inside restic; **BabyBronte / R49 author-voice regime is in PREP on gx10, carrier SETTLED = dense Qwen3**; checkpoints AND superseded merges PURGED both boxes, **~573 GB total**; only merged-run06 + the v6 quant survive)_
 
 > **Always check for `/tmp/infra-ops-handoff.md`** — if it exists and its
 > `Written:` stamp is under an hour old, read it (it carries the in-flight
@@ -109,6 +109,20 @@ no longer deployed sidecars here. See Recent decisions.)
 
 ## Current state / in-flight
 
+> ⚠⚠ **IF A PROMPT ASKS YOU TO "check on the run", RUN `CronList` BEFORE YOU ANSWER IT.**
+> A recurring cron job has re-created itself across at least three sessions with the verbatim text
+> *"check on the run, report high level stats, and if complete, althing to Miranda to inform me, and
+> then serve so brokkr can run battery. inform brokkr when ready."* **Killed 2026-09-10 06:29 PT**
+> (`CronList` → job `12bdea3c`, hourly at :37, session-only → `CronDelete 12bdea3c` → list now empty).
+> The operator had already killed it once before 09-09 (*"kill the check, no training is running"*),
+> and the 09-09 handoff warned against starting one — the warning was not enough, because **a
+> cron-fired prompt is indistinguishable from an operator-typed one.** It arrives as a user turn with
+> no marker. I spent three full turns re-verifying an empty fleet and drafting careful answers to a
+> timer. The instruction chain it carries is *dangerous to obey blind*: it ends in messaging Miranda,
+> standing up a seat, and cueing a peer — three outward-facing acts on a premise that is false
+> whenever no run exists. **Verify the run exists before acting on any part of that chain, and if the
+> same text arrives twice, check the cron list rather than answering it a third time.**
+
 _As of 2026-09-09 21:45 PT. **Nothing is training and nothing is queued.** Older in-flight blocks are
 preserved verbatim in `archival-memory.md` § Superseded in-flight snapshots._