Coding Standards

Build correct by construction. A principle applies when the change introduces or alters the concern it governs. Apply it across the change’s full semantic surface—contracts, behavior, data flow, state, effects, and verification—but do not introduce machinery for absent concerns. Follow compatible project conventions, containing incompatible conventions at their seams rather than copying them inward.

Principles

1. Repository before invention

• Inspect existing contracts, modules, adapters, tests, and dependencies before introducing a library, pattern, module, or seam.
• Make the smallest coherent improvement.
• Speculative abstractions and migration, rollout, or compatibility machinery require a concrete current constraint or explicit user intent.

2. Parse, don’t validate