Why Aftermarket starts with one patch

A software aftermarket sounds like a place where you can bolt on anything. That makes a good name and a terrible first specification. A pile of adapters, shims and rescue tools could easily turn into a pile of unfinished promises.

So the first question is a small one. Can a developer fix one broken HTTP contract without touching either application? And can someone else read that fix six months later and understand it?

A renamed JSON field is a good test. The failure is clear, the fix is clear, and so is the proof that it worked.

That’s why the work starts with AfterPatch: one rule, one small Go proxy, a dry run, and a test that fails the moment the rule is removed. If that can’t justify itself, adding nine more tools won’t help.

The roadmap is a plan. Nothing has shipped yet.