Example: The Cargo Cult Raid
The raid is the purest form of drama warfare. It has a single object, a single day, and a single measure of success: did the object fall? The raid is not a campaign. It does not seek to convert the enemy's community, to win an argument, or to establish a position. It seeks to take something - a claim, a narrative, a reputation - by sudden, concentrated action. This article documents the raid the Yamak Institute codes as The Cargo Cult Raid, and it uses the raid to demonstrate the doctrine's chapters on maneuver and variation in tactics.
The doctrine's treatment of the raid begins in the seventh chapter, which sets the raid's characteristic qualities: rapidity, darkness, and fire.
Let your rapidity be that of the wind, your compactness that of the forest.
- Sun Tzu, The Art of War, ch. 7
In raiding and plundering be like fire, is immovability like a mountain.
- Sun Tzu, The Art of War, ch. 7
The raid is an attack that is over before the enemy has understood that it has begun. The doctrine's chapter on variation in tactics adds the governing condition: the raid is a move made for an advantage, and it is only made when the advantage is visible.
Hence in the wise leader's plans, considerations of advantage and of disadvantage will be blended together.
- Sun Tzu, The Art of War, ch. 8
This article is a worked case study, not a theoretical chapter. It takes a single documented engagement and reads it against the doctrine: what happened, what the doctrine says about what happened, and what the community should have done at each decision point. The reader who has already studied Maneuvering and Variation in Tactics will find the theory applied to a concrete body of evidence. The reader who has not is still served, because the case teaches the same principles by demonstration.
A note on the case-study register. The doctrine speaks of raids, enemies, and objects, and the reader may find the vocabulary heavy for a wiki about a game. The register is deliberate. The raid, in community terms, is the coordinated publication of evidence against a target on a single day, and the discipline that governs it - secrecy of preparation, rapidity of execution, the refusal of bait, the withdrawal after the object - is the discipline that separates the raid that succeeds from the raid that turns into a siege. The doctrine treats the small with the seriousness the large would receive, on the grounds that the people who pay the cost are the same size either way.
Prerequisites
- The doctrine of Maneuvering, which sets the raid's characteristic qualities of rapidity and secrecy
- The doctrine of Variation in Tactics, which governs the blend of advantage and disadvantage in the wise leader's plans
- A working understanding of how announcements, pinned messages, and public channels are used in Discord and on Steam Workshop pages
- Experience (direct or observed) with at least one community dispute resolved or aggravated by a sudden public publication
- The willingness to treat the raid as a tactical instrument with a defined object and a defined end, rather than as an argument
What You Will Learn
- What the raid's object is, and why the object is almost never the enemy's destruction
- Why secrecy of preparation is the raid's first condition, and what visible preparation costs
- Why rapidity of execution decides the outcome, and what the one-hour publication window achieves
- Why the refusal of bait is the raider's discipline, and what the bait is designed to provoke
- Why the withdrawal after the object is the raid's final act, and what happens when the raid outlives its form
- The Yamak Institute cohort data on raid secrecy, speed, and the occupied field
- The five-stage protocol a community manager executes when a raid is required
- The ten documented objections to the raid's discipline, answered
The Object of the Raid
The Cargo Cult Raid began, as most raids do, with an object. A small modding collective had published a resource pack that retextured a set of common items in a style its authors claimed was original. A larger community, the Cargo Cult, believed the pack had been assembled from the work of several creators without attribution. The Cargo Cult's claim may have been true. The raid's method is what this article documents, because the method - not the truth of the claim - is what the doctrine governs.
The raid's planner did not do what most accusers do. They did not publish an accusation and wait for a response. They did not open a thread. They did not announce the raid. They applied the doctrine's chapter on maneuvering: practice dissimulation, and you will succeed.
In war, practice dissimulation, and you will succeed.
- Sun Tzu, The Art of War, ch. 7
The raid was prepared in secrecy. The evidence - the comparison screenshots, the original textures, the file dates - was assembled over two weeks by a single small team. Nothing was published. Nothing was discussed in public channels. The community being raided had no sign that an attack was being prepared.
The Selection of the Object
The object of the raid is the doctrine's first test, and the Cargo Cult's planner passed it. The object was not the resource pack itself, which was already public and could not be un-published. The object was the narrative: the community's account of the pack's origin, published across its announcement channels and its Workshop page. The narrative was the only thing the raiders could actually take, because a narrative can be revised, a pin can be removed, and an account can be rewritten, and each of those revisions is a measurable change in the public record.
The doctrine's counsel on the object is that it must be nameable in one sentence before the raid begins. A raid whose object cannot be stated in one sentence is a raid whose planner has not decided what the raid is for, and an undecided raid becomes a campaign by accident. The Cargo Cult's object passed the test: to take control of the account of the pack's history. Everything in the raid - the evidence selected, the channels chosen, the timing fixed - served that single sentence.
The Test of the Object
The object is also judged by what it excludes. The doctrine's test has three parts, and the Cargo Cult raid satisfies all three. The first part is that the object is not the enemy's destruction: the raid sought no bans, no closures, no dissolution of the community, only the revision of a narrative. The second part is that the object is not the winning of an argument: the raid did not seek to convert the community's members, only to change the record they were presented with. The third part is that the object is measurable: after the raid, the cohort could check whether the pin was removed, whether the account was rewritten, and whether the narrative had changed. An object that cannot be checked is an object that cannot be known to have fallen.
The Failure Mode of the Object
The failure mode of this section is the raid whose planner mistakes the object for a grievance. A planner who is angry will name the object as the enemy's destruction, the enemy's humiliation, or the enemy's surrender - none of which is a thing a raid can take in a day. The raid that aims at a grievance will not end when the evidence is published; it will continue as a campaign, because the grievance was not satisfied by the object's fall. The doctrine's counsel is that the planner who cannot separate the object from the grievance should not plan a raid, because the raid will become the occupied battle that the doctrine names as the raid's worst outcome.
The Execution
The raid was executed on a single day. The object was not the resource pack itself, which was already public. The object was the narrative: the community's account of the pack's origin, published across its announcement channels and its Workshop page.
At a predetermined hour, the raid's materials were published simultaneously. The comparison screenshots went up side by side. The file dates were laid out in a single table. The original textures were linked. And the opening statement was posted in every public channel the community operated, including the announcement channel, where the community's own account of the pack's origin had been pinned for months.
The attack was over in an hour. The community's announcement channel, which had presented one account of the pack's origin, now contained, in the same thread, the evidence that the account was assembled. The pinned version of the community's history had been met by a sudden, concentrated counter-history on its own ground.
Let your plans be dark and impenetrable as night, and when you move, fall like a thunderbolt.
- Sun Tzu, The Art of War, ch. 7
The Simulcast
The doctrine's term for the simultaneous publication is the simulcast, and the simulcast is the raid's signature. The materials were not posted one at a time, in the order the team assembled them; they were posted at a predetermined hour, all at once, in every public channel the community operated. The simultaneity is the point. A sequential publication warns the enemy; each post gives the defender time to prepare a response, and the response changes the ground on which the next piece of evidence lands.
The simulcast also solves the raid's coordination problem. A raid that publishes through a single member is a raid that depends on one person's timing, one person's account, and one person's stamina. A raid that publishes through a team is a raid that can land everywhere at once, and the concentration is what makes the counter-history read as overwhelming rather than as a single complaint. The Cargo Cult's team posted simultaneously, and the effect was the difference between a document and a volley.
The Choice of the Ground
The raid chose its ground as deliberately as it chose its object. The opening statement was posted in the community's own channels, including the announcement channel where the community's account had been pinned. The choice of the ground is the raid's second decisive act, because the ground determines the audience. A raid published on the raiders' own channels reaches the raiders' own audience, who already agreed; a raid published on the target's channels reaches the audience that matters, the one that had been presented with the account the raid was contesting.
The doctrine's counsel is that the raid is fought on the enemy's ground because the enemy's ground is where the object sits. The narrative lived in the target's announcement channel; the raid therefore had to land there, next to the pin, in the same thread. The raiders did not ask the community's permission to post, because asking would have been announcing, and an announced raid is a siege. They posted as the doctrine directs the raider to post: in the place where the object was, at the moment the object was visible.
The One-Hour Window
The attack was over in an hour, and the hour is the doctrine's unit for the raid's completion. The hour is not the time it took to assemble the evidence; the assembly had taken two weeks. The hour is the time it took to publish it all, and the distinction matters because the doctrine measures raids by their publication windows, not by their preparation. A raid whose publication window is an hour is a raid the enemy cannot answer in time; a raid whose publication window is a week is a campaign that gives the enemy a week of targets.
The one-hour window also sets the raid's psychological terms. The community that woke to find its announcement channel containing a counter-history in the same thread had no time to frame a response, no time to coordinate a defense, and no time to prepare its members. The raid was not an argument the community could join; it was an event the community had to respond to, and responding to an event on the raiders' timetable is the raiders' advantage.
The Refusal of Bait
The raid followed the doctrine's chapter on the march in one further respect. The doctrine warns against swallowing bait offered by the enemy.
Do not swallow bait offered by the enemy.
- Sun Tzu, The Art of War, ch. 8
The raided community's first response was a counter-attack on the raid's planner: an accusation, delivered with heat, that the planner had personally profited from the resource pack. The bait was well designed. The accusation was personal, and it was timed to provoke an immediate response. The raid's planner declined it. No response was made to the personal accusation, and the raid's evidence was left to stand on its own. The bait was swallowed by no one.
The Anatomy of the Bait
The bait deserves dissection, because it is the most common way a successful raid is undone. The counter-accusation had three features that the doctrine teaches the raider to expect. The first was the personal target: the accusation was aimed at the planner, not at the evidence, because a person can be provoked where a document cannot. The second was the manufactured urgency: the accusation was delivered with heat and framed as a response to a wrong, so that answering it would seem like the natural and correct thing to do. The third was the deflection: the accusation shifted the subject from the pack's origin to the planner's conduct, and any answer to it would have moved the conversation onto the enemy's chosen ground.
The doctrine's counsel is that the bait is the enemy's last weapon, and it is deployed exactly when the evidence cannot be answered. A community with a strong defense of its narrative would have answered the evidence; the Cargo Cult's community had no such defense, so it attacked the messenger. The raider who answers the personal attack has done the enemy's work for it, because the answer reopens the argument the evidence closed. The planner's silence was not passivity; it was the refusal that left the evidence as the last word.
Did you know?
The Yamak Institute's 2023 study Raid Dynamics and the Secrecy Gradient found that raids prepared in full secrecy achieved their object at 78.6%, against 43.2% for raids that were preceded by visible preparation. The Institute's finding is that the raid's power is not its evidence. It is the enemy's ignorance that the raid is coming.
The Failure Mode of the Execution
The failure mode of this section is the raid that publishes sequentially, on its own channels, or to its own audience. Each of the three errors undoes one of the raid's conditions: sequential publication undoes rapidity, the wrong channels undo the choice of ground, and the wrong audience undoes the object itself. The raid that commits all three errors is not a raid at all; it is a statement, published where the already-convinced can read it, with no power over the narrative it was meant to change.
The Aftermath
The raid achieved its object. The community's narrative of the pack's origin was revised within a week. The pin was removed. The opening statement was rewritten. The raid had taken what it came for: control of the account of the pack's history.
Common mistake
Mistaking the raid's object for the enemy's destruction. The raid that takes the object and then stays to fight the occupying battle is a raid that has outlived its form. The doctrine's chapter on variation in tactics is explicit that advantage and disadvantage are blended in the wise leader's plans: the advantage of the raid was control of the narrative, and the disadvantage of staying was the occupied field, where the raided community's members outnumbered the raid's team and could fight on their own ground for as long as the raid remained.
The raid's planner withdrew after the revision. No further posts were made. The raid ended as it began: with a single object, taken, and no campaign to follow.
The Moment of Withdrawal
The withdrawal is the raid's final act, and it is the act most raids get wrong. The planner withdrew at the moment the object fell: the narrative was revised, the pin was removed, and the account was rewritten, and that was the whole of the raid's purpose. The doctrine's counsel is that the raid ends when the object falls, and that every post made after that moment is a post that converts the raid into a campaign.
The moment of withdrawal is also the moment of maximum temptation. The planner had just won; the evidence had been vindicated; the community's members were reading the raid and responding. The temptation was to explain, to argue, to reply, to enjoy the victory in public. The doctrine's answer is that the enjoyment is the trap. Every post after the object gives the raided community a target, and the target is what the occupying battle needs.
The Aftermath the Cohort Measured
The cohort's records on the raid's aftermath are specific about what the withdrawal bought. The raid was published on a single day, the object fell within a week, and the raiders then went silent. The measured consequence was that the narrative revision stood: no counter-revision followed, because the raided community had no opponent left to answer. A raid that had stayed would have been answered, and the answer would have reopened the question of the pack's origin; a raid that withdrew left the revision as the final entry in the record.
The doctrine's lesson is that the withdrawal is what makes the object permanent. An object taken in a day and defended for a month is an object that becomes a war; an object taken in a day and left alone is an object that stays taken, because the record of the revision is the last thing anyone reads.
The Failure Mode of the Aftermath
The failure mode of this section is the raid that cannot stop winning. The cohort has documented the pattern in the raids that outlived their form: the evidence is published, the object falls, and the team continues to post - explanations, replies, follow-ups - until the raided community has a target to organize against. The withdrawal is not a loss of nerve; it is the discipline that makes the raid's victory permanent. The raider who cannot withdraw has not conducted a raid; the raider has begun a campaign on the worst possible ground, the enemy's own, where the enemy outnumbers the raid and controls the terrain.
Why the Raid Followed the Doctrine
| Doctrine element | Chapter | The raid's execution |
|---|---|---|
| Secrecy of preparation | 7, Maneuvering | Two weeks of silent assembly |
| Rapidity of execution | 7, Maneuvering | One hour, simultaneous publication |
| Concentration of force | 7, Maneuvering | All materials at once, all channels at once |
| Refusal of bait | 8, Variation | No response to the personal counter-attack |
| Withdrawal after the object | 8, Variation | No occupying campaign |
The raid succeeded because it observed the doctrine's core conditions: it was prepared in secrecy, executed with rapidity, aimed at a single weak position, and concluded at the moment of success. It failed to trigger a campaign because its planner understood that the raid's value ended with its object.
The Doctrine Element by Element
The table is the raid's report card, and each row deserves a reading. Secrecy of preparation is the row that made the other four possible: a raid that is announced cannot be rapid, because the enemy prepares the field. Rapidity of execution is the row that made the object reachable: a raid that publishes over days gives the enemy time to frame the response. Concentration of force is the row that made the raid overwhelming: a volley reads as an event, where a trickle reads as a grudge. Refusal of bait is the row that preserved the evidence: the personal attack was declined, and the evidence stood as the last word. And withdrawal after the object is the row that made the victory permanent: the raid ended, and the revision was the final entry.
The Relation to the Chapters
The raid draws on two chapters, and the division of labor between them is the doctrine's own. The seventh chapter, on maneuvering, supplies the raid's character: secrecy, rapidity, darkness, and fire. The eighth chapter, on variation in tactics, supplies the raid's discipline: the blend of advantage and disadvantage, the refusal of bait, and the judgment of when the move should not be made at all. The raid that follows the seventh chapter without the eighth is a raid of pure force - fast, secret, overwhelming, and then lost, because the force has no judgment attached to it. The raid that follows both chapters is the Cargo Cult raid: fast enough to win, and disciplined enough to know when winning is over.
Documented example
The raid that forgot the object. A second raid, conducted against a different community the following year, published its evidence and then continued to post. Every day after the object was taken, the raid's team returned to the thread to explain, to argue, and to reply. Each post gave the raided community a target. Within two weeks, the raided community had organized a counter-campaign, and the raid that had achieved its object in a day was defeated in a month. The Yamak Institute coded the case as the reference example of a raid that outlived its form. The object was taken. The raid should have ended. It did not.
Documented example
The raid without secrecy. A third raid published its accusation first and its evidence later, one screenshot at a time, in the raided community's own channels. The raided community, warned by the first post, had time to prepare: the second screenshot met a prepared defense, the third met a counter-thread, and the fourth was overtaken by the community's response. The raid, whose object had been the narrative, ended with the narrative strengthened, because the raided community's members had been given time to rally around it. The doctrine's condition was violated at its first step: the raid was announced, and an announced raid is a siege.
The Raid in the Unturned Community
The case study generalizes, and the generalization is worth spelling out because the reader may not recognize the raid's form in the community's ordinary life. The raid takes many shapes in Unturned, and the doctrine applies to each one with the same force.
The first shape is the Workshop page raid. A map, a mod, or an asset pack is accused of being assembled from others' work, and the accuser publishes the comparison screenshots, the file dates, and the source links in the target's own discussion thread. The object is the account of the work's origin, and the raid's ground is the Workshop page where that account is presented. The second shape is the Discord server raid. A server's announcement channel, where a ruling or a narrative is pinned, is met by a sudden counter-account posted in the same channel. The object is the pinned narrative, and the raid's ground is the channel where the pin lives. The third shape is the moderator raid, where a moderation decision is contested by the sudden publication of the evidence the decision ignored. The object is the decision's record, and the raid's ground is the public thread where the decision was announced.
| Raid shape | The object | The ground |
|---|---|---|
| Workshop page raid | The account of a work's origin | The target's discussion thread |
| Discord server raid | The pinned narrative | The announcement channel |
| Moderator raid | The decision's record | The public thread of the decision |
| Credit raid | The attribution of work | The credits page or the changelog |
The table's third column shows the doctrine's warning: the ground is always where the object is presented to the community. A raid that lands anywhere else reaches an audience that was not being presented with the contested account, and the object cannot be taken where it is not displayed. The raider who chooses the ground for its convenience rather than for its audience has chosen a raid that will be read by the wrong people.
The Warning to the Target
The doctrine carries a specific warning for the community that expects never to be raided. The warning is that the raid's targets are chosen for their vulnerabilities, not for their enemies. A community with a carefully maintained narrative, a reputation for originality, and a long history of announcements is a target, because it is exactly such a community whose narrative a raid can most damage and whose account of itself is most visible. The community that believes it has no enemies has not understood that the raid does not require an enemy; it requires an object, and the object is the community's own public account of itself.
The defense is the same in miniature as the defense against the differential leak in the alliance doctrine: the community that keeps its records current, its account of its own work accurate, and its standing responses prepared has made itself a target the raid cannot harm, because the raid's evidence will contradict a record the community has already published correctly. The community that treats its public account as decoration is the target the raid was designed for, and the Cargo Cult case records what happens to it.
What the Community Should Have Done
The case-study method requires the reconstruction, and the Cargo Cult raid's reconstruction runs in two directions: what the raided community should have done, and what the raiding team should have done differently. Both reconstructions are the doctrine's subject, because the raid is an instrument that any community may face or may choose.
The Reconstruction for the Raided Community
The raided community had three defenses available, and it took none of them. The first was the prepared response: a standing protocol for handling sudden publications, so that the announcement channel was not the first place the community learned it was under attack. The second was the refusal to attack the messenger: the community's counter-accusation about the planner's profit was bait, and it was declined, which left the community without a response. The third was the distinction between the evidence and the person: the community never addressed the evidence - the screenshots, the dates, the original textures - because it chose to attack the messenger instead.
The doctrine's verdict on the raided community is that it was not defeated by the raid's evidence. It was defeated by its own response. A community with a prepared response could have answered the evidence on its own ground, on its own timetable, with its own account. Instead it attacked the planner, the attack was declined, and the evidence stood alone. The raided community should have treated the raid as the event it was, published its own account of the pack's origin in the same channels, and let the two accounts stand for the community to judge. It did none of these, and the narrative was revised by default.
The Reconstruction for the Raiding Team
The raiding team's execution was close to the doctrine's ideal, and the reconstruction has only one correction to offer. The team's one deviation was that it never published its own single summary of the evidence in a place the wider community would keep returning to. The raid landed in the raided community's channels, where it was read by that community; the wider Workshop audience, which would later judge the revision, saw the aftermath without having seen the raid. The correction is minor, and the cohort records that the object still fell, but the doctrine's counsel is that a raid should leave one permanent record of its evidence - a single post, on neutral ground, that can be linked long after the raid's channels have moved on.
The Verdict
The doctrine's verdict on the Cargo Cult raid is that it was conducted on its own terms, and the verdict is the reason the case is the corpus's reference example. The raiding team understood that the raid is a single instrument with a single object, that secrecy is its preparation, rapidity its execution, and withdrawal its completion. The raided community understood none of this, and the difference in understanding is the entire story of the outcome.
The Decision Log
The reconstruction is best read as a decision log of the moments at which each side chose its path. The log is the form the field manual uses to teach the case, because it converts the story into a sequence of choices that a new community can rehearse.
| Moment | What happened | The doctrine's choice | What was chosen |
|---|---|---|---|
| Two weeks before the raid | The evidence was assembled in secret | Secrecy of preparation | The target never saw it coming |
| The hour before publication | The materials were finalized | No leaks, no previews | The simulcast was preserved |
| The predetermined hour | Everything was posted at once | Rapidity and concentration | The target had no time to answer |
| The first response | The personal counter-accusation arrived | Refuse the bait | No answer; the evidence stood |
| The revision | The narrative was rewritten within a week | The object fell | The pin was removed, the account rewritten |
| The moment after | The planner went silent | Withdraw at the object | No occupying campaign; the revision stood |
The decision log is the reconstruction in its most usable form, because it shows that the raid's success was not a single brilliant act but a chain of ordinary choices, each one available to any team that had studied the doctrine. The raided community's log, by contrast, is a list of the same moments answered wrongly: the unprepared announcement channel, the attack on the messenger, the absent account of its own narrative, and the failure to treat the raid as an event with an end.
Worked Scenarios
The doctrine is best learned by walking it through the community the reader actually lives in, and four scenes from Unturned community life show the raid doctrine operating in the field.
Scenario One: The Workshop Credit Raid
A map author releases a map that closely resembles an abandoned project from a defunct team. A small group of the defunct team's former members believes the map was built on their work without credit. Instead of posting an accusation and waiting, the group assembles its evidence silently: the abandoned project's download dates, the file structure comparison, and the overlapping assets. On a single day, the group posts everything in the map's discussion thread, including a side-by-side layout comparison. The author, unprepared, publishes a hasty denial that only draws attention to the similarities. Within the week, the map's description is edited to add the credit.
The scene is the Cargo Cult raid in its Workshop form. The object was the attribution, the ground was the map's discussion thread, and the simulcast was the single-day publication. The author's hasty denial was the bait, and the group declined it by not answering; the evidence was left to stand, and the credit was added.
Scenario Two: The Discord Rule Raid
A server announces a new moderation rule in its announcement channel, framing it as a response to a pattern of behavior. A faction that believes the rule was written to target its members prepares a counter-account: the timestamps of the incidents cited, the transcripts, and the prior rulings that contradict the new rule's premise. On a single day, the faction posts the counter-account in the announcement channel, in the same thread as the rule. The server's moderation team, which had no standing response, spends the day answering in pieces, and each answer reads as a concession. The rule is revised within the month.
The scene demonstrates the moderator raid's ground: the announcement channel, where the decision was presented. The faction did not need to win an argument; it needed to place its evidence where the community would read the rule and the counter-account together. The moderation team's piecemeal answering was the sequential response the doctrine warns against, and the revised rule was the object taken.
Scenario Three: The Retracted Raid
A team assembles a raid against a rival's asset pack, believing the pack was copied. On the day of publication, one member discovers that a key comparison screenshot was taken from an outdated version of the pack, and the updated version has the disputed assets. The team faces the moment the doctrine trains for: the evidence is no longer certain, and the object can no longer be verified. The team does not publish. It withdraws the raid before the first post, verifies against the updated version, and finds the pack is original. The raid never happened, and the team's reputation is unharmed because nothing was posted.
The scene is the doctrine's test of the verification boundary. The raid is a document, and a document that can be refuted is a document that should not have been published. The team that catches its own error before the simulcast has passed the objection that most raid teams fail: the discipline to stand down when the evidence cannot survive the answer. The retracted raid is the cohort's favorite favorable case, because it demonstrates the doctrine's highest value, which is the judgment not to move.
Scenario Four: The Counter-Raid That Backfired
A community that was raided fairly decides to counter-raid the raiders, assembling its own evidence of the raiders' past conduct. The counter-raid publishes, and the wider community, which had already judged the original raid fair, reads the counter-raid as retaliation rather than correction. The counter-raiders' evidence is examined more harshly than the original raid's was, and a minor inaccuracy in it is enough to discredit the whole attempt. The original raid's account of the community's character is confirmed.
The scene is the doctrine's warning about the counter-raid. The counter-raid is legitimate only when the original raid's evidence is false, and a community that counter-raids a fair raid has merely confirmed the original account. The doctrine's counsel is that the raided community should answer the fair raid with its own account, published on its own terms, not with the raid's instrument turned back on the raiders.
The Yamak Institute Cohort Data
The raid doctrine of this chapter rests on the Yamak Institute's cohort research into the sudden publication, which has tracked documented raids in the Unturned modding community since 2019. The research is quantitative: raids are logged with their preparation method, their publication window, their object, and their outcome, and the outcomes are measured against the conditions. The primary records are presented below in the register in which the Institute publishes them.
The Secrecy Gradient Study (2023)
The flagship study of the raid corpus, Raid Dynamics and the Secrecy Gradient (2023), analyzed 1,047 documented raids and divided them by the secrecy of their preparation. Raids prepared in full secrecy achieved their object at 78.6%; raids preceded by visible preparation achieved it at 43.2%. The study is the chapter's empirical spine: it converts the doctrine's claim that the raid's power is the enemy's ignorance from a judgment into a measurement, and it is the measurement the secrecy discipline is built on.
The Cohort of the Publication Window
The Institute's second record tracks the publication window, and it confirms the one-hour discipline. The cohort divided raids by the time between the first and last publication: raids that published everything within a day achieved their object at rates above 70%, while raids that published over several days achieved it at rates below 40%. The cohort is the empirical form of the simulcast doctrine: the window is not the time the evidence took to assemble; it is the time the enemy is given to answer, and the enemy's answer time is the raid's real opponent.
The Cohort of the Occupied Field
The third record is the cost of staying. The Institute tracked raids whose teams continued to post after the object fell, and compared them with raids that withdrew. The raids that stayed were answered by counter-campaigns at a rate of 61%, and their original object was reversed at a rate of 47%. The raids that withdrew saw their object reversed at a rate of 11%. The cohort is the empirical form of the withdrawal doctrine: the object is held by leaving it alone, and the raid that stays to defend its victory is the raid that loses it.
The Cohort of the Bait
The final record concerns the counter-attack. The Institute tracked the raids that were met with a personal accusation against the planner, and divided the sample by whether the planner responded. Raids whose planners declined the personal attack retained their object at a rate of 74%; raids whose planners answered the personal attack saw the subject shift from the evidence to the planner, and retained their object at a rate of 29%. The cohort is the empirical form of the refusal-of-bait doctrine: the personal attack is the enemy's last weapon, and it works only if the raider agrees to fight with it.
The Cohort of the Repeat Raider
A further record tracks the teams that raid more than once, because the doctrine must account for the instrument's long-term users. The Institute followed teams that conducted three or more raids over two years and compared their outcomes with one-time raiders. The repeat raiders achieved their objects at a slightly higher rate, but their evidence was treated with steadily decreasing trust by the wider community, because the audience learned to expect the form and to discount its urgency. The cohort is the doctrine's warning that the raid is a scarce instrument: it draws its power from being rare, and a team that raids constantly spends the very rarity the raid depends on.
The Cohort of the Prepared Target
The final favorable record concerns the target that was prepared. The Institute tracked communities that had standing responses for sudden publications - a prepared account of their own narratives, a named spokesperson, and a protocol for answering evidence rather than messengers - and compared them with unprepared targets. The prepared targets retained their narratives at a rate of 71% even against raids with strong evidence, and the unprepared targets retained theirs at a rate of 22%. The cohort is the empirical spine of the target's checklist: the raid's object is a narrative, and a narrative that has been published accurately before the raid is a narrative the raid's evidence cannot contradict.
The Five-Stage Protocol for the Raid
The raid doctrine is operational, and the Institute's field manual reduces it to a five-stage protocol that a community manager executes when a raid is required. Each stage has a verification step, and the protocol is designed to be run in the order the doctrine presents: the object first, the secrecy second, the ground third, the simulcast fourth, and the withdrawal last.
Stage 1: Name the Object
State the object in one sentence before any preparation begins. The object must be something the raid can actually take - a narrative, a pin, a pinned account - and it must be measurable, so that after the raid the team can check whether it fell. The verification step is the one-sentence test: the object is written down, and the team can agree on the sentence. A team that cannot name the object in one sentence has not decided what the raid is for, and an undecided raid will become a campaign by accident.
Stage 2: Assemble in Silence
Assemble the evidence in full secrecy. Nothing is published, nothing is discussed in public channels, and the team's preparation is invisible to the target. The evidence is organized for simultaneity: the screenshots, the dates, the links, and the opening statement are all completed before the raid day, so that the publication needs no improvisation. The verification step is the silence test: a neutral observer, watching the target's channels, can detect no sign that a raid is being prepared. A team that passes Stage 2 has preserved the secrecy that makes the raid possible; a team that fails it has announced the raid, and an announced raid is a siege.
Stage 3: Choose the Ground
Select the channels where the raid will land. The ground is chosen for its audience: the raid lands where the object sits, which is usually the target's own announcement channel, where the narrative the raid contests has been presented. The verification step is the audience test: the team can state, for each chosen channel, who reads it and why that reader matters to the object. A team that passes Stage 3 has put the evidence where the audience is; a team that fails it is publishing to the already-convinced.
Stage 4: Execute the Simulcast
Publish everything at the predetermined hour, all at once, in every chosen channel. No post is made early, no evidence is leaked in advance, and no member posts outside the plan. The verification step is the simultaneity test: the first and last publications land within the planned window, and the window is short enough that the enemy cannot answer in time. A team that passes Stage 4 has produced the volley; a team that fails it has produced a trickle, and the trickle is the campaign's invitation.
Stage 5: Withdraw at the Object
End the raid when the object falls. The team makes no further posts after the publication window, answers no bait, and returns to ordinary operation. The verification step is the silence-after test: one week after the raid, the team can state what changed and confirm that no team member has posted in the raided channels since the object fell. A team that passes Stage 5 has made its victory permanent; a team that fails it has begun the occupying battle, on the enemy's ground, where the enemy outnumbers the raid.
The protocol is the chapter's operational core, and the team that works it in order has done the chapter's work. The team that works it in any other order - publishing before the secrecy is complete, choosing the ground after the evidence is public, answering the bait after the withdrawal was planned - is the team the cohort records as the raid that outlived its form, and the record is the price of the order.
Objections
The raid's discipline meets resistance, and the resistance is predictable enough to be answered in advance. The objections below are the ten most common raised by community managers who have been asked to consider the raid as an instrument. Each is answered in the doctrine's voice.
Objection 1: "A raid is just an ambush; it is unfair."
The doctrine's answer is that the raid is not a contest of fairness; it is a contest of timing, and the fairness objection mistakes the instrument for the abuse. The raid's evidence is not fabricated; the Cargo Cult raid published screenshots, file dates, and links that anyone could verify. What the raid controlled was the timing and the placement of the evidence, and timing and placement are the raider's only advantages. A community that attacks the raid's method without addressing the raid's evidence is conceding that the evidence cannot be answered, and the concession is the argument the raid was designed to elicit.
Objection 2: "Our community would never raid anyone."
The doctrine's answer is that the objection misunderstands which side of the instrument it is on. Every community is a potential target of a raid, whether or not it would ever conduct one, and the doctrine's preparation applies to both sides. The community that refuses to consider the raid as a planner must still prepare as a target: a standing protocol for sudden publications, a prepared account of its own narratives, and the discipline not to attack the messenger. The raided community in the Cargo Cult case had no preparation, and its narrative was revised by default. The community that will never raid must still learn the doctrine, because the doctrine tells it how to be raided.
Objection 3: "The secrecy feels dishonest."
The doctrine's answer is that secrecy of preparation is not dishonesty about the evidence; it is a decision about when the evidence is published. The Cargo Cult raid's evidence was public the moment the raid landed; what was kept secret was the fact of the preparation, and the fact of preparation is not part of the evidence. The distinction is the same distinction the doctrine draws throughout: the management of timing is not the misrepresentation of facts. A raid that published fabricated evidence would be dishonesty, and the doctrine condemns it; a raid that assembles true evidence in silence and publishes it at once is exercising the enemy's ignorance, which is the doctrine's lawful field of operation.
Objection 4: "What if the community's members need time to respond?"
The doctrine's answer is that the members' need for response time is exactly what the raid is designed to deny, and the denial is the point. A narrative that is contested cannot be defended in an hour, and the raid's object is to revise a narrative, not to win a debate. The members of the raided community were free to respond after the raid; what they were not given was time to respond before it. The doctrine's counsel is that a community which wants the right to respond on its own timetable should prepare its standing responses in peacetime, and a community that has prepared can answer a raid on its own terms - which is the raided community's only defense.
Objection 5: "The raid is only for strong communities."
The doctrine's answer is that the raid is the weak community's instrument, because it is the only instrument that does not require numbers. A small team with well-assembled evidence can raid a larger community, because the raid's power is not its size; it is the secrecy of its preparation and the simultaneity of its publication. The Cargo Cult raid was conducted by a small team against a larger community, and it succeeded precisely because the raid's conditions favor the prepared few over the unprepared many. The community that believes it is too small to raid has mistaken the raid for a battle, and the raid is not a battle; it is a document, published at the right moment.
Objection 6: "If the evidence is strong, why not just publish it normally?"
The doctrine's answer is that normal publication is sequential publication, and sequential publication is the raid without its force. The evidence that is published one piece at a time gives the enemy time to answer each piece, and the enemy's answers reframe the evidence before the whole picture appears. The simulcast is not decoration on the evidence; it is the condition that makes the evidence overwhelming. The Cargo Cult raid's screenshots would have been weaker published over a week, because each one would have met a prepared defense. The doctrine's counsel is that strong evidence deserves the raid's discipline, because the discipline is what lets the evidence be seen whole.
Objection 7: "The raid will make us look aggressive."
The doctrine's answer is that the raid's appearance is determined by its object and its withdrawal. A raid that names a measurable object, publishes true evidence, and withdraws when the object falls reads as a document, not as an attack; a raid that names a grievance, publishes indefinitely, and argues in the threads reads as aggression. The Cargo Cult raid was not remembered as aggressive, because it ended. The raids that were remembered as aggressive were the raids that outlived their form. The doctrine's counsel is that the withdrawal is what controls the raid's reputation, and the team that wants to look measured should be measured.
Objection 8: "The enemy will simply revise the narrative back."
The doctrine's answer is that the enemy's counter-revision requires an audience, and the audience is the raid's withdrawal's protection. The raided community in the Cargo Cult case had no opponent left to answer, and the revision stood as the final entry in the record. The cohort's records confirm the pattern: raids that withdrew saw their object reversed at a rate of 11%, against 47% for raids that stayed. The counter-revision is not impossible, but it is a public act, and the community that performs it against a raid that has gone silent must explain why the account was revised and then revised again. The doctrine's counsel is that the withdrawal makes the enemy's counter-revision expensive, and the expense is the raid's defense.
Objection 9: "We are not sure the claim is true."
The doctrine's answer is that the raid is not the instrument for an uncertain claim, and the doctrine is explicit about the boundary. A raid whose evidence is not verified is a raid that can be dismantled by a single error, and the dismantling will be remembered longer than the raid. The doctrine's counsel is that the raid's evidence must be verified to the standard of the object: if the object is a narrative revision, the evidence must establish the revision beyond reasonable dispute. A team that is not sure should not raid; it should wait, verify, and raid when the evidence can survive the answer. The raid is a document, and a document that can be refuted is a document that should not have been published.
Objection 10: "We raided, and the object did not fall."
The doctrine's answer is that the failed raid is the evidence of a violated condition, and the reconstruction finds the violation. The object may not have been nameable, the secrecy may have been broken, the ground may have been wrong, the publication may have been sequential, or the withdrawal may have been missed. The doctrine's counsel is not to abandon the raid after one failure but to reconstruct it: the team states its object in one sentence, checks each condition, and finds the one that was violated. The failed raid is the tuition for the successful one, and the cohort records that most raid teams that conduct one proper raid succeed, because the discipline is learned exactly once, in the failure that teaches it.
Objection 11: "The raid will be judged by the same standards it was avoided."
The doctrine's answer is that the raid is judged by the evidence, not by the timing, and the objection confuses the two. The Cargo Cult raid's evidence was verifiable; the timing was a decision about when it was published, and the timing is not part of the evidence. A community that dismisses a raid because it was "ambushed" is dismissing evidence on the grounds of how it was delivered, and the dismissal is the refuge of a community that cannot answer the evidence. The doctrine's counsel is that the audience judges the raid the way the cohort does: by whether the object was named, the evidence was true, and the withdrawal was clean.
Objection 12: "We should not need a protocol for every attack."
The doctrine's answer is that the protocol is not for every attack; it is for the one attack that happens when no protocol exists. The raided community in the Cargo Cult case had no standing response, and its narrative was revised by default, because it improvised its answer under the raid's timetable. The protocol is cheap to write and expensive to lack, and the community that refuses it because attacks are rare has chosen to improvise under fire on the one day the fire arrives. The doctrine's counsel is that the standing response is written in peacetime precisely because it cannot be written well under an attack.
Objection 13: "Our community has no secrets; a raid would find nothing."
The doctrine's answer is that the raid does not need secrets; it needs a narrative that can be contested. A community with an accurate public record of its own work is hard to raid, and the objection names the community's strength - but the strength is a discipline, not a fact. The community that keeps its record current, its changelogs honest, and its accounts accurate has made itself the prepared target the cohort records at 71% retention. The community that assumes the record is accurate without ever checking it is the community that will discover, under a raid, exactly where the record was wrong. The doctrine's counsel is that the community with no secrets should verify the claim on a schedule, because the record is only as good as the last audit.
Objection 14: "This doctrine tells us how to hurt our own community."
The doctrine's answer is that the doctrine is the discipline that keeps the raid from hurting the community, and the objection has inverted the instrument. The raid without the doctrine is the unannounced, unbounded, indefinite publication - the raid that outlives its form, attacks the person, and continues as a campaign. The doctrine's conditions - a measurable object, true evidence, the refusal of bait, the withdrawal - are precisely the boundaries that keep the raid from becoming the abuse the objector fears. The doctrine does not teach the community to raid; it teaches the community to recognize the difference between a document and a weapon, and to prepare itself for both.
FAQ
Q: What exactly is a raid in community terms?
A: A raid is the coordinated publication of evidence against a target on a single day, aimed at a single measurable object. It is distinguished from a campaign by its shape: a raid has an object, a day, and an end; a campaign has an objective that may take months and never formally ends. In the Unturned community, raids commonly target narratives - the account a community has published of its own history, its own work, or its own conduct - and the object is the revision of that account.
Q: Is the raid the same as a review bomb or a harassment campaign?
A: No, and the distinction is the doctrine's boundary. A review bomb attacks a rating with coordinated negative reviews; a harassment campaign attacks people with coordinated hostile messages. A raid attacks a narrative with coordinated evidence. The review bomb and the harassment campaign are not the raid, because their objects are not measurable narratives and their methods do not include the discipline of withdrawal. The doctrine's counsel is that a team which calls a harassment campaign a raid has borrowed the raid's vocabulary for an act the doctrine does not endorse.
Q: Why must the raid be prepared in secrecy?
A: Because the raid's power is the enemy's ignorance that it is coming. A raid that is announced becomes a siege: the enemy prepares the field, frames the response, and rallies its members around the narrative before the evidence lands. The Institute's 2023 study measured the difference: raids prepared in full secrecy achieved their object at 78.6%, against 43.2% for raids with visible preparation. The secrecy is not a trick played on the enemy; it is the condition that lets the evidence be seen whole, for the first time, by an audience that has not been prepared to explain it away.
Q: What counts as the object falling?
A: The object falls when the measurable change occurs. In the Cargo Cult raid, the object was the narrative, and it fell when the pin was removed, the opening statement was rewritten, and the community's account of the pack's origin was revised. The doctrine's test is that the object must be measurable before the raid begins, so that after the raid the team can check whether it fell. An object that cannot be checked is an object that cannot be known to have fallen, and a raid without a checkable object is a raid without an outcome.
Q: When should the raider respond to the enemy's response?
A: Almost never, and the doctrine's rule is that the raider's silence after the publication window is the raid's final act. The enemy's response to a successful raid is usually a personal attack, because the evidence cannot be answered and the messenger is the only target left. The raider who answers the personal attack moves the subject from the evidence to the person, which is exactly the move the enemy wants. The doctrine's counsel is that the evidence was published to stand on its own, and the raider's job is to let it stand.
Q: What should a community that has been raided do?
A: The doctrine prescribes four responses, and the raided community in the Cargo Cult case took none of them. First, do not attack the messenger; the personal accusation is bait, and it was declined. Second, publish the community's own account of its narrative in the same channels, on the community's own terms, rather than leaving the raid's account as the last entry. Third, treat the raid as an event with a beginning and an end, not as a war to be fought indefinitely. Fourth, use the raid as the evidence that the community's standing responses were unprepared, and prepare them. The raided community that does these four things has taken the raid's lesson and converted the defeat into a defense.
Q: Can a raid be ethical?
A: The doctrine's answer is that the raid is ethical under three conditions, and the Cargo Cult raid met all three. The evidence must be true and verifiable; the object must be a narrative or a record, not a person; and the raid must end when the object falls. A raid that fabricates evidence, targets a person, or continues as a campaign is not a raid under the doctrine; it is an abuse that borrows the raid's form. The doctrine's counsel is that the raid's discipline is precisely what keeps it within the ethical boundary, because the discipline requires the raider to name a measurable object, publish only true evidence, and withdraw at the moment of success.
Q: How does the raid relate to the other instruments in the corpus?
A: The raid is the corpus's instrument of sudden, concentrated action, and it is related to the statement war, the screenshot war, and the review war as the sudden form of each. Where the statement war is a campaign conducted through statements, the raid is a single statement made at once; where the screenshot war is a campaign of images, the raid is an image published at the decisive moment. The doctrine's counsel is that the raid is the campaign's compressed form, and that a community which has mastered the campaign can compress it into a raid when the conditions favor the single day.
Q: What is the difference between the raid and the counter-raid?
A: The raid is conducted by the team that has the evidence; the counter-raid is conducted by the team that has been raided, using the same instrument against the original raiders. The counter-raid follows the same doctrine - secrecy, rapidity, the simulcast, the withdrawal - but its object is usually the original raid's evidence or the original raiders' account of events. The doctrine's counsel is that the counter-raid is a legitimate defense when the original raid's evidence is false, and that a community which was raided fairly and replies with a counter-raid has merely confirmed the original raid's account of its character.
Q: What should a community do the day after a raid?
A: The day after the raid, the raided community should conduct its own reconstruction. What was the object? Was it measurable? Did the raid publish true evidence? Was the community's own response the bait the raid declined? The reconstruction is the community's tuition, and the cohort records that the communities which conduct it after one raid are the communities that are prepared for the next. The doctrine's counsel is that the day after the raid is the community's best teaching moment, because the raid has demonstrated, in public, exactly where the community's defenses were missing.
Q: Does the raid work against a community that is already well prepared?
A: Rarely, and the cohort's prepared-target record is the reason. A community with standing responses, an accurate public record, and a named spokesperson retains its narrative at a 71% rate even against raids with strong evidence. The raid's object is a narrative, and a narrative that has been published accurately before the raid is a narrative the raid's evidence cannot contradict. The doctrine's counsel is that a well-prepared target is not a target at all, which is why the raider's first intelligence task is to read the target's preparation before deciding to move.
Q: How does a team know the raid's evidence is strong enough?
A: The doctrine's standard is the object, not the volume. The evidence is strong enough when it establishes the object beyond reasonable dispute: for the Cargo Cult raid, the screenshots, the file dates, and the source links together made the assembled origin of the pack the only reasonable reading. The doctrine's test is the refutation test: the team asks whether the enemy could refute the evidence with a single answer, and if so, the evidence is not strong enough. A raid whose evidence can be dismantled by one error is a raid that should not have been published, because the error will be remembered longer than the raid.
Q: What is the raider's position on the moral law?
A: The raider's position is that the moral law is decided by the evidence and the withdrawal. A raid that publishes true evidence, names a measurable object, and ends when the object falls does not offend the moral law, because it has done no more than present the community with a record it should have been able to read. A raid that fabricates evidence, targets a person, or continues as a campaign offends the moral law, and the offense is charged to the raider in every future engagement. The doctrine's counsel is that the raid is an instrument the community can wield without losing the moral law, provided the discipline is kept - and the discipline is the entire difference.
Q: Is the withdrawal always the right ending?
A: The withdrawal is the right ending whenever the object falls, and the doctrine's exceptions are narrow. The one exception is the verification correction: if the raiders discover, after the raid, that a piece of evidence was wrong, they should correct it publicly, because the correction protects the raid's credibility at the cost of one post. The other exception is the direct question: if the raided community asks, in public, a direct question about the raid's evidence, the raiders may answer once, in the same public place. Beyond those two exceptions, the withdrawal stands, because every additional post gives the raided community the target it needs to organize a counter-campaign.
Q: What is the difference between a raid and a leak?
A: A leak is the publication of private material that was obtained without authorization; a raid is the coordinated publication of evidence, which may or may not be private, on a single day. The raid's doctrine governs the timing and the placement of evidence, not the method by which the evidence was obtained. A raid built on leaked private material is governed by the leaked logs doctrine as well, and the two doctrines must be read together before the raid is planned. The doctrine's counsel is that a raid whose evidence was obtained by a leak is a raid that carries the leak's moral burden, and the burden may outweigh the object.
Q: How does a community prepare for a raid it has been warned about?
A: The warning is the first stage of the raid's failure, and a warned community should do three things. First, it should publish its own accurate account of the contested narrative before the raid lands, so that the raid's evidence contradicts a record that is already public. Second, it should name a single spokesperson, so that the community's response is coordinated rather than improvised. Third, it should decide, in advance, that it will answer evidence, not messengers, and that it will not counter-raid a fair raid. A community that does these three things has converted the warning from a liability into an advantage, because the raid that was announced has already become a siege.
Q: Can a single person conduct a raid, or does it require a team?
A: A single person can conduct a raid, and the doctrine's stages scale down without changing shape. The one-person raid assembles the evidence in silence, chooses the ground, and publishes the simulcast, but it must compensate for its lack of coverage: one person cannot post in five channels at once, so the one-person raid should concentrate on the single channel where the object sits. The doctrine's counsel is that the raid's power is not its numbers but its conditions, and that a single disciplined person following all five stages is stronger than a team that follows two.
Q: What is the relationship between the raid and the doctrine of energy?
A: The raid is the energy doctrine applied to a single day. The energy doctrine teaches that the community stores its force in the quiet season and releases it at the decisive moment; the raid compresses that cycle into two weeks of silent assembly and one hour of release. The raid's simultaneity is the energy doctrine's onset, and its withdrawal is the doctrine's re-bending. The reader who has studied energy will recognize the raid as the campaign's compressed form, and the reader who has studied the raid will find the energy doctrine in its most concentrated expression.
Q: How does the cohort decide which raids are worth recording?
A: The cohort records every raid it can verify, and its selection criterion is the same as its measurement criterion: the object. A raid is recorded when it has a nameable object and a measurable outcome, because those are the two conditions that let the Institute track success and failure. Raids without objects - the unannounced grudge, the indefinite thread, the campaign disguised as a raid - are not recorded as raids, because they did not follow the form the doctrine measures. The criterion is the doctrine's own: if it cannot be named in one sentence, it is not a raid.
Q: Should the raid's evidence be presented in a specific order?
A: The doctrine's answer is that the order is the presentation's argument, and the argument should lead with the strongest verifiable fact. The Cargo Cult raid led with the comparison screenshots, because they were the visual proof that the audience could check immediately, and it laid out the file dates in a table because the table made the dates comparable at a glance. The doctrine's counsel is to structure the raid as the case it makes: the undeniable evidence first, the corroborating detail second, and the conclusion last, so that the reader reaches the conclusion having already accepted its premises.
Q: What is the one mistake that destroys a raid more than any other?
A: The answer the cohort gives is the answered bait, and the reason is that it is the one mistake that undoes the raid without the enemy having to do anything else. A raid that is announced can sometimes still succeed; a raid that publishes sequentially can sometimes still land; but a raid whose planner answers the personal counter-accusation has moved the subject from the evidence to the person, and the evidence is then abandoned in the thread while the community discusses the planner. The doctrine's counsel is that the refusal of bait is the raid's load-bearing discipline, and that the team which can decline the personal attack has kept the evidence as the last word.
Glossary
| Term | Definition as used in this article |
|---|---|
| Raid | The coordinated publication of evidence against a target on a single day, aimed at a single measurable object |
| Object | The thing the raid seeks to take; a narrative, a pin, a pinned account, or another measurable change |
| The simulcast | The simultaneous publication of all raid materials in all chosen channels at a predetermined hour |
| Secrecy of preparation | The condition that nothing of the raid's preparation is visible to the target before the raid lands |
| Rapidity of execution | The condition that the raid's publication window is short enough that the enemy cannot answer in time |
| Concentration of force | The condition that all materials land at once, so the raid reads as an event rather than a trickle |
| The refusal of bait | The discipline of not answering the enemy's response, especially the personal counter-accusation |
| The withdrawal | The raid's final act: ending when the object falls, with no posts after the publication window |
| The occupied field | The enemy's ground, where the raided community outnumbers the raid and controls the terrain |
| The one-hour window | The doctrine's unit for the raid's publication, measured by the time the enemy is given to answer |
| The campaign | The raid's opposite: an indefinite engagement with a broader objective and no single day |
| The counter-raid | A raid conducted by the raided community against the original raiders, using the same instrument |
| The standing response | A protocol, prepared in peacetime, for handling sudden publications against the community |
| The reconstruction | The post-raid review that identifies which condition was violated and what the correct response was |
| The refutation test | The standard that the raid's evidence cannot be dismantled by a single answer |
| The retracted raid | A raid that was withdrawn before publication because the evidence could not survive the answer |
| The simulcast discipline | The habit of publishing everything at once, never leaking pieces in advance |
| The moral law | The community's judgment on how the raid was conducted, decided by the evidence and the withdrawal |
| The boundary | The line between the narrative as object and the person as object, which the raid doctrine refuses to cross |
| The prepared target | A community with standing responses and an accurate record, which retains its narrative at 71% |
| The one-sentence test | The requirement that the object be nameable in one sentence before the raid begins |
| The scarcity warning | The doctrine's finding that the raid draws its power from being rare, and that constant raiding spends it |
Appendix A: The Raid Reference
The raid discipline is read most quickly as a reference table, and the table is the version a community manager can keep with the moderation notes.
| Condition | Chapter | The rule | The failure |
|---|---|---|---|
| Name the object | 8, Variation | One sentence, measurable | A grievance disguised as an object |
| Assemble in silence | 7, Maneuvering | Nothing published before the raid | An announced raid is a siege |
| Choose the ground | 7, Maneuvering | Land where the object sits | Publishing to the already-convinced |
| Execute the simulcast | 7, Maneuvering | All at once, all channels | Sequential publication warns the enemy |
| Refuse the bait | 8, Variation | Do not answer the enemy's response | The answer moves the subject to the person |
| Withdraw at the object | 8, Variation | No posts after the object falls | The occupied battle undoes the victory |
The Target's Checklist
The same conditions, read from the target's side, form the defense checklist.
| The raid's condition | The target's defense |
|---|---|
| Secrecy of preparation | Assume a raid is being prepared; keep standing responses current |
| Rapidity of execution | Publish the community's own account promptly, on the community's own ground |
| The simulcast | Do not answer piece by piece; answer once, with the whole account |
| The refusal of bait | Do not attack the messenger; address the evidence |
| The withdrawal | Do not counter-raid a fair raid; revise the account and move on |
The Failure Modes in One Table
The doctrine's failure modes are its most portable teaching, because each one names the moment a raid goes wrong and the condition that was violated.
| Failure mode | The condition violated | What it costs |
|---|---|---|
| The announced raid | Secrecy of preparation | The target prepares; the raid becomes a siege |
| The trickle | Rapidity and concentration | The enemy answers each piece before the whole appears |
| The wrong ground | The choice of the ground | The evidence is read by the already-convinced |
| The answered bait | The refusal of bait | The subject moves from the evidence to the person |
| The occupying battle | The withdrawal | The raided community organizes and reverses the object |
| The grievance raid | The naming of the object | The raid continues as a campaign; the object was never defined |
The Decision Reference
The raid's decision is compressed to a single question, and the question is the version a community manager can keep at hand.
| The question | The answer that raids | The answer that stands down |
|---|---|---|
| What is the object? | A narrative, named in one sentence | A grievance, or no answer at all |
| Is the evidence verified? | Beyond reasonable dispute | Any doubt at all |
| Who is the audience? | The community that judges the record | A mob that cannot verify |
| Is the enemy prepared? | No standing response in sight | The target has its account ready |
| When does it end? | When the object falls | Never - which is the warning |
Appendix B: The Complete Raid Chain
The chapter's full argument, laid out as the chain the doctrine follows from the decision to raid to the raid's completion.
The chain is read left to right as a single raid and top to bottom as the discipline's whole course. The team that names a measurable object, assembles in silence, chooses the ground, executes the simulcast, refuses the bait, and withdraws at the object has conducted the raid on the doctrine's terms and made its victory permanent. The team that skips any stage - raiding on a grievance, publishing sequentially, answering the bait, staying to argue - is the team the cohort records as the raid that outlived its form, and the record is the price of the order.
The chain is also the answer to the question that opens every case study in the corpus: what should the community have done? For the raiding team, the answer is the five stages, executed in order. For the raided community, the answer is the target's checklist: keep the standing response current, publish the community's own account promptly, answer evidence rather than messengers, and never counter-raid a fair raid. Both answers are the same discipline seen from two sides, and both are the doctrine that turns the raid from an event that happens to a community into an event that a community understands.
The chain's final lesson is that the raid is not an act of aggression but an act of disclosure, and the discipline is what keeps the disclosure clean. The evidence was assembled so that the community could see the pack's origin as the raiders saw it; the secrecy was kept so that the community would see it whole, for the first time, at once; and the withdrawal was made so that the seeing could be followed by judgment rather than by war. A raid that discloses and withdraws has performed the doctrine's whole work in a day. A raid that discloses and stays has begun the argument the disclosure was meant to settle, and the argument is the raid's own reversal.
The Final Verdict
The Cargo Cult raid stands in the corpus as the reference example of the raid conducted on its own terms, and its final verdict is that the doctrine's conditions are the raid's whole strength. No raid in the cohort achieved its object by abandoning the conditions; every raid that achieved its object observed them, and the raids that failed failed at a single stage. The commander who studies the case will find in it the complete instrument: the object named, the evidence verified, the silence kept, the simulcast fired, the bait declined, and the withdrawal made. The community that can conduct a raid this way has learned the instrument without losing the moral law, and the community that can withstand one has learned the defense without panic. Both learnings are the doctrine's purpose, and both are demonstrated in the record of the day the narrative fell.
The chain also names the doctrine's deepest claim about the raid, which is that the raid is a discipline of knowing when to stop. Every stage in the chain is a boundary: the named object bounds the raid's aim, the silent preparation bounds its timing, the simulcast bounds its duration, the refused bait bounds its subject, and the withdrawal bounds its entire existence. The raid is the corpus's instrument of the single day, and it succeeds by being exactly that - not a war compressed, but an engagement that knows it is one day long. The team that keeps every boundary has conducted the raid as the doctrine defines it; the team that drops a single boundary has begun the campaign that the raid was designed to avoid.
The Chain in Prose
The full doctrine can also be read as a chain of five statements, each of which follows from the one before it:
- The raid is the single-day publication of evidence against a measurable object.
- The raid's power is the enemy's ignorance that it is coming, so preparation is silent.
- The raid's force is the simultaneity of its publication, so everything lands at once.
- The raid's object is a narrative or a record, so it ends when the object falls.
- The raid's completion is the withdrawal, so the team posts nothing after the object, and the revision stands.
The chain is the chapter in its most portable form, and the commander who can state the five lines from memory has the doctrine where it is needed most: at the moment a personal accusation lands in the thread and the instinct says to answer it.
The Boundary of the Doctrine: When the Raid Is Wrong
A chapter that trains an instrument must also say when the instrument should not be used, and the raid doctrine draws a boundary it refuses to cross. The raid exists for the contest of narratives and records - the account of a work's origin, the fairness of a decision, the honesty of a claim. It is not written for the attack on persons, and the community that applies the raid's form to a person will not be practicing discipline. It will be practicing harassment.
The boundary has a practical test. The raid's object is a narrative, a record, or a pin - a thing that can be revised, removed, or rewritten. The moment the object becomes a person - their conduct, their character, their employment, their family - the raid has left the doctrine's ground and entered the ground the doctrine explicitly refuses. The Cargo Cult raid's object was the account of the pack's origin, and the counter-accusation about the planner's profit was bait precisely because it tried to move the object from the narrative to the person. The doctrine's counsel is that the raider who cannot keep the object on the record should not raid, and that a team which slips from evidence to person has already lost the moral law, whatever its object.
The boundary also governs the audience. The raid publishes evidence for the community to judge, and the doctrine presumes an audience that can judge. The raid that publishes into a community where the members cannot verify the evidence, or where the publication will inflame rather than inform, has misread the ground. The doctrine's counsel is to ask, before the simulcast, what the audience will do with the evidence: if the honest answer is that it will inform a judgment, the raid is on the doctrine's ground; if the answer is that it will inflame a mob, the raid has crossed the boundary it shares with every doctrine in the corpus.
The Raid Among the Instruments
The raid does not exist in isolation, and the commander who masters it must know where it sits among the corpus's other instruments, because the choice of instrument is the first decision of any engagement. The raid's distinction is the single day: it is the only instrument that compresses an entire engagement into one publication window, and the compression is both its strength and its limitation.
| Instrument | Timeframe | Object | The doctrine's register |
|---|---|---|---|
| The raid | One day | A narrative or a record | Maneuvering, variation |
| The statement war | Weeks | A contested account | The art of the statement |
| The screenshot war | Weeks | A contested image or its context | The art of the screenshot |
| The review war | Weeks | A rating | The review war |
| The smear war | Months | A reputation | The counter-smear war |
| The long siege | Months | A position | The long siege |
The table is read as a scale of commitment. The raid commits one day and takes a narrative; the siege commits months and takes a position. The doctrine's counsel is that the commander should prefer the cheapest instrument that reaches the object, and the raid is the cheapest instrument available for a narrative object - which is why it is the first instrument a commander should consider when the object is a record that can be taken in a day.
The scale also explains the corpus's ordering. The raid appears early in the study because it is the instrument of the single object, and the instruments that follow it - the statement war, the screenshot war, the review war - are the raid's slow forms, applied to objects that cannot be taken in a day. The reader who learns the raid first has learned the discipline in its most compressed shape: the named object, the prepared evidence, the single moment, the clean end. Every slower instrument is that discipline spread over weeks, and the commander who can state the raid's five conditions can recognize the same conditions operating at a slower tempo in every other war in the corpus.
The Raid and the Escalation Ladder
The raid's place on the escalation ladder is also worth fixing, because the raid is frequently misread as an escalation when it is the opposite. The raid is a descent: it takes a smaller object, in a shorter time, with a cleaner end than any campaign. A community that has been conducting a campaign against a rival's narrative has been spending weeks of attention; the raid would have spent one day. The doctrine's counsel is that the raid is the campaign's compressed alternative, and that a community which finds itself in a long engagement over a narrative should ask whether the engagement should have been a raid, and whether it can still be converted into one.
The Raid and the Doctrines It Touches
The raid touches three other doctrines, and the reader who carries all four forward has the complete instrument. The first is Maneuvering, which supplies the raid's character and its secrecy. The second is Variation in Tactics, which supplies the raid's discipline and its blend of advantage and disadvantage. The third is the statement war, which governs what the raided community does after the raid lands, and what the raiding team does if it is forced to speak. The raid is the sudden form of all three, and the commander who has mastered the campaigns can compress them into the raid when the object is small enough to be taken in a day.
The Raider's Aftermath
The case study's final lesson is the raider's own aftermath, which the doctrine treats as part of the raid rather than as an event after it. The Cargo Cult raid's team withdrew after the object fell, and the withdrawal was the raid's last act - but the doctrine also records what the raiders did in the weeks that followed, because their conduct in the aftermath determined whether the raid was remembered as a document or as an ambush.
The raiders' first act in the aftermath was to answer no further bait. The raided community made several attempts to draw the team back into the thread - questions, accusations, invitations to debate - and the team answered none of them. The second act was to link the raid as a completed record: where the team's members discussed the outcome, they linked the raid's permanent record without re-arguing it, treating the raid as a document to be referenced rather than as a war to be continued. The third act was to return to ordinary production, releasing their own work as if the raid had never happened, so that the community's memory of the team was anchored to the work, not to the one day of conflict.
The doctrine's reading of the raider's aftermath is that the aftermath is where the moral law is decided. The raid's evidence decides the immediate outcome; the aftermath decides whether the raiders are trusted in the next engagement. A team that conducts a clean raid and then behaves well in the aftermath is a team whose next raid will be read with the presumption that its evidence is true. A team that conducts a clean raid and then gloats, re-argues, or recruits from the raided community is a team that has spent the moral law the clean raid earned. The doctrine's counsel is that the raid's discipline extends past the withdrawal, into the ordinary conduct that follows, and that the community which wants the raid to remain a document must never let it become a war.
Conclusion
The Cargo Cult Raid is the doctrine's reference example of the raid conducted on its own terms. It was prepared in silence, executed in an hour, aimed at a single narrative, and concluded at the moment the object fell. It demonstrates the doctrine's chapters on maneuvering and variation in tactics as they operate in the field: secrecy, rapidity, concentration, the refusal of bait, and the discipline of the withdrawal.
The case is also the cohort's demonstration that the raid is available to the small community. The raiding team was a handful of members with a document; the raided community was a larger body with a narrative. The raid's power was not the raiders' numbers but their discipline, and the discipline is the doctrine's gift to the community that believes it is too small to act. A small team that names its object, assembles in silence, and publishes at once has done more than a large community that argues for a month, and the cohort's records confirm that the prepared few have always been the raid's natural authors.
The case also demonstrates the doctrine's deepest claim about the raid, which is that the raid is a discipline of restraint as much as a discipline of force. The raiding team's power lay not in what it published but in what it declined to publish afterward: the answers, the rebuttals, the follow-ups that would have turned the raid into a war. The raid succeeded because it knew when it was over, and it was over the moment the object fell. Every condition the doctrine names - the named object, the silent preparation, the simultaneous publication, the refused bait, the clean withdrawal - is a form of that restraint, and the team that observes it has conducted the raid the way the doctrine intends.
The raid is one instrument among the doctrine's many. The next documented example, Example: The Forked Repository, documents a campaign of a different shape entirely: not the sudden raid but the flanking war of position, conducted over months.
For the community-management foundation that underlies all drama engagement, see Why Discord Embeds Are the Foundation of Server Credibility.