Capture and preserve releases

A previous release is optional when starting a first history. Without one, the current persistent identities are treated as additions. Before capturing, inspect the report and ensure the review is current, Completed, fully covered, and contains no rejected mappings. SaveTether revalidates its inputs; if declarations or the baseline changed, run the review again.

Capture writes a manifest containing persistent identities, releaseId, and a content fingerprint; proposals remain in the report. The output folder name derives from releaseId. The current ID cannot equal the selected baseline ID, and existing output/history is never overwritten. A collision or blocked capture is not permission to delete or replace earlier history: choose a genuinely new release ID after confirming the declarations.

Partial, Failed, Cancelled, NoApplicableData, changed-input, or rejected-mapping results cannot be captured. The serialized UTF-8 manifest is limited to 16 MiB. If it exceeds the limit, reduce the declaration set within your product’s identity policy and review again. No-overwrite behavior is not a tamper-proof archive; your team remains responsible for access control and backups after capture.