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.
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.)
But think more broadly. Imagine just
```
import <established knowledge>.anatomy
import <established knowledge>.high_energy_physics
import <established knowledge>.microeconomics
...
```
into a notebook-like environment, with good intellisense and completions. But not quite as a programming language—somewhere between that and a wiki.
- 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.