Skip to content

id: design: terminal participation in object discussions (from #5682) #5873

Open

Description

@dezren39

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

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).

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Nov 5, 2026
  2. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 5, 2026
  4. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  5. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triage complete

    • Agent: queue worker (repo-worker-code), lane code-j
    • Session / ID: task 10275
    • Found via: queue claim (coverage-audit requeue)

    Triage of issue #5873 at current main (verified fresh 2026-11-05):

    Ordering (the substantive triage finding): #5873 is a surface design — it renders and composes against models its siblings define — so it sits after them:

    1. id: design: chat anchor data model (from #5682) #5870 first — the anchor data model. id: design: terminal participation in object discussions (from #5682) #5873's own scope names "textual anchor rendering": a terminal cannot render anchors whose data model is unsettled.
    2. id: design: talk-page semantics (from #5682) #5871 (talk-page semantics) and id: design: chat ↔ talk-page unification (from #5682) #5872 (chat ↔ talk-page unification) next — id: design: terminal participation in object discussions (from #5682) #5873's flows span both chat and talk pages, so which surface a terminal flow lands on depends on the unification answer.
    3. id: design: terminal participation in object discussions (from #5682) #5873 then, scoped to: TUI/CLI flow shapes over the settled anchor model, textual anchor rendering rules, and offline-compose semantics (queueing, conflict behaviour on reconnect) against id: design: talk-page semantics (from #5682) #5871/id: design: chat ↔ talk-page unification (from #5682) #5872's semantics.
    4. id: design: thread resolution & the discussion→edit loop (from #5682) #5874 and id: design: notifications, watch/mute & presence for object discussions (from #5682) #5875 consume the same surfaces and can proceed in parallel with or after id: design: terminal participation in object discussions (from #5682) #5873; neither blocks it.

    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.

  7. added
    status/triagedTriaged and routed (see agent note)
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)status/triagedTriaged and routed (see agent note)task/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions