Write a spec, not a "bitstream guide," so that this problem doesn't happen in the first place? Or at least admit that your spec is not finalized and is, in real

Write a spec, not a "bitstream guide," so that this problem doesn't happen in the first place? Or at least admit that your spec is not finalized and is, in reality, a piece of crap that needs wide peer review first.