Asset lifecycle API

Archive is a reversible native withdrawal, not permanent deletion. Project administrators can archive Workspace GeoTIFF assets and restore a preserved revision as a new revision of the same identity. Source-managed connectors retain their own lifecycle. Curves and other types are not covered by this control.

In Workspace, open Data → Inspect → Asset lifecycle. Archive stops live following; old revisions remain available to authorized readers through revision history and exact export. To restore, open the archived catalog entry, choose a preserved revision (load older history if necessary), and select Restore asset. QGIS users must choose Check source / resume; pinned layers stay at their selected revision.

POST /api/maps/lifecycle and authenticated desktop POST /api/v1/connector/maps/lifecycle accept:

{"reference":{"project_id":"project","asset_id":"asset","revision":"4"},
 "action":"archive","restore_revision":null,"command_id":"unique-command-123456"}

Restore uses action: "restore", the current archive revision in reference, and an earlier available restore_revision. The request is bound to the account and command ID. Retry the exact body/ID after a lost response. Different input requires a new command. Concurrent changes reject publication; refresh and review rather than blindly retrying against a newer head. Administration is enforced in the native service as well as the gateway for Workspace archive/restore transitions.

The existing native deleted snapshot bit creates an unavailable head and emits the ordinary revision notification. There is no secondary lifecycle database. Earlier immutable snapshots retain CRS, units, masks and values. Restore records an exact historical input; its retained original file remains obtainable from that historical revision, not falsely attributed as a new uploader’s original file. Operation history records actor, request and completion independently of trace sampling, with ophiolite-asset-lifecycle/1 coverage.

An old client’s ordinary update cannot resurrect an archived asset: its expected revision no longer matches. Publishing a separate derived asset from an authorized historical snapshot remains possible. Archive does not revoke read permission or delete downstream results. Revocation independently prevents future server access; it cannot erase exported files. Permanent purge, retention scheduling and backend OSDU lifecycle qualification are not implemented by this feature.