3.0Memory
The knowledge base that writes itself.
Under the chat is a working memory: your clients, decisions, projects, and people, connected as you talk. Nothing to author, nothing to keep current.
3.1
Every wiki has one good month.
Authoring is a second job stacked on the first, so wikis rot. Naumu builds the same knowledge out of the conversation your team is already having.
3.2Ask it anythingNothing to author
No blank page and no template - saying what happened is the writing.
Meridian
Updated 2m ago - from chat
Never out of date
The newest thing your team said is already in it, because the work is what writes it.
Corrections are diffs
Say what changed and accept the proposed edit, attributed and reversible.
Meridian - renewal terms
agreed monthly from April - finance could not approve annual prepay
Pilot kickoff - Meridian
onboarding confirmed, pilot moved to Sep 14
A source on every fact
Each fact traces back to the member who added it and the thread it came from.
3.2
An answer, not a results page.
Ask in plain language and Naumu answers from your own material, searching by meaning, with the notes, threads, and people it drew on linked in the reply.
3.3Import
3.3
Start from what you already have.
Paste your website, add your files, or connect Slack, Jira, Linear, and ClickUp. Naumu reads them and does a first pass you can correct.
IntegrationsOne message to start
Attach what you have, say what you are - the first pass builds itself.
Files and folders
Specs, transcripts, and exports come in as a first pass you correct.
Connected tools
Issues and tasks sync in one way and stay current as they move.
Over MCP, acting as you
Your own AI
Claude and ChatGPT connect over MCP and write the same memory, acting as you.