>"A spec that detailed would basically have to _be_ the code itself."
No it wouldn't. The specs are applied as part of the test suite. Please read up on code contracts to see how this is possible.
If you didn't like the link I shared before, here's a video:
Right, the problem though is that you seemed to be suggesting that the spec would be so detailed and complete that a script checking that the code submitted in the PR matches the spec would be good enough to decide all on its own, with no human intervention, whether or not the code can be merged:
> Commit access is completely open. If the code matches the expected style, doesn't cause the related tests to fail, and doesn't cause performance regressions it's accepted into the codebase. If it doesn't it's removed.
A spec that detailed would basically have to _be_ the code itself.