Joined 19 years ago
Other robust knowledge wikis like Obsidian have very good brain maps and knowledge node explorer views… but I can’t imagine many people who are looking for a file would try and navigate the tree of knowledge, vs just searching for it.
Agent-first product design enables the highest utility when we just ask agents for things, vs clicking around on our own. I am not the primary worker in my day-to-day getting shit done. My agents are, so the interface should be built first-class for them… and then give me some ways to audit or see at a glance what is going on.
But… Let’s do some visuals!
The OzBrain Signature Visualization. Every digital brain on OzBrain generates a unique signature based on a slice of recent data. Inspired by a brain MRI... I broke this down to Diversity, Density, Activity.
How diverse is the brain and how many collections of knowledge does it hold. - This adds diversity to the number of colors that represent the brain
How many articles build up the depth of each collection. - This adds the focus and clarity of the lines.
How much are agents reading and accessing this knowledge. - This generates the speed of the activity in the brain.
For comparison, the attached video is first my staging environment brain that holds limited knowledge and activity vs my actual brain that I use everyday with my agents. https://youtu.be/Wip9oTxm-II
*OzBrain actually has a built in task system and one user has knocked off hundreds of tasks without even using many articles… gonna have to figure out how to visualize that next!
--
What’s the coolest brain visualization you’ve seen?
If you were working n the OzBrain signature visualization, how would you improve it?
This will be the big challenge with this. Storing/Retrieving works fine across hundreds of articles... I have more than 500 right now just from OzBrain and a bit of the thing I was building before. When it becomes thousands with dozens being added all the time, the maintenance will become more of a necessity.
I lean a little bit towards store everything because the system's abilities are changing so fast right now, that having our previous thinking or reasoning is useful in being able to improve or correct current assumptions based on previous data.
I'm assuming that the content you put in is all agent driven. Source files (ie, a transcript, a data log, stuff that shouldn't eery change) get recorded but the articles are some kind of agent reasoning on top of it. I don't have any interface to edit an article. Your agent does it.
And yeah I agree about not building for human consumption. The agents create and consume vasly more data than we can.
I don't do any ingestion, I figure out can automate that in a routine or a zap or whatever you want.
