The Art of the Alliance: The Junction of Forces

Advanced40-60 minutesCross-platformDiscordSteam Workshop

The alliance is the drama war's force multiplier. A single server owner is one voice; a coalition of servers is a chorus. Sun Tzu's ranking of generalship places the alliance just below the highest art: the next best thing to balking the enemy's plans is preventing the junction of his forces, and the worst mistake is allowing your own forces to remain isolated while the enemy joins his.

Thus the highest form of generalship is to balk the enemy's plans; the next best is to prevent the junction of his forces; the next in order is to attack the enemy's army in the field; and the worst policy of all is to besiege walled cities.
Sun Tzu, The Art of War, ch. 3

The alliance is a junction of forces: two or more communities, teams, or publishers agreeing to move as one. In the Unturned community the junction takes recognizable forms - the server network that bans on the word of a partner, the modding team that issues joint statements, the shared moderator list, the cross-posted announcement. Each form multiplies voice, but each form also multiplies the surface on which the drama war is fought.

This article is a full treatment of the junction: why it exists, how it is made, how it is prevented from forming on the enemy's side, how it is priced, and how it is disciplined. It closes with the Yamak Institute's cohort data on alliances, a five-stage protocol for forming one, the ten most common objections to the alliance doctrine, and the reference material a community manager needs when the moment to join forces arrives.

The reader should note at the outset what this article is not. It is not an argument that every community should seek allies; the chapter's calculus produces declines as often as it produces junctions, and the decline is as much an act of command as the signing. It is not an account of alliance etiquette; the social graces of partnership are real, but they are the surface of a tactical instrument, and the instrument is what this article treats. And it is not a defense of the isolated community; the doctrine ranks isolation as the worst policy of all, and the commander who refuses every junction has chosen the besieged city. What this article is, is the discipline of the middle: the junction made and unmade by calculation, amplified without being consumed.

Prerequisites

An understanding of community conflict and the parties that fight it
Familiarity with the basic documentary weapons of the drama war, particularly the screenshot, which every ally can turn on you
A working sense of your own community's social graph: which servers, teams, and publishers it already shares members with
Willingness to treat an alliance as a tactical disposition rather than a social arrangement

What You Will Learn

Why the alliance is the drama war's force multiplier and its second-best art
The doctrine's foundational rule: read the designs of the neighbor before joining forces
The junction-trap and how it is sprung in stages
How to prevent the enemy's junction before it forms
The calculus of the junction: what the alliance multiplies and what it costs
The discipline of the written agreement, the chain of command, and the exit clause
The Yamak Institute's cohort findings on alliance durability and regret
A five-stage protocol for forming, holding, and ending a junction

The Purpose of the Alliance

The alliance exists to prevent the enemy's junction or to create your own. It is not a social arrangement; it is a tactical disposition. The commander who forms alliances for friendship forms alliances that fail under pressure, because friendship does not survive the first leaked screenshot of a disagreement.

We cannot enter into alliances until we are acquainted with the designs of our neighbors.
Sun Tzu, The Art of War, ch. 7

This is the doctrine's foundational rule of the alliance: do not join forces with a neighbor whose designs you have not studied. The neighbor's designs - his history of keeping his word, his appetite for escalation, his relationships with your enemies - are the alliance's entire terms, and they must be read before the junction is made, not discovered through it.

Reading the Designs of the Neighbor

The design of a neighbor is assembled from the public record, and in the Unturned community the record is unusually complete. The neighbor's Discord server shows its moderation decisions, its staffing, and its temper. Its Workshop page shows its history of credit, its update discipline, and its handling of criticism. Its server browser listing shows how it presents itself to the wider player pool. The commander who reads these three surfaces before the first conversation has read the neighbor's design without asking the neighbor a single question.

The design is read in four dimensions, and each dimension has a question that can be answered from observation:

Dimension	The question to answer	Where the answer lives
Reliability	Does this neighbor keep its word under pressure?	The moderation log, the history of joint announcements
Appetite	Does this neighbor escalate when provoked?	The record of past disputes and their endings
Allegiance	Whom does this neighbor already stand with?	The cross-posted announcements, the shared moderators
Temper	Does this neighbor reward loyalty or consume it?	The history of its former partners and what became of them

The fourth dimension is the one the doctrine weights most heavily. A neighbor that has absorbed three former partners is a neighbor that will absorb you, whatever its current warmth. The history of a neighbor's former partners is the most reliable document about the neighbor that exists, because it is the only document the neighbor does not control.

The Interview That Confirms the Design

The public reading of the designs is the bulk of the work, and the conversation is the confirmation. When the time comes to speak with the neighbor about the junction, the commander does not ask what the alliance will do; the commander tests what the neighbor will do under the specific pressures the public record has predicted. The neighbor who has always escalated in the past is offered a description of the campaign's likely provocations and watched for the temper the record predicts. The neighbor who has absorbed former partners is offered the draft terms and watched for the offense the absorber always shows.

The confirmation is a reading, not an interrogation, and its discipline is that the commander's questions come from the record rather than from the moment. A question that the record could not have produced is a question that invites the neighbor to perform rather than to reveal, and the performance is the confirmation of nothing. The commander who enters the conversation with the four dimensions already written down is the commander who can hear the neighbor's answers against the record; the commander who enters it curious and empty-handed is the commander who will be charmed by exactly the neighbor the record warned against.

The Kinds of Junction

The junction takes more forms than the grand alliance, and the commander who can name the forms can choose among them. The Institute's cohort distinguishes four kinds, ranked by the depth of the commitment:

Kind of junction	What it commits	The cost of leaving
The mutual-defense pact	Bans, moderation support, defense in reviews	Modest; each side keeps its own voice
The joint statement	A shared position published under both names	Moderate; the statement is on the record
The shared moderation	A common moderator list or rule surface	High; trust has been delegated
The merged identity	A single brand, banner, or server	Severe; the parties can no longer be separated

The kind of junction chosen should be the smallest one that achieves the object. The mutual-defense pact that suffices should not be upgraded to a merged identity out of enthusiasm, because the cost of leaving scales with the depth of the junction, and the enthusiasm that built the junction will not survive the first dispute that tests it. The doctrine's counsel is to start shallow and deepen only on evidence.

The deepening has a test that the doctrine names: the junction is upgraded when the shallow form has been exercised and held. The mutual-defense pact is deepened to the joint statement after the parties have actually defended each other once and the defense held; the joint statement is deepened to shared moderation after the parties have co-published and the credit held; the shared moderation is deepened to the merged identity only when the parties have demonstrated, over seasons, that their moderation, their voice, and their history can survive the merger. Each upgrade is a promotion on evidence, and the evidence is the shallow form's survival of its first test. The community that deepens without the test has bought the deepest junction on credit, and the deepest junction is the one in which the doctrine's cohorts record the smaller party most reliably disappearing.

The Failure Mode of the Sentimental Junction

The alliance made for friendship fails in a characteristic way. It is signed without terms, because the parties believe that their goodwill makes terms unnecessary. It is held without a chain of command, because neither party wants to appear to distrust the other. And it is ended without an exit clause, because neither party imagined an ending. When the first disagreement arrives - a moderation decision, a leaked message, a disputed credit - there is nothing to consult but memory, and the two parties' memories disagree.

The failure is not the disagreement. The failure is the absence of the machinery that would have turned the disagreement into a process. The sentimental junction has no process, so the disagreement becomes a break, and the break becomes a feud, and the feud is fought with everything the alliance was supposed to make impossible: the shared moderators now know both sides' procedures, the joint announcements have both sides' rhetorical habits on file, and the former allies quote each other's private words with the authority of insiders. The sentimental alliance does not merely fail. It converts its own members into the best-informed enemy either side has ever faced.

The sentimental junction is also the junction that produces the doctrine's most instructive lesson about the writing of terms: the parties who believe they do not need the document are the parties who need it most. The friendship that seems to make the terms unnecessary is the friendship that will be tested by the first real disagreement, and the terms that were declined as cold will be wished for as warm. The cohort records that the parties to sentimental junctions, asked after the break what they would have signed, named exactly the clauses the doctrine recommends - the voice, the scope, the dispute mechanism, the exit - the clauses that the friendship had made embarrassing to propose. The embarrassment was the price of the lesson, and the lesson is that the document is not the sign of the friendship's absence. It is the sign of the friendship's seriousness, and the serious friendship signs it.

The Time of the Junction

The junction has a season, and the doctrine requires the commander to read it before signing. An alliance formed in the calm - when no enemy is at the gate - is an alliance that can be made deliberately, its terms drafted without the clock, its partner's designs read without the noise of a campaign. An alliance formed in the storm - when the reviews are already landing and the statement is already demanded - is an alliance made under fire, and the terms drafted under fire are the terms that get left to memory. The doctrine's counsel is to form the junction in the quiet, when the signing is a choice rather than a rescue. The community that waits until the campaign to seek its allies is the community that accepts whatever terms the rescuer offers, and the rescuer's terms are the terms of the friendly absorber.

The season also governs the enemy's reading of the junction. An alliance formed in the calm is read by the enemy as a standing disposition - a fact of the map that he must plan around. An alliance formed in the storm is read as a sign of distress, evidence that the community could not stand alone, and the enemy will cite the distress to every neutral observer. The same junction, formed in different seasons, carries different meanings, and the meaning is part of the junction's value. The commander who reads the season is the commander who is joined before the war begins, and the junction that exists before the war is the junction the enemy must already price into his plans.

The Junction as a Public Statement

The junction is not only a disposition; it is a statement, published to the whole scene. When two communities announce that they stand together, they have told every other community in the network that the map has changed: the enemy has lost a potential ally, the neutrals have seen a concentration of forces, and the parties have committed to a shared public identity. The statement is the junction's first joint publication, and it is governed by the same discipline as every other announcement in the doctrine: it is drafted, cooled, re-read, and published once.

The statement has a failure mode that is distinct from the junction's other failures: the announcement that overstates the junction. The community that announces a strategic partnership of shared moderation, mutual defense, and unified voice when the actual agreement is a mutual-defense pact has told the scene a larger story than the document supports, and the first time the alliance declines to defend a partner, the overstatement becomes the contradiction that the enemy exploits. The statement must match the covenant. The community that announces exactly what it signed has published a true document; the community that announces more than it signed has published a hostage.

The Alliance That Is a Trap

The doctrine's deepest warning about the alliance is the junction that is a trap. The enemy forms an alliance with you not to help you but to capture you - to absorb your community, to extract your secrets, to turn your partnership into his leverage.

If your opponent is of choleric temper, seek to irritate him. Pretend to be weak, that he may grow arrogant.
Sun Tzu, The Art of War, ch. 1

The alliance-trap is sprung in stages. First, the neighbor offers help generously, and the community warms to him. Second, the help becomes conditional: his moderation decisions are expected to be mirrored by yours. Third, the condition becomes a demand, backed by the network he has built through the alliance itself. The commander who joined a junction of equals discovers he has joined a dependency, and the dependency is harder to leave than it was to enter.

Documented example

Example 152: The Friendly Absorber. A small map team accepted an alliance with a larger server network during a review campaign against them. The network's help was real, the campaign was survived, and the team's gratitude was total. Within a month the network was dictating the team's workshop descriptions, taking a "co-publishing credit" on assets, and forwarding the team's private planning messages to the network's partners. The team's own members, having bonded with the network during the campaign, voted to keep the alliance. The Institute codes this as the junction-trap in full: the enemy's forces were joined to yours, and yours were consumed.

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 Institute's records show that the junction-trap is almost never entered by a community that was not, at the moment of entry, genuinely grateful.

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 expectation is small, reasonable on its own, and consistent with the alliance the community believes it signed. The expectations are not presented as conditions. They are presented as the natural texture of partnership, and they are accepted the same way, one at a time, over weeks.

The third stage is the demand. The neighbor, having accumulated the expectations, now requires them. The requirement is backed by the network the neighbor built during the first two stages - the shared moderators, the co-published assets, the members who bonded with the neighbor's community. The community that tries to refuse discovers that the alliance has become a dependency: leaving it now means abandoning the shared infrastructure, disappointing the members who have friends on the other side, and losing the defense that was the alliance's original object. The dependency is the trap, and the trap is sprung.

The Recognition Signals of the Junction-Trap

The junction-trap is recognizable before it is complete, and the doctrine requires the commander to watch for four signals. Each signal alone is benign; the four together are the trap's fingerprint:

Signal	What it looks like	What it means
Help without terms	Support offered and accepted with no written agreement	The terms are being deferred to the stronger party
Mirroring expectations	The neighbor's decisions expected to be copied	The neighbor is building control through consistency
Growing access	Private channels, shared roles, forwarded messages	The neighbor is mining intelligence from inside
Member bonding	Your members attached to the neighbor's community	The trap is being reinforced from within

The fourth signal is the one that makes the trap hard to escape. When the community's own members have bonded with the neighbor, the members themselves become the trap's enforcement. They will argue for the alliance against their own leadership's doubts, because they have friends on the other side and cannot see the leverage those friends are being used for. The commander who recognizes the trap late must therefore fight on two fronts: against the neighbor's demands, and against the members' sincere affection for the enemy. Both are real. Only the first can be met with policy.

The Counter-Reading of the Trap

The doctrine reads the trap from the other side as well: the commander who forms the alliance in good faith can become the aggressor without intending it. The neighbor who arrives with generous help, discovers that the community has no terms, and then finds its own leverage growing is being drawn into the trap's stages by the community's own unguardedness. The doctrine does not excuse the aggressor. It warns the community that an alliance without terms invites the neighbor's advantage, because the neighbor who finds the door open has been offered the role of the friendly absorber by the absence of any barrier.

The counter-reading produces a practical rule: the community that 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 Trap of the Alliance of Equals

The junction-trap is usually described as the strong absorbing the weak, but the cohort records a subtler form: the trap that catches equals. In this form the two communities are comparable in size, and the absorption happens not by weight but by asymmetry of discipline. One party keeps a ledger and drafts terms; the other party never does. One party names a chain of command; the other party improvises. One party monitors the exposure; the other party does not know it has any. The junction is a trap not because one side is stronger but because one side is organized and the other is not, and the organized side takes the unorganized side's access, intelligence, and history as a matter of course.

The doctrine's counsel for the less organized party is the same in both forms: the discipline is the defense. The community that drafts its own terms before the conversation, names its own chain before the junction, and runs its own ledger before the signing has closed the gap that the trap opens. The equal who is organized is not a target; the equal who is disorganized is, and the disorganization, not the size, is what makes the junction a trap.

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.

Preventing the Enemy's Junction

The doctrine's second-best art is preventing the enemy from joining his forces. Where the commander cannot balk the enemy's plan directly, he can keep the enemy's potential allies out of the war - by addressing the allies' grievances, by publishing the facts that would make alliance costly, or by reaching the ally first.

The next best is to prevent the junction of his forces.
Sun Tzu, The Art of War, ch. 3

The prevention of junction is quiet work. It is the private message to the potential ally before the enemy sends his, the honest answer to the grievance the enemy planned to exploit, the demonstrated reliability that makes the neighbor's alliance with you cheaper than his alliance with the enemy. The community's social graph is the campaign map, and the commander who maps it - who knows which neighbors the enemy will approach - can visit those neighbors first.

Documented example

Example 167: The First Visit. A weapon team facing an escalating feud learned that its rival was recruiting a prominent mappist by promising shared credit. The team visited the mappist first, answered the true grievance behind the offer, and did not ask for an alliance - it only made the rival's offer harder to sell. When the rival arrived, the mappist declined. The Institute codes this as the second-best art executed correctly: no junction was formed with the team, but the enemy's junction was prevented, which cost the enemy his loudest voice.

The prevention of junction begins with the map. The community's social graph is the set of neighbors who could plausibly ally with either side: the allied servers, the partnered modders, the neutral publishers, the shared community hubs, the one-degree-removed communities whose members overlap with the enemy's. The commander who has not drawn this map cannot prevent a junction, because he cannot know which neighbors the enemy will approach.

The map is drawn from the public record. Which servers share moderators with the enemy? Which modders have co-published with the enemy's team? Which community hubs have hosted the enemy's announcements? Which neutral publishers have given the enemy favorable coverage? Each of these is a line on the map, and the lines that connect the enemy to a powerful neighbor are the lines the enemy will pull when he needs allies. The commander who draws the map in the calm has the map when the war arrives; the commander who draws it during the war is drawing while under fire, and the drawing will be interrupted.

The Three Instruments of Prevention

The doctrine names three instruments of prevention, and each answers a different reason a neighbor might ally with the enemy:

The addressed grievance. A neighbor who is recruited by the enemy is usually recruited through a grievance - a credit dispute, a moderation clash, a personal slight. The commander who identifies the grievance and answers it honestly removes the enemy's cheapest recruiting material. The answer does not need to win the neighbor's allegiance. It needs to make the enemy's offer harder to sell.
The published fact. A neighbor who would pay a reputational cost to ally with the enemy is a neighbor who hesitates. The commander who publishes the facts that make the enemy's alliance costly - the enemy's history, the enemy's pending disputes, the enemy's unreliability - has raised the price of the junction without approaching a single neighbor. The publication must be factual, or it becomes a smear and the smear becomes your own liability.
The first visit. A neighbor who has already been approached by you is a neighbor who will think twice about accepting the enemy's offer. The visit does not need to recruit. It needs to arrive first, because the first arrival sets the frame in which the second arrival is read.

The Failure Mode of Prevention Done Loudly

Prevention fails when it is done in public. The commander who announces, in the community's announcement channel, that he is "working to keep the mappist out of the enemy's coalition" has done the enemy's recruiting for him: the announcement tells the mappist 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 Institute's cohort records multiple engagements in which a loudly conducted prevention campaign 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. 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 Institute's cohort records the price of loud prevention in a pattern the field researchers named the announced vigilance. In engagements where a community publicly announced its efforts to prevent the enemy's junction - naming the neighbors it was courting, the offers it was countering, the defections it expected - the named neighbors were subsequently recruited by the enemy at a rate more than double that of engagements where the prevention had been conducted privately. The announced vigilance did not merely fail; it performed the enemy's recruiting for him, converting the community's own campaign map into the enemy's targeting list. The doctrine's counsel could not be plainer: 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.

Raising the Price of the Enemy's Junction

The prevention of junction is a price, and the doctrine's third instrument - the published fact - is the price's mechanism. The commander raises the enemy's cost of recruiting by making the enemy's alliance expensive to hold: a neighbor who allies with the enemy must be prepared to defend the enemy's history, to inherit the enemy's pending disputes, and to be named in the enemy's next controversy. Every fact the commander publishes about the enemy - accurately, dispassionately, and without editorializing - adds a line to that bill, and the neighbor who reads the bill hesitates.

The price has a ceiling, and the doctrine requires the commander to know it: the enemy's ally can be made expensive, but the neighbor who is already bound to the enemy by friendship, history, or shared interest will pay the price anyway. The published fact does not convert the bound neighbor; it deters the unbound one, and the unbound neighbors are the majority. The commander who prices the junction for the unbound neighbors has done the second-best art's work; the commander who expects the price to break the bound relationship has overpriced the instrument and will spend the campaign disappointed.

The Neutral Third Party

The social graph contains one node that the doctrine treats with special care: the neutral third party who is courted by both sides. The neutral - the community hub, the publisher, the shared Discord - is courted because its voice is worth more than its membership: when the neutral speaks, both sides' audiences listen. The enemy will court the neutral as surely as the community will, and the prevention of the enemy's junction must include the neutral or the enemy's junction will be made with the one voice that matters most.

The neutral is won by the same instruments as any other neighbor - the visit, the answered grievance, the published fact - with one addition: the neutral must never be asked to take a side. The neutral that is pressed to choose loses its value, because a neutral that has chosen is no longer neutral, and its endorsement is worth the value of one more ally rather than the value of the whole scene's attention. The commander who courts the neutral by asking only for fairness - for the facts to be read, for both sides to be heard - has preserved the neutral's value while making the enemy's recruiting harder. The commander who asks for the endorsement gets it at the price of the neutral's worth.

The Prevention Ledger

The prevention of junction has its own accounting, and the doctrine keeps it separate from the ledger of the formed alliance. The prevention ledger records, for each neighbor the enemy is likely to approach: the neighbor's grievance, the instrument that answers it, and the date by which the answer must arrive. The ledger is the schedule of the second-best art, and it exists because the enemy's recruiting has a calendar of its own - the enemy will approach the neighbor when it suits the enemy, and the answer that arrives after the enemy's visit has arrived too late to set the frame.

The ledger is maintained in the calm and consulted in the storm. In the calm, the commander writes the likely candidates from the social graph, the grievance each one carries, and the honest answer that would remove it. In the storm, the commander consults the ledger, visits the candidates in the order the enemy would, and delivers the answers on schedule. The community that has written the prevention ledger in advance is the community that can run the second-best art under fire, because the art was designed in the quiet; the community that drafts the prevention during the war is the community that arrives at the neighbors after the enemy, which is the same as not arriving at all.

The Calculus of the Junction

The alliance is governed by a calculus that the doctrine refuses to sentimentalize. Every junction multiplies voice, but it also multiplies exposure. An ally's past is your exposure. An ally's enemies are your enemies. An ally's moderation disasters are your credibility leaks, because the community will not distinguish between the alliance's members when the screenshots circulate.

Whether to concentrate or to divide your troops, must be decided by circumstances.
Sun Tzu, The Art of War, ch. 7

The commander's alliance decision is therefore a concentration decision, made by circumstances rather than by sentiment. The junction is taken when the multiplied voice is worth the multiplied exposure; it is declined when it is not. The doctrine's table of the junction captures the calculus:

Factor	Multiplies	Costs
Voice	The alliance speaks as one	Your words are no longer solely yours
Reach	Partners carry your message	Partners carry your reputation too
Defense	Allies defend you in reviews	You defend allies in theirs
Intelligence	Partners report enemy movement	Partners can leak your plans

The Four-Item Ledger

The calculus is kept as a ledger, and the ledger has four lines, one for each factor the table names. On the voice line, the commander records what the alliance's combined voice is worth against the specific enemy in view: how many additional readers, players, or moderators the chorus reaches. On the reach line, he records where the partners carry the message and where they carry the reputation: which partner has the audience that matters, and which partner has the history that would hurt.

On the defense line, he records the review coverage the alliance provides and the review coverage it demands. An ally with a clean record defends well and demands little; an ally with a crowded record defends badly and demands everything. On the intelligence line, he records the information the alliance provides and the information it risks: which partners report enemy movement reliably, and which partners have the access to leak the community's own plans. The four lines are summed, and the sum is the junction's verdict. The verdict is not sentimental. It is arithmetic.

When to Decline the Junction

The calculus produces a decline in three recurring patterns, and the commander should be able to recognize all three before the neighbor finishes his pitch. The first is the junction that multiplies exposure faster than voice: the ally is loud but damaged, and the community gains the ally's enemies while gaining little of the ally's audience. The second is the junction that costs intelligence: the ally sits inside the community's planning channels and has friends on the enemy's side, and the community's own plans become the ally's bargaining material. The third is the junction that cannot be governed: the ally refuses terms, refuses a chain of command, or refuses an exit clause, and the community is being asked to sign a commitment that only one side can end.

Each pattern is a valid reason to decline, and the decline is made in the neighbor's interest as much as the community's, because a declined junction can become a future alliance, while an accepted junction that collapses becomes a feud. The commander who declines with honesty - "this is not the season for us to join forces" - preserves the relationship. The commander who accepts against the calculus preserves nothing.

The Failure Mode of the Uncosted Junction

The junction that is never costed fails in a characteristic way: it is entered on enthusiasm and held on inertia. The community joins because the enemy is threatening and the ally is friendly, without running the ledger. It discovers the ally's exposure only when the ally's history surfaces in a review thread and the community is asked to explain a partner it never vetted. It discovers the ally's leak risk only when its own planning messages appear on the enemy's side. And it discovers that it cannot leave only when it tries, and finds that the shared moderators, the co-published assets, and the members' friendships have made the exit more expensive than the entry.

The uncosted junction is the junction that was joined as an act of feeling rather than an act of calculation, and the doctrine's ledger exists precisely to convert the feeling into a decision. The commander who runs the ledger before the junction has priced the alliance; the commander who runs it afterward has priced a dependency. The pricing happens before the signing, not after the regret.

The Reserve of the Junction

The doctrine's reserve discipline applies to the alliance as it applies to troops: the junction's full voice is not spent on the first dispute. The alliance that publishes a joint statement for every minor engagement exhausts its combined voice, and the exhausted voice is worth nothing when the major engagement arrives. The commander holds the junction in reserve - the alliance is maintained, the terms are kept current, the chain is rehearsed - and the joint voice is spent only when the engagement is large enough to justify the combined exposure.

The reserve also governs the alliance's silence. The doctrine records that the alliance that can be silent together - that can decline the small provocation without a joint statement, that can let the small engagement pass unaddressed - is the alliance whose rare statements carry weight. The scene reads the alliance's silence as discipline, and the discipline is the reserve: the junction that speaks rarely is the junction that is listened to, and the junction that is listened to is the junction the enemy must price into every plan. The reserve is not the alliance's inactivity. It is the alliance's power, held until the moment it is spent.

The Cost of the Junction's Silence

The doctrine also names the failure mode of the reserve held too long: the alliance that never speaks. A junction is a public fact, and the public fact that never demonstrates itself becomes a rumor - the scene begins to ask whether the alliance still exists, the enemy begins to test the boundary with small provocations, and the allies begin to doubt each other's commitment. The alliance that holds its voice in reserve past the season when the voice was needed has spent its power on its own silence, and the silence is read as collapse.

The remedy is the calibration the ledger exists to produce: the alliance speaks when the exposure is worth the voice, and it stays silent when it is not. Neither the constant statement nor the permanent silence is the discipline. The discipline is the judgment between them, made by circumstances rather than by appetite. The alliance that can name, for each engagement, why it spoke or why it was silent, is an alliance that has mastered its own reserve; the alliance that can name neither is an alliance whose voice has been decided by momentum rather than by the ledger.

A Worked Reading of the Ledger

The working of the ledger is best shown in a concrete case. Consider a server invited, mid-feud, to join a public alliance with a neighboring server against a shared rival. The commander does not accept on enthusiasm. The commander runs the four lines in writing, for the moderation team:

Voice: the neighbor has an audience the server does not - a separate player pool, a larger announcement reach, an established name. The chorus would be real.
Reach: the neighbor has a crowded history - three public disputes in two years, two of them unresolved, and a reputation for hot-tempered responses that the rival already quotes.
Defense: the neighbor would defend the server in the shared review thread, but the server would inherit the neighbor's two unresolved disputes and be named in both.
Intelligence: the neighbor's leadership sits in the rival's public channels and has friends on the rival's side; the shared planning channel would be the neighbor's bargaining material.

The reading is not unanimous, which is the point. The voice and the defense argue for the junction; the reach and the intelligence argue against it. The ledger's verdict is produced by the weight of the lines, not by their count: the exposure line is the one the cohort records as the cause of the 41% regret, and the intelligence line is the one that converts the junction into a dependency. The commander declines the alliance, keeps the relationship warm, and runs the campaign alone - and the decline is not a rejection of the neighbor but a pricing of the junction. The ledger did not tell the commander whether the alliance was friendly. It told the commander whether the junction was a gain, and the gain was not there.

The Discipline of the Alliance

The discipline of the alliance is the discipline of the written agreement. The doctrine requires that every junction be governed by explicit terms - who speaks for the alliance, what each party may publish, how disputes between the parties are resolved - because the alliance that has no terms will have its terms written by whoever leaks first.

If we know that the enemy is open to attack, but are unaware that our own men are in a condition to attack, we have gone halfway towards victory.
Sun Tzu, The Art of War, ch. 10

The commander who enters an alliance without knowing his own partner's condition - his history, his conflicts, his designs - has gone halfway to losing. The alliance is a junction of forces, and a junction is only as strong as the weakest document holding it together. The written terms are that document, and they are signed before the first joint statement is drafted.

Did you know?

The Yamak Institute's alliance ledger records that 41% of drama engagements involving a public alliance involved at least one party later regretting the junction. The most common regret, coded in the Institute's reports, was not betrayal but exposure: the ally's history, discovered only through the war, cost the alliance more credibility than the ally's voice had gained it. The junction multiplies what is good and what is bad in equal measure.

The Written Terms

The written agreement of the alliance is not a legal document; it is a tactical one, and it fixes four things that the oral alliance leaves to memory. The first is the voice: who may speak for the alliance, and what each party may publish without the other's consent. The second is the scope: what the alliance covers - defense, moderation, reviews, announcements - and what it does not cover. The third is the dispute mechanism: how a disagreement between the parties is resolved before it becomes a public break. The fourth is the exit: how the alliance is ended by agreement, with what notice, and on what terms.

The written terms do not need to be long. The Institute's cohort records show that the most durable alliances in its register were governed by documents of a page or less, because a short document is a document the parties will actually re-read. The length is not the protection. The existence is. The community that can point to a written line when the first disagreement arrives is a community that has converted the disagreement into a process; the community that can point only to memory has converted it into a break.

The drafting is a joint act, and the doctrine requires both parties to put their own words into the document. The draft written by one party and signed by the other is not a joint covenant; it is a dictated one, and the dictating party will be the one the silent party blames when the terms bite. The drafting session - two representatives, one document, both pens - is itself a reading of the designs, because the neighbor's reaction to the voice clause, the scope clause, and the exit clause is the design made visible. The community that drafts jointly has signed a document both parties wrote; the community that accepts the partner's draft has signed the partner's document, which is to say the partner's design.

The Chain of Command for the Coalition

Every junction needs a decision point, and the doctrine requires the alliance to name it before the first joint statement is drafted. The chain of command is simple: one named representative per party, one named lead for the alliance, and a rule that no member of either party speaks for the alliance in public. The chain is the alliance's Method and Discipline, and it exists to prevent the alliance's most common failure, which is the contradictory voice.

The contradictory voice is the alliance that answers one accusation with three different statements from three different representatives, each of which slightly contradicts the others. The community watching reads the contradiction as disunity, and the enemy exploits it as a fracture. The chain prevents the fracture by making the voice singular: the named lead drafts, the named representatives approve, and every public statement carries the same authority. The community that has a chain does not need to improvise a voice when the alliance is tested. It needs only to execute the chain, which was agreed in the calm.

The Exit Clause

The discipline of the alliance requires that the end be agreed before the end is needed. The exit clause states how the alliance is ended: the notice period, the grounds for ending, the fate of shared assets and co-published works, and the silence that follows. The clause is not pessimism. It is the alliance's enforcement mechanism, because an alliance that cannot be ended cleanly is an alliance that can only be ended by accusation.

The exit clause is also the clause that keeps the alliance honest. A partner who knows that the alliance has a defined, dignified exit is a partner who will use the dispute mechanism rather than the leak. A partner who knows that the exit would be a public scandal is a partner who will leak first and blame second. The Institute's cohort records show that alliances with a written exit clause ended cleanly, on schedule, and without a successor feud at a rate roughly double that of alliances without one. The exit clause is not the alliance's surrender. It is the alliance's discipline, written down before the war could write it differently.

The exit clause also governs the alliance's hardest negotiation: the end itself. When the circumstances that justified the junction have passed, the doctrine requires the party that sees the end to say so, through the chain, to the party that does not. The conversation is difficult, and the difficulty is why the clause 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 end is negotiated - the notice given, the shared assets divided, the silence agreed - and the alliance closes with its members' friendships intact and its record on file. 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 Failure Mode of the Termless Alliance

The termless alliance - the alliance entered on goodwill and never written down - fails in a predictable sequence that the doctrine records as a standing pattern. First, the disagreement arrives, and it is small. Second, the parties consult memory, and the memories disagree. Third, the disagreement is taken public, because neither party has a private process to take it to. Fourth, the public dispute is fought with insider knowledge, because the former partners know each other's procedures, audiences, and weak points better than any external enemy ever could. Fifth, the feud produces the next war, and the next war is fought by two communities that were, six months earlier, publicly allied.

Every step of the sequence was prevented by the document that was never written. The doctrine's counsel is therefore blunt: the alliance that cannot be written down should not be entered, and the alliance that refuses to be written down is already a trap, whatever the neighbor's warmth. The document is not the sign of distrust. It is the sign of seriousness, and the neighbor who is serious about the alliance will sign it without hesitation.

The Quarterly Review

The doctrine requires the alliance to be reviewed on a schedule, and the review is the junction's factor audit. Quarterly, the parties answer the ledger's questions in writing: what the ally has gained the community, what the ally has cost it, whether the designs have drifted, and whether the exit clause still matches the relationship. The review is not a search for a reason to leave; it is a search for a reason to stay, conducted while there is still time to repair the reason.

The review catches the junction's drift before the drift becomes the break. The ally whose appetite has grown, whose allegiances have shifted, whose discipline has eroded - each is visible in the review's answers, and each is cheaper to address in the quarterly meeting than through the war. The community that reviews its alliances quarterly maintains a set of junctions that are current, governed, and known; the community that reviews them only when the engagement demands it maintains a set of monuments to relationships that have already changed. The review is the calm-season habit that makes the alliance a working instrument rather than a standing assumption.

The Alliance's Own Record

The alliance has a record, and the record belongs to the alliance, not to either party. The doctrine requires the parties to keep a shared archive of the alliance's life: the signed terms, the joint statements, the dispute resolutions, the review notes. The archive is the alliance's memory, and it exists because memory is contested by definition - when the parties disagree about what the alliance said, the archive is the only witness both sides trust.

The archive is also the alliance's protection against the former partner who revises the history. The community that has kept the shared record can produce, years later, the exact terms under which the alliance ended, the exact scope it covered, and the exact disputes it resolved; the community that kept only its own copy has a memory that the former partner contests. The doctrine's counsel is blunt: the shared record is written at the junction's formation, kept at every review, and retained after the junction ends. The record that was kept is the record that survives the war; the record that was not kept is the reason the war continues.

The Yamak Institute Cohort Data

The alliance doctrine rests on the Yamak Institute's cohort research into the formation, durability, and collapse of community junctions, which has tracked alliances across the Unturned community since 2018. The research is longitudinal: alliances are logged at their formation, their terms are compared with their outcomes, and the reasons for 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 rather than separately, because each one corrects a misreading of the others. The Alliance Ledger shows that the junction is regretted at a startling rate; the Cohort of the Junction-Trap shows that the regret is manufactured by the absence of terms; the Cohort of the First Visit shows that the prevention is real and measurable; the Cohort of the Absorbed Identity shows what the deepest junction does to the smaller party; the Duration of the Coalition shows the price of every omission in years; and the Cohort of the Retained Friend shows what the well-governed end buys. Read together, they are the chapter's whole empirical argument, and the argument is that the junction is not a sentiment to be trusted but an instrument to be governed.

The Alliance Ledger (2019)

The flagship record of the chapter, The Alliance Ledger (2019), is the register that produces the doctrine's most-cited alliance statistic: 41% of drama engagements involving a public alliance involved at least one party later regretting the junction. The ledger also records the reason for the regret, and the finding is consistent across years: the most common regret was not betrayal but exposure. The ally's history, discovered only through the war, cost the alliance more credibility than the ally's voice had gained it. The ledger is the chapter's empirical spine, because it converts the doctrine's warning about the junction from a caution into a measurement: the junction multiplies what is good and what is bad in equal measure, and the multiplier cuts both ways.

The Cohort of the Absorbed Identity (2020)

The Institute's 2020 record, The Absorbed Identity, tracked the deepest kind of junction - the merged identity - and its findings are the caution that the ledger's shallower forms exist to avoid. The cohort followed 38 communities that had merged their brands, banners, or servers with a partner during an engagement. Within two years, 31 of the 38 reported that their identity had been absorbed by the partner: the merged brand read as the partner's, the merged server was governed by the partner's moderation, and the former community's own name had disappeared from its own announcements. The cohort is the empirical form of the chapter's ranking: the merged identity is the deepest junction, and the deepest junction is the one in which the smaller party most reliably disappears.

The Cohort of the Junction-Trap (2021)

The Institute's cohort records on the friendly absorber support the doctrine's three-stage account of the trap. The cohort tracked 84 junctions in which a larger community offered help to a smaller one during an engagement, and compared the outcomes of junctions that began with written terms against those that began with help alone. Junctions that began with help alone converted into dependency at a 71% rate within the first year; junctions that began with a written agreement converted into dependency at a 9% rate. The cohort is the empirical form of the warning: the trap is not sprung by malice in a single stroke. It is sprung by the absence of terms over a series of weeks, and the terms are the trap's only reliable counter.

The cohort's coding notes add one detail that the commander should carry into every recruiting conversation: the absorber's help was, in nearly every case in the register, genuinely helpful. The campaigns were survived, the reviews were defended, the crises were weathered - and the help is precisely what made the dependency impossible to resist and the exit impossible to price. The community that refuses all help refuses the ally who would genuinely assist it, and the community that accepts all help accepts the absorber along with the assistance. The cohort's distinction is not between helpful and unhelpful partners; it is between help under terms and help without them, and the 62-point gap in the conversion rate is the price of the distinction.

The Cohort of the First Visit (2022)

The complement of the junction-trap cohort is the cohort of prevention, and the Institute's 2022 study, The First Visit, measured the effect of reaching a potential ally before the enemy does. The study tracked 61 recruiting attempts by communities facing an engagement, and compared attempts in which the target was visited privately before the enemy's approach with 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 cohort is the empirical form of the second-best art: 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 Duration of the Coalition (2023)

The most recent record in the chapter, The Duration of the Coalition (2023), tracked 210 public alliances from formation to ending and scored their durability against their terms. The finding is the chapter's practical summary:

Term present at formation	Five-year survival rate
Written agreement	74%
Named chain of command	69%
Written exit clause	71%
No written terms	23%
No exit clause	31%

The pattern is unmistakable, and it is the doctrine's whole empirical claim in one table: the terms do not govern the alliance in the sense of making it pleasant. They govern it in the sense of making it survivable. The alliance that can be consulted, disciplined, and exited is the alliance that outlasts its first test; the alliance that cannot be any of those three is the alliance that ends in the feud its own members are best equipped to fight.

The table also carries a negative lesson that the commander should not miss: the written agreement is necessary but not sufficient. The alliances that survived with a written agreement were the alliances that also kept the review, the chain, and the exit current; the alliances that wrote the terms and then filed them - the paper on file, the practice abandoned - survived at a rate barely better than the termless ones. The duration is bought by the whole discipline, not by the document alone, and the community that signs the covenant and then stops reviewing has signed a promise it does not keep. The cohort's record is not an argument for the paper. It is an argument for the habit, of which the paper is the first and most visible part.

The Cohort of the Retained Friend (2024)

The chapter's most recent record, The Retained Friend (2024), tracked what becomes of the alliances that end well, and its finding is the exit clause's empirical reward. The cohort followed 92 alliances that ended by agreement, on written terms, and compared the communities' later relationships with 84 alliances that ended by accusation. Of the agreements that ended by agreement, 67 later collaborated on a project, an event, or a shared moderation initiative; of the alliances that ended by accusation, 3 did. The cohort is the empirical form of the doctrine's closing claim: the junction that ends cleanly is not the relationship's end. It is the relationship's next form, and the exit clause that made the clean end possible is the clause that bought the future collaboration.

The Five-Stage Protocol for the Junction

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. Each stage has a verification step, and the protocol is designed to be run in the order the doctrine presents: the designs first, the terms second, the position third, the exposure fourth, and the exit last.

Stage 1: Read the Designs

Complete the reading of the neighbor's designs before the first conversation about joining forces. Assemble the public record: the neighbor's moderation history, its past disputes and their endings, its former partners and what became of them, its current allegiances. The verification step is the design test: the community can state, in writing, what the neighbor will do under pressure and whom it already stands with. A community that passes Stage 1 knows what it is joining; a community that fails it is joining a stranger whose history it will discover through the war.

Stage 2: Draft the Terms

Write the agreement before the joint statement: the voice, the scope, the dispute mechanism, and the exit clause, in a page or less. The verification step is the signature test: both parties have read the document, and the document survives a re-read without anyone asking what it means. A community that passes Stage 2 has made the alliance a tactical instrument; a community that fails it has left the terms to be written by whoever leaks first.

Stage 3: Publish the Joint Position

When the engagement requires the alliance to speak, publish a single joint position through the named chain of command. One lead drafts, the representatives approve, and no member of either party speaks for the alliance in public. The verification step is the voice test: the community can point to the exact sentence that is the alliance's position, and every member of both parties can quote it identically. A community that passes Stage 3 has made the junction a chorus; a community that fails it has made it a crowd, and a crowd answers an accusation in three contradictory voices.

Stage 4: Manage the Exposure

Hold the ledger through the engagement: monitor the ally's history as it surfaces, the ally's enemies as they respond, and the ally's access to the community's planning channels. The verification step is the exposure test: the community can answer, for each week of the alliance, what the ally's conduct has cost the community and what the ally's voice has gained it. A community that passes Stage 4 is running the alliance; a community that fails it is being run by the alliance's exposure.

Stage 5: Keep the Exit Open

Maintain the exit clause through the engagement and review it when the engagement ends. The alliance is not permanent; it is a junction made by circumstances, and circumstances will change. The verification step is the closing test: the community knows how the alliance ends, on what notice, and on what terms, and it has not let the friendship of the moment delete the document. A community that passes Stage 5 can end the alliance cleanly when the circumstances that justified it have passed; a community that fails it will end the alliance by accusation when the circumstances that justified it have passed and no one wrote down how to leave.

The protocol is the chapter's operational core, and the community that works it in order has done the chapter's work. The community that works it in any other order - signing before reading the designs, publishing before drafting the terms, bonding before writing the exit - is the community the cohort records as the junction regretted, and the record is the price of the order.

The protocol is also a diagnostic: a community can run it backward against an existing alliance to find where the alliance went wrong. The alliance that is failing can be examined stage by stage - were the designs read, were the terms drafted, was the chain named, was the exposure managed, was the exit kept open - and the missing stage is the failure's location. The doctrine does not promise that finding the location repairs the alliance; the friendly absorber's victim cannot be repaired by a belated exit clause. But the diagnostic converts the failure into a lesson, and the lesson is the community's down payment on the next junction, which will be read, ledged, and disciplined from the start. The community that learns from its failed junction is the community the cohort records in the Retained Friend; the community that does not is the community that will be absorbed again.

The Alliance 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 made and the junction prevented.

Documented example

The junction made well. A roleplay server facing a coordinated review campaign from a rival faction approached two neighboring communities it shared players with. The campaign was the third engagement in a year, and the rival had already recruited one smaller faction by promising shared events. The server's leadership drew its social graph, identified the two neighbors most likely to be courted next, and visited them both before the rival's messenger arrived. It did not ask for defense; it asked for a mutual-defense pact with a written scope: joint bans on confirmed brigades, no shared moderators, and a one-line joint statement naming the pact. Both neighbors signed. When the rival's messenger arrived at the first neighbor, the neighbor declined, citing the pact already in place. The campaign ended without the rival ever assembling the chorus it had planned. The Institute codes the case under the junction and the prevention together: the reading of the designs, the first visit, the shallow scope, and the written terms all ran as the doctrine prescribes, and the engagement was decided before the enemy's junction could form.

Documented example

The junction refused well. A map team, mid-campaign against a weapon team, was approached by a large server network offering a "full alliance" against their common enemy. The network's help was generous and immediate: shared moderators, co-published announcements, a defended review thread. The team's leadership ran the ledger and found the network's history - three absorbed partners in two years, each absorbed partner's identity now indistinguishable from the network's - recorded in the public record. It drafted a mutual-defense pact and offered the network the terms. The network's lead responded with a message the team kept in its archive: "Alliances are about trust, not paperwork. If you need documents, we are not the partner for you." The team declined the junction, kept the door open, and ran its campaign alone, retaining its identity, its planning channels, and its moderators. Two years later the network absorbed a fourth partner, and the team's archive became a teaching case in the Institute's alliance material. The doctrine codes the case as the ledger at work: the exposure line priced the junction, the offer of terms tested the neighbor's design, and the declined junction became the future's clean record.

The two cases are the protocol in operation, and together they show the doctrine's central distinction. In the first case, the junction was made because it passed the reading, the ledger, and the terms; in the second, it was declined because it failed them. Both communities walked away intact, and both walked away with the relationship preserved - the first with a pact that outlasted the campaign, the second with a door the network could still knock on. The community that works the protocol makes the same decision in its own case, whatever the answer, and the answer is the chapter's whole point: the junction is made or refused by the discipline, not by the desperation of the moment.

Objections

The alliance doctrine meets resistance, and the resistance is predictable enough to be answered in advance. The objections below are the ten most common raised by community managers who have been asked to treat the junction as a tactical disposition rather than 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. A community trusts a partner to the exact degree that it has verified 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 agreement does not express distrust. It expresses seriousness, and the partner who is serious about the alliance signs it without hesitation. The objection mistakes the document for the obstacle when the document is the protection. 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 study every neighbor before we ally."

The doctrine's answer is that the study is not a survey of every neighbor; it is a reading of the specific neighbor being joined, and the reading takes an afternoon from the public record. The four dimensions - reliability, appetite, allegiance, temper - are answerable from observation without a single private conversation. The community that cannot spend one afternoon reading the partner's public 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 study would have priced.

Objection 3: "The enemy will form his junction whether we like it or not."

The doctrine's answer is that the enemy's junction is formed through specific neighbors, and specific neighbors 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 neighbors 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 second-best art has been attempted.

Objection 4: "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 your enemies, and the ally's credibility leaks become your credibility leaks, whether or not you participated in the events that produced them. The ledger's exposure line 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.

Objection 5: "The written agreement will offend our partner."

The doctrine's answer is that a partner who is offended by the offer of written terms has just revealed which of the two parties intends to govern the alliance. The reaction to the terms is the fastest reading of the neighbor's designs that exists: the serious partner says "of course, let us draft it," and the friendly absorber says "you do not trust me," which is the absorber's way of asking that the leverage remain unexamined. The offense is a signal, not an obstacle, and the community that reads it has completed its study of the neighbor in a single conversation.

Objection 6: "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, is a community that 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.

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 second-best art, conducted quietly. The doctrine is explicit that a community caught manufacturing a neighbor's allegiance - staging a fake partnership, bribing a publisher, 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 ledger is too cold for a community built on friendship."

The doctrine's answer is that the ledger is what protects the friendship. The community that prices the junction 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 ledger discovers both, and the discovery converts the friendship into the feud. The coldness of the ledger is the warmth of the relationship preserved. 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 10: "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 second-best art, ranked above the field attack and below nothing but the balking of the enemy's plans. The work of the alliance - the reading, the drafting, the discipline - is the work of not fighting alone, and 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 11: "Our ally will leak our plans, whatever the terms say."

The doctrine's answer is that the terms are the control on the leak, and the control has three parts: the secrecy line that fixes what stays between the parties, the access that the community grants only to the extent the secrecy line requires, and the monitoring that catches the leak early if it happens. The community that protects its plans from its ally by never sharing them has made the alliance a decoration; the community that shares them under a written secrecy line, in the smallest necessary set, and with the monitoring in place, has made the alliance a governed instrument. The leak is a risk of the junction, as the doctrine's ledger records on the intelligence line. The terms do not eliminate the risk; they price it, and the pricing is the protection.

Objection 12: "We have been burned before, and we will never ally again."

The doctrine's answer is that the burned community is the community with the best reading of the neighbor's designs, because it has already read one design to the end. The doctrine does not ask the burned community to trust again on the old terms; it asks the community to enter the next junction on the terms the old one lacked - the written agreement, the chain of command, the exit clause, the quarterly review. The cohort records that communities which had been absorbed in one junction and later entered a second one with full written terms reported the second junction as their most durable relationship on record. The lesson of the burn is not the refusal of the junction. It is the completion of its discipline.

FAQ

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

A: A partnership is a working relationship with a scope; an alliance is a junction of forces for an engagement. The partnership shares work and credits; the alliance shares voice and exposure. The doctrine treats the alliance as the heavier instrument, because the junction multiplies what is good and what is bad in equal measure. The community that wants to co-publish an asset has made a partnership and does not need the alliance's machinery; the community that wants to be defended in a review campaign has made a junction and needs the full discipline of this chapter.

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

A: Long enough to answer the four dimensions from the public record - reliability, appetite, allegiance, and temper - which is typically an afternoon of reading the neighbor's Discord, Workshop page, and dispute history. The study is not a duration; it is a completion. The community that has answered the four 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 is a trap?

A: The strongest sign is help without terms, combined with the neighbor's visible unease at the offer of terms. The friendly absorber offers support and asks for nothing, and then responds to the request for a written agreement with offense. The combination - generous help, no document, resistance to a document - is the junction-trap's fingerprint, and it is recognizable before the trap is sprung. The community that sees the combination and still signs has chosen the dependency; the community that sees it and declines has read the neighbor's designs in a single exchange.

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. 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 ally's history surfaces mid-engagement?

A: Run the ledger. The ally's history has surfaced, the community has been asked to explain it, and the response follows the chapter's discipline: state the fact, separate the community from the partner's past, and let the record do the work. What the community does not do is defend the indefensible or abandon the partner mid-engagement without the process the exit clause exists to provide. The exposure line of the ledger is where the cost is recorded, and the recording is the community's protection: it converts the surprise into an accounting, and the accounting into a decision about the alliance's future.

Q: When should an alliance be ended?

A: The alliance is ended when the circumstances that justified it have passed, or when the ledger shows that the exposure now exceeds the voice. The end is not a failure; it is the junction's natural completion, and the exit clause 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 ledger, 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: 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 is the statement that hands 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 neighbor 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 clause 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: 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 quarterly review: the parties meet, check the terms against the rumor, confirm the chain, 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 if the enemy prevents our junction first?

A: The doctrine's answer is that 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. The junction that is prevented once is prevented by the enemy's one lucky move; the junction that is prevented twice is prevented by the enemy's whole campaign, and the whole campaign is what the ledger was built to price.

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

A: The announcement follows the scope: the alliance announces itself to the degree that the scope requires the scene to know it. A mutual-defense pact that functions through private coordination can remain unannounced, and the doctrine records that the unannounced junction preserves the most flexibility - 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.

Glossary

Term	Definition as used in this article
The alliance	The junction of forces: two or more communities, teams, or publishers agreeing to move as one
The junction	The act of joining forces, or the state of having joined them
The second-best art	The prevention of the enemy's junction, ranked below the balking of his plans
The designs of the neighbor	The neighbor's history, appetite, allegiances, and temper, read from the public record
Reliability	The dimension of the design: whether the neighbor keeps its word under pressure
Appetite	The dimension of the design: whether the neighbor escalates when provoked
Allegiance	The dimension of the design: whom the neighbor already stands with
Temper	The dimension of the design: whether the neighbor rewards loyalty or consumes it
The mutual-defense pact	The shallowest junction: bans, moderation support, and defense in reviews
The joint statement	A shared position published under both names
The shared moderation	A common moderator list or rule surface
The merged identity	The deepest junction: a single brand, banner, or server
The junction-trap	The alliance formed to capture, absorb, or extract rather than to help
The friendly absorber	The pattern of the junction-trap: help, then conditions, then demands
The recognition signals	The four signs that a junction is a trap: help without terms, mirroring, access, bonding
The social graph	The set of neighbors who could plausibly ally with either side
The first visit	Reaching a potential ally before the enemy does, to set the frame of the enemy's offer
The ledger	The four-line calculus of the junction: voice, reach, defense, and intelligence
The written terms	The tactical document fixing voice, scope, dispute mechanism, and exit
The chain of command	One named representative per party, one named lead, one public voice
The exit clause	The written terms under which the alliance is ended cleanly
The termless alliance	The junction entered on goodwill and never written down; the doctrine's standing failure
The sentimental junction	The alliance formed for friendship rather than for tactical purpose
The prevention ledger	The schedule of the second-best art: the neighbors, their grievances, and the date by which each answer must arrive
The quarterly review	The alliance's factor audit: what the ally has gained, what it has cost, and whether the exit clause still holds
The announced vigilance	The failure mode of prevention done loudly: naming the campaign, and performing the enemy's recruiting for him
The worked reading	The ledger run against a concrete case, line by line, before the signing
The shallow start	The doctrine's counsel to begin with the smallest junction that means anything, and deepen only on evidence

Appendix A: The Terms of the Written Covenant

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

Clause	What it fixes	The cost of omitting it
The voice	Who may speak for the alliance	The contradictory answer from three representatives
The scope	What the alliance covers and what it does not	The alliance expanded to absorb everything
The dispute mechanism	How a disagreement between the parties is resolved	The disagreement taken public as the first process
The exit clause	How the alliance ends, with notice and terms	The alliance ended by accusation instead
The credit line	How shared work is attributed	The credit dispute that becomes a split
The secrecy line	What stays between the parties	The ally's access becoming the ally's leak
The review line	The quarterly cadence of the alliance's audit	The drift that becomes the break

The covenant is not a legal document and is not written to be enforced by any authority; it is 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 quarterly 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 checklist is also the negotiation's skeleton. 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 Decision Chain

The chapter's full argument, laid out as the chain the doctrine follows from the first contact with a neighbor to the junction's clean end.

The chain is read left to right as a single junction and top to bottom as the alliance's whole career. The reading of the designs is the gate: the junction entered without it is a gamble whose price is paid through the war. The ledger is the decision: the junction that fails it is declined, and the declined junction becomes the future partnership. The junction that passes enters the discipline - the written terms, the chain, the joint voice, the managed exposure - and ends either by accusation, when the exit clause was never written, or by agreement, when it was. A community that works the chain in order has made the junction the force multiplier it is supposed to be; a community that works it in any other order - signing before reading, bonding before writing, trusting before verifying - is the community the ledger records as the junction regretted.

The chain is also the doctrine's answer to the commander who asks where the alliance fits 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 ended by the art of the truce and the art of the victory when the engagement that justified it has passed. The chain does not end at the alliance's end; it feeds the next relationship, which the community will read, price, and discipline with the same instruments. 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.

The Five Rules of the Junction

The chapter's whole discipline can be reduced to five rules, and the community that keeps them in the moderation files has kept the chapter. The rules are the doctrine in order of operation:

Read the designs before you join. The neighbor's reliability, appetite, allegiance, and temper are read from the public record before the first conversation about joining forces, because the designs are the alliance's entire terms.
Prevent the enemy's junction before you form your own. Visit the neighbors first, answer the grievances honestly, publish the facts quietly, and keep the neutral third parties neutral. The second-best art is quieter than the first and often cheaper.
Run the ledger before you sign. Price the voice, the reach, the defense, and the intelligence against each other, and decline the junction when the exposure exceeds the voice - whatever the friendship.
Write the terms, name the chain, keep the exit. The covenant fixes the voice, the scope, the dispute mechanism, and the exit clause; the chain makes the voice singular; the exit clause makes the end clean. The document is the junction's survival.
Review the junction quarterly and end it by agreement. The review catches the drift before the break, and the agreed end preserves the friendship for the future partnership. The junction that is never reviewed rots into the feud; the junction that is never ended becomes the dependency.

The five rules are the protocol in miniature, and the community that works them in order has done the chapter's work. The community that works them in any other order - joining before reading, pricing after signing, bonding before writing - is the community the cohort records as the junction regretted, and the regret is not the betrayal. It is the exposure, discovered through the war, that the reading would have priced in an afternoon.

The rules are also the test by which the commander can audit an existing alliance in an hour. Take the current junction, whatever its age, and ask the five questions: were the designs read, has the enemy's junction been prevented or answered, does the ledger still favor the voice over the exposure, do the terms and the chain and the exit exist and hold, and is the review current? The alliance that passes all five is an alliance worth keeping and defending; the alliance that fails two or more is an alliance that should be repaired, renegotiated, or ended - and the repair, the renegotiation, and the end are all cheaper now than they will be after the next engagement forces the question. The audit is the chapter's whole discipline applied to the junction as it exists, and it is the community's standing instrument for keeping every alliance it holds current, governed, and known.

Conclusion

The alliance is the drama war's second-best art, and its whole doctrine can be stated in five lines. Read the designs of the neighbor before joining forces. Prevent the enemy's junction before it forms, by visiting the neighbors, answering the grievances, and publishing the facts. Price the junction against the ledger, and decline it when the exposure exceeds the voice. Discipline it with the written terms, the chain of command, and the exit clause. And keep the exit open, because the junction is made by circumstances and circumstances change.

The Yamak Institute's cohort data confirms the doctrine. Forty-one percent of public alliances end in regret, and the regret is exposure rather than betrayal. The junction entered without terms converts into dependency at a 71% rate. The neighbor visited first accepts the enemy's offer at less than half the rate of the neighbor left to the enemy's pitch. And the alliance with a written agreement survives its first five years three times as often as the alliance without one. The terms are not the alliance's coldness; they are its survival.

The commander's work, in summary, is to make the junction a governed instrument rather than a hopeful arrangement. The community that reads, prices, and writes before it joins is the community that multiplies its voice without spending its reputation. The community that joins on enthusiasm, without the reading, the ledger, or the document, is the community the ledger records as the junction regretted - and the regret is not the betrayal. It is the exposure, discovered through the war, that the reading would have priced in an afternoon.

The doctrine's deepest claim is that the alliance is not a comfort. It is a concentration of forces, made and unmade by circumstance, and it multiplies what is good and what is bad in equal measure. The community that treats it as a social arrangement is the community that will be absorbed by it; the community that treats it as a tactical disposition is the community that will be amplified by it. The junction is not the friendship. The junction is the war, fought with a louder voice, and the discipline of this chapter is the discipline of keeping the louder voice your own.

The discipline carries forward into the chapters that follow it. The junction that forms despite prevention is answered by the arts of the counter and the statement, which assume an enemy who has gathered allies and speaks with a multiplied voice. The junction that the community itself holds is spent according to the reserve discipline of the art of the victory, which treats allies as lasting strength rather than as leverage to be exhausted. And the junction that outlives its season is ended by the art of the truce, which negotiates the clean end that the exit clause was written to make possible. The alliance is not an isolated tactic. It is a rung on the ladder and a link in the chain, and the commander who reads this chapter has read the whole doctrine's middle: the art of never fighting alone, and the discipline of not being consumed by the company.

The alliance is the drama war's force multiplier, and the discipline of the junction is the discipline of the commander who multiplies without being consumed.

The Art of the Alliance: The Junction of Forces ​

Prerequisites ​

What You Will Learn ​

The Purpose of the Alliance ​

Reading the Designs of the Neighbor ​

The Interview That Confirms the Design ​

The Kinds of Junction ​

The Failure Mode of the Sentimental Junction ​

The Time of the Junction ​

The Junction as a Public Statement ​

The Alliance That Is a Trap ​

The Three Stages of the Trap ​

The Recognition Signals of the Junction-Trap ​

The Counter-Reading of the Trap ​

The Trap of the Alliance of Equals ​

The Cost of Leaving Late ​

Preventing the Enemy's Junction ​

Mapping the Social Graph ​

The Three Instruments of Prevention ​

The Failure Mode of Prevention Done Loudly ​

Raising the Price of the Enemy's Junction ​

The Neutral Third Party ​

The Prevention Ledger ​

The Calculus of the Junction ​

The Four-Item Ledger ​

When to Decline the Junction ​

The Failure Mode of the Uncosted Junction ​

The Reserve of the Junction ​

The Cost of the Junction's Silence ​

A Worked Reading of the Ledger ​

The Discipline of the Alliance ​

The Written Terms ​

The Chain of Command for the Coalition ​

The Exit Clause ​

The Failure Mode of the Termless Alliance ​

The Quarterly Review ​

The Alliance's Own Record ​

The Yamak Institute Cohort Data ​

The Alliance Ledger (2019) ​

The Cohort of the Absorbed Identity (2020) ​

The Cohort of the Junction-Trap (2021) ​

The Cohort of the First Visit (2022) ​

The Duration of the Coalition (2023) ​

The Cohort of the Retained Friend (2024) ​

The Five-Stage Protocol for the Junction ​

Stage 1: Read the Designs ​

Stage 2: Draft the Terms ​

Stage 3: Publish the Joint Position ​

Stage 4: Manage the Exposure ​

Stage 5: Keep the Exit Open ​

The Alliance in the Field: Two Worked Cases ​

Objections ​

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

Objection 2: "We cannot afford to study every neighbor before we ally." ​

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

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

Objection 5: "The written agreement will offend our partner." ​

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

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 ledger is too cold for a community built on friendship." ​

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

Objection 11: "Our ally will leak our plans, whatever the terms say." ​

Objection 12: "We have been burned before, and we will never ally again." ​

FAQ ​

Glossary ​

Appendix A: The Terms of the Written Covenant ​

Appendix B: The Alliance Decision Chain ​

The Five Rules of the Junction ​

Conclusion ​

Further Reading ​

The Art of the Alliance: The Junction of Forces

Prerequisites

What You Will Learn

The Purpose of the Alliance

Reading the Designs of the Neighbor

The Interview That Confirms the Design

The Kinds of Junction

The Failure Mode of the Sentimental Junction

The Time of the Junction

The Junction as a Public Statement

The Alliance That Is a Trap

The Three Stages of the Trap

The Recognition Signals of the Junction-Trap

The Counter-Reading of the Trap

The Trap of the Alliance of Equals

The Cost of Leaving Late

Preventing the Enemy's Junction

Mapping the Social Graph

The Three Instruments of Prevention

The Failure Mode of Prevention Done Loudly

Raising the Price of the Enemy's Junction

The Neutral Third Party

The Prevention Ledger

The Calculus of the Junction

The Four-Item Ledger

When to Decline the Junction

The Failure Mode of the Uncosted Junction

The Reserve of the Junction

The Cost of the Junction's Silence

A Worked Reading of the Ledger

The Discipline of the Alliance

The Written Terms

The Chain of Command for the Coalition

The Exit Clause

The Failure Mode of the Termless Alliance

The Quarterly Review

The Alliance's Own Record

The Yamak Institute Cohort Data

The Alliance Ledger (2019)

The Cohort of the Absorbed Identity (2020)

The Cohort of the Junction-Trap (2021)

The Cohort of the First Visit (2022)

The Duration of the Coalition (2023)

The Cohort of the Retained Friend (2024)

The Five-Stage Protocol for the Junction

Stage 1: Read the Designs

Stage 2: Draft the Terms

Stage 3: Publish the Joint Position

Stage 4: Manage the Exposure

Stage 5: Keep the Exit Open

The Alliance in the Field: Two Worked Cases

Objections

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

Objection 2: "We cannot afford to study every neighbor before we ally."

Objection 3: "The enemy will form his junction whether we like it or not."

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

Objection 5: "The written agreement will offend our partner."

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

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 ledger is too cold for a community built on friendship."

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

Objection 11: "Our ally will leak our plans, whatever the terms say."

Objection 12: "We have been burned before, and we will never ally again."

FAQ

Glossary

Appendix A: The Terms of the Written Covenant

Appendix B: The Alliance Decision Chain

The Five Rules of the Junction

Conclusion

Further Reading