True, but to me it seems the product is halfway there with org-roam/logseq/obsidian and that Rust code is the wrong way to start building it.
I'd try generating markdown to be rendered in logseq by teaching the AI how to link and whatnot in my AGENT.md (or whatever people call their project-local instruction/context file).
From outside, I'd not trust hallucinated stuff, but it'd be neat to start a project where knowledgeable humans did oversee all the proposed changes.
well yeah this is not itself the product, this is a demonstration of the need
Obsidian/etc really isn't it either, though; clearly OP wants to be able to do calculations with this stuff. They want both the knowledge graph AND an executable code environment. (I imagine Emacs can do both.)
Similar: for years I've been lugging around the idea of making a game like Civilization but where all of the different theories of history can be turned on/off as modules. Maybe going back to prehistory:
- did fire lead to cooking lead to big brains lead to tools lead to agriculture?
- or was it ice ages ending that lead to agriculture?
- or did oxygen levels change leading to more efficient brains?
- or were we Born to Run?
- or did women's hips change shapes to allow bigger brains?
- or perhaps 2001: A Space Odyssey occurred as written
- or Ancient Aliens...
Repeat for every other highly-debated period of history.
Somehow having all of these in the same modular system feels like it would metabolize them in a way that reading a bunch of separate theories can't really do. Same for OP's anatomy.
I'd try generating markdown to be rendered in logseq by teaching the AI how to link and whatnot in my AGENT.md (or whatever people call their project-local instruction/context file).
From outside, I'd not trust hallucinated stuff, but it'd be neat to start a project where knowledgeable humans did oversee all the proposed changes.