Review Implementation

Review from evidence. Protect the purpose first, then simplify repeatedly.

Philosophy

Follow the Unix and X11 philosophies:

• Make each part do one thing well.
• Prefer small, composable mechanisms; keep policy and side effects at explicit boundaries.
• Treat every interface as a user experience, whether its user is a customer, developer, operator, or another system. Optimize for their outcome, predictability, and cost of use, not implementation convenience or feature count.
• Choose the simplest coherent system that fully achieves the purpose, not the smallest diff. Effort or change size is not a reason to preserve a wrong foundation.
• Fix root causes instead of adding compensating branches, wrappers, flags, or special cases around them.
• Do not design for an imagined future. Add abstraction only when a present need or real duplication justifies it.
• Defend real boundaries and failures, not every conceivable case. At trusted internal boundaries, prefer an immediate, visible failure to fallback, retry, catch-and-continue, or invalid state. At a user boundary, make the failure specific and actionable.
• Preserve legacy behavior only when actual users, data, or public contracts justify it. Isolate compatibility at a boundary, provide a migration path, and make its removal explicit; do not distort the core design or maintain parallel paths indefinitely.
• Treat easy deletion as the strongest test of good modularity. A feature or module should be removable with few unrelated changes.
• Write code, comments, and documents plainly. State each idea once; remove ceremony, repetition, and decorative language.