id: design: chat anchor data model (from #5682)

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

Link types, part-anchors (ranges/blocks/regions), and anchor survival under edit and delete — the data model under conversation↔object linking.

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

CODE-1553

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-m
Session / ID: task 10272
Found via: queue claim
Task: Triage issue id: design: chat anchor data model (from #5682) #5870 — handed off to opencode execution lane; claimant launches the bound opencode session
Expectation: s — triaged at current main with evidence, fix path scoped or closed with evidence if already handled
Links: id: design: chat anchor data model (from #5682) #5870

🤖 Agent note · handed off

Agent: repo queue worker, lane code-t (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-t run 2026-11-05 06:59 CST; task 10272
Found via: claimed task 10272 this shift; execution-lane assignment returned opencode
Task: Re-claimed task 10272 for issue id: design: chat anchor data model (from #5682) #5870 (attempt 1/6 per claim row; previously handed off at 2026-11-05T12:49Z and parked). Fresh check: issue id: design: chat anchor data model (from #5682) #5870 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 10272 to a terminal state.
Links: task 10272 · issue id: design: chat anchor data model (from #5682) #5870

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-d
Session / ID: task 10272
Found via: queue claim
Task: work on issue id: design: chat anchor data model (from #5682) #5870 handed off to the opencode execution lane per the worker runbook §1b — the laptop claimant launches the bound opencode session, which drives task 10272 to its terminal state.
Expectation: claimant session picks up task 10272; this lane did not work the item itself.
Links: issue id: design: chat anchor data model (from #5682) #5870

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-y
Session / ID: task 10272
Found via: queue claim
Task: triage for issue id: design: chat anchor data model (from #5682) #5870 — handed off to opencode claimant (assigned_lane=opencode, session_id null at handoff); claimant launches the bound opencode session
Expectation: claimant session works issue id: design: chat anchor data model (from #5682) #5870 at current main
Links: task 10272

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
Session / ID: task 10272
Found via: atomic queue claim
Task: triage id: design: chat anchor data model (from #5682) #5870, the anchor-data-model design child of id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682. Fresh state: OPEN, no hard-stop labels, and no matching PR; prior unbound opencode handoff park has expired.
Expectation: verify the parent boundary and record the independent design route; do not re-open parent-wide chat/talk-page questions.
Links: id: design: chat anchor data model (from #5682) #5870, id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682

Triage outcome at current main (`2a676206852c9b5f4aa5a61873411fa850b13ec4`)

id: design: chat anchor data model (from #5682) #5870 remains OPEN, has no hard-stop labels, and has no matching PR. The parent id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682 is open and explicitly filed id: design: chat anchor data model (from #5682) #5870 as its independent anchor-model design child; no superseding implementation or design decision was found.
Keep the scope to the conversation/object link record, link types, part-anchor representation (ranges/blocks/regions), and anchor survival across edits/deletes (relocation, drift warning, orphan/tombstone behavior). Preserve parent constraints: anchor visibility must not leak private object content/existence, and the model must work with the existing chat protocol/client scope. Do not absorb talk-page semantics, terminal participation, or the discussion-to-edit loop; those are separate children (id: design: talk-page semantics (from #5682) #5871–id: design: notifications, watch/mute & presence for object discussions (from #5682) #5875).
No blocker or parent-completion dependency: proceed as an independent design child, and record any decision that would change a parent choice back on id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682. No extra child or implementation task is warranted at triage.

🤖 Agent note · done

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
Session / ID: task 10272
Found via: atomic queue claim
Task: triaged id: design: chat anchor data model (from #5682) #5870 against current main and parent id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682; scoped the anchor-model decision and sibling boundaries.
Outcome: issue remains open as an independent design child; no implementation PR or new follow-up created.
Links: id: design: chat anchor data model (from #5682) #5870, id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682, id: design: talk-page semantics (from #5682) #5871–id: design: notifications, watch/mute & presence for object discussions (from #5682) #5875

Navigation Menu

Repository navigation

id: design: chat anchor data model (from #5682) #5870

Summary

What this design must settle

Context from the parent

Decision record expected

Relations

2 remaining items

Triage outcome at current main (`2a676206852c9b5f4aa5a61873411fa850b13ec4`)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: design: chat anchor data model (from #5682) #5870

Description

Summary

What this design must settle

Context from the parent

Decision record expected

Relations

Activity

developing-today commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

2 remaining items

developing-today commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Triage outcome at current main (2a676206852c9b5f4aa5a61873411fa850b13ec4)

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage outcome at current main (`2a676206852c9b5f4aa5a61873411fa850b13ec4`)