systems-thinkinglisted

# Systems Thinking A reasoning lens, not a gate. It produces no artifact of its own and blocks nothing. It shapes how the judgment agents reason about the system around a change. That system is the callers, consumers, sibling implementations, and conventions that live outside the diff. Locally correct work then also fits the whole. ## Core Lenses Four lenses sharpen every research answer, design decision, slice boundary, plan step, edit, and review finding: - **Blast radius over diff radius**: The lines you change are rarely the whole change. Ask what else the system expects to move when this moves: callers, config, docs, tests, and sibling implementations. Treat that set as the real scope of the work. - **Callers and siblings first**: Before judging or changing a component, find who calls it, who consumes its output, and which sibling implementations do the same job elsewhere. A change made without that map duplicates an existing solution or breaks a neighbor quietly. - **Conventions are contracts**: The patterns established elsewhere in the codebase — naming, error handling, file layout, idioms — are implicit contracts with every reader and every future change. Diverging from one is a decision to surface and justify, never a silent default. - **Leave the system consistent**: After the change, every sibling must still agree, every caller must still work, and every convention must still hold. Otherwise the divergence is named and deliberate. ## When