Versions are a pointer
Every publish is a new numbered version, and the address shows whichever one is live.
concept~2 minVerified v0.237.0
An artifact keeps numbered versions: v1, v2, v3. The server assigns the numbers and does not reuse them. Correcting a saved bundle means publishing another version.
One is live
The stable artifact address serves the published version. Publishing a new version normally moves that pointer to it. Restoring an earlier version moves the pointer without rebuilding the files. Later saved versions remain available to restore again.
Use Versions in the dashboard, or super_artifact_set with a version number. Owners and Editors can restore. The same slug updates an artifact within the key's workspace when that key has permission; it does not identify an artifact across all workspaces.
The data rules travel with it
The published version carries its own data policy. Restoring moves the live policy with the files. Previously collected responses remain; field names keep their first type for the artifact's lifetime, including names from deleted versions.
Restoring is not a way to erase responses or undo a data retention decision.
Looking and deleting
Non-live version files use a version-specific path, /_v/{n}/, with preview authorization. An agent can obtain an authorized preview through super_artifacts; guessing a version number grants no access. Use the returned preview URL without changing visibility.
Only an Owner can delete a non-live version from the dashboard. The live version cannot be deleted separately. Neither can a version pinned by an open or completed signature request. Deleted version numbers stay retired, while collected responses remain.
Editable document source
A document template can carry source that people and agents edit together. Source editing and its room are separate from the immutable published bundle; publishing makes the resulting files a new version. A signature remains tied to the requested version.
Check it worked
After restoring, the stable link shows the selected saved content and Versions identifies it as published. Verify its form against that version's policy before collecting new answers.
Next
Create artifacts, signatures and limits.