Link to article: Chaos Insurgency Hub.
float:right
[[>]] [[module Rate]] [[/>]] [[=image CI%20Main.png]] [[tabview]] [[tab Overview]] In 1924, the SCP Foundation formed a covert special task force, known only to the O5 Council, codenamed the "Insurgency." The leadership of the Insurgency was comprised of members of MTF Alpha-1, the Red Right Hand, famed for their loyalty to the O5 Council and the total secrecy of their origins, identities, and operations. The Insurgency leadership was supported by research, security, and retrieval personnel, all taken from Foundation ranks. To the majority of the Foundation and the anomalous world, the Insurgency was a splinter group that went A.W.O.L. with several researchers and anomalous objects. In reality, the O5 Council had created the Insurgency to complete missions with ethically questionable methods and politically unsavory results--while keeping the Foundation's public reputation clean. For approximately twenty-four years, the Insurgency operated under the guise of Foundation defectors, using anomalous objects to secretly further the goals of the O5 Council. In 1948, as part of a seemingly routine staged operation, the Insurgency removed several SCP objects from Foundation containment and transported dozens of defecting Foundation researchers to various safe locations. That same day, multiple other unplanned raids of Foundation facilities occurred. The Insurgency seized SCP objects with great research and military potential and inflicted severe casualties to Foundation personnel. The Foundation's biggest lie had become a reality. Their covert black ops team had defected, and the Foundation faced a new threat from an organization now calling itself by a new name: the Chaos Insurgency. The O5 Council was stunned. The defection or even the slightest hint of disloyalty from Red Right Hand personnel had been unprecedented. The motives behind the Insurgency's betrayal remain unknown to the Foundation. All attempts to find, apprehend, or assassinate the defecting Insurgency operatives failed. This information is classified within the Foundation, which maintains that the Insurgency defected in 1924 and that the actual defections in 1948 were simply raids made by the already-existing splinter organization. The modern-day Chaos Insurgency bears some similarities to the organization that founded it. The Chaos Insurgency's Delta Command, shrouded in mystery, issues orders to the lower ranks. Gamma-class researchers and military commanders have oversight over the execution of the Delta Command's orders, while Beta-class personnel, while not given the same level of command as Gamma-class, carry out the Insurgency's work in the field. Alpha-class personnel, often recruited from individuals with little to no knowledge of the anomalous, accept offers of employment often because the alternative is to carry on a miserable existence outside the anomalous world. They are the grunt workers: numerous and expendable. The Insurgency is split into two divisions: military and R&D. Cells within both divisions work independently, unaware of the exact actions and goals of other cells. New recruits receive instructions from their superiors and are expected to follow them unquestioningly, not knowing that every action they take is part of a larger plan orchestrated by the Delta Command. They are told that they are carrying out a great rebellion against the anarchy of the status quo—a world where "consensus reality" itself is an illusion, history's great lie, perpetrated by the Foundation. They are told that they will use the anomalous to build a utopian future, where humanity is master of everything, not just a mirage. But really, who knows what the Chaos Insurgency actually wants? [[/tab]] [[tab Collected Data]] ++ Contest Tales * Darkness On the Face of the Deep * [[[gate-of-janus |Gate of Janus]]] * [[[asymptomatic-carrier |Asymptomatic Carrier]]] * [[[the-ant |The Ant]]] * [[[Polycephaly]]] * [[[cactus-insurgent |Cactus Insurgent]]] * [[[Headhunted]]] ++ Contest Objects [[module ListPages parent="." tags="-tale" separate="no" order="created_at"]] * %%title_linked%% [[/module]] [[/tab]] [[tab Further Research]] [[module ListPages order="ratingAsc" limit="100" tags="-archived -admin -author -sandbox scp -tale -goi2014 +chaos-insurgency" rating=">-0" separate="no" perPage="100"]] * %%title_linked%% [[/module]] [[/tab]] [[tab Documented Accounts]] [[module ListPages order="ratingAsc" limit="100" tags="-archived -admin -author -sandbox -goi2014 -scp tale +chaos-insurgency" rating=">-0" separate="no" perPage="100"]] * %%title_linked%% [[/module]] **International Operations** * [https://scp-int.wikidot.com/reunion-inexistante The meeting that never were] * [https://scp-int.wikidot.com/jane Jane] * [https://scp-int.wikidot.com/ghost-sign The Ghost Sign] * [https://scp-int.wikidot.com/ventanas-a-otro-mundo Windows To Another World] * [https://scp-int.wikidot.com/scp-ru-178 SCP-RU-178 - The Heroes Of Vólorovsk] (ES Branch Regional SCP) * [https://scp-int.wikidot.com/the-plan-failed The Plan Failed] [[/tab]] [[tab Information]] 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. ---- + Document Break-Down **DeCIRO Catalogue Number:** The DeCIRO (__De__lta __C__ommand __I__ntelligence __R__ecording __O__ffice) 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 [[code]] [[>]] [[module Rate]] [[/>]] [[div style="float:right"]] [[image https://scp-wiki.wdfiles.com/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] [[/code]] + Sub-Documents Templates ++ Summary Report [[code]] > **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.] [[/code]] ++ Post-Operation Summary Report [[code]] > **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.] [[/code]] ++ Covert Operations [[code]] > **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.] [[/code]] [[/tab]] [[/tabview]]