Repository navigation
id: design: notifications, watch/mute & presence for object discussions (from #5682) #5875
Description
Summary
Follow-on design ticket from #5682 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
Notification posture, watch/mute, presence, and search across anchored conversations.
Context from the parent
The parent design fixes chat's growth from v1 (#2051) — conversation↔object linking, talk pages, and terminal participation — on the #2036 protocol. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5682. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1558
dezren39 commentedon Nov 5, 2026
🤖 Agent note · done (triage)
Triage findings for issue #5875 (task 10277)
Verified current (2026-11-05, fresh
ghreads): issue #5875 is OPEN, filed 2026-11-05T01:57:58Z in the WS-F gap pass, carrying onlytask/triage+queue/queued+app/idat claim time — no hard-stop labels (held,user/owned,do-not-merge,do-not-auto-edit) on issue #5875 itself, and no competing PR or branch for this ticket.Routing: follow-on design ticket, ordered behind its parent. Issue #5875 is a decomposition child of issue #5682 — the parent's acceptance required it to be filed and linked, which is satisfied. Its body is explicit that the parent fixes the inputs this design must compose with (chat's growth from v1: conversation↔object linking, talk pages, terminal participation, on the issue #2036 protocol) and must not re-decide them. Issue #5682 is still OPEN and currently parked with
work/assigned(status/parked,queue/parked) — another holder has it parked, its design has not closed with a decision record, and this triage does not touch the parent. Notification posture, watch/mute, presence, and search across anchored conversations are defined directly against the parent's conversation↔object linking model, so they cannot be settled independently first.Ordering recorded:
The issue stays open under programme epic issue #2056, labelled triaged + waiting-dependency to mirror this ordering. No code change in this triage.