> Everybody is building their own llm-wiki systems these days
there is a dark side to this. my coworker is insistent that his variant of this is going to become the teams backbone and i can't get him to stop even when i showed him a page of beyond wrong answers. he straight up doesn't understand that having a knowledge base != claude now sees all of it at once and can consider the endless breadth and shades of gray that make up human decisions. he's 100% convinced that claude grepping through the files is foolproof and won't miss any details lol
i personally just stopped messing with grand knowledge base ideas and these techs. i think everyone's shooting a lil too high and can't fully define what exactly they're after.
so i stepped back and i keep claude there for a very black and white need. claude's there to speed up stuff in domains i know well so i can guardrail him with massive success and have him code pieces im simply too lazy to code myself or alley oop something im struggling with. in a tortoise and the hare parable kind of way im the only guy here who isnt getting huge gotcha holes from AI in the solutions im delivering. all polished with the same attention to detail ive always had. i've just found these grand wiki everything ideas are just not yielding what people think they're yielding. for whatever reason i'm still the meatware layer thats a better index in the end if ive done my homework. perhaps something is lost when we cede a huge chunk of our journeys to seek information. i've still yet to be impressed by any "claude tied all these things together and found this insight this is insane" moments, every single time ive pointed out that any of that could've been a report.
Hey zby, if you're collecting these, Hjarni (hjarni.com) would fit your source-only tier alongside Fintool and Supermemory. Hosted SaaS with MCP built in, hierarchical LLM instructions (global/team/container/note), and a shared-note protocol for Claude/ChatGPT multi-agent workflows. Happy to write up a page in whatever shape you want.
The wishlist doc you linked is good, would be up for collaborating on that.
This is a really cool list and repository of ideas. Seems like the focus of the work is on making knowledge legible to AI. I wonder if you (or others) have done a similar level thinking about the inverse – making AI more legible to humans?
there is a dark side to this. my coworker is insistent that his variant of this is going to become the teams backbone and i can't get him to stop even when i showed him a page of beyond wrong answers. he straight up doesn't understand that having a knowledge base != claude now sees all of it at once and can consider the endless breadth and shades of gray that make up human decisions. he's 100% convinced that claude grepping through the files is foolproof and won't miss any details lol
i personally just stopped messing with grand knowledge base ideas and these techs. i think everyone's shooting a lil too high and can't fully define what exactly they're after.
so i stepped back and i keep claude there for a very black and white need. claude's there to speed up stuff in domains i know well so i can guardrail him with massive success and have him code pieces im simply too lazy to code myself or alley oop something im struggling with. in a tortoise and the hare parable kind of way im the only guy here who isnt getting huge gotcha holes from AI in the solutions im delivering. all polished with the same attention to detail ive always had. i've just found these grand wiki everything ideas are just not yielding what people think they're yielding. for whatever reason i'm still the meatware layer thats a better index in the end if ive done my homework. perhaps something is lost when we cede a huge chunk of our journeys to seek information. i've still yet to be impressed by any "claude tied all these things together and found this insight this is insane" moments, every single time ive pointed out that any of that could've been a report.