|
|
|
|
|
by dietr1ch
249 days ago
|
|
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. |
|
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.