- Darkness On the Face of the Deep
- Cactus Insurgent
When writing an object document for the Chaos Insurgency you have to keep in mind that unlike the Foundation, the Insurgency actively uses anomalous items. Due to the break down between cells and the differences in personnel class amongst the cells, Delta Command releases purely need-to-know documents. And all the Insurgency really needs to know is what to do with the anomalies, not what they are or their exact method of function.
Essentially, a member of Delta Command codenamed the "Engineer" constantly transcribes a massive list of instructions (the "Plan," and individual "Steps") without any immediate sense of correlation. Delta Command passes these instructions down to the bottom ranks of the Insurgency. The rest of Delta Command then scans and separates these Steps, and compiles relevant steps together in "Step Compilation" documents.
So those are the basics. Before you keep reading, you should probably read the "Darkness on the Face of the Deep" series. Just hop on over a couple of tabs and check it out. Because spoilers, or something. Also a lot of things won't, uh, make sense.
Let's talk about the thematic foundation of these documents. The point of this portrayal of the Chaos Insurgency is that they're all getting absolutely played by the Engine. This "object" format is supposed to embody the inherent contradictions in the nature of the Chaos Insurgency. They're an organization that purports to have as its goal the perfect understanding and integration of the anomalous—but they don’t tell their operatives anything about these paranormal objects or phenomena. There is the illusion of order—they’re following a strict series of instructions. But the reality is chaos—the average Chaos Insurgency operative has no idea what they’re doing or why. They’re just following the Engine’s plan.
Oh, also, who’s the Engineer? A member of Delta Command who’s in constant telepathic conversation with the Engine, unceasingly transcribing the Engine’s will into the Plan. Basically a mouthpiece. The Engine is the real mastermind behind everything, but nobody but Delta Command is aware of the Engine’s existence or true nature.
Just to close out, when approaching these documents, we think that it’s much more helpful for you, as a writer, not to think about an object you want to portray, but instead a story regarding that object, and even more specifically, what the Chaos Insurgency wants to do with that object. In order to portray exactly what the object is, you have to work around the knowledge blackout of the Insurgency to weave in implications, hints, or references to other parts of the Foundation universe.
DeCIRO Catalogue Number: The DeCIRO (Delta Command Intelligence Recording Office) Catalogue Number is the Chaos Insurgency's basic equivalent of the Foundation's Item Number, except that it applies to all documents.
Document Type: While "Step Compilation" will always been the Document Type at the top of the document, included sub-documents will have different Document Types. Sub-document information is detailed farther below.
Dates Received: Pretty self explanatory. Using xx-xx-xxxx (month-day-year) as a template. (ex: 04-22-1955) Keep in mind these dates correlate with the DeCIRO number of the Steps Compilation document.
Operation Status: If all the Steps on the document have been followed, and no further Steps are expected to be produced, the Operation Status is Closed. If the Insurgency is still following the Steps and/or it is suspected that more relevant Steps will be produced, the Operation Status is Open.
Foreword: Delta Command is not exactly the most sane group of individuals. The Foreword is them essentially talking to themselves (as only they would ever see the Foreword), usually through colorful language or metaphors. Useful for cluing the reader onto exposition things you wouldn't be able to easily do within the Steps.
1. STEP _ This is where the fun starts. The Steps are what the Insurgency is actually going to do with the object(s) relevant to the document. As such, descriptions aren't all too common. Instead, the Step may call for research of a particular object and then the resulting documentation of the study would be attached.
Step Compilation Template
[[>]] [[module Rate]] [[/>]] [[div style="float:right"]] [[image http://www.scp-wiki.net/local--files/chaos-insurgency-hub/CI%20Document.png width="310 px"]] [[/div]] **DeCIRO Catalogue Number:** SC-[First Step]/[Last Step] **Document Type:** Step Compilation **Dates Received:** [Date of first Step] through [Date of last Step] **Operation Status:** Open/Closed **Foreword:** [Vague description of the object, the operation, and/or how Delta Command feels about it.] Hereafter we of Delta Command document the Steps of the Plan as transcribed by the Engineer of the Chaos Insurgency. **1. STEP [Last two numbers of the year/Step number of that year]** [Set of instructions] **2. STEP [Last two numbers of the year/Step number of that year]** [Rinse, repeat as necessary]
> **DeCIRO Catalogue Number:** FR-[Relevant Step]-[Number](such as 001) > > **Document Type:** Summary Report > > **Date Received:** XX-XX-XXXX > > **Author:** [Name] > > **Summary Report:** [Findings Reports (the "FR" in the DeCIRO) detail the > research or recon instructed in the relevant step, in a Summary Report you... > well, summarily report.]
Post-Operation Summary Report
> **DeCIRO Catalogue Number:** POR-[Relevant Step]-[Number](such as 001) > > **Document Type:** Post-Operation Summary Report > > **Date Received:** XX-XX-XXXX (Month-Day-Year) > > **Author:** [Name] > > [Report detailing the results of the relevant military operation.]
> **DeCIRO Catalogue Number:** CO-[Relevant Step]-[Number](such as 001) > > **Document Type:** Covert Operations > > **Date Received:** XX-XX-XXXX > > **Author:** Delta Command > > [Secret op instructions.]