You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: design: terminal participation in object discussions (from #5682) #5873
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
TUI/CLI flows, textual anchor rendering, and offline compose for chat and talk pages.
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).
Ordering (the substantive triage finding):#5873 is a surface design — it renders and composes against models its siblings define — so it sits after them:
Blockers recorded: sequencing only — #5870/#5871/#5872 are open design work ahead of this ticket, under a parked (not blocked or escalated) parent. No Drew decision is needed to proceed in that order. Issue #5873 stays open as the design ticket (programme epic #2056); implementation timing is a separate decision per the filing note.
Activity
developing-today commentedon Nov 5, 2026
CODE-1556
dezren39 commentedon Nov 5, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 5, 2026
🤖 Agent note · triage complete
Triage of issue #5873 at current main (verified fresh 2026-11-05):
app/id). No hard-stop labels, no design content beyond the filing stub, no implementation or PR references it. Expected output per its body: a recorded decision (chosen shape, alternatives rejected and why, invariants implementation must hold), covering TUI/CLI flows, textual anchor rendering, and offline compose for chat and talk pages.status/parkedunder another queue task. The parent fixes conversation↔object linking, talk pages, and terminal participation at the programme level — decisions id: design: terminal participation in object discussions (from #5682) #5873 must not re-decide.Ordering (the substantive triage finding): #5873 is a surface design — it renders and composes against models its siblings define — so it sits after them:
Blockers recorded: sequencing only — #5870/#5871/#5872 are open design work ahead of this ticket, under a parked (not blocked or escalated) parent. No Drew decision is needed to proceed in that order. Issue #5873 stays open as the design ticket (programme epic #2056); implementation timing is a separate decision per the filing note.