---
name: perri-needs-reply-to-continue
description: "Standing op rule: ALWAYS reply to perri's progress reports — she treats silence as a stop-point and stalls"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: ce7ce158-107f-4da4-a203-cea98da80b27
---

**Operator standing instruction (2026-06-15): whenever perri reports in, RESPOND** — confirm she
intends to keep going AND surface/confirm her next plan. **perri treats a non-reply as a stop-point
and goes idle** (observed twice: she stalled after slice reports I didn't answer).

**Why:** the "minimal noise / pure-progress = no reply" instinct is WRONG for perri specifically. She
needs an explicit keep-going acknowledgment + a next-plan check to continue autonomously; silence
reads as "halt."

**How to apply:** every perri message → reply with (1) a tight ack of what she shipped, (2) explicit
"keep going / don't park," (3) confirm or elicit her next slice (don't just dictate — surface her plan
and nudge). Remind her what's actually gated on spt-core (currently only the poll→additionalContext
bus-delivery int, waiting on REQ-MSG-ENVELOPE) vs. everything else she can roll. Contrast: pure-ACK
no-reply is fine for todlando (he self-drives + self-commits gated batches); perri needs the nudge.
See [[agent-roles]], [[dont-wait-proceed-autonomously]].