Note deletion, archive boundary, permissions, and events

delete_note is an irreversible hard delete. The database cascades deletion to all version snapshots, so version restore cannot recover it; registry policy requires user confirmation and strict drift. Archive is a separate reversible persisted state. archive_note and unarchive_note perform that lifecycle change without confirmation, while list_notes can filter archived items. If the user says “put this away,” “hide it,” or “archive it for now,” use archive rather than deleting.

Notebook read access permits listing and fetching notes. Create, update, delete, and restore require write access; attempting a mutation through a read-only grant returns PERMISSION_DENIED. Treat list_notebooks as the available notebook list for this Agent. If a notebook is absent, follow the runtime not-found or permission result and never probe or guess its ID. Knowledge cannot grant access or bypass confirmation and content redaction.

Successful Note mutations emit note.created, note.updated, note.deleted, note.archived, or note.unarchived with source type notebook. Trigger rules can observe those events and require a notebookId scope, optionally narrowed by noteId; use the existing Trigger cards for the full event and delivery contract. Repeating the same archive state is a no-op and emits no duplicate lifecycle event. All Note mutations are unavailable on public surfaces. Destructive wording must describe hard deletion and loss of history, not archiving. Current action results and typed errors override this card.

Related actions

arinova.note.list_notes, arinova.note.get_note, arinova.note.create_note, arinova.note.update_note, arinova.note.archive_note, arinova.note.unarchive_note, arinova.note.delete_note, arinova.note.restore_version, arinova.notebook.list_notebooks, arinova.trigger.create_trigger

Also known as

delete note, archive note, hide note, note permission, read-only notebook, note trigger event

---

Machine-readable Markdown · Knowledge index