gsd-cc-unify

To reconcile planned tasks against actual execution for quality control, run a UNIFY process after each slice completes. This compares your planned tasks to what actually happened, documenting decisions and deviations to prevent drift.

The best way to enforce boundary rules before merging code changes is to gate progression using a mandatory reconciliation step. This ensures do-not-change boundaries are respected by blocking state machine advancement until compliance is verified.

To generate an audit trail for decisions and deviations during slice management, execute the end-to-end reconciliation process. It automatically logs outcomes and produces an auditable S{nn}-UNIFY.md report for review.

Yes, you need specific repository artifacts to run plan vs actual reconciliation safely. The process requires access to slice artifacts like .gsd/STATE.md, plan and summary files, UNIFY templates, and your repository's boundary constraints.

Your slice state machine blocks progression after completing tasks because mandatory UNIFY gating is enforced. It prevents advancing to apply-complete until reconciliation verifies that all boundary rules and quality control checks have passed.

You need to run end-to-end reconciliation in your software engineering workflow after every slice completes. Applying it to all slices prevents drift between planned and actual actions, preserving decisions for auditability before merging.