Love this article - Satya talks about building "token capital" - or organisational learning to turn workflows and tasks into AI systems and loops.
Why doesn't it exist today?
This is (and will be) an unsolved problem - requiring great research, infrastructure AND product work. also what we're doing at
@supermemory right now. (I personally have been working on this problem for years now!) and i'm glad people are talking about it now!
1/ Research
No one knows the right "winning" architecture to build something like this. There is no right answer. There are no deterministic good benchmarks.
for the AI system has to learn and improve over time - It has to have an understanding of time, how the world evolves and connect the dots just like humans do. It would have to infer or "reason" through knowledge. It has to forget things as well.
This article talked about building evals specific to your org - We believe this is the right way! We have been building a framework to easily evaluate systems on any setup (
Git.new/membench) and also a dataset for long horizon organizational data (
smfs.ai/research). A lot of our customers have set up evals that matter to them.
It does not matter if it's graph vector etc - customers don't care. This system should be composable to whatever use case the enterprise wants, and something they can build on / amend.
2/ Infrastructure
It's not just about having a huge vector store. Every raw document / item can amount to hundreds or thousands of interconnected knowledge, that's also being dreamt on and new knowledge being evolved from it.
The model that actually makes the learning also can't be too expensive. it can't even be 50% of the main model! Because this model will be looking at everything and choosing what to learn. So there's also a lot of distillation / inference engineering involved there.
At
@supermemory we solve these by building our own data systems and a model that is doing the learnings. We have a fact based temporal graph that also ensures that everything is properly attributed and traceable.
3/ Product
For people building on top of supermemory, we have to make it completely hackable and composable for every use case.
Complex organizations have different permissions structures - And different data sources to learn from. Different things to learn.
They also have different ways of bringing it back to the agent - Sometime it will be "implicitly" given, or the agent may "explicitly" look up data.
Maybe you want to give that data as
@karpathy LLM wiki (filesystems) style!
For this we have built all permission system and controls into supermemory. It's natively multi tenant, and queryable deterministically (as SQL) at the same time.
You can also use it as a filesystem! We bring the knowledge as needed to the agent . We call it
SMFS.ai
------
We are trying to build the best memory and context system for AI so that organizations can build their own token capital!
This is a hard unsolved problem and an important one to solve.