Impasse

An impasse is a reason, from one participant’s point of view, that a discussion is not working. It is not a disagreement about the topic itself but a complaint about the discussion process: that the method, format, pacing, or good faith of the exchange has broken down. CF treats raising an impasse as a metacommunicative move that takes priority over the original subject — because if the process is broken, continuing to argue the topic just buries the real problem.

Crucially, an impasse is judged by the person who has it. If you think the discussion is failing, that is itself a fact about the discussion that the other party should address, not silently work around. CF warns that quietly “fixing” things while pressing on at the original level reads as ignoring your interlocutor’s stated concern. The correct response is explicit: name the problem, propose a way forward, and confirm agreement before resuming.

CF resolves impasses by switching to a higher meta level — discussing the stuck discussion rather than the topic. You can hit an impasse while resolving an impasse, and move up again; higher levels are deliberately less ambitious and so easier to settle (“given we’re stuck on everything, what minimal thing should we do?”). Recurring impasses form impasse chains, where the most recent impasse is addressed first. This makes impasses part of Paths Forward: a way to keep error correction alive instead of letting a discussion die unaddressed, and they slot naturally into structured idea trees as nodes about the debate itself.