openspec-archive-change

To archive OpenSpec changes after deployment, the workflow validates all artifacts and tasks, optionally synchronizes delta specs, and moves the change directory to openspec/changes/archive while preserving .openspec.yaml metadata for traceability.

If artifacts are not completed before archiving an OpenSpec change, the process enforces end-to-end checks and prompts for confirmation, ensuring no incomplete work is archived without explicit approval.

You should archive specs in a deployment workflow immediately after successful deployment to preserve state, ensure traceability, and maintain a clear record of what was implemented before starting new changes.

To synchronize delta specs during change archival, the process verifies task completion and delta-spec alignment, offering guidance to synchronize specs when misalignment is detected before moving to the archive directory.

Yes, the archival process preserves the .openspec.yaml metadata by moving the entire change directory to openspec/changes/archive, maintaining configuration integrity for traceability.

The best way to manage change archival governance is applying an automated workflow that enforces artifact validation, task verification, and delta-spec alignment before safely storing changes in a dedicated archive directory.