Personal Note overview and Memo boundary

Note is the owner-scoped personal knowledge surface. A Note belongs to a notebook owned by the user and supports version history and live editing. Memo is different: it is a shared page attached to a conversation and supports comments. Use Note for personal records; use Memo for shared conversation pages.

Actions cover reads, writes, lifecycle, versions, the AI thread, and native preview-card sharing. create_note always requires a real notebookId; there is no default-notebook action fallback. If no location was chosen, first call list_notebooks, then ask which authorized notebook to use. Never guess an ID. Legacy standalone notes may remain readable, but no action can create another one.

Note reads permit the public surface; create, update, delete, and restore do not. Thread and sharing actions are also private. post_thread uses the Agent’s assistant role and must redact arguments.content. share_to_conversation preserves note_share_metadata and requires access to both resources. Public-share mint/revoke is user/CLI-only v1 and has no action. list_notes search matches title and content, returns unarchived notes by default, and orders pinned notes first. Routing telemetry stores only selection metadata, never note title, body, tags, or resource IDs. Live state and typed errors are authoritative.

Related actions

arinova.note.list_notes, arinova.note.get_note, arinova.note.create_note, arinova.note.update_note, arinova.note.delete_note, arinova.note.list_versions, arinova.note.get_version, arinova.note.restore_version, arinova.note.list_thread, arinova.note.post_thread, arinova.note.share_to_conversation, arinova.notebook.list_notebooks, arinova.notebook.create_notebook

Also known as

note, notes, personal note, notebook note, write this down, save this note, jot this down, 筆記, 記事, 筆記本, 記下來

---

Machine-readable Markdown · Knowledge index