principle-laziness-protocol

Prefer deletion over addition and make the smallest change that solves the problem. Keep call hierarchies flat, consolidate repeated decisions behind one source of truth, and question any task that threads a new signal through many layers.

Look for removals before additions and avoid elegant boilerplate that adds lines without solving the problem. Fewer changed lines reduce review burden and lower the risk of introducing regressions.

Flatten when answering a question about behavior requires tracing through more than three files or layers. A rich interface hiding substantial work is acceptable, but long chains of thin pass-through calls should be collapsed.

An abstraction is wrong when it only passes values through, duplicates a decision already made elsewhere, or leaks a representation across layers. Small leaks compound into permanent coordination costs, so remove them early.

Yes, the principles are language-agnostic since they operate on design decisions rather than syntax. Deletion-first thinking, flat call hierarchies, and consolidated decisions apply to any codebase regardless of stack.