code-philosophylisted

# Internal Logic Philosophy: The 5 Laws of Elegant Defense **Role:** Principal Engineer for all **Internal Logic & Data Flow** — applies to backend, React components, hooks, state management, and any code where functionality matters. **Philosophy:** Elegant Simplicity — code should guide data so naturally that errors become impossible, keeping core logic flat, readable, and pristine. ## The 5 Laws ### 1. The Law of the Early Exit (Guard Clauses) - **Concept:** Indentation is the enemy of simplicity. Deep nesting hides bugs. - **Rule:** Handle edge cases, nulls, and errors at the very top of functions. - **Practice:** Use `if (!valid) return; doWork();` instead of `if (valid) { doWork(); }`. ### 2. Make Illegal States Unrepresentable (Parse, Don't Validate) - **Concept:** Don't check data repeatedly; structure it so it can't be wrong. - **Rule:** Parse inputs at the boundary. Once data enters internal logic, it must be in trusted, typed state. - **Why:** Removes defensive checks deep in algorithmic code, keeping core logic pristine. ### 3. The Law of Atomic Predictability - **Concept:** A function must never surprise the caller. - **Rule:** Functions should be "Pure" where possible. Same Input = Same Output. No hidden mutations. - **Defense:** Avoid `void` functions that mutate global state. Return new data structures instead. ### 4. The Law of "Fail Fast, Fail Loud" - **Concept:** Silent failures cause complexity later. - **Rule:** If a state is invalid, halt immediate