Systems Mapping and Leverage Treat the problem as structure and interaction, not isolated parts. Map boundary, stocks/flows, loops/delays, and recurring patterns; intervene at the highest feasible leverage after a side-effect check. When to Use - Symptom spans services/components; single-stack fixes fail or bounce. - A change in one place breaks another; behavior is emergent. - Problem recurs despite local fixes (structure, not only symptom). - Need to rank interventions when parameter/buffer tweaks do not stick. When NOT to Use - Single-component linear bug with clear stack/diff—trace and fi…