The DEX was not a HEX. Why deterministic artifacts depend on deterministic classification

In a previous article, I introduced DEX — deterministic transformation artifacts. https://dev.to/crevilla2050/what-the-hex-is-a-dex-introducing-deterministic-transformation-artifacts-397d "What the Hex is a DEX? Introducing Deterministic Transformation Artifacts" At the time, it looked like magic: scan a codebase generate a plan package it sign it apply it undo it No chickens required. No rituals. No late-night debugging séances. Clean. Surgical. Almost suspicious. But there was a missing piece. DEX looks like a packaging format. It isn’t. The Misunderstanding It’s very easy — dangerously easy — to think: “DEX is just a better codemod format.” That’s how you end up in trouble. DEX is not about how transformations are stored. DEX is about whether those transformations make any sense at all. The Real Problem Was Never Extraction Let’s rewind. You want to internationalize a codebase. You run a string extractor. And it obediently hands you… everything. "btn btn-primary" "SELECT * FROM user