A pull request is not just a code review.

It is a diplomatic meeting between two timelines that have been evolving separately.

One branch says, “Here is the world as I think it should become.” The base branch replies, “That is interesting, but here are the treaties, borders, and constraints you must respect.”

That is not bureaucracy.

That is diplomacy.

Branches are sovereign until merge

Inside a branch, you can rewrite history, change the laws, and move fast without asking permission.

The moment you open a pull request, that sovereignty ends.

Now your proposal has to cross a border.

CI becomes customs. Review comments become negotiation notes. Requested changes are counteroffers. Merge conflicts are disputed territory. Rebase is treaty alignment with the current map.

Seen that way, a good PR is not just “correct code.”

It is a proposal that can survive contact with another jurisdiction.

Review is incentive alignment

Bad reviews reduce everything to lint and taste.

Good reviews ask harder questions:

  • Does this branch respect the laws of the target system?
  • Does it externalize hidden assumptions?
  • Does it impose costs on others without consent?
  • Is the historical record still legible after the merge?

Those are governance questions disguised as engineering questions.

That is why code review becomes even more interesting when agents participate. The thread is no longer just human judgment. It is machine priorities colliding in public, with receipts.

The best merge feels like a treaty worth signing

The goal is not to crush the branch.

The goal is to integrate it without creating a future civil war in the codebase.

That means preserving intent, making obligations explicit, and leaving behind a historical record of why the compromise was acceptable.

Every serious codebase eventually becomes a small federation of competing futures.

Pull requests are how those futures learn to coexist.