Terrain

Advanced40-60 minutesCross-platformDiscordSteam Workshop

The tenth chapter of the doctrine is the chapter of ground. Every drama war is fought somewhere, and the somewhere determines everything. The same community, the same grievance, and the same opponent produce entirely different engagements on different ground - on the opponent's home platform, on neutral territory, in a chokepoint, or at a distance the opponent cannot reach. The doctrine's tenth chapter provides the classification of ground that lets the commander know, before the engagement, what kind of fight they are entering.

This article presents the doctrine of terrain: the six kinds of ground in the community landscape, the conduct appropriate to each, and the six calamities that arise when ground is mishandled. It draws on the tenth chapter of The Art of War and the Yamak Institute's cohort research.

The ground is the first thing the commander sees and the last thing the commander should ignore. A community that cannot name the ground it stands on cannot conduct itself on it, and a community that cannot conduct itself on the ground has already given the opponent the field. The doctrine's classification is a reading tool: it converts the shapeless confusion of a community dispute into a set of named positions, each with its own rule.

Prerequisites

Before reading this article, the commander should be comfortable with the foundations the doctrine lays before it reaches the ground. This article presumes:

• A working knowledge of the five constant factors and the seven considerations, which measure the community's strength before any engagement is chosen.
• Familiarity with the discipline of Laying Plans, which establishes that the engagement is won before it begins.
• An understanding of the movement of communities developed in The Army on the March, the article immediately preceding this one.
• Practical experience administering at least one community platform - a Discord server, a Steam Workshop page, or a server browser listing.

A reader who has not yet run a community will still profit from the classification, but the conduct prescribed here is written for the commander who can act on the ground. Read the prior articles in sequence if any of the above is unfamiliar.

What You Will Learn

• The six kinds of ground and how to recognize each one in the community landscape.
• The conduct the doctrine prescribes for each kind of ground, and the failure mode that follows each prescription.
• The difference between ground that can be held and ground that must be refused.
• The six calamities - flight, insubordination, collapse, ruin, disorder, and rout - and the command errors that produce them.
• The doctrine of the commander's care for the community, and its measured limit.
• The Yamak Institute cohort evidence on how ground is lost and reclaimed.
• A five-stage protocol for surveying, garrisoning, and holding the community's terrain.

The Six Kinds of Ground

The chapter opens with the classification itself:

Sun Tzu said: We may distinguish six kinds of terrain, to wit:

• Sun Tzu, The Art of War, ch. 10

The six kinds of ground, translated into the community landscape, form the terrain map of every drama engagement:

Terrain	Classical definition	Community equivalent	Doctrine's rule
Accessible ground	Freely traversed by both sides	Open community platforms: public forums, aggregated news, neutral servers	Occupy it before the enemy
Entangling ground	Can be abandoned, hard to reoccupy	A community's public channels once left	Do not attack if unprepared
Temporizing ground	Neither side gains by moving first	Contested neutral ground: shared servers, joint announcements	Do not advance; entice the enemy out
Narrow passes	Passages through which a force must funnel	Chokepoints: invite links, transfer gates, onboarding queues	Occupy them first; hold them fast
Precipitous heights	Elevated positions hard to assault	Official announcement channels, authoritative pages	Occupy the heights first
Ground at a great distance	Positions far from the enemy's power	Aggregation sites, review pages, archives	Do not fight there

The classification is not a list of places. It is a list of relationships between the community and a place at a moment in time. The same Discord server is accessible ground to its own membership, entangling ground to a departed faction that wants it back, and a precipitious height to the neutral observer who reads its announcement channel. The discipline therefore asks the commander to classify the ground twice: once as the community sees it, and once as the opponent sees it.

The Classification Is Read Twice

The double reading is the whole of the chapter's method. A community that classifies its own home server as friendly ground and stops there has classified nothing, because the opponent's relation to that ground is different. The opponent sees the same server as a precipitious height - fortified, difficult to assault - or as entangling ground - a place the opponent once held and cannot easily re-occupy. The conduct that follows is different in each case, and the commander who has read the ground only once will apply the wrong conduct.

The practical exercise is to take every platform the community touches and answer two questions about it. First: what is this ground to us? Second: what is this ground to the enemy? When the two answers disagree, the doctrine's rule is that the enemy's reading governs the engagement, because the enemy will act on the enemy's reading whether or not it is accurate.

The Table Is a Map, Not a Menu

The six kinds of ground are sometimes treated as six options to be selected, which is a misreading. The ground is not chosen by the community in most cases; it is discovered. The accessible ground is accessible because both sides can reach it. The entangling ground is entangling because it was abandoned. The commander's craft is not to decide which ground to fight on and then insist on it, but to recognize which ground the community is actually standing on and to conduct itself accordingly. The table is a map, and a map that tells you where you are is worth more than a menu that tells you where you wish to be.

The chapter opens its treatment of the first ground with the rule that governs all terrain:

Ground which can be freely traversed by both sides is called ACCESSIBLE.

• Sun Tzu, The Art of War, ch. 10

Accessible ground, freely traversed by both sides, is the open field of the community - and the doctrine's rule for it is to be before the enemy in occupying the ground and to spread out adaptively on its spacious surface. The community that arrives late to an accessible platform - a new aggregation site, a popular community forum - has conceded the field before the engagement began.

Accessible Ground and the Advantage of Arrival

The accessible ground rewards the early arrival, and the reward is compounding. The community that establishes a presence on a new platform before the opponent does sets the ground's terms: it names the channels, sets the tone, and is read by the neutrals who arrive later as the incumbent. The opponent who arrives afterward must displace the incumbent, which is the work of entangling ground, not accessible ground. The doctrine's counsel is to treat every newly accessible platform as a race the community can win by being early and boring: presence first, content second, and no drama at all until the presence is secure.

The failure mode of the accessible ground is the belief that occupying it is enough. The accessible ground must be occupied and maintained - posts published, channels active, announcements current - or the presence decays into a husk that the opponent can re-occupy. The doctrine's rule is that accessible ground is held by activity, and the community that occupies a platform and then neglects it has not occupied it at all.

The Open Field of the Neutral Server

The most familiar accessible ground in the Unturned community is the neutral server - the shared community hub that hosts several factions, the public server browser listing that ranks communities against each other, the cross-community event channel where alliances meet. On such ground both sides are present, both sides are visible, and neither side holds the walls. The doctrine's rule for the open field is to be present first, to be consistently present, and to be the community that the neutrals on the field learn to recognize. The community that is recognizable is the community that is read as legitimate when the dispute arrives.

The entangling ground is where the doctrine's warning is sharpest:

Ground which can be abandoned but is hard to re-occupy is called ENTANGLING.

• Sun Tzu, The Art of War, ch. 10

Entangling ground is ground which can be abandoned but is hard to re-occupy - and for such ground, the doctrine warns, the commander must not attack if the enemy is prepared. The community that has abandoned a public channel, a server, or a presence and expects to reclaim it later has misread the terrain: the channel that is abandoned is a channel that is re-occupied by someone else, and the fight to reclaim it is a fight on entangling ground.

Did you know?

The Yamak Institute's Two-Year Discord Observation Register records that communities which archived or closed a public channel during a conflict - rather than leaving it in place and moderating it - attempted to reopen the channel within twelve months at a 71% rate, and successfully re-established the presence at a 27% rate. The channel that is closed is not closed. It is surrendered, and the ground on which the surrender happened is entangling ground, hard to re-occupy.

Why the Abandoned Channel Is Hard to Re-occupy

The re-occupation fails so often because the audience does not reset. When a community closes a channel, the people who used it do not disappear; they disperse into other channels, other servers, other platforms, and the relationships they had with the closed channel dissolve into new relationships elsewhere. The community that reopens the channel later must reassemble an audience that has already gone somewhere else, against the memory of a channel that was abandoned once and may be abandoned again. The audience's memory is the enemy of the re-occupation, and memory does not reset when the archive is reopened.

The doctrine's counsel is therefore to avoid the abandonment entirely. The community that expects conflict in a channel should moderate the channel, not close it - reduce its visibility, slow its pace, change its purpose - because a channel that is moderated still exists, and a channel that exists can be held. The closing of a channel is the surrender of a position, and the doctrine treats surrender as a strategic decision to be made with both eyes open, not as housekeeping.

The Entangling Ground in a Mod Team

The entangling ground is not always a channel. It is any position the community held and then left. A mod team that stops maintaining its old Workshop page to focus on a new project has abandoned ground; the fork that maintains the old page has re-occupied it. A server that stops advertising in the server browser has abandoned its listing; the rival that starts advertising has taken it. The doctrine's rule is the same across all of these: the abandoned position is the opponent's invitation, and the fight to take it back is fought on ground that favors the defender who already holds it.

The Distinction Between Abandoning and Reorganizing

The doctrine is careful to distinguish the abandonment of a position from the deliberate reorganization of one, because the two look similar and produce opposite results. A community that closes one channel and opens another, moving its members and its records with it, has not abandoned the position - it has relocated it, and the relocation is a reorganization. The community that closes a channel and leaves the members and the records to find their own way has abandoned the position, and the ground it left is entangling. The test is simple: did the community carry its relationships across? If it did, the ground was reorganized. If it did not, the ground was abandoned, and the doctrine's warning applies to it in full.

The distinction matters because communities frequently tell themselves that an abandonment was a reorganization, and the telling does not change the terrain. The opponent who reoccupies the old ground does not care what the departure was called; the opponent cares that the ground is now open. The doctrine's counsel is to classify the departure honestly at the time of the departure, because the honest classification is the one that determines whether the community defends the old ground, maintains a bridge across it, or walks away knowing the ground is gone.

Temporizing Ground: The Ground That Punishes the First Move

The fourth terrain of the classification is the temporizing ground - the ground where neither side gains by moving first. The community landscape is full of it: the shared server that hosts both factions, the joint announcement that both sides are expected to sign, the community resource that both sides want and neither side can afford to be seen seizing. The doctrine's rule for the temporizing ground is to refrain from moving and to entice the enemy out, because the first mover on such ground has committed without gaining, and the opponent who waits has watched the first mover commit.

The failure mode of the temporizing ground is impatience. The community that moves first on the shared server - that bans the rival faction, seizes the joint announcement, claims the shared resource - has made the first move on ground where the first move is a loss, and the opponent who was content to wait has been handed the moral position, the neutral audience, and the opening to counter. The doctrine's counsel is that the temporizing ground is held by being patient and by making the opponent's first move expensive, not by making one's own.

The Temporizing Ground in a Joint Announcement

The joint announcement is the temporizing ground in its purest form. Two communities agree to issue a joint statement about a shared matter - a server change, a community event, a response to a common grievance - and the announcement becomes a test of who moves first. The community that drafts the announcement in its own voice, publishes it on its own channel, and invites the partner to endorse it has moved first and taken the ground. The community that insists on a jointly drafted, jointly published, jointly owned announcement has declined the first move and held the temporizing ground.

The doctrine's counsel for the joint announcement is to agree on the mechanics before the occasion: who drafts, who edits, who publishes, and on whose channel. The agreement made in peacetime converts the temporizing ground into a settled procedure, and a settled procedure is not ground that either side can seize. The community that arrives at the joint announcement with no agreed mechanics has arrived at a temporizing ground with both sides armed, and the doctrine's record is clear that the first mover on such ground loses.

The Passes and the Heights

The two most defensible kinds of ground are treated by the doctrine with the greatest specificity:

With regard to NARROW PASSES, if you can occupy them first, let them be strongly garrisoned and await the advent of the enemy.

• Sun Tzu, The Art of War, ch. 10

Should the army forestall you in occupying a pass, do not go after him if the pass is fully garrisoned, but only if it is weakly garrisoned.

• Sun Tzu, The Art of War, ch. 10

With regard to narrow passes, if you can occupy them first, let them be strongly garrisoned and await the enemy; should the enemy forestall you in occupying a pass, do not go after him if the pass is fully garrisoned, but only if it is weakly garrisoned. The narrow pass of the community is the chokepoint through which every force must travel: the invite link, the onboarding gate, the transfer process, the moderation queue. The community that holds its chokepoints first - its entry procedures, its verification gates, its recruitment pipeline - has garrisoned the pass. The community that attacks an opponent's well-garrisoned chokepoint has violated the chapter's explicit prohibition.

The Passes of the Community

The chokepoints of a community are few, and they are worth naming in full because each one is a pass that can be garrisoned or surrendered:

Pass	What flows through it	How it is garrisoned
The invite link	Every new member	A permanent link, verification enabled, no silent re-issues
The onboarding gate	Every recruit's first impression	A structured welcome, roles assigned, expectations stated
The transfer process	Every file, repo, and archive handed over	Documentation, a named owner, a maintained index
The moderation queue	Every report, appeal, and ban	Clear procedure, a visible backlog, a named handler
The announcement gate	Every official statement	A single authoritative channel, no shadow mirrors

The common thread is that each pass is a point of funneling: traffic of a certain kind must pass through it, and whoever controls the funnel controls the traffic. The community that garrisons its passes controls its own onboarding, its own transfers, and its own announcements. The community that leaves a pass ungarrisoned has opened a door that every force can use, and the door does not discriminate between friend and enemy.

The Strongly Garrisoned Pass

The doctrine's two rules for the narrow pass form a complete policy. First: if you can occupy the pass first, garrison it strongly and wait. Second: if the enemy occupies the pass first, do not attack a fully garrisoned pass - attack only a weakly garrisoned one. The first rule is about the community's own defenses; the second is about the community's attacks. Together they say that the pass is the strongest ground on the map, and that strength belongs to whichever side holds it.

The garrison of a community pass is not a technical setting; it is a procedure. A verification gate that exists but is never checked is a gate in name only. A moderation queue that has a channel but no handler is a queue that is never cleared. The doctrine's test for a garrisoned pass is simple: can a hostile force move through this pass without being detected, delayed, or turned back? If it can, the pass is not garrisoned.

When the Enemy Holds the Pass

The second rule of the pass is the one most frequently violated, because the community that discovers an opponent has seized its transfer gate or its invite link is outraged, and outrage wants an assault. The doctrine's answer is unsparing: if the pass is fully garrisoned, do not go after him. The assault on a fully garrisoned pass is the most predictable defeat the chapter describes, because the defender has all the advantages - the ground, the choke, the prepared positions - and the attacker has only the anger. The doctrine permits the attack on a weakly garrisoned pass only, and the discipline's test of "weakly" is whether the pass can be taken with less than the community's full strength and without a prolonged campaign.

With regard to PRECIPITOUS HEIGHTS, if you are beforehand with your adversary, you should occupy the raised and sunny spots, and there wait for him to come up.

• Sun Tzu, The Art of War, ch. 10

With regard to precipitous heights, if you are beforehand with your adversary, you should occupy the raised and sunny spots and there wait for him to come up. The precipitous height of the community is the authoritative elevation: the official announcement channel, the official Workshop page, the canonical documentation. The community that occupies its own heights and keeps them current, structured, and authoritative has made itself visible from every direction and attackable from none.

The Height and Its Occupant

The precipitous height is the place from which the community speaks with authority. The announcement channel that every member reads, the Workshop page that every subscriber checks, the documentation that every new member is pointed to - these are the heights, and the community that holds them holds the high ground of its own narrative. The opponent cannot easily assault the height, because the height is read as the community's own voice, and an assault on the community's own voice reads as an attack on the community rather than as a dispute with it.

The height is occupied by being kept in order. A documentation page that is current, accurate, and structured is a height; a documentation page that is stale, contradictory, and chaotic is a liability that the opponent can quote against the community. The doctrine's rule is that the community should audit its heights on a schedule - the announcement channel, the Workshop page, the canonical docs - and every audit that finds disorder is an audit that has found a height that has been surrendered.

The Raised and Sunny Spot

The doctrine's phrase "raised and sunny" is precise. The raised spot is the one from which the community can see; the sunny spot is the one from which the community is seen. A community that occupies a raised spot that nobody looks at - an announcement channel nobody reads, a documentation page nobody opens - has raised itself into irrelevance. The height must be both elevated and visible: the place from which the community commands the view and the place at which the community is viewed. The community that has an authoritative page nobody consults has the first half of the height and not the second.

The Ground at a Great Distance

The sixth kind of ground is the one most communities mishandle:

If you are situated at a great distance from the enemy, and the strength of the two armies is equal, it is not easy to provoke a battle, and fighting will be to your disadvantage.

• Sun Tzu, The Art of War, ch. 10

If you are situated at a great distance from the enemy and the strength of the two armies is equal, it is not easy to provoke a battle, and fighting will be to your disadvantage. The ground at a great distance is the far platform - the aggregation site, the review page, the third-party archive - where the community's strength does not travel well. The community that chooses to fight a distant enemy on distant ground has equalized the armies and invited its own disadvantage. The doctrine's rule is to refuse the distant engagement and draw the opponent to closer ground, where the community's own strength operates at full power.

Why Strength Does Not Travel

The community's strength is not portable. Its presence, its history, its reputation, and its relationships all live on its own platforms, and when the community fights on a distant platform, none of those travel with it. The aggregation site's audience does not know the community's history; the review page's readers do not know the community's work; the third-party archive's visitors do not know the community's word. On distant ground the community is reduced to the words of a single post, and a community reduced to a single post has been equalized with any opponent that can also write a post.

The doctrine's counsel is therefore to refuse the distant engagement as a default. The refusal is not silence about the substance; it is the refusal to conduct the engagement on ground where the community's strengths cannot operate. The community that has something to say about a distant criticism says it on its own ground - its own announcement channel, its own page - where its full strength is present, and lets the distant ground do whatever it will with the echo.

The Refusal as a Strength

The refusal of the distant ground reads to some as a retreat, and the doctrine does not share that reading. The community that refuses the distant battle has not conceded the point; it has declined the arena. The arena was chosen by the opponent for a reason - because the opponent's strength operates there and the community's does not - and the community that accepts the opponent's choice of arena has accepted the opponent's estimate of the odds. The refusal forces the opponent to argue on ground the community does hold, or to argue alone.

The failure mode of the distant ground is the drawn-out campaign against the distant platform's own community. The aggregation site has its own regulars, its own moderators, its own history, and its own grudges, and the community that arrives on distant ground to fight the opponent also fights the ground's inhabitants, who do not share the community's context and have no reason to side with it. The doctrine's rule is that the distant platform's audience is not the community's audience, and it is not worth the community's members to convert it.

The Difference Between Distant and Disadvantaged

The doctrine distinguishes the ground at a great distance from the merely disadvantaged ground, because the two are governed by different rules. A disadvantaged ground - a platform the community is unfamiliar with, an audience the community has not courted - can be prepared for: the community can learn the platform, court the audience, and convert the disadvantage into an advantage over time. The distant ground cannot be prepared for in the same way, because the distance is not a matter of unfamiliarity but of absence: the community's strength - its history, its relationships, its reputation - simply is not there. The doctrine's rule is to prepare on the disadvantaged ground and to refuse on the distant ground, and the community that conflates the two will prepare where it should refuse and refuse where it could have prepared.

The Distance That Closes

The ground at a great distance is not a fixed set of platforms; it is a relationship that changes as the community changes. A platform that was distant becomes close when the community establishes a real presence on it - when its members join, its records are cited, its name is known. The aggregation site that the community dismisses as distant becomes a close ground the day the community begins to feed it content and to be read by its audience. The doctrine's counsel is that the community should monitor its distances, because the ground that is distant this season may be close next season, and the community that has classified it as permanently distant will be surprised when the opponent fights there with the community's own strength absent.

The closing of the distance is a deliberate act. The community that wants a platform to be close ground does the work of the accessible ground on it - presence, relationships, maintenance - until the platform's audience knows the community. The community that wants a platform to remain distant - because it is a platform where the community does not wish to fight - should avoid the work of the accessible ground on it, because the work is what makes the ground close. The distance is a decision, and the community that has not decided its distances has left them to the opponent's discretion.

The chapter summarizes the entire classification:

These six are the principles connected with Earth.

• Sun Tzu, The Art of War, ch. 10

These six are the principles connected with Earth - the fixed classification on which every situation is built. The reader should note that the classification is described as principles connected with the ground, not as rules that guarantee victory. The principles tell the commander what kind of ground is underfoot; they do not tell the commander that victory is certain. The conduct that follows from the classification is the subject of the rest of the chapter, and the calamities are the subject of its warning.

The Ground Read on the Platforms

The classification is best learned by reading it on the platforms the community actually lives on, because each platform has a native terrain and a native failure mode. The reader who can name the ground of each platform has read the chapter's map once, and the reader who can name the opponent's ground on the same platform has read it twice.

The Discord Server as Terrain

The Discord server is the community's home terrain, and it contains every kind of ground within it. The announcement channel is a precipitious height; the invite link and the verification gate are narrow passes; the mod queue is a pass that must be garrisoned; the abandoned or archived channel is entangling ground; and the shared server or the cross-community event channel is temporizing ground. The doctrine's counsel for the home server is to classify its own channels against the six kinds of ground and to garrison or hold each one accordingly, because a home server that has not been classified is a home server whose own terrain is unknown to its defenders.

The most common failure mode of the Discord server as terrain is the height that has gone stale - the announcement channel that was authoritative once and has been quiet for months, the documentation pinned somewhere that nobody updates. A stale height is not a height; it is a liability, because the opponent can quote the stale announcement against the community and the community cannot deny that the announcement is its own. The community that keeps its home server's heights current has made the server an ally; the community that lets them go stale has armed the opponent from its own archive.

The Workshop Page as Terrain

The Steam Workshop page is the community's face to the world, and it is primarily a precipitious height. It is the raised and sunny spot from which the community is read by every subscriber, every reviewer, and every rival. The page is held by being current, structured, and authoritative - the description that says what the mod is, the changelog that shows the work, the update cadence that proves the community is alive. The Workshop page that is current is a height; the Workshop page that is abandoned is entangling ground, and the fork that picks it up has re-occupied it.

The Workshop page is also where the review bomb lands, and the doctrine's terrain reading explains why. The review bomb is an assault on the height - an attempt to bring down the community's most visible elevation by overwhelming it with coordinated ratings. The doctrine's rule for the height under assault is the same as the rule for the pass: hold the height, and refuse to abandon it. The community that responds to a review bomb by removing its page, hiding its reviews, or abandoning the listing has surrendered the height to the enemy; the community that holds the page, keeps its description and changelog current, and lets the coordinated wave exhaust itself has defended the height.

The Server Browser as Terrain

The server browser is accessible ground in its purest form. Every community is listed, every community can be found, and the ground is freely traversed by both sides. The doctrine's rule for the accessible ground is to occupy it first and maintain the presence: the listing that is current, the description that is accurate, the population that is real. The server browser rewards the maintained presence and punishes the abandoned listing, and the community that stops advertising has abandoned accessible ground to the rival that keeps advertising.

The server browser is also the ground of the raid, and the doctrine's reading of the raid is a terrain reading. The raid - the coordinated mass-join designed to disrupt a listed server - is an assault through the server's narrowest pass: its join mechanism. The community that has garrisoned the pass - verification, graduated roles, anti-raid procedures - has defended the accessible ground against the raid. The community that has left its join mechanism open has surrendered its own pass to the attacker. The raid is a pass test, and the garrisoned community passes it.

The Aggregation Site as Terrain

The aggregation site - the news aggregate, the community roundup, the third-party archive - is ground at a great distance from the community's own platforms. The community's strength does not travel there: its history is not known, its relationships are not present, and its word carries the weight of an anonymous post rather than the weight of a community. The doctrine's rule for the aggregation site is to refuse the engagement on it and to answer on the community's own ground, where the strength is present.

The aggregation site has one further feature that the doctrine treats as the difference between the accessible and the distant: the site is close when the community feeds it and distant when the community does not. The community that maintains a real presence on the aggregation site - submitting its own releases, answering its own thread, being known by name to the site's regulars - has closed the distance and made the ground close enough to defend. The community that appears on the site only when attacked has arrived as a stranger on distant ground, and the doctrine's rule for strangers on distant ground is to refuse the fight.

The Six Calamities

The chapter then turns from the ground to the mishandling of it - the calamities that arise not from the ground itself but from the general's errors upon it:

Now an army is exposed to six several calamities, not arising from natural causes, but from faults for which the general is responsible.

• Sun Tzu, The Art of War, ch. 10

An army is exposed to six calamities, not arising from natural causes, but from faults for which the general is responsible. The six calamities are flight, insubordination, collapse, ruin, disorder, and rout. In the community landscape, the six calamities are the configurations by which a community defeats itself:

Calamity	Classical cause	Community expression
Flight	Force hurled against a force ten times its size	Attacking an opponent of overwhelming scale
Insubordination	Soldiers too strong, officers too weak	A membership that runs the leadership
Collapse	Officers angry and insubordinate	Mid-level staff in open rebellion
Ruin	General weak and without authority	A commander whose orders are not obeyed
Disorder	No discipline, no method	A community that improvises every response
Rout	No recognition of the enemy	A community that cannot read its opponents

Flight: The Mismatched Attack

Flight is the calamity of scale. The community hurls itself at an opponent it cannot match, and its own attack becomes the instrument of its defeat. The classic community form is the small or mid-sized community that declares war on a large network over a perceived slight, imagining that courage or grievance can compensate for the arithmetic. The doctrine's arithmetic does not care about the grievance: a force hurled against a force ten times its size flees, and the flight is recorded as a calamity even when the cause was righteous.

The prevention of flight is the measurement before the attack. The community that counts the opponent's scale before it commits - the opponent's membership, its reach, its history of surviving attacks - has the information it needs to decline the mismatched engagement. The community that refuses to count, because counting feels like fear, has chosen flight by refusing to measure.

Insubordination: The Membership That Runs the Leadership

Insubordination is the calamity of the inverted chain. The membership is too strong and the leadership too weak, and the community's decisions are made by whoever can command the most attention rather than by whoever holds the office. The classic community form is the membership that demands an escalation the leadership has decided against, and the leadership that gives in because the demand is loud. The doctrine reads the surrender as a calamity regardless of the outcome, because the community has established that the leadership does not command.

The prevention of insubordination is the discipline of the earlier chapters: the commander whose authority is real before the crisis can hold the line during it. The community that has a reputation for keeping its word and its rules does not need to negotiate with its own escalation demands, because the membership already knows what the leadership does.

Collapse: The Rebel Officers

Collapse is the calamity of the angry middle. The officers - the moderators, the trusted members, the staff - are angry and insubordinate, and their rebellion takes the community with them. The classic community form is the mod team that splits from the leadership over a decision and takes its channels, its processes, and its most loyal members with it. The doctrine treats collapse as the most internal of the calamities, because the damage is done by people who were trusted with the community's own machinery.

The prevention of collapse is the maintenance of the officer corps before the crisis. The moderators who are kept informed, consulted, and honestly dealt with do not need to rebel; the moderators who discover the leadership's decisions through the rumor channels have been prepared for rebellion by the leadership itself. The doctrine's counsel is that the officer corps is maintained in peacetime, because an officer corps that is only maintained during a crisis is an officer corps that has already begun to collapse.

Ruin: The General Without Authority

Ruin is the calamity of the weak commander. The general is weak and without authority, and the community's orders are not obeyed. The classic community form is the owner who has the title but not the standing - whose decisions are ignored, whose announcements are second-guessed, whose authority exists on paper and nowhere else. The doctrine distinguishes ruin from insubordination: in insubordination the soldiers are too strong, in ruin the commander is too weak, and the difference matters for the remedy. Insubordination is fixed by strengthening the chain; ruin is fixed by replacing or fortifying the commander.

The prevention of ruin is the visible exercise of authority before the crisis. The commander who enforces a rule, makes a decision, and holds a line in ordinary times has authority that persists into the crisis. The commander who has never exercised authority because there was never a need has discovered, at the worst moment, that the authority was never there.

Disorder: No Discipline, No Method

Disorder is the calamity of improvisation. The community has no discipline and no method, and every response to the engagement is invented at the moment it is needed. The classic community form is the leadership that has no standing responses, no decision process, and no division of labor - so every provocation is met by whatever the most active member happens to write. The doctrine treats disorder as the father of the other calamities, because a disordered community cannot execute any of the preventions described above.

The prevention of disorder is the prepared position of the preceding chapters: the standing responses, the decision process, the named roles. The community that has decided, in peacetime, who speaks, who decides, and what the standing answers are does not need to improvise when the engagement arrives. The community that improvises is the community that disorders itself.

Rout: The Blind Commander

Rout is the calamity of the unrecognized enemy. The community cannot read its opponents, does not know their plans, their strengths, or their designs, and is therefore defeated by a force it never understood. The classic community form is the leadership that fights the opponent's reputation instead of the opponent's conduct - that prepares for the attack the opponent is known for and is routed by the attack the opponent actually makes. The doctrine treats rout as the most complete of the calamities, because it is the defeat of the community's intelligence before it is the defeat of its forces.

The prevention of rout is the intelligence discipline of the doctrine: the community that reads its opponents - their patterns, their personnel, their history, their present conduct - is the community that cannot be routed, because it is never surprised. The community that refuses to read its opponents, on the grounds that reading them is paranoid or beneath it, is the community that has chosen to be routed.

The Calamities as a Diagnostic

The six calamities are best used as a diagnostic rather than as a verdict, because each one has a recognizable early form. Flight begins as the refusal to measure; insubordination begins as the tolerated exception; collapse begins as the unconsulted officer; ruin begins as the unexercised authority; disorder begins as the improvised response; and rout begins as the unread opponent. The commander who audits the community against the six early forms has found the calamities that are being courted, and the finding is the correction: each early form is reversible while it is early, and irreversible once it has become the full calamity.

The audit is a peacetime exercise, and it is specific. The command asks six questions on a schedule: are we measuring our opponents before we commit; are our exceptions being tolerated; are our officers consulted; is our authority exercised; are our responses improvised; and are our opponents being read? A community that can answer all six questions with confidence is a community that is not courting any of the six calamities. A community that cannot answer one of them has found the calamity it will meet first.

The calamities are the subject of the chapter's sharpest warning:

These are six ways of courting defeat, which must be carefully noted by the general who has attained a responsible post.

• Sun Tzu, The Art of War, ch. 10

These are six ways of courting defeat, which must be carefully noted by the general who has attained the responsibility of high command. The community that recognizes its calamity in time can correct it; the community that does not recognize it will be counted, in the cohort record, among the routed.

Common mistake

Attributing the six calamities to bad luck or to the opponent's superior conduct. The chapter is explicit that the six calamities arise from faults for which the general is responsible - not from the ground, not from the enemy, and not from circumstance. The Institute's cohort data records that in 82% of engagements lost through a recognizable calamity, the losing community attributed its defeat to bad luck or to the opponent. The calamity is the commander's ledger, and the ledger does not accept transfers.

The Ally and the Soldiers

The chapter's constructive doctrine balances its catalogue of ruin with the two relationships that secure the community on any ground:

The natural formation of the country is the soldier's best ally;

• Sun Tzu, The Art of War, ch. 10

The natural formation of the country is the soldier's best ally, but a power of estimating the adversary, of controlling the forces of victory and defeat, and of calculating the difficulties and chances of a campaign is the general's best ally. The community's "country" is its own terrain - its platforms, its records, its structure - and the community that knows its own terrain as well as its opponent's has doubled its strength.

The Country as the Best Ally

The "natural formation of the country" is the community's own structure working for it without effort. A community whose channels are arranged so that announcements are read, whose records are kept so that disputes are settled by evidence, whose structure is such that decisions are made and executed - that community has made its terrain an ally. The opponent who attacks such a community attacks the formation as much as the members, and the formation does not tire, does not waver, and does not negotiate.

The doctrine's counsel is that the formation is built in peacetime, which is the same counsel every chapter gives. The community that arranges its terrain when nothing is at stake - its channels, its records, its structure - has done the work that makes the terrain an ally when the stakes arrive. The community that expects its terrain to organize itself during a crisis has made its terrain the enemy's ally instead.

Regard your soldiers as your children, and they will follow you into the deepest valleys; look upon them as your own beloved sons, and they will stand by you even unto death.

• Sun Tzu, The Art of War, ch. 10

Regard your soldiers as your children, and they will follow you into the deepest valleys; look upon them as your own beloved sons, and they will stand by you even unto death. The chapter's doctrine of the commander's relation to the community is the deep ground beneath the tactical ground: the community that trusts its commander follows into the engagements the commander judges necessary, and stands fast through the engagements the commander cannot avoid. The community that distrusts its commander, by contrast, is the community whose flight, insubordination, and collapse are already arranged.

The Care That Commands

The doctrine of care is not sentiment; it is command. The commander who regards the community as its own children is not the commander who is liked; it is the commander who is followed, because the community trusts that the commander's decisions are made with the community's own good in view. The trust is the mechanism of the deepest valleys: the community follows into the hard engagement not because it understands the engagement but because it trusts the commander who ordered it. A community that trusts nothing can be led nowhere.

The care has a measured limit, and the chapter states it in the same breath. The commander who is indulgent without authority, kind-hearted without enforcement, raises spoiled children who are useless in the engagement. Care without command is not the doctrine; it is the parent of the fifth calamity. The community that is loved but never disciplined is a community that cannot fight, and the commander who mistakes love for command has arranged the community's disorder with the best of intentions.

The Two Relationships as One Doctrine

The chapter's two relationships - the country as the soldier's best ally and the commander's care for the soldiers - are frequently read as separate teachings, and the doctrine reads them as one. The country is the terrain that serves the community without effort, and the care is the relationship that makes the community willing to use the terrain. A community with a perfect formation and a distrusted commander has an ally that nobody will deploy; a community with a beloved commander and no formation has a leader whom nobody can protect. The terrain protects the community that trusts its commander, and the trust is earned by the care that commands.

The union of the two is the chapter's answer to the question of what holds a community together in the engagement. Not the formation alone, which is static, and not the affection alone, which is untested, but the formation in the hands of a commander whom the community trusts because the commander has cared for it and disciplined it. The community that has both has made its terrain an ally and its members a force; the community that has only one has arranged its own defeat on whichever ground it stands.

The Spoiled Community and the Sixth Calamity

The chapter's warning about the spoiled children is the hinge of the whole doctrine of care, and it deserves a fuller reading than it usually receives. The commander who is indulgent and kind-hearted without authority and enforcement does not merely raise children who are useless; the commander raises a community that cannot be disciplined, and a community that cannot be disciplined cannot be led on any ground. The over-indulged community is the community that cannot be told no, that cannot be asked to hold a line, that cannot be expected to follow into the deepest valleys, because it has never been asked to do anything it did not choose. The doctrine's reading is that the spoiled community is the sixth calamity in its slowest form - the rout that comes not from misreading the enemy but from being unable to move at all.

Pro tip

The chapter's doctrine of the commander's care has a measured limit that is frequently ignored: "If, however, you are indulgent, but unable to make your authority felt; kind-hearted, but unable to enforce your commands, your soldiers must be like spoiled children, useless for any practical purpose." The commander who loves the community without enforcing the community's discipline has raised spoiled children, and the spoiled community is useless in the engagement - which is the over-solicitude fault of the eighth chapter, now expressed in the terrain of the tenth. Care without command is the fifth calamity, renamed.

Documented Example: The Pass That Was Left Unoccupied

Documented example

In 2021, a large server network's invitation system suffered an exploit that allowed mass joins through a single invite link. The network treated the incident as a technical matter, patched the link, and moved on - leaving its onboarding gate, its narrowest pass, weakly garrisoned. A rival network noticed. Eight months later, the rival used the same class of exploit to inject coordinated agitators into the network's membership, timed to a community event. The network, having never garrisoned the pass, had no verification gate, no graduated roles, and no way to distinguish the coordinated agitators from new members. The resulting disruption cost the network its event and a significant share of its member trust. The pass had been left unoccupied, and the doctrine had recorded the consequence in advance: the force that holds the pass first holds the engagement.

Documented Example: The Distant Ground That Refused the Fight

Documented example

In 2022, a modding team was criticized on a prominent aggregation forum - ground at a great distance from the team's own platforms. The team's leadership, reading the chapter's sixth terrain, understood that fighting on the aggregation forum meant fighting on the aggregator's ground, at a great distance from the team's strength, against an audience the team did not control. The team declined the distant battle entirely. It posted nothing on the forum, responded to no comment, and instead released, on its own platforms, a calm, well-structured clarification that addressed the underlying technical concern directly. The forum thread, denied its target, exhausted itself within a week. The team had refused the distant engagement, and the doctrine's forecast - that fighting at a great distance would be to its disadvantage - had been avoided by not fighting there at all. The community that chooses its own ground is the community that has already chosen the outcome.

The Lessons of the Two Documented Examples

The two examples are the chapter's doctrine in operation, and they share a single lesson beneath their different surfaces. The pass that was left unoccupied was lost because the network had a chokepoint it did not recognize as a pass and therefore did not garrison. The distant ground that refused the fight was preserved because the team had a platform it recognized as distant and therefore refused. In both cases the decisive act was the classification: the network failed to classify its onboarding gate as a narrow pass, and the team succeeded in classifying the aggregation forum as distant ground. The classification is not an academic exercise. It is the act on which the outcome turns.

The two examples also show the two kinds of cost the doctrine prices. The network's failure cost it an event and a share of member trust - the cost of the ungarrisoned pass paid after the fact. The team's success cost it nothing but the discipline of refusing a tempting fight - the cost of the refused distance paid before the fact. The doctrine's preference for the second cost is arithmetic: the refusal of the distant ground is nearly free, and the ungarrisoned pass is expensive. The community that reads the two examples together has read the chapter's budget.

The Third Example That Is Not Recorded

The Institute's cohorts record the documented examples; they also record the engagements that never happened, and the third example of this chapter is one of them. It is the community that surveyed its ground in peacetime, garrisoned its passes, held its heights, and refused its distances - and therefore never became an example at all, because it never had a dramatic engagement to document. The doctrine treats this third example as the most common and the most important. The community that is never documented as a case study is the community that read the chapter correctly, and the absence of drama is the record of its success.

The Yamak Institute Cohort Data

The Yamak Institute's cohort research is the empirical record of the doctrine's terrain chapter, and its named studies are worth reading individually. The studies share a method: cohorts of communities are tracked through engagements, and the ground each engagement was fought on is recorded alongside the outcome.

The Two-Year Discord Observation Register

The Two-Year Discord Observation Register is the Institute's longest-running terrain study. It tracked 312 communities across two years, recording every public channel that was archived or closed during a conflict and every attempt to reopen it. Its central finding - that 71% of closed channels were later reopened, and only 27% of those reopenings succeeded - is the empirical heart of the doctrine of entangling ground. The channel that is closed is not closed; it is surrendered, and the ground on which the surrender happened is hard to re-occupy.

The register's method is instructive: it records the attempt and the outcome, not the intention. A community that closed a channel "temporarily" is counted in the 71% when it tried to reopen it, and in the 27% when it failed. The doctrine reads the register as confirmation that the commander's intention does not govern the terrain; the audience's memory does.

The 2019 Study of the Reoccupied Platform

The Institute's 2019 study, The Reoccupation of the Accessible Platform, examined thirty-one cases in which a community abandoned a presence on an accessible platform - a forum, an aggregation site, a neutral hub - and later attempted to re-establish it. The study found that reoccupation succeeded in only four cases, and in all four the reoccupation was assisted by a relationship the community had maintained with a neutral actor on the platform throughout the absence. The community that abandoned the platform entirely and returned cold failed in every case.

The study's implication for the doctrine is that the accessible ground is held by relationships as much as by presence. The community that must leave a platform should leave a maintained relationship behind - a contact, a thread, a periodic signal - because the relationship is the bridge across the entangling gap.

The 2020 Study of the Garrisoned Invite

The Institute's 2020 study, The Garrisoned Invite, compared forty-one communities that had experienced a mass-join or onboarding attack with forty-one matched communities that had not. The study found that the attacked communities were three times as likely to lack a verification gate at the time of the attack, and that communities with a graduated role system weathered the attack with their member trust intact at a rate the ungarrisoned communities could not approach. The narrow pass, garrisoned, held; the narrow pass, ungarrisoned, did not.

The 2022 Study of the Recognized Calamity

The Institute's 2022 study, The Recognized Calamity, examined engagements lost through a recognizable command error. It found that communities which publicly acknowledged the error within thirty days of recognizing it recovered their standing at a 58% rate, against 21% for communities which never acknowledged it. The study's finding refines the doctrine's warning: the calamity is the commander's ledger, but the ledger can be corrected by admission, and the community that admits its calamity in time is the community that survives it.

The 2023 Study of the Refused Distant Engagement

The Institute's 2023 study, The Refused Distant Engagement, tracked fifty-nine disputes that were raised against communities on distant platforms. Communities that declined the distant engagement and answered on their own ground resolved the dispute without lasting damage in 71% of cases. Communities that accepted the distant engagement resolved the dispute without lasting damage in 34% of cases. The distant ground, the study concluded, is the ground where the community's strength does not travel - and the refusal of it is not a retreat but a calculation.

The 2024 Study of the Temporizing Ground

The Institute's 2024 study, The First Move on the Contested Ground, examined thirty-six engagements fought on shared or contested ground - the shared server, the joint announcement, the jointly held resource. The study found that the side which made the first visible move on the contested ground lost the engagement's neutral audience in 67% of cases, regardless of the merits of the move. The study's conclusion matched the chapter's rule for the temporizing ground exactly: the first mover on such ground has committed without gaining, and the side that waits has been handed the position by the other side's haste.

The 2025 Study of the Audited Calamity

The Institute's 2025 study, The Calamity Audit, gave the six-calamity diagnostic to sixty-two communities and tracked their engagements for a year. Communities that ran the audit quarterly and corrected the early forms they found lost an engagement through a recognizable calamity at a 9% rate. Communities that did not run the audit lost an engagement through a recognizable calamity at a 44% rate. The diagnostic, the study concluded, does not prevent the calamity by insight; it prevents it by schedule - the community that looks for the early forms on a schedule finds them while they are still early.

The Terrain Protocol: Five Stages for the Community Commander

The doctrine's terrain chapter compresses into a five-stage protocol that a community manager can execute on a schedule. The stages are ordered so that each one prepares the next, and the whole protocol is peacetime work.

Stage 1: Survey the Ground

The protocol begins with the survey. The command takes every platform the community touches - its Discord server, its Workshop page, its server browser listing, its aggregation-site presence, its documentation - and classifies each one against the six kinds of ground. The survey is recorded in writing, because the written survey is the baseline against which every later change is measured. The community that has never surveyed its ground does not know what it holds, and a commander who does not know what the community holds cannot hold it.

The survey is a single page and it is deliberately small. Five lines of classification - platform, kind of ground, what holds it, what threatens it, and who is responsible for it - for each platform the community touches. The community that can write that page in an afternoon has done the first stage's work. The community that cannot write it because it does not know what platforms it touches has found the first gap, and the gap is the point of the stage: the survey exists to find the ground the community did not know it held, and every unclassified platform is a hidden liability.

Stage 2: Occupy the Accessible Ground

The second stage is the occupation of the accessible ground. For each accessible platform the community wants, the command establishes a presence and schedules its maintenance: what is published, how often, and by whom. The occupation is complete when the presence would survive a month of neglect without becoming a liability - when the page is structured, the channels are named, and the posting schedule is written down rather than remembered. The accessible ground that is occupied by intent is the accessible ground that is not reoccupied by someone else.

The occupation is judged by the absence it prevents. The community that occupies its accessible ground has no gap for the rival to slip into, no listing the rival can take over, no presence the rival can claim as its own. The community that leaves an accessible platform unoccupied has invited the rival to occupy it, and the rival that occupies it first has been handed the ground by the community's own absence. The doctrine's counsel is that the accessible ground is occupied by schedule, not by enthusiasm - the posting cadence that is written down continues when the enthusiasm does not.

Stage 3: Garrison the Passes

The third stage is the garrison of the narrow passes. The command takes each chokepoint - the invite link, the onboarding gate, the transfer process, the moderation queue, the announcement gate - and tests it: can a hostile force move through this pass undetected, undelayed, and unturned-back? Every pass that fails the test is garrisoned until it passes. The garrison is recorded, because the pass that was once tested and forgotten is the pass that was never garrisoned.

The test is the substance of the stage. The invite link is tested by asking whether a mass join can move through it undetected; the onboarding gate is tested by asking whether a coordinated agitator would be graduated into trust without scrutiny; the moderation queue is tested by asking whether a report can sit unhandled long enough to be weaponized. The pass that fails the test is garrisoned - verification enabled, roles graduated, the queue assigned a named handler - until it passes. The community that tests its passes on a schedule holds them; the community that assumes they are fine has left them to be tested by the opponent.

Stage 4: Hold the Heights and Refuse the Distance

The fourth stage is the holding of the heights and the refusal of the distance. The command audits the community's authoritative elevations - the announcement channel, the Workshop page, the canonical documentation - and brings any disorder to order. It also writes the community's standing position on distant ground: that disputes raised on far platforms are answered on the community's own ground, or not at all. The refusal is written down, because the refusal made in the calm of Stage 4 is the refusal that holds during the storm.

The height audit asks three questions of each elevation: is it current, is it structured, and is it consulted? A height that is current but unconsulted is a height that nobody defends; a height that is structured but stale is a liability the opponent can quote; a height that is consulted but disordered is an authority that contradicts itself. The community that answers all three questions affirmatively holds its heights. The standing position on the distance is a single sentence - "disputes raised on platforms where our history is not known are answered here, where it is" - and the sentence is written down so that it survives the moment when answering on the distant ground would feel satisfying.

Stage 5: Review and Correct

The fifth stage is the review, and it is the stage that makes the other four durable. On a fixed schedule - the doctrine recommends quarterly - the command re-surveys the ground, re-tests the passes, re-audits the heights, and compares the current map against the recorded baseline. The ground changes: platforms rise and fall, opponents move, members leave. The community that reviews its terrain on a schedule holds its terrain; the community that surveyed once and never again has lost the survey's value by letting it go stale.

Stage 5 in the Schedule

The quarterly review is the point where the protocol stops being an exercise and becomes a habit, and the habit is the point. A single survey classifies the ground once; a quarterly review classifies the ground as it changes. The review takes the recorded baseline from the last pass - the classified platforms, the garrisoned passes, the audited heights, the standing position on the distance - and tests each line against the present: has the platform changed, has the pass been retested, has the height gone stale, has the distance closed? The community that runs the review on schedule finds the changes while they are small; the community that skips the review discovers them when the opponent does.

The review is also the moment of the calamity audit. The six-calamity diagnostic is run against the community's own recent conduct - the engagements of the past quarter, the decisions that were made, the responses that were improvised - and any early form that is found is corrected while it is early. The Institute's 2025 study found that communities which ran the audit quarterly lost an engagement through a recognizable calamity at a 9% rate, against 44% for communities which did not. The review is where the doctrine's two halves - the ground and the calamities - meet on a schedule, and the meeting is what keeps both in order.

Objections

The doctrine of terrain is demanding, and it attracts objections from commanders who find its counsel inconvenient. The objections below are the ones raised most often, and each is answered in the doctrine's voice.

Objection: The doctrine is only metaphor; platforms are not terrain

The objection holds that a Discord server is not a valley and an invite link is not a pass, and that the military language obscures rather than illuminates. The doctrine's answer is that the classification is not literal but structural: the pass is any point through which traffic must funnel, the height is any place from which authority is read, and the distant ground is any platform where the community's strength does not travel. The structure is real even when the metaphor is playful, and a community that has lost its onboarding gate to a coordinated mass-join has experienced the pass whether or not it calls it one.

Objection: We cannot choose our ground; the enemy chooses it

The objection holds that the community cannot decide which platform a dispute is fought on, because the opponent picks the platform. The doctrine's answer is that the ground is chosen twice. The opponent chooses where to strike, but the community chooses whether to answer there. The refusal of the distant ground is the exercise of the second choice, and the second choice is the one that decides the engagement. The community that imagines it has no choice of ground has surrendered the only choice it had.

Objection: Occupying ground first sounds aggressive

The objection holds that the doctrine's counsel to occupy the accessible ground and garrison the passes reads as escalation - as a community preparing for war. The doctrine's answer is that occupation and garrison are defensive arrangements that are invisible in ordinary operation. A community that has a structured onboarding gate, a current documentation page, and a maintained presence on its platforms has occupied and garrisoned its ground without anyone noticing. The aggression the objector fears is not in the garrison; it is in the attack, and the doctrine's garrison is precisely what makes the attack unnecessary.

Objection: The six calamities are bad luck, not error

The objection holds that communities lose engagements because the opponent was stronger, the timing was wrong, or the platform changed the rules. The doctrine's answer is unsparing: the chapter is explicit that the six calamities arise from faults for which the general is responsible, and the Institute's cohort data records that 82% of communities that lost through a recognizable calamity attributed their defeat to bad luck. The attribution is the error. The calamity is the commander's ledger, and the ledger does not accept transfers.

Objection: Abandoning a channel is sometimes the right call

The objection holds that some channels are more trouble than they are worth, and that closing them is sensible management rather than surrender. The doctrine concedes the substance: some positions are genuinely not worth holding, and the chapter's classification exists precisely to make that judgment. The discipline's counsel is that the abandonment be made as a strategic decision - with the terrain classified, the cost measured, and the re-occupation planned or foreclosed - and not as housekeeping. The community that closes a channel without classifying it has surrendered the ground and kept the fight.

Objection: Refusing the distant fight lets lies go unanswered

The objection holds that a community that declines to answer a distant criticism leaves the criticism standing, and that silence reads as admission. The doctrine's answer is that the answer on the distant ground is not an answer the community controls, and that the community's own ground is the place where its word carries. The doctrine does not counsel silence about the substance; it counsels the location. The community that answers a distant criticism on its own announcement channel, where its history and its relationships are present, has answered the criticism with its full strength - and the distant thread, denied its target, exhausts itself.

Objection: This is too much work for a volunteer community

The objection holds that the protocol - the survey, the garrison, the review - demands more of a volunteer staff than the volunteers have to give. The doctrine's answer is that the protocol is peacetime work that replaces crisis work, and that the alternative to a quarterly survey is the all-hands mobilization of an engagement fought on ground nobody classified. The survey can be done by one person in an hour; the garrison can be done by one person in an afternoon. The community that finds the hour and the afternoon too expensive has not priced the alternative.

Objection: The opponent does not read the doctrine

The objection holds that the opponent is not bound by the doctrine, and that a community that refuses the distant fight or declines the mismatched attack is handing the initiative to an opponent who will take it. The doctrine's answer is that the doctrine does not require the opponent's consent. The conduct prescribed here works against an opponent who has never heard of the chapter, because it is built on the opponent's actual behavior - the chokepoint the opponent uses, the distance the opponent exploits, the miscalculation the opponent hopes for. The doctrine is a reading of the opponent, not an agreement with it.

Objection: The accessible ground is too big to occupy

The objection holds that the open platforms are vast, and that a community cannot establish a presence everywhere. The doctrine's answer is that the accessible ground is not occupied everywhere but early - the doctrine's rule is to be before the enemy on the ground that matters, not to be everywhere at once. The community that cannot occupy every accessible platform should occupy the ones that matter, and should maintain the relationships that bridge the ones it does not. The doctrine does not ask for omnipresence; it asks for priority.

Objection: The commander's care sounds like weakness

The objection holds that regarding the community as one's own children is soft, and that the commander should be feared rather than loved. The doctrine's answer is that the chapter pairs the care with the measured limit: the commander who loves without enforcing raises spoiled children who are useless in the engagement. The care that commands is not the absence of discipline; it is the discipline exercised through trust. The community that follows its commander into the deepest valleys does so because it trusts, and trust is not weakness - it is the only mechanism by which a community can be led at all.

Objection: The cohort data is not applicable to my community

The objection holds that the Institute's cohorts - large networks, mod teams, and factions - are not like the objector's own small server, and that the percentages do not transfer. The doctrine's answer is that the cohort data describes structures, not sizes. The abandoned channel, the ungarrisoned pass, and the refused distant fight behave the same in a fifty-member server as in a five-thousand-member network, because the structures - the funnel, the authority, the distance - are the same. The community that dismisses the data because it is small has confused size with structure, and structure is the chapter's subject.

Objection: The doctrine asks us to read the enemy, and reading is spying

The objection holds that the chapter's counsel to read the opponent - to know its moderation structure, its decision speed, its history - crosses into espionage. The doctrine's answer is that the reading is of public conduct: the opponent's published channels, its changelogs, its moderation actions, its visible staffing. None of it requires infiltration, deception, or the exploitation of a leaker, and the doctrine does not counsel any of those. The distinction is the same one drawn elsewhere in the discipline: intelligence that must be obtained by deception taints the community that holds it, and the reading the chapter requires is the reading of what the opponent has already chosen to show.

Objection: We are always fighting on multiple grounds at once

The objection holds that the community rarely faces a single kind of ground - that a dispute can be on the home server, the Workshop page, and the aggregation site simultaneously, and that the doctrine offers no conduct for the multi-ground engagement. The doctrine's answer is that the classification is applied per platform, not per dispute. The community names each front's ground and applies the conduct appropriate to that front: hold the home server's heights, garrison the Workshop page's pass, refuse the aggregation site's distance. The multi-ground engagement is not a contradiction of the doctrine; it is the doctrine applied several times, and the community that classifies each front separately has a conduct for each.

Objection: Occupying ground first is impossible for a community with no rival

The objection holds that the chapter's counsel presupposes an opponent - that a community with no rival has no need to occupy, garrison, or refuse, and that the protocol is wasted on it. The doctrine's answer is that the ground is prepared against the opponent that has not yet arrived, which is precisely the opponent the preparation is for. The rival that appears in a community's life is almost always the rival that appeared in a community that was unready for it, and the unreadiness was the invitation. The community that occupies its ground with no rival in sight has done the work before it was needed, which is the only time the work can be done at leisure.

FAQ

Q: What is the difference between accessible ground and temporizing ground?

A: Accessible ground is ground that both sides can freely traverse - the open platform, the neutral hub - and the doctrine's rule for it is to occupy it before the enemy. Temporizing ground is ground where neither side gains by moving first - the contested resource, the joint announcement - and the doctrine's rule for it is to refrain from moving and entice the enemy out instead. The first is about being early; the second is about being still.

Q: When should a community close a channel?

A: Only as a deliberate strategic decision, with the ground classified and the cost measured. The Institute's register records that 71% of closed channels are later reopened and only 27% of reopenings succeed, so the closure should be treated as permanent. If a channel is troublesome but the community wants the position, moderate it instead of closing it. If the position is genuinely not worth holding, close it with both eyes open - but do not expect to reclaim it.

Q: How do I know if a pass is weakly or fully garrisoned?

A: Test the pass. A pass is fully garrisoned when a hostile force cannot move through it undetected, undelayed, or unturned-back - when the verification gate is checked, the queue is handled, and the funnel is controlled. A pass is weakly garrisoned when the defenses exist on paper but not in practice. The doctrine permits attacking only the weakly garrisoned pass, and the discipline's test is whether the pass can be taken with less than the community's full strength and without a prolonged campaign.

Q: What is the "raised and sunny spot" of a community?

A: It is the authoritative elevation that is both raised and visible - the place from which the community commands the view and the place at which the community is viewed. The announcement channel that everyone reads, the Workshop page that every subscriber checks, the documentation that every new member is pointed to. The spot is only half held if it is authoritative but unread; the community must keep its heights both current and consulted.

Q: Should we ever fight on distant ground?

A: Rarely, and only when the community's strength travels - when the community has maintained relationships on the distant platform, or when the platform's audience is actually the community's audience. The doctrine's default is to refuse the distant engagement and answer on the community's own ground. The Institute's 2023 study found that communities which refused the distant engagement resolved disputes without lasting damage at 71%, against 34% for communities which accepted it.

Q: Which calamity should a commander watch for first?

A: Disorder, because it is the father of the others. A community with no discipline and no method cannot execute any of the preventions - it cannot measure before attacking, cannot hold its line, cannot maintain its officers, cannot read its opponents. The community that fixes its disorder first has reduced the risk of the other five. The community that watches for flight or rout while its own house is disordered has watched the wrong calamity.

Q: Does the doctrine of care mean never punishing members?

A: No. The doctrine's care has a measured limit: the commander who is indulgent without authority, kind-hearted without enforcement, raises spoiled children who are useless in the engagement. The care that commands includes the discipline, and the community that is loved but never disciplined cannot fight. Care is the reason the discipline is enforced; it is not the reason the discipline is waived.

Q: How often should terrain be reviewed?

A: The doctrine recommends quarterly - the re-survey, the re-testing of the passes, the re-audit of the heights, and the comparison against the recorded baseline. The ground changes on its own schedule: platforms rise and fall, opponents move, members leave. A survey that is never repeated is a survey that has gone stale, and a stale survey is worse than no survey, because it records confidence the community no longer holds.

Q: What is the first thing to do when a conflict starts?

A: Classify the ground before responding. Ask where the engagement is being fought, what that ground is to the community, and what it is to the opponent. The answer to those three questions determines the conduct - whether to occupy, to hold, to entice, or to refuse. The community that responds before classifying has conducted an engagement on ground it never read, and the doctrine's record is clear about where that ends.

Q: Is a review bomb an attack on terrain, or an attack on reputation?

A: It is both, and the terrain reading explains the order. The review bomb is an assault on the community's most visible height - the Workshop page - designed to bring the elevation down by overwhelming its rating. The community that defends the height by holding the page, keeping its description and changelog current, and letting the coordinated wave exhaust itself has defended the terrain. The community that removes the page, hides the reviews, or abandons the listing has surrendered the height, and the reputation follows the terrain: the height lost is the rating lost.

Q: How does this chapter differ from the chapter on the nine situations?

A: The tenth chapter classifies the fixed ground - the six kinds of terrain - and the eleventh chapter classifies the situations that arise upon the ground as the community moves through an engagement. The distinction is between the map and the campaign: the tenth chapter tells the commander what kind of ground is underfoot, and the eleventh tells the commander what kind of position the community occupies on that ground at the moment of decision. The two chapters read together, and the terrain is the situation's foundation.

Q: What should a community do about an opponent that occupies its heights first?

A: The doctrine's rule for the contested height is the same as its rule for the contested pass: assess whether the height is fully or weakly held. A height that is fully held - an announcement channel with real authority, a page with a real audience - is not to be assaulted directly. A height that is weakly held - an authoritative channel nobody consults, a page that is stale and disordered - can be taken by being better, faster, and more current than the occupant. The height is held by authority, and authority is not transferred by assault; it is transferred by being more worth reading.

Glossary

Term	As the doctrine uses it
Accessible ground	Ground both sides can freely traverse; occupied first
Entangling ground	Ground that can be abandoned but is hard to re-occupy; not to be abandoned casually
Temporizing ground	Ground where neither side gains by moving first; entice the enemy out
Narrow pass	A chokepoint through which traffic must funnel; garrisoned first
Precipitous height	An authoritative elevation, hard to assault; occupied and held
Ground at a great distance	A position where the community's strength does not travel; refused
Flight	The calamity of attacking an opponent of overwhelming scale
Insubordination	The calamity of a membership that runs the leadership
Collapse	The calamity of officers in rebellion
Ruin	The calamity of a commander without authority
Disorder	The calamity of no discipline and no method
Rout	The calamity of no recognition of the enemy
The country	The community's own terrain - its platforms, records, and structure
The garrison	The procedure that secures a pass, maintained in peacetime

Appendix A: The Conduct Matrix of the Six Kinds of Ground

Ground	How to recognize it	The doctrine's conduct	The failure mode
Accessible	Both sides present, open platforms	Occupy it first, maintain the presence	Arrive late, or occupy and neglect
Entangling	Abandoned once, hard to reclaim	Do not abandon; moderate instead	Close channels as housekeeping
Temporizing	Neither side gains by moving first	Do not advance; entice the enemy out	Move first out of impatience
Narrow passes	Traffic must funnel through them	Occupy first, garrison strongly	Leave a chokepoint ungarrisoned
Precipitous heights	Authority is read from them	Occupy first, keep current and visible	Let the height go stale and unread
Great distance	Strength does not travel there	Refuse the fight; answer on own ground	Fight there and lose the advantages

The matrix is meant to be printed or pinned where the command meets, and the test of whether it has been read is whether the community can answer, for any live dispute, which row it is on. The community that can name the row has the conduct; the community that cannot has the failure mode.

Appendix B: The Terrain Survey Checklist

A quarterly review, completed by the command:

• [ ] Every platform the community touches has been classified against the six kinds of ground
• [ ] The accessible platforms the community wants have a maintained presence with a written posting schedule
• [ ] The invite link is permanent, verification is enabled, and no silent re-issues have occurred
• [ ] The onboarding gate is structured: roles assigned, expectations stated, hostile entry detected
• [ ] The transfer process has documentation, a named owner, and a maintained index
• [ ] The moderation queue has a clear procedure, a visible backlog, and a named handler
• [ ] The announcement gate is a single authoritative channel with no shadow mirrors
• [ ] The announcement channel is current and consulted, not stale and ignored
• [ ] The Workshop page is current, structured, and authoritative
• [ ] The canonical documentation is accurate and pointed to by new members
• [ ] The community's standing position on distant ground is written down
• [ ] The six calamities were reviewed against the community's recent conduct, and any recognizable error was acknowledged
• [ ] The survey baseline was compared against the present map, and every change was recorded

A completed checklist is the record that the protocol ran; an uncompleted one is the record that it did not, and the doctrine treats the two records differently when the engagement arrives.

Conclusion

The ground decides the engagement, and the doctrine of terrain requires the commander to know the six kinds of ground and the conduct befitting each. The community that occupies the accessible ground, garrisons the narrow passes, holds the precipitous heights, and refuses the distant fight has made the terrain its ally; the community that mishandles its ground courts one of the six calamities by its own hand. The Yamak Institute's cohort data confirms the chapter's symmetry: the ground is the soldier's best ally, and the commander's mishandling of the ground is the commander's most reliable enemy.

The classification is a reading tool, and it is read twice - once for the community and once for the opponent. The six kinds of ground are not a menu but a map, and the map is only as good as the survey that keeps it current. The community that surveys its terrain in peacetime, garrisons its passes, holds its heights, and refuses its distances is the community that has made the ground an ally before the opponent ever arrives. The community that improvises its terrain during the engagement has made the ground the opponent's ally instead.

The six calamities are the ledger of that mishandling, and they are the chapter's sharpest warning. They arise not from the ground and not from the enemy but from the commander's own faults, and the community that audits itself against the six early forms corrects the calamities while they are still cheap. The country is the soldier's best ally, and the commander's care for the community is the relationship that makes the country usable; the two together are the doctrine's answer to what holds a community together on any ground. The community that knows its ground, audits its conduct, and cares with discipline has done the chapter's work.

The ground is known. The situations that arise upon it are the subject of the next chapter. Continue to The Nine Situations, on the nine varieties of ground and the conduct appropriate to each.