Developer finds 5 false claims in own spec; a single tag byte broke a key encoding rule

A software developer audited 18 formal claims in their own project specification using an automated checker that resolves terms against actual definitions. Of the 18 claims, 9 were valid, 5 were invalid, and 4 returned an unknown result. The most concrete failure involved the encoder being labeled a homomorphism, a mathematically strong claim that a single prepended tag byte renders false for every input. Other errors included conflating related but non-interchangeable graph concepts like DAGs, covering relations, and transitive closures, as well as a direct contradiction between lens round-trip laws and a statement 130 lines away in the same document. The developer argues that retaining 'unknown' as a distinct result category is critical, since collapsing it into 'invalid' would misrepresent assumptions as verified facts.