The problem
You know more than your tools can hold.
You know that the email from last Tuesday connects to a conversation you had three months ago, which relates to a project that lives in a different app, which depends on a document someone shared in a chat that has since scrolled out of reach. You know this. You carry these connections in your head. Your tools do not.
This is not a complaint about any particular tool. Each one does its job. The email client handles email. The note-taking app handles notes. The project tracker tracks projects. The file system stores files. They all work, in isolation, for the narrow task they were designed for.
The problem is that your life is not narrow. Your work is not isolated. The connections between things are where the meaning lives, and no tool you use today captures them.
The flood
It was not always this bad.
In the early days of personal computing, the amount of digital information a person handled was small. A few files, a few emails, a few bookmarks. You could keep track. It was even fun: jumping from one puddle to the next, each one a small, bright thing. Your email here, your files there, maybe a website you built yourself. Manageable. Playful, almost.
Then the puddles multiplied. Social networks, cloud services, messaging platforms, collaborative documents, streaming, subscriptions. Each one a new place where a piece of your life now lives. Each one with its own login, its own interface, its own way of organizing things, its own terms of service. The jumping stopped being fun; now you were running, trying to keep up, getting soaked.
By the 2020s, it is no longer puddles. It is a flood. Every tool generates more content than you can process. Every platform wants to be the center of your life. Every new AI assistant produces text faster than you can read it.
The volume is not the problem; the fragmentation is. Your information is scattered across dozens of systems that do not talk to each other, and the only thing that connects them is you.
When you are there, looking at the screen, you can make the connections. When you are not, they vanish.
Data, information, knowledge
There is an old framework, often drawn as a pyramid, that distinguishes four layers: data, information, knowledge, wisdom. The version by Jono Hey captures it cleanly.
Data is raw facts. Numbers, dates, file names, timestamps. A temperature reading. A row in a spreadsheet. It has no meaning by itself.
Information is data with context. A weather report. A sorted table. A search result. Patterns emerge. You can answer “what” and “when.”
Knowledge is understanding the relationships between pieces of information. Knowing that these weather patterns, combined with that terrain, produce avalanche risk. Knowing that this colleague's question connects to that project's deadline. You can answer “why” and “how.”
Wisdom is knowledge applied over time. The instinct that comes from years of experience. We will not get there today. But we can get to knowledge, and that is already further than most systems take us.
Here is the uncomfortable truth: almost every tool marketed as a “knowledge management system” manages information. Some manage it very well. But information is not knowledge. A perfectly organized Notion database, a meticulously tagged Evernote library, a beautifully linked Obsidian vault: these are information systems. They store facts and documents. They let you search and filter. Some even let you link one note to another.
But a link is not a relationship. “Note A links to Note B” tells you nothing about why they are connected, what kind of connection it is, or what it means from your perspective. It is a wire, not an understanding.
Knowledge requires three things that no current tool provides together: 1. Semantic relationships. Not “A links to B” but “A uses B, and that implies that the argument in A uses the framework in B.” Or “C elaborates on D”, or… A typed, meaningful connection that carries consequences. 2. A point of view. The same information, seen from different perspectives, produces different knowledge. Knowledge is not objective; it is perspectival. 3. Boundaries that protect focus without destroying connections. You need to work within a project without drowning in everything else; but when you need a connection to something outside, it must be reachable.
No file system offers this. No SaaS product offers this. No “second brain” offers this. That is the problem.
The imposed perspective
There is a subtler problem, one that is easy to miss because we have lived with it for so long.
Every system you use tells you how to think about your own information.
A file system gives you a hierarchy: folders inside folders. One tree, one root, one path to each file. If a document belongs in two places, you make a copy or a shortcut, and both are workarounds for a model that does not match how you think. You do not think in trees; you think in webs.
Gmail gives you labels and a search box. Notion gives you databases with properties. Slack gives you channels. Each one imposes a model: this is how your information is shaped, these are the categories that exist, this is what a “workspace” means. You adapt. You learn the system's language. You organize your life the way the tool allows.
This has been the deal since the beginning of personal computing: the system defines the perspective, and the human adapts.
But perspective is not a feature. It is the foundation. The reason you organize anything is because you need to find it, you need to understand it, you need to act on it. The organizing principle should be yours, not the tool's.
What if the system adapted to your perspective, instead of the other way around? What if you defined the categories, the relationships, the boundaries, and the tools served that structure instead of imposing their own?
This is not a rhetorical question. It is a design requirement.
The sovereignty problem
There is a final layer to this problem, and it is the most practical one.
Your data is not yours.
Your emails live on Google's servers. Your notes live on Notion's servers. Your messages live on Slack's servers. Your documents live on Microsoft's servers. You access them through their interfaces, on their terms, for as long as they choose to offer the service.
If Google changes Gmail's interface tomorrow, you adapt. If Notion changes their pricing, you pay or you leave (and good luck exporting everything). If Slack decides your free tier no longer includes message history beyond 90 days, those messages are gone.
You are not a user; you are a tenant, and the landlord can renovate without asking.
This is not paranoia. It is the business model. SaaS companies do not sell you software; they sell you access. The moment you stop paying, or the moment they stop offering, the access disappears. Your data was always theirs; you just had a view of it.
Sovereignty over your data means: your files live on your machine, in open formats you can read with any tool. Markdown, not proprietary databases. Plain text, not locked binary formats. If a tool disappears tomorrow, your information survives. You can open it with a text editor.
But sovereignty over data is necessary and not sufficient.
What you really need is sovereignty over the meaning: the relationships, the perspective, the structure. Not just “my files are on my disk” but “my way of organizing the world is mine, encoded in a vocabulary I control, in a system that reflects my perspective.”
That is what we are going to build.
Next: The failed solutions