openspec-archiving

To merge spec deltas into living documentation, you archive completed change proposals and automatically integrate the delta changes into the current living specification docs, ensuring the archived history stays in sync and preventing drift after deployment.

The best way to archive completed change proposals is using a deterministic workflow that moves the completed change folder to a timestamped archive, maintaining an immutable record and providing a clear rollback path for auditability.

You need to archive change proposals and update living specs when targeting deployment-ready changes and scenarios where specifications must be updated immediately after implementation to prevent documentation drift.

To prevent specification drift after deployment, you enforce a deterministic archiving workflow that merges delta changes directly into the living specification documentation, keeping the current specs and archived history perfectly synchronized.

Yes, you can roll back changes because the archiving process maintains an immutable archive with timestamped records, providing a clear rollback path even after delta changes are merged into the living specification documentation.

No, the archiving workflow requires no external dependencies to process spec deltas, relying entirely on a deterministic internal process for timestamped archiving, delta merging, and generating audit trails for living specification documentation.