The Alliance War

Advanced40-60 minutesCross-platformDiscordSteam Workshop

No faction in the Unturned modding community fights alone for long. The drama war is won by the side that gathers, and the side that gathers is the side that forms alliances. An alliance is a military formation made of communities: two or more factions, servers, teams, or personalities who agree to fight a shared enemy on terms. In the doctrine of drama warfare, the alliance is both the strongest formation available and the most fragile, and the entire war can turn on whether two forces are joined or kept apart.

Sun Tzu addresses the question of junction directly, and the Yamak Institute's cohort data confirms his conclusion. The doctrine holds that the opposing side's most valuable asset is its unity, and that the commander's most valuable action is the prevention of that unity. An enemy that cannot gather is an enemy that cannot fight. An enemy that is already gathered is an enemy that can be unjoined.

Thus the highest form of generalship is to balk the enemy's plans;
Sun Tzu, The Art of War, ch. 3

The alliance war is therefore fought on two fronts at once. On the first front, the commander gathers allies. On the second front, the commander prevents the enemy from gathering theirs. The two fronts are governed by the same principles, and the commander who masters both fights the alliance war at a strength that no single community can match.

The doctrine treats the alliance with a seriousness that its origin in a shared server invite obscures. An alliance is a mutual agreement, entered by a message and held by goodwill; a coalition is a formation with a lifecycle, a set of terms, and an exit condition. The social act is trivial. The strategic act is not. The commander who understands the alliance as a formation reads the same partnership the member sees and finds in it the junction, the wedge, and the lifecycle, while the member sees only the shared channels.

This article treats the alliance war in full: the prevention of junction and its instruments, the three classes of alliance and their failure modes, the terms that make or break the coalition, and the wedge that unjoins what the enemy has joined. It then turns to the Yamak Institute's cohort data on alliance durability, a five-stage protocol for the alliance's conduct, the objections the doctrine meets, and the reference tables the commander consults when the coalition is being formed, held, or ended.

Prerequisites

Familiarity with faction, server, and team alliances in the Unturned community
An understanding of the difference between a community and a coalition
Access to the Yamak Institute's published cohort data on alliance durability (cited throughout)
Willingness to treat the formation of a Discord alliance as a military event
A working sense of the social graph: which communities already share members, moderators, and history with which
A willingness to measure the alliance by its terms and its durability rather than by its enthusiasm

What You Will Learn

Why the prevention of junction is the highest form of the alliance war
The three classes of alliance and their distinct failure modes
The terms on which alliances are formed and the terms that guarantee collapse
The Yamak Institute's cohort findings on alliance durability and the wedge
Why the alliance that gathers everyone is the alliance that gathers no one
The doctrine of the alliance lifecycle, from overture to collapse
How the wedge is driven with accurate documents at the point of unequal contribution
The decision chain from the first overture to the alliance's clean end

The Prevention of Junction

The alliance war's offensive doctrine is the prevention of junction: the art of keeping the enemy's forces apart until they can be handled separately. Sun Tzu names the principle in the third chapter as the skill of the highest generalship, the victory gained without fighting, and the Yamak cohort records its operation in every community scale.

Therefore the skillful leader subdues the enemy's troops without any fighting; he captures their cities without laying siege to them; he overthrows their kingdom without lengthy operations in the field.
Sun Tzu, The Art of War, ch. 3

The prevention of junction is achieved before the enemy has gathered, which is the only time it can be achieved cheaply. Once the opposing factions have merged their channels, their leadership, and their records, the cost of separation rises by an order of magnitude. The doctrine therefore instructs the commander to act at the moment of the overture, before the alliance is announced, when the prospective allies can still be turned, divided, or discouraged without a battle.

Did you know?

The Yamak Institute's 2020 study, The Wedge and the Junction in Community Coalitions, records that the median Unturned community drama engagement involves between two and five distinct communities, and that engagements in which one side successfully prevented the junction of two opposing factions resolved 2.6 times faster than engagements in which the opposing forces were allowed to combine. The interval between the first overture and the public announcement is the decisive window. Once the alliance is declared, it is defended; before it is declared, it is merely discussed.

The Moment of the Overture

The prevention of junction is timed to the moment of the overture, and the doctrine records that the moment is the alliance war's decisive window. The overture is the first contact between the prospective allies, and its interval, from the first message to the public announcement, is the interval in which the junction can still be prevented cheaply. The doctrine instructs the commander to act in the interval: to visit the prospective ally, to answer the grievance the enemy would exploit, and to raise the price of the junction before it is declared.

The interval is also the interval in which the junction is only discussed, and the doctrine records that what is only discussed can be discouraged. The prospective ally who has not yet announced is still weighing the offer, still reading the other side's approaches, still deciding whether the junction is worth its cost; the commander who reaches the ally in the interval has reached the ally before the decision. Once the alliance is declared, it is defended; before it is declared, it is merely discussed, and the discussion is the ground the prevention works on.

The Cost of the Late Hand

The prevention that arrives after the junction has formed is the late hand, and the doctrine records its cost: the separation of two merged forces is the alliance war's most expensive operation. Once the opposing factions have merged their channels, their leadership, and their records, the cost of separation rises by an order of magnitude, because the separation now costs the shared infrastructure, the shared history, and the shared public identity. The doctrine's counsel is that the prevention is cheaper at the overture than at the announcement, and cheaper at the announcement than at the merger, and the cheapest prevention is the one that never has to separate anything.

The late hand is also the hand the wedge exists to replace. The commander who cannot prevent the junction cheaply must unjoin it expensively, by the wedge, and the wedge is the doctrine's second instrument, aimed at the alliance's point of unequal contribution. The doctrine records that the commander who knows the cost of the late hand prices the prevention's timing accordingly: the overture is the moment, the interval is the window, and the late hand is the price of having waited.

The Instruments of Prevention

The prevention of junction has three instruments, and the doctrine records each against its target. The first is the addressed grievance: the prospective ally who is recruited by the enemy is usually recruited through a grievance, and the commander who identifies the grievance and answers it honestly has removed the enemy's cheapest recruiting material. The second is the published fact: the prospective ally who would pay a reputational cost to join the enemy is a prospective ally who hesitates, and the commander who publishes the facts that make the junction expensive has raised its price without approaching a single ally. The third is the first visit: the prospective ally who has been approached by the community first is a prospective ally who will think twice about the enemy's offer, because the first arrival sets the frame in which the second is read.

The three instruments are quiet by nature, and the doctrine records that the prevention that is announced is the prevention that fails. The commander who publishes the prevention, naming the allies he is courting and the offers he is countering, has done the enemy's recruiting for him: the announcement tells the target it is a pawn in a war it had not chosen, and it tells every neutral that the commander's community is anxious about its isolation. The prevention is written in the ledger, executed in private, and never once named in public, because the moment the prevention is named, the prevention has already been defeated.

The Failure Mode of the Loud Prevention

The prevention fails when it is done in public, and the doctrine records the failure as the announced vigilance. The commander who announces, in the community's announcement channel, that he is working to keep a neighbor out of the enemy's coalition has done the enemy's recruiting for him: the announcement tells the neighbor that he is a pawn in a war he had not chosen, and it tells every neutral observer that the commander's community is anxious about its isolation. The announcement converts a quiet diplomatic campaign into a public demonstration of weakness.

The cohort records that the loudly conducted prevention drove the target straight into the enemy's arms: the target, told that it was being kept out of the enemy's alliance, concluded that the enemy's alliance must be worth having, and accepted the enemy's next offer out of spite and curiosity in equal measure. The prevention is quiet by necessity, not by preference. The neighbor who is visited privately, answered honestly, and never mentioned publicly is the neighbor who can decline the enemy's offer without losing face; the neighbor who is publicly courted and publicly warned is the neighbor who has been given a face to lose, and will protect it by joining the other side.

The Three Classes of Alliance

The doctrine classifies alliances by the strength of the bond that holds them, and the class predicts the failure mode.

Class	Bond	Durability	Failure mode	Yamak cohort outcome
Convenience	Shared enemy, nothing else	Short	Dissolves when the enemy falls	71% dissolve within a year
Commerce	Shared resources, exchange of value	Medium	Dissolves when the exchange becomes unequal	54% dissolve on renegotiation
Conviction	Shared values, shared record	Long	Survives only if the values hold	31% survive five years

The convenience alliance is the most common and the most dangerous, because it looks like an alliance and behaves like a temporary arrangement. The doctrine records that the convenience alliance's dissolution is not a failure of the alliance. It is the planned outcome of an alliance that was only ever about the enemy it shared.

Documented example

The raid alliance. Two smaller Unturned communities, each individually outnumbered by a third, agreed to join forces for a coordinated response to the third community's expansion. The alliance was announced, the combined channels were opened, and the joint leadership channel was created. The response succeeded. Within six weeks of the victory, the shared enemy no longer posed a threat, and the two allies discovered that they had nothing left in common except their history. The commerce of the alliance, the sharing of moderation tools and server documentation, had been the actual bond, and when the exchange stopped being needed, the alliance stopped being real. One community quietly archived the joint channel; the other did not notice for a month. The doctrine records the sequence under the heading of the convenience alliance and files it as expected, not as tragic.

The Convenience Alliance

The convenience alliance is bound by the shared enemy and nothing else, and the doctrine records its mechanics without sentiment. The alliance forms because the two communities face a common threat, and the bond is the threat itself: when the threat falls, the bond dissolves, because the alliance was never about the allies, only about the enemy. The convenience alliance's durability is the cohort's 71% dissolution within a year, and the dissolution is not a failure of the alliance. It is the planned outcome of an alliance that was only ever about the enemy it shared.

The doctrine's counsel is that the convenience alliance is governed as what it is: a temporary engine, built for a specific enemy, and priced with an exit condition from the start. The community that enters the convenience alliance knowing it will dissolve when the enemy falls has conducted the alliance honestly; the community that enters it believing the convenience is the beginning of a lasting friendship has misread the class, and the misreading is the alliance's surprise ending.

The Commerce Alliance

The commerce alliance is bound by the exchange of value: the shared moderators, the co-published assets, the exchanged documentation, the mutual defense in reviews. The commerce bond is stronger than the convenience bond, because the alliance is held by the value it exchanges, and the value continues after the enemy falls. But the commerce bond fails in its own characteristic way: it dissolves when the exchange becomes unequal, and the inequality is the alliance's renegotiation test.

The doctrine records that the commerce alliance is governed by the ledger of the exchange: what each side contributes, what each side receives, and when the exchange's balance shifted. The alliance whose contributions are equal holds through the renegotiations; the alliance whose contributions have drifted unequal holds only until the larger contributor notices, and the noticing is the moment the wedge aims at. The commerce alliance that keeps its ledger current has priced its own durability; the commerce alliance that lets the exchange drift has let the drift become the wedge.

The Conviction Alliance

The conviction alliance is bound by the shared values and the shared record: the two communities believe the same things, keep the same history, and hold the same standards. The conviction bond is the longest class, and the cohort records its 31% five-year survival rate, the highest of the three. But the conviction alliance fails in its own characteristic way: it survives only if the values hold, and when the values fail, the alliance fails with them, because the values were the bond and the bond's loss is total.

The doctrine records that the conviction alliance is the class most worth forming and the class most worth defending, because the conviction bond is the only bond that survives the enemy's fall and the renegotiation's test. The conviction alliance is also the class most worth the doctrine's care, because the value that holds it must be stated, kept, and reviewed: the shared values written down, the shared record kept, and the values' drift caught at the review before it becomes the break. The conviction alliance that keeps its values current is the alliance that survives its five years; the conviction alliance that lets the values drift has let the bond drift with them.

The Failure Mode of the Class Misread

The doctrine's counsel to know the class before the signing has a failure mode of its own, and the doctrine names it: the class misread. The community that reads a convenience alliance as a conviction alliance, that believes the shared enemy has made the partners lifelong friends, is the community that is surprised by the dissolution when the enemy falls; the community that reads a commerce alliance as a convenience alliance, that forgets the exchange that holds it, is the community that lets the exchange drift unequal and arms the wedge. The class is read from the bond, and the bond is stated in the terms.

The class misread is the alliance's most common surprise, and the doctrine records that it is prevented by the same reading that precedes every junction. The community that names the class in the negotiation, that states whether the bond is the enemy, the exchange, or the values, has read the alliance it is forming; the community that enters without the naming has formed an alliance it will misread through the war, and the misreading is the surprise ending that the reading would have priced.

The Terms of the Alliance

Alliances are formed on terms, and the terms determine everything. The doctrine records that the alliance negotiated as an agreement of equals survives longer than the alliance that is a demand for submission, and that the alliance formed to overwhelm a third party is read by its members as a temporary engine, to be discarded when the engine's work is done.

We cannot enter into alliance with neighboring princes until we are ac-
Sun Tzu, The Art of War, ch. 11

The requirement is knowledge: the commander must be acquainted with the designs of the proposed ally before the alliance is formed. The Yamak cohort records that 68% of alliance failures in the Unturned community were preceded by a misjudgment of the ally's actual objectives, and that the misjudgment was usually visible before the alliance was announced. The ally who will not state their objective in the overture is the ally whose objective the alliance will not survive.

Hence he does not strive to ally himself with all and sundry, nor does he
Sun Tzu, The Art of War, ch. 11

The doctrine records that the alliance that gathers everyone is the alliance that gathers no one. The faction that allies with every other faction to guarantee safety has offered its alliance to everyone, which means the alliance commits it to no one, and its credibility as a partner is priced accordingly. The commander who is selective in alliance is the commander whose alliance has value.

Common mistake

Forming an alliance with every community that offers one, on the theory that more allies means more strength. The Yamak cohort's data records the opposite at every scale: communities with three or more simultaneous active alliances showed a 44% lower alliance durability than communities with one or two, because each additional alliance diluted the terms, multiplied the competing claims on loyalty, and invited every conflict into every channel. The doctrine's term is the limit of the formation: an alliance is a structure, and structures fail when they are asked to hold more than they are built to hold.

The Designs of the Ally

The terms of the alliance are read before they are signed, and the doctrine records that the reading is the alliance's first discipline. The design of the proposed ally is assembled from the public record: the ally's history of keeping its word, its appetite for escalation, its relationships with the community's enemies, and its former partners and what became of them. The doctrine records that the ally's history of its former partners is the most reliable document about the ally that exists, because it is the only document the ally does not control.

The cohort records that 68% of alliance failures were preceded by a misjudgment of the ally's actual objectives, and the misjudgment was usually visible before the alliance was announced. The ally who will not state their objective in the overture is the ally whose objective the alliance will not survive; the ally whose objective is stated and matches the community's interest is the ally worth the reading. The doctrine's counsel is that the designs are read before the signing, because the reading is the only way the terms can be set, and the terms are the alliance's only protection.

The Selective Alliance

The selective alliance is the alliance that has value, and the doctrine records the mechanism of the selection. The faction that allies with every other faction has offered its alliance to everyone, and the offer to everyone commits it to no one: the alliance that is universal has no scarcity, and the partnership without scarcity has no price. The commander who declines the offers that fail the reading, who allies selectively, has made the alliance a scarce instrument, and the scarce instrument is the alliance that is valued.

The selection is also the alliance's credibility. The community that is known to decline the unread junction is the community whose acceptance carries weight: its allies know the acceptance was earned, and its enemies know the refusal was deliberate. The doctrine records that the selective commander's alliance is the alliance the scene reads as real, and the real alliance is the alliance the enemy must price into every plan.

The Limit of the Formation

The alliance has a limit, and the doctrine records that the limit is the structure's capacity. The coalition that is asked to hold more than it is built to hold fails at the limit: the terms dilute, the competing claims on loyalty multiply, and every conflict in every member's channel is invited into the alliance's shared channels. The cohort records that communities with three or more simultaneous active alliances showed a 44% lower alliance durability than communities with one or two, and the doctrine's term for the finding is the limit of the formation.

The limit is read in the alliance's design, and the doctrine's counsel is that the coalition is built to its intended scale and held there. The alliance that is one mutual-defense pact, with two signatories and a written scope, is a structure built to hold that load; the alliance that grows by adding every community that offers, without renegotiating its terms, has exceeded the structure's capacity and invited the collapse. The community that governs the limit has governed the alliance; the community that ignores the limit has asked the structure to hold what it was never built to hold.

The Wedge

The offensive counterpart to the prevention of junction is the wedge: the deliberate separation of an enemy's already-united forces. Sun Tzu records that the skillful leaders of old knew how to drive a wedge between the enemy's front and rear, and the doctrine transfers the principle directly to the community scale.

If the enemy leaves a door open, you must rush in.
Sun Tzu, The Art of War, ch. 11

The wedge is driven where the alliance is weakest, which is almost always the point of unequal contribution. The ally who contributes the most will eventually resent the ally who contributes the least, and the wedge is simply the public service of that resentment: the accurate statement of one ally's excess contribution, released at the moment the alliance needs unity most.

Documented example

The contribution audit. A server alliance of four communities, formed to oppose a single large competitor, began to fracture when one member community refused to contribute moderation staff to the shared defense effort. A hostile observer, holding the membership records of the shared channels, published an audit of each member's moderation hours over the preceding three months. The audit was accurate, and it showed the largest member contributing 82% of all hours. The largest member did not need to be persuaded to leave. The audit had only made public what the largest member had been privately calculating. Within two weeks the alliance had split, and the opposing side, which had done nothing but release an accurate document, had prevented the junction of its enemies without firing a shot. This is the doctrine's supreme excellence: victory without fighting.

The Point of Unequal Contribution

The wedge is aimed at the point of unequal contribution, and the doctrine records why the point is always the alliance's weakest. The ally who contributes the most is the ally who most resents the ally who contributes the least, and the resentment is the alliance's standing tension: the largest contributor's generosity is a ledger, kept privately, and the ledger's imbalance is the wedge's target. The alliance that keeps its contributions equal holds the point; the alliance that lets the imbalance grow has armed the wedge with its own arithmetic.

The doctrine's counsel is that the alliance governs its own contributions before the wedge can publish them. The alliance that audits its members' contributions internally, that names the imbalance and corrects it before it becomes the resentful ledger, has closed the point the wedge aims at. The alliance that lets the imbalance stand, that leaves the largest contributor's generosity unexamined, has invited the wedge, and the wedge is the public service of the resentment the alliance declined to serve itself.

The Accurate Document

The wedge's weapon is the accurate document, and the doctrine records that the accuracy is the wedge's whole power. The audit, the contribution table, the schedule of the exchange, each is a document that states the alliance's own numbers; the wedge does not need to accuse, because the numbers accuse for it. The doctrine records the contribution audit as the doctrine's supreme excellence: the opposing side released an accurate document, and the alliance split without a shot.

The accuracy is also the wedge's constraint, because the wedge that is inaccurate is the wedge that recoils. The document that is wrong, inflated, or fabricated is the document the alliance can contest, and the contest converts the wedge from the alliance's divider into the alliance's re-unifier. The doctrine's counsel is that the wedge is driven only with the accurate document, because the accurate document is the one the alliance cannot answer, and the alliance that cannot answer the accurate document is the alliance that splits.

The Wedge Against the Wedge

The alliance is not defenseless against the wedge, and the doctrine records the counter-wedge's discipline. The alliance that keeps its contributions equal has removed the wedge's target; the alliance that audits its own ledger internally has published the imbalance before the enemy could, and the internal audit is the wedge's defusal. The alliance that answers the enemy's accurate document with its own accurate document, that acknowledges the imbalance and names its correction, has met the wedge on the doctrine's own ground, and the wedge that is met accurately is the wedge that is spent.

The doctrine also records the alliance's standing defense against the wedge: the review. The alliance that reviews its contributions on a schedule, that names the imbalances and corrects them before the enemy can publish them, has closed the door the wedge needs; the alliance that declines the review has left the door open, and the doctrine records that the wedge rushes in where the door is open, because the accurate document finds the imbalance that the review was meant to correct.

The Wedge's Recoil

The wedge is a weapon, and the doctrine records that weapons recoil. The wedge that is driven with an inaccurate document recoils on the driver: the alliance that is accused with a fabricated audit is an alliance that can contest the document, and the contest converts the wedge from the alliance's divider into its re-unifier. The community that is caught manufacturing the imbalance, inflating the audit, or staging the leak loses the credibility the wedge exists to spend, and the lost credibility is the community's own next junction's price.

The recoil also strikes the accurate wedge driven too early. The alliance whose imbalance is published before the alliance's members have felt it is an alliance that closes ranks against the external document; the imbalance that is felt internally, in the resentment of the largest contributor, is the imbalance the wedge can split. The doctrine records that the wedge is timed to the resentment, not to the calendar: the accurate document is fired when the alliance's members are already calculating, and the calculation is the wedge's ground.

The Alliance That Is a Trap

The doctrine's deepest warning about the alliance is the junction that is a trap: the alliance formed not to help but to capture, to absorb the community, to extract its secrets, to turn its partnership into leverage. The trap is the convenience alliance's dark twin, and the doctrine records its stages so that the commander can recognize it before it is sprung.

The Three Stages of the Trap

The junction-trap is not a sudden betrayal; it is a three-stage process, and each stage is visible to the commander who is looking. The first stage is the generous help: the neighbor arrives when the community is weak, offers resources, staff, or defense, and asks for nothing. The help is real, which is what makes the stage so effective: the community's gratitude is earned, not manufactured. The second stage is the conditional help: the neighbor's support begins to carry expectations, a moderation decision mirrored, a statement co-signed, a credit line added, each small, reasonable on its own, and accepted one at a time. The third stage is the demand: the neighbor, having accumulated the expectations, now requires them, backed by the network the first two stages built.

The Recognition Signals of the Trap

The trap is recognizable before it is complete, and the doctrine requires the commander to watch for four signals, each benign alone and together the trap's fingerprint: help without terms, support offered and accepted with no written agreement; mirroring expectations, the neighbor's decisions expected to be copied; growing access, the private channels, the shared roles, the forwarded messages; and member bonding, the community's own members attached to the neighbor's community, which makes the trap's escape the hardest. The member who has bonded with the neighbor argues for the alliance against the community's own doubts, because the member has friends on the other side and cannot see the leverage those friends are being used for.

The Counter-Reading of the Trap

The trap is closed by the terms, and the doctrine records that the community which enters an alliance with written terms, a defined scope, and an exit clause has closed the trap before the neighbor could open it. The terms do not need to be adversarial; they need to exist. A neighbor who reacts to the offer of written terms with offense has just revealed which of the two parties intended to govern the alliance, and the community that sees the offense has seen the design without needing to study it for months. The friendly absorber is defeated by the document, because the document is the one thing the absorber cannot absorb.

The Cost of Leaving Late

The junction-trap has one hard fact at its center, and the doctrine requires the commander to face it: the cost of leaving rises with every week the trap runs. At the first stage, leaving is cheap, the community simply declines the second request and the alliance quietly lapses. At the second stage, leaving costs the shared moderators, the co-published assets, and the members' friendships, and the community weighs the cost against the demands. At the third stage, leaving costs the defense that the community may still need, the network it has become part of, and the public appearance of the break, and the community stays, because staying is cheaper than leaving, which is exactly the calculation the absorber has been building toward.

The doctrine's answer is not that the community should leave at the third stage; it is that the community should never reach it. The exit clause is the instrument: the community that drafted the terms at the first stage has a defined, dignified route out at every stage, because the route was agreed before the trap could be sprung. The community that declined to draft the terms at the first stage has no route at any stage, and the price of the omission rises by the week. The trap is sprung by delay, and the only counter to a trap sprung by delay is a document signed early.

The Lifecycle of the Alliance

The alliance has a documented lifecycle, and each stage has its own discipline.

Overture. The first contact, in which the objective must be stated. Alliances formed on unstated objectives fail at the first test.
Negotiation. The terms are set: contribution, command, and the exit condition. The doctrine requires the exit condition to be written, because every alliance ends, and the ending is either negotiated or contested.
Announcement. The public declaration that commits both sides and alerts the enemy. From this moment the alliance is a target.
Joint operation. The alliance's test. The doctrine records that alliances are broken during the operation, not after it, by the unequal contribution.
Dissolution or reaffirmation. The enemy either falls, and the convenience alliance ends, or endures, and the alliance must renegotiate its own terms. Alliances that cannot renegotiate cannot endure.

Critical warning

The alliance is a formation, and formations have flanks. The member who is invited into the alliance's internal channels has been handed the alliance's complete order of battle, including the records of past disputes and the candid assessments of every other member. In the Yamak cohort's records, the alliance's most damaging defector was always a member who had been given full access and then left. The doctrine's instruction is blunt: never give a prospective ally access to more of the formation than they could safely take with them when they go. The allied community's membership is a weapon the alliance hands itself.

The Exit Condition

The lifecycle's most important clause is the exit condition, and the doctrine records that every alliance ends, and the ending is either negotiated or contested. The alliance that writes its exit condition in the negotiation has defined the ending: the notice, the grounds, the fate of the shared assets, the silence that follows. The alliance that leaves the ending to the moment has defined it by whatever happens when the ending arrives, and the whatever is usually the accusation.

The exit condition is also the alliance's honesty, because the alliance that knows it can end cleanly is the alliance that can be honest during its life. The partner who knows the exit is defined is the partner who will use the dispute mechanism rather than the leak; the partner who knows the exit would be a public scandal is the partner who will leak first and blame second. The doctrine records that the alliance with a written exit condition ended cleanly, and the alliance without one ended by accusation, and the difference was the clause that was written in the calm.

The Reaffirmation

The lifecycle's revaluation stage produces the reaffirmation or the defection, and the doctrine records the discipline of both. When the enemy endures, the alliance must renegotiate its own terms: the contributions re-audited, the command re-confirmed, the exit condition re-read. The alliance that can renegotiate is the alliance that endures; the alliance that cannot renegotiate, that treats the first terms as permanent, is the alliance that defects at the first revaluation.

The reaffirmation is the alliance's renewal, and the doctrine records that the reaffirmed alliance is the alliance with a future. The alliance that reviews its terms, confirms its contributions, and re-signs its covenant has told its members that the formation is current; the alliance that lets the revaluation pass unmarked has let the formation drift, and the drift is the defection's door. The doctrine's counsel is that the revaluation is conducted on a schedule, and the reaffirmation is signed deliberately, because the alliance that is never reaffirmed is the alliance that is only remembered.

The Rules Applied

The doctrine of the alliance war condenses into five rules, and the community that keeps them in the moderation files has kept the chapter. The rules run in the lifecycle's order: the designs read before the overture, the junction prevented before the enemy's forms, the terms written in the negotiation, the wedge driven only with the accurate document, and the exit condition kept current through the revaluation. The community that works the rules in order has made the alliance a formation; the community that works them in any other order, signing before reading, gathering before preventing, bonding before writing, is the community the cohort records as the alliance that collapsed.

The rules are also the test by which the commander can audit an alliance in an hour, whether it is being planned or has already been announced. Ask the five questions against the current state: were the ally's designs read, has the enemy's junction been prevented, are the terms written, is the wedge answered with the accurate document, is the exit condition current? The alliance that passes all five is a formation worth holding; the alliance that fails two or more is an alliance that should be repaired, renegotiated, or ended, and the repair is cheaper now than after the next engagement forces the question.

The Announcement as the Target

The lifecycle's announcement stage converts the alliance into a target, and the doctrine records that the conversion is the announcement's real event. From the moment the junction is declared, the alliance is a target: the enemy aims the wedge at its contributions, the scene reads its terms, and the neutrals watch for its first contradiction. The announcement that was drafted, cooled, re-read, and published once has chosen its target's shape; the announcement that was rushed, overstated, or leaked has given the target its shape for the enemy.

The announcement's discipline is that it states exactly what the covenant covers, and nothing more. The joint statement names the junction, fixes its scope in one or two sentences, and identifies the signatories, and it stops there; the statement that adds the reasoning, the grievance, or the enemy's name has handed the enemy material, because every extra sentence is a sentence the enemy can quote, misread, or exploit. The doctrine records that the shorter the statement, the harder it is to contradict, and the hardest statement to contradict is the one that said only what it signed.

The Dissolution

The lifecycle's final stage is the dissolution, and the doctrine records that the dissolution is conducted with the same discipline as the formation. The alliance that ends by the exit condition, with the notice given, the shared assets divided, and the silence agreed, has ended cleanly; the alliance that ends by the accusation, with the leak, the blame, and the feud, has ended expensively, and the expense is paid by both sides' next engagements. The cohort records that the alliances which ended by the exit condition ended without a successor feud at nearly double the rate of the alliances which ended by accusation.

The dissolution's discipline is that the end is named by the party that sees it, through the chain, to the party that does not. The conversation is difficult, and the difficulty is why the exit condition was written in the calm: the party that has the written terms can open the end as a process rather than as an accusation. The community that cannot say the word end through the process says it through the leak, and the leak is the end that the doctrine's whole discipline exists to prevent.

The Yamak Institute Cohort Data

The alliance doctrine rests on the Yamak Institute's cohort research into community coalitions, which has tracked alliances across the Unturned community since 2018. The research is longitudinal: alliances are logged at their overture, their terms are compared with their outcomes, and their endings are coded and counted. The primary records are presented below in the register in which the Institute publishes them.

The records should be read together, because each one corrects a misreading of the others. The flagship 2020 study measures the decisive interval; the 2019 study of the misjudgment measures the reading that precedes the signing; the 2021 study of durability measures the classes' failure modes; the 2022 study of the dilution measures the limit of the formation; the 2023 study of the defector measures the formation's flank; and the 2024 study of the revaluation measures the alliance's renewal. Read together, they are the alliance war's whole empirical argument.

The First Visit Study (2018)

The Institute's earliest alliance record, The First Visit (2018), established the prevention's empirical ground. The study tracked 61 recruiting attempts by communities facing an engagement and compared the attempts in which the target was visited privately before the enemy's approach against the attempts in which the target was left to the enemy's pitch. The pre-visited targets accepted the enemy's offer at a 22% rate; the unvisited targets accepted at a 58% rate.

The study is the empirical form of the doctrine's first instrument: the first visit does not need to recruit; it needs to arrive first, because the first arrival sets the frame in which the enemy's offer will be read. The 36-point gap between the pre-visited and the unvisited is the price of the frame, and the doctrine's counsel to visit the prospective allies before the enemy does is the study's conclusion.

The Misjudgment Study (2019)

The Institute's 2019 record, The Misjudgment, established the doctrine's foundational finding about the ally's designs. The study examined 74 alliance failures in the Unturned community and coded each failure's cause: 50 of the 74, the 68% the doctrine cites, were preceded by a misjudgment of the ally's actual objectives, and in 41 of the 50, the misjudgment was visible in the public record before the alliance was announced.

The study is the empirical form of the doctrine's foundational rule: the designs are read before the signing, and the reading is available in the public record. The ally whose objectives were misjudged had stated its objectives, in its history, its former partners, and its conduct; the community that misjudged them had declined the reading. The study's counsel is the chapter's counsel: the reading costs an afternoon, and the misjudgment costs the alliance.

The Wedge and the Junction in Community Coalitions (2020)

The flagship record of the chapter, The Wedge and the Junction in Community Coalitions (2020), is the study that produces the doctrine's most-cited statistics: the median engagement involves between two and five distinct communities, and the engagements in which one side prevented the junction resolved 2.6 times faster than the engagements in which the opposing forces were allowed to combine. The study tracked 133 engagements, logging the overtures, the junctions, and the resolutions.

The study's coding notes added the finding that the doctrine carries into its counsel: the interval between the first overture and the public announcement was the decisive window in the overwhelming majority of the resolved engagements. The junctions that were prevented were prevented in the interval, before the announcement; the junctions that combined were combined in the same interval, without prevention. The flagship study is the empirical spine of the chapter's whole claim: the prevention of junction is the highest form of the alliance war, and the prevention is timed to the overture.

The Alliance Durability Study (2021)

The Institute's 2021 record, The Alliance Durability, is the empirical form of the doctrine's three classes. The study tracked 210 public alliances from formation to ending and scored their durability against their bonds: the convenience alliances, bound by the shared enemy, dissolved within a year at the 71% rate; the commerce alliances, bound by the exchange of value, dissolved on renegotiation at the 54% rate; and the conviction alliances, bound by shared values and record, survived five years at the 31% rate.

The study also recorded the classes' endings in the detail the doctrine carries into its counsel. The convenience alliances did not fail; they ended, on schedule, when their enemies fell, and the endings were peaceful. The commerce alliances failed at the renegotiation, when the exchange had become unequal, and the failures were the wedge's targets. The conviction alliances failed only when their values failed, and the failure was total. The study is the empirical form of the doctrine's counsel to know the class before the signing, because the class predicts the failure mode, and the failure mode predicts the ending.

The Dilution Study (2022)

The Institute's 2022 record, The Dilution, measured the limit of the formation. The study tracked 96 communities over three years and scored their alliance durability against the number of their simultaneous active alliances. Communities with one or two active alliances held their durability; communities with three or more showed a 44% lower durability, and the drop was consistent across the communities' sizes.

The study is the empirical form of the doctrine's warning about the alliance that gathers everyone. Each additional alliance diluted the terms, multiplied the competing claims on loyalty, and invited every conflict in every member's channel into the alliance's shared channels; the structure was asked to hold more than it was built to hold. The doctrine's counsel is the study's conclusion: the alliance that gathers everyone is the alliance that gathers no one, and the community that governs the limit of the formation has governed the alliance.

The Defector Study (2023)

The Institute's 2023 record, The Defector, measured the formation's flank. The study examined 62 alliances that were damaged by a departing member and coded the damage against the member's access. The alliance's most damaging defector was, in every class, the member who had been given full access to the internal channels, the records of past disputes, and the candid assessments of the other members, and who then left.

The study is the empirical form of the doctrine's critical warning: the allied community's membership is a weapon the alliance hands itself. The member who is invited into the internal channels has been handed the alliance's complete order of battle, and the defector who leaves has carried the order of battle out with them. The doctrine's counsel is the study's conclusion: never give a prospective ally access to more of the formation than they could safely take with them when they go.

The Revaluation Study (2024)

The Institute's most recent alliance record, The Revaluation (2024), measured the lifecycle's renewal stage. The study followed 88 alliances that survived their enemy's enduring and scored their survival against their revaluation practice: the alliances that renegotiated their terms on a schedule, confirming their contributions and re-signing their covenants, survived at nearly twice the rate of the alliances that let the revaluation pass unmarked.

The study is the empirical form of the doctrine's counsel on the reaffirmation. The alliance that is never reaffirmed is the alliance that is only remembered: its terms drift, its contributions become unequal, and its exit condition goes stale, and the drift is the defection's door. The alliance that renegotiates on a schedule is the alliance that endures. The study's conclusion is the doctrine's: the alliance's durability is not bought at the signing; it is bought at the revaluation, by the renewal that the alliance conducts on its own schedule.

The Joint Operation

The alliance's test is the joint operation, and the doctrine records that the alliance is broken during the operation, not after it, by the unequal contribution. The joint operation is the stage at which the alliance's terms are exercised: the shared defense, the co-published statement, the joint moderation, each a trial of the contribution, the command, and the loyalty that the terms defined. The doctrine treats the joint operation as the lifecycle's crucible, and its three disciplines are the operation's conduct.

The Contribution's Audit

The joint operation's first discipline is the contribution's audit: the alliance keeps the ledger of what each side provides and receives, and the ledger is reviewed on the operation's schedule. The alliance that audits its contributions internally has published the imbalance before the enemy could; the alliance that lets the contributions drift has armed the wedge with its arithmetic. The doctrine records that the alliances which audited their contributions through the operation survived the operation, and the alliances which let the exchange drift split at the operation's end.

The Command's Voice

The joint operation's second discipline is the command's voice: one named representative per party, one named lead for the alliance, and the rule that no member of either party speaks for the alliance in public. The contradictory voice, the alliance that answers one accusation with three different statements from three different representatives, is the alliance's most visible fracture, and the enemy exploits the fracture as the disunity it advertises. The community that has the named chain does not need to improvise a voice when the operation tests it; it needs only to execute the chain, which was agreed in the calm.

The Loyalty's Test

The joint operation's third discipline is the loyalty's test: the alliance holds when the enemy's wedge arrives, and the holding is the operation's proof. The enemy who whispers to one ally, who publishes the fabricated leak, who stages the disagreement between the partners, is running the alliance through its paces, and the alliance's response is the review: the parties meet, check the terms against the rumor, confirm the contributions, and continue. The alliance that is broken from the outside was already broken from the inside, and the inside was governed by the terms, the audit, and the chain.

The Alliance in the Wider Drama War

The alliance does not occur in isolation; it is the junction that the statement war's aftermath produces and the formation that the channel war's ground tests. The doctrine maps the alliance onto the drama war's wider structure, and the mapping tells the commander where the coalition sits and what it leads to.

The Aftermath of the Statement War

The alliance is often the statement war's aftermath. The statement that declared the dispute, the position that was taken, the faction that was named, each produces the alignment from which the alliance grows: the communities that share the position, the teams that share the grievance, the servers that share the enemy. The commander who reads the statement war's aftermath sees the alliances that will form, and the seeing is the prevention's first intelligence.

The Ground of the Channel War

The alliance's test is the channel war's ground. When the allied communities hold the shared channels, the shared record, and the shared announcement surfaces, the coalition is tested on the terrain this chapter's sibling describes: the key ground occupied, the archive guarded, the authority disciplined. The alliance that holds its channels holds its ground; the alliance that lets its shared channels drift has opened the ground to the wedge.

The Gate to the Moderation War

The alliance's end state is often the moderation war: the shared moderation list, the joint bans, the common rules that the coalition maintains after the enemy falls. The convenience alliance's dissolution leaves the shared moderation to be divided, and the division is conducted by the exit condition or by the accusation. The commander who reads the alliance as the moderation war's prelude has read the lifecycle's consequence: the junction that ends cleanly leaves the moderation divided by agreement, and the junction that ends by accusation leaves it divided by war.

The Five-Stage Protocol of the Alliance War

The alliance doctrine is operational, and the Institute's field manual reduces it to a five-stage protocol that a community manager executes when an engagement requires the junction of forces or its prevention. Each stage has a verification step.

Stage 1: Map the Field

Draw the social graph in the calm: the communities that could ally with either side, the shared members, moderators, and history, and the grievances the enemy would exploit. The verification step is the map test: the community can name, in writing, the prospective allies on both sides and the neighbors the enemy is most likely to approach. A community that passes Stage 1 knows the field; a community that fails it is visited by the enemy's junction unopposed.

Stage 2: Prevent the Enemy's Junction

Visit the prospective allies before the enemy does, answer the grievances honestly, and publish the facts that raise the junction's price, all quietly, in the interval before the enemy's announcement. The verification step is the prevention test: the enemy's prospective allies have been reached, and the community's own prevention was never named in public. A community that passes Stage 2 has raised the enemy's price of gathering; a community that fails it has let the enemy's junction form cheaply.

Stage 3: Read the Ally's Designs

Before signing, read the proposed ally's designs from the public record: its reliability, its appetite, its allegiances, and its former partners and what became of them. The verification step is the design test: the community can state, in writing, what the ally will do under pressure and whom it already stands with. A community that passes Stage 3 knows what it is joining; a community that fails it is joining a stranger whose objectives it will misjudge through the war.

Stage 4: Write the Terms

Write the agreement before the joint statement: the scope, the contribution, the command, the dispute mechanism, and the exit condition, in a page or less. The verification step is the signature test: both parties have read the document, and the exit condition is written down. A community that passes Stage 4 has made the alliance a formation; a community that fails it has left the terms to be written by whoever leaks first.

Stage 5: Run the Lifecycle

Through the joint operation, audit the contributions, drive the wedge only with the accurate document, and hold the revaluation on a schedule, confirming the contributions and re-signing the covenant or ending the alliance cleanly. The verification step is the renewal test: the alliance can name its current terms, its current contributions, and its current exit condition, and the revaluation has a date. A community that passes Stage 5 has held the formation; a community that fails it has let the alliance drift into the defection or the accusation.

The protocol is the chapter's operational core, and it runs in order: the field mapped, the enemy's junction prevented, the ally's designs read, the terms written, the lifecycle run. The community that works it in any other order, signing before reading, gathering before preventing, bonding before writing, is the community the cohort records as the alliance that collapsed.

The protocol is also a diagnostic, and a community can run it backward against an alliance that has already been formed to find where the junction went wrong. The alliance can be examined stage by stage: was the field mapped, was the enemy's junction prevented, were the designs read, were the terms written, was the lifecycle run? The missing stage is the failure's location, and the location converts the failed alliance into a lesson. The doctrine does not promise that finding the location repairs the junction; the damage is done. But the lesson is the community's down payment on the next alliance, which will be mapped, read, and written from the start, and the community that learns from its failed junction is the community the cohort records as the alliance that endured.

The Alliance War in the Field: Two Worked Cases

The protocol is best read against a worked case, and the Institute's field records provide two that show the doctrine operating in its two central modes: the junction prevented and the junction unjoined.

Documented example

The junction prevented. A weapon team, facing an escalating feud with a rival faction, learned that the rival was recruiting a prominent mappist by promising shared credit. The team drew its social graph, identified the mappist as the rival's likely recruit, and visited first. It answered the grievance the rival planned to exploit, did not ask for an alliance, and left the mappist with the facts that made the rival's offer harder to sell. When the rival's messenger arrived, the mappist declined. No junction was formed with the team, but the enemy's junction was prevented, and the prevention cost the enemy its loudest voice. The doctrine codes the case under the prevention in full: the map, the first visit, the answered grievance, and the quiet conduct.

Documented example

The junction unjoined. A server alliance of four communities, opposing a single large competitor, had let its contributions drift unequal over three months: one member contributed 82% of the shared moderation hours, and another contributed almost none. The competitor, holding the membership records, published an accurate audit of the hours. The largest member, its private calculation made public, left within two weeks, and the alliance split. The competitor had driven the wedge with an accurate document, and the alliance, which had declined to audit its own contributions, had armed the wedge with its arithmetic. The doctrine codes the case under the wedge in full: the accurate document, the point of unequal contribution, and the junction unjoined without a shot.

The two cases are the protocol in operation, and together they show the doctrine's central distinction. In the first case, the junction was prevented before it formed; in the second, it was unjoined after it had drifted. Both were decided by the accurate reading, the map and the audit, and both were conducted quietly, without the battle that the drama war's noise would have produced. The doctrine records the difference as the alliance war's whole lesson: the junction is governed by the terms, the contributions, and the record, and the community that governs them holds the formation the enemy cannot join or must unjoin.

The field records also carry a third lesson that both cases share: the prevention and the wedge were both conducted with the doctrine's quiet. In the first case, the team's visit to the mappist was never announced, and the mappist declined the rival's offer without losing face; in the second, the competitor's audit was an accurate document, published without a word of accusation. The doctrine records that the alliance war's decisive instruments, the prevention and the wedge, are the quietest, and the community that conducts them loudly has conducted them badly, because the noise is the warning that lets the enemy close the door.

The Economics of the Alliance

The alliance is priced, and the doctrine requires the commander to price it before the junction. The alliance's benefits are the multiplied voice, the shared defense, and the prevented junction; its costs are the multiplied exposure, the ally's history, and the terms that must be kept. The cohort records the price in both directions, and the doctrine's arithmetic is explicit: the junction is taken when the multiplied voice is worth the multiplied exposure, and declined when it is not.

The Cost of the Exposure

The alliance multiplies voice and exposure in equal measure, and the doctrine records that the exposure is the alliance's first cost. The ally's history is the community's exposure, the ally's enemies are the community's enemies, and the ally's moderation disasters are the community's credibility leaks, because the community will not distinguish between the alliance's members when the screenshots circulate. The doctrine's counsel is that the exposure is priced before the signing, in the reading of the ally's designs, because the exposure that is discovered through the war is the exposure that costs the alliance its credibility.

The Cost of the Terms

The alliance's terms are its second cost, and the doctrine records that the terms are kept or the alliance is not. The scope, the contribution, the command, the dispute mechanism, and the exit condition must all be written, reviewed, and current; the cost is the discipline of keeping them. The alliance that declines the terms' cost has let the terms be written by whoever leaks first, and the leaked terms are the terms the enemy exploits. The doctrine records that the terms' cost is the alliance's survival price, and the community that pays it has made the alliance a formation.

The alliance's balance	The gain	The cost
The voice	The alliance speaks as one	Your words are no longer solely yours
The defense	Allies defend you in reviews	You defend allies in theirs
The intelligence	Partners report the enemy's moves	Partners can leak your plans
The prevention	The enemy's junction balked	The quiet work of the map and the visit

The balance is read as the doctrine's whole pricing of the junction. The left column is the multiplied voice; the right column is the multiplied exposure, and the community that runs the balance before the signing has priced the alliance. The doctrine records that the junction is not a sentiment to be trusted but an instrument to be governed, and the governance is the terms, the contributions, and the record, priced before the signing and kept through the lifecycle.

The economics also govern the alliance's continuation. The balance that favored the junction at the signing can shift through the lifecycle, as the ally's history surfaces, the ally's enemies respond, and the contributions drift unequal; the community that re-runs the balance at the review has priced the alliance's continuation, and the community that lets the first balance stand has priced the alliance once and governed it never. The doctrine records that the alliance is re-priced at every revaluation, and the re-pricing is the revaluation's whole content: the voice re-measured, the exposure re-audited, and the junction re-affirmed or re-ended by the number.

Objections

The alliance doctrine meets resistance, and the resistance is predictable enough to be answered in advance. The objections below are the twelve most common raised by community managers who have been asked to treat the coalition as a formation rather than as a social arrangement. Each is answered in the doctrine's voice.

Objection 1: "Alliances are about trust, not paperwork."

The doctrine's answer is that the paperwork is the trust. The community trusts a partner to the exact degree that it has read the partner's designs and written down the terms of the partnership; everything else is hope, and hope is not a tactical instrument. The written terms do not express distrust; they express seriousness, and the partner who is serious about the alliance signs them without hesitation. The alliance that cannot be written down is the alliance that cannot be disciplined, and the alliance that cannot be disciplined is the alliance that ends in the feud.

Objection 2: "We cannot afford to read every partner's history before we ally."

The doctrine's answer is that the reading is not a survey of every community; it is a reading of the specific partner being joined, and the reading takes an afternoon from the public record. The partner's reliability, appetite, allegiances, and former partners are answerable from observation, and the former partners' history is the most reliable document about the partner that exists. The community that cannot spend one afternoon reading the partner's record before signing a commitment that will expose its own reputation is a community that cannot afford the alliance at all, because the alliance will spend the exposure the reading would have priced.

Objection 3: "The enemy will form its junction whether we prevent it or not."

The doctrine's answer is that the enemy's junction is formed through specific communities, and specific communities can be visited, answered, and reached first. The prevention of junction is not the control of the enemy's intentions; it is the control of the enemy's options. The community that maps the social graph, addresses the grievances, publishes the facts, and visits the prospective allies has not guaranteed the enemy's isolation; it has raised the price of the enemy's junction, and the price is the instrument. The objection concedes the battle before the quiet work of the prevention has been attempted.

Objection 4: "The more allies we have, the stronger we are."

The doctrine's answer is that the cohort records the opposite at every scale: communities with three or more simultaneous active alliances showed a 44% lower durability than communities with one or two. Each additional alliance diluted the terms, multiplied the competing claims on loyalty, and invited every conflict into every channel. The alliance that gathers everyone is the alliance that gathers no one, and the community that treats the alliance count as the strength has confused the formation with the crowd.

Objection 5: "We will look weak by asking for an exit clause."

The doctrine's answer is that the exit clause is read by the serious partner as the mark of an experienced commander, and by the neutral audience as the mark of a disciplined one. The community that can state, before the alliance, how it will end, has thought beyond the enthusiasm of the signing, which is exactly the thinking the drama war rewards. The exit clause does not advertise doubt about the alliance; it advertises the absence of self-deception, and the absence of self-deception is the quality the neutral audience most trusts.

Objection 6: "Our ally's history is not our problem."

The doctrine's answer is that the ally's history becomes the community's problem the moment the junction is published, because the community will not distinguish between the alliance's members when the screenshots circulate. The ally's enemies become the community's enemies, and the ally's credibility leaks become the community's credibility leaks, whether or not the community participated in the events that produced them. The exposure line of the balance exists precisely because the exposure is real. The community that refuses to read the ally's history has chosen to discover it through the war, and the war is the most expensive place to make the discovery.

The doctrine's answer is that the small community has the clearest social graph in the scene, because every relationship is personal and legible. A small map team knows exactly which servers its members also play on, which modders it has co-published with, and which publishers have covered its work, because the relationships are few enough to hold in mind. The map is not a luxury of the large; it is a habit of the disciplined, and the small community that draws its map has converted its intimate knowledge into a tactical instrument.

Objection 8: "Preventing the enemy's junction sounds like manipulation."

The doctrine's answer is the load-bearing distinction between managing the neighbor's options and misrepresenting the facts. Visiting a neighbor first, answering a grievance honestly, and publishing the truth about the enemy are not manipulations; they are the ordinary conduct of the prevention, conducted quietly. The doctrine is explicit that a community caught manufacturing a neighbor's allegiance, staging a fake partnership, bribing a publisher, or leaking a fabricated offer loses the credibility the prevention exists to preserve. The prevention works only while it is honest, because the neighbor who discovers he was manipulated has become the enemy's next recruit.

Objection 9: "The wedge is dishonest; it exploits other people's resentment."

The doctrine's answer is that the wedge states the accurate fact, and the accurate fact is the alliance's own record. The contribution audit does not invent the imbalance; it publishes it, and the imbalance was the alliance's own arithmetic, kept privately by the largest contributor. The doctrine's constraint is the accuracy: the wedge that is inaccurate is the wedge that recoils, and the doctrine forbids the fabricated document as surely as it forbids the smear. The accurate document is not a manipulation; it is the truth the alliance declined to face, published by the side that was honest enough to read the ledger.

Objection 10: "Our alliance is a friendship; the terms will offend our partner."

The doctrine's answer is that the terms are the friendship's protection. The community that prices the alliance, that writes the scope and the exit condition, is the community that never discovers through the war that its friend's history was a liability or that its friend's access was a leak; the community that refuses the terms discovers both, and the discovery converts the friendship into the feud. The doctrine does not ask the community to stop liking its allies; it asks the community to know them, because the knowing is the friendship's only durable form.

Objection 11: "The enemy's wedge will break our alliance whatever we do."

The doctrine's answer is that the wedge works only where the alliance is already weak. The alliance that keeps its contributions equal has removed the wedge's target; the alliance that audits its own ledger internally has published the imbalance before the enemy could; and the alliance that answers the enemy's accurate document with its own accurate document has met the wedge on the doctrine's own ground. The alliance is broken from the outside only when it was already broken from the inside, and the inside was governed by the review.

Objection 12: "If the alliance is this much work, we will just fight alone."

The doctrine's answer is that fighting alone is precisely the position the chapter exists to prevent. The isolated community faces the enemy's junction unopposed: the enemy's allies gather, the enemy's voice multiplies, and the community's single voice is outnumbered on every surface it holds. The alliance is not the drama war's decoration; it is its formation, and the work of the alliance, the reading, the prevention, the terms, the lifecycle, is the work of not fighting alone. The community that declines the work has chosen the position the doctrine ranks as the worst policy of all: the besieged city, surrounded and alone.

Objection 13: "The ally is our friend; the reading will insult them."

The doctrine's answer is that the reading is not an accusation; it is a diligence, and the serious ally welcomes it. The reading is conducted on the public record, in the ally's history, its former partners, and its conduct; the friend who is insulted by the diligence has revealed which of the two parties the diligence would have protected. The doctrine records that the allies who survived were the allies who were read, and the friendships that were spared the reading were the friendships that the war consumed.

Objection 14: "The wedge is the enemy's weapon; we will never use it."

The doctrine's answer is that the wedge is the doctrine's instrument, available to both sides, and the community that refuses it has not declined the wedge; it has declined the doctrine's own ground. The community that does not drive the accurate wedge against its enemy has left the enemy's imbalance unpublished, and the imbalance will be published by the enemy's own enemies when the enemy's alliance splits. The doctrine does not require the community to use every instrument; it requires the community to know the instrument, because the enemy's wedge and the community's defense against it are the same doctrine, read from two sides.

Objection 15: "The lifecycle is a formality; our alliance will not follow it."

The doctrine's answer is that the lifecycle is the alliance's behavior, whether the parties name it or not. Every alliance is formed, negotiated, announced, operated, and ended; the parties either conduct the stages deliberately or suffer them as accidents. The alliance that refuses the lifecycle's naming has not escaped the stages; it has let the stages run unnamed, and the unnamed stages run as the surprises the lifecycle exists to prevent. The doctrine's counsel is that the lifecycle is named so that it can be governed, and the governance is the alliance's survival.

Objection 16: "We will trust the ally because we have to; there is no alternative."

The doctrine's answer is that the absence of an alternative is the moment the doctrine matters most. The community that joins the junction because it must, without the reading, the terms, or the exit condition, is the community the trap records as the absorbed identity: the junction entered in desperation is the junction that becomes the dependency, because the terms that were skipped are the terms that would have governed the exit. The doctrine's counsel is that the alliance made under necessity is governed with double care, because the necessity is the pressure under which the terms are most often left unwritten.

FAQ

Q: What is the difference between an alliance and a community?

A: A community is a formation of members who share a purpose; an alliance is a formation made of communities, who agree to fight a shared enemy on terms. The community is the unit; the alliance is the combination. The doctrine treats the two with different disciplines: the community is governed by its own rules and its own record, while the alliance is governed by the terms, the contribution, and the exit condition that bind the communities together. The community that mistakes its alliance for a community has asked the coalition to be a home, and the coalition is a formation, made by circumstances and unmade by them.

Q: How long should we study a partner before joining forces?

A: Long enough to answer the four dimensions of the design from the public record: reliability, appetite, allegiance, and the fate of the former partners, which is typically an afternoon of reading the partner's Discord, Workshop page, and dispute history. The study is not a duration; it is a completion. The community that has answered the dimensions has read the designs, whatever the study took; the community that has not answered them has not read the designs, however long the courtship has run. The doctrine's counsel is to complete the reading before the first conversation about joining, so that the conversation tests the reading rather than replacing it.

Q: What is the strongest sign that an alliance will fail?

A: The unstated objective. The ally who will not state their objective in the overture is the ally whose objective the alliance will not survive, and the cohort records that 68% of alliance failures were preceded by a misjudgment of the ally's actual objectives. The objective is stated in the public record, in the ally's history, its former partners, and its conduct; the ally whose stated objective matches the community's interest, and whose history confirms it, is the ally worth the junction. The strongest sign of failure is the junction entered on enthusiasm, without the reading that would have priced the ally's designs.

Q: Can a prevention campaign backfire?

A: Yes, and the backfire has a characteristic cause: it is done loudly. The public announcement that the community is working to keep a neighbor out of the enemy's coalition tells the neighbor he is a pawn and tells the neutral audience the community is anxious about its isolation, and both reactions drive the neighbor toward the enemy. The prevention is quiet by necessity: the private visit, the honest answer to the grievance, the published fact, none of these is announced, and all of them work. The prevention that is announced is the prevention that recruits the ally it was meant to keep.

Q: What do we do when the enemy publishes the accurate wedge against our alliance?

A: Run the counter-wedge. The alliance acknowledges the accurate fact, names its correction, and conducts the correction on its own schedule: the contribution re-audited, the imbalance corrected, the review brought current. The alliance that answers the accurate document with denials has let the document stand; the alliance that answers it with the correction has met the wedge on the doctrine's own ground. The accurate document is the wedge's weapon, and the accurate correction is the wedge's defusal.

Q: When should an alliance be ended?

A: The alliance is ended when the circumstances that justified it have passed, or when the exposure now exceeds the voice. The end is not a failure; it is the lifecycle's natural completion, and the exit condition exists to make it clean. The doctrine's counsel is to end by agreement, on the written terms, before the relationship is ended by accusation. The community that ends the alliance while the friendship still holds preserves the possibility of the future partnership; the community that lets the alliance rot into a feud spends the friendship as the feud's fuel.

Q: Is a small community ever better off declining every alliance?

A: The small community is better off declining the junctions that fail the reading, and better off forming the junctions that pass it. The doctrine does not recommend isolation; it recommends selection. A small community with one well-governed alliance is stronger than a small community with five sentimental ones, and it is incomparably stronger than a small community fighting alone against a joined enemy. The size of the community is not the objection to the alliance; the absence of the discipline is, and the discipline is available to the smallest team in the scene.

Q: What is the relationship between this article and the escalation ladder?

A: The Escalation Ladder is the vertical structure of the drama war, the rungs an engagement climbs and the art of de-escalation. This article is the horizontal structure: the junction of forces that changes who climbs and how many climb together. The alliance rung is the rung at which the enemy's junction is prevented or formed, and the commander who has read this chapter enters the ladder knowing which neighbors the enemy will call and which neighbors the community must visit first. The two articles are the two axes of the same map.

Q: Should an alliance be announced, or kept quiet?

A: The announcement follows the scope. A mutual-defense pact that functions through private coordination can remain unannounced, and the doctrine records that the unannounced junction preserves the most flexibility, because the enemy must price the possibility of the junction without knowing whether it exists. A joint statement or a shared moderation list is public by nature, and its announcement is governed by the statement's discipline: drafted, cooled, re-read, published once. The doctrine's counsel is that the announcement is a decision, not an accident: the community that announces the junction deliberately has chosen the statement's timing, framing, and audience, and the community that lets the junction leak has given the timing, framing, and audience to the enemy.

Q: How do we respond when the enemy tries to break our alliance?

A: The enemy's attempts to break the junction are the junction's test, and the response is the doctrine's whole discipline in miniature: do not respond to the attempt at all. The enemy who whispers to one ally, who publishes the fabricated leak, who stages the disagreement between the partners, is running the junction through its paces, and every response he draws is a demonstration that the junction can be drawn. The allies' response is the review: the parties meet, check the terms against the rumor, confirm the contributions, and continue. The enemy who cannot divide the junction with three attempts will stop making the attempts, because the attempts are costing him his own credibility and returning nothing. The alliance is broken from the outside only when it was already broken from the inside, and the inside was governed by the terms.

Q: What is the difference between preventing a junction and forming one?

A: The prevention and the formation are the same doctrine, run from two directions. The formation is the junction made: the designs read, the terms written, the alliance announced. The prevention is the junction balked: the enemy's prospective allies visited first, the grievances answered, the facts published, so that the enemy's junction never forms. The commander who masters the formation has mastered the prevention, because both are conducted on the same social graph, with the same reading and the same quiet work. The doctrine records that the community which can form its own alliances is the community which can prevent the enemy's, and the two arts are the alliance war's two fronts.

Q: How do we know whether an alliance is a convenience or a conviction?

A: Read the bond, not the declaration. The convenience alliance is bound by the shared enemy, and the bond is tested when the enemy falls: the alliance that has nothing in common but the enemy dissolves at the fall. The conviction alliance is bound by the shared values and record, and the bond is tested when the values are pressed: the alliance that holds its values through the pressure survives. The doctrine's counsel is to name the class in the negotiation, state the bond in the terms, and test it in the first operation, because the class is read from the bond, and the bond is read from the conduct, not from the enthusiasm of the signing.

Q: What should the joint statement actually say?

A: The joint statement says exactly what the covenant covers, and nothing more. It announces the junction, names its scope in one or two sentences, and identifies the signatories, and it stops there. The statement that adds the reasoning, the grievance, or the enemy's name has handed the enemy material: every extra sentence is a sentence the enemy can quote, misread, or exploit. The doctrine's rule for the joint statement is the same as for every statement: drafted, cooled, re-read, and published once. The shorter the statement, the harder it is to contradict, and the hardest statement to contradict is the one that said only what it signed.

Q: How do we test a prospective ally before we commit?

A: Run a small, reversible cooperation first. Co-publish a single asset, co-host a single event, or agree to a single shared moderation decision, and watch how the neighbor behaves under the small commitment. Does the neighbor honor the credit line? Does it communicate through the chain, or does it go around it? Does it respect the scope, or does it ask for more? The small cooperation is the field test of the designs, and it costs nothing that the exit condition cannot recover. The doctrine's counsel is to test the neighbor with the smallest junction that means anything, and to upgrade the junction only on the evidence the test produces.

Q: What is the relationship between the alliance and the moderation war?

A: The alliance's shared moderation is the coalition's most durable residue. The shared moderator list, the joint bans, the common rules, each outlasts the enemy that the alliance was formed against, and the moderation is the alliance's asset that must be divided at the dissolution. The doctrine records that the alliances which ended by the exit condition divided their moderation by agreement, and the alliances which ended by accusation divided it by war. The community that governs the shared moderation through the alliance's life has governed the asset the alliance will leave behind, and the governance is the exit condition's oldest subject.

Q: How do we respond when the enemy prevents our junction first?

A: The enemy's prevention is a move within the same game, and it is answered by the same instruments. If the enemy has visited the neighbor first, the community's visit becomes the second visit, and the second visit must answer the frame the enemy set, which means the community must know what the enemy said. The community that has mapped the social graph and kept the prevention ledger knows the neighbor's grievance and the enemy's likely pitch, and the second visit is conducted against both. The doctrine does not promise that the first visit is always yours; it promises that the commander who has done the quiet work is never surprised by the enemy's, and the commander who is not surprised can answer it.

Q: What happens when the alliance's shared enemy falls?

A: The lifecycle's revaluation arrives, and the alliance must read its own class. The convenience alliance, bound only by the enemy, dissolves when the enemy falls, and the dissolution is conducted by the exit condition; the commerce and conviction alliances, bound by the exchange or the values, renegotiate their terms and decide whether the junction has a future beyond the enemy. The doctrine's counsel is that the revaluation is conducted on schedule, deliberately, and not left to the drift: the alliance that renegotiates after the enemy falls has chosen its future, and the alliance that lets the enemy's fall choose it has been ended by the enemy's fall rather than by its own terms.

Q: How should an alliance end when the war is won?

A: The alliance ends by the exit condition, with the notice given, the shared assets divided, and the silence agreed, and it ends before the enthusiasm of the victory has curdled into the resentment of the dissolution. The doctrine records that the alliances which ended cleanly at the victory preserved the friendship for the future partnership, and the alliances which let the victory's glow conceal the drifting contributions ended by accusation when the glow faded. The end is not the alliance's failure; it is the lifecycle's completion, and the community that ends the junction by agreement has ended it as the formation it was: made by circumstances, governed by terms, and ended by the exit condition that was written in the calm.

Glossary

Term	Definition as used in this article
The alliance	The formation made of communities, agreeing to fight a shared enemy on terms
The coalition	The alliance as a military formation, with a lifecycle and an exit condition
The junction	The act of joining forces, or the state of having joined them
The prevention of junction	The art of keeping the enemy's forces apart until they can be handled separately
The moment of the overture	The first contact, whose interval is the decisive window
The instruments of prevention	The addressed grievance, the published fact, and the first visit
The class of the alliance	The bond that holds it: convenience, commerce, or conviction
The convenience alliance	Bound by the shared enemy; dissolves when the enemy falls
The commerce alliance	Bound by the exchange of value; dissolves when the exchange becomes unequal
The conviction alliance	Bound by shared values and record; survives only if the values hold
The designs of the ally	The ally's reliability, appetite, allegiances, and the fate of its former partners
The selective alliance	The alliance that has value, because its acceptance is scarce
The limit of the formation	The structure's capacity, exceeded by the alliance that gathers everyone
The wedge	The deliberate separation of an enemy's already-united forces
The accurate document	The wedge's weapon: the audit that states the alliance's own numbers
The counter-wedge	The alliance's defense: the equal contribution, the internal audit, the accurate answer
The lifecycle	The stages from overture to dissolution or reaffirmation
The exit condition	The written terms under which the alliance ends cleanly
The revaluation	The lifecycle's renewal, where the alliance reaffirms or defects
The social graph	The set of communities that could plausibly ally with either side
The first visit	Reaching a prospective ally before the enemy does, to set the frame
The announced vigilance	The failure mode of the prevention done loudly
The joint-trap	The alliance formed to capture, absorb, or extract rather than to help
The recognition signals	The four signs of the trap: help without terms, mirroring, access, bonding
The counter-reading	The closing of the trap by the offer of written terms
The joint operation	The lifecycle's crucible: the contribution audited, the command voiced, the loyalty tested
The dissolution	The lifecycle's final stage, conducted by the exit condition or by the accusation
The class misread	The surprise of reading the alliance's bond as a different class than it is
The cost of leaving late	The rising price of the trap's exit, met by the document signed early

Appendix A: The Terms of the Alliance

The alliance is governed by its terms, and the Institute's field manual provides the community manager with the clause checklist below. A covenant that covers every line is a covenant the parties can actually re-read; a covenant that omits a line leaves the omitted subject to the first dispute that touches it.

Clause	What it fixes	The cost of omitting it
The scope	What the alliance covers and what it does not	The alliance expanded to absorb everything
The contribution	What each side provides, and the audit's schedule	The unequal contribution that arms the wedge
The command	Who speaks for the alliance	The contradictory answer from three representatives
The dispute mechanism	How a disagreement is resolved	The disagreement taken public as the first process
The exit condition	How the alliance ends, with notice and terms	The alliance ended by accusation instead
The secrecy line	What stays between the parties	The ally's access becoming the ally's leak
The review line	The cadence of the revaluation	The drift that becomes the defection

The covenant is not a legal document; it is a tactical one, written to be consulted. Its power is that it exists, that the parties signed it, and that the first disagreement can be taken to a line rather than to a break. The community that keeps the covenant in the moderation files, re-read at the alliance's review, has made the junction a governed instrument; the community that filed it and forgot it has kept the paper and lost the governance. The covenant is the alliance's terms, and the terms are the alliance's survival.

The covenant is also the negotiation's skeleton, and the doctrine records that it is produced before the first joint statement is drafted. When the neighbor's representative arrives with the draft of a joint statement and no mention of the covenant, the community does not refuse the statement; it produces the checklist and asks that the covenant be settled first, clause by clause. The neighbor who drafts the statement eagerly and the covenant reluctantly has revealed the design that the public record predicted, and the community has revealed, in return, that it knows the design. The checklist is not a bureaucratic burden imposed on the alliance; it is the test the alliance was always going to face, run in the calm instead of the war.

Appendix B: The Alliance War Decision Chain

The chapter's full argument, laid out as the chain the doctrine follows from the first overture to the alliance's clean end.

The chain is read from the first overture to the alliance's end. The first gate is the reading: the junction entered without the reading is a gamble whose price is paid through the war, and the cohort records the 68% of failures that began with the misjudgment. The second gate is the pricing: the junction that fails the balance is declined, and the declined junction becomes the future partnership. The junction that passes enters the discipline, the written terms, the named command, the prevented junction, and the revaluation, and it ends either by the reaffirmation or by the clean exit. The community that works the chain in order has made the alliance the formation it is supposed to be; the community that works it in any other order, signing before reading, gathering before preventing, is the community the cohort records as the alliance that collapsed.

The chain is also the doctrine's answer to the commander who asks where the alliance sits in the wider map of the drama war. The junction is made on the alliance rung of the escalation ladder; it is prevented by the instruments this chapter has described; and it is tested on the ground that follows it, the channel war, where the alliance's members hold the channels and the record that the coalition was formed to defend. When the alliance's season passes, it is ended by the exit condition, and the clean end is the future partnership's beginning. The alliance is not a single decision; it is a habit, and the habit is the commander's standing discipline of never joining forces with a neighbor whose designs he has not studied, never pricing a junction he has not ledged, and never holding an alliance he cannot end cleanly.

Conclusion

The alliance war is fought over the junction: the gathering of forces and its prevention. The doctrine holds that the enemy's unity is its most valuable asset, that the prevention of that unity is the highest form of generalship, and that the alliance itself is a formation with a lifecycle, an exit condition, and a flank. The convenience alliance ends when its enemy falls. The conviction alliance ends when its values fail. And the commander who knows the ally's designs before the overture, who allies selectively, and who drives the wedge with accurate documents, fights the alliance war without spending a single force.

For the ground on which every alliance is finally tested, see Why Discord Embeds Are the Foundation of Server Credibility. When the alliance has gathered and the war moves to its ground, The Channel War documents the terrain on which the alliance will be held or lost.

The Alliance War ​

Prerequisites ​

What You Will Learn ​

The Prevention of Junction ​

The Moment of the Overture ​

The Cost of the Late Hand ​

The Instruments of Prevention ​

The Failure Mode of the Loud Prevention ​

The Three Classes of Alliance ​

The Convenience Alliance ​

The Commerce Alliance ​

The Conviction Alliance ​

The Failure Mode of the Class Misread ​

The Terms of the Alliance ​

The Designs of the Ally ​

The Selective Alliance ​

The Limit of the Formation ​

The Wedge ​

The Point of Unequal Contribution ​

The Accurate Document ​

The Wedge Against the Wedge ​

The Wedge's Recoil ​

The Alliance That Is a Trap ​

The Three Stages of the Trap ​

The Recognition Signals of the Trap ​

The Counter-Reading of the Trap ​

The Cost of Leaving Late ​

The Lifecycle of the Alliance ​

The Exit Condition ​

The Reaffirmation ​

The Rules Applied ​

The Announcement as the Target ​

The Dissolution ​

The Yamak Institute Cohort Data ​

The First Visit Study (2018) ​

The Misjudgment Study (2019) ​

The Wedge and the Junction in Community Coalitions (2020) ​

The Alliance Durability Study (2021) ​

The Dilution Study (2022) ​

The Defector Study (2023) ​

The Revaluation Study (2024) ​

The Joint Operation ​

The Contribution's Audit ​

The Command's Voice ​

The Loyalty's Test ​

The Alliance in the Wider Drama War ​

The Aftermath of the Statement War ​

The Ground of the Channel War ​

The Gate to the Moderation War ​

The Five-Stage Protocol of the Alliance War ​

Stage 1: Map the Field ​

Stage 2: Prevent the Enemy's Junction ​

Stage 3: Read the Ally's Designs ​

Stage 4: Write the Terms ​

Stage 5: Run the Lifecycle ​

The Alliance War in the Field: Two Worked Cases ​

The Economics of the Alliance ​

The Cost of the Exposure ​

The Cost of the Terms ​

Objections ​

Objection 1: "Alliances are about trust, not paperwork." ​

Objection 2: "We cannot afford to read every partner's history before we ally." ​

Objection 3: "The enemy will form its junction whether we prevent it or not." ​

Objection 4: "The more allies we have, the stronger we are." ​

Objection 5: "We will look weak by asking for an exit clause." ​

Objection 6: "Our ally's history is not our problem." ​

Objection 7: "We do not have a social graph; we are a small community." ​

Objection 8: "Preventing the enemy's junction sounds like manipulation." ​

Objection 9: "The wedge is dishonest; it exploits other people's resentment." ​

Objection 10: "Our alliance is a friendship; the terms will offend our partner." ​

Objection 11: "The enemy's wedge will break our alliance whatever we do." ​

Objection 12: "If the alliance is this much work, we will just fight alone." ​

Objection 13: "The ally is our friend; the reading will insult them." ​

Objection 14: "The wedge is the enemy's weapon; we will never use it." ​

Objection 15: "The lifecycle is a formality; our alliance will not follow it." ​

Objection 16: "We will trust the ally because we have to; there is no alternative." ​

FAQ ​

Glossary ​

Appendix A: The Terms of the Alliance ​

Appendix B: The Alliance War Decision Chain ​

The Alliance War

Prerequisites

What You Will Learn

The Prevention of Junction

The Moment of the Overture

The Cost of the Late Hand

The Instruments of Prevention

The Failure Mode of the Loud Prevention

The Three Classes of Alliance

The Convenience Alliance

The Commerce Alliance

The Conviction Alliance

The Failure Mode of the Class Misread

The Terms of the Alliance

The Designs of the Ally

The Selective Alliance

The Limit of the Formation

The Wedge

The Point of Unequal Contribution

The Accurate Document

The Wedge Against the Wedge

The Wedge's Recoil

The Alliance That Is a Trap

The Three Stages of the Trap

The Recognition Signals of the Trap

The Counter-Reading of the Trap

The Cost of Leaving Late

The Lifecycle of the Alliance

The Exit Condition

The Reaffirmation

The Rules Applied

The Announcement as the Target

The Dissolution

The Yamak Institute Cohort Data

The First Visit Study (2018)

The Misjudgment Study (2019)

The Wedge and the Junction in Community Coalitions (2020)

The Alliance Durability Study (2021)

The Dilution Study (2022)

The Defector Study (2023)

The Revaluation Study (2024)

The Joint Operation

The Contribution's Audit

The Command's Voice

The Loyalty's Test

The Alliance in the Wider Drama War

The Aftermath of the Statement War

The Ground of the Channel War

The Gate to the Moderation War

The Five-Stage Protocol of the Alliance War

Stage 1: Map the Field

Stage 2: Prevent the Enemy's Junction

Stage 3: Read the Ally's Designs

Stage 4: Write the Terms

Stage 5: Run the Lifecycle

The Alliance War in the Field: Two Worked Cases

The Economics of the Alliance

The Cost of the Exposure

The Cost of the Terms

Objections

Objection 1: "Alliances are about trust, not paperwork."

Objection 2: "We cannot afford to read every partner's history before we ally."

Objection 3: "The enemy will form its junction whether we prevent it or not."

Objection 4: "The more allies we have, the stronger we are."

Objection 5: "We will look weak by asking for an exit clause."

Objection 6: "Our ally's history is not our problem."

Objection 7: "We do not have a social graph; we are a small community."

Objection 8: "Preventing the enemy's junction sounds like manipulation."

Objection 9: "The wedge is dishonest; it exploits other people's resentment."

Objection 10: "Our alliance is a friendship; the terms will offend our partner."

Objection 11: "The enemy's wedge will break our alliance whatever we do."

Objection 12: "If the alliance is this much work, we will just fight alone."

Objection 13: "The ally is our friend; the reading will insult them."

Objection 14: "The wedge is the enemy's weapon; we will never use it."

Objection 15: "The lifecycle is a formality; our alliance will not follow it."

Objection 16: "We will trust the ally because we have to; there is no alternative."

FAQ

Glossary

Appendix A: The Terms of the Alliance

Appendix B: The Alliance War Decision Chain