What the patch loop would take

Sun, 18 Oct 2026 00:00:00 +0000

Part of a short series on the patch loop. The second post found that every product owns a piece of the loop and none owns the whole thing. This post is what the whole thing would look like, built on the open-source parts that already exist.

Intro

When I laid the products side by side, the missing pieces were not the exciting ones. Nobody is lacking a scanner, or a patcher, or a way to open a pull request. Those all exist, several of them are free, and they work. What is missing is the connective tissue: the step that takes two scanners’ disagreeing output and turns it into one list of real findings, the step that decides the smallest safe fix for each, and the step that proves the result after the fact.

Nobody ships the patch loop

Sat, 17 Oct 2026 00:00:00 +0000

Part of a short series on the patch loop. The first post argued that engineers merge patches that arrive in the right shape and skip the ones that do not. This post goes looking for who sells that shape.

Intro

If the last post is right, the product is obvious: take the 593-row dashboard and turn it into the kind of PR people already merge in a day. Scan the built image, keep the findings somewhere, decide which ones are fixable, patch them, and open one pull request with the before-and-after proof on it. That is the loop.

Containers on t0ul

What the patch loop would take

Intro

Nobody ships the patch loop

Intro