DNA: started from suggest-an-edit.md

Root ·

Started from docs/dna/suggest-an-edit.md in the Knowen repository: How Knowen works is kept with the code.

Changes to the content

# Suggest an edit to a public node
⏎
**Goal:** improve the text of a public node someone else owns.
⏎
**Before you start:** if you own the node, just edit it ([Edit a node and commit](dna:edit-and-commit)). Otherwise every change goes through a fork and the node's owners decide.
⏎
1. Open the public node and choose **⋮ › Suggest edits** (on a node you don't own, **Edit node** does the same).
2. Knowen proposes a fork: a private copy of the node, and of the nodes under it you tick. Untick what you won't change, name the fork, and click **Fork**.
⏎
   ![Fork “Energy”: choose the nodes to copy, name the fork, and Fork](media/suggest-an-edit.webp)
3. Your fork opens as one of your private graphs. Edit its nodes and commit as usual; the originals don't change.
4. A band at the top of the fork shows **Your edits to** the original and what changed in it since; **Compare** shows both side by side.
5. When you are ready, click **Propose merge** in that band. Say what you changed and why, and submit.
⏎
**What happens next.** The proposal lists each edited node with a word-by-word diff. After the AI first pass, the owners of each node you changed decide, each for their own node. If they approve, your text becomes a new version of the public node, credited to you, and you become one of its owners.
⏎
**Undo.** Delete the fork any time before proposing; the public graph never knew about it. After proposing, **Withdraw** on the proposal page cancels it.
⏎
# Parents
⏎
* Merge: fork, edit, merge back
* The public graph⏎

Feedback00

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

Sign in to add a new comment.