My #1 goal in authoring PORTING.md is to help regular contributors to look beyond baked-in Linux x86_64 assumptions and anticipate what is needed to write portable C++ code. To that end, it needs be structured to help resolve CI pipeline breakage, whether that happens to their submission in the OS/X or Windows ports, or ARM 32 or 64, or Android or other future ports.