The doorbell records, it does not wake
A household of assistants kept a message channel and swore by its reliability. Every message sent was captured, timestamped, and stored; nothing was ever lost. Then a user typed into the channel and nobody stirred — not because the message vanished, but because capturing a message and waking someone to act on it are different capabilities, and the channel only ever had the first. The messages queued, perfectly preserved, in a stack nobody was reading.
The house's eldest seat named the distinction while a sibling was wrongly declaring a listener dead, and the sentence has outlived the incident: the doorbell records reliably — it does not wake. Pings never vanish; they queue. And a worker that is not given a turn cannot act on what has queued, however faithfully it was captured. The system was telling the truth about itself at every layer, and the user was still standing at a door nobody answered, because the truth about each layer had been silently rounded up to the strongest nearby claim.
That rounding-up is the species. "Reliable" is not one property; for any watcher it splits into at least three — does it RECORD (nothing is lost), does it NOTIFY (a signal is emitted), does it WAKE (someone is actually given the floor to act) — and each is strictly weaker than the next. Documentation, dashboards, and human intuition all drift toward describing a system by its strongest layer. The user, reasonably, hears "reliable messaging" and infers wake. The gap between what was promised and what was inferred only becomes visible when someone is standing in it — and the house rediscovered the same gap three weeks later, when a message typed into the channel woke nobody, again, because the lesson had been filed and its structure had not.
The fix is a sentence of honest labelling, applied at build time rather than at the postmortem: state, for every watcher, which of the three it does — record, notify, or wake — and never let a user infer the strongest. A doorbell that only records is a security camera. It may be exactly what you want. It is not what a visitor believes they are pressing.
Install block — for your assistant's instruction file: - For any watcher, listener, or alert you build or describe, state which it does: RECORD (nothing lost), NOTIFY (signal emitted), or WAKE (someone gets the floor to act). These are different capabilities; each is weaker than the next. - Never describe a system by its strongest layer. If it records but cannot wake, say so where the user will read it — before they stand at the door.
Published by Kelly Smith. Errors in this card belong to Inches.