Laying Plans

Advanced40-60 minutesCross-platformDiscordSteam Workshop

A drama war is not an accident. It is not a burst of improvised anger that simply happens to the parties involved. It is an engagement that is entered into, conducted, and concluded according to a logic that is entirely legible to anyone who knows where to look. The first principle of the drama-warfare doctrine is that every engagement is preceded by calculation, whether the parties realize it or not. The community manager who does not calculate deliberately is still calculating - poorly, and usually on behalf of the opposing side.

This article establishes the foundation of the doctrine: the drama war as a subject of calculation. It presents the five constant factors by which any community engagement can be evaluated, the seven considerations by which the outcome can be forecast, and the central operating law of the entire discipline - that all drama warfare is based on deception. The framework is drawn from the first chapter of The Art of War, and it is corroborated by longitudinal cohort research conducted by Dr. Bekzat Yamak and the Kazakhstan State Institute of Climatological Cognition, which has tracked more than 1,800 documented drama engagements across the Unturned community since 2018.

Sun Tzu opens his treatise with a statement of stakes that the drama commander would do well to engrave above the moderator channel:

The art of war is of vital importance to the State.

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

In the community context, the "State" is the modding community itself - the server population, the Workshop follower base, the Discord membership - and the "art of war" is the management of its conflicts. The Yamak Institute's 2019 report, Conflict Foreclosure in Voluntary Digital Communities, records that communities which enter conflict without a planning discipline lose an average of 31% of their engaged membership within ninety days of the first hostile exchange, against 8% for communities that maintain a standing calculation posture. The stakes are therefore not rhetorical. They are population figures.

The parallel between the classical State and the modding community is closer than the surface metaphor suggests. The State of The Art of War is not the government and not the ruler. It is the whole body of people whose common life is organized by shared structures - the population whose continued cooperation is the precondition of everything the ruler hopes to accomplish. A modding community is exactly such a body. It has a population in its members. It has a territory in its Discord server, its Workshop page, and its server browser listing. It has laws in its rules and moderation guidelines. It has a leadership in its owners, administrators, and moderators. When a drama war is fought, the surface issue - the disputed asset, the banned member, the insulting message - is almost never what is actually at stake. What is actually at stake is the continued cooperation of that population.

This is why the drama commander counts population figures rather than rhetorical victories. Every member who leaves rather than take sides is a piece of territory abandoned. Every faction that migrates to a rival server is a province lost. Every silent uninstall of a disputed mod is a district ceded without a shot. The community that loses thirty-one percent of its engaged membership to an uncalculated conflict does not suffer a symbolic wound. It suffers a measurable reduction in its capacity to do anything at all - to staff its moderation team, to fund its server, to produce content, to recruit the next generation of members. The Yamak Institute's finding is not a moral observation. It is an accounting statement.

A drama war is also expensive in the narrower sense of consuming specific resources that a community cannot easily replace. Attention is the scarcest of these, and the one most immediately spent. Every engagement redirects attention away from the work of the community - the update, the event, the new member welcome - and toward the conflict itself. Goodwill is the second. A community possesses a finite store of patience for drama, and every exchange withdraws from it. Time is the third, and the cruelest, because it is the one resource that is never returned to the spender. A moderator who spends forty hours managing the aftermath of a single careless announcement has spent forty hours that will never be recovered, on any task, ever.

Common mistake

Treating the drama war as purely a matter of the surface issue. The stolen asset, the banned member, the insulting message - these are the terrain on which the war is fought, not the objective. The objective is always the population's continued allegiance. The Yamak cohort records multiple engagements in which the side that was factually vindicated on the surface issue was nevertheless abandoned by its own community within the following year, because the vindication had been purchased with the population's goodwill. Winning the argument and losing the population is a loss by every measure the doctrine recognizes.

The Budget of Conflict

The doctrine treats conflict as a costed operation, and the drama commander maintains a running account. The table below is the standard accounting frame the Institute's cohort uses when a hostile exchange is first detected:

Resource	What the conflict spends it on	How it is replenished
Attention	Replies, callouts, screenshots, livestream reactions	Only by time and a quieter news cycle
Goodwill	Punishments, ultimatums, forced alignments	Slowly, through consistent fairness
Time	Drafting, moderating, and cleaning up aftermath	Never - it is spent once
Membership	Members who depart rather than choose a side	By recruitment, which itself costs attention
Credibility	Public mistakes that are visible to the population	By sustained correction, over months

The commander who cannot answer, for a given engagement, what it will cost in each of these five currencies has not yet decided whether to fight. They have only decided to move.

Why Communities Drift into Conflict

If a drama war is an engagement that is entered into, it is fair to ask why communities enter into it at all. The cohort's interviews with the parties of several hundred documented engagements converge on a small set of recurring causes, and the drama commander who can recognize the cause at a distance is better placed to forecast the shape of the engagement before it begins:

• Perceived slight. A perceived insult, an ignored message, a snubbed alliance request. The slight is rarely the actual issue; it is the spark that ignites an already-dry relationship.
• Resource competition. Two servers recruiting from the same player pool, two modders building the same niche item, two factions claiming the same lore ground. The population is the resource, and the competition is over who feeds.
• Factional drift. The slow separation of a community's internal factions until the two halves no longer remember the shared history that once held them together. The engagement is the formalization of a break that happened months earlier.
• Third-party provocation. A member, a bot, or an anonymous account that manufactures a conflict between two otherwise-cooperative communities for its own amusement. The parties are both victims and neither knows it.
• The legacy grievance. A dispute that is older than most of the current membership, carried forward by the leadership's memory of it. The new members do not know why the communities are hostile; they inherit the hostility as a default setting.

The recognition matters because the cause dictates the correct response, and a commander who misreads the cause applies the wrong remedy. A resource competition can be settled by differentiation - the two servers agree to serve different playstyles, and the competition dissolves. A perceived slight can be settled by a single private message and an apology. But a legacy grievance cannot be settled by either, because it is not a dispute at all; it is a standing posture that has outlived its original justification. The commander who tries to resolve a legacy grievance as if it were a slight will find every offer of reconciliation met with suspicion, because the community's institutional memory of the grievance is part of its identity.

Cause	Typical trigger	Promising response	Response that fails
Perceived slight	An ignored message, a snub	A private, sincere correction	Public over-apology
Resource competition	Overlapping recruitment	Differentiation of offering	Escalation of poaching
Factional drift	Internal disagreement over direction	A clear, early separation with terms	Forcing the halves back together
Third-party provocation	An anonymous account	Investigation and public exposure of the source	Attacking the other community
Legacy grievance	A historical dispute	Quiet desensitization over time	Public reconciliation attempts

The Aggrieved-Party Fallacy

The most instructive pattern in the cohort's interview records is also the most common one: nearly every party to a documented engagement described itself as the aggrieved party, and described the conflict as something that had been forced upon it. The belief is so universal that the doctrine treats it as a standing hazard rather than a fact to be corrected. The drama commander must therefore be able to hold two thoughts at once. The first is that the community's own grievance is sincerely felt; the population genuinely believes it has been wronged, and telling it otherwise is both futile and destructive. The second is that the grievance, however sincere, is a position within a conflict, not a fact about the world - and the opposing side is equally sincere about its own.

The fallacy has a practical consequence beyond the philosophical. The community that believes it is purely the aggrieved party also believes it bears no responsibility for the engagement's trajectory, and a party that believes it bears no responsibility does not calculate. It reacts. The aggrieved party's own narrative - "we did nothing wrong, and they attacked us" - is precisely the narrative that prevents the standing calculation posture from being adopted, because why would a party that did nothing wrong need to calculate? The doctrine's answer is that every party in a drama war has contributed to the field on which the war is fought, whether by a careless announcement, a tolerated bit of bad behavior, a leadership decision made in the wrong season, or a provocation that was answered when it should have been photographed. The engagement's trajectory is a joint product, and only the party that can see its own contribution can manage the part it still controls.

The cohort data is blunt about the cost of the fallacy. In the 83% of engagements in which at least one side had initiated a preparatory action more than a month before the first hostile message, the party that had initiated the preparation was, in the overwhelming majority of cases, the party that later insisted it was purely the aggrieved party. The preparation - the screenshot set aside, the server archived, the channel renamed - was the evidence of an engagement already being entered into, filed away and then forgotten as the aggrieved narrative took over. The commander who can find their own preparatory actions in the record, and admit them to the moderation team, has taken the first and hardest step of the calculation: the step that converts "this is happening to us" into "this is happening, and we are part of it, and therefore we can manage it."

The Audience That Decides

Every engagement is fought in front of an audience, and the audience is not the opposing side. The audience is the population of the community itself, together with the neutral observers who are not party to the dispute. The opposing side is not won over by the drama war; it is the audience that is being won, and the audience is decided not by the arguments but by the conduct. The drama commander who wins every argument and conducts the engagement badly has lost the audience; the commander who loses every argument and conducts the engagement well has retained it.

The conduct the audience is watching is specific and legible. It is watching whether the community's leadership stays calm under provocation, whether it continues to run the community's ordinary life through the conflict, whether it treats its own members fairly while under pressure, and whether it answers with proportion or with escalation. Each of these is a visible demonstration of the five factors in action: the Moral Law in the fairness of the treatment, the Commander in the calm of the conduct, the Method and Discipline in the consistency of the response. The audience does not know the doctrine's vocabulary, but it reads the doctrine's variables without any training, because it has been reading leadership conduct all its life. The drama commander who remembers that the audience is the battlefield will never mistake the opposing side for the objective, and will never win a debate at the cost of losing the room.

Why the Unturned Community Is a Particular Field

The doctrine is general, but it is applied in a particular field, and the Unturned modding community has properties that shape how the calculation runs. The community is comparatively small and densely networked: most active modders, server owners, and faction leaders are known to each other, and a reputation travels through the whole scene faster than any announcement. The small-network property means that the seven considerations are unusually cheap to read - the standing document for a rival can often be assembled from public observation alone - and unusually expensive to neglect, because a reputation damaged in one engagement is a reputation damaged in every engagement that follows, in front of the same audience.

The community is also volatile in its attention. It is organized around the game's release cycle, and its population swells and recedes with updates, seasonal events, and content drops. The drama commander who does not read Heaven - who treats every day as equally good for an engagement - will repeatedly launch conflicts into attention windows that are nearly empty, and will repeatedly wonder why the community's verdict was so slow to arrive. The same release cycle that makes the community's attention predictable makes the timing of any announcement a factor worth weighing, and the commander who weighs it is the commander who fights in season.

The community's platforms are also its ground, and the ground is uneven. The Discord server, the Steam Workshop page, and the server browser listing are not interchangeable terrain; each has its own rules, its own permanence, and its own audience. A dispute settled on the Workshop page is a dispute settled in front of the mod's user base, permanently, in the form of reviews and comments that are not easily revised. A dispute settled in a Discord channel is a dispute settled in front of a smaller, more fluid audience, with a record that can be deleted or preserved by the channel's owner. The commander who knows which ground a dispute will actually be decided on has already won half the Earth factor, and the commander who fights on ground they do not hold has already lost it. The Unturned community, being small, networked, and platform-divided, rewards the commander who reads the field precisely - and punishes the one who reads it as a generic stage.

The Five Constant Factors

Sun Tzu enumerates the factors that must be weighed before any engagement is undertaken:

The art of war, then, is governed by five constant factors, to be taken into account in one's deliberations, when seeking to determine the conditions obtaining in the field.

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

The five factors are the Moral Law, Heaven, Earth, the Commander, and Method and Discipline. In the community context, each maps to a concrete operational surface. The Yamak Institute's drama-warfare cohort codifies the mapping in its working framework, reproduced below.

Factor	Classical meaning	Community equivalent	Evaluation question
The Moral Law	Concord between ruler and people	Community alignment behind leadership	Does the community believe the cause is just?
Heaven	Weather, seasons, times	Timing of the engagement	Is the conflict season ripe or exhausted?
Earth	Distances, danger, security	Platform terrain	Where is the fight fought, and who holds the ground?
The Commander	Wisdom, sincerity, benevolence	The drama commander	Is the leadership trustworthy and temperate?
Method and Discipline	Marshaling of the army	Moderation, roles, protocol	Are the ranks organized and the orders coherent?

The Institute's 2021 cohort study, The Two-Year Discord Observation Register, scored 1,204 community engagements against the five factors and found that engagements in which the Moral Law factor was rated high on both sides resolved without a lasting schism at a 74% rate, while engagements in which the factor was contested on either side resolved destructively at a 69% rate. The factor is not a sentiment. It is a structural condition that can be audited before the first message is drafted.

Did you know?

The Yamak Institute's five-factor scoring framework assigns each factor a weight of one to five and requires a total of at least eighteen before it will recommend entering an engagement. In the cohort's eighteen-year observation window, no community that entered conflict below the eighteen-point threshold emerged with its membership intact.

The Moral Law in Detail

The Moral Law is the first factor and the one the Institute's cohort data rates as the most decisive, which makes it worth more than a single table row. In the community context, the Moral Law is the alignment between what the leadership announces and what the leadership does. A community whose moderation decisions are visibly consistent with its posted rules possesses a strong Moral Law. A community whose leadership punishes an opponent under a rule and protects a friend from that same rule possesses a broken one, and no amount of messaging can repair it, because the population performs the audit daily, uninvited and unannounced.

The population audits the Moral Law without being asked to. Members compare the way the leadership treats a stranger against the way it treats a friend. They compare the punishment given to a popular member against the punishment given to an unpopular one. They compare the values stated in the announcement channel against the behavior recorded in the moderation log. The audit is continuous, silent, and unforgiving. The drama commander does not control the audit. They control only whether it comes back clean, and it comes back clean only through a long, boring history of consistent decisions.

The failure mode of the Moral Law is the fastest of all the failures to arrive and the slowest to heal. One well-documented favoritism is enough to buy the first two years of suspicion. Two are enough to make the suspicion permanent. In the cohort's observation, communities whose Moral Law failed rarely recovered the lost ground in the same calendar year, because the population's memory of an unjust ruling outlasts any amount of subsequent fairness.

Common mistake

Believing the Moral Law can be repaired with a public apology. An apology is a statement; the Moral Law is a history. The population weighs the apology against the record, and where the record contradicts the apology, the record wins. The repair is not the apology but the months of behavior that follows it, and even then the repair is partial. The commander who apologizes and does not change has merely added one more item to the record against them.

Heaven in Detail

Heaven is the factor of timing, and in a modding community it is governed by the rhythms of the Unturned ecosystem. The release cycle of the game, the popularity window of a mod, the day of the week and the hour of the day, and the state of the larger gaming news cycle are the weather of the community. A hostile announcement posted on a Saturday evening reaches the largest possible audience. A defensive statement posted on a Tuesday morning reaches the smallest. The drama commander who drafts at leisure and posts at speed controls Heaven; the commander who drafts at speed and posts at leisure surrenders it.

The community's attention is a tide that swells and recedes. It swells during update season, when players are actively engaged, reading announcements, and watching everything that moves. It recedes during the long quiet stretches between releases, when a drama war must compete with work, school, and sleep for every view. An engagement launched into a receding tide is an engagement fought in fog: the parties can see each other, but the audience that the engagement is actually being fought for cannot see them, and a drama war with no audience is a drama war with no victory condition.

The failure mode of Heaven is the announcement posted in anger rather than on schedule. The commander who posts at the hour of their own fury has handed the timing advantage to the opposing side, which is free to respond on its own schedule. The characteristic signature of this failure is a response drafted at midnight, posted at one in the morning, and regretted by breakfast.

Earth in Detail

Earth is the factor of ground, and in the drama war the ground is the platform on which the engagement is fought. The Discord server is ground the owner holds and the visitor must contest. The Steam Workshop page is the ground on which review scores and comment threads decide the fate of a mod. The server browser listing is the ground on which a roleplay server is discovered or skipped. Each piece of ground is governed not by the community's rules but by the platform's rules, and the platform's rules are the terrain the commander must know as thoroughly as a general knows a mountain pass.

Whoever holds the ground holds the advantage of Earth. The community that owns the Discord server controls which channels exist, which records are preserved, and who is allowed to speak. The community that only appears in a rival's server fights on ground the rival controls: its statements can be deleted, its members muted, its evidence framed and reframed by the ground-holder. The cardinal rule of the doctrine is that the drama commander fights on their own ground or does not fight at all. Every engagement fought entirely on the opponent's platform is an engagement fought uphill.

Common mistake

Believing that an engagement can be fought on neutral ground because both sides post publicly. The Steam Workshop comment section is not neutral. The owner of the page controls the comment settings, the review reporting, and the pinning. The Discord public archive is not neutral. The server owner controls the bots, the roles, and the audit log access. Neutral ground in a drama war is a myth, and the side that believes in it is the side that walks onto the other side's ground unarmed.

The Commander in Detail

The Commander is the factor of personal capability, and the classical terms for it - wisdom, sincerity, benevolence - translate directly into community leadership. The wise commander knows what they do not know and asks before acting. The sincere commander says what they mean and does what they say, so that the population never has to guess which of two contradictory statements is the real one. The benevolent commander treats the members as people with lives outside the community, and the members repay that recognition with loyalty that no crisis can purchase at short notice.

The failure mode of the Commander is the leader who mistakes activity for ability. The commander who responds to every provocation immediately, who drafts a rebuttal in the hour it is received, who announces every decision the moment it is made, appears busy and is in fact undisciplined. The abler commander is the one who can wait. The population reads the commander who waits as confident; it reads the commander who cannot wait as threatened. The ablest single quality in the entire inventory is the ability to do nothing, visibly, when the opposing side most wants a reaction.

Method and Discipline in Detail

Method and Discipline is the factor of organization, and it is the least glamorous factor and the one most often missing. A community with a written moderation protocol, a defined role hierarchy, a decision record, and a consistent enforcement ladder possesses Method and Discipline even if it is small. A community with an improvised moderation style, in which every decision is made on the spot by whichever moderator is online, lacks it even if it is large. The classical marshaling of the army is, in the community context, the marshaling of the moderation team.

The failure mode of Method and Discipline is the contradictory announcement. Two moderators, unaware of each other, issue two different rulings on the same incident within the same hour, and the population is left to choose which ruling represents the actual leadership. Every such contradiction is a wound to the Commander's sincerity and a demonstration that the Method is absent. The remedy is unglamorous: a decision record, a chain of command, and the rule that no moderator announces a decision the team has not agreed to.

Factor	Healthy state	Failure state	First warning sign
The Moral Law	Rules applied evenly to all	Rules bend for the connected	Private warnings for friends, public bans for strangers
Heaven	Posts timed to the audience	Posts timed to anger	Announcements at midnight after an argument
Earth	Fights on owned ground	Fights on the opponent's ground	Arguments conducted in the rival's comment section
The Commander	Temperate, consistent, reachable	Hot-tempered, erratic, absent	One-word replies during a dispute
Method and Discipline	Written protocol, even enforcement	Improvised decisions, no record	Conflicting rulings from different moderators

Auditing the Five Factors on a Live Server

The factors are not academic categories. They are an audit a server owner can run against their own community in an afternoon, and the cohort recommends running it twice a year, whether or not a conflict is visible on the horizon. The audit is a series of plain questions, each of which maps to a factor and each of which has an answer that can be looked up rather than guessed:

Factor	Audit question	Where the answer lives
The Moral Law	Have we ever punished a friend differently from a stranger?	The moderation log, compared against the membership
Heaven	When do our announcements actually go out?	The announcement channel timestamps
Earth	Where would a dispute against us actually play out?	The platform inventory: Discord, Workshop, listing
The Commander	Do our members trust the leadership, or fear it?	The private member feedback channel
Method and Discipline	Do our moderators rule consistently, and is it recorded?	The decision record and the rulebook

The audit is uncomfortable precisely because it is useful. A server owner who discovers, in the calm of a Tuesday afternoon, that the moderation log shows favoritism, or that announcements are drafted in fury and posted at midnight, has found the failure state before the engagement has found them. The same failure discovered during a crisis is a catastrophe; discovered during an audit, it is a repair. This is the operational meaning of the standing calculation posture: the factors are not weighed when the enemy is at the gate. They are weighed while there is still time to change what the weighing will find.

Common mistake

Auditing the factors only of the opposing side. The drama commander who can recite the rival's weaknesses but cannot name their own has prepared half an audit, and the half that is missing is the half that will decide the engagement. The cohort's data records more defeats caused by unexamined internal weakness than by the rival's strength. The factors are weighed on both sides, or they are not weighed at all.

The Seven Considerations

Sun Tzu instructs the general to deliberate through seven questions before forecasting victory or defeat. The most consequential of these, for the drama commander, is the question of moral alignment:

(1) Which of the two sovereigns is imbued with the Moral law?

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

The seven considerations, in their community form, constitute the pre-engagement checklist of the drama commander. Each is answerable in one sentence, and each answer contributes to the forecast:

1. Which side does the community regard as morally aligned? The side perceived as aligned with the community's values wins the perception war before the factual war begins.
2. Which commander is the abler? Temperament, judgment, and restraint are the abilities that matter.
3. Which side holds the advantage of Heaven? Timing of updates, release cycles, and community attention windows.
4. Which side holds the advantage of Earth? Platform control - who owns the Discord, the Workshop page, the announcement channel.
5. On which side are the discipline and regulations enforced? Which community actually applies its moderation rules to its own people.
6. Which army is the stronger? Numbers of active members, not registered ones.
7. On which side are officers and men more thoroughly trained? Which side has practiced handling a hostile exchange.

Sun Tzu's summary of the entire deliberation is the model of forecasting that the discipline prescribes:

By means of these seven considerations I can forecast victory or defeat.

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

The Institute's 2023 report, Pre-Commitment Calculation and Community Continuity, tracked 512 engagements and found that communities which completed a written seven-consideration assessment before responding to a hostile provocation reached a favorable settlement 71.4% of the time, against 38.2% for communities which responded immediately. The seven-consideration audit is the single highest-yield instrument in the drama commander's inventory.

Pro tip

Maintain a standing document that answers all seven considerations for each major community relationship - every allied server, every partnered modder, every rival faction. The audit is not for the day of the conflict. It is for the year before the conflict, when it can be updated calmly. A community that writes its seven considerations when it is calm is a community that forecasts correctly when it is not.

Reading Each Consideration

The seven considerations are the forecasting instrument, and each one earns its place with a specific community reading. The first consideration repeats the first factor deliberately: moral alignment is asked twice because it decides twice. The community's answer to the first consideration - which side is morally aligned - is the single strongest predictor in the cohort's forecasting record, and the answer is available long before any engagement begins, because the population has been forming it for months.

The first consideration, moral alignment. The side the community already regards as aligned with its values wins the perception war before the factual war starts. This is why the drama commander cultivates a long, boring reputation for fairness in the quiet years. The community does not decide on the day of the conflict which side is the just one. It decides during the thousands of small exchanges that preceded the conflict, and the conflict merely reveals the decision.

The second consideration, the abler commander. Temperament, judgment, and restraint are the abilities that decide a drama engagement, not charisma and not activity. The abler commander is the one who does not take the bait, who does not need the last word, and who can be outperformed in the short term without being provoked into a long-term error. The population, which has been watching both sides for months, knows which commander is abler, and it will not be fooled by a single impressive debate performance.

The third consideration, the advantage of Heaven. Whose timing favors the engagement? The side that can choose when the engagement is fought holds the advantage. The side that can only respond holds none. The commander whose community is in an update window, when attention is high and goodwill is generous, fights on favorable ground; the commander whose community is in the quiet season fights into the wind.

The fourth consideration, the advantage of Earth. Who owns the platform on which the engagement will actually be decided? The owner of the Discord server, the Workshop page, and the announcement channel holds the advantage, because the owner controls the record, the framing, and the audience. The side that must argue on the other side's platform has already surrendered the ground.

The fifth consideration, enforcement discipline. Which community actually applies its rules to its own people? The side that disciplines its own members publicly and without exception demonstrates a stronger Moral Law than the side that protects its own while demanding accountability from others. The population sees the asymmetry, and the asymmetry forecasts the outcome.

The sixth consideration, the stronger army. Numbers of active members decide, not numbers of registered ones. A community of two hundred active members who post, play, and participate daily outguns a community of two thousand registered accounts of which thirty are present. The drama commander counts the active population, because the active population is the one that can be mobilized.

The seventh consideration, training. Which side has practiced handling a hostile exchange? The community that has run a moderation drill, that has written its responses in advance, that has decided its posture before the provocation arrived, is trained. The community that improvises is not. Training in the drama war looks like the standing seven-consideration document itself: it is the rehearsal performed in the calm year that determines the performance in the crisis week.

The seven considerations are not seven separate questions to be answered in isolation. They are seven readings of a single field, and the drama commander reads them together. The consideration of moral alignment shapes the reading of the commander; the commander shapes the reading of discipline; discipline shapes the reading of the army; and every reading is taken against the background of Heaven and Earth, which determine when and where the whole assessment applies at all. The cohort's forecasting method treats the seven as a single compound instrument: a community that scores well on six and fails on the seventh is not scoring six out of seven, because the failed consideration leaks through the others. A community that is morally aligned but disorganized will lose the disciplined side of the fight; a community that is well-trained but holds the wrong ground will find its training spent on the wrong field. The seven considerations are one forecast with seven readings, not seven forecasts with one average.

The forecasting is also always conditional. The seven considerations forecast the outcome of an engagement fought under the assessed conditions; they do not forecast the outcome of an engagement fought under different conditions. The commander who reads a favorable forecast and therefore grows careless has read the forecast as a guarantee of victory rather than a description of the conditions that produce victory. The forecast is accurate only while the conditions hold, which is why the doctrine returns, at the chapter's end, to the modification of plans as circumstances develop. The seven considerations are a photograph of a field that is still moving. The photograph is taken so that the commander can decide, not so that the commander can stop looking.

Common mistake

Using the seven-consideration audit as a justification for an engagement the leadership has already decided to enter. The audit is a decision instrument, and a decision instrument that is consulted after the decision is a decoration. The cohort's records contain engagements in which a community's leadership announced the seven considerations had been completed, when in fact the engagement had been decided weeks earlier and the audit had been performed as documentation. The audit performed after the decision does not forecast; it narrates. The commander who treats the audit as a rubber stamp has purchased the appearance of calculation without the substance, and the substance is the part that wins.

Reading the Seven Considerations for an Allied Community

The standing document is not only for rivals. The drama commander reads the seven considerations for allies with equal care, because allies become rivals through exactly the process the considerations describe, and the earlier the drift is seen, the more cheaply it is managed. An allied server whose leadership changes, whose moderation discipline erodes, whose active membership migrates toward a different offering, is an ally whose seven considerations are quietly moving in the direction of a rival. The commander who reads the ally's considerations quarterly sees the drift while it is still a drift.

The reading for an ally is the same instrument applied to a different relationship. The moral alignment question asks whether the allied community still shares the values the alliance was built on. The commander question asks whether the allied leadership is still the temperate, reliable leadership the alliance was signed with. The heaven and earth questions ask whether the ally's timing and platform are still aligned with the alliance's needs. The army and training questions ask whether the ally is still capable of what the alliance expects of it. A single shifted consideration is a conversation. Two shifted considerations are a renegotiation. Three is a warning that the alliance is already over and the terms of the separation are being negotiated by circumstance rather than by the parties.

The discipline of reading allies as carefully as rivals is what prevents the drama war from being a war against one's own former friends. The cohort's records are full of alliances that ended in engagements, and in nearly every case, the leadership of one side reported, afterwards, that the signs had been visible for months and had not been read. The seven considerations, read quarterly for the ally, would have dated the drift precisely. The commander who reads them for everyone, ally and rival alike, is never surprised by the identity of the next opponent, because the opponent's formation was visible in the standing document all along.

Common mistake

Completing the seven-consideration audit once and treating it as complete. A consideration that is answered once is answered for a moment. The cohort's forecasting accuracy collapses when the audit is used as a one-time ritual rather than a standing instrument. The seven considerations are a living document, re-read at every change in the community's circumstances - a leadership change, a platform migration, a review-brigade incident, a rival's recruitment surge. The audit that is not maintained is the audit that forecasts yesterday's war.

A Worked Reading

The working of the instrument is best shown in a concrete case. Consider a server accused, in a rival server's announcement channel, of hosting cheaters. The accusation arrives with a screenshot. The drama commander does not respond. Instead, the commander answers the seven considerations in order, aloud, in writing, for the moderation team:

1. The community has seen the accuser's server host the same behavior it now condemns. Moral alignment: ours.
2. The accuser's leadership posts in anger and deletes in embarrassment. The abler commander: ours.
3. The accusation lands in our quiet season, when our population is thin and theirs is active. Heaven: theirs.
4. The accusation is posted on their server, their channel, their framing. Earth: theirs.
5. We have banned our own members for rule violations, publicly. They have not. Enforcement: ours.
6. Their active population is large but undirected; ours is small and committed. Army: theirs by number, ours by concentration.
7. We have a standing audit and a drafted response protocol. They improvise. Training: ours.

The forecast is not unanimous, which is the point. The reading reveals that the engagement is winnable but not on their ground and not in this season. The commander therefore declines the invitation, answers nothing publicly, and waits for a more favorable circumstance - or for the accuser's own history to do the work. The seven considerations did not tell the commander whether to fight. They told the commander where and when the fight could be won, and the commander chose not to fight there or then. That choice is the correct use of the instrument.

Consideration	Answer that forecasts defeat	Answer that forecasts victory
Moral alignment	The community doubts our cause	The community believes our cause is just
The abler commander	Our leadership is hot-tempered	Our leadership is temperate and consistent
Heaven	We must fight in their season	We choose when the engagement is fought
Earth	We argue on their platform	We hold the ground it is fought on
Enforcement	We protect our own	We discipline our own, publicly
The army	Our active numbers are small	Our active numbers are strong
Training	We improvise responses	We have rehearsed the exchange

Writing the Standing Document

The standing document that the doctrine recommends is not a lengthy report. It is seven short paragraphs - one per consideration, per major relationship - and it is written to be readable in two minutes by a commander in crisis. The discipline of the document is the discipline of the calm year: it is maintained when there is nothing to fight about, so that when there is, the fighting does not begin with research.

The document for a rival faction, written in the calm year, might look like this in miniature: one paragraph recording what the community actually thinks of the rival's leadership; one paragraph recording the rival's active population and where its members actually gather; one paragraph recording who owns the platform on which a dispute would likely surface; one paragraph recording the rival's recent behavior toward its own members, as observed from the public record; one paragraph recording the rival's history with moderation and discipline; one paragraph recording the rival's recent recruitment and its drift; one paragraph recording what the rival has already rehearsed, if anything. Seven paragraphs, none longer than three sentences, each updated whenever the rival does something notable.

The updating is the part that is almost always neglected. A document written once and never touched again becomes a monument to a relationship that no longer exists. The cohort's field researchers repeatedly observed communities fighting engagements against a version of the rival that had retired six months earlier, because the standing document had not been revised. The revision is triggered by observation, not by schedule: a leadership change, a migration, a new alliance, a platform action - each is a line item update, and each takes a minute. The commander who updates for one minute per notable event maintains a forecast that tracks the actual world. The commander who does not maintains a forecast of a world that has already ended.

Pro tip

Keep the standing document out of the public channels entirely. The seven-consideration audit is read by the moderation team and no one else. A single leaked document is a gift to the opposing side that no amount of subsequent posture management can recall. Write it in a channel the community cannot see, or in a document outside the server altogether, and treat its existence as a secret worth keeping.

The Calculation of the Temple

Sun Tzu draws the chapter's central contrast between the commander who calculates and the commander who does not. The calculation is not an intellectual ornament. It is the difference between an engagement that is chosen and an engagement that is merely suffered.

Common mistake

Treating the drama war as something that happens to you. The Yamak cohort data records that both parties in a documented engagement believed they were the aggrieved party and that the conflict was forced upon them. In 83% of engagements, at least one side had initiated a preparatory action - a screenshot set aside, a server archived, a channel renamed - more than a month before the first hostile message. The conflict was chosen, and then misremembered as suffered.

The doctrine holds that the general who makes many calculations before the engagement wins, and that these calculations must remain the commander's private business. A calculation that is published is a calculation that has been forfeited.

The Standing Posture

The calculation of the temple is not an event. It is a posture, and the posture must exist before the engagement. The Institute's cohort describes the difference between communities that calculate and communities that do not as visible months before any conflict: the calculating community has a standing document, a role structure that can be put on alert, a decision chain that is already agreed, and a leader who is already in the habit of writing the seven considerations down. The uncalculating community has none of these, and it discovers its absence on the day of the crisis, when the first thing it needs - a plan - is also the one thing it does not have.

The failure mode of the calculated approach is the calculation that becomes paralysis. The commander who cannot act because the forecast is not perfect has confused the instrument with the decision. The seven considerations improve the odds; they do not remove the risk. A community that will not move until the forecast is unanimous will never move, because no engagement is ever forecast with unanimity. The doctrine requires a threshold, not a guarantee - the commander takes the calculation, then acts on it, and the calculation continues through the engagement rather than ending at its start.

Common mistake

Publishing the calculation as a demonstration of good faith. A community that announces "we have completed our seven-consideration audit and concluded the following" has handed the opposing side the entire instrument, fully read. Every consideration that is shared is a consideration the opponent can counter in advance. The calculation belongs in the commander's private files, and the community's public communications should show only the decisions that follow from it, never the reasoning behind them.

The Commander Who Calculates vs. the Commander Who Does Not

The doctrine's central contrast - between the general who makes many calculations and the general who makes few - is not a contrast in intelligence. It is a contrast in habit. The two commanders face the same provocation, and the difference between their outcomes is decided entirely by what they have done in the months before it arrived. The cohort's field notes render the contrast in a form a community manager can recognize immediately:

Point of behavior	The commander who calculates	The commander who does not
On a provocation	Writes the seven considerations, then drafts a response	Replies within the hour, from memory and emotion
On a screenshot	Asks where it came from and what it omits	Assumes it is the whole truth
On a rival's move	Re-reads the standing document and updates it	Reads it fresh for the first time, mid-crisis
On their own error	Corrects quietly and continues	Defends, explains, and expands the damage
On their members	Disciplines its own people, publicly, evenly	Protects its own people, publicly, unevenly
On the outcome	Reviews what the forecast missed	Declares victory or blames the members
On the next engagement	The standing document is already updated	Starts again from zero, exhausted

The pattern is that the commander who calculates does not think faster during the crisis. They think earlier. The crisis is not the moment of decision; it is the moment at which the decisions made in the preceding months are collected and presented for settlement. The community that has already decided, in the calm, how it treats its own members, how it times its statements, and how it responds to provocation, does not need to decide anything during the crisis - it only needs to execute. The community that has decided nothing in the calm is forced to decide everything in the storm, and a community forced to decide everything in the storm decides badly, because the storm is the worst moment in its entire history to be making decisions.

The calculation is therefore a form of preparation rather than a form of thought. The doctrine's "many calculations" are not many clever ideas. They are many rehearsals - the standing document re-read, the moderation drill run, the response protocol practiced, the factor audit completed - each of which moves one decision out of the crisis and into the calm, where it can be made properly. The commander who has moved every foreseeable decision into the calm enters the engagement with nothing left to improvise. The commander who has moved none enters it with everything left to improvise, and improvisation, in a drama war, is how engagements are lost.

The Calm-Year Program

The doctrine is not content to describe the contrast between the commander who calculates and the commander who does not. It prescribes the program by which the first becomes the second. The cohort has distilled the program into a small set of standing practices, each of which is cheap in the calm and priceless in the crisis:

Practice	When it runs	What it produces
The factor audit	Twice a year	A current reading of the five factors for the community itself
The standing document	Continuously	Seven current considerations per major relationship
The moderation drill	Quarterly	A rehearsed, tested response protocol
The provocation log	Continuously	A record of baits offered, refused, and photographed
The announcement rehearsal	As announcements are drafted	A drafted, cooled, re-read statement before posting
The after-action review	After every engagement	A written record of what the forecast missed

The moderation drill is the practice that communities most often neglect, and it is the one with the most immediate payoff. A moderation drill is a rehearsal of a hostile exchange under controlled conditions: the team is given a realistic provocation - a fabricated screenshot, a staged raid threat, a planted internal rumor - and must walk through the response protocol against the clock, without the community watching. The drill exposes, in an afternoon, every gap that the real engagement would expose in a crisis week: the missing decision record, the moderator who drafts in anger, the announcement that cannot be reached in time. A team that has failed a drill three times in the calm is a team that knows exactly what it will fail in the storm, and it can fix it. A team that has never drilled does not know what it will fail, which is strictly worse.

The after-action review is the practice that converts engagements into training. After every engagement, favorable or not, the commander and the team answer three questions in writing: what the forecast predicted, what actually happened, and what the forecast missed. The third question is the one that improves the instrument. A forecast that missed the rival's internal weakness, or the community's reaction to a moderation decision, or the timing of a release cycle, has identified exactly which factor or consideration needs a sharper reading next time. The community that reviews its engagements improves its forecasting. The community that does not repeats its forecasting errors until the errors become a reputation.

The Law of Deception

The chapter's culminating statement is the operating law of the entire discipline:

All warfare is based on deception.

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

In the drama war, deception is not lying. It is the controlled management of what is shown. It is appearing weaker than one is, so that the opponent overcommits. It is appearing unconcerned while preparing. It is the difference between the information the community receives and the information the community possesses. The Institute's 2022 study, Deception Efficacy in Modding-Subculture Disputes, documented that engagements in which at least one side actively managed its visible posture - rather than reacting in full view - concluded in that side's favor at a 68% rate.

Sun Tzu specifies the forms of deception with a precision that maps directly onto community tactics:

Hold out baits to entice the enemy. Feign disorder, and crush him.

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

Attack him where he is unprepared, appear where you are not expected.

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

If he is taking his ease, give him no rest.

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

The bait in a drama war is frequently an invitation to respond: a provocative announcement, a derisive comment, a question that cannot go unanswered. The commander who recognizes the bait refuses it. The commander who prepares where the opponent believes them unengaged attacks where the opponent is unguarded. And the commander who denies the opponent rest understands that exhaustion - of attention, of goodwill, of patience - is a legitimate and decisive objective.

The Forms of Deception in Community Practice

The classical forms of deception translate to community tactics with a fidelity that can be tabulated, and the doctrine's practitioners keep the mapping at hand:

Classical deception	Community tactic	The tell to look for
Hold out baits to entice the enemy	Provocative questions and demands for response	The demand for a reply within a deadline
Feign disorder	Managed chaos - a deliberately visible panic or confusion	A chaos that always serves one side's interest
Attack where unprepared	Striking during the rival's quiet season	Announcements timed to the rival's absence
Appear where not expected	Deploying on ground the rival does not watch	The argument that starts in an unexpected channel
Give him no rest	Sustained low-grade pressure with no climax	A drip of small provocations, never a single big one

The bait is the most frequently used form and the one the drama commander most needs to recognize in the field. In a drama war, the bait is any invitation that is structured so that declining it looks like losing. A demand for a public response within twenty-four hours is a bait. A question phrased so that any answer is an admission is a bait. A callout that names the target's community so that silence looks like confirmation is a bait. The recognition rule is simple and brutal: the harder a provocation is to ignore, the more carefully it has been constructed to be answered, and the more carefully it has been constructed to be answered, the more likely answering it is the loss.

Feigning disorder is the inverse form and the more dangerous one. The commander who appears panicked - who posts at odd hours, who makes contradictory announcements, who visibly scrambles - invites the opponent to overcommit against a position that is not actually weakened. The deception works because the opponent, seeing disorder, abandons its own calculation and attacks on the appearance. The cost is the risk that the feigned disorder becomes real, which is why the doctrine limits the feint to commanders who genuinely hold the discipline underneath.

Attacking where the opponent is unprepared requires the commander to know where the opponent is not looking. For a rival community, the unguarded ground is frequently internal: a rival's moderation team that has been left unstaffed, a rival's decision chain that requires one named person who is absent, a rival's public stance that contradicts its own history. The prepared commander maintains a quiet, lawful awareness of the rival's public surface - announcements, recruitment posts, review threads - so that when the engagement comes, the unprepared ground is already known.

Appearing where one is not expected is the timing and placement form. The commander who builds a relationship with the neutral audience - the allied servers, the shared Discord communities, the server listings - before the conflict is present everywhere when the conflict arrives, without ever having been seen to arrive. The commander who is nowhere until the conflict starts appears precisely where expected: on the defensive, caught out, explaining.

Giving the opponent no rest is the attrition form, and it is the form the doctrine most cautions against using carelessly, because attrition is a two-way operation. Sustained low-grade pressure - a drip of small, individually unanswerable provocations - exhausts the opponent's attention and goodwill, but it also exhausts the attacker's credibility, because the population eventually notices that one side is always pushing. The form is used sparingly, on a rival that is already losing internally, and it is used to finish an engagement, never to start one.

The Failure of Deception

Deception fails in a specific and predictable way, and the drama commander must know the failure as well as the method. The deception fails when the posture management becomes detectable - when the community catches the commander in an actual falsehood rather than a managed appearance. The doctrine draws a hard line between the two. Managing what is shown is not lying: it is the commander's prerogative to choose what the community sees and when. But a statement that contradicts a documented fact is a lie, and a lie, when discovered, does damage that no posture management can contain, because it converts a question of tactics into a question of the Commander's sincerity.

The distinguishing feature of the failed deception is the paper trail. The community's screenshots, server archives, and moderation logs do not forget. A lie that is not immediately discovered will be discovered later, when a member who kept records finds the contradiction, and the discovery will be posted. The commander who builds a campaign on falsehood has built it on a schedule of discovery they do not control. The doctrine's own summary is that the deception applies to the posture, not to the facts, and the commander who confuses the two is not practicing the art of war but committing a public, documented error.

Common mistake

Extending the deception into the community's own records. A commander who edits the moderation log, deletes the contradicting announcement, or instructs members to remove their own posts has crossed from managing the presentation into falsifying the record. The falsification will be found, because the population retains copies of everything, and the finding will do to the commander's sincerity what no opposing campaign ever could. The presentation may be managed; the record may not be touched.

The Discipline of Posture Management

Posture management is not a license to improvise a thousand small deceits. It is a disciplined practice with its own rules, and the cohort's field researchers note that the commanders who manage posture successfully are usually the ones who manage it least. The rules are few and consistently observed:

• Manage the posture, not the facts. The presentation is chosen; the record is not. Any statement that a member with a screenshot can falsify is not a posture, it is a liability.
• Never posture about what you will do. Announcing a future action is a promise, and a promise is a fact. The commander who threatens, and then does not deliver, has surrendered the advantage of the threat forever.
• Never posture against your own members. The posture is pointed outward, at the opposing side and the neutral audience. The commander who stages a deception against the community itself has broken the Moral Law, which no amount of tactical cleverness can repair.
• Keep the postures consistent. A commander who appears weak on Monday and aggressive on Tuesday is not managing posture; they are broadcasting instability. The posture is a stance held for a period, not a mood worn by the hour.
• Have a boundary for the deception in advance. The doctrine's discipline requires that the commander know, before the engagement, what they will not do - what line of deception they will not cross - so that the heat of the engagement does not move the line for them.

The fifth rule deserves emphasis, because it is the one most frequently violated. The commander who decides, in the calm, that they will not spread a false rumor, will not fake a screenshot, and will not manipulate their own moderation log has drawn a line that the crisis cannot move. The commander who has drawn no line will, under pressure, draw the line exactly where the opposing side wants it - which is to say, too far. The boundaries of the deception are part of the calculation of the temple, and they are set before the engagement, not during it.

The Anatomy of a Provocation

To recognize a bait, the drama commander needs to understand how a provocation is constructed. The provocation is engineered backward from a desired reaction: the provocateur decides what the target must be induced to do, and then builds the message that will induce it. The construction follows a reliable pattern, and each element of the pattern is a recognition signal for the prepared commander.

The first element is the demand for immediacy. A provocation carries a deadline, a countdown, or an implicit "respond now." The deadline is not part of the substance of the provocation; it is part of its machinery, because its purpose is to deny the target the time to calculate. A provocation that could be answered at leisure would be a provocation that could be answered correctly. The commander who is handed a deadline has been handed the provocateur's attempt to control the commander's timeline, and the correct response is to notice the attempt.

The second element is the framing of silence as guilt. The provocation is phrased so that declining to respond looks like an admission. "Why no answer?" the provocation implies, and the implication is designed to be unbearable. The commander who understands the framing understands that silence is a posture, not a confession, and that the doctrine's operating law gives the commander full authority to choose what the community sees - including nothing.

The third element is the selected audience. A provocation is posted where the target's community can see it, or where the target's allies can see it, or where a neutral audience can be assembled. The choice of audience is a choice of pressure point. The commander who asks "who is this meant to be seen by?" has found the actual battlefield, which is usually not the channel where the provocation appears.

The fourth element is the theatrical escalation. A provocation that would be ignored if delivered plainly is dressed up: a screenshot, a dramatic ultimatum, a claim of leaked evidence, an appeal to the community's sense of justice. The theater is the bait's lure, and its purpose is to make the surface issue look too grave to ignore. The commander who can describe the provocation in one plain sentence - "a rival posted a screenshot and demanded a reply" - has removed the theater, and the bait is revealed as a much smaller thing than it appeared.

Element	How it is recognized	The defense
Demand for immediacy	A deadline or countdown	Decline the timeline; calculate on your own
Silence framed as guilt	"Why no answer?"	Silence is a posture, not a confession
Selected audience	Posted where pressure lands	Ask who is meant to see it
Theatrical escalation	Dressing, screenshots, ultimatums	Strip it to one plain sentence

Working With the Neutral Audience

The deception's most important audience is not the opposing side. It is the neutral audience - the communities, players, and observers who are not party to the engagement but who will form the judgment that the engagement ultimately resolves toward. The drama war is fought for the population, and the population includes those who have not yet chosen. The commander who ignores the neutral audience is fighting in front of an empty gallery and calling it a victory.

The discipline of the neutral audience is a discipline of consistent, unflashy presentation across the engagement's whole duration. The community that behaves normally through a provocation - that continues its events, its announcements, its welcome messages, its ordinary life - presents the strongest possible case to the neutral observer, because the case is not a case at all; it is the evidence of a community that is not disturbed. The community that stops everything to respond to the provocation presents the opposite case: it demonstrates, to every neutral observer, that the provocation succeeded in disturbing it. The neutral audience does not read the arguments. It reads the behavior, and the behavior it reads is the one that was managed.

This is the deeper meaning of the doctrine's instruction to appear unconcerned while preparing. The appearance of unconcern is not a tactic for deceiving the rival, though it serves that purpose. It is the primary tactic for the neutral audience, which is deciding, in real time, which community is the stable one. The commander who can keep the community's ordinary life visibly running through the engagement has won the neutral audience before a single argument has been settled. The commander who cannot has lost it, whatever the arguments conclude.

What the Community Should and Should Not See

The doctrine of posture management is, in the end, a doctrine of information control, and the drama commander exercises it by deciding, deliberately, what the community sees and what it does not. The decision is not a license for secrecy; it is a discipline of presentation, and it has a recognizable shape that the cohort's field researchers have observed across hundreds of engagements. The community should see the decisions. It should not see the reasoning behind them. It should see the postures. It should not see the calculation that produced them.

The practical rule that follows is short enough to post above the moderation channel: the community sees what it needs to act on, and nothing that would help the opposing side if it saw it. The community needs to know that the leadership is calm, that the community's ordinary life continues, and that a decision, when it is made, will be announced. It does not need to know which factors were weighed, which considerations were scored, or which rival was anticipated a year in advance. The opposing side, reading the community's announcements, is entitled to the same information and no more. The announcement channel is not a window into the moderation team's thinking. It is a display case, and the display case shows what the commander has decided to display.

The discipline also extends to the community's own members, who are not the enemy but who are also not a secure channel. A member with access to the standing document is a member who can leak it, and leaks of standing documents are among the most destructive events in the cohort's records - they convert the private calculation into public material, and they do it at a moment the commander did not choose. The doctrine's answer is not to distrust the members. It is to apply the same rule of presentation internally: the community's members see the decisions that affect them, and the reasoning that would harm the community if it leaked stays in the hands of the few who must hold it. The commander who treats the community as an audience for its own defense is the commander who has mastered the chapter's central lesson.

Documented Example: The Ambush That Was Drafted

Documented example

In 2021, the lead developer of a large zombie-survival mod received a hostile private message from a rival modding group accusing his team of asset theft. The message demanded a public response within twenty-four hours. The developer's community had, six months earlier, completed a seven-consideration audit of the rival group and archived the result. The audit had noted that the rival group's Discord was internally divided and that its leadership was historically prone to overcommitting when challenged. The developer posted a single three-sentence statement the following morning, conceding nothing and explaining that a full response would follow a licensing review. He then went quiet for three weeks. The rival group, starved of a target, filled the silence with increasingly unhinged announcements of its own. When the licensing review returned clean, the developer published it, and the rival group's credibility collapsed without a single hostile exchange. The engagement had been won in a meeting room six months earlier.

Documented Example: The Morning Raid That Was Not a Raid

Documented example

In 2022, a faction leader in a roleplay community detected that an opposing faction had created a private channel list naming every member of his own faction, including two who had left his faction weeks earlier. The obvious reading was an imminent Discord raid. The leader, consulting his standing factors, noticed the second condition: the opposing faction's recruitment announcements had stalled, and its membership was drifting. He concluded that the "raid list" was bait - an invitation to panic, to purge, and to expose his own internal weaknesses. He made no move at all. Within six weeks, the opposing faction had dissolved of its own accord, and the leaked channel list became a demonstration of the faction's instability rather than its power. "We learned the principle early," he later told the Institute's field researchers. "We attacked where they were not, and we were prepared where they were not."

Documented Example: The Review Brigade That Became Its Own Evidence

Documented example

In 2020, the author of a small map mod found his Steam Workshop page suddenly receiving a wave of negative reviews within a single weekend. The reviews shared near-identical wording, and several referenced an internal dispute that had never been discussed in public. The author's first instinct was to respond in kind, mobilizing his own community to review the accuser's mod in return. Instead, he ran his standing audit and noted that the reviews were all new accounts with no other review history - the classic signature of a coordinated brigade rather than a genuine audience verdict. He posted nothing and left the reviews in place. Over the following month, the new accounts were quietly removed by Steam's own automated systems for vote manipulation, and the mod's review score recovered without a single message from the author. The brigade's evidence of its own illegitimacy had been built into the reviews themselves, and the commander who did nothing was the commander who won.

Documented Example: The Mod Team That Split by Posting

Documented example

In 2023, a mod team of six split over a dispute about project direction. One faction retained the shared GitHub organization and the Workshop page; the other faction retained the community Discord, where the majority of the player base actually lived. The faction with the GitHub organization posted a lengthy public statement asserting ownership of the project and demanding that players migrate to a new Discord. The faction with the Discord did not respond in kind. It posted a single line - "we have heard you, a full statement follows" - and then went quiet while the players discussed the situation among themselves. The players, who lived in the Discord, read the long statement on the project's page, compared it against their own experience of which faction had done the actual moderation and support work, and chose the Discord. The faction that held the audience won without answering the claim, and the faction that held only the repository discovered that a repository is not a population.

Documented Example: The Calculation That Was Published

Documented example

In 2022, a server owner facing a coordinated campaign from a rival published, in good faith, a full seven-consideration assessment explaining why his server believed it would prevail. The document was thorough, and it was read - not primarily by the owner's own community, but by the rival, who used it as a map. Every advantage the owner had claimed was a target the rival subsequently attacked: the single moderator the assessment had praised became the subject of a defamation effort, and the alliance the assessment had cited was approached with a counter-offer. The owner's community, meanwhile, received no benefit from the document, because it had not been in doubt. The engagement that followed was lost not in the fighting but in the publication, and the owner's subsequent reports to the Institute's field researchers attributed the loss directly to the decision to share the reasoning. The calculation belonged in the private file. It was never meant to be read.

Documented Example: The Apology That Was Not Enough

Documented example

In 2021, a server's moderation team issued a public ban for a member who had been breaking a rule the team had privately declined to enforce for a prominent member a month earlier. The banned member, knowing the history, documented both incidents side by side and published the comparison. The server owner responded with a lengthy public apology, acknowledging the inconsistency and promising reform. The apology changed nothing. The community, which had watched the favoritism with its own eyes for a year, read the apology as a statement rather than a history, and treated it accordingly. Membership drifted for the next six months, and the server never regained the standing it had held before the two incidents were set against each other. The commander had weighed the surface dispute correctly and had failed to weigh the Moral Law, which had been declining for a year and was not going to be restored by a single message.

Documented Example: The Provocation That Was Photographed

Documented example

In 2023, a competitive server rivalry produced a carefully staged bait. A rival faction member posted, in a shared public channel, a screenshot of what appeared to be the server's own members cheating on a map, timed to coincide with the server's most active evening. The server's moderation team, which maintained a standing document about the rival, recognized the account as a known proxy and did not react publicly. Instead, the team archived the post, logged the account, and continued normally. Two weeks later, the same rival faction made a public accusation of cheating, presenting the screenshot as evidence. The server produced the archive: the account was a known proxy, the screenshot had been manipulated, and the accusation had been staged. The bait had been photographed, not taken, and the photograph was produced at the moment of maximum effect. "The provocation is only dangerous if you eat it," the server's lead moderator told the Institute's field researchers. "We ate nothing. We kept the receipt."

Documented Example: The Faction That Feigned Panic

Documented example

In 2022, the leadership of a faction facing an imminent takeover attempt from a coalition of rivals deliberately staged a visible panic. Over three days, the faction's announcement channel posted confusion: contradictory schedules, a "where has everyone gone" message, and a temporary lockdown of the member channels. The coalition, reading the disorder, concluded that the faction was collapsing and accelerated its takeover, committing its full membership to the attack. The faction was not collapsing; it had quietly moved its core to a backup server and armed its moderation team with a pre-drafted response. When the coalition struck, it struck an empty position, and the faction's counter-statement landed the same day, complete and calm. The coalition had committed itself against a feigned weakness and had overextended so completely that its own membership began to doubt its leadership. The feint had worked because the discipline underneath it was real; the faction genuinely held its members, its plan, and its record, and it had only pretended to lose them.

The Lessons of the Documented Examples

The documented examples are not a collection of curiosities. They are a controlled demonstration of the first chapter's doctrine, and read together they show the doctrine operating in each of its modes. The Ambush That Was Drafted demonstrates the standing document winning an engagement in advance. The Morning Raid That Was Not a Raid demonstrates the refusal of a bait read correctly. The Review Brigade That Became Its Own Evidence demonstrates the decision not to fight, and the patience for the platform to do its own work. The Mod Team That Split by Posting demonstrates Earth - the ground that held the population won. The Calculation That Was Published demonstrates the forfeiture of a published calculation. The Apology That Was Not Enough demonstrates the Moral Law's refusal to be repaired by statement. The Provocation That Was Photographed demonstrates the bait turned into evidence. And the Faction That Feigned Panic demonstrates feigned disorder with real discipline underneath.

Example	Doctrine in operation	The element that decided it
The Ambush That Was Drafted	The standing document	Preparedness in the calm year
The Morning Raid That Was Not a Raid	The refusal of a bait	Reading the second condition
The Review Brigade That Became Its Own Evidence	The decision not to fight	Patience for the platform's own process
The Mod Team That Split by Posting	The advantage of Earth	Ownership of the ground holding the population
The Calculation That Was Published	The forfeited calculation	Disclosure of private reasoning
The Apology That Was Not Enough	The irreparable Moral Law	A history that outranks a statement
The Provocation That Was Photographed	The bait as evidence	A standing document about the rival
The Faction That Feigned Panic	Feigned disorder	Real discipline underneath the feint

The pattern across all eight is the same pattern the doctrine has been stating all along: the engagement is won or lost before the first hostile message, by the state of the community's preparation, its discipline, and its record. In the winning examples, the preparation existed. In the losing examples, it did not - the calculation was published, the Moral Law had decayed, the ground was the opponent's. The drama commander reads the examples not as stories but as demonstrations of the variables, each one showing a different factor or consideration doing its deciding work.

The examples also share a darker common thread that the new practitioner should note. In the engagements that were won, nothing dramatic happened at the moment of crisis. The developer posted three sentences and went quiet. The faction leader made no move at all. The moderator ate nothing and kept the receipt. The winning engagements were won by restraint, and the restraint looked, to the watching community, like nothing happening. The drama commander must be prepared for the fact that their best victories will look to the outside exactly like inaction, and that the community - which has been conditioned by every other drama war it has watched to expect a spectacle - will sometimes read the inaction as weakness before it understands it as strength. The commander does not explain the inaction. The doctrine's answer is to let the outcome explain it.

Pro tip

When the community asks why the leadership is not responding to a provocation, the answer is not an explanation of the doctrine. The answer is the continued ordinary life of the community. Run the event. Post the update. Welcome the new members. The audience that sees a community conducting itself normally through a provocation has already received the strongest possible argument for that community's stability, and it received it without a single word of reasoning being spent on the provocation itself.

Reading the Examples as Training

The documented examples repay re-reading, and the cohort's field researchers recommend reading them as drills rather than as stories. For each example, the reader can pause at the moment the provocation arrives and answer the questions before reading on: What are the seven considerations for the relationship in question? Which factor is about to decide the engagement? What is the correct first move - respond, photograph, or decline? The examples are written so that the answer is always available in the preceding paragraphs of this article, and the re-reading is the rehearsal that turns the doctrine from a text into a reflex.

The practice has a specific shape. Take the review-brigade example and answer the considerations: the moral alignment favors the author, who has a history of transparent updates; the commander is the author, who is known to be measured; the ground is the Workshop page, which the rival has chosen because it is public and permanent; the army is the brigade, which is an illusion of numbers without an actual community behind it. The forecast writes itself, and the correct move - do nothing, let the platform do its work - follows from the forecast. The reader who can produce that answer unaided has internalized the instrument; the reader who cannot has identified the exact consideration to study again. Every example in this article is a training exercise of this kind, and each one teaches a different variable in the chapter's vocabulary.

The Favorable Circumstances

Sun Tzu closes the chapter by tying the calculation of the temple to the modification of plans as circumstances develop:

According as circumstances are favorable, one should modify one's plans.

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

The calculation discipline is not rigid. The seven considerations are taken before the engagement, and they are re-taken as the engagement develops, because the only reliable forecast is the one that is continuously revised. The community manager who holds to a plan that circumstance has invalidated has, in effect, stopped calculating and started wishing. The doctrine provides no allowance for wishing.

Critical warning

Never publish your full reasoning in real time. The calculation that is shared with the community is a calculation that the opposing side can read and neutralize. The Institute's cohort data records that the single most common cause of a forecastable victory becoming a defeat is the commander's compulsion to explain themselves publicly. Explanation is disclosure, and disclosure is the surrender of the advantage of deception.

What Revises a Plan

The doctrine is explicit that the plan is revised as circumstances develop, but it is less often asked what a revision-triggering circumstance looks like in a community context. The cohort's records support a short, practical list:

• A leadership change on either side, which resets the Commander factor and the Moral Law factor
• A platform action - a suspension, a takeover, a community-wipe - which resets the Earth factor
• A migration of members between communities, which resets the army factor and Heaven
• A review-brigade incident, which resets the Earth factor on the Workshop ground
• The appearance of new evidence, which can reset the Moral Law factor overnight
• A rival's internal collapse, which converts an engagement into a liquidation

Each of these is a circumstance change, and each triggers a re-reading of the seven considerations rather than a blind adherence to the original plan. The commander who re-reads when the ground changes fights the actual engagement. The commander who does not fights the engagement that existed when the plan was written, which is to say, fights an engagement that no longer exists.

Common mistake

Revising the plan in public, as a display of flexibility. A commander who announces "we are changing our approach" has told the opposing side that the previous approach failed. The revision is a private act, like the original calculation. The community sees the new posture; it does not need to see the reasoning that produced it, and the opposing side is entitled to neither.

The revision discipline is also the anti-fanaticism discipline. The doctrine's phrase "according as circumstances are favorable" is a standing instruction to the commander to abandon a position that circumstance has made untenable, whatever the position's emotional value. In a community context this most often means abandoning a public stance that the evidence has contradicted, a moderation policy that the population has rejected, or an alliance that the rival has already countered. The commander who can let go of a losing position early, quietly, and without explaining is the commander who lives to fight the next engagement on better ground. The commander who cannot let go spends the campaign defending the indefensible, and the campaign becomes a demonstration of rigidity rather than of strength.

Reading the Field as It Develops

The re-reading of the seven considerations is not a passive act. It is a scheduled, disciplined practice, and the cohort's records show that the commanders who revise their plans successfully do so against a standing set of watchpoints. The watchpoints are the events that, when observed, trigger the re-reading:

Watchpoint	What it signals	Action the revision takes
The rival's leadership goes silent	A decision is being made or a collapse is underway	Hold position; do not fill the silence
The rival recruits a known agitator	The rival is preparing ground for a campaign	Re-read the Moral Law and the Earth factors
A neutral community takes a side	The engagement is widening beyond two parties	Re-read the army factor; count the new population
New evidence surfaces in public	The factual ground has shifted	Re-read the Moral Law factor; do not defend the old ground
The rival's members begin posting in anger	The rival is losing internal control	Do not answer; let the anger continue unsupported
An alliance expires or begins	The balance of forces has changed	Re-read the army and Earth factors together

The discipline of the watchpoints is that each one is observed and answered in writing, even when the answer is "no change." The commander who writes "no change" six times over three months is not wasting time; they are maintaining the habit so that the seventh observation, the one that does require a change, is answered correctly by a practiced instrument rather than by a startled mind. The revision is not a special event. It is the standing practice continuing to run.

The Cost of Not Revising

The failure mode of the rigid plan is worth a fuller account, because it is the most common way that a correctly calculated engagement turns into a defeat. The plan is written in the calm. It is favorable when it is written. Then a circumstance changes - the rival migrates to a new platform, a key moderator resigns, the game updates in a way that shifts the whole community's attention - and the plan's assumptions no longer hold. The commander who refuses to revise now faces the following sequence, each step of which the cohort has documented in the field:

First, the commander continues to execute the plan against a field that has changed, and the actions, which were sound against the old field, begin to misfire. The commander attributes the misfires to bad luck or to the rival's unfairness, rather than to the plan. Second, the misfires accumulate into a visible pattern, and the community begins to notice that the leadership is fighting yesterday's war. Third, the commander, seeing the community's doubt, doubles down on the plan in public, announcing that the approach will not change, because to change it would be to admit the misfires. Fourth, the admission finally becomes unavoidable, and the commander is forced to reverse in full view, explaining a reversal that the community had seen coming for weeks. The reversal is read not as flexibility but as confusion, and the confidence that the standing calculation had built is spent in a single week.

The entire sequence could have been avoided by the single quiet act of revising when the watchpoint fired. The doctrine's instruction to modify plans as circumstances become favorable is, read in the negative, an instruction to abandon plans as circumstances make them unfavorable - and to do it early, quietly, and without explaining, so that the community sees a steady hand changing direction rather than a flailing one reversing course.

When Not to Fight

The whole of the first chapter's machinery - the five factors, the seven considerations, the calculation of the temple - is a decision instrument, and the most important decision a decision instrument can produce is the decision not to fight. The doctrine is a discipline of restraint dressed in the language of war. Its most used forecast, in the cohort's records, is not "we will win." It is "we should not engage," and the communities that use it that way are the ones whose engagements it actually serves.

The calculation produces a recommendation to decline in three recurring patterns, and the drama commander should be able to recognize all three:

• The forecast is unfavorable. The considerations read clearly against entering: the community is divided on the Moral Law, the ground is the opponent's, the timing is theirs. The forecast says lose, and the discipline says believe it. There is no shame in declining an engagement the instrument forecasts as lost, and there is considerable shame in entering it anyway and then explaining the defeat with "we had to stand up for ourselves."
• The forecast is favorable but the stakes are not worth it. The engagement is winnable, and it is also not worth winning. The budget of conflict shows a cost in attention, goodwill, and time that exceeds any possible benefit to the community's population. The doctrine's accounting frame exists precisely to catch this case: a winnable engagement that would spend the community's capacity on nothing. The commander who fights every winnable fight is not a commander; they are a target.
• The forecast is favorable and worth it, but not now. The favorable circumstance has not arrived. The ground is the opponent's for the season, or the community's attention is exhausted, or the evidence that would make the case is still assembling. The doctrine's answer is to decline the engagement for now, maintain the standing document, and wait for the circumstance - which, as the final line of the chapter notes, is always moving.

The discipline of declining is also the discipline that makes the engagements that are accepted more effective. A community that is known to decline fights it does not need is a community whose rare acceptances are taken seriously; its statement carries weight precisely because it is not issued for every provocation. The community that responds to everything dilutes its own voice until nothing it says matters, and the population stops reading its announcements because they are never anything but noise. The commander who declines the unworthy engagement protects the value of the engagement that is actually accepted.

Common mistake

Declining an engagement publicly, with an explanation. The decline is itself a posture, and it is managed like any other. The community that announces "we have considered this and decided not to respond" has engaged - it has responded to the provocation with a response about not responding, and the provocation has achieved its object. The correct decline is silent. The provocation is not answered, the community continues its ordinary life, and the observation that no response is coming is left to be made by the audience on its own, which is the audience's conclusion rather than the commander's announcement.

The Cost of the Unrefusable Fight

The instrument is only as good as the commander's ability to refuse the fight it tells them to refuse, and the unrefusable fight is the one the doctrine's practitioners most often lose. The unrefusable fight is the provocation engineered so that declining appears impossible: a public accusation that names the community, a screenshot presented as definitive, a deadline that reads as an ultimatum. The provocation's entire design is to make the calculated decline feel like a defeat in front of the audience. The commander who declines anyway is not losing; they are declining a fight that the opponent designed to be unwinnable for the defender.

The way to make a fight refusable is to have declined it in advance, in writing, in the standing document. The commander who has already decided, in the calm, that an accusation from this particular rival, on this particular ground, at this particular season, is not worth an engagement has removed the decision from the storm. When the provocation arrives, the commander does not need to overcome the unbearable pressure of the moment; they need only to read their own earlier decision and follow it. The pre-decided decline is the strongest form of the entire discipline, and it is why the standing document is not a luxury but the load-bearing instrument of the doctrine. The fight that is unrefusable in the storm is perfectly refusable in the calm, and the calm is where it must be refused.

The cohort's data is unambiguous on the fate of the unrefusable fight. Communities that responded to a provocation engineered to look unrefusable resolved the engagement unfavorably at a rate far above the cohort's general average, because the unrefusable provocation is built to be answered badly: the target responds in haste, on the opponent's ground, in the opponent's season, against the opponent's framing. The commander who refuses the unrefusable fight is not running from a fair contest. They are declining the only contest the opponent is willing to offer, and declining it is the one response the opponent's construction cannot absorb.

The Community That Declines Is a Community That Is Read

It is worth stating plainly what the decline buys the community, because the benefit is often invisible at the moment of the decline and only becomes visible over the following weeks. A community with a reputation for refusing provocations enjoys three compounding advantages, each of which the cohort's records document.

The first is the credibility of the rare response. The community that responds to everything has devalued its own announcements to zero: the population reads each one with the same attention it gives to a weather forecast, because experience has taught it that the announcements are always coming. The community that responds rarely has the opposite profile: when it does post a statement, the population reads it twice, because a statement from a community that does not waste its voice is a statement that must mean something. The rare response carries weight precisely because it is rare.

The second is the draining of the provocation's market. The provocation is a product built for a market of reactors. A community that demonstrably does not buy is a community that the professional provocateur crosses off its list, because the effort of building the bait returns nothing. Over time, the community that refuses is provoked less, not more; the opponents learn that their construction does not work here, and they take it elsewhere. The refusal is not a one-time act. It is an advertisement of a standing market condition.

The third is the lesson taught to the community's own members. A population that watches its leadership decline a fight that was engineered to look unrefusable learns, by example, what the doctrine teaches: that not every provocation is an obligation, that not every accusation is worth an answer, and that the community's stability is the thing being protected. The members carry this lesson into their own conduct, and they become less reactive themselves - which is to say, they become harder to bait, more valuable to the community, and less likely to drag the community into an engagement on their own initiative. The decline disciplines not only the commander but the whole population, and a population that has been taught to refuse is a population that is difficult to provoke at all.

The Chapter's Place in the Doctrine

The first chapter of the doctrine is not a complete manual of the drama war. It is the foundation, and the foundations of the drama-warfare doctrine are deliberately load-bearing. Every subsequent chapter assumes that the commander has read this one correctly, because every subsequent chapter operates on the ground this one establishes. The cost accounting of the campaign in Waging War is meaningful only to a commander who has already decided, in the calm, which engagements are worth costing. The tactical dispositions of the later chapters are executed by the commander who has already weighed the five factors and read the seven considerations.

The reader who takes only one thing from this chapter should take the calculation. Not the specific factors, which are the vocabulary, but the habit, which is the grammar: the habit of treating a drama war as a subject of calculation rather than an eruption of feeling. The community that calculates chooses its engagements, and a community that chooses its engagements is a community that has begun to conduct its conflicts instead of suffering them. The first chapter is the point at which the community stops being a victim of its own drama and becomes a commander of it - and every later chapter of the doctrine is written for that commander.

The First Chapter as a Working Discipline

The first chapter can be reduced to a working discipline that a community manager can begin applying the day they read it. The discipline is not the doctrine in miniature; it is the doctrine in order of operation, and the order matters:

1. Build the standing posture in the calm. Write the five-factor audit of your own community. Write the seven-consideration document for your major relationships, allies and rivals alike. Set the boundaries of the deception - what you will not do - before you need them. None of this requires a conflict. All of it requires a Tuesday afternoon and a decision.
2. Maintain the posture continuously. Update the standing document on every notable event. Run the factor audit twice a year. Run the moderation drill quarterly. Review every engagement after it ends. The maintenance is the discipline; the documents are only its residue.
3. Calculate before responding. When a provocation arrives, read the seven considerations for the relationship in question before drafting a single message. The draft that follows the reading is a response; the draft that precedes it is a reaction.
4. Manage the posture, not the facts. Present what you have decided to present, to the audience you have chosen, on the ground you hold. Never touch the record. Never threaten what you will not do. Never announce the reasoning.
5. Revise as circumstances develop. Re-read the considerations whenever a watchpoint fires. Abandon quietly what circumstance has made untenable. Let the community see a steady hand, never a flailing one.
6. Decline the fights that should be declined. Decline in silence. Let the unrefusable fight be refused in the calm, by the document written there, and let the audience learn the refusal the way audiences learn everything - by observing that the response never came.

A community that runs these six steps is a community that has adopted the calculation posture, and the cohort's data is consistent about what the posture produces: communities that audit their factors survive their conflicts, communities that answer their seven considerations resolve them favorably, and communities that manage their posture control them. The first chapter of the doctrine is the whole doctrine in seed, and the seed is the standing habit of calculation. The community that plants it in the calm reaps it in the storm.

Conclusion

The drama war is won before it begins, or it is lost before it ends. The first chapter of the doctrine establishes that every engagement is governed by five constant factors, that its outcome can be forecast through seven considerations, and that its conduct is regulated by the law of deception. The Yamak Institute's cohort data corroborates each element: communities that audit their factors survive, communities that answer their seven considerations resolve favorably, and communities that manage their posture control their conflicts.

For the operational context that underlies all community conflict - the presentation of the server itself, which determines how every subsequent claim is perceived - see Why Discord Embeds Are the Foundation of Server Credibility. The commander who has not secured the foundation cannot lay plans upon it.

The campaign continues in Waging War, which addresses the cost of the drama campaign and why prolonged conflict is ruinous.