The room is already pushing you to force a fight. The team is pulling apart, and you are walked into striking now. This chapter does not ask whether you look bold enough. It asks about commitment: different situations demand different commitments. On dispersive ground, do not fight; last-resort ground is last resort. Too deep a pledge locks the next cycle. So you pause before treating urgency as a license. This chapter stops forcing a fight on dispersive ground.
Refuse the nine-grounds dump — keep this site’s judgment
Search pages on this chapter usually open with the nine grounds, then paste lines like “on dispersive ground, do not fight.” The live page you use here does not ask you to memorize nine-grounds slogans, and it does not teach fighting by ground type to crush a rival. It gives you a judgment first: different situations demand different commitments. On dispersive ground, do not fight; last-resort ground is last resort. Too deep a pledge locks the next cycle.
So you can refuse the encyclopedia opening. Nine grounds and nine requirements stay as evidence in the text, not your license to force a fight today. Your work is different: name the situation, and the one commitment it requires. Next, verify only whether that commitment is too much or too little. Treating the nine situations as a fight menu is how urgency hides inside “must strike.”
You also do not need to read this chapter as a commercial playbook for fighting by ground. This site’s founding direction is fewer unnecessary fights, not a playbook for crushing a rival or running a nine-grounds SOP. The nine situations here teach: on dispersive ground, do not force a fight. If you came for the nine grounds as a fight menu, this is the wrong door.
“When feudal lords fight on their own ground, it is dispersive ground” and “on dispersive ground, do not fight” can stay in the original for you to check later. What you ask first is not “how to use all nine grounds today.” You ask whether you are already on dispersive ground; whether this ground says do not fight, or fight only as a last resort; whether the commitment is too deep or too shallow. Treating the list as a strike menu is how “do not fight” gets renamed as must-force.
On dispersive ground, do not force a fight: commitment depth outranks pride
The classical lines run long, and they are written for you to use. Fighting on one’s own ground is dispersive ground; on dispersive ground, do not fight. You first ask whether this is dispersive ground, then whether you are holding the “do not fight” commitment — or stacking pride and the calendar into the pledge. Too deep a pledge locks the next cycle. If forcing a fight already rewrote the aim, do not force it.
The step that makes you look decisive may only be a collision on dispersive ground. So you separate two facts: a team already pulling apart is not the same as a duty to force a fight now; their movement is not the same as your duty to lock the next cycle with a deeper pledge. On dispersive ground, do not force a fight. Name the situation and the commitment before you move.
Rooms like to rename an instant hard fight as resolve. Others already moved, so asking whether the fight is worth it looks slow. The chapter splits that rename. If the resolve is fewer unnecessary fights, a pause is not slow. If the resolve is only that the calendar says strike now, you already forced a fight on dispersive ground under a false name.
You can also refuse the dump that turns every ground into a license to crush the other side. Those lines stay as evidence on the live page. Your job today is narrower: name the situation and the one commitment it requires before you name the strike. If you cannot name them, you are not using the nine situations — you are hunting for cover to force a fight.
You can also write “too deep a pledge locks the next cycle” onto the urgency in front of you. Striking fast still fails if the pledge is too deep. So each time you want a hard fight now, you ask whether the commitment is too much or too little, not whether the room is loud. If that is not written, you do not force it.
People will tell you that not fighting is already a loss. The chapter does not protect your face for the next ten minutes. It protects the next cycle. Naming dispersive ground and refusing the fight outranks looking decisive. If you hold the room by forcing a fight you know you should not force on dispersive ground, the next cycle is often harder to reverse — and this round was already the opening of an unnecessary fight.
Write object, goal, resistance — then check situation and commitment
You name the object: the person, the team, or the system this hard fight would actually touch — not an abstract “must strike.” You name the goal: a result that makes the next cycle better, not “must force a fight now.” You name the resistance: the real block, not the wait you dislike.
Then you run the same four checks as the live page. Which of the nine situations are you in? Does this ground say do not fight, do not linger, do not assault, or fight only as a last resort? Is the commitment too deep, or too shallow — and would too much lock the next cycle? Does morale come from the situation itself, or only from pressure from above?
If “dispersive ground — do not fight” or “commitment too deep” fills even one line, you are not using the advantage of the nine situations. You are being walked into a forced fight by urgency. So you name the situation first, and the one commitment it requires. Next, verify only whether that commitment is too much or too little. If it is too much, pull one layer back — do not force the fight.
You do not owe the room a speech about Sun Tzu. You owe the next cycle one fewer fight started by forcing it on dispersive ground. Naming situation and commitment outranks striking. Holding commitment depth outranks looking decisive.
After the three lines and four checks, you verify only one thing: whether that commitment is too much or too little. If it is too much, you pull back. If it is still short, you still ask whether you are filling the commitment — or actually forcing a fight for pride. Treating “they moved” as the only reason to fight is often a forced fight signing for you.
If urgency already walked you into a hard fight on dispersive ground once, you do not owe the room a deeper pledge to “recover face.” Naming dispersive ground still applies: name where the crack happened, and verify only whether the commitment is too much or too little next. Being able to change the second round is fewer unnecessary fights — not renaming a collision as resolve.
On dispersive ground, do not force a fight
The judgment on this site sits on Dispersive ground. The original lines stay there as evidence for you, not decoration. Different situations demand different commitments. On dispersive ground, do not fight; last-resort ground is last resort. Too deep a pledge locks the next cycle. Name the situation and the commitment before you move.
You name the situation, and the one commitment it requires, before you talk about striking. Naming it is not surrender. It is writing the situation and the commitment, and verifying only whether that commitment is too much or too little. The live page asks you to move only while the pledge is not too deep — not to lock the next cycle with it. Using “do not fight on dispersive ground” as a constraint often opens fewer unnecessary fights than an instant hard strike.
So you can treat “do not force a fight on dispersive ground” as today’s action, not a slogan. You write which strikes cannot return the next cycle if you force a fight tonight on dispersive ground. You write how the next cycle can start without an unnecessary fight if you pull one layer of commitment back first. A forced fight is expensive. Colliding once on dispersive ground makes the next cycle harder to reverse.
You can keep the nine-grounds catalogue on the chapter page for later checking. What you carry into the room is shorter: one written situation, one required commitment, one verification, and a pullback when it is too deep. That is how you keep striking after the fight is right without turning the nine situations into an encyclopedia.
You are not asked never to strike. You are asked to check first whether this fight is necessary, and what would make the next cycle better — and not to treat urgency as the only advance. This week’s situation and commitment also belong in your review. Your review is three sentences: the judgment, what you verified, what would make the next cycle better. If you opened a fight by forcing it on dispersive ground, the review names where you forced it. Being able to change is using the nine situations — not renaming a collision as resolve after the fact.
You can also keep this chapter separate from Variation, Terrain, Attack by Stratagem, and The Army on the March. Variation owns refusing the path that should be refused. Terrain owns whether the ground fits — fight or do not fight. Attack by Stratagem owns attacking the plan first, and not fighting when you need not. The Army on the March owns visible signals on the road: read the signals before contact. The nine situations own this: on dispersive ground, do not force a fight — and whether commitment depth will lock the next cycle. Do not make “refuse the path,” “ground does not fit,” “without fighting,” or “read the signals” the main frame of this article. What you stop today is forcing a fight you already know you should not force on dispersive ground.
Questions people ask when the room demands a hard fight now
The team is already pulling apart — must I force a fight at once to look like I have resolve?
No. Instant hard fighting is often urgency deciding for you. The chapter splits situation from commitment: different situations demand different commitments; on dispersive ground, do not fight. So you write object, goal, and resistance first. You ask whether striking is because the fight is necessary, or only to look decisive. If resolve means the next cycle opens with fewer unnecessary fights, a pause is not slow. Slow is treating urgency as a license to force a fight.
Does “on dispersive ground, do not fight” teach me how to fight by ground type and crush the other side?
No. That line is evidence in the text; the live page does not turn it into a nine-grounds SOP or commercial strike manual. The nine situations are a constraint: you ask what commitment the ground requires, not how to dominate a rival. So you ask about the situation and commitment first. This site’s founding direction is fewer unnecessary fights. If you read the nine grounds as a method for crushing a rival, this is the wrong door.
To keep the window, can I force the fight first and check situation and commitment afterward?
Forcing the fight is not an opening condition. The live page asks: did you name the situation? Did you write the one commitment it requires? Next, verify only whether that commitment is too much or too little. So you write the situation and the commitment. If that is not written, do not force it. Colliding first with a locked next cycle is the exact forced fight this chapter was written to stop.
Does “on dispersive ground, do not force a fight” mean I am surrendering, so the room will think I dare not strike?
No. Naming dispersive ground means writing the situation and commitment and verifying only depth, instead of letting urgency walk you into a hard fight now. On dispersive ground, do not force a fight. So you can pull one layer of commitment back without a speech. If the other person only scores speed, you still do not join that scoreboard. What you protect is a next cycle you can still walk, not the strike label of this hour.
Do I need to memorize the nine-grounds details before I have understood this chapter?
No. Those details are evidence in the text, not your hard-fight list for today. The live judgment is: different situations demand different commitments; on dispersive ground, do not fight; last-resort ground is last resort; too deep a pledge locks the next cycle. So you check which ground you are on, whether it says do not fight, and whether the commitment is too deep. Skipping do-not-fight while memorizing slogans is encyclopedia reading, not judgment.
Is this the refuse-the-path, ground-fit, without-fighting, or signals article under a new title?
They differ. Variation owns refusing the path that should be refused. Terrain owns whether the ground fits — fight or do not. Attack by Stratagem owns attacking the plan first when you need not fight. The Army on the March owns visible signals: read them before contact. The nine situations own: on dispersive ground, do not force a fight, and commitment depth. So today’s action for you is naming situation and commitment and verifying only depth — not rewriting those frames.
If I already forced a fight on dispersive ground once, how can I still use the nine situations now?
You still can. Naming dispersive ground is not pretending you never collided. You name the crack: which step was a forced fight on dispersive ground, and how the next cycle got locked. You write what next verifies: only whether the commitment is too much or too little. You refuse a second deeper pledge from urgency. Do not force still applies after a strike taken. So you can halt the next forced fight. Open fewer unnecessary fights next.
The next move is not a hard fight now. You name the situation, and the one commitment it requires. Next, verify only whether that commitment is too much or too little. If a team needs that judgment in one room, and it fits, Contact Us — teaching, training, and content, not crushing a rival. We reply within two business days. You name dispersive ground before you move. Open the next cycle with one fewer unnecessary fight.