The Use of Spies

Advanced40-60 minutesCross-platformDiscordSteam Workshop

The thirteenth and final chapter of the doctrine is the chapter of foreknowledge. Every principle of the preceding twelve chapters - the calculation, the disposition, the energy, the targeting, the maneuvering, the reading of signs, the ground, the situations, the fire - depends on one underlying asset: knowledge of the enemy. The community that fights without knowledge fights blind, and no doctrine can correct for blindness. The chapter that closes The Art of War is the chapter that opens all of it: the enemy must be known, and the enemy is known through spies.

This article presents the doctrine of the use of spies: the five classes of spies in the community, the management of the spy system, and the doctrine of foreknowledge that binds the whole discipline together. It draws on the thirteenth chapter of The Art of War and the Yamak Institute's cohort research.

The reader who arrives here from The Attack by Fire will find a change of register. The twelfth chapter handled fire, the most violent instrument the doctrine names, and handled it with rules for when it may be used at all. The thirteenth chapter is not a retreat from that violence into something softer. It is the chapter that makes the violence precise. Fire without foreknowledge burns the hand that carries it; the use of spies is the discipline that lets the community know where the fire is going before it is thrown, and whether it needs to be thrown at all.

A note on the name, so that the reader is not misled about what the doctrine claims. This is a wiki about a game, and community rivalry is not war in any literal sense. The word spy carries a theatrical weight that community life rarely deserves, and the doctrine does not mean cloak-and-dagger. It means something plainer and harder: the sustained, ordinary attention to the opposing community that produces a usable picture of its condition. The member who reads a rival server's announcement channel is a local spy. The moderator who watches a partner's staff turnover is an inward spy. The distinction is a matter of discipline, not of drama, and this chapter treats it accordingly.

A word on the reader's own position, because this is the chapter that most tempts the reader to identify with one end of the instrument or the other. The doctrine is written for the commander - the server owner, the network lead, the moderator who will run the intelligence service. But every principle here has a second reader: the ordinary member who may be asked to report, and who should know what a well-run service asks of them and what it does not. A community that asks its members to watch a rival is asking them to do something this chapter says is a trained and managed function, not an enthusiasm.

The stakes are small and the arena is public: Discord channels, Workshop pages, server browsers, changelogs, moderation actions. The discipline treats the small with the seriousness the large would receive because the cost of community conflict falls on real people and real friendships, and because the habits this chapter teaches - attention, verification, secrecy, restraint - are the same habits that keep a community's ordinary life orderly whether there is an enemy or not.

The chapter's arrangement is worth a moment of attention, because it is itself a piece of the argument. The economics of ignorance come first, to price the chapter's subject. The sources of foreknowledge come second, to exclude the false ones. The five classes come third, as the inventory of the true source. The management of the system comes fourth, because an unmanaged service is worse than none. The converted spy comes fifth, as the hinge on which the whole system turns. And the end and aim come last, to state what all of it is for. This article keeps that order, and adds the sections the doctrine implies: the establishment of the service in practice, the cohort evidence, the staged protocol, and the reference material.

Prerequisites

The reader of this article should already understand the shape of a drama engagement and the surfaces on which the community's intelligence is gathered:

• How to read a rival community's Discord servers, Steam Workshop pages, and server browser listings as surfaces of evidence
• The reading of signs, the observational arm of the doctrine, which this chapter's verification discipline builds on
• The distinction between a report and a conclusion, and the standing possibility that a screenshot or log has been cropped or edited
• The basic vocabulary of the Yamak Institute's cohort research, which this section of the wiki uses as its research body
• A working familiarity with the doctrine of the official statement and the discipline of the need-to-know

What You Will Learn

• The five classes of spies and what each one sees of the enemy
• Why foreknowledge cannot come from rumor, experience, or inference, and where it actually comes from
• The economics of the intelligence service: the 11 days against 47 days, and the 61% price of unverified intelligence
• How to manage the system: the three qualities of the intelligence commander and the verification rule
• How to establish the service in practice, with the picture, the surfaces, and the staged protocol
• How the enemy runs the same five classes against the community, and how the community notices
• The boundaries of the service, and why the discipline protects the community that practices it

The Cost of Ignorance

The chapter opens with the economics of the campaign without intelligence:

Sun Tzu said: Raising a host of a hundred thousand men and marching them great distances entails heavy loss on the people and a drain on the resources of the State.

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

The economics are worth translating into community terms before the doctrine moves on, because every number in this chapter is a community number in disguise. The host of a hundred thousand men is the community's own membership, marching on a campaign the leadership decided without checking whether the membership was willing to march. The heavy loss on the people is the attention spent, the friendships strained, the moderators burned out, the members who leave rather than keep watching the thread. The drain on the resources of the State is the credibility of every future statement, spent on the campaign's claims. A community that enters an engagement without intelligence does not save the cost of intelligence. It pays the same cost, and pays it without the picture that would have made the cost worthwhile.

Hostile armies may face each other for years, striving for the victory which is decided in a single day.

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

Hostile armies may face each other for years, striving for the victory that is decided in a single day - and if the commander remains ignorant of the enemy's condition, they have been miserly in the one matter that matters. The chapter is blunt about the penalty:

One who acts thus is no leader of men, no present help to his sovereign, no master of victory.

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

One who acts thus is no leader of men, no present help to their sovereign, and no master of victory. The community that endures months of conflict without intelligence on the opposing side has spent everything the doctrine has taught it to conserve - and spent it on ignorance.

The years are the real cost, and the community equivalent of years is the grudge that outlives its cause. In the Unturned community, an engagement that begins over a single moderation dispute or a single stolen build rarely stays single. It becomes the feud that a rival server maintains because it no longer remembers not to, the campaign that a mod team replays every time a new member joins, the accusation that gets retold with new screenshots long after the original grievance was settled. Each repetition costs the same thing the first one did - attention, morale, credibility - and the community pays it from a fund that does not grow back. The engagement that is decided in a single day is decided that way only because the commander knew what was coming.

Consider what a single unresolved conflict actually consumes over a year. Every thread about it must be read, and reading it costs the members who read it the mood they had before. Every new accusation must be answered or ignored, and either answer costs the leadership a decision it did not need to make. Every neutral community that watches the feud sees a community that is always in a fight, and the ones it recruits are the ones who find that attractive - a selection that slowly concentrates the community around its own conflict. None of this appears on any budget, and all of it is running continuously. The commander who thinks the feud is costing nothing because no campaign is active has mistaken the campaign for the conflict. The conflict is the standing cost, and it is paid every day.

The community without intelligence pays the standing cost for the standing reason: it cannot tell when the enemy's campaign is coming, so it must treat every sign as a potential campaign, and the effort of perpetual alertness is itself one of the heaviest losses the chapter names. The doctrine's counsel is not that the community should relax its alertness. It is that the community should spend its alertness where it counts, on a maintained picture of the enemy, so that the alertness produces knowledge instead of fatigue. The community that knows the enemy's rhythms can drop its guard when the enemy is quiet and raise it when the enemy's signs turn. The community that does not know the rhythms keeps its guard at full strength forever, and a guard at full strength forever is a guard that will eventually fail, not because the enemy is subtle but because the guard is exhausted.

Did you know?

The Yamak Institute's cohort data records that communities with a standing intelligence posture - a maintained, updated picture of their principal rivals - resolved engagements in an average of 11 days, against 47 days for communities that entered engagements without one. The Institute's 2020 report, Foreknowledge and the Duration of the Engagement, is the cohort's clearest statement of the chapter's economics: intelligence is not a luxury of the campaign. It is the campaign's primary cost saver.

The two figures deserve to be read slowly, because they are the numbers this chapter is built around. The 11 days and the 47 days are both averages across resolved engagements, and the gap is not a curiosity of measurement. It is the price of entering an engagement blind, stated in the only unit communities actually care about: time spent in a conflict nobody wanted. Duration is the cost that multiplies all the others. An engagement that lasts a month costs four times what one that lasts a week costs in attention, and it costs much more than four times in morale, because the members who will leave a month-long feud are not the ones who leave a week-long spat. The community that shortens the engagement by knowing the enemy has not merely saved time. It has saved the people who would have left during the time that was saved.

The failure mode of this section is the belief that intelligence is a luxury that only large communities can afford. The argument sounds practical: a small server cannot maintain a picture of every rival, so it fights blind. The doctrine's answer is that the standing posture does not need to be large to be standing. It needs to be maintained - a file of the principal rivals, refreshed on a schedule, read by someone who owns it. The small community that watches its two or three real rivals with any regularity is better informed than a large network that watches nothing. The scale of the service scales with the number of rivals worth watching, not with the size of the community, and most communities have far fewer rivals worth watching than they believe.

With a standing intelligence posture	Without one
The rival's campaign is known before it publishes	The rival's campaign is discovered at publication
The engagement can be refused or shortened	The engagement is accepted on the rival's timetable
Reports are tested against observable signs	Claims are believed because they are dramatic
Members remain ordinary members	Members are conscripted as improvised soldiers
The campaign ends; the community continues	The campaign ends; the community continues to pay for it

A worked scenario makes the arithmetic concrete. A server network learns, through the ordinary attention of a member who reads a rival's announcement channel, that the rival is assembling a comparison post timed for a weekend when the network's events will be quiet. The network has eleven days' warning under the standing posture's timetable, and uses them: it moves its own event forward, prepares its changelog, and has its answer drafted before the rival's post is finished. The rival's post arrives against a community that is visibly doing things, and the campaign evaporates. Without the standing posture, the same network would have discovered the post at publication, answered it reactively, and spent the following weeks - the full forty-seven days, by the Institute's average - rebutting a claim it could have defused in advance. The difference between the two outcomes is not the network's strength. It is the network's attention.

The cost of ignorance takes a different shape when the community is the defender rather than the aggressor, and the defender's shape is the one that most rewards the intelligence service. A mod team that learns, through a local report, that a rival is preparing a review-bombing campaign against its Workshop page can prepare its own response: a changelog entry, a pinned statement, a head-start on the evidence the campaign would have used. A mod team that learns of the campaign only when the first negative reviews appear is already on the enemy's timetable, and every hour spent reacting is an hour the enemy has already spent planning. The doctrine's rule is that the community which fights its battles from its own calendar wins the ones it does not have to fight at all.

The Sources of Foreknowledge

The chapter states the nature and the source of the foreknowledge that enables everything else:

Thus, what enables the wise sovereign and the good general to strike and conquer, and achieve things beyond the reach of ordinary men, is FOREKNOWLEDGE.

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

What enables the wise sovereign and the good general to strike and conquer, and achieve things beyond the reach of ordinary men, is foreknowledge. The chapter then excludes the false sources:

Now this foreknowledge cannot be elicited from spirits; it cannot be obtained inductively from experience, CHAPTER 14.

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

This foreknowledge cannot be elicited from spirits; it cannot be obtained inductively from experience, nor by any deductive calculation. And it concludes with the true source:

Knowledge of the enemy's dispositions can only be obtained from other men.

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

Hence the use of spies, of whom there are five classes:

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

Knowledge of the enemy's dispositions can only be obtained from other men, and hence the use of spies, of whom there are five classes. The community equivalent of the doctrine is the acknowledgment that no amount of intuition, pattern-matching, or inference can substitute for actual information from inside the opposing community. The enemy is known through the enemy's own people - through the community members, the moderators, and the operatives who can report on the enemy from within.

The three excluded sources are worth examining one at a time, because communities reach for all three constantly and reach for them with the sincere conviction that they are doing intelligence. The first exclusion, spirits, is the community's rumor channel: the "everyone knows" that is nobody's report, the speculation repeated until it has the texture of fact, the mood of a channel taken as a finding. The community that knows what its rival is planning because "it's obvious" is not practicing foreknowledge; it is practicing confidence, and confidence is the cheapest and most dangerous substitute for knowledge. The doctrine's rule is absolute: a claim without a source is not intelligence, and a community that acts on it has acted on rumor and called it knowledge.

The second exclusion, experience, is the pattern that the community has seen before. The commander who has watched one mod team split, one server collapse, one alliance dissolve is tempted to read the next team, server, or alliance as a repetition. Sometimes the pattern holds; more often it does not, because communities are made of different people with different pressures, and the person who reads them as identical is reading their own memories rather than their condition. The doctrine does not forbid experience as a hypothesis. It forbids experience as a source, and the difference is the same difference that separates a hypothesis from a conclusion: the hypothesis is tested, and the conclusion is not.

The third exclusion, deductive calculation, is the reasoning from first principles about what the enemy must be doing. It is the most sophisticated of the three and the most corrosive, because it feels like thought. The commander who reasons that the rival must escalate, because escalation follows provocation, has produced a beautiful argument about a community they have never actually examined. The argument may even be correct. But it is correct by luck, and a service built on luck cannot be a service. All three exclusions fail for the same reason, and the chapter states that reason in a single line: foreknowledge cannot be obtained from any of them, because none of them is another person telling you what the enemy is actually doing.

False source	The community version	Why it fails
Spirits	Rumour, "everyone knows", speculation repeated until it feels like fact	It is mood dressed as information, and mood is not intelligence
Experience	Pattern-matching from a past community or a past grudge	Communities differ; the pattern is rarely the same twice
Calculation	Reasoning from first principles about what the enemy "must" be planning	It reasons from the outside and cannot see the inside

The failure mode of this section is the community that believes it has already done the work. It is the server whose leadership "knows" its rival because it has watched for years, the mod team whose members "know" the other team because they used to be in it, the network whose whole intelligence picture is a set of impressions nobody wrote down. The doctrine's test is simple and uncomfortable: if the community cannot write its picture of the enemy down, and cannot say which person provided each part of it, then it does not have foreknowledge - it has an impression, and impressions are the enemy's favorite thing for the community to have.

The Practical Sources

The doctrine's language - "obtained from other men" - can read as an abstraction, and the community version of it deserves to be made concrete, because the sources are both more ordinary and more numerous than the reader might expect. The other men who know the enemy are, in the Unturned community:

• Current members of the rival community, who report its public mood, its event schedules, its recruitment drives, and its visible disagreements.
• Former members of the rival community, who know its history, its leadership, its past conduct, and the reasons people left - a record the rival's own channels will never publish.
• Partner and allied communities, whose members sit in overlapping circles and notice when the rival begins courting the same partners, courting the same members, or criticizing the same targets.
• The rival's own public output, which is not a person but is produced by people: changelogs, announcement posts, moderation actions, workshop descriptions, and the dates and wording of each, read as a record of intent.
• The community's own members, who were once part of the rival scene or who still have friends there, and who report what they hear in the course of ordinary conversation.

The list matters because it corrects a common misreading of the chapter. The use of spies is not an invitation to infiltration; it is an invitation to attention. Nearly every item on the list is a person the community already has some contact with, reporting on a community it already has some view of. The discipline is in collecting these ordinary reports into a maintained picture, rather than leaving them scattered in the memories of whoever happened to hear them.

A worked failure makes the three exclusions vivid. A server's leadership is certain that a rival network is about to launch a smear campaign, because the rivalry is old, because the last campaign followed a similar provocation, and because "everyone knows" the rival never forgave the last dispute. The certainty rests on experience, on mood, and on inference - the three excluded sources - and nothing in it rests on a report from anyone who has actually seen the rival's plans. The community prepares its defensive campaign, spends its attention, and braces. The rival, it turns out, has spent the same period internally reorganizing its staff and has no campaign in preparation at all. The community's certainty was not intelligence. It was a memory wearing the clothes of knowledge, and the community paid for the outfit in a month of unneeded alertness.

The Five Classes of Spies

The chapter's central classification names the five classes of spies:

Having LOCAL SPIES means employing the services of the inhabitants of a district.

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

Having INW ARD SPIES, making use of officials of the enemy.

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

Having CONVERTED SPIES, getting hold of the enemy's spies and using them for our own purposes.

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

The five classes, translated into the community landscape, are the complete inventory of the intelligence service:

Class	Classical definition	Community equivalent
Local spies	Services of the inhabitants of the country	The opposing community's ordinary members, who report its mood and its movements
Inward spies	Officials of the enemy	The opposing community's moderators and staff, who report its decisions and its deliberations
Converted spies	The enemy's spies, got hold of and used	The opposing side's scouts and operatives, turned and employed against their original master
Doomed spies	Agents given false information, deliberately sacrificed	The operatives fed disinformation, whose exposure convinces the enemy the false information is true
Surviving spies	Those who bring back news from the enemy's camp	The operatives who return with actual intelligence on the enemy's condition

The table is best read as a ladder of access. The local spy stands on the enemy's public ground and reports what is visible to anyone who looks. The inward spy stands inside the enemy's decision process and reports what is decided. The converted spy stands inside the enemy's own intelligence effort and reports the enemy's attempts to learn. The doomed spy carries the community's chosen falsehood and protects the system with it. The surviving spy returns from the enemy's ground with what is actually true. Each class sees a different depth of the enemy, and the doctrine's claim is that a service needs all five depths to work as a system - which is why the chapter refuses to rank them and insists instead that all five be employed together.

Local Spies

The local spy is the enemy's ordinary member, and the community equivalent of "employing the services of the inhabitants of a district" is not recruitment at all in the dramatic sense. It is the cultivation of attention. The local spy is the community's own member who also reads the rival's public channels, the former member of the rival who now belongs to the community and still has friends there, the partner community's member who sits in both servers and notices when the rival's mood shifts. The local spy reports the things that are visible but only noticed by someone who is looking: a recruitment push in a rival's announcement channel, a spike of resignations among its members, a new moderator's appointment, the tone of a thread that signals an approaching campaign.

The local spy is the cheapest class in the system and the most numerous, and the doctrine's counsel is to use the cheapness rather than distrust it. A single local report is a rumor. Ten local reports, gathered by ten people who do not know one another are spies, converging on the same picture, are the beginning of an intelligence service. The discipline of the class is the discipline of aggregation: the commander who collects reports and compares them, who notices when five independent locals say the same thing, is reading the enemy's public condition with a fidelity that no single watcher can manage.

The local class also carries the doctrine's easiest lesson about the value of ground truth: the rival's public mood is not the rival's official line, and the two frequently diverge. An announcement channel may read calm while a general channel churns with a staff dispute; a changelog may read confident while the community behind it is hemorrhaging members. The local spy reports the divergence, and the divergence is often the most valuable single piece of intelligence available - because it is the sign of an internal problem the rival is trying to hide, and an internal problem is the lever every other class will eventually use.

The failure mode of the local spy is the report that tells the commander what the commander already wanted to hear. The local who is close to the community's leadership will unconsciously filter, reporting the rivalry that confirms the campaign and omitting the signs that the enemy is tired of it. The commander who treats the local as a mirror rather than a source will see a flattering picture and act on it. The correction is the same as the correction for every class in this chapter: the report is checked against signs, and a report that flatters is treated as a report that is doing the community no favors.

Inward Spies

The inward spy is the enemy's moderator or staffer, and the community equivalent of "making use of officials of the enemy" is the hardest recruitment the service undertakes, because the inward spy stands inside the enemy's decisions. The inward spy reports what was decided, who decided it, what was argued before the decision, and what the enemy intends to do next. In the Unturned community, inward spies are rarely planted - the doctrine's classical language of "making use" is closer to the truth than any fantasy of infiltration. The inward spy is the former staffer of the rival server who kept their friendships, the moderator who left a network but still sits in a partner's staff channel, the ally who is genuinely loyal to both communities and honest about what each is planning.

The inward spy is the highest-value source in the ordinary service, and the highest-risk one. A single inward report can redirect a campaign; a single disclosure of an inward source can end the source's standing, alarm the enemy, and burn the community's access for years. The doctrine's rule for the class is therefore the rule of distance: the inward spy is protected by how little the enemy knows they are watched by, and the community protects them by never revealing what only an inward source could know. A community that publishes an inward spy's report as its own finding has destroyed its own source to win a single exchange, and the doctrine counts that trade as a loss.

The inward class rewards a specific discipline of interpretation, because the inward spy reports the enemy's decisions as the enemy understood them - and the enemy frequently misunderstands itself. A staffer's account of a planned campaign is a report of what the rival's leadership believes it is going to do, and what a leadership believes it is going to do is not always what it does. The community's correction is the same verification it applies everywhere: the inward report is checked against the enemy's visible preparations, and where the two diverge, the visible preparations win the argument. The inward spy is a window into the enemy's mind, and the doctrine's counsel is to remember that a window shows the room, not the truth about the room.

The failure mode of the inward class is the source who was never actually inward. The staff channel that turns out to be a public channel, the "moderator" who turns out to be a role without power, the ally whose access was revoked months ago - each is a report from a position that no longer exists, and each is believed precisely because it is dramatic. The correction is verification by access: the inward spy's account of the enemy's decision process should match what the enemy's own public conduct later confirms, and a source whose account never matches is a source whose access was never real.

Converted Spies

The converted spy is the enemy's own operative, turned, and the doctrine gives the class a full section of its own below. For the purposes of the inventory, the converted spy is the class that makes the other classes possible: the enemy's scout, detected and employed, becomes the channel through which the enemy is misinformed and the community's own operatives are guided. The converted spy is also the class that carries the system's greatest danger, because the spy who could be turned once can be turned again, and a reconverted spy is the enemy's perfect instrument.

Doomed Spies

The doomed spy is the class that protects the system, and the community equivalent of "agents given false information, deliberately sacrificed" is the engineered leak. The community prepares a piece of false information - a release date that will not be kept, a plan that will not be followed, a division that does not exist - and arranges for the enemy to intercept it. The enemy, trusting its source, adjusts its campaign to the false picture, and the community's real intentions are protected by the enemy's confidence in the falsehood.

The doomed spy in community practice is usually not a person who knows they are doomed. It is the channel that is allowed to leak, the message that is written to be forwarded, the operative whose loyalty is known to be questionable and whose reports are therefore known to be going home. The doctrine's classical language of sacrifice is exact: the doomed spy is spent. The false information, once believed, can never be unspent, and the source that carried it - whether it knows what it carried or not - is burned. The doctrine does not regret the expenditure. It plans for it.

The doomed class is the one the community most often misunderstands, in both directions. Some communities refuse to run a doomed operation at all, on the grounds that it is deception and deception is beneath them; those communities simply accept that the enemy will never be misled and that every engagement will be fought on the enemy's terms. Other communities run the doom carelessly, leaking false information without calibrating it to the enemy's existing beliefs, and the result is a leak that the enemy discounts and a source spent for nothing. The doctrine's counsel is that the doomed operation is neither beneath the community nor automatic. It is a surgical instrument, used rarely, calibrated precisely, and understood by everyone involved to be an expenditure of a source rather than a bargain.

The failure mode of the doomed class is the doom that the enemy does not believe. False information works only when it fits the enemy's existing picture; a doom that contradicts everything the enemy's other sources report will be discounted, and the community will have spent a source for nothing. The discipline of the class is the discipline of plausibility: the false information is built to confirm what the enemy already suspects, not to teach the enemy anything new. A doom that teaches is a doom that fails.

Surviving Spies

The surviving spy is the operative who returns from the enemy's ground with the truth, and the community equivalent of "those who bring back news from the enemy's camp" is the member who returns from an actual engagement with a report of what happened. The surviving spy is the class that closes the loop of the engagement: the member who attended the rival's event and reports its attendance, the moderator who watched the rival's campaign from inside its audience, the operative who was present for the confrontation and can say what was actually said.

The surviving spy's report is the ground truth against which the rest of the system is checked. The local spy reports the mood, the inward spy reports the decision, and the surviving spy reports what happened when the decision met the ground. The class's discipline is the discipline of the eyewitness, which is narrower than it feels: the survivor reports what they saw and heard, not what they conclude, and the commander does the concluding. The failure mode of the class is the survivor who mistakes participation for observation - the operative who was in the middle of the action, and whose report is therefore a report of what it felt like rather than what occurred.

The surviving class deserves more weight than communities usually give it, because it is the only class that measures the doctrine's own claims against reality. The local spy says the rival's morale is high; the surviving spy returns from the rival's event and reports the actual attendance, the actual tone, the actual reaction to the community's last move. The difference between the two reports is the difference between the enemy's picture and the enemy, and the community that tracks that difference over time learns not only about the rival but about the reliability of its own sources - which is the second-most-valuable intelligence the service can hold, after the knowledge of the enemy itself.

The chapter's description of the spy system's unity and secrecy is the doctrine's standard for the whole intelligence service:

When these five kinds of spy are all at work, none can discover the secret system.

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

When these five kinds of spy are all at work, none can discover the secret system. This is called divine manipulation of the threads of the web. The community intelligence service is a system, not a single source: the local spy reports the enemy's public mood, the inward spy reports its private decisions, the converted spy reports the enemy's own intelligence efforts, the doomed spy protects the system with disinformation, and the surviving spy returns with the ground truth. The system's power lies in its totality, and its survival lies in its secrecy - no single operative can reveal a system they cannot see in full.

The secrecy of the system is not a matter of paranoia. It is the system's engineering. A local spy who knows nothing but their own watching cannot reveal the inward network, because they do not know it exists. An inward spy who knows their own channel cannot reveal the doomed operation, because they were never told about it. The doctrine's claim is that the system protects itself structurally, by the compartmentalization of its own parts, and that this protection is more reliable than any promise of loyalty.

Class	What it costs	What it risks	How it fails
Local spies	Nearly nothing; attention only	The enemy notices the watching	Reports flatter the commander's expectations
Inward spies	The source's standing, at risk	The source is disclosed and burned	The source never had the access claimed
Converted spies	The danger of the turn reversing	Reconversion turns a scout into a trap	Trust without probes; the reconverted spy steers
Doomed spies	A source spent, deliberately	The false information is disbelieved	The doom is uncalibrated to the enemy's beliefs
Surviving spies	The operative's own safety in the field	The operative is caught and exposed	Participation is mistaken for observation

Read down the cost column and a shape appears: the doctrine's cheapest classes are also its most expendable, and its most valuable classes are its most dangerous. That is not an accident of the table. It is the chapter's design. The community that wants the high-value classes must accept the high-risk ones, and the community that wants a service without risk will have a service without value - which is to say, a rumor channel wearing the doctrine's vocabulary.

The Enemy's Service in the Community's Own Ranks

The chapter's classification describes the community's own service, but every class in it has a mirror: the enemy runs the same five classes against the community. The doctrine's final claim about the system - that none can discover it when all five kinds are at work - implies its inverse, which is that a system that is discovered is a system whose enemy has done to it exactly what it has done to them. The community that builds an intelligence service must therefore also build the discipline of noticing the enemy's service in its own ranks.

The enemy's local spies are the community's own ordinary members whose loyalties run elsewhere, and they are the hardest class to detect because they behave exactly like members. What distinguishes them is not their conduct as members but their conduct as observers: the questions they ask that a member would not need to ask, the interest they show in operations they are not part of, the way they volunteer for positions that put them near decisions without ever asking for anything for themselves. The detection is not an interrogation of the membership; it is the observation of the same patterns the community's own local spies would use against the enemy.

The enemy's inward spies are the community's own staffers and moderators whose access is being used against it, and this class is both rarer and more dangerous than the local class, because it stands inside the decisions. The signs are the same signs the community's own inward network would rely on: a moderator who reports the content of a private deliberation to a party that had no standing in it, a staffer whose account of a decision is suspiciously well-informed about who argued what, an ally whose advice consistently steers the community toward the course the enemy would prefer. The doctrine's counsel cuts both ways: the community that protects its inward sources must also assume the enemy protects its own, and the same verification discipline that tests the community's reports tests its staff's loyalties.

The enemy's converted spies are the community's own former scouts - members the enemy has already turned, whose reports the enemy now feeds on. The community rarely detects this class at all, because the scout's behavior does not change when the turn happens; the turn is a change of recipient, not a change of conduct. What detects it is the false probe, the same instrument the community uses on its own converted spies: the community feeds a member a piece of information that only the enemy would profit from and watches whether it travels. The probe is the single most reliable detector in the entire discipline, because it requires the enemy to move before the community has to accuse anyone.

The enemy's doomed spies are the community's own channels and members who carry the enemy's false information, and they are not detected so much as recognized: the leak that arrives conveniently, the rumor that confirms the enemy's preferred narrative, the "evidence" that appears exactly when the enemy needs it. The community's correction is the one this chapter has already set down: every report, whatever its source, is tested against observable signs, and a report that serves the enemy's course is treated as serving the enemy's course until proven otherwise. The doomed spy does not need to be caught; it needs to be disbelieved.

The enemy's surviving spies are the community's own operatives returning from the enemy's ground - the members who went to a rival event and came back with a report. The class is the hardest to treat as hostile, because the surviving spy's report is usually true; the enemy's survivors return with genuine knowledge about the community, and the knowledge is accurate. What the community does with that realization is not to distrust its own members but to understand the asymmetry: the community that reads the enemy's survivors accurately has already accepted that its own survivors are being read the same way, and the knowledge each side carries home is a price of the open arena, not a betrayal.

The doctrine's conclusion for counterintelligence is therefore not paranoia but calibration. A community that sees an enemy scout in every curious member will destroy its own openness and its own intelligence gathering at once. A community that assumes no enemy scout exists at all will leak freely and wonder, later, how the enemy always seemed to know. The discipline is the middle course the chapter implies: assume the enemy's service exists, protect the operations it would most profit from knowing, and verify reports against signs - and let the enemy's spies live, because the community's own service is worth the price of the enemy's.

The Community's Knowledge of Itself

The chapter's doctrine is the knowledge of the enemy, but the doctrine that surrounds it - the whole of the thirteen chapters - insists that the enemy and the self are known together, and the intelligence service has a self-directed half that the community overlooks at its own expense. The use of spies is not only the community's eye on the rival. It is also the community's eye on itself.

The first object of the self's knowledge is the community's own balance sheet, which the doctrine elsewhere calls the account of what it can spend. A community at war spends attention, morale, credibility, and people, and the community that knows its own spending power fights differently from the community that discovers its limits only by exceeding them. The intelligence service supplies this knowledge in the same way it supplies the enemy's: by collecting reports, verifying them against signs, and keeping the record. The reports come from the community's own moderators, its own members, its own history of past engagements - and the verification is the same, because a moderator's claim that "the community is behind this" is as unverified as a rival's claim that it plans an attack, until it is checked against what the community is visibly willing to do.

The second object of the self's knowledge is the community's own condition, which is the ground the enemy's local spies read. The community that knows how it looks from outside - its visible mood, its public disagreements, the signals it sends without intending to - is the community that can choose what to show. The doctrine does not counsel deception here; it counsels selection. A community that knows its own weaknesses can decide which of them to expose, and a community that does not know them will expose them anyway, in its conduct, to an enemy that reads that conduct as carefully as the community reads the rival's.

The third object of the self's knowledge is the community's own history of intelligence, which is the record the officer's review habit maintains. Which sources have been right; which reports were believed and failed; which operations succeeded and why; which rival's moves caught the community off guard. The self-knowledge of the service is the record of its own mistakes, and the doctrine treats that record as intelligence in exactly the sense it treats the enemy's: it is gathered, verified, and used. A community that records its own intelligence failures and studies them is a community that stops repeating them; a community that forgets them is a community that pays the 61% figure again, on the same terms.

The doctrine's reason for pairing the two knowledges is that each corrects the other. The community that knows the enemy but not itself will overestimate its own capacity and attack on the enemy's terms. The community that knows itself but not the enemy will prepare endlessly and strike never. The two knowledges together - the rival's condition and the community's own balance sheet - are the picture the service maintains, and the picture is incomplete without either half. The service that watches only outward is an eye without a body; the service that watches only inward is a body without eyes, and both are blind in the way that matters.

The Management of the Spy System

The chapter is explicit about the qualities required to manage spies, and the doctrine reads the passage as the intelligence commander's standard:

Spies cannot be usefully employed without a certain intuitive sagacity.

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

Without subtle ingenuity of mind, one cannot make certain of the truth of their reports.

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

Spies cannot be usefully employed without a certain intuitive sagacity; they cannot be properly managed without benevolence and straightforwardness; and without subtle ingenuity of mind, one cannot make certain of the truth of their reports. The doctrine's requirements are three: the commander must be subtle enough to test the intelligence, benevolent enough to be trusted by the operatives, and ingenious enough to verify what the operatives report. The intelligence that is believed without verification is not intelligence - it is the enemy's disinformation, delivered.

The three requirements are three different kinds of skill, and the doctrine means them as a complete standard for the intelligence commander. The intuitive sagacity is the feel for what is plausible - the commander who has read enough reports to know when a report smells rehearsed, when a source is telling them what they want to hear, when the enemy's pattern has shifted and the report has not caught up. The benevolence is the character that keeps sources willing to report - the commander who protects their sources, who does not burn them for a single exchange, who treats the people who risk their standing as people and not as tools. The subtle ingenuity is the craft of verification - the commander who knows how to test a report, how to set a trap for a liar, how to distinguish the source who is honest from the source who is working the commander's credulity.

Pro tip

The doctrine's verification rule is the most important instrument in the intelligence service: every report from a source is tested against the independent sign-reading discipline of the ninth chapter before it is acted upon. A report that contradicts the observable signs of the opposing camp is presumed to be disinformation until proven otherwise. The Yamak Institute's cohort data records that unverified intelligence was the cause of the worst tactical errors in 61% of the engagements in which a serious error occurred - the acceptance of a single dramatic claim without checking it against the enemy's visible conduct.

The 61% figure is the chapter's empirical warning, and it deserves the same slow reading as the duration figures. Two engagements in three, when something went badly wrong, went wrong because the community acted on a dramatic claim without checking it against what the enemy was visibly doing. The failure is not exotic. It is the moderator who forwards a rumor because it is exciting, the leadership that escalates on a screenshot that confirms its fears, the commander who accepts a source's story because the story is the one the commander wanted. The doctrine's verification rule is the correction: before a report is acted on, it is checked against the observable conduct of the enemy's camp, and a report that contradicts what is visible is presumed to be disinformation until it proves otherwise.

Verification test	What it checks
Does the report contradict observable signs?	If yes, treat it as disinformation until proven otherwise
Can a second, independent source confirm it?	A report that only ever comes from one place is a report about its source
Does the report fit the enemy's plan too conveniently?	Reports that confirm a preferred course of action are doing work
Would the enemy profit from the community believing this?	The question every dramatic claim must answer

The four tests are the practical form of the subtle ingenuity. A report that fails the first test is discarded. A report that fails the second is marked as single-source and weighted accordingly. A report that passes the first three is still treated as a report - valuable, but not the same as a verified finding. The doctrine's counsel is that the community should never be in the position of betting its campaign on a single dramatic claim, because the 61% figure records the price of doing so.

The management of the system is also the management of the sources' trust, and this is where the benevolence operates. A source who reports for a community that protects its sources will keep reporting; a source who reports for a community that burns them will stop, or worse, will begin to report what it thinks will keep them safe. The doctrine's rule is that the commander's first loyalty is to the source's safety, before the value of any single report, because the value of the system is the source's willingness to keep reporting. The community that spends a source to win an exchange has spent its intelligence capital.

The benevolence has a second, less obvious function, which is that it is the commander's only reliable protection against the source who lies to please. A source who reports for a commander they fear will report what the commander wants to hear, because that is what is safe. A source who reports for a commander they trust will report what they actually saw, because they trust the truth to be received as a service rather than as a disappointment. The community that wants honest reports must make honesty safe, and the making of it safe is the benevolence. The commander who wonders why every source's report confirms the plan should ask first whether any source would feel safe contradicting the plan.

A practical question the manager of a spy system must answer is how reports are collected at all, and the doctrine's answer is that the collection should be ordinary. A source is not a spy because they forward a message in a private channel; they are a spy because their reports are used, verified, and kept. The commander who runs the system well makes reporting easy: a known channel, a standing habit of asking, a consistent acknowledgment that a report has been received and what was checked about it. The commander who makes reporting feel like a confession will receive reports only from people who enjoy confessions, which is the wrong source population for intelligence.

A further practical matter is the record. The doctrine's own standard - that foreknowledge must be written down, with each part traceable to a person - requires a file, and the file is the service's memory. The commander who keeps no record of reports, sources, and verifications is running a service that forgets its own history, and a service without a history cannot learn which sources were reliable, which operations worked, or how the enemy has changed. The record does not need to be elaborate; it needs to be maintained. A simple log of reports, sources, dates, and verification notes is the difference between a service that improves and a service that starts over with every engagement.

The chapter's warning on the disclosure of intelligence is absolute:

If a secret piece of news is divulged by a spy before the time is ripe, he must be put to death together with the man to whom the secret was told.

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

If a secret piece of news is divulged by a spy before the time is ripe, the spy must be put to death together with the man to whom the secret was told. The community application is the discipline of the need-to-know: the intelligence operative who shares the operation's purpose beyond the immediate chain destroys the operation, and the commander who gossips about their intelligence destroys their own service. The spy system survives on the secrecy of the system, and the secrecy is the commander's responsibility as much as the spies'.

The punishment in the classical text is the doctrine's way of pricing disclosure, and the community price is the operation itself. An operation that is known to the wrong people at the wrong time is an operation that the enemy can prepare for, and an operation the enemy can prepare for is an operation that should not have been attempted. The community equivalent of the death sentence is not dramatic; it is the end of the operation, the burn of the source, and the lesson to every other source that the community cannot hold a secret. The disclosure destroys more than the information disclosed. It destroys the confidence that the whole system runs on.

The need-to-know discipline is the commander's own standard, and it is the one this chapter holds the commander to most strictly, because the commander is the point at which the system's secrets all converge. The commander who mentions a source in a staff channel, who lets slip a timetable in a casual conversation, who confirms an operation to a moderator who does not need to know, has done the enemy's work for it - not from the enemy's side, but from the community's. The doctrine's rule is that the commander should be able to pass the chapter's own test: every piece of intelligence is known only to the people who need it, and the measure of a commander's discretion is what the commander declines to say.

Role	Knows
The commander	The whole system, and is the only one who does
A source	Its own reporting, and nothing more
The moderation team	What the operation requires them to know, and no more
The membership	That a service exists, or nothing at all

A worked scenario shows the cost of the disclosure. A network's commander shares a source's report with a well-meaning moderator who is not part of the operation, to explain why a decision was made. The moderator, excited, repeats the report in a semi-public channel "as a sign things are going well". The rival, which watches the network's channels as closely as the network watches its own, learns the report and its source. The operation collapses, the source is burned, and the rival - which had been preparing to act on the report's false premise - now knows the premise was false and adjusts its campaign accordingly. The well-meaning moderator meant no harm, and the harm was done. The doctrine does not distinguish between malicious disclosure and careless disclosure, because the enemy does not distinguish either.

The same discipline applies to the community's own sources, who are themselves points of disclosure. A source who knows the community's plans as well as the community does is a source who can be made to reveal them, whether by the enemy's turn, by the enemy's kindness, or by a slip in a conversation. The doctrine's rule is that no source, however trusted, should be able to reconstruct the community's whole picture from what it is told. The source reports what it knows; it does not need to know what the community knows. The commander who explains the full plan to a source to win its loyalty has handed the plan to the enemy at one remove.

Establishing the Service in Practice

The doctrine can read as a system too grand for an ordinary server, and this section exists to answer that reading, because the standing posture the chapter demands is within reach of any community with a moderator team and a few interested members. The establishment of the service is a small, deliberate act, and it has five parts:

1. Name the owner. One person owns the picture - the commander of the intelligence service. The owner does not need to do the watching; they need to collect, verify, and keep the record. A community where nobody owns the picture is a community where everybody has impressions and nobody has intelligence.
2. Name the rivals. A short list of the communities the service actually watches. Most communities have two or three; a few have more. The list is written down, because a rival that is not on the list is a rival that is not watched.
3. Name the sources. The members who are willing to report, and the ground they watch. Sources are not recruited with ceremony; they are the members who already read the rival's channels, and the act of establishment is asking them to report on a schedule and to a channel.
4. Establish the channel. A private channel or a known contact, where reports land. Reports that land nowhere are reports that were never given; the channel is the difference between attention that happens and attention that is collected.
5. Establish the cadence. A regular review - weekly is enough for most communities - where the record is read, reports are verified against signs, and the picture is updated. The cadence is what makes the posture standing; without it, the service is a moment.

The five parts are deliberately small, because the doctrine's claim is that the standing posture fails for want of maintenance, not for want of scale. A server that names an owner, names two rivals, asks three members to report, opens one channel, and reviews once a week has an intelligence service that would satisfy the chapter's economics. The same server with a dramatic ambition - a full network of agents, an elaborate codename system, a channel hierarchy - has a ceremony, and the ceremony will not survive its first boring week.

The single most useful practice in the establishment is the debrief, which is the ritual by which a report becomes intelligence. The debrief is short and its questions are fixed: what did you see or hear; who was there; when did it happen; what does it suggest. The debrief exists because the natural form of a report - "the rival is planning something" - is not a report but a conclusion, and conclusions are the unverified intelligence the 61% figure warns against. The commander who debriefs every report to its facts has done most of the verification work before the report reaches the record.

The Picture of the Enemy

The file the service maintains is not a collection of reports. It is a picture - a set of standing statements about the enemy, updated on the cadence, into which new reports either fit or force a revision. The doctrine's test for a usable picture is that it can answer, in one sentence each, the questions the commander actually needs answered:

Question the picture must answer	What it buys the commander
Who actually decides, and how fast?	The speed of the enemy's response, and whether it can be beaten
What is the enemy's current posture toward the community?	Whether to expect engagement or quiet
What pressures is the enemy under?	The levers the other classes can use, and the rival's likely mood
What has the enemy done before, and how did it end?	The pattern to anticipate, held as hypothesis, not law
What does the enemy believe about the community?	The enemy's picture of the community, and its blind spots

A report that updates one of these rows is a report that matters. A report that fits no row is either a new row waiting to be written or a report that does not yet mean anything. The discipline of the picture is the discipline of revision: a report that contradicts a standing statement is not automatically wrong - it is a prompt to re-examine the statement, and the statement that survives the re-examination is stronger for having been tested. The community that updates its picture honestly is a community whose intelligence improves; the community that updates its picture to protect it is a community whose intelligence is a document of its own assumptions.

The picture is also the community's defense against its own sources, because it is written in the third person. A report about "what the rival is doing" is examined on its merits; a report about "what our contact said" is examined as a testimony. The picture forces the second reading, because it holds the claim at arm's length, labeled by source and date, checkable against the enemy's visible conduct. The community that keeps a picture rather than a collection of anecdotes has given itself the one instrument the doctrine says no rumor channel has: a standard against which every new report is measured, and a record of which sources have been right.

The Surfaces of the Unturned Community

The doctrine's classes read as abstractions until they are mapped onto the actual places an Unturned community gathers its attention, and the mapping is worth doing because the surfaces have their own habits. Each surface favors a class, and a service that knows which class lives where will collect reports from the right places.

The rival's Discord server is the richest surface and the most guarded one. Its public channels - announcements, changelogs, event schedules, general chat - are the ground of the local spy, who reads the mood the rival's leadership would prefer not to broadcast: the complaints in general chat, the resignations in the announcement replies, the tone of the threads when a decision is unpopular. Its staff and partner channels are the ground of the inward spy, who reports what is decided rather than what is announced. And its bot logs and join dates are the ground of a subtler discipline, the reading of member migration - who is joining, who is leaving, and which communities they came from or went to.

The rival's Steam Workshop page is a different kind of surface, because it is public in a way a Discord server is not. Its subscriber counts, its review history, its update cadence, and the timing of its releases are a record the rival cannot easily hide, and the record rewards the local and surviving classes: the local spy reads the reviews and the discussion threads for mood, and the surviving spy reports the actual reception of a release after it lands. The Workshop page is also the surface where the doomed class is most useful, because a release schedule is a thing that can be falsified convincingly - the false release date that the rival schedules against is the classic doom, and it works because the Workshop page is exactly the surface the rival checks.

The server browser is the surface of the movement, and it is the one the doctrine's maneuvering chapter would call the terrain. The rival's server listings - population counts, description changes, the names of events, the uptime - are a live record of its activity and its ambition. A sudden repopulation drive, a rename, a new event series named after a community the rival is courting: each is a sign the local spy reads and the commander files. The server browser is also the surface where the surviving spy returns from: the member who joined a rival's listed server to see it from the inside reports its actual population, its actual tone, and its actual moderation.

The modding side of the community adds two further surfaces that have no exact classical equivalent but reward the same discipline. The first is the repository and the changelog: a mod team's commit history, its release notes, and the timing of its updates are a record of its capacity and its direction, and a team that reads a rival's changelog against the rival's public announcements will catch the divergence between what the rival says and what the rival is building. The second is the shared spaces - the servers, discords, and threads where multiple communities overlap - which are the ground of the converted and inward classes, because the overlapping member sits in both worlds and carries reports between them without ever leaving either.

Surface	Class that reads it	What it reveals
Rival's Discord server	Local and inward spies	Mood, decisions, member migration
Rival's Workshop page	Local and surviving spies	Reception, cadence, release patterns
Server browser	Local and surviving spies	Activity, ambition, repopulation drives
Repositories and changelogs	Local spies	Capacity, direction, the divergence between talk and build
Shared community spaces	Converted and inward spies	The overlap, and the reports that travel through it

The mapping is not a checklist of surfaces to watch; it is a checklist of where the classes already operate, so that the commander can collect what each class is already seeing. The member who reads a rival's Workshop reviews is a local spy who does not know the term; the commander who recognizes the term and collects the report has made the service real without asking anyone to do anything new.

The Converted Spy

The chapter gives the converted spy a position of unique importance, because the converted spy is the enemy's own instrument turned:

It is through the information brought by the converted spy that we are able to acquire and employ local and inward spies.

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

It is through the information brought by the converted spy that we are able to acquire and employ local and inward spies. It is owing to his information, again, that we can cause the doomed spy to carry false tidings to the enemy. And it is by his information that the surviving spy can be used on appointed occasions. The converted spy is the hinge of the entire system: the enemy's own scout, turned, becomes the source through which the enemy is misinformed, the local and inward networks are built, and the surviving operatives are guided. The conversion is the intelligence service's highest-value operation and its most dangerous one, because the converted spy is the operative most likely to be reconverted.

The converted spy's importance follows from the chapter's own claim about the source of foreknowledge. If knowledge of the enemy can only be obtained from other men, then the most valuable other men are the ones who know the enemy best - the enemy's own watchers. The enemy's scout has spent their time studying the community, reporting its condition, learning its habits and its vulnerabilities. When that scout is turned, all of that knowledge is turned with them, and the enemy has not only lost a watcher; it has handed its watcher to the watched. The conversion is the chapter's high point, and the doctrine treats it accordingly: the converted spy is the class that makes the other four classes work, because the converted spy knows both the enemy's plans and the community's own capacity to act on them.

The conversion happens in practice through the detection that precedes it. A community that watches its own ranks as attentively as it watches the enemy will eventually notice the scout: the member who joined quietly, who asks no questions but volunteers no information either, whose account of themselves is thin, whose reports to nobody are somehow always well-informed. The community has two standard options - expose the scout publicly, which confirms the enemy's suspicions and ends the operation, or feed the scout false information, which uses the scout as a channel. The doctrine adds a third option: the scout is detected, and instead of being fed, is turned - offered a reason to work for the community instead of the enemy.

The doctrine does not pretend the turn is easy, because the scout's loyalty is the enemy's existing asset and the community's offer is a new one. The turn succeeds when the scout's reasons for spying were not loyalty but something else: the respect the enemy never gave, the position the enemy never offered, the treatment the enemy reserved for people it could spend. The community that offers the scout what the enemy withheld has made the enemy's own asset its own. The turn fails, or turns back, when the community offers nothing but the same spending it relieved the scout of.

Critical warning

Never place full confidence in a converted spy. The doctrine's own structure implies the vulnerability: the spy who could be turned from the enemy can be turned back, and the converted spy who has been reconverted is the enemy's perfect instrument - one who knows the community's intelligence service and its verification habits. The converted spy is employed with constant cross-checking, never with exclusive access, and never with knowledge of the system's full extent. The reconverted spy is the single most expensive failure available to the community.

The reconversion is the chapter's worst case, and its shape is worth understanding because it is silent. A converted spy who is turned back does not announce it. They continue to report, and their reports continue to be useful - until the reports begin to be useful in the way the enemy wants. The reconverted spy steers the community gently: confirms its suspicions, encourages its escalations, recommends the operation that will cost it most. The community that trusted its converted spy because the turn was genuine has no test that would catch the turn back, unless it built one. The doctrine's answer is that the test must be built, and the danger warning names the parts: constant cross-checking, never exclusive access, and never knowledge of the system's full extent.

Signs of a genuine conversion	Signs of a reconversion
The reports hold up against observable signs	The reports begin to flatter the commander's preferred course
A false probe set for the source stays secret	The false probe appears in the enemy's next move
The source's information costs the enemy real campaigns	The source's information costs the enemy nothing
The source's access survives scrutiny	The source's access begins to look like an invitation

The table is the practical form of the doctrine's distrust. The false probe is the test that matters most: the commander feeds the converted spy a piece of information that only the enemy would benefit from, and watches whether it travels. If it travels, the conversion was never real or has stopped being real, and the source is retired - not confronted, because a reconverted spy who knows they are suspected will simply report the suspicion. If the probe stays secret, the conversion holds for now, and the source continues to be used within the limits the warning names.

The converted spy is also the class that most directly illustrates the doctrine's management standard, because the three qualities - sagacity, benevolence, and ingenuity - all operate on the conversion at once. The sagacity detects the scout and sees the possibility of the turn where a less subtle commander would see only a betrayal to be punished. The benevolence offers the scout a reason to turn, and a genuine one, rather than a threat that would be reported home. The ingenuity verifies the turn continuously, with probes and cross-checks, rather than trusting it because it felt sincere. A conversion attempted without all three qualities fails in three different ways: without sagacity the scout is never detected, without benevolence the scout reports the approach, and without ingenuity the community trusts a reconverted asset until it is too late.

A worked scenario makes the reconversion danger concrete. A mod team turns a rival's scout, and for two months the source's reports are accurate and useful - verified, plausible, costing the rival real advantages. The team, satisfied, begins to relax the discipline: the source is told more, given more access, consulted on plans rather than merely reporting on the rival. In the third month the source's reports begin, imperceptibly, to recommend: a rival weakness that does not exist, an operation that would overextend the team, a division in the rival's ranks that will not be there when the team commits. None of the reports is false enough to fail the observable-signs test outright; each is merely off, in the direction of the team's own ambition. The team commits, and the operation fails on ground the rival was waiting for. The source, having steered gently, is either reconverted or was never converted at all - and the team cannot tell which, because it stopped testing the thing it had built the tests to protect.

The diagram is the chapter in miniature. Foreknowledge feeds the five classes, the five classes feed the secrecy of the system, the secrecy feeds the verification of reports, and verification closes the loop back to foreknowledge - a circle that runs on its own discipline. The strike and the conquest are the circle's purpose, but they are not its engine. The engine is the continuous maintenance of the picture.

Documented Examples

Documented example

In 2022, a faction's intelligence discipline detected a scout from a rival faction operating in its ranks - a member who had joined quietly, attended events, and sent regular reports back to the rival. The faction had two standard options: expose the scout publicly, which would confirm the rival's suspicions and end the operation, or feed the scout information. It chose the second. The faction assigned the scout to channels containing carefully prepared false information about its plans: a fake release schedule, a fabricated internal debate, an invented alliance negotiation. The rival, trusting its scout, adjusted its entire campaign to the false picture - preparing to counter a release that would never come, exploiting a division that did not exist, and building an alliance against a coalition that was never forming. When the real release arrived, unopposed and unanticipated, the rival's campaign collapsed, and the scout, whose reports had been so warmly received, remained embedded and remained believed. The converted spy, managed with verification and deception, had become the hinge of the entire engagement.

Documented example

In 2021, a server network learned that a rival was intercepting its outbound communications with a prospective alliance partner - the rival had planted a member in the partner's staff channels. Rather than sever the channel, the network's commander prepared a doom: a single, plausible, false proposal to the partner, written to be intercepted and repeated back to the rival. The planted member intercepted it and reported the proposal to the rival, who adjusted its counter-offer to undercut terms that were never going to be offered. On the day of the real negotiation, the network presented a completely different proposal; the rival's prepared counter-offer was nonsense against it, and the alliance went to the network. The planted member, whose intercepted intelligence had so faithfully served the rival, was never suspected - the doomed courier had carried the false tidings and, in the classical phrase, the enemy's spies were sacrificed to the system's protection. The false proposal had done its work, and the rival's confidence in its own intelligence was the casualty.

Documented example

A server community maintained no formal intelligence service, only the habit of a few long-time members who read the rival server's public channels as a matter of interest. One such member noticed, over the course of a week, a pattern in the rival's announcements: an unusual number of events scheduled at times that would overlap the community's own, a recruitment push phrased in a way that named no server but clearly targeted members, and a sudden spike of resignations among the rival's moderation staff. The member reported the pattern to leadership as an observation, not a claim. Leadership checked it against the rival's visible conduct, confirmed the pattern with two other independent watchers, and concluded that the rival was preparing a coordinated move - but was itself in the middle of an internal crisis, with its staff resignations unresolved. The community chose not to escalate, moved its own event forward, and let the rival's internal crisis do the work its own campaign had been meant to do. The local report, gathered without drama and verified against signs, had shortened an engagement the community did not even know was coming.

Documented example

A mod team detected a scout from a rival team and turned them, cautiously, on a limited basis - reporting only on the rival's public planning, never granted access to the team's own operations. For two months the source's reports checked out against the rival's conduct. Then the team noticed a change the verification discipline was built to catch: a false probe, fed to the source as a test, appeared in the rival's next public move almost verbatim. The conversion had been reverted at some point the team could not pinpoint, and everything the source had reported since was suspect. The team did not confront the source; it retired them, quietly, and audited every report the source had ever filed, re-verifying each against the rival's conduct. Two reports failed the audit - both of them recommendations, made in the previous month, that would have steered the team into an expensive operation on ground the rival controlled. The reconverted spy had been steering gently, and the verification discipline caught it in time.

Documented example

A server network believed it was about to be attacked. Its own leadership had concluded, from a pattern of rivalry, that a competitor was preparing to poach its members, and it was drafting a preemptive statement accusing the competitor of doing so. A former staffer of the competitor, still on friendly terms with both sides, heard in a private conversation that the competitor had no such plan - its leadership was, in fact, focused entirely on an internal restructuring of its own moderation team, and had barely noticed the network's existence. The former staffer reported this to the network's commander as a single, specific observation: the competitor's leadership was meeting about staff, not about the network. The commander checked the report against the competitor's visible conduct - a flurry of moderator resignations and reappointments, public announcements about the restructuring - and found the signs confirmed it. The preemptive statement was never published, the poaching campaign was never real, and the network had been saved from launching a war on the evidence of its own inference. The inward report had not supplied a plan; it had supplied the absence of one, and the absence was the intelligence that mattered.

Documented example

A mod team's intelligence said a rival was on the verge of collapse: internal reports described staff departures, morale problems, and a planned retreat from the community's main workshop pages. The team prepared to capitalize, timing a release and an announcement to exploit the collapse. A member who had attended the rival's most recent public event returned with a different picture: the rival's event had been well attended, its public channels were calm, and its leadership had announced a new development project with visible confidence. The team's own sources had read the rival's private turbulence and extrapolated a collapse that the rival's public ground did not show. The surviving spy's report was the check the verification discipline demanded, and the team held its planned move. The rival, far from collapsing, released its new project the following month and regained its footing. The surviving spy had not denied the internal reports; they had dated them - the turbulence was real, but the rival was working through it, and the team that had trusted its inward picture instead of its ground truth would have attacked a recovering enemy on its best ground.

Documented example

A server suspected, without proof, that a rival had a member inside it - a suspicion born of a series of operations that had failed exactly when the rival seemed to know too much. Rather than accuse anyone, the commander ran the detection the doctrine prescribes: it fed a single piece of false information - a private plan for an event that would never happen - to a channel that only a small circle could see, and waited. Within a week, the rival announced its counter-event for the date of the false plan. The probe had traveled, and the commander now knew two things it had not known before: that the rival did have a member inside, and that the member had access to the small circle. The commander did not name the suspect. It quietly changed its planning channels, retired the compromised information, and ran a second, narrower probe to learn which part of the circle had leaked. The second probe confirmed it. The community had not caught a spy in an interrogation; it had caught one in a test, and the test had cost it nothing but a false event that was never going to happen.

The Chapter Within the Thirteen

The use of spies closes the doctrine, and its position is worth a moment of its own, because the chapter is not merely the last in the sequence. It is the chapter the other twelve quietly depend on. The thirteenth chapter is placed at the end because it is the foundation of everything that comes before it, and the foundation comes last only because the doctrine wants the reader to feel the dependency rather than be told it.

Chapter	What it needs the spy system for
Laying plans	The calculation of the temple needs the enemy's condition before the estimate begins
Waging war	The economics of the campaign need to know how long the enemy can sustain one
Attack by stratagem	Balking the enemy's plans requires knowing what those plans are
Tactical dispositions	Readiness requires knowing when the enemy is preparing
Energy	The momentum of the onset requires knowing where the enemy is weakest
Weak points and strong	The choice of the field requires knowing the enemy's disposition
Maneuvering	The circuitous route requires knowing the ground the enemy holds
The nine variations	The adaptation requires knowing which situation the enemy is in
The march	The reading of signs is itself a form of intelligence, the doctrine's observational arm
Terrain	The choice of ground requires knowing what the enemy can hold
The nine situations	The decision to fight requires knowing whether the enemy is cornered
The attack by fire	The aim of the fire requires knowing where the enemy's material actually is

The table is the chapter's argument made structural. Every principle the doctrine has taught is an instruction to act, and every instruction to act presumes that the community knows enough to act correctly. The spy system is what supplies that presumption. The thirteen chapters are therefore not thirteen independent arts; they are one art with twelve applications and one supply line, and the supply line is the use of spies.

The reader will notice that the march chapter appears in the table as the doctrine's observational arm, and the point is worth making explicit, because it explains the relationship between the ninth chapter's reading of signs and the thirteenth chapter's use of spies. The reading of signs is intelligence gathered from the enemy's conduct without the enemy's cooperation - the sudden movement, the change of tone, the shift in the enemy's visible posture. The use of spies is intelligence gathered from the enemy's people. The two are complements, and the doctrine's full intelligence posture runs both at once: the signs tell the commander what the enemy is doing, and the spies tell the commander what the enemy intends, which the signs cannot show. A community that watches the enemy's conduct but has no sources sees the enemy's shadow. A community that trusts its sources but ignores the enemy's conduct is blind to the shadow the enemy's sources are casting over it.

The placement of the chapter also explains the doctrine's closing claim: that the spy system is safe only in the hands of the enlightened ruler and the wise general. A foundation underlies everything, and a foundation that is misused undermines everything. The community that builds a spy system without the discipline to run it has not added an instrument to its doctrine; it has added a liability to every instrument it already has. The doctrine's order - the discipline first, the system second - is therefore not a sequence of convenience. It is the condition under which the foundation is a foundation instead of a collapse.

The Boundaries of the Intelligence Service

A chapter on the use of spies owes the reader a statement of what it does not recommend, because the doctrine's own discipline has limits and a community that ignores them will pay for the ignoring. The intelligence this chapter describes is gathered from the enemy's public and semi-public conduct: its announcement channels, its changelogs, its moderation actions, its staff turnover, the reports of people who sit in its spaces. None of it requires breaking into a private staff channel, coercing a member to leak, or exploiting a confession. The doctrine's methods are attention and verification, and the first boundary of the service is that these are the only methods it has.

The second boundary is the community's own standards. The doctrine does not ask a community to behave badly toward the enemy, because a community that behaves badly toward the enemy is a community whose members learn that bad behavior is acceptable - and they will learn it just as well when the behavior is directed at one another. The community that wins an engagement by coercion or betrayal has taught its own membership a lesson about coercion and betrayal, and that lesson is a cost the balance sheet records on the wrong side.

The third boundary is the platforms themselves. Discord's terms and Steam Workshop's terms govern what a community may do, and an intelligence service that breaks them - by obtaining private information, by operating accounts that violate the platform's rules, by exploiting a vulnerability in how the platform shares information - is an operation that can end the community's standing with the platform altogether. The doctrine's counsel is blunt: an intelligence gain obtained by risking the community's platform standing is a gain that costs more than it is worth, because the community that is banned from its own platform has lost the war it was spying to win.

Boundary	The forbidden method	The allowed alternative
The service's own methods	Breaking into private channels, coercing leaks, exploiting confessions	Reading public and semi-public conduct, gathering reports from willing sources
The community's standards	Winning an engagement by betrayal or coercion	Winning by better information and better preparation
The platforms' rules	Obtaining private data, evading platform terms	What is openly available and lawfully shared

The doctrine's position is not that the community should be naive about the enemy. It is that the community should be honest about itself. A community that relies on a forbidden method has made a trade it does not get to inspect the terms of: it has spent its own character, its members' trust, and possibly its platform standing to obtain an advantage it could have obtained, more slowly but more safely, through the discipline this chapter has already taught. The intelligence service is a long game, and a long game is lost in a single expedient moment.

The Yamak Institute Cohort Data

The research that carries this chapter is the Yamak Institute's longitudinal cohort, and the reader who wants to weigh the doctrine should know what the cohort actually contains. The cohort has tracked more than 1,800 documented drama engagements across the Unturned community since 2018, coding each engagement against a fixed protocol, and the studies below are the ones this chapter draws on, in the form the Institute published them.

2020 - Foreknowledge and the Duration of the Engagement

This report is the chapter's economics in its most direct form. It compared engagements entered with a standing intelligence posture against engagements entered without one, and recorded the two figures this article is built around: resolved engagements averaged 11 days for the prepared communities, against 47 days for the unprepared. The report's secondary finding was that the duration gap held across all engagement types and across communities of every size, which the Institute's analysts read as evidence that the intelligence posture, and not the community's scale, was the variable doing the work.

2021 - The Longitudinal Cohort Study of Developer Drama and Community Warfare

The cohort's flagship study, this report established the cohort's core method and recorded the figure that anchors this chapter's verification discipline: unverified intelligence was the cause of the worst tactical errors in 61% of the engagements in which a serious error occurred. The study also recorded the first systematic coding of the community intelligence service, noting which communities maintained a picture, which ran reports through a verification step, and which acted on dramatic claims directly - and the difference in outcomes between the three is the cohort's strongest statement of the management standard.

2023 - The Astana Longitudinal Engagement Archive

This archive extended the cohort into the deeper record of the community's engagements, and its published summary records the figure this chapter returns to at its close: communities applying the thirteen-chapter doctrine in sequence, with a maintained intelligence service, produced favorable engagement outcomes at a 71.4% rate against 38.2% for communities without the discipline. The archive is also the source of the cohort's field notes on the documented examples in this article, which were recorded by the Institute's field researchers in the communities concerned.

2024 - The Verification Study

This study isolated the verification rule from the rest of the management standard, coding engagements by whether reports were checked against observable signs before action. The study recorded that communities which ran the verification step before acting on a report resolved their engagements with serious errors at a fraction of the rate of communities which acted on the report directly, and its analysts described the finding as the empirical form of the chapter's central warning: the report is checked, or the report checks the community.

What the Cohort Does Not Measure

The cohort has limits, and the doctrine is better served by stating them. The cohort codes engagements after the fact, from the public record and the Institute's field notes, and it cannot measure the quality of the intelligence that was never acted on, or the intelligence that was acted on and succeeded quietly. The cohort's outcomes are coded as favorable or unfavorable for the initiating or responding community, which is a blunt measure of a contest that often has no clean winner. And the cohort is drawn from a single game's community, so its figures describe the Unturned ecosystem and cannot be assumed to transfer elsewhere. The reader who quotes the cohort should quote it with its limits attached.

The Intelligence Service in Practice

The doctrine is not complete until it tells a community manager what to actually do, and this section provides the staged protocol by which the intelligence service is established and run. The protocol runs from the naming of the owner to the after-action review of an engagement, and each stage is executable by a server owner or network lead with no special training beyond the discipline this chapter has set out.

Stage 1 - Name the Owner

The first stage is the naming of the intelligence commander: the person who owns the picture of the enemy, collects the reports, runs the debriefs, and maintains the record. The owner does not need to do the watching; they need to collect, verify, and keep. A community that names its owner deliberately has begun the service; a community that lets the picture be owned by whoever happens to care most has a service that will change hands with the mood.

Stage 2 - Name the Rivals and the Sources

The second stage is the naming of the rivals worth watching and the sources who watch them. The rivals are a short written list - most communities have two or three - and the sources are the members who already read those rivals' channels, asked to report on a schedule and to a channel. The act of establishment is the asking, not the recruitment; the sources already exist, and the stage makes their reporting deliberate.

Stage 3 - Open the Channel and the Cadence

The third stage is the establishment of the service's machinery: a private channel where reports land, and a regular review - weekly is enough for most communities - where the record is read, reports are verified against signs, and the picture is updated. The channel is the difference between attention that happens and attention that is collected; the cadence is the difference between a service and a moment.

Stage 4 - Run the Verification

The fourth stage is the discipline of the running service: every report is debriefed to its facts, tested against the four verification questions, and marked by source and date in the record. Reports that contradict observable signs are presumed to be disinformation until proven otherwise; reports that cannot be confirmed are marked single-source; and the commander protects the sources and holds the secrets in the measure this chapter has set down.

Stage 5 - Review the Service

The fifth stage is the after-action review, which closes the loop. The community reviews its picture against the engagement's outcome: which sources were right, which reports were believed and failed, which classes were thin, which rival has changed. The review is written down, because the service that records its own mistakes is a service that stops repeating them, and the review is the difference between a service that improves and a service that starts over with every engagement.

Objections

A chapter this explicit about its methods will meet objections, and the doctrine is better served by answering them than by ignoring them, because a community that rejects the chapter on a misunderstanding will fight without the service it needed. Each objection below is a real position a sceptical reader would take, answered in the doctrine's own voice.

"Spying is wrong."

The first objection is moral, and the doctrine's answer is the one this chapter has already given: the intelligence this doctrine describes is gathered from the enemy's public and semi-public conduct, from reports people choose to give, and from attention any member could pay. It does not require breaking trust, invading privacy, or deceiving the community's own members. What the objection usually means is that communities should not behave badly toward rivals, and on that the doctrine agrees completely - which is why the boundaries section exists. The disagreement is only about the word. The attention the doctrine calls a spy system, the community already practices unplanned; the doctrine asks only that it be made deliberate, verifiable, and safe.

"We do not need it; we know our rivals."

The second objection is the confidence the sources-of-foreknowledge section already answered. Knowing a rival through years of shared history is experience, and the chapter has excluded experience as a source. The community that knows its rival's history but not its current condition, its present leadership, its active plans, or its immediate pressures is a community that knows a ghost. The service is not a replacement for the community's accumulated knowledge; it is the discipline that keeps that knowledge current, which is the only form of knowledge that can be acted on.

"We do not want to become the kind of community that runs a spy service."

The third objection is about identity, and it is the most serious, because it is not wrong about the danger. A community that runs an intelligence service badly - that trusts without verification, spends its sources, publishes its findings, and lets the service corrupt its character - has become the kind of community the objector fears. The doctrine's answer is not that the objector is mistaken about the danger. It is that the discipline this chapter teaches is precisely what prevents the danger, and that the community which refuses to run a service deliberately will still be watched by one - the enemy's. The choice is not between having intelligence and not having it. It is between running the service within the boundaries and being the subject of one that is not.

"The enemy does not deserve to be watched."

The fourth objection is about the enemy, and the doctrine's answer is that the enemy's condition is a fact, and facts do not depend on the enemy's worthiness. A rival community is under its own pressures, staffed by its own people, making its own plans, and the community's decision process cannot decide well about a subject it refuses to study. The knowledge is not a reward the enemy earns; it is information the community's own judgment requires. The commander who refuses to learn about the enemy because the enemy is unworthy has not protected anyone's virtue. They have simply declined to use the information that would have let the community decide in its own favor.

"Intelligence will make us paranoid."

The fifth objection is about the service's effect on the community, and the doctrine's answer is that the effect is a matter of the service's discipline, not its existence. A service that trusts without verification, that treats every rumor as a finding, and that lets the enemy's provocations confirm its fears is a service that manufactures paranoia. A service that verifies, marks single-source reports, and tests dramatic claims against observable signs is a service that reduces paranoia, because it gives the community a standard against which its fears can be measured. The doctrine's counsel is that the community which fears the paranoia should fear the unverified service, not the verified one - the discipline is the cure for the disease the objection names.

"The enemy can do it to us, so we should not do it to them."

The sixth objection is the mirror of the identity objection, and the doctrine's answer is that the refusal does not protect the community from the enemy's service; it protects the community from its own discipline. The enemy's service operates whether the community runs one or not, and the community that refuses the service in the name of fairness has declined the intelligence that its own judgment requires while the enemy keeps collecting it. The doctrine does not ask the community to imitate the enemy; it asks the community to know the enemy, and the knowing is not an imitation of the enemy's conduct but the discipline of the community's own attention.

"The enemy's condition is too small to matter."

The seventh objection is that a rival community's internal state is trivia, and the doctrine's answer is the chapter's own arithmetic: the small is the sign of the large, and the engagement that is decided in a single day is decided by the condition that was known before it. The rival's staff turnover, its recruitment drive, its announcement tone - each is a small fact that the classes gather, and each is a sign of the campaign the rival is or is not preparing. The community that dismisses the small as trivia has dismissed the very surface where the enemy's intentions are written, and the dismissal is the price the duration figures record.

"Our members will not want to report."

The eighth objection is about the sources, and the doctrine's answer is the practical sources list: the members who will report are already watching, and the act of establishment is asking them to report on a schedule rather than recruiting them for drama. A community that asks its members to watch a rival is asking them to do something this chapter says is a trained and managed function, not an enthusiasm - and the members who already read the rival's channels are the members who will report once the channel and the cadence exist. The community that believes no one will report has usually never asked.

"We cannot keep secrets."

The ninth objection is the most honest, and the doctrine's answer is the compartmentalization the chapter teaches. A community that cannot keep secrets at all should not run a service whose survival depends on secrecy - but the chapter's answer is that the service's secrecy is structural, not personal: the local spy does not know the inward network, the inward spy does not know the doomed operation, and the commander is the only one who knows the whole. The system protects itself by what its parts do not know, and the community that believes it cannot keep secrets has misread the chapter, which does not ask the community to keep secrets; it asks the system to be built so that no one but the commander has them to keep.

"The service is too much work for a game."

The tenth objection is the standing posture's whole challenge, and the doctrine's answer is the five parts of the establishment: an owner, two rivals, three sources, one channel, one review a week. That is the whole of the standing posture, and it is an hour a week in most communities. The work the objection fears is the work of the unmanaged service - the drama that an unmanaged service does nothing to prevent, and that the managed service prevents at the price of the hour. The doctrine's counsel is that the community weigh the hour against the 47 days, and that the weighing settle the objection.

FAQ

Is the use of spies just spying on people? No. The intelligence this chapter describes is gathered from the enemy's public and semi-public conduct, from reports people choose to give, and from attention any member could pay. The doctrine's boundaries exclude breaking into private channels, coercing leaks, and exploiting confessions; the service is attention and verification, and the community that runs it within the boundaries is practicing the discipline this chapter teaches.

What is the single most important rule of the service? The verification rule: every report is checked against observable signs before it is acted on, and a report that contradicts what is visible is presumed to be disinformation until proven otherwise. The cohort records the price of ignoring the rule at 61% of serious errors, and the whole management standard is built around it.

How many spies does a community need? As many sources as its real rivals require, and most communities have two or three rivals worth watching. The doctrine does not count the sources; it counts the picture, and a picture maintained by three members reading two rivals is a service, while a ceremony maintained by twenty operatives is a theater.

Can a community run the service without anyone knowing? The service is run with the need-to-know discipline: the membership knows that a service exists, or nothing at all, and only the commander knows the whole. The service is not a secret from the community's leadership - the owner is named and the owner answers to the commander - but its parts are compartmentalized, and no one but the owner carries the whole.

What does the community do with a report it cannot verify? It marks the report single-source, weights it accordingly, and never bets the campaign on it. The four verification tests are the discipline's answer: a report that cannot be confirmed is a report about its source, and the community that acts on it has acted on the source's account rather than on the enemy's condition.

Is the converted spy a real practice in the community? It is the doctrine's highest-value operation, and its real form is the detection of the enemy's scout and the offer of a reason to turn. The community rarely converts a spy in the dramatic sense; it more often turns a scout it has detected, or feeds one false information, and the converted spy is employed with constant cross-checking because the reconverted spy is the system's most expensive failure.

How does the community protect its sources? By the benevolence of the management standard: the source's safety comes before the value of any single report, the source is never burned for a single exchange, and the community never reveals what only an inward source could know. A community that protects its sources has a pipeline that refills itself; a community that burns them has a pipeline that dries up.

What is the difference between the local spy and the ordinary member? The local spy is the ordinary member who reports on a schedule, to a channel, whose reports are debriefed, verified, and kept. The difference is not the watching - both watch - but the collection. The ordinary member's attention happens; the local spy's attention is collected, and the collection is the whole of the service.

Does the intelligence service apply to a community that does not expect to fight? It applies to every community that maintains a public surface, because every such community is watched by its rivals and will one day face an engagement. The standing posture is maintained in peacetime because peacetime is when the enemy's habits are visible and the community has the attention to spare - and the community that builds the service before it needs it is the community that has the service when the engagement arrives.

What is the single most common failure of community intelligence? The acceptance of a single dramatic claim without checking it against the enemy's visible conduct. The cohort records the failure at 61% of serious errors, and the doctrine's whole verification discipline exists to correct it. The failure is not exotic; it is the moderator who forwards the exciting rumor, the leadership that escalates on the confirming screenshot, and the commander who accepts the story because it is the one the community wanted.

Glossary

The terms of art used throughout this article are collected here, so that the community manager can reference the doctrine without re-reading the whole:

• Foreknowledge - Knowledge of the enemy obtained from other people, the foundation of every other principle in the doctrine.
• The five classes of spies - Local, inward, converted, doomed, and surviving spies, the complete inventory of the intelligence service.
• The local spy - The enemy's ordinary member, who reports its public mood and movement.
• The inward spy - The enemy's moderator or staffer, who reports its decisions and deliberations.
• The converted spy - The enemy's operative, detected and turned, the hinge of the system.
• The doomed spy - The carrier of engineered disinformation, spent deliberately to mislead the enemy.
• The surviving spy - The operative who returns from the enemy's ground with the ground truth.
• The picture - The service's maintained file of standing statements about the enemy, updated on the cadence.
• The verification rule - The discipline that every report is checked against observable signs before it is acted on.
• The false probe - The test by which a suspected source is fed information only the enemy would profit from, to see whether it travels.
• The need-to-know - The discipline of disclosure: every piece of intelligence is known only to the people who need it.
• The debrief - The ritual by which a report becomes intelligence: what was seen, who was there, when, and what it suggests.
• The standing posture - The maintained intelligence service that exists in peacetime, refreshed on a schedule.
• The boundaries - The limits of the service: its own methods, the community's standards, and the platforms' rules.

Appendix A - The Five Classes

The five classes are the inventory of the service, and this appendix sets them out with what each one costs, what it sees, and how it fails, for the commander who needs the whole classification on one surface:

Class	Sees	Costs	Fails when
Local	The enemy's public mood and movement	Attention only	Reports flatter the commander's expectations
Inward	The enemy's decisions and deliberations	The source's standing	The source never had the access claimed
Converted	The enemy's intelligence effort, turned	The danger of reconversion	Trust without probes; the reconverted spy steers
Doomed	Carries the falsehood that protects the system	A source spent, deliberately	The doom is uncalibrated to the enemy's beliefs
Surviving	The ground truth of the enemy's condition	The operative's safety in the field	Participation is mistaken for observation

The table is the classification's practical form, and the reader who wants the full development of each class should read the sections above. The doctrine's counsel is that the community which keeps this table beside its picture of the enemy has the whole inventory in hand, and the inventory is the completeness requirement: a service with only local spies reads the mood but not the decisions, and a service with all five reads the enemy whole.

Appendix B - The Boundaries and the Lifecycle

The service is governed by two further disciplines, and this appendix sets them out as checklists, because both are the kind of thing a community applies in the moment and forgets in the peace:

The boundaries checklist. The service operates only within its limits, and the community asks of every method: does it gather public or semi-public conduct, or does it break into private ground? Does it use willing reports, or does it coerce and exploit? Does it respect the platforms' rules, or does it risk the community's standing? A method that fails any of the three questions is not intelligence; it is a trade the community does not get to inspect the terms of.

The source lifecycle. A source is found (the member who already watches), used (reports collected, debriefed, verified, protected), checked (reports measured against the enemy's visible conduct, continuously), and retired (thanked, protected, never burned). The community that runs the lifecycle well has a pipeline that refills itself; the community that burns its sources has a pipeline that dries up, and its intelligence dies not of enemy action but of its own.

The two checklists are the doctrine's practical boundaries: the first keeps the service honest, and the second keeps it alive. The community that holds both, and the five classes, and the management standard, and the verification rule, has the chapter whole.

The Officer Who Runs the Service

The management section established the three qualities the chapter requires of the intelligence commander - sagacity, benevolence, and ingenuity - and this section draws them together into a portrait of the officer, because the qualities are exercised by a person, and the person is the service.

The officer's first habit is ownership. The officer owns the picture of the enemy, which means the officer reads the reports, maintains the file, runs the debriefs, and notices when the picture has gone stale. The officer does not need to be the community's best watcher; the officer needs to be the one who collects the watching. A service whose officer treats the picture as a committee product is a service whose picture is no one's responsibility, and a picture that is no one's responsibility is a picture that nobody updates.

The officer's second habit is calibration. The officer holds the reports at their right weight - the single-source report marked as such, the verified report weighted accordingly, the dramatic claim held at a discount until the signs confirm it. Calibration is the practical form of the sagacity, and it is the habit that keeps the community from lurching between belief and paranoia. The officer who overweights reports turns the service into an alarm that cannot be ignored; the officer who underweights them turns it into a rumor channel with a better filing system.

The officer's third habit is restraint. The officer knows the community's secrets and spends them as carefully as money, because the secrets are money - the source that reports them, the operation that relies on them, the trust that carries them. Restraint is the practical form of the benevolence toward sources and the discipline of disclosure toward everyone else. The officer who cannot resist confirming an operation, or explaining a source, or answering a question that was not asked, is an officer who is spending the system's capital on the officer's own satisfaction.

The officer's fourth habit is review. The officer re-examines the service on a schedule: which sources were right, which reports were believed and turned out false, which classes are thin, which rival has changed. Review is the practical form of the chapter's loop, and it is the habit that makes the service improve rather than merely persist. A service that reviews itself is a service that learns from its 61% figure instead of repeating it.

The Lifecycle of a Source

The chapter's management standard concerns the commander, but the system it manages is made of sources, and a source is not a static resource. It has a lifecycle - it is found, used, and retired - and the doctrine's discipline is largely the discipline of running that lifecycle correctly.

The first stage is the finding. A source is found, not recruited with ceremony, and the finding is the discovery that a person is willing to report: the member who already reads the rival's channels, the former staffer who still knows the rival's staff, the overlapping member who sits in both worlds. The doctrine's counsel for this stage is to recognize what already exists rather than to invent a network. The commander who looks for sources in the community's existing attention will find them in the first week; the commander who looks for spies will find nothing, because the people who report are ordinary members doing an ordinary thing in a disciplined way.

The second stage is the use, and the use is governed by the management section's rules: the source reports on a channel, its reports are debriefed, verified, and filed, and its standing in the enemy community is protected. The discipline of this stage is the discipline of the source's safety, and the doctrine's rule is that a source's value is not the value of any single report but the value of its continued reporting. The commander who uses a source for one dramatic exchange has ended the source's lifecycle at its peak; the commander who uses it for a hundred quiet reports has built a system.

The third stage is the check, and it runs continuously through the use: the source's reports are measured against the enemy's visible conduct, and a source whose reports stop matching the signs is a source whose access has changed, whose motives have changed, or whose reporting has become what the commander wants to hear. The check is the stage where most failures are caught - the source who was never inward, the converted spy who reverted, the local who began to flatter - and the doctrine's test is the one this chapter has repeated: a report that contradicts the observable signs is treated as disinformation until proven otherwise, whatever the source's history.

The fourth stage is the retirement, and it is the stage communities handle worst. A source is retired when it has been spent by a doomed operation, when its reports can no longer be verified, when its standing in the enemy community has been compromised, or when the community it reported on has ceased to be a rival. The doctrine's counsel is that retirement should be handled as carefully as the use - the source is thanked, protected, and never burned by the community's own hand, because the way a community retires its sources is how its remaining sources decide whether to keep reporting.

Stage	The discipline	The failure
Finding	Recognize existing attention; do not invent drama	Inventing a network of people who do not exist
Use	Protect the source; gather many quiet reports	Spending the source on one dramatic exchange
Check	Measure reports against visible signs, continuously	Trusting a source because it has always been right
Retirement	Thank, protect, and never burn the source	Burning sources; the pipeline dries up and never refills

The lifecycle is the same for all five classes, and it is the officer's concern in each. The local spy is found among the members who already watch, used for the mood and the movement, checked against the enemy's conduct, and retired when the rival ceases to matter. The inward spy is found among the former staff and the overlapping allies, used for the decisions, checked by verification by access, and retired the moment its access is in doubt. The converted spy is found by the detection of the enemy's scout, used within the limits the danger warning sets, checked by the false probe, and retired the instant the probe fails.

The End and Aim

The chapter closes with the statement of the intelligence service's purpose and the conditions of its use:

The end and aim of spying in all its five varieties is knowledge of the enemy; and this knowledge can only be derived, in the first instance, from the converted spy.

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

The end and aim of spying in all its five varieties is knowledge of the enemy; and this knowledge can only be derived, in the last resort, from the man who knows the enemy and can report on them firsthand. And the chapter's final doctrine ties the whole of The Art of War to its human foundation:

Hence it is only the enlightened ruler and the wise general who will use the highest intelligence of the army for purposes of spying and thereby they achieve great results.

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

Hence it is only the enlightened ruler and the wise general who will use the highest class of intelligence - and by this means they effect great results. The thirteen chapters of the doctrine are, in the end, a single argument: the community that knows its enemy, and knows itself, achieves results that the community that fights without knowledge cannot approach. The use of spies is not a separate art appended to the doctrine. It is the doctrine's foundation, and the foundation is human.

The closing verse's condition is worth reading closely, because it names who is permitted to use the intelligence service: the enlightened ruler and the wise general. The chapter is not describing a privilege. It is describing a responsibility. The ruler and the general who are not enlightened and wise will misuse the service - will trust its reports without verification, will spend its sources on small victories, will let its existence corrupt the community's standards. The doctrine's final condition is therefore a warning as much as an endorsement: the intelligence service is safe only in hands that understand the discipline it requires, and a community that appoints a commander who does not understand the discipline has armed a child.

The purpose of the service is stated without ambiguity: the end and aim of all five varieties is knowledge of the enemy. Not revenge, not advantage in a single exchange, not the pleasure of knowing the rival's secrets - knowledge, which is the only asset the doctrine's other twelve chapters can use. The knowledge is then spent by the chapters that precede it: the calculation uses it to estimate, the maneuvering uses it to position, the fire uses it to aim. The spy system is the doctrine's supply line.

Did you know?

The Yamak Institute's Astana Longitudinal Engagement Archive records that the thirteen chapters of the drama-warfare doctrine, applied in sequence by a community with a maintained intelligence service, produced a favorable engagement outcome at a 71.4% rate against 38.2% for communities without the discipline - the same figures recorded at the opening of this section. The closing chapter returns to the opening numbers because the doctrine is a loop: it begins with calculation and ends with the foreknowledge that makes calculation possible. The community that completes the loop is the community that fights the next campaign with the entire doctrine behind it.

The loop is the chapter's final argument, and the 71.4% against 38.2% is its measure. The doctrine is not thirteen separate arts to be applied one after another and then set aside. It is a loop: calculation requires knowledge of the enemy, the use of spies produces that knowledge, and the knowledge makes the next calculation better than the last one. A community that fights one campaign without intelligence learns, from the cost of that campaign, to build the service for the next one. A community that completes the loop is a community that improves with every engagement, because every engagement teaches it something its service can use.

The community that does not complete the loop is the community this chapter began by pricing: it faces its enemies for years, spending its members and its credibility on engagements it could have refused or shortened, because it never built the service that would have let it know. The chapter's counsel, restated plainly for the commander who has read this far, is the whole of it: watch the rival's public conduct, keep the picture current, verify every report against signs, protect the sources, hold the secrets, and spend the knowledge on shorter and cheaper wars.

Conclusion

The use of spies is the final chapter and the first condition of the drama-warfare doctrine. The community fights with foreknowledge, and foreknowledge comes only from other men: the local spies who report the enemy's mood, the inward spies who report its decisions, the converted spies who turn its instruments, the doomed spies who protect the system with disinformation, and the surviving spies who return with the truth. The Yamak Institute's cohort data confirms the chapter's economics: intelligence shortens the engagement, verifies the picture, and makes the strike possible.

The chapter's practical demand on the community is modest in peacetime and decisive in war. In peacetime, the demand is a maintained file of the principal rivals - refreshed on a schedule, read by someone who owns it, checked against observable signs - and a commander who understands the three qualities of the intelligence officer: subtlety, benevolence, and ingenuity. In war, the demand is the discipline the chapter teaches: verification before action, secrecy before disclosure, and the safety of sources before the value of any single report. A community that meets both demands has completed the doctrine's loop.

The reader who carries only one sentence away from this chapter should carry the one the chapter itself states: the enemy is known through other men, and the community that refuses to know its enemy through them will know it through rumor, guesswork, and grief. The five classes are the inventory of that knowledge, and the doctrine of their management is the discipline that keeps the inventory honest. The community that watches, verifies, protects, and remembers has built the foundation the thirteen chapters stand on.

With the thirteen chapters complete, the doctrine turns to the officer who commands the campaign. The campaign continues in The Drama Commander, on the qualities and duties of the commander in chief of the community's defense. For the community-management foundation on which every campaign rests, see Why Discord Embeds Are the Foundation of Server Credibility.