Opening scene
Two teachers look at the same student on the same day.
The first says: "There's a rotation in your right hip, which is why your left side is more restricted. There may be a small shift in your sacroiliac joint."
The second says: "I can see a difference between your right and left side. I don't know where it comes from. Let's try these two things and see which one changes it."
Now ask the student: which one sounds more knowledgeable?
Almost everyone picks the first. The first teacher used more terms, spoke in more detail, and proposed a mechanism. The second said "I don't know."
And yet the first teacher spoke as if they had measured three things they hadn't measured. The second said what they saw, as far as they saw it, and offered a path forward.
This lesson is about exactly this reversal: detail sounds like certainty. And that feeling leaves a real mark on the student.
What this lesson covers
First we'll work out why detail sounds like certainty — the mechanism of the fallacy. Then we'll look at its three separate sources — one comes from language, one from the limits of measurement, one from the teacher's own position. After that we'll talk about the mark the fallacy leaves on the student; this mark has a name, and undoing it takes far longer than saying it did. Then the most useful part: a setting that lets you measure how much a sentence is claiming. In the master layer we'll see how "I don't know" is actually said, because a badly said "I don't know" destroys trust. We'll work through sixteen examples. By the end of the lesson, you'll be able to hear the claim level of your own sentences.
Starting point
Y1's sixth principle taught you to question the source of a claim. This lesson takes that principle one step further: alongside a claim's source, you also ask how much it claims.
The fallacy's mechanism is simple, which is exactly why it goes unnoticed. The more parts an explanation contains, the more things have to be true for it to be true — so the more detail there is, the lower the odds that the explanation is correct. But what you hear is the opposite.
Let's make this concrete with an example. "This restriction is coming from the hip" is one claim. "This restriction is coming from tension at the front of the hip, and because it tilts the pelvis forward, the low back is affected too" is four claims. The second sounds far more knowledgeable. But the odds of all four being true at once are lower than the odds of the single claim being true.
Mechanism
The fallacy has three sources, and each one feeds from a different place.
First source: language
The language of anatomy itself produces certainty. A structure's having a name implies that the structure's boundaries are settled — but as we saw in Y2.01, that boundary is a decision made by the hand that separated the structures.
When a Latin or technical term is used, discussion gets harder too. A student who runs into a word they don't know doesn't ask a question.
Second source: the limits of measurement
The list of things a teacher can measure in class is short. They can roughly see how far a movement goes. They can see a difference. They can hear what a student reports.
The list of things they can't measure is much longer: bone angles, tissue condition, how much each muscle is contributing, the inner surface of a joint. None of these is determined by eye, by hand, or by a correction.
Third source: the teacher's position
This one is the hardest. A teacher is expected to have an answer, and saying "I don't know" feels like a loss of competence. The fallacy usually doesn't come from bad intent, but from this pressure.
There's a distinction that eases this pressure, and it's easy to learn: not knowing the reason and not knowing what to do are not the same thing. A student usually wonders about the reason, but what they're actually asking for is to learn what to do. If you can give the second, not knowing the first doesn't leave a gap.
The name of the mark
Now, the fallacy's most expensive consequence.
The damage these labels do isn't only that they're wrong; they change behavior. A person who's been given a label protects that area, avoids those movements, and the avoidance lowers their capacity. So the label becomes self-confirming.
Measuring how much a sentence claims
Now the constructive part. You can check your own sentences with a setting.
The observation level states only what's seen: "your right side goes less far than your left." At this level, the margin for error is lowest.
The probability level proposes a candidate: "this difference might be coming from the hip." Notice the word — might.
The mechanism level builds a chain: "there's tension at the front of the hip, it tilts the pelvis, and that's why the low back is affected too." This level gives the most information and is wrong the most often.
The rule is this: use the mechanism level only after you've confirmed it by trying something. Before confirming it, stay at the probability level.
Claiming little has its own limit
So far we've spoken in one direction only, and as it stands, this lesson could be misread. Claiming little has its own way of failing too.
When a situation involves safety, cautious language isn't a virtue, it's a flaw. "I don't know, let's try" is the right sentence in the face of a restriction; it's the wrong sentence in the face of a symptom that hurts at night, doesn't ease with rest, or is getting rapidly worse. What's needed there is a definite sentence: this is outside my scope, you need to get this checked.
The distinction is this: the claim setting applies when you're talking about an explanation. It doesn't apply when you're talking about a boundary. Stating your scope isn't a claim, it's information.
Reading the examples
The same trade-off shows up across all the examples: the sentence that's convincing in the short run costs a lot in the long run.
A detailed explanation makes that moment of the lesson go well. The student feels satisfied, the teacher looks competent. The cost shows up later — a wrong mechanism sends the work in the wrong direction, or a label gets carried for years.
The second pattern is more subtle: sentences that claim little bring the student into the work. "I don't know, let's try" makes the student a partner in the trying. "Because of this" leaves the student a spectator. This is a difference less about transferring knowledge and more about distributing authority.
And a third: the fallacy's victim isn't only the student. A teacher who believes their own explanation stops testing it. The quietest cost of speaking with certainty is that the teacher's own learning stops.
Master layer
How "I don't know" is said matters as much as whether it's said at all.
A bare "I don't know" leaves the student stranded, and rightly costs you their trust. The form that works has three parts: say what you know, say what you don't know, then give the next step.
"I can see a difference between your right and left side. I don't know where it comes from. Let's try these two things." The second teacher in the opening scene did exactly this, and the third part of their sentence is what kept them from sounding helpless.
The master's second subtlety: when they notice they've said something wrong, they go back and correct it — even if three months have passed. A correction raises the value of every other sentence that teacher has said — because the student now knows the teacher will speak up when they're wrong.
Common mistakes and misconceptions
Common mistake"A detailed explanation is more reliable."
The more detail there is, the more parts have to be true, so the odds of the whole explanation being correct go down.
Common mistake"A teacher can determine alignment by looking."
Inter-examiner agreement on these hands-on, visual assessments is generally low. The difference you see may be real; its interpretation isn't certain.
Common mistake"Looking certain gives the student confidence."
It does, in the short run; in the long run it produces dependency. What produces lasting trust is knowing that you'll speak up when you're wrong.
Common mistake"If I see a difference, I have to correct it."
Not every difference you see is a problem; asymmetry is common and most of it produces no symptom. A correction should be tied to a complaint or a goal, not to the difference itself.
Common mistake"Saying I don't know is a loss of competence."
What produces the loss isn't the "I don't know" itself, it's that no next step follows it.
Practice
Keep in mind
Detail isn't certainty. The more parts an explanation has, the lower the odds that all of it is true.
The fallacy feeds from three places: technical language making questions harder to ask, the short list of what can be measured in a classroom, and the expectation that the teacher has an answer.
Its most expensive consequence is the stuck-on label. It takes a second to say, months to remove; and the label confirms itself through the avoidance it produces.
The claim setting has three levels: observation, probability, mechanism. The mechanism level is used only after it's been confirmed by trying something.
And "I don't know" is said in three parts: what I know, what I don't know, what we're doing now.
Bridge to the next lesson
This section's last lesson draws a distinction, and without it, the rest of this course gets muddled.
Yoga has been describing the body for centuries, and in a language completely unlike modern anatomy: channels, centers, a flowing life-breath. These two accounts aren't two versions of the same thing, and trying to prove one with the other's language damages both.
The next lesson separates the two: which one claims what, how each is tested, and how a teacher keeps their honesty intact while using both.