2026-08-10

Why oversight isn't an all-or-nothing choice

A backlog that grows faster than it shrinks can’t be solved just by hiring — every additional person raises coordination overhead before they add any throughput at all. The obvious alternative, handing off responsibility entirely, brings a different problem: whoever sees nothing before it happens has nothing left to decide either.

The question isn’t whether, but how much

Anvil Coder doesn’t answer this with a single switch, but with approval levels: how much oversight a team keeps is a per-project setting — from every action needs approval to only the consequential ones. Without a level set, a run goes through without waiting on a human at every step. The difference between the levels isn’t whether a team keeps control, but WHERE it exercises it.

The handoff point stays the same

Regardless of the chosen level, one thing doesn’t change: a result arrives as a pull request draft, not as an already-merged state. A human merges it into the main branch. That’s the point where every work step has already left its own commit, staying traceable no matter how tight the approval level was during execution.

What that means for the backlog

The real lever isn’t checking less, it’s checking somewhere else: not on every single line during execution, but at the handoff point, where a human would decide anyway whether a pull request gets onto the main branch. The execution shifts; the decision stays — and that’s exactly what separates delegated work from work that’s simply been handed away.