Apply PEP 20 to Codebases

Use PEP 20 as a set of engineering decision principles across languages: make behavior explicit, choose understandable structures, name concepts precisely, and retain justified complexity. Apply the principles to the target language and repository rather than translating code into Python style.

Operating contract

• Preserve observable behavior, public contracts, supported platforms, performance obligations, and the target language's idioms.
• Treat PEP 20 aphorisms as decision guidance, not executable requirements or an excuse to flatten every abstraction.
• Do not replace established project conventions, formatters, or architecture solely because another form looks more “Pythonic.”
• Naming changes must improve semantic precision and update all authorized consumers; aesthetic preference alone is insufficient.
• Practicality can outweigh purity, but the tradeoff must be explicit and supported by the actual constraints.