06-reference/research

unprompted agent speech decision rules

2026-11-03·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)

When should an always-on agent speak up unprompted, and does anyone's answer transfer to Auto Mode?

The question

"What decision rules govern when an always-on AI agent should speak up unprompted in a shared/async channel, and do any of them transfer to RDCO's own Auto Mode escalation design?"

Every's platform lead named this as the one problem his team has not solved for @Every in Slack ([[2026-10-20-every-shared-agent-permissions-architecture]]), while RDCO has been running an undocumented answer on iMessage for seven months.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The honest headline is that the field has not settled this, and RDCO should stop treating its own answer as the ad hoc one. Exactly one source in this sweep states a general rule for unprompted agent speech, it is a CMU position paper whose backing is three evaluators' heuristic judgment, and its own evidence base is borrowed from voice-assistant studies where an interruption is synchronous and unignorable. Async text is a different cost structure. Adapt ships a real configurable mechanism with no evidence and no opinion. Anthropic ships an opinion and an undefined number. Every ships an admission. Against that, RDCO has a trigger taxonomy the founder ratified in his own words, a correction log that sharpened it after a specific miss, and a cooldown mechanism that is genuinely novel. The comparison runs in RDCO's favor, and the correct update is to raise confidence in what is already running rather than to go shopping.

Two things should not change. First, the four-category trigger stays. Replacing a founder-validated taxonomy with Adapt's write-your-own-policy model would trade a rule tested against real corrections for a configuration surface with no published evidence behind it, and it would hand the founder a prompt-writing chore in exchange for flexibility a single-recipient DM does not need. Second, do not follow Anthropic in deleting the explicit gate in favor of model judgment. RDCO's own data says the mechanical check holds its rate while judgment decays, and the classifier hard-gate is load-bearing specifically because a channel message cannot authorize a production write. Softening the speech side toward in-model discretion while the action side stays mechanically gated would be a coherent split; softening both would not.

One thing is worth adopting, cheaply and reversibly. RDCO's speech decision is currently binary: send a bubble or stay silent. Anthropic's enumerated four outcomes - reply inline, open a thread, route into an existing workstream, say nothing - name a middle that RDCO half-practices and never decided. Today "brief iMessage, link to HQ" and the morning-brief digest both function as that middle, but they are chosen by habit rather than at speech time. Making it an explicit four-way choice (bubble now / append to an existing open thread / file to vault or HQ and surface in the brief / nothing) costs one paragraph in the Auto Mode rules and would cut fresh bubbles for items that are real but not urgent. Frame that as one vendor's enumeration reported secondhand, not as industry practice, and adopt the shape without the claim.

The urgency question should be named and then left alone. CMU's rule gates on task urgency and the recipient's current context, which is exactly the variable [[feedback_no_babysitting]] forbids Ray from inferring. The resolution already exists and looks accidental: the 9am-9pm parking window and the off-hours no-park carve-out are a coarse, mechanical proxy for recipient availability that requires no attention modeling at all. That is the right trade for a single-human channel, and it should be written down as a deliberate substitution so nobody later "fixes" it by building attention inference. Finally, the shared-channel half of the question mostly does not transfer. The ambient-spam problem, bystander externalities, per-channel scoping and re-tagging etiquette are all artifacts of a multi-party room; RDCO runs a single-recipient DM. What transfers is the attention budget of one person, and that is the narrower, more tractable problem RDCO is actually solving.

Why this is in the vault

This is the first vault doc to compare published decision rules for unprompted agent speech, and it closes the gap flagged in [[2026-10-20-every-shared-agent-permissions-architecture]] by establishing that RDCO's Auto Mode trigger is better evidenced than any shipped alternative found - which converts a suspected weakness in the channels agent ([[project_channels_agent_setup]]) into a defensible position, and gives the agents-in-production credibility thesis an original mechanism (the ask cooldown) to write from rather than a restatement of vendor posts.

Open follow-ups

Related

Sources

Vault

Web