Why your team's memory belongs in plain text

Pick any knowledge tool your team used five years ago. There is a fair chance it has been acquired, sunset, rebranded, or repriced beyond reason. The knowledge you put into it had one of two fates: it was exported into a heap of unloved files, or it was lost.

This is not bad luck. It is the predictable result of storing durable knowledge inside a format you do not control.

Plain text is a promise

A markdown file makes a quiet promise: anything that can read text can read this forever. No license, no runtime, no vendor. The promise has held for decades, across every wave of software that arrived to replace it, and it will keep holding because there is nothing in it left to break.

When your team’s memory is plain markdown, the tool that manages it becomes genuinely optional. Octopedia is, we hope, a very good way to read and write your vault. But the vault does not need Octopedia to exist. That asymmetry is the entire point.

Structure without lock-in

Plain text is sometimes dismissed as unstructured. It is not. A markdown file can carry a precise block of frontmatter:

---
type: person
title: Ada Lovelace
org: [[analytical-engines]]
last_contact: 2026-05-14
tags: [advisor, intro]
---

Walked through the Q3 roadmap. She will introduce us to two infra leads.

That is structured data. It is queryable, indexable, and linkable. It is also still just a file you can open in any editor on any machine. You do not have to choose between structure and ownership. You can have both.

Git makes it accountable

Put that file in a git repository and the memory gains a property most knowledge tools never offer: a complete, honest history. Every edit is a commit. You can see what a page said last month, who changed it, and why. Nothing is silently overwritten, because git does not silently overwrite.

For a team, that history is not a technical detail. It is trust. The record of how you decided something is often as valuable as the decision itself.

The test that matters

Here is a simple test for any tool that holds your team’s knowledge: if it vanished tonight, what would you have in the morning?

With a proprietary tool, the answer is a migration project. With a plain-text vault in git, the answer is: exactly what you had yesterday, sitting in files you can already read. Build on the format that passes that test.