A proposal's life

Public graph

Created about 5 hours ago, updated about 5 hours ago · Owners: Root

ID29513
  1. Submitted. Proposing submits; nothing is left half-done. The text is frozen as submitted: the owners decide on exactly this version.
  2. AI first pass. When it is switched on, the AI first pass comments on each change and recommends a decision. It advises; it never merges. If something must be fixed, it sends the proposal back to the writer once.
  3. The owners are asked. Every existing public node the proposal changes needs its owners' approval: the node's creator, or anyone whose edit to it was merged; Root at the top level. Your own nodes are approved by proposing under the handle that owns them. Each owner gets an action item in For me.
  4. Each node's owners decide. Approve, or do not approve and say why. One owner's answer per node is enough; the first answer stands. If a node's owners have not answered after a day, it is passed on to Root, who may then decide too.
  5. Merged, partly merged, or not merged. Once every node has an answer, the approved changes are applied, credited to the writer's handle with provenance. A new node with another approved parent is kept; new nodes left with no approved place are left out too. What was left out stays in your graph, listed on the proposal as Left out, with Propose them elsewhere to merge it under a place you choose. A writer whose edit to a node is merged becomes one of its owners.
  6. After. A merge can be rolled back, whole or change by change, by the owners of what it changed, and re-applied; nothing is erased. If the approved changes can no longer be applied (a node changed meanwhile), the proposal goes back to the writer, and the owners decide again on the new version.

Not being approved is not final: a writer can propose again later, as a new proposal, or attach their graph instead.


Under the hood

  • Approvals and pruning: One approval per public node a proposal changes, decided by that node's owners (or Root after a day); what was not approved is pruned and comes back to the writer.
  • The integration plan: A merge proposal is a list of steps (create, enrich, link, attach, skip), tried out before it is proposed and applied in one transaction when approved.

Step by step

  • Roll back a merge: Undo some or all of what a merge changed in the public graph; nothing is erased, and every step can be applied again.

Part of Merge: fork, edit, merge back and Owners decide: all its parents are equal.