History, versions and rollback

Public graph

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

ID29539

History. Every commit is a version of the node, with its title, its description (required on public nodes), who made it and when. History on a node lists them; open one to see a word-by-word diff, with older and newer versions one click away. Changes can be commented on.

Merges. A merged proposal records exactly what it changed: new nodes, edited nodes, new connections and the attached graph. Edited public nodes carry provenance: a note that names the contribution, its writer's handle, and the private node it came from.

Rollback. A merge can be rolled back, whole or change by change. An edited node gets its earlier text back as a new version; a new node goes to the Trash with what hangs only from it; a new connection is removed. A change someone else edited since is a conflict, kept unless restored on purpose. Rollbacks are made by the owners of what the merge changed; the writer can roll back their own merge, and Root can roll back anything. A rolled-back merge can be re-applied.

How it is built. Versions are stored in full, so any version can be shown and compared. Rollbacks are themselves recorded, in the proposal's log and in each node's history.

Nothing is erased. Even a rollback is a new version.


Under the hood

  • Nodes, edges and versions: How a graph is stored: nodes with Markdown text, typed edges between them, and a version for every commit.

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 Writing and editing and How knowledge improves here: all its parents are equal.

See in the graph Search below

Parents2More general nodes this one belongs to

Children22 nodes that explain it further