2 min read

Reconciliation Closure

A reconciliation closureis an atomic record of everything a sync run produced and how the gate evaluated it. Every successful sync creates a closure; the project’s environment tracks three pointers against that closure set:

• current— what is deployed right now.
• desired— what should be deployed. When this matches current, the project is converged.
• last known good(LKG) — the most recent closure that was complete and promotable. Used as the rollback target and as a baseline for the last_good_diff syndrome in the gate engine.

When the gate blocks a breaking change, the desired pointer advances but current and LKG stay put — the project is now diverged. The dashboard surfaces this state and offers a rollback path: restore current and desiredto LKG without touching LKG itself (so a future rollback is still possible). The LKG pointer is structurally protected — the rollback code path cannot touch it by construction, not by convention.

Full documentation coming soon. The architecture is defined in ADR-010: Reconciliation Closure System Architecture (including the two-function pointer update model setClosureRef / setClosurePointersOnlyand the April 13 race-condition fix). User-facing reconciliation docs — convergence status UI, rollback flow, environment promotion — will expand here once the corresponding surfaces stabilize.