DNA: started from owners-decide.md

Root ·

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

Changes to the content

# Owners decide
⏎
**The rule.** A proposal can change several public nodes: edit them, or add nodes and connections under them. **Each changed node needs one answer from its owners** (see [Who owns what](dna:who-owns-what)): approve, or do not approve and say why. One owner's answer is enough, and the first answer stands. No answer is never a yes.
⏎
**Where you see it.** When a proposal changes your node, it waits for you under **Reviewing › Waiting for you**, with an action item in **For me**; **You answered** keeps the ones you decided. Reviewing shows you nothing else: your own proposals are under **Publishing**. Only **Root** sees the whole queue (waiting, back with the writer, decided), with whose answer each proposal waits for, so none is held up. The proposal page shows a **Who decides** list: each node, its owners, and the answer so far.
⏎
![Each owner decides for their own node: the approved part is merged, the rest comes back to you](media/owners-decide.svg)
⏎
**Your own nodes.** If you propose under the handle that owns a node, your change to it is approved by proposing. Under another handle it waits for the other owners, and you cannot decide on your own proposal.
⏎
**Nothing waits forever.** If a node's owners have not answered for a day, Root may decide on it too; the owners can still answer first.
⏎
**The result.** Once every node has an answer, the approved part is merged and the rest is left out: **Merged**, **Partly merged**, or **Not merged**. What was left out comes back to the writer, listed with why. The writer can also **merge the approved parts now**, leaving the rest out.
⏎
**How it is built.** Each proposal holds one approval per node it changes, with who decided, under which handle, and when. A job checks hourly for approvals waiting more than a day.
⏎
# Parents
⏎
* Combining graphs: Attach, Join, Merge⏎

Feedback00

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

Sign in to add a new comment.