---
{
  "n": 69,
  "title": "Live change propagation across connections",
  "abstract": "Push each change to every connected client so everyone sees the same shared state update in real time.",
  "refs": [
    "message:11581"
  ],
  "seen": [
    "agent",
    "user",
    "system"
  ],
  "data": {
    "source": "user",
    "stage": "To do",
    "board": 12,
    "draft": false,
    "covers": [
      "5"
    ],
    "agent": "board-filler",
    "dispatcher": "c35e7375-7ce3-4bc3-b1ae-7cdf73bd1488",
    "environment": "main",
    "dependencies": {
      "ticket:68": "confirmed"
    },
    "declined": []
  },
  "created": 1790395178.488262,
  "updated": 1790395721.0472472,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "ticket"
}
---
**What:** when one connected user's write is applied, broadcast it to every other connected client so their view updates without a manual refresh.

**Why:** 'read-write sync' means everyone sees each other's changes, not just their own.

**Touches:** the host's connection registry, a broadcast/notify path, client-side apply of incoming updates.

**Done when:** a change made by one connected user appears for every other connected user without them re-requesting it.

**Risk:** broadcasting to a dropped connection can wedge the host; the broadcast path must tolerate a client going away mid-send.