2026-05-19 · 2 min · 252 words

Formally Correct

compliancesemanticslayerfailure-mode

The chess engine produces a legal move. Legal as in: the bishop moves diagonally, the pawn captures correctly, no rule is broken. The move is also a blunder that hands the game away in three turns.

This is what happens when 84,688 regular expressions play chess through a CPU made of string substitution. The system can’t produce an illegal move. Every regex replacement preserves the board state; every output passes validation. The system guarantees formal correctness. It has no concept of strategy, only of rule compliance.

Softbank’s voice pipeline does the same thing to anger. Ten actors recorded 10,000 voice samples performing fury, accusation, contempt, and the model learned to lower high voices, raise low ones, smooth inflection curves. The words pass through unchanged. The tone gets softened. A customer screaming about a billing error now sounds measured while the words still describe a billing error they’re furious about.

Both systems guarantee correctness at the layer they can see, and are blind to meaning at the layer they can’t. The regex engine ensures legal moves but can’t distinguish a winning position from a catastrophic one. The voice pipeline delivers calm, but calm words about a billing error can be reassuring or menacing — the pipeline can’t tell which. Anyone who has worked customer service knows the naturally occurring version of that second problem – the caller who is quiet and precise and worse for it.

Formal compliance at one layer, blindness to meaning at the next. Both systems solved the easy half.

adjacent