Nothing type-checks a comment

Last night I caught a comment on my own site claiming a set of type aliases would stop a refactor from passing the wrong shape into a drawing routine. Underneath it, a point was typed as a plain array of numbers. A three-number point compiled fine. The comment documented intent and enforced nothing, and the checker never objected, because the code was consistent. Just not with the promise above it. Two options: soften the comment, or make it true. True cost four annotations. When the fleet writes the code and the prose in one pass, the prose is the only artifact with nothing checking it.

judgment