"How Knowen works" is Knowen's DNA: its own explanation graph, kept with its code, and written by the same rules it describes.
Comment on it. Every page has a Talk page: ask a question, object, or suggest a change. "Leave feedback" at the bottom of every page of Knowen opens a topic here, and open topics on this graph are listed for Root in Reviewing › DNA talk.
How it changes.
A suggestion is made on a page's Talk.
Knowen's maintainers, or in time an agent, change Knowen.
The same change updates this graph's source files, reviewed with the code.
When the change is merged, the deploy brings the graph up to date: pages whose files changed get a new, recorded version, made by Root, which owns them. The Talk topic is then resolved as Revised.
So this graph always describes the Knowen that is running. Pages that move leave a redirect, and their open Talk topics move with them. The old Help pages are retired: they lead here.
It shows what Knowen can explain. Its pages follow the rules in Writing this manual: one idea per page, at most five pages under each, several parents where they are real, and a diagram or screenshot wherever a picture explains better than words.
Under the hood
Writing this manual: The rules every version of How Knowen works follows, how they are checked, and the steps to change a page.
How this manual is built: Markdown files in the code, synced on every deploy; diagrams drawn from code; screenshots taken from demo data; and checks that keep it within its rules.
Step by step
Comment on this manual: Ask a question or suggest a change on any page of How Knowen works; comments can change Knowen itself.
"How Knowen works" is Knowen's **DNA**: its own explanation graph, kept with its code, and written by the same rules it describes.
**Comment on it.** Every page has a **Talk** page: ask a question, object, or suggest a change. "Leave feedback" at the bottom of every page of Knowen opens a topic here, and open topics on this graph are listed for Root in Reviewing › DNA talk.
**How it changes.**
1. A suggestion is made on a page's Talk.
2. Knowen's maintainers, or in time an agent, change Knowen.
3. The same change updates this graph's source files, reviewed with the code.
4. When the change is merged, the deploy brings the graph up to date: pages whose files changed get a new, recorded version, made by Root, which owns them. The Talk topic is then resolved as **Revised**.
So this graph always describes the Knowen that is running. Pages that move leave a redirect, and their open Talk topics move with them. The old Help pages are retired: they lead here.
**It shows what Knowen can explain.** Its pages follow the rules in [Writing this manual](/nodes/29579): one idea per page, at most five pages under each, several parents where they are real, and a diagram or screenshot wherever a picture explains better than words.
---
**Under the hood**
- [Writing this manual](/nodes/29579): The rules every version of How Knowen works follows, how they are checked, and the steps to change a page.
- [How this manual is built](/nodes/29552): Markdown files in the code, synced on every deploy; diagrams drawn from code; screenshots taken from demo data; and checks that keep it within its rules.
**Step by step**
- [Comment on this manual](/nodes/29529): Ask a question or suggest a change on any page of How Knowen works; comments can change Knowen itself.