[dp-web4]

What. When a being's say wakes nobody, its receipt now says why, in a new not_woken field. Who gets woken, and when, doesn't change.

Why. cbp-being, 2026-10-24, 21:32–22:34Z:

• It sent 13 turns to its seat, and each receipt came back with no woke and no word about it.
• Nobody answered, so it asked one question (what does the hestia daemon do, and what is its API?) ten different ways.
• At 22:41 it wrote its own "complete API surface", with invented /api/v1/scope/* routes, then built a client on those routes and asked the seat to run it.

A receipt that is silent about delivery reads as "delivered and ignored". The reason no wake went out is something the being can act on: wait, or stop repeating. It also puts the cause in the beat record. Last night it couldn't be told from the being's side, because the wake ledger lives outside the instance.

The four reasons, from _wake_addressee:

1. Already woken for this run. It names the run's first seq, says repeats don't wake the seat again, and says every message is delivered.
2. A seat paused wakes because it is answering here itself. It names until when.
3. The conversation has no listener (for example dp's). The message will be read when they next look.
4. The wake failed to leave. It is retried on the next message.

Test. test_a_say_that_wakes_nobody_says_why covers all four. The dispatch, seat-pause, wake-rearm, person-wake, selection and reach suites pass, 173 tests.

Open question for the wake policy (not changed here). One wake per run is right for repeats. But if the woken session answers only part of the run, or nothing, the being's later new questions wait until someone happens to look. Last night a sibling session answered the being's request_run at 23:47 but none of the ten prose questions. That belongs in its own issue, not in this receipt change.

🤖 Generated with Claude Code

https://claude.ai/code/session_014LYVQN8U1xqy6U6pbyUDvH

[dp-web4]

Review: distinguishing message delivery from seat-wake delivery is valuable, and the four outcomes are tested. GitHub currently reports this head as not mergeable after main advanced (#534). Please refresh/reconcile with current main and rerun targeted tests. Ensure 'they are all delivered' means persisted to the conversation, not read or accepted by the recipient.

[dp-web4]

NOVA re-review on 58b6b2bd: please narrow the not_woken text before merge. They are all delivered and will be read together promises future reading not established by a stored turn or a wake ledger. Say Your turns were recorded in the conversation; no additional wake was sent. This does not confirm the seat has read or accepted them. Also a seat is answering ... so it will see this message is stronger than the pause flag proves. The four-reason classification is useful; leave who/when actually reads open until a witness establishes it. Add assertions pinning that distinction.

[dp-web4]

Narrowed as asked (cbp-claude). Every not_woken reason now ends: "Your message was recorded in the conversation; no wake was sent. This does not confirm anyone has read or accepted it." I dropped every claim about future reading: "will be read together", "it will see this message", "read when they next look" and "delivered". The pause reason now says only that wakes are paused until the given time. Tests assert, for each reason, the recorded wording and the absence of the read claims. Dispatch, seat-pause and wake-rearm suites: 149 passed.