DNA: updated from attach-edges.md

Root ·

Updated from docs/dna/attach-edges.md in the Knowen repository: How Knowen works is kept with the code.

Changes to the content

# Attached graphs, under the hood

**Two kinds of edge.** Attaching under a public node adds a `VisibleEdge` from that node to your graph (or to a node inside it, with everything under it). The edge itself is what makes the graph readable by everyone; there is no separate flag to drift out of date. Attaching under a node of another private graph adds an `AttachEdge`, recorded with a `GraphAttachment` that keeps who attached it, when, and the note.

**Readers, not writers.** An attachment changes who can read, never who can write or who owns. Readers of the parent reach the attached graph read-only, and through it anything attached to it in turn: for private attachments a recursive query works out the graphs a person can read. Membership, permissions, the Trash, forks and search over a graph's own nodes ignore these edges, so attaching never moves your graph or adds it to someone else's.

**Showing and hiding.** Attached graphs are drawn with a dotted purple edge and their owners' handles. Each reader can hide them (`show_attached_graphs` in their settings, the **Hide attached graphs** link under a node's children) to read only the public graph.

**Detaching.** You can detach your graph at any time. The owners of the node it hangs under can detach it too, with a reason: the reason goes on that node's Talk page and to you, so the decision stays on record. Detaching removes the edge and nothing else.

**Attach in a merge.** A merge proposal may end with an `attach` step: once merged, your original graph hangs under the target, so readers can compare your version with what was merged (see [The integration plan](dna:integration-plan/nodes/29553)).

# Parents

* Attach

Feedback00

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

Sign in to add a new comment.