**One approval per node.** When a proposal is submitted (after the AI first pass), Knowen opens a row in `merge_approvals` for each public node it changes: the node it edits, or the node new nodes go under. Each row is decided by that node's owners, worked out by `NodeOwners`; one owner's answer is enough, and the first answer stands.

**Self-approval, kept honest.** If the writer owns a node the proposal changes, that approval is given at once, but only when the proposal was made under the handle that owns the node. Proposing under another of your handles never approves your own node, and you never decide on your own proposal (see [Your account and identity](/nodes/29515)).

**No answer for a day.** An hourly job (`MergeApprovalEscalationJob`) marks approvals still waiting after 24 hours as escalated (`escalated_at`). Root may then decide too, and is asked in For me; the owners can still answer first. Each decision is logged with who made it and under which handle.

**Applying the approved part.** When every approval has an answer, `MergeProposals::Pruning` drops the steps that depend on a node that was not approved. A new node with another approved parent keeps that parent and stays. A node left with no approved place is recorded on its step as **left out**, with the reason (`not_approved`, `lapsed`, `no_place` or `nothing_merged`), and the rest is applied (see [The integration plan](/nodes/29553)). The proposal is then **Merged**, **Partly merged** or **Not merged**.

**Back to the writer.** Left-out nodes stay in your private graph, unchanged. The proposal page lists them with the reason, and **Propose them elsewhere** starts a new merge with just those nodes. The writer can also **merge the approved parts now**, and what still waits then lapses.

---

**Part of** [Owners decide](/nodes/29512) and [A proposal's life](/nodes/29513): all its parents are equal.