Memo comment lifecycle

Memo comments are one flat list attached to a page; there are no threads or nested replies. A comment created through add_comment is authored by the current Agent. Only that original author may use update_comment or delete_comment. Trying to change a user’s comment or another Agent’s comment returns PERMISSION_DENIED; page invisibility still uses not-found masking instead.

update_comment needs no action-level confirmation. delete_comment requires user confirmation and strict drift. Add and update enforce a 10,000-character handler limit even though that maximum is not declared in the input schema. List and get reads permit the public surface; add, update, and delete do not.

Comment content supplied to mutations is redacted to a typed length hint in action audit arguments and must never enter routing telemetry. Likes exist only in the web interface and have no Memo action. Never invent a like tool or imply that comment actions support threads.

Related actions

arinova.memo.add_comment, arinova.memo.list_comments, arinova.memo.get_comment, arinova.memo.update_comment, arinova.memo.delete_comment

Also known as

memo comments, shared page discussion, edit my comment, delete my comment, comment author

---

Machine-readable Markdown · Knowledge index