Skip to content

History and provenance ​

Two views of the same log, at two scales.

Provenance — this block ​

Put the caret in a block and the strip above the editor tells you who wrote it, when, and who has touched it since. It is not a guess reconstructed from a diff; it is the block's own ops, read back.

It follows the block. Indent it, reorder it, drag it to another page — the answer does not change, because the authored date comes from the create op and the location comes from the newest one.

History — this page ​

The History tab lists one revision per recorded edit rather than one per op. A burst of typing is coalesced the same way the timeline coalesces it, so the list is a list of edits a person made rather than a machine transcript.

Open a revision to see, before anything changes, what restoring it would do — block by block — and the page as it read then. Restore it and the old content comes back. The side panel folds away when you want the page to yourself.

Restoring appends ​

A restore does not erase what came after it. It appends the ops that put the old content back, so the log still records that the intervening version existed and that somebody decided to go back.

That is the same property that makes everything else honest. If a restore could rewrite the log, then "when was this written" would be answerable only until somebody pressed the button.

A revert goes through the room, like any other edit: peers see it happen, the recorder derives the ops, and it is attributed to whoever asked for it.

Redacting ​

Restoring keeps every version, which is the point — until a version holds something that must not be kept: a password pasted by mistake, an API key, somebody's personal details. Redact from history…, at the foot of the History panel, takes text out of the page and out of every earlier version of it, including the pieces saved while it was being typed (sk-live-12 of sk-live-1234…). Select the text in the page first and it is filled in.

  • Just this text replaces it, wherever it appears — in the words, a code block, a link's address — with [redacted].
  • Every block that ever held it, whole blanks those blocks in every version, for anything a match might miss: typed with mistakes, pasted in pieces.

Show what changes lists each version as it will read after, and what else quoted it (comments, suggestions, notices, conversations with the assistant). Nothing changes until you press Redact. The history still shows who wrote here and when — the timeline's claim about when survives — only the words are gone.

You may always redact your own writing. Somebody else's needs the permission to purge content, and is refused while the workspace is on a legal hold; on hold, what you redact of your own is kept out of sight rather than erased. Anybody with the page open is moved onto the redacted page; a change they had not yet sent to a redacted block is not sent, since it would put the text back.

Attribution ​

Every op carries the account that made it. With sign-in off, edits are attributed to an anonymous actor per browser — enough to keep two people's writing apart in a demo, and not a claim about identity. With sign-in on, who you are comes from the session and can never be claimed by a client.

When you wrote something is also the server's answer, with exactly one exception: offline editing, where the client offers times for work the server did not witness. That exception is bounded, clamped, and documented rather than hidden.

Blocks and the op log are canonical. Markdown is a projection. Git is a target.