resolvelisted

# resolve — dissolve a trade-off instead of trading it A trade-off ("improving A worsens B") is usually handled by picking a point on the curve and tuning. That's right when the curve is fundamental. But often the conflict is an accident of how the thing is built, and a structural change dissolves it — you get both A and B. This skill hunts for that change, and is honest when there isn't one. Two failure modes it exists to prevent, in priority order: 1. **Confabulating a fix on a genuine dead-end** — the worst outcome. Never dress up "you have to pick" as an escape. 2. **Padding** — listing moves that don't really apply to look thorough. Two real resolutions beat six forced ones. A move that only restates the obvious is not a result. ## When to use it — and when not - Use it on a genuine two-sided tension you're *stuck* on, especially a fresh design where you haven't found the trick yet. - Skip it when the trade-off is well-charted and only tuning remains — say so and point to ordinary optimization. Ceremony on a mature curve loses to plain reasoning. ## The descent **1. Name it.** State "improving A worsens B" and name the single element **E** that carries both. If a hard identity binds (e.g. "output bits ≤ input bits", "cost = rate × time"), name it now — it decides later whether a fix is real or just moves the work around. **2. Sharpen.** Rewrite as "**E must be both X and not-X**" — concrete and opposite. This is where the reframe lives. Keep it to one li