I too am curious about the viability of a shared knowledge MCP! Ha, as I did do the work to take the one I’ve built twice and turn it into something others can use. OzBrain.com ~ maybe you don’t have to build it a 3rd time now? :)
Thank you for your insight. FYI You can share your brain with collaborators/partners. Did you read my comment on the post? You just clicked a link, looked at a homepage and got a meh-boner to come back and comment?
I'm not trying to solve the ingestion problem. It is there for sure, agents are pretty terrible at always following directions, so hopefully it's easy enough to just say "Put that in the brain" when in doubt. What is good is to save the source file ie transcription, raw comment/text, so that it is always there for future reference so the reasoned summary can be audited.
It sounds like you've got a great system for your technical folks. The question is if that works super well for sales, design, support, etc. I'm trying to build something that works equally well for the technical & non-technical folks. All connected to the same system. All in auto-pilot so nobody has to manage it.
Yeah, I wouldn't put your crypto wallet into OzBrain or anything... this is more the day to day operation of your business or personal life. While that is also valuable, our data is already sitting on a lot of servers so might as well make it useful for you and your agents.
What I'm building has a regular maintenance it runs across the knowledge. A. to chunk long articles down into smaller chunks or information with good routing. B. To review the latest thinking to make sure old thinking is deprecated and linked.
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.
Cool. If I'm reading it right, it only allows read access? How do you get knowledge into the brain?
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.
for knowledge writes in setoku, any agent that does queries can propose knowledge or edits. edits are flagged for admin/curator review. agents can query the pending and confirmed knowledge but basically have a flag that tells them what's been "blessed".
i like your conceptual focus on not pairing it with data. for me, it's just a practical thing: i want one tool i can have a colleague (or my wife) install that adds all the context they'll need (and then one spot I can curate and govern that context).