Past versions

Every completed generation, revision, and added service enters your Workflow Map's history. A revision is never destructive: the map you are working from is always the newest complete version, and what came before stays traceable.

Finding the history

At the bottom of the business detail, "Show past versions" lists every version with its date, its workflow count, and whether it was a revision. The current map is always the newest complete version.

What each version offers

Each past version has View and Copy. View opens the version so you can read it exactly as it was generated. Copy takes its full content to your clipboard.

Versions with a predecessor also carry two more actions: "Copy changes" and "Export changes .md". These give only what that version changed from the one before it, using the same comparison that powers changes-only exports.

How long versions are kept

Each map keeps its three most recent revisions. Older revisions may be removed. Your current map is never affected. If a version holds content you want to keep long term, export it: an export is yours permanently.

Why this matters

If a revision moves the map in a direction you did not intend, the prior version is still there, readable and copyable. You can compare a version against its predecessor, recover content from an earlier draft, or trace how the map evolved across recent revisions.

The history is part of the deliverable. Structure you can audit, at every recent point in time.