Skip to content

A comment in an artifact's thread is deleted by its author, the artifact's owners, or whoever may take the artifact down (artifact.comment.delete, its row removed with no tombstone), and edited by its author while they may write in the thread (artifact.comment.edit, marked with edited_at); both audited without the text, the thread says per comment who may do which, and neither is announced to the session

Decision 1016 · accepted · 2026-11-16 · issue #979

Who

  • Delete (artifact.comment.delete {id, comment}): the comment's author, always, as long as they still see the artifact (their own words are theirs to take back, even after an owner took their role away); the artifact's owners, any comment in their thread; and whoever may take the artifact down as artifact.delete lets them (a platform administrator, the administrator of the team a team:<name> artifact is for), any comment. Whoever may remove the whole artifact may remove one comment of it: the takedown is the same method, decided by the plane from who calls it, not a separate administrator's method in admin.ex. A platform administrator calls it as themselves from either app, and the audit says by: takedown. A private artifact's thread is not reachable to a platform administrator who cannot see it (visible/3), so its comments go with the artifact's takedown, as before.
  • Edit (artifact.comment.edit {id, comment, body}): the author alone, while they may still write in the thread (owner, edit or comment); nobody edits another's words. The text is checked as a new comment's is (trimmed, not empty, at most 4000 characters). The argument is body, as artifact.comment names it, not text.

What happens

  • A deleted comment's row is removed: no tombstone "a comment was removed" is kept in the thread. The thread is a conversation on the artifact, not a record; the audit is the record (who deleted which comment of whose, and how), and a mark in the thread would say to every reader that somebody took something back, which is what the author or owner chose not to leave. The artifact's comment count drops with it.
  • An edit replaces the text and sets edited_at (a column added by the migration 20261116001016_artifact_comment_edits, additive); the thread shows "edited" with when. Earlier texts are not kept.
  • Audited as the write is, never with the text: artifact.comment.delete with the comment's id, its author's subject and by (author, owner or takedown); artifact.comment.edit with its id and new length.
  • Not announced. artifact_commented is unchanged. A session told of a comment is not told it was edited or deleted, and a deleted comment is never in a later daemon poll (Decision 1015). Who steers the session reads the thread for the current words.

Clients

artifact.comments gives each comment may_edit and may_delete for the caller, and edited_at, so a client offers each control only to whoever the plane will let use it (DESIGN §8: remove, don't disable) and never reasons about roles itself. The desktop app's thread and the console's show Edit (the text in a box, Save and Cancel) and Delete, which asks once in place, saying what it does ("It goes from the thread for everybody, and cannot be brought back."), with Delete and Keep it (DESIGN §11: say the consequence, not "Are you sure?"). The daemon forwards both methods with only their arguments and refuses them under Local only, as every artifact.* (Decision 1007).

Governs: apps/troupe_plane/lib/troupe/plane/artifacts/comments.ex, apps/troupe_plane/lib/troupe/plane/artifacts/comment.ex, apps/troupe_plane/lib/troupe/plane/artifacts.ex, apps/troupe_gateway/lib/troupe/gateway/artifacts.ex, clients/gui/apps/desktop/src/views/Artifacts.tsx, clients/gui/apps/console/src/views/ArtifactComments.tsx