docs(vrs): require quiet evented coordination

Author: myobie

docs/vrs/requirements.md

@@ -52,6 +52,18 @@ accepted.
   deterministic st2 reconciler keeps declared local processes converged; the
   root observes host-local runtime health, diagnoses failures, performs bounded
   recovery, and escalates what it cannot resolve.
+- **R22 Quiet, evented coordination:** A network using minimal or default
+  personas remains quiet while useful work proceeds. Agents coordinate only
+  when a real event requires it: an inbox DING, a durable failure, a true
+  blocker, a completion or decision handoff, or an explicitly declared named
+  schedule. Once admitted, coordination is vigilant and outcome-focused until
+  the need is cleared; chatty status loops and polling are not substitutes.
+  Ordinary supervisors are exception handlers for failures and truly blocked
+  work, not continuous managers of healthy work. An intentionally extended
+  supervisor persona may declare a higher coordination cadence; CoS is one
+  non-normative example, not a core role that st2 requires, types, or
+  standardizes. Transport loss never blocks host-local work that does not
+  require coordination.
 
 ### Must preserve delivery and launch behavior
 

docs/vrs/spec.md

@@ -180,6 +180,31 @@ positive declaration/template wakes, negative runtime/bus events, bounded
 discovery/materialization/PTY queries and writes, continuous-event starvation,
 and no-op desired-equals-actual behavior.
 
+## Quiet, evented coordination (R22)
+
+Useful work is silent by default. Presence, status, and durable plan state are
+inspectable facts, not invitations to send status messages or poll peers.
+Coordination begins only at an understandable event boundary:
+
+| Admitted event | Coordination obligation |
+| --- | --- |
+| unread inbox message | DING the recipient; process or hand off the request |
+| durable failure or true blocker | notify the responsible supervisor; diagnose, recover, or escalate until cleared |
+| completion or decision | hand the outcome to the agent or principal that needs it, then become quiet |
+| explicitly declared named schedule | perform that named coordination; do not emulate it with an ambient chat or polling loop |
+
+The inbox path follows the source contract in
+[DING requirements](./01-ding/requirements.md). A normal supervisor is an
+exception handler for failure and truly blocked work, not a continuous manager
+of healthy agents. An intentionally extended supervisor persona may declare a
+higher coordination cadence. CoS is one non-normative example only: st2 does not
+require or type that role, and R22 grants it no standardized authority.
+
+This boundary does not define the still-open schedule grammar in DQ1; it only
+requires a named declared event rather than an implicit loop. A transport
+partition may delay coordination, but it does not stop independent host-local
+work or create a global availability dependency.
+
 ## Targeted reconciliation (R19)
 
 `st2 up --materialize-only --task <host.agent.task>` resolves one exact local