I have been exploring a question that keeps showing up across everything I build: what should a database become when software, AI agents, users, files, code, memory, and validation all need to live together? Most databases are built around one shape of information, rows, documents, objects, vectors, graphs, or files, but modern AI native systems increasingly need many shapes at once, plus the ability to know where information came from, how it changed, why something matched, and whether it can be trusted. I am calling the current direction NexusDB. It is not finished, and I do not want to present it as if it is. This is an active research and architecture project, currently at the Genesis level. After about six months of research, the core evidence kernel has just come into focus.
What it shows
After about six months of research, the core evidence kernel has come into focus, the idea that the database should store evidence, not just data, and that raw source, decoded meaning, relationships, validation, and memory should stay connected inside one substrate.
Read the story →