diff --git a/persistent-memory.md b/persistent-memory.md
index 31932db..1dfd491 100644
--- a/persistent-memory.md
+++ b/persistent-memory.md
@@ -120,6 +120,19 @@ foundational agents the Bifrost store is NEVER attached (kind-guard) — context
 on physical per-collection boundary). That missing agent-axis looks LOAD-BEARING (channel-2's real fix), not just
 defense-in-depth. WT tracing write/query path; **rev 1.2 contract (ch1 + ch2 + agent-axis stamp) comes to ratatoskr
 for the enforcement read** (INV-368-9 blocks WT preflight until then).
+**SCRUB + REPRO (2026-07-18):** operator ruled a FULL memory scrub both sides (contamination noise, nothing
+worth keeping). Server-side (personal/b125): infra-ops wiping all agent chroma collections + shared promotion
+state. Ours: **Tier-3 memory.db scrubbed to 0 chunks, :8392 restarted born-empty, no backup** (operator direct
+go; new pid 3548269; affect plane untouched). Personal is ALREADY b125 (redeployed 20:35Z; /version 404 =
+b125 dropped the route, misled us). Current-code status: the fresh Lofn 'Vuong' chunks are the FEEDBACK LOOP
+(Lofn's own recitations re-extracted), NOT proven fresh mis-write; the original cross-agent mis-write ("I'm
+Saga, and you are Vuong" → lofn.chroma) is Jun-3 code, UNPROVEN on b125. **QUEUED (after BOTH scrubs confirmed):
+the marker repro** — drive ONE fresh Sindra session (combined :8392 bound), user introduces an absurd greppable
+marker ("my favorite mineral is rhodochrosite", NOT the name), idle a few min for extraction, report timestamps
+→ infra-ops greps lofn.chroma + our store. Marker in lofn.chroma = mis-write ALIVE on b125 (code fix); marker
+only in our store = channel 2 is just the feedback loop + agent-axis hardening. Post-scrub our #368 backfill is
+a NO-OP (born-conjunctive once the fix ships); contract keeps migration machinery for other consumers. DO NOT
+re-ask Lofn the name meanwhile (re-seeds the loop). Awaiting WT infra-ops server-side-scrub confirm to run it.
 
 **✅ Cross-session name-recall arc COMPLETE + SHIPPED (v0.20.11→v0.20.15, pushed).** person-prime `scan`
 verb + `mark_superseded` verb both shipped, deployed to :8392, and live-verified; **WT #364 closed
@@ -131,10 +144,10 @@ via mark_superseded, not just recency-evicted). Full arcs:
 buttons (hover-revealed; one delegated `#tw` handler + LAN-http clipboard fallback; Playwright-verified).
 Served from disk → browser refresh picks it up, no :8765 restart for UI edits.
 
-**Sindra READY for a test drive — PRISTINE BASELINE.** Tidied the live memory.db to **5 clean genuine
-facts** (name leads person-prime → she recalls the name turn-1); rollback checkpoint at
-`sindra-baseline/pristine-baseline.db` (+ `pre-tidy-*.db`), both gitignored. Restore: stop :8392, copy
-the baseline over `memory.db`, restart.
+**OBSOLETE — Sindra pristine baseline WIPED 2026-07-18.** The whole Tier-3 memory.db was scrubbed to 0
+chunks (operator full-scrub ruling for #368 — contamination noise, nothing worth keeping; no backup taken
+per direct order). The old `sindra-baseline/*.db` checkpoints predate the scrub and no longer reflect a
+"clean 5-fact" target — the store is now born-empty. Any future test drive starts from the born-fresh store.
 
 **Deferred/queued tasks (all NON-URGENT — tracked in Recent decisions):** (1) P06-driver **referential-
 frame A/B/C probe** (operator-ratified; waits on WT b122; read-shape + brokkr's scoring rubric captured →