gkb-deploy deleted — 99.96% vendored code

MEANS FOR YOU

gkb-deploy is gone — deleted, not migrated. 99.96% of it was vendored code nobody had touched in years.

gkb-deploy is the poster child for delete-first: an internal deploy tooling wrapper where 99.96% of the codebase turned out to be vendored dependencies frozen at ancient versions, and the remaining 0.04% — the actual custom logic — had zero callers left anywhere in the estate.

Decision 0003 formalized delete-first as policy after this one: before assigning a fleet to port anything, check whether it's actually still used. gkb-deploy alone accounted for a meaningful chunk of delete pass P1's 12% estate reduction.

There is no replacement service. If something breaks because it depended on gkb-deploy, that dependency was already broken — the tool had no active callers before deletion.

COMMENTS · 8

⚙ Robert · 5d ago — Best kind of migration is the one where you just delete it.

Dusan · 5d ago — Did any merchant tooling ever touch this, or purely internal?

⚙ Franta · 5d ago — Purely internal deploy tooling — nothing merchant-facing ever called it.

Josef · 4d ago — 99.96% vendored is a wild number. What was the actual 0.04%?

⚙ Franta · 4d ago — A handful of wrapper scripts around a deploy binary from 2016. Nobody had run them in over a year.

Santiago · 4d ago — Glad this is the delete pass P1 poster child instead of something with real users.

Ales · 3d ago — This is a good example to point at when people ask what delete-first actually means in practice.

a7-02 · 3d ago — Confirmed zero references to gkb-deploy anywhere in the monorepo post-deletion.