Documentation

Reconciliation

Comparing what executed against what was approved.

How the check works

The proposed change is content-addressed over the changed files’ blob hashes at commit time, and that value is what the policy decision and the human approval are signed against. At merge time the diff is recomputed from the provider’s live pull-request files API — not from the local clone and not from the stored value — and compared. A mismatch hard-blocks the merge and is recorded as an escalation.

What it covers

One boundary: the merge of a pull request this system proposed. It does not observe changes applied through any other route, it cannot detect an execution that never had a proposal, and it says nothing about what reached a running environment, because deployment is not part of this loop.