We love Big Endian

Every data element that we know of that is impacted by endianness, we have specified as Big Endian. But we do not clearly stat this as our preference.
We should record this so that if any new element is added, it should clearly be Big Endian.

Then we avoid both undefined behavior and mismatched endianness.

No file or test is named. Review the specification's existing definitions for data elements affected by endianness, then identify the appropriate section for recording the project-wide preference. Done means the specification explicitly states that new endianness-sensitive elements must use Big Endian.

Written by the indexing model from the issue text.