LATER: comments as notes — one comment system for canvases, notes and every item #996

Open
opened 2026-10-03 08:05:22 +00:00 by kayg · 0 comments
Owner

Owner decisions (2026-10-03, #509 K1–K4): later, one comment system for every item

Contract: DESIGN §60 "Comments". "Comments as notes please! No separate notes!"

  • Comments are ordinary Notes (file over app). Each commented item (canvas element, note block, photo, Event, file…) gets ONE companion note " · comments"; each thread is a heading anchored to the target by stable ID (element ID, block ID, item ID), entries carry author and time.
  • Permissions follow §54: Collaborate read+write, Share read, public links none.
  • @name notifies that User in Notifications with a deep link to the exact element/block.
  • UI: count badge on the element/block → thread in an anchored popover (no right sidebar); Resolve marks the thread resolved in the note, never deletes.
  • Parity: API, CLI, MCP, WebMCP through the action registry; the companion note is editable like any note (edits there show in the popover).
    Status: LATER. Design details (file location of companion notes, rename behaviour, how a thread survives target deletion) get a short round before building.
## Owner decisions (2026-10-03, #509 K1–K4): later, one comment system for every item Contract: DESIGN §60 "Comments". "Comments as notes please! No separate notes!" - Comments are ordinary Notes (file over app). Each commented item (canvas element, note block, photo, Event, file…) gets ONE companion note "<item> · comments"; each thread is a heading anchored to the target by stable ID (element ID, block ID, item ID), entries carry author and time. - Permissions follow §54: Collaborate read+write, Share read, public links none. - `@name` notifies that User in Notifications with a deep link to the exact element/block. - UI: count badge on the element/block → thread in an anchored popover (no right sidebar); Resolve marks the thread resolved in the note, never deletes. - Parity: API, CLI, MCP, WebMCP through the action registry; the companion note is editable like any note (edits there show in the popover). Status: LATER. Design details (file location of companion notes, rename behaviour, how a thread survives target deletion) get a short round before building.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#996
No description provided.