Version History: Tracking Changes to a Saved Schema

Every saved schema (a “lineage”) can accumulate a linear history of versions, opened via History in the Collections panel. History is append-only: nothing is ever mutated or deleted one version at a time.

How versions are created

The first Save after a lineage starts tracking history lazily backfills its then-current content as version 1 — the immutable Source. Every subsequent save over that same schema (rather than Save as New) appends the next version instead of overwriting anything.

Reading the panel

Versions are listed newest-first, each with a per-version added/removed line delta so you can see the size of a change at a glance without opening it. A “Compare Source vs. [any version]” view shows the cumulative diff from the very first version to whichever one you pick — not just the step between two adjacent versions.

Reverting forward

Loading a historical version into the canvas and hitting Save again doesn’t rewrite history — it appends a new head version on top, effectively a “revert forward.” The only way version history is ever removed is as a cascade of deleting the entire saved schema (or its parent project/collection), never piecemeal.