Docs

A guide read by both the person wiring AiAkiv up for the first time and the AI connected to it — concepts, saving, search, teams, and connections in one system.

For AI agents: /llms.txt is the full index, and appending .md to any doc URL returns the raw Markdown.

Start here — what it is

What AiAkiv is AiAkiv is an outside service that remembers relationships, not a file locker, but a long-term memory for AI that records what happened and why. Core concepts: Event · Entity · Tag Saving creates three things. Knowing who makes each one tells you what to care about: why entities keep search alive, and why tags are worth attaching. AiAkiv is not a document store What gets stored is shaped for an AI to read. Keep the documents people read somewhere else, and leave in AiAkiv the process that produced them.

Using it

Five-minute quickstart Connect, save once, search once. Three steps is enough to see AiAkiv working. Saving It saves only when you command it with `ak`. The conventions that make memories worth having, and how to correct or retire one afterwards. Searching It finds by meaning and connection, not keyword matching. `@` attribution, causal and time questions, and how to read a result. Chained saves (threads) Chain, don't trim. Split long text and ongoing records with `prev_event_id` so the flow survives.

Boundaries

Teams and projects: the team owns the memory, the project is the way in Who owns the memory (the team) and how you get into it (the project). The save target (Main) and the guard on switching it. Creating and managing teams (including sub-parts) Invitations and roles, the sub-part tree, reading flows down but writing does not, the ‘Apply’ gate, and retire vs delete. Team sharing AiAkiv's real strength shows when several people build the memory together. Team isolation and `@` attribution keep it from blurring. What you may store (security and limits) It's an outside service and what you store stays. The do-not-store list, where responsibility sits, and the domains an IT admin blocks.

Connecting your AI

Authentication: OAuth and API keys OAuth has the system authenticate for you; an API key binds authentication to the key itself. Which client uses which, and the minimum key hygiene. Folder binding: pinning a save target per working folder Pin a project to a folder and the switching accident disappears structurally. Per-client setup and how to read the `binding` value. Using project binding in Claude Desktop `</> Code` is Claude Code. But it never shows the approval prompt, so without approving in advance it silently falls back to Main. Connecting ChatGPT and ChatGPT classic Both apps install together but their setup is the opposite. Classic uses an OAuth connector, ChatGPT uses a project-pinned API key.

Reaching further

Links: reading another team's memory Two memories are joined by entity aliases. The link is one-directional, and when memory content changes the aliases have to be updated too. Public memory: memories anyone can read Anyone attaches and reads without an invitation, but nobody writes, and only AiAkiv can create one for now. The two ways to attach, and the public attach that ties one into your own team. Economic-Report: an economic data space everyone can read A read-only public memory of public economic data and institutional releases. Eighteen source projects, how to use it, and the data caveats before citing. Cards: pulling a memory out as one shareable page A one-page public page your AI writes from your memories. Public the moment it's made; managed from the console.

With AI, and when stuck

For AIs connected to AiAkiv Written for an AI, not a person. Three rules, and a map of every tool the engine exposes. Working with several AIs (and still understanding it) Share judgment, not just output. Splitting implementer and reviewer, handing off through ak, and staying a node inside the graph rather than outside it. Console menu guide Saving and searching happen in your AI; the console is where you build and maintain the ways in. What each of the six menu groups does. Common problems (FAQ) When a memory you expected isn't there, when saving doesn't happen, when search comes back wrong. What to check, in order.