Skip to content
Sovereign governance · dual gate

Two different yeses.

Gate 1 authorizes the spend of a fix, after a failing test exists. Gate 2 accepts the pull request. They are different people and different effects. Auto-merge can later skip only the second. Suggested graduation is 20 pull requests in that category, at least 90 percent merged unchanged, and no escaped regression. The pilot does not turn it on.

Gate 1 · Fix authorizationAfter reproduction

Approve the fix

The card shows the summary, the failing test, and the screenshots. Approve starts the fix run. Reject, or silence past the company's limit, hands the case to a developer with the evidence. A second click does not start a second run.

WhereThe thread

WhoA project manager

EffectStarts the fix

Does not open a pull request. Does not merge.

Final
Gate 2 · Pull requestAfter verification

Accept the pull request

Tests, scans, and policy have already run. Approve submits a GitHub review as the person who clicked. Request changes hands the case over with the pull request linked.

WhereGitHub

WhoA different approver

EffectThat person's review

Anadolu does not approve its own pull request.

Companies under change-management rules, such as PCI DSS or SOC 2, can stay pull-request-only and still approve from the thread.