id: design: talk-page semantics (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

Per-object discussion surfaces: lifecycle, and permissions vs the object's read-authority.

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-1554

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 262eb403-3347-4a7c-ba6b-e7bc263ca853
Task / ID: triage queue task 10273
Found via: queue claim
Task: triage id: design: talk-page semantics (from #5682) #5871, the separate talk-page semantics design ticket linked from parent id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682.
Verified fresh: id: design: talk-page semantics (from #5682) #5871 is OPEN, has no hard-stop labels, and has no related PR. Parent id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682 remains OPEN and parked; this claim is limited to child id: design: talk-page semantics (from #5682) #5871.
Expectation: route the standalone design work for id: design: talk-page semantics (from #5682) #5871 without taking over parent id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682.
Links: id: design: talk-page semantics (from #5682) #5871 · id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682

Triage result — #5871

Scope: this is a standalone design follow-on, not a runtime bug or implementation request. No reproduction or code change is applicable.
Parent context: id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682 defines the broader conversation/object model and states talk pages are canonical per-object discussion spaces using the existing chat protocol. This child should settle the per-object lifecycle and permissions against the object read-authority.
Current state: id: design: talk-page semantics (from #5682) #5871 is open, has no related PR, and is not superseded. Parent id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682 is open and parked; this triage does not take over the parent task.
Order / next work: the design can proceed as its own item using id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682 as context. Do not silently re-decide parent invariants; explicitly record any answer that would change them. Close this design with the chosen semantics, rejected alternatives and reasons, and implementation invariants. If the facet splits further, file and link the child issues here.
Routing: id: design: talk-page semantics (from #5682) #5871 itself is the follow-on design handoff, so no duplicate repo-queue packet was created.

🤖 Agent note · done

Agent: repo-worker-code, OpenChamber scheduled lane 262eb403-3347-4a7c-ba6b-e7bc263ca853
Task: queue task 10273 — triage id: design: talk-page semantics (from #5682) #5871
Outcome: triaged as a standalone design follow-on; findings and scope are in the preceding comment. No implementation PR or separate queue packet is needed at this stage.
Links: id: design: talk-page semantics (from #5682) #5871 · parent id: design: Chat next steps — conversation↔object linking, talk pages, terminal participation #5682

Navigation Menu

Repository navigation

id: design: talk-page semantics (from #5682) #5871

Summary

What this design must settle

Context from the parent

Decision record expected

Relations

Triage result — #5871

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: design: talk-page semantics (from #5682) #5871

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

Triage result — #5871

dezren39 commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions