Memos
Capture decisions in your library — PDF export, versioned, citeable.
What a memo is
A memo is the captured output of a conversation or synthesis session. It is the load-bearing artifact of Cortex — the system gets more valuable as your memo store grows, because every future answer can reference the past.
A memo has: title, summary, body (markdown), agent role (or roles, for synthesis), product, cited topic files, model version, and version history.
How to save one
From inside a chat conversation or synthesis session, click Save as memo. Cortex pre-fills the title from the conversation summary and the body from the most recent agent reply (you can edit before saving). Hit confirm and it lands in the library.
Versioning
Memos are append-only. Editing a memo creates a new version; the old one stays readable in the change-log tab. This means a cited memo never silently changes underneath you. When a decision is reversed, publish a new version that explains the reversal — don’t delete the old one.
PDF export
Every memo can be exported as a print-quality PDF. Use this for board packs, sharing with outside counsel, or filing away in your own document store. The PDF includes the citation list and the version stamp.
Searching
The memo list supports filter by agent role, by product, by date range, and full-text search across titles and bodies. Search is tenant-scoped — you only see your own memos.
Referencing a memo from a new conversation
To bring a past memo into a new conversation, open it from your library and paste the relevant content into your message — the agent then uses it as context for that turn. Autonomous memo lookup (an agent searching the memo store or fetching a pasted URL on its own) is on the roadmap, not yet available.
What memos are NOT
Memos are not edit-in-place documents. They are not a wiki, a CRM record, or a Notion clone. If you find yourself wanting to edit a memo to keep it “current”, that’s a sign the content belongs in a topic file instead.