Are justifications / rationales in focus of the spec?

The spec states:

This document attempts to specify Markdown syntax unambiguously.

It has come up in the issue tracker that explanations on why a certain syntax was chosen might be interesting for the reader (#94). They might also be helpful for future development of the syntax, because they enable tracing syntax back to specific use cases as in requirements tracing (#24). Are these within the focus of the spec or should they be collected elsewhere?

I can’t speak to the details, but as far as I understand, the team has been using BabelMark a lot to find the consensus amongst markdown implementations, and then codified the consensus into the spec.