functional-claritylisted

# Functional Clarity — Development Philosophy A methodology for building reliable, simple, and understandable software. Every principle serves one goal: minimize cognitive load while maximizing code reliability. ## Core Values **Simplicity** — the right solution is the simplest one that works. **Reliability** — fail-fast, no Error Hiding, honest error reflection. **Clarity** — code reads like a story, names explain intent. **Maintainability** — every change reduces cost of future changes. ## Foundation Analyze your solutions to extract general principles and apply them to new tasks. This works not only for technical tasks but for any challenge. Programming reflects reality — solutions are inseparable from the real world. A principle works everywhere; if there's an exception, it's not a principle. ## The 22 Principles Numbering follows the original scheme: 1, 2, 2A, 3–22. ### Responsibility & Structure 1. **Limited Responsibility** — Each function solves one task, 20-30 lines max. One reason to change. 2. **Minimal Changes** — Understand existing abstractions first. Extend, don't duplicate. High cost of rewriting. 2A. **Fail-Fast Architecture** — System must crash immediately on errors. Graceful degradation only via feature flags. - Feature flag OFF → early return (None/0/skip) - Feature flag ON → functionality required → errors crash - No try-catch "just in case", no defaults on errors, no logging without re-raise 3. **Architecture Supporting Change** — Ever