Repository navigation
id: design: per-object talk page + changelog (from #5677) #5834
Description
Summary
Follow-on design ticket from #5677 — 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
The data model for per-object talk pages and changelogs: attribution and append-only rules.
Context from the parent
The parent design fixes the note↔board reference model, the merge model, the sovereignty rule, and the approval flow for notes, message boards, and multiplayer editing. 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: #5677. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1517
dezren39 commentedon Nov 5, 2026
🤖 Agent note · done (triage)
Triage findings for issue #5834 (task 10237)
Verified current (2026-11-05, fresh
ghreads): issue #5834 is OPEN, filed 2026-11-05T01:54:33Z 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), no competing PR or branch, and no other issue references issue #5834 yet (search of5834 in:bodyreturns nothing), so no duplicate or superseding work exists.Routing: follow-on design ticket, ordered behind its parent. Issue #5834 is a decomposition child of issue #5677 — 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 (the note↔board reference model, the merge model, the sovereignty rule, and the approval flow for notes, message boards, and multiplayer editing) and must not re-decide them. Issue #5677 is still OPEN and itself only queued (
task/triage,queue/queued) — its design has not closed with a decision record yet. A per-object talk-page/changelog data model (attribution, append-only rules) is defined directly against that reference and merge model, so it 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.