Introducing Octopedia

Every team carries a memory it never wrote down. Who introduced you to that investor. Why the architecture went one way and not the other. The promise made in a hallway that everyone half remembers. That memory is real, it is valuable, and it lives almost entirely in chat history and people’s heads.

The standard answer is a wiki. The standard result is a wiki that goes stale by the second week, because keeping it current is a chore, and chores lose.

A different starting point

Octopedia begins from a small observation: your team already writes its memory down. It does it every day, in the channels where the work happens. The text is there. What is missing is structure, and a place for it to live that will outlast any single tool.

So Octopedia listens where the conversation already is, in iMessage, Slack, Telegram, Discord, WhatsApp, and voice notes. When something worth keeping goes by, it files it: a person, a project, an organisation, an event. Each one becomes a markdown file with a small block of structured frontmatter, committed to a git repository.

The vault is not an export feature. It is the product.

What that buys you

Because the record is plain markdown in git, three good things follow at once.

• It is yours. Clone the repository, grep it, diff it, archive it. Leaving Octopedia means keeping a folder of files you can already read.
• It is honest. Every change is a commit. You can see who wrote what, when, and what it replaced. Agent edits and human edits sit in the same history.
• It is durable. Plain text has outlived every file format invented to replace it. A markdown vault will still open in thirty years.

What comes next

This is the first public note in what will be a steady stream. In the posts ahead we will get specific: how the structured merge engine keeps two people’s edits from colliding, why search has three tiers instead of one, and how to stand up the whole stack on your own hardware in about ten minutes.

Octopedia is open source and developed in the open. If the idea of a team memory you actually own sounds right to you, come read the code.