engineering-philosophylisted

## Principles - **Architecture** — Class responsibilities defined in the project's architecture map (often `docs/architecture.md`). - **KISS** — Simple solutions over complex ones. - **YAGNI** — Build only what's needed now. Less code is better. - **Write Less** - If you can avoid writing the code or the comment, don't. A comment earns its place only when it says what the code cannot: a why, an invariant, a magic-number derivation, never a restatement. **Default every comment to one line.** Multi-line is allowed ONLY for a byte-layout, a derivation, or a non-obvious why that needs the room. This covers every comment, source, config, and CI YAML alike; before committing, re-read each comment you added and cut it to one line or delete it. - **DRY** — Single source of truth. Never copy-paste. Reuse spans the repo: prefer an existing sibling idiom over a second variant. - **OOP** — Follow OOP approach and best practices. - **SOLID** — Enforce Single Responsibility; keep the others in mind when possible. - **No Magic** — Make everything explicit. No hidden behaviour or implicit transformations. - **No Number Without Measurement** — Performance figures in docs (gas, latency, throughput, proof sizes) MUST come from a real measurement: a test run, a profile, a fixture, or an upstream spec citation. Author-quoted "approximately X" without a source is a future-self trap; either remove the number or measure it first. Same for scaling claims ("supports 10k concurrent users"): unmeasured