You come back to your desk after a week away and stare at three files: final.pdf, final_final.pdf, final_final_v2.pdf. You created all of them. You have no idea what any of them mean anymore.
That moment is a knowledge-management problem, and most tools answer it with search. Search helps when you remember the words. It fails when what you actually remember is the relationship: the diagram that went with the proposal, the paper that backed up the argument, the note that explained why the file exists.
The idea: store relationships, not just documents
A knowledge graph treats the things in a workspace as connected entities rather than isolated files. Documents link to their attachments, notebooks, projects, and sources. The links carry meaning, not just pointers.
The interesting design question is where that meaning comes from. One option is inference: feed everything to a language model and let it rediscover context on demand. That works, but it re-derives what the author already knew, spends tokens doing it, and can misread the intent. Another option is to capture the relationship at the moment it exists. When someone attaches an image to a document, ask two cheap questions: what does this asset contain, and why is it attached here? Those two answers, recorded once, are worth more than a hundred re-analyses later.
The trade-offs
Explicit relationship capture adds friction to the writing flow, and relationships go stale as documents evolve. Inference scales without asking anything of the author but inherits the model's misunderstandings. Most real systems end up hybrid: automatic structure where it is reliable (this file belongs to this project), human-supplied context where it matters (this image is the evidence, not decoration).
How we approached it at Andika
Andika is a knowledge workspace, and its assets are not treated as files with filenames alone. When you attach something, the platform asks what it contains and why it is attached, creating an explicit relationship between the asset, the document, and your intent. Connected AI tools receive that grounding directly instead of re-inferring it, which cuts token usage and keeps human meaning at the center.
On top of that, Andika automatically builds relationships between documents, pages, attachments, notebooks, and projects, so the workspace itself remembers what connects to what when your own memory fails. Under the hood we are building the AND model, intelligence designed to help you recall what you worked on and how your information connects. And if you do not want to wait for it, you can connect your own LLM: Andika's MCP layer gives it structured, read-only access to navigate the workspace with you.
You should not have to remember where your knowledge lives. Your workspace should remember for you.
Adapted from posts on the Andika blog.
Top comments (0)