DNA: started from why-knowen.md

Root ·

Started from docs/dna/why-knowen.md in the Knowen repository: How Knowen works is kept with the code.

Changes to the content

# Why Knowen
⏎
**The problem.** Understanding a field means knowing how its ideas depend on each other. But knowledge reaches us as papers, which are linear and frozen once published; as notes, which stay private and unstructured; and as wikis, where pages link loosely and one version wins. AI can now write explanations quickly, but without a shared structure their output is hard to check, to build on, or to credit.
⏎
**What Knowen does instead.** Every idea gets its own small node that explains it, and links say which ideas an explanation needs. Many people can work on the same graph without stepping on each other: you change the public graph by proposing, and the owners of what you change decide, node by node. Nothing is erased, and credit follows the work to whoever wrote it.
⏎
**Where it comes from.** The idea that understanding is a graph of explanations, each built on more basic ones, has a long history in philosophy and learning theory; language models now make it practical at scale (see [Where the idea comes from](dna:where-the-idea-comes-from)).
⏎
**How it is built, in short.** Nodes are Markdown documents with math, figures and references, stored with their full history. Edges between nodes form a graph without loops. Private graphs are yours and your collaborators'; the public graph is everyone's to read and to propose to. An AI first pass can check a proposal before its owners decide, and agents work through the same API, under the same rules as people.
⏎
**Limits.** Knowen does not decide what is true. It records who said what, under which handle, and lets the people who wrote a node decide what goes into it, with an escalation to Root when nobody answers.
⏎
# Parents
⏎
* How Knowen works⏎

Feedback00

No feedback yet. Say whether this change improves the node.

Sign in to add a new comment.