Dyad buying guide: bringing back an older draft should not erase the later alternative

Three version cards separate what is current from what stays in the history. Additive history keeps a later draft available for review without making it current.

Source: dyad.sh
October 19, 2026
2 min

In its February 4, 2026 explanation, Dyad describes its history as always additive. The versioning guide also separates restoring content from keeping history. For a local prototype, ask whether a later alternative remains available for review after choosing a working older state. The current view and historical catalog are not the same.

Make three fictional exhibit-label cards. Version A uses two columns. Version B clarifies the margin note but replaces two columns with one. The designer wants A's two columns as the current draft while keeping B's experiment with the note. On paper, C is a new record after restoring A's content. Give reviewers just the version log and three cards. Ask which is current and whether they can still find B's original note. If C shows two columns but B disappears, the content returned but the comparison was lost. These letters are illustrative, not product identifiers or a guarantee that an entire working state can be restored.

If you often revisit alternatives, preserving history helps later reviewers see why you went back. For a few static changes, named copies and a one-line change note may suffice. If your repository already has a complete record, compare handoff costs across two histories. This is only about local design content and version records, not settings, databases, external systems or deployment. No app is run or actual version restored.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:dyad.sh