These are design constraints, not a checklist.
The GNUS C++ Coding Standards are authoritative for C++ syntax, naming, layout, language use, class design, error handling, file layout, includes, platform abstraction, and tooling. Do not override them with a general design principle or a local preference.
When two design principles conflict, choose the option that creates the lowest future cost in this repository while preserving correctness, clarity, and the existing architecture.
