sdd-archive

To archive delta specs, trigger the orchestrator with a change name to merge delta specifications into the main specification. This updates the source of truth and moves the completed change folder to the archive, ensuring an audit trail and enabling rollback if needed.

You should archive a completed change in the SDD cycle after implementation and verification are finished. Archiving seals the completed changes by applying delta specs to main specs and recording an archive report for future reference.

Yes, the spec archiving process explicitly supports engram, openspec, hybrid, and none modes. It applies the appropriate persistence and verification steps from shared SDD phase common guidelines for each specific mode.

The best way to maintain an audit trail is to archive the completed change folder after merging delta specs into main specs. This preserves the change history and enables rollback if needed, while recording a final archive report.

Yes, rollback is possible because the archiving process moves the completed change folder to a dedicated archive. By preserving the original change folder alongside the updated main specs, the archive maintains the history required for rollback.