2,254 karma · joined September 12, 2007
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.
Are you seeing engineers use it or more every day people getting the hang of it to?
OzBrain is text only, and basic markdown formatting (OKF). No fancy PDFS, etc. BUT that is what your agent is for. If you want to generate a fancy PDF, have an agent reference the relevant articles and generate what you want. I've considered a lot of additional services like automatic ingestion, ie every call transcript auto-ingested as a source article in the brain... but you can do that with routines or Zapier. My focus is on the infra of the data getting to and from your agents.
I think Karpathy's llm-wiki was a boost to the wiki-markdown club, and it makes a ton of sense why a technical person would adopt that. They're already veru comfortable with github and moving files with terminal commands. They're not my target audience right now, but maybe when we have more robust brain maintenance they'll decide it's jsut easier to use OzBrain and not maintain their own thing.
P.S. In true move fast break things mode... I spent a good 15min working on the name. :) It works for now and if it really works well for people and they love it, the name won't matter so much.
P.P.S. Thanks, it's either genius or incredibly stupid... hard to know these days as stuff moves so quickly and your AI tells you you're so smart. It's what I HAD to build, because I don't speak any of the current languages. I lost my coding skills long ago, so at a point where it might make sense for a smart engineer to review or approve something... I needed to insert an agent that actually knows what it's talking about and understands how to make a good decision. That thing is constantly improving or breaking... I tried to automate one more step a few days ago and have been paying the price and bug fixing my thing that builds things, instead of just BUILDING THE THINGS! ugh.
P.P.P.S. I mean I used OzBrain to build OzBrain and make that eng flow work. If you think something in there would be useful, I'd just point an agent at it that is connected to your whole workspace/flow and ask it what is useful/dumb.
*Bonus point. Because my whole brain is in OzBrain and it knows what I'm building, why, how... I can take a talk transcript like Garry's from Startup School and just ask an agent "Save this transcript in the brain as a source and then review it and show me where this validates or invalidates some of my thinking. And what else would be interesting for me to consider in my broader work."
We’ve started with social messaging for kids under 12, that includes a kid friendly GPT bot they can interact with... Genie.
DM me for early beta access.
Beta site: https://beta.genie.gg