openspec-archiving

To keep living specification documents in sync with deployed changes, archive completed change folders with a timestamp and merge ADDED, MODIFIED, and REMOVED spec deltas into the living docs after deployment.

The best way to archive spec deltas for release management is to copy completed change folders into an archive structure with a timestamp, preserving a traceable history of deployed requirements alongside the living specs.

Delta merge works by applying explicit operations for ADDED, MODIFIED, and REMOVED requirements from completed changes directly into the corresponding living specification documents with auditable traceability.

Yes, you need to validate living specs after merging documentation changes to ensure the structural integrity of the updated requirements and enforce a consistent archival workflow for release management.

Yes, you can use this approach to manage change documentation for software engineering projects, as it applies during development and release workflows to archive completed changes and merge spec deltas.

You should archive completed change folders instead of keeping them active after changes are implemented, tested, and deployed, ensuring the living documentation only reflects current system requirements.