<!-- canonical: https://klappy.dev/page/canon/methods/using-ease-and-resistance-as-signals -->
<!-- content: klappy/klappy.dev@b750d7d3aa85a3e5ed6d1e2b24d63471f3df4bac -->

# Method: Using Ease and Resistance as Signals

> Resistance is often a classification error, not a lack of insight.

## Description

This method treats the subjective experience of writing as a diagnostic signal. Difficulty or friction does not always mean the idea is wrong. It often means the idea is in the wrong container.

---

## Ease as a Signal

When writing begins to feel as if it is "writing itself," this usually indicates:

- the abstraction is correct
- the category fits the insight
- the system no longer resists expression

Ease does not mean correctness. It means alignment.

---

## Resistance as a Signal

Persistent resistance often indicates:

- mixed narrative forms
- authority leaking into the wrong container
- an attempt to make one document do multiple jobs

Do not push through resistance by force. Reclassify instead.

---

## Reclassification Loop

When resistance appears:

1. Stop writing.
2. Ask which container is being used.
3. Ask which container the insight actually requires.
4. Move the content before continuing.

This prevents overfitting and mythology.

---

## Constraint

Ease and resistance are signals, not validators.

They guide *where* to write, not *what* to conclude.
