Pull requests that carry proof.
Every pull request carries the failure, the fix, and the verification evidence.
How it works
Open branch-only fixes with assessment, checks, and verification evidence.
Create a branch
The fix is isolated from main so branch protection, CI, and review rules still apply.
fix: guard cart against expired sessions
to200/fix-checkout → main
Commit the scoped change
Only files required for the fix are changed, with a concise explanation of the patch.
Open the PR
Reviewers get the production signal, likely cause, patch summary, and verification result in one place.
$ to200 pr open
default branch + PR
ci required
merge team-controlled
✓ Check results attached to the PR
In practice
What reviewers get
A narrow diff
The branch changes the files needed for the failure, not a broad refactor.
A repair narrative
Root cause, plan, and outcome are written in human review language.
A review boundary
By default, To200 stops at the pull request. Scale and High volume owners can deliberately enable merge-to-main, while branch protection, CI, and required reviews still apply.
FAQ
Questions, answered.
Why not push directly to main?
Protected branches, required reviews, and CI rules are production controls. To200 respects them by default and uses PRs as the normal handoff.
Who merges the pull request?
Your team does by default. Scale and High volume owners can deliberately enable merge-to-main; branch protection, CI rules, and required reviews still apply.