Distinction
Bring something tangled. I’ll name 2–4 candidate distinctions — the axes that, if drawn, would change what the question even is. Not advice. Just the line.
A distinction isn’t advice. It isn’t a binary I’m importing for you. It’s an ambiguity already inside the language you used — two meanings smuggled into the same word, a question sitting partway between two registers. Nothing here is stored.
What this is good for
- Decisions that feel stuck — the “should I do X” question that won’t resolve. Often what’s stuck isn’t the answer; it’s that you’re asking two questions at once and they have different answers.
- Conversations you’ve been avoiding — the language you reach for when you rehearse the talk in your head usually contains the distinction the conversation actually needs.
- Feelings that don’t name themselves — an emotion that won’t settle is often two feelings overlapping. Naming the axis usually doesn’t resolve them, but it does let you stop fighting one with the other.
- Pieces of work that won’t finish — a draft you can’t close, an architectural call that won’t commit. Often the project is two projects that were running in the same file.
If what you brought is already clear, I’ll say so — one paragraph, no headers, no padding. The tool is calibrated against the failure mode of manufacturing a line where there isn’t one.