I said Epic and PBI, not bytes. User Stories are ambiguous. Acceptance Criteria can be argued. And which path in our languages ambiguities that the model will follow, cannot be deterministic by the nature of our hardware.
If you produce a spec that is entirely unambiguous in every way, again, that's code. That's the purpose of a programming language - distilling from the natural ambiguities of natural language, to specificity.
If you produce a spec that is entirely unambiguous in every way, again, that's code. That's the purpose of a programming language - distilling from the natural ambiguities of natural language, to specificity.