DNA: started from merge.md
Root ·
Started from docs/dna/merge.md in the Knowen repository: How Knowen works is kept with the code.
Changes to the content
# Merge: fork, edit, merge back ⏎ **The three moves.** 1. **Fork.** **Edit** on a public node you don't own, **Suggest edits**, or **Prepare a merge** from your own graph makes a private copy of the public nodes, your fork. Prepare a merge first matches your nodes to public nodes that cover the same idea, and lets you mark each one new or left out. 2. **Edit.** Your fork is a private graph: edit it with the full editor, and add nodes where something is missing. Your own matching nodes are shown beside the editor, to fold in. The public nodes don't change. 3. **Merge back.** **Propose merge** submits the fork. Proposing submits: there are no draft proposals, and the text is frozen as submitted, so the owners decide on exactly this version. ⏎  ⏎ **What happens next** is in [A proposal's life](dna:a-proposals-life): an AI first pass, then the owners of each node it changes decide. ⏎ **Owners skip all this.** If you own a public node (you wrote it, or your edit to it was merged), **Edit** changes it directly, recorded in its history. ⏎ **How it is built.** A proposal holds an integration plan of steps: edit an existing node, create a new one, connect two, attach the original graph. It is checked against the public graph before submission, and applied in one transaction when the owners have decided. ⏎ **Undo.** A merge can be rolled back whole or change by change; nothing is erased. ⏎ # Parents ⏎ * Combining graphs: Attach, Join, Merge⏎
Feedback00
No feedback yet. Say whether this change improves the node.
Sign in to add a new comment.
