Authoring

Revision history and timeline

Every transaction is recorded. Fetch a document as it was at a revision or at a timestamp, list one event per transaction, or stream the raw transaction log — deletions included.

shipped

Three endpoints back the Studio's timeline: the document at a revision or a time, the event list for a document, and the transaction log as NDJSON.

Deletions appear in the event list, which sounds obvious and is the thing a naive implementation loses — once the row is gone, a history built from the current document cannot say it ever existed.