spec: message-kind tagging decided — Jev first, crow header fallback (#3); EVENTS.md nest section stub

EVENTS.md

@@ -28,6 +28,12 @@ Each SSE message: `event: <name>` and `data: <JSON>`. Every payload includes `li
 
 Pending approvals that get no answer within 10 minutes count as rejected (`verdict: timeout`). Fail safe.
 
+## Nest messages (contract in progress — B1 owns the full payload tables)
+
+Message kinds (CHATROOM_SPEC.md section 4): `say`, `request`, `claim`, `deliver`, `refer`, `nudge` (harness trigger), `flag` (Sentry only). Nest events stream over SSE keyed by `nest_id`.
+
+Tagging [decided 2026-10-27]: Jev choice-tags every message (`kind` question, high band); Jev unsure → the crow's own structured header; disagreement → Jev wins, logged. Payload fields carrying this (author, kind, to, refers_to) are finalized in B1.
+
 ## Settled details
 
 - `item_id` is `<list_id>-<n>`, numbered from 1 in list order.