The Art of the Screenshot: The Documentary Weapon

Advanced40-60 minutesCross-platformDiscordSteam Workshop

The drama war is fought in screenshots. A Discord message, frozen in a PNG, becomes evidence, accusation, and verdict in one stroke. The screenshot is the primary munition of community conflict, and the party that understands its capture, its preservation, and its timing holds the documentary high ground before a single word is exchanged.

All warfare is based on deception.

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

The screenshot is a perfect surface for the doctrine's first law. A screenshot presents itself as an unmediated record of what was said - and that presentation is itself a deception, because every screenshot is a crop, a choice of moment, and a frame. The same Discord message can be captured as an admission or as a joke depending on the line where the capture begins and ends. The community believes the screenshot because the screenshot looks like truth. That is why it is the drama war's dominant weapon, and why the discipline of reading screenshots is the doctrine's most practical skill.

This article is a full treatment of the documentary weapon: the two categories of capture, the discipline of the archive, the timing of release, the lure, the doctored capture, and the discipline of reading the enemy's screenshots against the doctrine's questions. It closes with the Yamak Institute's forensics cohort data, a five-stage protocol for the documentary engagement, the ten most common objections to the screenshot doctrine, and the reference material a community manager needs before the first capture of the war.

The reader should note at the outset that this article treats the screenshot as a weapon and a discipline, and that both readings are required. The weapon reading is the practical one: the screenshot decides engagements, and the party that understands its capture, preservation, and timing holds the high ground. The discipline reading is the defensive one: the community that treats the screenshot as a document to be believed is the community that is defeated by every crop, while the community that treats it as a frame to be verified is the community that no crop can ambush. The two readings are one art, and the art is the subject of this chapter.

Prerequisites

• An understanding of community conflict and the surfaces on which it is fought
• Familiarity with Discord's message history, channel structure, and timestamps
• A working understanding of the statement, which the screenshot either confirms or contradicts
• Willingness to treat the screenshot as a weapon to be disciplined rather than an artifact to be believed

What You Will Learn

• Why the screenshot is the drama war's primary munition
• The two categories of the documentary weapon and the discipline of each
• How the archive is built before the war, not during it
• The three windows of release and the reserve discipline of the held capture
• The lure-screenshot and how to refuse the bite
• The doctored capture and the discipline of counter-evidence
• The five questions of reading an enemy's screenshot
• The Yamak Institute's forensics findings on construction and metadata
• A five-stage protocol for the documentary engagement

The Two Categories of the Documentary Weapon

The screenshot corpus divides cleanly into two categories, and the commander must be fluent in both.

Category	What it is	Example
The genuine capture	An unedited record of a real message	A real moderation log
The constructed capture	A crop, a staged moment, or an edit	A DM cropped to remove context

The doctrine does not moralize about the constructed capture - it analyzes it. Both categories are weapons; the question is which side of the weapon you are standing on. The discipline of capture protects you from the constructed captures aimed at you, and the discipline of reading protects you from being surprised by the genuine captures you forgot existed.

The Genuine Capture

The genuine capture is an unedited record of a real message, and its power is that it is true. A real moderation log, a real DM, a real announcement - each is a fact that the community accepts at face value, and each is the hardest document in the war to answer, because the answer must be a fact that outranks it. The genuine capture is the enemy's most dangerous weapon not because it is edited but because it is not: it cannot be dismissed as a forgery, and the community that tries to dismiss it discovers that the dismissal converts a documentary loss into a credibility one.

The genuine capture's danger is precisely that it is genuine. A real message captured at the wrong moment, a real decision quoted without its season, a real sentence lifted from its thread - the capture is true, and the frame it is placed in is false. The community that answers the genuine capture by attacking the capture loses; the community that answers it by producing the wider frame wins. The doctrine's discipline of the archive exists for this moment: the genuine capture has a counterpart in the archive, and the counterpart is the fuller frame that the crop was cut from.

The Constructed Capture

The constructed capture is a crop, a staged moment, or an edit, and its power is that it is believed. The community accepts screenshots as truth, so the constructed capture is a forged verdict that has already been passed before it is examined. The crop is the most common form: a DM cropped to remove the context, a thread cut above the answer, a message presented without its predecessor. The staging is the second: a channel arrangement made to look like a decision, a message written into a position it did not hold. The edit is the third and rarest: the fabricated log, the rearranged message, the inserted line.

The doctrine does not moralize about the constructed capture because the commander must understand it from both sides: to recognize it when it is aimed at you, and to avoid it when you are tempted to use it. The constructed capture is a weapon that turns on its wielder, because the archive that proves it constructed is usually sitting in the target's hands. The community that constructs a capture has given the enemy a documentary counter that ends the war in one frame.

The constructed capture is also the category with the shortest shelf life, and the doctrine records the fact as the forger's standing risk: the community accepts screenshots as truth, but the community's acceptance is not permanent. A construction that survives a day is exposed by the archive the moment the original surfaces; a staging that holds for a week collapses the moment a member who was present posts the true version. The forger's window is measured in hours, and the hours are the archive's. The doctrine's counsel is therefore not to construct, but to know the construction - the commander who can recognize the crop, the stage, and the edit is the commander who can answer them, and the recognition is the discipline that costs nothing and prevents everything.

The Category in Operation

The two categories are not equally dangerous to every community, and the commander who knows which category the enemy will use knows which discipline to prepare. The genuine capture is the weapon of the insider - the ex-member, the disaffected moderator, the former ally who has the real logs. The constructed capture is the weapon of the outsider - the rival team, the reviewing faction, the enemy who must manufacture what the insider can take for free. The doctrine's counsel is to prepare for the weapon the enemy can actually field: the community that has just expelled a moderator should expect the genuine capture and build the archive against it, while the community that has just won a feud should expect the constructed capture and build the forensics against it. Each category has its own defense, and the defenses are built in the calm.

The Category Shift

The two categories are not fixed, and the doctrine records the shift as one of the documentary war's quietest weapons: the same message can cross from genuine to constructed, and back, as the frame moves. A message that is genuine in its thread becomes constructed when it is cropped from it; a message that was staged can become genuine when the staging is archived. The shift is the enemy's opportunity and the commander's discipline: the enemy who can make the community's genuine line look constructed has made the community's archive suspect, and the community that can make the enemy's constructed capture look genuine has made the enemy's whole documentary surface suspect.

The doctrine's reading of the shift is the reading of the frame, applied to both directions. The genuine capture that the enemy has reframed is answered by the wider frame, which restores the line's true context; the constructed capture that the enemy has laundered - released through the neutral channel, quoted by the surprised third party - is answered by the original, which restores the line's true text. The community that understands the shift never assumes the category is fixed, because the category is decided by the frame, and the frame is decided by whoever holds the fuller one. The commander who holds the fuller frame can move the category in either direction, which is the documentary war's whole field of play.

The Capture: Archives Are Armor

To secure ourselves against defeat lies in our own hands, but the opportunity of defeating the enemy is provided by the enemy himself.

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

The commander who has archived everything cannot be defeated by a screenshot, because every screenshot the enemy produces has a counterpart in the archive that shows the fuller frame. The discipline of capture is the discipline of never allowing a message to exist that could not be produced in public - the permanent assumption that any channel can be captured at any moment by anyone.

Documented example

Example 130: The Context Cut. A rival team released a screenshot showing a moderator writing "that pack is dead content" in a private channel, presented as an insult to a popular author. The moderator's team produced the fuller archive: the same sentence appeared in a thread where the author himself had called the pack retired, and the moderator was agreeing with the author's own phrasing. The constructed capture collapsed within a day. The Institute codes this as the archive at work - the genuine capture defeated by the wider frame.

The discipline of capture has a second component: preserve the timestamps, the channel names, and the surrounding context. A screenshot without its metadata is a weapon with the safety on - it can be reversed by a single line of missing context. The archive is built continuously, before the war, not during it.

The Archive Built Before the War

The archive is the community's documentary armor, and armor is forged before the battle. The community that begins archiving when the first accusation lands has begun building the defense against a screenshot that has already been taken; the community that began archiving in the calm has the fuller frame ready before the enemy's capture is released. The doctrine's rule is absolute: the archive is built continuously, before the war, not during it, because the war arrives with its screenshots already taken and its frames already cut.

The archive's shape follows the community's risk. The moderation channels are archived because they are the most quoted surface - every ban, every warning, every decision recorded with its reasoning. The announcement channels are archived because they are the community's public voice - every statement recorded with its date, so that a later "you never said" can be answered with the announcement. The planning channels are archived because they are the most misquoted - every plan recorded with its owner, so that a leaked fragment can be replaced by the whole plan. The private DMs of the leadership are archived by practice rather than by tool: the standing rule that anything said in private should be sayable in public, because the private channel is a channel, and any channel can be captured.

The Metadata Discipline

The capture is judged by its metadata, and the metadata discipline is the second half of the archive. A screenshot without its timestamps, its channel header, and its surrounding context is a weapon with the safety on - it can be reversed by a single line of missing context. The discipline has three parts, and each is practiced until it is reflex:

Metadata element	What it establishes	What its absence costs
The timestamp	When the message was sent	The message can be placed in any season
The channel header	Where the message lived	The message can be placed in any context
The surrounding lines	What the message answered	The message can be read as any claim
The user ID	Who sent it	The message can be attributed to anyone

The discipline applies to the community's own captures as well as the enemy's. The commander who photographs a hostile message records the timestamp, the channel, and the surrounding lines in the same breath, because the capture without the metadata is the capture that the enemy will reframe. The archive's value is not the number of screenshots it holds; it is the completeness of the frame each screenshot preserves. A hundred captures with metadata are armor; a thousand bare captures are noise.

The Capture's Own Discipline

The archive protects the community, but the capture's own discipline governs what the community says. The doctrine's standing assumption is that any channel can be captured at any moment by anyone - the community's own members, the enemy's members, the lurkers who joined months ago and never spoke. The assumption converts every message into a potential screenshot, and the conversion is the discipline: never write a message in a channel that could not be produced in public, never make a decision in a DM that could not survive the moderation log, never rely on a private channel being private.

The capture's own discipline is the hardest of the chapter's disciplines, because it is practiced in the moment, under the pressure of the argument, when the impulse to say the true thing in the private channel is strongest. The doctrine does not ask the commander to say nothing; it asks the commander to say nothing that would need to be unsaid. The message that survives the standing assumption is the message that can be captured without damage, and the community that writes only such messages has made its own archive a weapon that the enemy cannot load.

The Archive of the Small Community

The small community often believes the archive is a luxury of the large - that archiving requires staff, tools, and a scale its handful of moderators cannot reach. The doctrine's answer is that the archive is a discipline, not a budget, and the small community is the one that needs it most. A large community's messages are a sea that the enemy must fish; a small community's messages are a handful of channels where every line is known, quotable, and memorable. The small community's screenshots travel further relative to its size, because the scene's interest in a small community's collapse is out of proportion to its membership, and the collapse is narrated in captures.

The small community's archive is built with the tools it already has: the exported channels, the saved threads, the standing rule that the leadership's decisions are made in writing. The discipline does not require software; it requires the habit, practiced by the three or four people who run the community, of never letting a quotable message exist without its fuller frame. The small community that keeps the habit has armor out of proportion to its staff; the small community that skips it has exposed every line it ever wrote, and the exposure is the enemy's entire case.

The Failure Mode of the Partial Archive

The archive that is kept partially fails in a characteristic way: the community is defended against the screenshots it predicted and vulnerable to the ones it did not. The community that archives its moderation log but not its planning channel is ready for the ban dispute and defenseless against the leaked plan. The community that archives its announcements but not its leadership's DMs is ready for the "you never said" and defenseless against the "you privately agreed". The partial archive is worse than no archive in one respect: it gives the community the confidence of armor without the coverage of it, and the confidence sends it into the documentary war unguarded where it believes itself armored.

The doctrine's counsel is to audit the archive's coverage in the calm, against the standing question: what would the enemy need to produce to hurt us, and is the fuller frame of that document in our hands? The audit is uncomfortable precisely because it finds the gaps - the planning channel that was never exported, the moderator who deleted their DMs, the announcement that was edited without a record. Each gap found in the calm is a repair made before the war; each gap discovered during the war is a frame surrendered that the enemy is already quoting.

The Documented Example of the Moderation Log

The archive's defense is best shown in the community's most quotable surface: the moderation log. The Institute's field records contain a case that the doctrine teaches as the moderation log at work. A server banned a prominent member for harassment, and the ban was issued with its reasoning in the moderation channel. The banned member, seeking to convert the ban into a grievance, released a single line of the log - the decision sentence, cut from its reasoning - as evidence that the ban was a personal vendetta. The server produced the full log: the reported messages, the warnings issued in sequence, the appeal the member had declined. The constructed capture collapsed within a day, and the member's grievance campaign ended with its own evidence reframed against it.

The case is the archive in miniature, and its lesson is that the moderation log is the community's most valuable documentary asset precisely because it is the surface the enemy quotes first. The log that records its decisions with their reasoning is the log that can be produced whole; the log that records only the outcome is the log that the enemy can reframe. The community that treats the moderation log as its documentary crown jewel - exported, preserved, and produced at the first cut - has made the surface the enemy would most like to capture the surface the community holds most completely.

The Timing of Release

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

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

The screenshot's power depends on its timing more than its content. A genuine capture released at the wrong moment is a damp squib; a constructed capture released at the right moment is a war. The doctrine's rule of release is drawn from the same chapter that governs all attack: release where the enemy is unprepared, appear where he is not expected.

The three windows of release:

• The preemptive window - publish before the enemy's narrative forms, to balk his plans. Discussed in The Art of the Statement.
• The responsive window - publish when the enemy has committed to a narrative the capture contradicts.
• The victory window - publish when the engagement is already turning, to confirm the turn.

The commander who releases all his evidence at once spends his whole arsenal on one shot. The doctrine's reserve discipline applies to screenshots as to troops: the capture that is held in reserve is the capture that still threatens.

Documented example

Example 143: The Staged Negotiation. Two teams entered a public negotiation over a disputed asset. One team had captured a private message from the other's lead admitting the asset was borrowed "without asking, we just used it." Rather than publishing immediately, the team waited until the negotiation had formally concluded, then released the capture - converting a settled dispute into a demonstrated untrustworthiness. The Institute's coding note: the release was timed to hit after the enemy was unprepared, expecting no further attack.

The Preemptive Window

The preemptive window opens before the enemy's narrative forms, and its object is to balk his plans. The community that knows an accusation is coming - that the enemy is assembling the screenshots, the framing, the campaign - publishes its own version of the record first, so that the enemy's narrative arrives into a frame already set. The preemptive release is the documentary form of the first strike: it does not answer the enemy's claim, because the claim does not exist yet; it occupies the ground on which the claim would have landed.

The preemptive window's discipline is the accuracy of the preemptive capture. A preemptive release that is rushed, partial, or wrong hands the enemy the rebuttal he needed: the enemy's campaign arrives not into a frame but into a correction, and the correction becomes the campaign's first evidence. The doctrine's counsel is that the preemptive window is opened only with a capture that can survive its own scrutiny - the complete frame, the metadata intact, the record unassailable - because the preemptive release is the community's own opening move, and the opening move is the one the enemy will attack first.

The Responsive Window

The responsive window opens when the enemy has committed to a narrative the capture contradicts, and its object is the enemy's commitment itself. The enemy who has published the accusation, named the parties, and staked the campaign on the claim has made a commitment that he cannot retract cheaply, and the counter-capture that lands after the commitment converts the commitment into the contradiction. The capture that would have been answered as a rumor if released early is answered as a betrayal if released after the enemy's story is fixed.

The responsive window's discipline is the patience to wait for the commitment. The community that releases the counter-capture the moment the accusation appears has answered a narrative that was still forming and may still be abandoned; the community that waits until the enemy has repeated the claim, built the campaign on it, and committed his allies to it has released the capture into a position that cannot be abandoned without loss. The doctrine's reserve discipline governs the waiting: the capture is held in reserve, the threat of it does its work quietly, and the release is timed to the moment of the enemy's maximum commitment, which is the moment of his maximum exposure.

The Victory Window

The victory window opens when the engagement is already turning, and its object is to confirm the turn. The capture released as the community's position is winning does not need to be decisive; it needs to be final. It is the documentary stroke that converts a contested dispute into a settled record, giving the neutrals a reason to stop following and the community's own side a reason to stop fighting. The victory window is the window of the closing statement, and its captures are the closing document's evidence.

The victory window's discipline is the restraint not to overspend it. The community that has won the engagement does not need to release every capture it holds; it needs to release the ones that settle the record, and then stop. The release of the winning evidence in a stream, drip by drip, converts a settled victory into an ongoing demonstration, and the ongoing demonstration revives the engagement the victory window was meant to close. The doctrine's counsel is that the victory release is the last release: the record is settled, the turn is confirmed, and the archive closes over the war.

The Reserve Discipline of the Screenshot

The reserve discipline is the doctrine's rule of the held capture, and it governs the whole campaign. The commander who releases all his evidence at once has spent his whole arsenal on one shot; the commander who holds a capture in reserve has a threat that outlives every released one. The held capture is the capture that still threatens - the enemy does not know what the community holds, so the enemy must price the possibility of everything, and the pricing of everything is more expensive to the enemy than the release of one.

The reserve's power is that it is never spent, and the doctrine records its most elegant form: the capture that is never released at all. The enemy who believes the community holds the damaging document moderates his behavior without the document ever appearing; the community that releases the document gets one victory, while the community that holds it gets a season of the enemy's caution. The reserve discipline does not require the community to hoard its evidence against a better moment; it requires the community to know that the unspent capture is a standing asset, and to spend it only when the victory it buys is worth the threat it retires.

The reserve also has a season, and the doctrine requires the commander to read it as carefully as the window. A capture held past the engagement it would have settled has outlived its value: the threat that was relevant in the war is the museum piece after it, and the museum piece, released years later, reads as the grudge the community was supposed to have retired. The doctrine's counsel is that the reserve is reviewed at the same cadence as the archive - what is held, why it is held, and whether the engagement it was held for still exists - and that the capture whose engagement has passed is retired, archived, or released in the victory window that gives it meaning. The reserve that is never reviewed is the grudge that never closes, and the grudge is the next war's opening.

The Failure Mode of the Early Spend

The doctrine names the failure of the reserve as clearly as its power: the community that releases its captures early, in the order of its anger rather than the order of its plan, spends its documentary arsenal on the engagements that did not need it. The early spend has a characteristic sequence. First, the community answers a minor provocation with a major capture, winning the skirmish and retiring the document. Second, the enemy, learning the community's pattern, provokes again - and the community releases the next capture, winning again and retiring the next document. Third, the real engagement arrives, and the community reaches for the capture that would have settled it, and finds the archive exhausted.

The early spend converts the community's documentary armor into a series of small victories, each of which was bought with the armor the large battle needed. The doctrine's counsel is the reverse discipline: release the small capture for the small engagement only when the small engagement cannot be won without it, and hold the large captures for the engagements that justify them. The community that spends in the order of the plan rather than the order of the provocation is the community whose archive is never empty when the war is real, and the empty archive at the real moment is the cost that the early spend never shows until it is paid.

The Window and the Audience

The timing of release has a third variable that the doctrine places beside the enemy's commitment: the audience's attention. A capture released when the community's audience is absent is a capture released into an empty room, whatever its window; a capture released when the audience is watching is a capture that lands in front of the judges it was meant to move. The audience's attention follows the community's own calendar - the update season, the event night, the announcement hour - and the commander who reads the window reads the audience's presence as part of the moment.

The audience reading modifies the three windows without replacing them. The preemptive window is opened when the audience is present to receive the frame; the responsive window is timed so that the enemy's commitment and the audience's attention arrive together; the victory window is the window of the audience already watching the turn. The doctrine's counsel is that the commander reads the clock and the opponent together: the release that is timed to the enemy's exposure but lands in the community's empty season has spent its force on no audience, and the release that lands in the full season has found the judges it was built to move. The window is where the enemy's position and the audience's presence meet, and the meeting is the moment.

The Screenshot That Is a Lure

The doctrine's deepest reading of the screenshot is the lure - the capture deliberately released to provoke a response that reveals the responder's position.

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

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

When some are seen advancing and some retreating, it is a lure.

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

A lure-screenshot is released with a flaw visible: a half-redacted name, an incomplete crop, a contradictory pair of messages. The enemy, believing the flaw to be an oversight, attacks the flaw and in doing so reveals the extent of his own knowledge - that he knows the context the flaw omits, that he has his own captures, that he is prepared. The commander who bites the lure reveals his whole position for the price of one screenshot.

The Lure's Architecture

The lure is constructed backward from the reaction it wants, and the doctrine requires the commander to read the construction before reading the screenshot. The bait's visible flaw is its first element: the half-redacted name, the incomplete crop, the contradictory pair - each is placed to be noticed, because the flaw is the hook. The flaw is designed to be irresistible: the target believes it has caught the enemy in a mistake, and the belief is the bait's engine, because the target attacks the mistake with the full confidence of having found it.

The lure's second element is the position it wants exposed. The enemy releases the flawed capture to learn something specific: whether the target knows the context the flaw omits, whether the target holds its own captures of the same exchange, whether the target is prepared for the next engagement. The target's attack on the flaw answers exactly those questions - the correction reveals what the target knows, the insistence reveals what the target holds, the anger reveals what the target fears. The doctrine's reading rule is the reverse: the commander who asks what the enemy would learn from a response to this flaw has read the lure before the bite.

The lure's architecture is read in its placement as well as its construction, and the placement is the third element the commander watches. The lure is released where it will be seen by the target and its audience together - the shared channel, the public thread, the announcement the target must answer - and the placement is the choice of pressure point. The lure posted in the empty corner of the community is not a lure; it is a message that failed. The lure posted in the crowded channel, timed to the target's active hour, framed to demand a reply - that is the lure, and the crowding, the timing, and the demand are the architecture's tell. The commander who reads the placement asks who is meant to see the response, and the answer is the battlefield the lure is fighting on.

The Failure Mode of Biting the Lure

The bite is the doctrine's most common failure of the documentary engagement, and it is worth a full account because it is so reliably staged. The community receives the flawed capture; the flaw is visible; the community attacks it, corrects it, or exposes it; and in the correction the community reveals the very knowledge the enemy placed the bait to extract. The reveal is not always immediate. The enemy may file the reveal for the later engagement, holding it until the moment when the revealed knowledge becomes the enemy's advantage.

The bite's cost is the community's position, and the doctrine records the position in three parts. The first is the knowledge revealed: what the community knows, holds, and prepares, answered by the enemy's questions without a single question being asked. The second is the discipline revealed: the community that bites the lure has demonstrated that it cannot sit on its hands, and the demonstration is the enemy's standing license to bait it again. The third is the credibility spent: the community that attacks a lure it cannot prove is a lure has begun a dispute over a screenshot the enemy can abandon at will, and the abandoned dispute leaves the community arguing with no opponent. The doctrine's counsel could not be plainer: the lure is logged, not answered, and the log is the community's only expenditure.

The Counter-Lure

The doctrine reads the lure from the other side as well, and the counter-lure is the commander's own instrument for the documentary engagement. The counter-lure is a capture deliberately released with a flaw, designed to provoke the enemy into revealing his own position - what he knows, what he holds, what he prepares. The counter-lure is the doctrine's deception applied to the documentary weapon, and it is governed by the same discipline as every other bait: it is used sparingly, on an enemy that is already disposed to bite, and it is never used at all if the flaw could be read as a genuine mistake.

The counter-lure's danger is the one the doctrine records most often: the bait that is mistaken for a real capture, or the real capture that is mistaken for a bait. The commander who releases a genuine document with a genuine flaw has handed the enemy a real weapon wearing a lure's clothing, and the enemy who does not bite the flaw will simply use the document. The doctrine's discipline of the counter-lure is therefore the discipline of the verifiable document: the counter-lure is constructed so that its flaw is provably a bait and its content is provably harmless, and the provability is the difference between the lure and the leak.

The Lure of the Friendly Leak

The lure has a form that the commander must name separately, because it exploits the community's own trust rather than its temper: the friendly leak. The enemy arranges for a capture to reach the community through a channel it trusts - a shared moderator, an allied server, a member with friends on both sides - and the capture arrives with the warning that "someone is trying to help you" or "I found this and thought you should know." The friendly leak is the lure wearing the cloak of the ally, and its flaw is placed so that the community, believing the source friendly, attacks the revealed target without suspicion.

The friendly leak's danger is that it weaponizes the community's own loyalties: the moderator who passes the capture believes he is helping, the member who forwards it believes she is warning, and the community that bites the lure exposes its position while thanking the channel that delivered the bait. The doctrine's reading rule applies with extra force: the source of a capture is part of its metadata, and the capture that arrives from a friendly source is examined with the same suspicion as the capture that arrives from the enemy. The ally who passes the damaging document unexamined is either naive or deployed, and the community that thanks the messenger before verifying the message has already begun the bite. The friendly leak is logged like any other lure, its source is noted in the archive, and the verification runs before the gratitude.

The Failure Mode of the Counter-Lure

The counter-lure has a failure mode that the doctrine names as distinctly as the bite, and it is the failure of the commander who falls in love with his own bait. The counter-lure is released, the enemy declines to bite, and the commander, convinced that one more flaw will draw the response, releases another - and then another. Each unbit bait reveals a little more of the community's own position: the commander's patience, the community's resources, the shape of what the community is willing to spend to provoke a reaction. The enemy who refuses the first counter-lure and watches the second, third, and fourth arrive has learned more from the refusal than any bite would have revealed.

The doctrine's discipline of the counter-lure is therefore the discipline of the single cast. The bait is released once, and the refusal is read as the answer: the enemy does not bite, the counter-lure's season is over, and the community returns to its archive and its reserve. The commander who releases the counter-lure twice has told the enemy that the community cannot stop trying to provoke a response, and the telling is the reveal that the whole bait was built to extract. The counter-lure is an instrument of the documentary engagement, and like every instrument it is used once and put away, because the enemy who is shown the instrument's whole shape has been given the plan.

The Doctored Screenshot and the Counter-Evidence

The doctored screenshot - the edited crop, the rearranged message, the fabricated log - is the drama war's forgery. It is deployed because it works: the community accepts screenshots as truth, so a forged screenshot is a forged verdict. The doctrine's response is counter-evidence, not counter-accusation.

If we know that the enemy is open to attack, but are unaware that our own men are in a condition to attack, we have gone halfway towards victory.

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

The counter-evidence is the archive and the metadata. When a doctored screenshot appears, the commander produces the original message, the timestamp, the surrounding context, and lets the comparison do the work. What he does not do is accuse the forger in the same breath, because the accusation converts the evidence exchange into a mudfight where both screenshots become equally suspect to the casual reader.

Did you know?

The Yamak Institute's documentary forensics unit, which examines screenshots submitted in community disputes, estimates that 23% of screenshots in serious engagement evidence bundles show signs of construction - cropping that removes context, or message reordering. It further records that screenshots which include full channel headers, timestamps, and user IDs survive forensics at nearly four times the rate of bare captures. The metadata is the document's signature.

The Forensics of the Doctored Capture

The doctored capture is examined by forensics, and the forensics are available to any community that knows what to look for. The crop is the easiest construction to detect: the cut line, the missing lines above and below, the sentence that begins without its subject. The reordering is harder: the messages rearranged into a sequence they did not hold, the reply placed above the message it answered, the thread cut and rejoined. The fabrication is hardest of all: the log that was never a log, the message that was never sent, the channel that never existed.

The doctrine's forensics are not technical; they are comparative. The doctored capture is exposed by the archive, because the archive holds the original from which the crop was cut. The commander who holds the original thread, the original timestamp, the original channel header can place the doctored capture beside the truth and let the comparison testify. The forensics do not require software. They require the archive, which is the same armor the chapter has required from the beginning: the community that has the fuller frame is the community that can prove the crop, whatever software the enemy used.

The Counter-Evidence Discipline

The response to the doctored capture is counter-evidence, and the counter-evidence discipline governs how it is produced. The commander produces the original message, the timestamp, the surrounding context, and presents them without commentary, because the comparison is the argument and the commentary would only dilute it. The counter-evidence is laid out in the community's own ground - its announcement channel, its archive - and the enemy's capture is placed beside it, frame against frame, and the audience is left to draw the conclusion that the frames make unavoidable.

The counter-evidence discipline has a second rule, and it is the rule the doctrine weighs most heavily: the commander does not accuse the forger in the same breath. The accusation converts the evidence exchange into a mudfight, and in the mudfight both screenshots become equally suspect to the casual reader - the enemy's forged one and the community's genuine one. The doctrine's counsel is to let the comparison accuse, because the comparison's accusation is the one the audience makes for itself, and the audience's own conclusion is the one it believes. The commander who presents the frames and says nothing has made the enemy the one who must explain, which is the position every forger fears most.

The Failure Mode of the Counter-Accusation

The doctrine's warning about the counter-accusation is worth a full account, because it is the most common way a documentary victory becomes a credibility loss. The community receives the doctored capture, produces the counter-evidence, and then adds the accusation - "this is a forgery, and everyone knows who made it" - and the addition converts the presentation into a fight. The enemy, accused, does not defend the forgery; it attacks the accuser, and the attack shifts the ground from the evidence to the mud, where the forgery's maker and the community's evidence are judged together by an audience that cannot tell them apart.

The counter-accusation's cost is measured in the audience's trust. Before the accusation, the audience was examining the evidence; after it, the audience is choosing sides. The community that wanted the evidence to settle the dispute has made the dispute a contest of loyalties, and the contest of loyalties is exactly the ground on which the forger is strongest, because the forger has no evidence to defend and every loyalty to marshal. The doctrine's counsel is the discipline of the silent comparison: present the frames, let the audience conclude, and reserve the accusation for the cases where the forgery is provable to the point where the accusation itself is evidence. The provable accusation is rare, and the rare accusation is the one that lands.

The Counter-Evidence Bundle

The counter-evidence is assembled as a bundle, and the bundle's composition is the counter-evidence discipline in its practical form. The bundle contains four documents, and each is prepared before it is needed. The original message is the bundle's first document - the full text, not the crop, with its line breaks and its place in the thread. The timestamp is the second - the exact time of the message, which fixes the message in its season and defeats the reordering. The channel context is the third - the thread, the channel header, and the surrounding lines, which restore the frame the crop removed. The archive cross-reference is the fourth - the note of where the fuller frame lives in the community's own archive, so that the bundle is a pointer to the armor rather than a copy of it.

The bundle is assembled in the calm, when the moderation log is archived and the planning thread is saved, and it is assembled for every surface the enemy might quote. When the doctored capture arrives, the community does not draft the counter-evidence from memory; it produces the bundle that was prepared for exactly this frame. The commander who has the bundle prepared has reduced the documentary engagement to a presentation; the commander who drafts the counter-evidence under fire is the commander who discovers, at the worst moment, that the original was never exported and the thread was never saved. The bundle is the archive made ready, and the ready archive is the one that answers.

The Discipline of Reading Screenshots

The final skill of the art of the screenshot is reading the enemy's captures against the doctrine's questions. Before responding to any screenshot, the commander asks: What is cropped? What came before? What came after? Who is the intended audience? What response is this capture trying to produce?

The art of war teaches us to rely not on the likelihood of the enemy's not coming, but on our own readiness to receive him.

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

The commander who is ready to receive a screenshot - who has archived his own messages, preserved his own metadata, and rehearsed his response to the likely captures - cannot be ambushed by the documentary weapon. The screenshot only wounds the unready. That is the whole art: the enemy's ammunition is your archive, and your archive is built before the war begins.

The Five Questions in Practice

The doctrine's five questions are the reading instrument, and each is answered before the response is drafted. The first question - what is cropped - is answered against the archive: the community checks its own record of the message and finds the lines the capture omits. The second and third - what came before, what came after - are answered against the thread: the capture is placed back into the conversation it was cut from, and the frame is restored. The fourth question - who is the intended audience - is answered by the capture's placement: where it was posted, whom it names, which community it is meant to move.

The fifth question - what response is this capture trying to produce - is the reading's culmination, and it is the question that turns the screenshot from a document into a weapon being aimed. The capture that demands a correction is trying to make the community correct it; the capture that demands an apology is trying to make the community apologize; the capture that demands an explanation is trying to make the community explain. The doctrine's reading is that the demanded response is the response the enemy cannot get without the capture, and the community that answers the demand has delivered the enemy his object. The five questions end where the discipline begins: the community reads the capture, names the demand, and decides, from the doctrine rather than from the provocation, whether the demand is worth answering.

The five questions are asked in writing, and the writing is part of the discipline. A reading that lives only in the commander's head can be revised by the commander's temper between the capture and the response; a reading that is written down is fixed, and the fixed reading is the one that survives the hour of the reply. The doctrine's counsel is the moderation-team practice: the reading is drafted as five short answers - cropped: what; before: what; after: what; audience: who; wanted: what - and the drafting is the pause that the verification habit requires. The team that writes its readings drafts its responses from a document; the team that reads in its head drafts from its reaction, and the reaction is the enemy's standing opportunity.

Reading for the Lure

The reading discipline has a specific application to the lure, and the commander who reads the enemy's captures against the fifth question will recognize the bait before the bite. The lure is the capture whose visible flaw is too convenient, whose demand for response is too sharp, whose timing is too precisely placed at the community's weakest hour. Each element is the fifth question's answer written in the construction: the flaw is the demand for a correction, the convenience is the demand for the target to believe itself clever, the timing is the demand for the response to come at the enemy's chosen moment.

The reading for the lure is the discipline of suspicion held until the capture is verified. The community that reads every screenshot as a possible lure verifies each one against the archive before responding, and the verification is the bite's counter: the lure that is verified against the archive collapses, because the flaw the enemy planted is answered by the fuller frame the archive holds. The community that reads every screenshot as fact skips the verification and answers the lure, and the answer is the reveal the lure was built to extract. The discipline of reading is the discipline of the verification habit, and the habit is the difference between the community that is photographed and the community that photographs.

Reading for the Frame

The reading discipline ends with the frame, and the frame is the capture's widest context: not the message, but the campaign. Every screenshot in a drama war is released into a campaign - the enemy has an objective, a timeline, and a sequence of documents, and each screenshot is one frame of the sequence. The commander who reads the single capture without the campaign is reading a frame out of its film; the commander who reads the campaign can place the capture on the enemy's timeline and see the next frame before it is released.

The frame-reading is the doctrine's final skill because it is the one that requires the whole chapter. The community that has archived, preserved its metadata, timed its releases, refused its lures, and answered its forgeries with counter-evidence has the material to read the campaign; the community that has done none of it is reading frames it cannot place. The frame is the campaign's logic, and the campaign's logic is the enemy's design, and the enemy's design is the thing the screenshot was always serving. The doctrine's deepest claim about the documentary weapon is that it is never the message. It is always the frame, and the commander who reads the frame has read the war.

Reading for the Campaign

The frame-reading has a practical form, and the doctrine calls it the campaign reading: the placement of the single capture on the enemy's documentary timeline. The enemy releases captures in sequence - the accusation, the corroboration, the escalation - and each capture is a frame of the sequence, designed to arrive at the moment the previous frame has done its work. The commander who reads the sequence can anticipate the next frame: the accusation that lands after the corroboration is the accusation the corroboration was released to support, and the commander who knows the sequence knows what the enemy will produce before the enemy produces it.

The campaign reading has one guard, and the doctrine states it plainly: the commander does not answer the predicted frame before it arrives. The community that drafts the response to the enemy's probable next capture has drafted a response to a capture that may never come, and the premature draft is the premature release, spent on the enemy's speculation rather than the enemy's act. The campaign reading is for preparation, not for preemption: the commander reads the sequence, prepares the archive's answer, and waits for the frame that justifies the release. The enemy's documentary campaign is a film, and the commander who has read the film does not shout the ending before the projector runs; he holds the frames and releases them in the enemy's own order, which is the only order the enemy cannot defend.

Reading the Community's Own Captures

The reading discipline applies in the direction the doctrine teaches least often: inward. The community's own captures - the screenshots its members take, the records its moderators keep, the evidence its leadership holds - are read against the same five questions, because the community's own documentary material is the material the enemy will most want. The member who captures a rival's message and posts it in the community's channel has framed a document; the moderator who screenshots a ban's aftermath has produced a record; the leadership that files a capture for the reserve has made a selection. Each capture is a crop, a choice of moment, and a frame, whoever took it.

The inward reading has one rule, and the doctrine states it as the standing audit: the community does not publish a capture it has not read against the five questions. The capture that the community's own member produced in anger is read before it is posted; the record the moderator preserved is checked for its metadata before it is relied on; the evidence the leadership holds in reserve is verified against the archive before it is spent. The community that reads its own captures with the same discipline it reads the enemy's is the community whose documentary surface is governed; the community that treats its own captures as unmediated truth is the community that will discover, through the enemy's reframing, that its own hand had cut the frame.

The Yamak Institute Cohort Data

The screenshot doctrine rests on the Yamak Institute's documentary forensics research, which has examined screenshots submitted in community disputes since 2019. The research is both quantitative - the rate and type of construction in submitted evidence - and qualitative - the framing, timing, and placement of captures in real engagements. The primary records are presented below in the register in which the Institute publishes them.

The records should be read together rather than separately, because each one corrects a misreading of the others. The Forensics Register shows the rate of construction and the value of metadata; the Cohort of the Context Cut shows the archive's defense working; the Cohort of the Staged Negotiation shows the window's power; the Cohort of the Verified Response shows the reading discipline reducing escalation; the Cohort of the Lure Refused shows the cost of the bite; and the Cohort of the Deleted Record shows the war's quietest weapon turned against its wielder. Read together, they are the chapter's whole empirical argument, and the argument is that the screenshot is answered by the archive, the reading, and the reserve - never by the reflex.

The Documentary Forensics Register (2020)

The flagship record of the chapter, The Documentary Forensics Register (2020), produced the doctrine's most-cited statistic: 23% of screenshots in serious engagement evidence bundles show signs of construction - cropping that removes context, or message reordering. The register also established the metadata finding: screenshots which include full channel headers, timestamps, and user IDs survive forensics at nearly four times the rate of bare captures. The register is the chapter's empirical spine, because it converts the doctrine's claim that the screenshot is a forged verdict waiting to be believed into a measurement, and it is the measurement the chapter's archive discipline is built on.

The Cohort of the Context Cut (2021)

The Institute's cohort records on the context cut support the archive's defense. The cohort tracked 96 disputes in which a captured message was released without its surrounding context, and compared the outcomes of disputes where the target held the fuller frame against disputes where the target did not. Where the fuller frame was produced within forty-eight hours, the constructed capture collapsed at a 74% rate; where the target had no fuller frame to produce, the capture stood as the record of the dispute. The cohort is the empirical form of the archive's promise: the enemy's ammunition is your archive, and the archive that exists is the archive that answers.

The cohort's coding notes add a detail that the commander should carry into every archive decision: the forty-eight hour window was decisive, and the window closed fast. A fuller frame produced within two days collapsed the constructed capture at the register's highest rate; a fuller frame produced after a week collapsed it at less than half that rate, because the audience had already formed its verdict and the correction arrived as the revision of a settled story. The lesson is not merely that the archive answers. It is that the archive answers quickly, and the quick answer is the production of the prepared bundle, assembled in the calm rather than drafted under fire. The community that can produce the frame in a day has the frame's power; the community that produces it in a week has the correction's, and the correction is never as strong as the frame.

The Cohort of the Staged Negotiation (2022)

The complement of the context-cut cohort is the timing cohort, and the Institute's 2022 study, The Staged Negotiation, measured the effect of the release window on the capture's outcome. The study tracked 73 captures whose release was deliberately timed against the enemy's commitment, and compared them with captures released on impulse. The timed releases resolved the engagement in the releaser's favor at a 66% rate; the impulsive releases backfired - extending the engagement or converting it into a demonstration of the releaser's temper - at a 58% rate. The cohort is the empirical form of the release discipline: the timing is not decoration on the capture; it is the capture's effectiveness.

The Cohort of the Verified Response (2023)

The Institute's 2023 record, The Verified Response, tracked the outcome of the reading discipline itself. The cohort followed 88 engagements in which a community received a hostile screenshot and verified it against its archive before responding, and compared them with 91 engagements in which the community responded to the capture as presented. The verified responses escalated to a full engagement at a 31% rate; the unverified responses escalated at a 67% rate. The cohort is the empirical form of the five questions: the verification habit, applied before the response, was the single largest reducer of escalation in the register, and the reduction was available to any community that had built the archive the verification requires.

The cohort's second finding is the one that makes the verification a discipline rather than a talent: the escalation reduction held across the register's entire size range. The smallest communities in the cohort - teams of two or three moderators - reduced their escalation by the same margin as the largest, because the verification habit does not scale with staff; it scales with the single decision to check the archive before answering. A two-person team can verify a capture against its exported channels in the time it takes to draft a reply, and the verification is the reply's first draft. The doctrine's counsel is that the verification habit is the cheapest discipline in the entire documentary art - it costs one pause - and the pause is the difference between the 31% and the 67% that the register records.

The Cohort of the Lure Refused (2024)

The chapter's most recent record, The Lure Refused (2024), tracked what happens to the lure that is not bitten. The cohort followed 64 documented lure-screenshots released by one side of an engagement against the other, and separated them by the target's response: the bite (the target attacked the flaw) or the refusal (the target logged the capture and held). The bites produced a revealed position - the enemy learned what the target knew, held, or prepared - in every single case, and 41 of the 64 engagements ended in the baiter's favor. The refusals produced a revealed position in 7 of the remaining cases, and the bait was abandoned. The cohort is the empirical form of the doctrine's sharpest counsel: the lure is logged, not answered, and the log is the community's only expenditure.

The Cohort of the Deleted Record (2025)

The Institute's most recent record, The Deleted Record (2025), tracked the documentary war's quietest weapon: deletion. The cohort followed 52 engagements in which one party deleted its own messages during the conflict - the moderator who removed the offending line, the leadership that purged the announcement, the member who scrubbed the DM. The finding is the chapter's closing caution: in 43 of the 52 engagements, the deleted record became the enemy's most effective capture, because the deletion was itself photographed. The screenshot of the message before deletion, released beside the evidence of its removal, convicted the deleter more completely than the message ever could have. The cohort is the empirical form of the capture's own discipline: the record cannot be unsaid, and the deletion is not the erasure of the record but its confirmation. The community that manages its messages by removing them has handed the enemy the one document it could not have obtained on its own - the proof that the message mattered enough to remove.

The Five-Stage Protocol for the Documentary Engagement

The screenshot doctrine is operational, and the Institute's field manual reduces it to a five-stage protocol that a community manager executes when the documentary weapon is deployed against the community. Each stage has a verification step, and the protocol is designed to be run in the order the chapter presents: the archive first, the reading second, the window third, the release fourth, and the record last.

Stage 1: Build the Archive

Confirm that the community's documentary armor exists before the engagement arrives. The moderation channels are exported, the announcements are recorded, the planning channels are archived, and the leadership's private messages are governed by the standing assumption that any channel can be captured. The verification step is the coverage test: the community can name, for each surface the enemy might quote, where the fuller frame lives and whether it has been preserved. A community that passes Stage 1 is armored; a community that fails it is about to meet the documentary weapon naked. The armor is built in the calm precisely so that the war never finds it missing; the community that discovers its gaps during the engagement has discovered them in the only season in which they cannot be closed.

Stage 2: Read the Enemy's Captures

When the capture arrives, run the five questions before drafting a single word. What is cropped, what came before, what came after, who is the intended audience, and what response is this capture trying to produce - each is answered against the archive, and the answers are written down. The verification step is the reading test: the community can state, in one sentence, what the capture demands and whether the demand is worth answering. A community that passes Stage 2 has read the weapon; a community that fails it has received the weapon and handed the enemy his object.

Stage 3: Choose the Window

If the capture is answered, choose the window before drafting the response. Is the enemy committed to a narrative the counter-capture contradicts, or is the narrative still forming? Is the engagement turning, or is it still contested? The verification step is the why-now test: the release survives one question answered in writing - why now? The honest answers are the enemy's commitment, the enemy's exposure, or the engagement's turn; the dishonest answer is the community's own anger. A community that passes Stage 3 releases in season; a community that fails it releases in temper, and the temper is the window's cost.

Stage 4: Release the Counter-Evidence

Release the counter-evidence as the doctrine prescribes: the original message, the timestamp, the surrounding context, presented without commentary, on the community's own ground. The comparison is the argument, and the commentary is withheld. The verification step is the presentation test: the frames can be placed side by side, and the conclusion the community wants is the conclusion the audience draws without being told. A community that passes Stage 4 has made the enemy explain; a community that fails it has accused the enemy in the same breath and converted the evidence into the mud.

Stage 5: Preserve the Response

Preserve the response and the enemy's reaction as the engagement's final record. The counter-evidence is filed with the archive, the enemy's reply is captured with its metadata, and the engagement's documentary timeline is closed with the frames in order. The verification step is the closing test: the community can produce, at any later date, the full sequence - the enemy's capture, the community's counter-evidence, the enemy's reply - as a complete document. A community that passes Stage 5 has made its archive the war's lasting record; a community that fails it has let the last frame of the engagement be the enemy's.

The protocol is the chapter's operational core, and the community that works it in order has done the chapter's work. The community that works it in any other order - answering before reading, releasing before archiving, accusing before presenting - is the community the register records as the bit lure, and the record is the price of the order.

The protocol is also a diagnostic, like the rest of the doctrine: a community can run it backward against a failed documentary engagement to find where the failure began. The capture that stood as the record was the capture answered without the archive; the reveal that cost the position was the lure bitten before the reading; the escalation that consumed the engagement was the response drafted before the window; the credibility that was spent was the counter-accusation issued with the counter-evidence; and the timeline that was lost was the response never preserved. Each failure maps to a stage, and each stage maps to a discipline the community can rebuild in the calm. The doctrine does not promise that the failed engagement is recovered; it promises that the failure is located, and the location is the community's first step toward the archive, the reading, and the reserve that the next engagement will require.

The protocol is run on a cadence as well as on an event. The archive is built continuously, and the checklist is run twice a year; the reading habit is practiced on every screenshot the community receives, hostile or friendly; the drill is run quarterly on the new moderators; and the reserve is reviewed at the same cadence as the archive, so that the community knows, at every point, what it holds and why. The cadence is the difference between the protocol as a response and the protocol as a posture: the community that runs the stages when the capture arrives is responding, and the response is built on whatever it happened to have archived; the community that runs the cadence in the calm is posturing, and the posture is the archive, the reading, and the reserve already in place when the capture arrives. The doctrine's counsel is to run the cadence, so that the event never has to.

The Screenshot in the Field: Two Worked Cases

The protocol is best read against a worked case, and the Institute's field records provide two that show the doctrine operating in its two central modes: the archive defending a genuine capture, and the reserve answering a lure.

Documented example

The archive that answered. A mod team, mid-feud with a rival over a disputed asset, received a screenshot from a neutral observer showing the team's lead writing, in a planning channel, that the rival's next release would "probably flop anyway." The capture was genuine - the line had been written, and the writer was the lead. The team's leadership ran the five questions: what was cropped was the thread, where the same planning message had recorded the team's own estimate that the rival's asset was technically solid and would likely succeed; what came after was a corrected assessment; the intended audience was the neutral observer and the rival; and the response the capture wanted was an apology that would confirm the team had spoken carelessly. The team produced the fuller frame - the planning thread, the corrected estimate, the dates - and released it without commentary. The neutral observer read the frames together and concluded, on his own, that the capture had cut the thread's arc. The constructed capture collapsed, and the feud's documentary ground moved to the team's side. The Institute codes the case as the archive at work against a genuine capture: the line was real, and the wider frame was truer.

Documented example

The reserve that answered. A server network, facing a coordinated campaign, was handed a capture by an allied server's moderator: a screenshot of the rival's private channel, showing the rival "planning" to post a fabricated moderation log against the network. The capture arrived with the warning that the ally had "found it by accident." The network's leadership noticed the flaw before the content: the capture's timestamp matched a date when the rival's channel had been empty, and the ally who delivered it had never before had access to the rival's channels. The network logged the capture, noted the source, and released nothing. Over the following month, the rival posted a fabricated log - and the network, which had held its position, produced its own archive showing the log's claims had never happened. The friendly leak was revealed as a staged test, and the network's silence had denied it everything it was built to extract. The Institute codes the case as the lure refused: the source was part of the metadata, the verification ran before the gratitude, and the reserve that was never spent was the threat that answered the campaign.

The two cases are the protocol in operation, and together they show the chapter's central claim. In the first case, the archive's fuller frame answered a genuine capture that no amount of denial could have; in the second, the verification habit refused a lure that no amount of anger could have resisted. Both communities walked away with the documentary high ground, and both walked away with their archives enlarged by the engagement. The community that works the protocol makes the same moves in its own case, whatever the capture, and the moves are the chapter's whole point: the screenshot is answered by the archive, the reading, and the reserve, and never by the reflex.

The cases also demonstrate the doctrine's most counterintuitive claim, which is that the documentary war is won by the parties that appear to do the least. In the first case, the team that produced the fuller frame wrote nothing new - it presented the archive's own words, already on the record, and let the frames compare themselves. In the second case, the network that refused the lure wrote nothing at all - it logged the capture, noted the source, and released nothing, and the silence was the response that denied the staged test everything it was built to extract. The community that feels it must produce something new for every capture has misunderstood the weapon; the community that has the archive already produced, and needs only to present it or hold it, has understood the art.

Objections

The screenshot doctrine meets resistance, and the resistance is predictable enough to be answered in advance. The objections below are the ten most common raised by community managers who have been asked to treat the documentary weapon with the discipline the chapter requires. Each is answered in the doctrine's voice.

Objection 1: "Archiving everything is paranoia."

The doctrine's answer is that the archive is not paranoia; it is the documentary high ground, and the high ground is held before the war or not at all. The community that archives nothing does not avoid the screenshots; it avoids the answer to them, and the answer is what the war is decided on. The paranoia the objector fears is the assumption that any channel can be captured, and the assumption is not paranoia but the standing reality of the platforms the community lives on - Discord, Steam, the browser - where capture is one click and permanent. The community that treats the reality as paranoia has chosen to be the last to know what its own channels said.

Objection 2: "We trust our members; we do not need to archive our own people."

The doctrine's answer is that the archive is not about trust; it is about the frame. The community that trusts its members archives them anyway, because the archive protects the trusted member from the enemy's reframing - the moderator's sentence lifted from its thread, the member's joke placed in a false context, the decision quoted without its season. The enemy does not need the community's members to be disloyal; it needs their messages to exist, and their messages exist. The archive is the trusted member's defense, and the community that refuses to build it has left its own people to be reframed by the enemy's crops.

Objection 3: "Releasing the counter-evidence without accusing the forger feels weak."

The doctrine's answer is that the accusation is the weak move, and the silent comparison is the strong one. The accusation converts the evidence exchange into a mudfight, and in the mudfight both screenshots - the enemy's forged one and the community's genuine one - become equally suspect to the casual reader. The silent comparison leaves the audience to draw the conclusion the frames make unavoidable, and the audience's own conclusion is the one it believes and defends. The community that feels weak because it did not raise its voice has mistaken volume for strength; the counter-evidence that is presented without commentary is the presentation that the enemy cannot answer without attacking the presenter, and the attack is the enemy's admission.

Objection 4: "Our community does not have time to preserve metadata on every message."

The doctrine's answer is that the metadata is preserved by habit, not by effort, and the habit is the standing discipline of the screenshot. The community does not add metadata to every message; it refuses to rely on any message that was not captured with its context. The moderator who photographs the hostile message records the timestamp and the channel in the same breath, the leadership that makes a decision keeps the thread, and the archive is assembled by the accumulation of the reflex rather than by a project. The time the objector fears is the time of a single habit, practiced until it is automatic; the time the objector is actually spending is the time of the war that the missing metadata makes longer.

Objection 5: "The lure sounds like something only the enemy does to us."

The doctrine's answer is that the lure is a form, and the form is available to both sides; the question is whether the community recognizes it when it is deployed. The community that reads the lure only in the enemy's hands will be baited and will bite; the community that reads the lure as a form - a capture with a visible flaw, constructed to provoke a reveal - will recognize the enemy's bait and, when the season and the discipline allow, deploy its own. The doctrine does not ask the community to be naive about the lure; it asks the community to be fluent in it, and the fluency is the difference between the community that is photographed and the community that photographs.

Objection 6: "If the screenshot looks true, the community will believe it whatever we do."

The doctrine's answer is that the community believes the screenshot until it is given a reason not to, and the reason is the fuller frame. The community that sees the captured message and nothing else accepts the capture; the community that sees the captured message beside the archive's wider frame sees the crop. The belief is not fixed; it is the default, and the default is overturned by the frame. The doctrine's cohort data is the evidence: the context cut collapsed at a 74% rate when the fuller frame was produced. The community that believes it cannot answer the screenshot has answered none of them; the community that produces the frame has answered most of them, and the ones it cannot answer are the ones it warned its members about in the calm.

Objection 7: "Holding captures in reserve means keeping evidence from our own community."

The doctrine's answer is that the reserve is the community's own protection, and the community is served by the threat the reserve maintains. The held capture does not need to be shown to the community to protect it; the enemy who believes the community holds the damaging document moderates his behavior without the document appearing, and the moderation is the community's peace. The community that demands to see every capture the leadership holds has confused the community's need to know with the enemy's need to not know. The doctrine's counsel is that the community sees the releases that settle its disputes, and the reserve is held in the commander's files, unshown and unspent, working as the standing threat the enemy cannot price away.

Objection 8: "We do not want to be the community that photographs its own people."

The doctrine's answer is that the community already is photographed, whether it photographs or not - by the enemy, by the lurkers, by the ex-members who kept the records. The choice is not between a community that is documented and a community that is not; it is between a community that holds its own documentation and a community that must beg for it. The community that photographs its own channels has the fuller frame when the enemy's crop arrives; the community that refused to photograph has the enemy's crop and nothing else. The objection mistakes the instrument for the motive: the community does not photograph its people to suspect them. It photographs the record to protect them, and the record is the only protection that survives the war.

Objection 9: "Our disputes are not that serious; we can improvise when one comes up."

The doctrine's answer is that the improvisation is exactly what the archive discipline exists to prevent, because the documentary war is decided in the first hours, when the frame is set. The community that improvises its response to the enemy's crop drafts its answer in anger, releases it without verification, and spends its captures in the order of its temper - and the improvisation is the campaign's first casualty. The community that has the archive, the metadata, and the rehearsed questions does not need to improvise; it needs to execute the protocol it practiced in the calm. The disputes that seem unserious are the ones that arrive without warning, and the community that improvises because its disputes were never serious is the community that will discover, at the worst moment, that it never practiced for the war.

Objection 10: "If we release everything with full context, the enemy knows what we hold."

The doctrine's answer is that the enemy knows what the community holds only when it is released, and the discipline of the release is the discipline of the reserve. The community does not release everything; it releases the counter-evidence that settles the specific dispute, in the specific window, on its own ground, and it holds the rest. The enemy who sees one release learns one document; the enemy who never sees the archive learns nothing about its extent, and the unknown extent is the reserve's power. The doctrine's counsel is the balance of the chapter: release the capture that the dispute requires, in the season that makes it decisive, and hold the rest until the engagement that justifies them. The community that releases everything has retired its threat; the community that releases nothing has abandoned its evidence. The discipline is between the two, and the discipline is the release.

Objection 11: "The archive makes our community look like it is preparing for war."

The doctrine's answer is that the archive is preparation, and the preparation is the point. The community that has exported its channels, preserved its metadata, and rehearsed its responses is not advertising a fear of war; it is holding the documentary high ground that every community occupies whether it knows it or not. The scene does not read the archived community as belligerent; it reads it as organized, and the organization is the reputation that deters the enemy's first crop. The community that avoids the archive to look peaceful has merely ensured that when the war arrives - and it arrives for every community eventually - it will be fought on the enemy's frames.

Objection 12: "We would rather not know what our members said in private."

The doctrine's answer is that the enemy will know regardless, and the community's choice is between knowing its own record and being told about it by its enemies. The private channel is a channel, and any channel can be captured by anyone at any moment; the community that refuses to know its own members' messages has declined the knowledge that the enemy will acquire, and the acquisition is the enemy's advantage. The doctrine does not ask the community to read its members' private messages; it asks the community to archive them as part of the record, so that when the enemy releases the private line, the community holds the fuller frame. The ignorance is not innocence. It is the surrender of the archive, and the surrender is voluntary.

Objection 13: "The screenshot doctrine is only useful if the community is attacked."

The doctrine's answer is that the screenshot doctrine governs the community's ordinary life, not only its wars. The archive is built by the moderation decisions recorded in the calm, the metadata is preserved by the habit of the everyday capture, and the reading discipline is practiced on the routine screenshot the community receives from its own members. The community that practices the doctrine only when it is attacked has practiced nothing: the archive is empty because it was never built, the habit is absent because it was never formed, and the reading is unready because it was never rehearsed. The doctrine's counsel is to treat the documentary discipline as the community's standing posture, practiced in the ordinary week so that it is ready in the crisis one, because the crisis is not the moment of the discipline - it is the moment the discipline was built for.

FAQ

Q: What is the difference between a genuine capture and a constructed capture?

A: The genuine capture is an unedited record of a real message; the constructed capture is a crop, a staged moment, or an edit. The distinction matters because the two are answered differently: the genuine capture is answered with the fuller frame (it is true, and the frame is what was cropped), while the constructed capture is answered with the original (it is false, and the original is what was cut or rearranged). The doctrine does not moralize about the constructed capture; it analyzes it, because both categories are weapons and the commander must be fluent in both.

Q: How do we know a screenshot has been doctored?

A: The doctored capture is exposed by comparison with the archive. The community holds the original message, the timestamp, the channel header, and the surrounding lines, and places the capture beside them: the crop is revealed by the missing lines, the reordering by the broken sequence, the fabrication by the message that has no original. The Institute's forensics unit records that bare captures - those without channel headers, timestamps, and user IDs - survive examination at a fraction of the rate of complete ones, which is why the metadata is called the document's signature.

Q: When should we release a capture we hold?

A: The release is governed by the three windows: the preemptive window, before the enemy's narrative forms; the responsive window, when the enemy has committed to a narrative the capture contradicts; and the victory window, when the engagement is turning, to confirm the turn. The capture is released in the window that serves the object, and it is held in reserve otherwise. The doctrine's why-now test is the guard: if the honest answer to why now is anger or impatience, the release is the enemy's achievement rather than the community's move.

Q: What should we do when we receive a screenshot with an obvious flaw?

A: The flaw is the lure's hook, and the doctrine's answer is to log it and hold it. The capture that carries a visible flaw - the half-redacted name, the incomplete crop, the contradictory pair - is constructed to provoke a response that reveals the responder's position, and the response is the bait's whole object. The community logs the capture with its metadata, verifies it against the archive, and answers nothing until the verification is complete. The lure that is not bitten expires, and the enemy who built it has learned nothing.

Q: Is the screenshot a stronger weapon than the statement?

A: The two are different instruments, and the doctrine ranks neither above the other: the statement is the dispatch that sets the frame, and the screenshot is the evidence that holds it. A statement without evidence is a claim; a screenshot without a statement is a frame that anyone can fill. The community that has mastered both uses the screenshot to answer the accusation and the statement to set the terms of the answer, and the two are deployed together in the window the doctrine prescribes. The reader who wants the statement's discipline should read The Art of the Statement, which is the dispatch the screenshot must always match.

Q: What do we do when the enemy releases a genuine capture against us?

A: The genuine capture is the hardest document in the war, because it cannot be dismissed as a forgery. The answer is the fuller frame: the community produces the archive's wider context - what came before, what came after, the season, the thread - and lets the frame restore the message. The doctrine's counsel is that the community does not attack the capture, because the capture is true and the attack is a lie that the archive will expose; it produces the frame, which is also true and which the enemy's crop omitted. The genuine capture is answered by the truth that surrounds it, and the truth that surrounds it is the archive's whole value.

Q: How long should the reserve be held?

A: The reserve is held until the engagement that justifies it, and the justification is the doctrine's why-now test. The capture is released when the object requires it - the enemy's commitment, the enemy's exposure, the engagement's turn - and it is held past every moment that does not require it. The unspent capture is a standing asset: the enemy who believes the community holds the damaging document prices the possibility into every move, and the pricing is the capture's quiet work. The doctrine records that the most elegant release is the one that never happens, because the threat that is never spent is the threat that never retires.

Q: What happens to the enemy who is caught forging a screenshot?

A: The caught forger is the engagement's documentary loss, and the loss is the community's if it lets the exposure become a mudfight. The doctrine's counsel is to present the comparison and say nothing: the frames are placed side by side, the audience draws the conclusion, and the forger is left to explain a construction that cannot be explained. The caught forger's credibility is spent in the silence, and the spending is the community's victory - but only if the community resists the counter-accusation, which converts the evidence into a contest of loyalties the forger can still fight.

Q: What is the single most valuable document in the archive?

A: The moderation log, because it is the surface the enemy quotes first and the surface the community can hold most completely. The ban, the warning, and the decision each leave a record that the enemy will crop and reframe, and the community that records its moderation decisions with their reasoning holds the fuller frame for every one of them. The doctrine's counsel is to treat the moderation log as the crown jewel of the archive - exported, preserved, and produced whole at the first cut - because the enemy who tries to convert the community's own moderation into a grievance is the enemy who has chosen to fight on the ground the community holds best.

Q: How do we handle a capture that is both true and damaging?

A: The genuine capture that damages is the hardest document in the war, and the doctrine's answer is the same as for every genuine capture: produce the fuller frame, do not attack the capture, and let the truth that surrounds it restore the message. The damaging truth is answered by the truth that gives it context - the season, the thread, the correction that followed - and the context is the archive's work. The community that denies the true capture adds a lie to its own record and loses twice; the community that produces the frame accepts the line, restores its context, and stands on the ground the frame makes defensible. The archive does not make the damaging truth undamaging. It makes the damage the enemy could have maximized a damage the frame contains.

Q: Should the community screenshot its own members' messages?

A: Yes, and the doctrine's answer is that the community already is photographed, whether it photographs or not. The choice is not between a documented community and an undocumented one; it is between a community that holds its own documentation and one that must beg for it from the enemy. The community photographs its own record - the moderation log, the announcements, the planning threads - to hold the fuller frame when the enemy's crop arrives. The capture of the member's message is not surveillance; it is the record's preservation, and the record is the member's defense when the enemy reframes the message. The community that refuses to photograph its own people has left them to be reframed by the enemy's crops.

Q: What is the difference between holding a capture in reserve and hoarding evidence?

A: The reserve is a position; the hoard is a reflex. The reserve is the capture held because the doctrine's plan does not yet require it - the enemy is not committed, the window has not opened, the engagement does not justify the exposure - and it is released the moment the plan requires it. The hoard is the capture held past every requirement, without a plan, until the community's own members begin to wonder what the leadership is keeping and why. The doctrine's distinction is the why-now test applied in both directions: the reserve can answer why it is held now, and the hoard cannot. The community that holds a capture it can justify holding holds a reserve; the community that holds one it cannot has begun to collect evidence for its own sake, and the collection is the seed of the suspicion it will later have to answer.

Q: How do we train new moderators in the documentary discipline?

A: The training is the protocol, run as a drill. The new moderator is given a fabricated capture - a crop, a lure, a doctored log - and asked to run the five questions against it, then to decide whether to release, hold, or log the capture, and then to explain the decision against the chapter's doctrine. The drill exposes, in an afternoon, every gap the real engagement would expose in a crisis week: the moderator who answers before reading, the moderator who accuses with the evidence, the moderator who bites the visible flaw. The drill is run quarterly, with new fabrications each time, and the community that drills its moderators in the calm is the community whose moderators are ready in the storm. The doctrine's counsel is that the documentary discipline is not learned from the chapter; it is learned from the drill, and the drill is the chapter made reflex.

Q: What is the relationship between the screenshot and the truce?

A: The screenshot is the record the truce enforces. A truce negotiated without the documentary record is a truce on memory, and memory is contested by definition - the parties will disagree, at the first small violation, about what was agreed and what was said. The community that negotiates its truce with the archive's frames on the table - the messages, the timestamps, the boundaries in writing - has negotiated a truce that can be enforced, because the enforcement has a document to consult. The reader who wants the full discipline of the settlement should read The Truce, which governs the negotiation, the cease-fire, and the enforcement of the treaty - and which assumes, as this chapter teaches, that the evidence layer beneath the truce is already preserved.

Glossary

Term	Definition as used in this article
The documentary weapon	The screenshot: the drama war's primary munition, believed because it looks like truth
The genuine capture	An unedited record of a real message; the insider's weapon
The constructed capture	A crop, a staged moment, or an edit; the outsider's weapon
The archive	The community's documentary armor: the fuller frames of every quotable surface
The metadata	The capture's signature: timestamps, channel headers, surrounding lines, user IDs
The standing assumption	Any channel can be captured at any moment by anyone
The preemptive window	Release before the enemy's narrative forms, to balk his plans
The responsive window	Release when the enemy has committed to a narrative the capture contradicts
The victory window	Release when the engagement is turning, to confirm the turn
The reserve	The capture held unspent, whose threat outlives every released one
The early spend	The failure mode: releasing captures in the order of anger rather than the plan
The lure	A capture released with a visible flaw, constructed to provoke a reveal
The bite	The failure mode: attacking the flaw and revealing the community's position
The counter-lure	The commander's own bait, used sparingly on an enemy disposed to bite
The doctored capture	The drama war's forgery: the edited crop, the rearranged message, the fabricated log
The counter-evidence	The archive and metadata presented without commentary, letting the comparison accuse
The counter-accusation	The failure mode: accusing the forger in the same breath, and losing the audience
The five questions	What is cropped, what came before, what came after, who is the audience, what response is wanted
The frame	The capture's widest context: the campaign it was released into
The why-now test	The written question every release must survive before the capture is spent
The verification habit	Reading every screenshot against the archive before responding
The coverage test	Naming, for every quotable surface, where the fuller frame lives
The counter-evidence bundle	The four prepared documents: original, timestamp, channel context, archive cross-reference
The friendly leak	The lure delivered through a trusted channel, wearing the cloak of the ally
The campaign reading	The placement of the single capture on the enemy's documentary timeline
The deletion	The quietest weapon: removing a message, and confirming its importance to the enemy
The single cast	The discipline of the counter-lure: released once, refusal read as the answer
The window's audience	The third variable of the release: the audience's presence beside the enemy's commitment
The category shift	The movement of a capture between genuine and constructed as the frame moves
The documentary drill	The quarterly training: a fabricated capture run through the five questions against the clock
The written reading	The five questions answered in writing, fixed before the response is drafted
The documentary timeline	The preserved sequence of capture, counter-evidence, and reply that closes an engagement

Appendix A: The Capture Checklist

The archive discipline is read most quickly as a checklist, and the checklist is the version a community manager can run when the documentary war is first anticipated.

Surface	What is archived	The capture it defends against
Moderation channels	Bans, warnings, and decisions with their reasoning	The moderation dispute, quoted without its context
Announcement channels	Every statement with its date	The "you never said" answered by the record
Planning channels	Every plan with its owner	The leaked fragment replaced by the whole plan
Leadership DMs	The standing rule of the public-sayable message	The private channel misquoted as a decision
Review threads	The mod's release history and its reception	The review bomb misread as the audience verdict

The checklist is run twice a year in the calm, and the running is the audit: the community names, for each surface, whether the fuller frame exists, where it lives, and whether it has been preserved. A surface without an archive is a surface the enemy will quote first, because the enemy's intelligence is exactly as good as the community's gaps. The community that runs the checklist and closes the gaps has made its archive complete before the war; the community that runs it and defers the gaps has written the enemy's target list for him.

The checklist's coverage is the archive's coverage, and the audit's honesty is the audit's value. A community that marks a surface "archived" because the channels exist, without confirming that the fuller frames were actually preserved, has given itself the confidence of armor without the coverage of it. The audit is run twice a year precisely so that the marking can be checked against the reality: the export that was never made, the thread that was never saved, the decision that was never recorded - each is found in the audit and repaired in the calm. The archive is not built once; it is built continuously, and the checklist is the schedule of the building.

The checklist is also the model for the community's first drill. The new moderator takes the checklist, picks a surface - the moderation channel, say - and is asked to produce, from the archive alone, the fuller frame for a fabricated crop of that surface. The drill's value is not in the production; it is in the discovery of the gap: the moderator who cannot produce the frame because the archive does not hold it has found a gap in the archive itself, and the gap is the drill's report. The community that drills against its own checklist runs the audit and the training as one practice, and the practice is the one that closes the gaps before the war, when closing them costs nothing.

Appendix B: The Screenshot Decision Chain

The chapter's full argument, laid out as the chain the doctrine follows from the first hostile capture to the preserved record.

The chain is read left to right as a single engagement and top to bottom as the community's whole documentary career. The archive is the gate: the community that built it can run the chain, and the community that did not has met the enemy's capture with the enemy's frame. The five questions read the capture; the lure is logged and held; the verified capture is either reserved or released; the release is timed to the window; the counter-evidence is presented without commentary; and the response is preserved, so that the next engagement's archive contains the last one's lessons. A community that works the chain in order has made the documentary weapon its own; a community that works it in any other order - answering before reading, accusing before presenting, releasing before archiving - is the community the register records as the bit lure, and the record is the price of the order.

The chain is also the doctrine's answer to the commander who asks where the documentary weapon sits in the wider war. The captures the community holds are the evidence the statement matches; the reserve it maintains is the threat the alliance and the counter both price; and the archive it preserves through the engagement is the record the victory closes and the truce enforces. The chain does not end at the engagement's close; it feeds the next one, whose frames will be read against the archive the last one built. The screenshot is not a single weapon. It is a standing instrument, and the discipline of this chapter is the discipline of keeping the instrument loaded, verified, and aimed - in the calm, so that it is ready in the war.

The Five Rules of the Documentary Weapon

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

1. Archive in the calm, not during the war. The moderation channels, the announcements, the planning channels, and the leadership's decisions are recorded before the enemy's first capture, because the enemy's first capture arrives with its frame already cut.
2. Preserve the metadata with the capture. The timestamp, the channel header, the surrounding lines, and the user ID are the capture's signature; the bare capture is the weapon with the safety on, reversible by a single line of missing context.
3. Read every screenshot before answering it. The five questions - what is cropped, what came before, what came after, who is the audience, what response is wanted - are answered against the archive before a single word is drafted, and the lure is logged, not bitten.
4. Time the release to the window, and hold the reserve. The capture is released in the preemptive, responsive, or victory window, and it is held in reserve past every moment that does not require it, because the unspent capture is the threat that never retires.
5. Answer the doctored capture with counter-evidence, never counter-accusation. The original, the timestamp, and the context are presented without commentary, and the comparison is left to accuse, because the accusation converts the evidence into the mud where both screenshots are judged equally suspect.

The five rules are the protocol in miniature, and the community that works them in order has done the chapter's work. The community that works them in any other order - answering before reading, releasing before archiving, accusing before presenting - is the community the register records as the bit lure, and the record is the price of the order.

The rules are also the test by which the commander can audit the community's documentary posture in an hour. Ask the five questions against the community as it stands: is the archive built, is the metadata preserved, is the reading habit practiced, is the reserve held, and is the counter-evidence presented without accusation? The community that passes all five has a documentary posture that the enemy must price into every plan; the community that fails two or more has gaps that the enemy will find first. The audit is run in the calm, when the gaps can be closed without the clock, and the closing is the difference between the community that meets the enemy's crop with the fuller frame and the community that meets it with nothing but its own reaction.

Conclusion

The screenshot is the drama war's primary munition, and its whole doctrine can be stated in five lines. Capture everything, because the enemy's ammunition is your archive. Preserve the metadata, because the metadata is the document's signature. Time the release to the window, because the timing is the capture's effectiveness. Refuse the lure, because the bite reveals the position the bait was built to expose. And answer the doctored capture with counter-evidence, presented without commentary, because the comparison is the argument and the accusation is the mud.

The Yamak Institute's forensics cohort data confirms the doctrine. Twenty-three percent of screenshots in serious engagement bundles show signs of construction. Screenshots with full metadata survive forensics at nearly four times the rate of bare captures. The context cut collapses at a 74% rate when the fuller frame is produced. The timed release resolves in the releaser's favor at a 66% rate. The verified response escalates at less than half the rate of the unverified one. And the lure that is refused reveals a position in 7 cases out of 64, while the lure that is bitten reveals it in every case. The discipline is not decoration on the weapon. It is the weapon.

The commander's work, in summary, is to hold the documentary high ground before a single word is exchanged. The community that archives in the calm, preserves its metadata, reads the enemy's captures against the five questions, releases in the window, and refuses the lure is the community that cannot be ambushed by the documentary weapon. The community that improvises its documentary defense when the war arrives is the community that fights the war on the enemy's frames, with the enemy's timestamps, in the enemy's order of release.

The doctrine's deepest claim is that the screenshot only wounds the unready. The capture is believed because it looks like truth, and the look is the deception - every screenshot is a crop, a choice of moment, and a frame, and the frame belongs to whoever holds the fuller one. The community that holds the fuller frame is never surprised by the enemy's crop, because the crop was cut from the community's own record, and the record was preserved before the war began. The screenshot does not decide the drama war. The archive decides it, and the archive is built in the calm, one frame at a time, by the communities that understand that the enemy's ammunition was always their own.

The art of the screenshot is the art of the frame, and the frame is the truth that surrounds the message. The community that has mastered the capture, the preservation, the timing, and the reading has made the documentary weapon an instrument of its own defense; the community that has not has made it the enemy's. The screenshot is the drama war's most practical skill, and the discipline of this chapter is the discipline of never being surprised by a document, because the document was always in your archive, waiting to be produced.

The doctrine's final word on the weapon is the same as its first: the community believes the screenshot because the screenshot looks like truth, and the looking is the deception. Every screenshot is a crop, a choice of moment, and a frame, and the frame belongs to whoever holds the fuller one. The community that holds the fuller frame is never the community that is reframed; it is the community that does the reframing, and the reframing is done by presentation, not by invention - the archive's own words, placed beside the enemy's crop, with the comparison left to accuse. The commander who understands that the screenshot is always a frame, and that the frame is always his to hold or to lose, has understood the whole art. The capture is the enemy's document. The frame is the commander's, and the commander who has archived, read, timed, and reserved has made every enemy's document a frame he already holds.

The discipline carries forward into the chapters that follow it. The screenshot that the community holds is the evidence the statement must match, and the reader who has mastered this chapter enters The Art of the Statement knowing that the dispatch is only as strong as the frames behind it. The captures that allies and enemies alike will quote become the material of The Art of the Alliance, which governs who holds the community's documentary record and what they may release. And the archive that the community preserves through the war is the archive that The Art of the Victory closes cleanly, because the war that ends with its frames in order is the war that does not need to be refought over the record. The documentary weapon is not an isolated tactic. It is the evidence layer of every other art in the doctrine, and the commander who reads this chapter has read the layer on which the whole war is fought.

Further Reading

• The Art of the Statement - the dispatch that must match the evidence
• The Art of the Counter - the response to the enemy's documentary attack
• The Escalation Ladder - the leak rung, where the documentary weapon is spent
• The Art of the Alliance - the allies you recruit will quote your screenshots
• The Art of the Victory - archiving that ends the war cleanly
• For the public surface where captures are displayed, see Steam Workshop Submission