Nine-Tailed Fox / MTFEPSILON

  • PMC
  • Casual
  • Role play
  • Security
    Security
  • Bounty Hunting
    Bounty Hunting

Mobile Task Force Epsilon-11 handles internal security for the SCP Foundation, under oversight by MTF Alpha-1. They are a special ops force deployed to Foundation Sites when standard protocols fail and multiple breaches are imminent. As such, most of their operations are classified.



History

Addendum 2139/1 – Site-35 Daily Briefings

Below are relevant extracts from Site-35’s scheduled daily briefings to US central command. On 17 January 2016, Command noted that Site-35 had a higher rate of research proposals than usual, and queried the reason for this increase.

18 January 2016

We have discussed the growth of research proposals with the heads of department, and their reports indicate that researchers are generating more ideas than usual to explain the anomalies secured on site. At this stage our working hypothesis is that there is some form of interaction between the anomalies on-site that is causing a positive feedback loop and making their properties more readily ascertainable.

19 January 2016

You’re correct, of course, that any anomalous interaction would have shown up before now – we have discarded that possibility. We are now wondering whether the effect is the result of a new anomaly, yet to be classified. Testing across the site with Kant-counters has shown no unexpected readings, which we interpret as evidence that this new anomaly must have a side-effect of disabling Foundation technology. That would also explain why none of the Scranton Reality Gauge Alarms were triggered. Noting that this could be a more serious situation than originally anticipated, we have cancelled all non-essential staff leave as a precaution.

20 January 2016

Alternatively, the anomalous effect could simply be to enhance creativity and generate more research proposals in that manner. A behavioural influence, rather than an effect on reality, would explain why the anomaly doesn’t give rise to abnormal Hume readings. Dr. Carter has raised the point that, if the anomaly is focused so narrowly on assisting the development of original thought, it is unlikely to have arisen naturally. The question is: who would have the ability and incentive to construct such an anomaly, and for what purpose?

21 January 2016

On reflection, we agree with you that the anomaly appears to affect credulity, rather than creativity. Our previous theories have been discarded, and we have initiated a site-wide lockdown. We are looking into potential sources of the anomalous effects, based on when symptoms first became evident.

22 January 2016

Investigations have uncovered the following potential sources of the anomaly: Uncommonly mild winter weather through January 2016, potentially indicating a meteorological phenomenon Extended D-Class testing of SCP-1011 during November 2015 Change of Site-35 supplier of cardboard boxes on 1 December 2015 15 August 2015 – further amendments to SUSEOCT (Southern United States Extranormal Organization Cooperation Treaty) on behalf of the Foundation and representatives of UIU and Marshall, Carter and Dark LLP Third anniversary of the death of former Region 352 Director John O’June in January 2016 Unscheduled visit on 4 January 2016 by Site Director Aktus, Site-81 We will advise further as our hypotheses develop.

23 January 2016

Numerological combinatorics to assess congruence between January temperatures and significant dates in Director O’June’s life has so far yielded few results. At Dr. Yu’s suggestion, we will incorporate the section numbers of SUSEOCT amendments into our next iteration. Separately, cross-checking of Foundation containment files to which we have access has turned up several possibilities which we think Command should investigate further. SCP-2366 and SCP-2604 are both mind-affecting anomalies stemming from otherwise-ordinary wood and wood-derived products. Both are deliberately manufactured, and would fit with our working theory of an intentionally designed anomaly. They could also easily evade standard detection – when everyone is looking at the trees, the wood is the one thing on Earth no-one has their eyes on. There could be other similar anomalies out there, hidden in plain sight. We hereby request delivery of samples of SCP-2366 and SCP-2604 to Site-35 for comparative analysis with our supplies of cardboard boxes.

24 January 2016

The Site-35 management committee, having debated at length, are agreed that cardboard boxes are the most likely source of the anomaly. All site resources have now been devoted to this investigation – we look forward to your response to our requisition request. Senior Researcher Michaels has noted that the new supplier for the boxes was “Apollo Office Supplies Inc.”. Could this company be related to the Order of the Hyacinth, responsible for the death of Director O’June? According to Greek myth, Hyacinth was a lover of the god Apollo, suggesting a connection. The infestation of Louisiana by water hyacinth is well-known, and several staff have since corroborated reports of increased growth of the plant in bodies of water near the site. Water hyacinth is also known as the Terror of Bengal. Please advise.

25 January 2016

Please respond to our previous requests. The general staff population are very concerned about the Order of the Hyacinth plot to destabilise Site-35, and silence from Command will encourage further talk of complicity in this scheme by Foundation personnel outside the site. We have discovered that the change of cardboard box supplier was confirmed by one “Declan Hall”. No person of that name is on the current Site-35 staff list, and we have been unable to discover any such person on the Foundation database. Presuming that the HR records have not been redacted by co-conspirators in RAISA, this appears to have been a fake name, suggesting an inside job. As the Order of the Hyacinth is a Catholic sedevacantist sect, we have taken the precaution of confining all known Catholic staff in the D-Class barracks.

26 January 2016

We continue to generate theories as to the source of the anomaly. Our previous cardboard box theory has been supplanted by new analysis suggesting that the anomaly could be caused by a single object with a large area of effect, or by a liquid or gas that is able to move around the site undetected. We accept that the detention of certain staff members may have been disproportionate, and they have been released. Indeed, we now consider that the anomaly may have been deliberately made to look like the work of a Catholic sect in order to frame innocent staff, and that the real perpetrators of this conspiracy have been manipulating the situation throughout. Could you please share with us information about the movements of Director Aktus between June 2015 and today. Certain staff have raised concerns that his visit may not have been as unscheduled as it originally appeared. Further data is required in order to ascertain the full extent of his involvement.

27 January 2016

Negative, Command: we strongly advise against shutting down Site-35. Our investigations into the anomaly continue to generate new leads, in a number of different directions, which should be pursued to the fullest extent by the site community. We recognise that we are under the influence of the anomaly, but we do not understand why you have dismissed our contention that it was deliberately engineered as a threat to the Foundation. Surely the anomaly’s effect puts us in the best position to develop theories as to its source? The removal of personnel or objects risks the loss of containment of the anomaly within site walls, before it is formally identified. Taking objects off-site, or worse, to other Foundation sites, risks cross-contamination of anomalous properties and could cause a cascade effect, with further sites compromised by the anomaly. This could be exactly what the anomaly’s creators want. We are very concerned with Command’s attitude to our advice and updates. We have noted your refusal (or inability?) to provide us with details of Director Aktus’ movements, and thus the suppression of our quest for the truth. Please be advised that, as of this time, we will consider any Foundation approach to the site as evidence of collusion with the person or group behind this anomaly, and will respond with force.

On 28 January 2016, MTF Epsilon-11 (“Nine-Tailed Fox”) was deployed to establish control over Site-35. [REDACTED]. The site was eventually subdued with no further casualties and all personnel and affected MTF members removed to Site-73 for quarantine.

Incident 3030-Alpha: SCP-3030 was created during unapproved cross-testing and research into two previously unrelated objects. The first object, now classified as SCP-3030-1, was a non-anomalous supercomputer designed for taking and processing data on anomalies to assist in producing viable containment strategies. The second object, hereafter referred to as SCP-3030-Gamma, was a Safe-class anomaly brought to the site for a short period to test and confirm properties, as similar facilities for Safe-class objects were over capacity. SCP-3030-Gamma was initially thought to simply be a standard classroom style blackboard that automatically produced fractal tessellation patterns when written upon. Upon further testing, it was found that SCP-3030-Gamma could reproduce these patterns with any material applied to it to a nanomolecular accuracy. At the suggestion of a junior researcher working on both projects, a number of designs for fractally tessellating circuits were drafted and produced using SCP-3030-Gamma. These circuits, when integrated into SCP-3030-1, caused the device to exhibit minimum levels of sentience. It then output a plan to incorporate living humans into its systems. A senior researcher volunteered to undergo the procedure first. This involved inserting a number of leads into the subject’s spinal column, then incising the [DATA EXPUNGED]. From this point the subject effectively became a part of SCP-3030-1’s systems, with a part of their own personality incorporated into its routines. Within 5 hours, all other researchers working on SCP-3030-1 had been incorporated into its systems. It has been suggested that SCP-3030-1 may have undocumented mind-affecting properties that contributed to this situation.

The next events are not quite understood at this time. The sector of Site-56 where these objects were being developed and researched underwent a total lockdown at 3:00PM, and by 6:00PM, five out of Site-56’s seven sectors began to undergo anomalous effects, and over 75% of site research staff were incorporated into SCP-3030-1’s systems. At this point, SCP-3030-1 entered its first active state and output 10 instances of SCP-3030-3, which were distributed to the newly created SCP-3030-2 facilities. General confusion around the situation resulted in a delay before the dispatch of MTF Psi-7 and MTF Mu-4 to attempt to contain SCP-3030. Their efforts, though productive, were not quick enough to contain all anomalies before SCP-3030-1’s timer reached zero. At this time, a state of emergency was declared, and Mobile Task Force Epsilon-11 (“Nine-Tailed Fox”) was dispatched to contain the situation as soon as possible. After 7 hours, all instances of SCP-3030-3 were contained, and the current procedures were put into place.

Incident 4511.1: 8 hours following the reception of Test Report 10, Regional Director Caleb authorized MTF Epsilon-11 (“Nine-Tailed Fox”) to raid Provisional Site-4511 after reports of possibly compromised site security. A transcript is attached.

MTF Body Camera Video Log Transcript

Date: 05-13-65

Task Force: MTF Epsilon-11 (“Nine-Tailed Fox”)

Subject: Provisional Site-4511

Team Lead: ε-1

Team Members: ε-2, ε-3, ε-4

«BEGIN LOG»

ε-1: Safeties off. Sound off on my count. One.

ε-2: Two.

ε-3: Three.

ε-4: Four.

Team enters the factory single-file, guns raised.

ε-1: No sign of research team on the main production floor. Descending into basement.

Command: Proceed with caution.

Team crosses the factory floor to the freight elevator, and enter.

ε-1: Three, time to earn your keep.

ε-3: Yessir.

ε-3 moves to the electrical box of the elevator and attempts to pull it open. After a few seconds of pulling, he succeeds in opening the cover. The interior of the fuse box is revealed to have been sealed to the door with a layer of waxy material.

ε-4: Is that… fat?

ε-3: Ugh.

ε-2: Probably from years of disuse. I don’t think anyone was cleaning it even when this place was still open. Three, can you get it working or do we have to throw ourselves down, lemmings-style?

ε-3: Yeah, I should be able to rig something up real quick. Gimme a second.

ε-3 spends several minutes interacting with the fuse box. With a lurch, the elevator begins slowly dropping.

ε-1: Well done. Unless they somehow moved the thing, SCP-4511 should be somewhere on this floor.

Command: Weapons free, though we’d prefer if at least a couple were brought in alive.

ε-1: Roger th-

The elevator reaches a stop and the overhead lights shut off.

ε-2: Three, was that you?

ε-3: I didn’t touch the lighting fuses. That’s something else.

ε-1: Doesn’t matter. Four, get over here and help me open these doors.

ε-1 and ε-4 work together to open the cargo doors of the elevator. The entire lighting system for the lower floor is shut off.

ε-1: Flashlights on, they’re creeping about here somewhere.

Team advances onto the catwalk and continue in silence for 2 minutes, until ε-2 pauses.

ε-2: Jesus fuck Three, did you piss yourself?

ε-3: What? No!

ε-1: We’re walking in it.

ε-1 gestures to the catwalk floor, and the shallow puddle of yellow liquid covering it.

ε-4: Fuck me, I think I’m going to vomit…

ε-3: God, that’s… who the fuck does that?

The team is interrupted by a drop splashing into the puddle. They raise their weapons and flashlights to reveal a fleshy growth attached to the ceiling, a hole from which is leaking the urine.

ε-1: (quietly) Keep moving. One of you guys, make sure you’re looking at it.

The team continues forward, ε-4 bringing up the rear to keep a view on the growth. They continue in silence for another 4 minutes, descending a stairwell.

ε-1: We’re reaching the basement floor.

Command: [Unintelligible]

ε-1: You’re cutting off. Repeat, we’re reaching the basement floor. Sound off. One.

ε-2: Two.

ε-3: Three.

Silence.

ε-1: Where the fuck is Four?

ε-3: I… she was just next to me!

ε-2: Do we go back to look for her?

ε-1: Yeah. Get ready.

The team retreats up three flights of stairs. ε-4 is splayed out on a landing, unconscious.

ε-1: Two!

ε-2: On it!

ε-2 begins applying first aid to ε-4, who has a large wound in her right thigh. ε-4 slowly regains consciousness.

ε-4: I don’t know what happened. One minute I was behind you guys… and the next, I’m clutching my head here.

ε-1: Active hostile entity in the area. Possibly anti-memetic. Can you walk?

ε-4: N-no.

ε-1: Take your gun and shoot anything that isn’t us. We’ll be back. I swear.

The team returns down the stairwell, reaching the bottom and spreading out. The floor is largely covered in various furnaces.

ε-2: There’s something up ahead.

The entrance to SCP-4511 is visible at the end of the room. A large pile sits next to it. Upon closer view, the pile is comprised of several white-coated bodies, all suffering from extreme exsanguination. A figure sits on the floor next to the pile.

ε-1: Hands up, now!

The figure stands up, wearing the uniform of a researcher. A large burn scar stretches across his right cheek. He is clutching something in his right hand.

ε-1: Whatever’s in your hand, drop it.

Unknown Individual: Whatever you think you can do to me, it’s nothing. Nothing compared to what it can do.

ε-2: What’s “it”?

The individual gestures behind him, seemingly at SCP-4511 and the pile of corpses.

Unknown Individual: I took their oil to feed it and I’ll take yours too…

ε-2: I’m giving you five seconds to sit the fuck down before I blow your brains out.

Unknown Individual: You can’t win! If you kill me, it wins. And you’ll never let it win, because you’ve had it so drilled into you that it is wron-

ε-2 terminates the individual with a single shot to the head. A rumbling sounds emanates from SCP-4511. ε-3 advances and inspects what the individual was holding: A small clump of bloody flesh and a scrap of paper.

ε-3: “Meat from those who seek to do in my faithful.”

ε-3 picks up the piece of flesh, and throws it into SCP-4511. The flames roar.

ε-1: What the fuck? Why did you do that?!

ε-3: I don’t know.

ε-2: Come on. We have to go get Four. She won’t last long as she is.

The team reascends the main stairwell, to the location Four was sitting in. Four is unmoving, her gun beside her.

ε-2: FUCK!

ε-1: Check for a pulse!

ε-2 shakes his head.

ε-2: Nothing.

ε-3: Christ. One, what do we do?

ε-1 sighs.

ε-1: Only thing we can do. Head back up. We terminated the threat, and Director Calebs is outside with an emergency ResCon2 team.

ε-2: Let’s go, then. We need backup to clean this place out.

«END LOG»

Incident Report ID #: 5018-A1

Summary: On 07/19/████, Site 119 initiated a 119/B/Coldsilver Lockdown Response Code following containment breaches of six Large Scale Aggressors, four Non-Terminable Threats, and five other extradimensional anomalous threats. O4 approved the detonation of Site 119’s nuclear warhead one hour and thirty-four minutes after the Lockdown Response Code was initiated. Site 68 received a backup of files, sent by Director David Bold, 26 minutes after the destruction of Site 119. Included in the backup was one folder of encrypted files and one image taken after the detonation. Following the incident, MTF Epsilon-11 (“Nine-Tailed Fox”) was dispatched to establish a perimeter around the affected area.

MTF ε-11 was unable to locate any threats after Site 119’s detonation. However, MTF ε-11 reported sightings of 5 unidentified individuals 3 days following Site 119’s destruction. MTF ε-11’s attempt to apprehend the individuals were unsuccessful5. MTF ε-11 was immediately relieved by MTF Nu-7 (“Hammer Down”) and sent to Site 68 for medical treatment and debriefing. 6 weeks after the detonation, MTF Omicron-2 (“Nuclear Nomads”) was sent to investigate the remains of Site 119.

MTF o-2 discovered 15 compromised MCLs in the remains of Site 119. This incident is recorded as the first insertion point of SCP-5018 into the Foundation’s network infrastructure.

Foundation agents are to work with local authorities to limit the sale of memorabilia, costumes and novelty items during events that feature fictional characters belonging to The Pokémon Company. A public ban on the adornment of Pokémon-related accessories will be imposed on festivals and mass gatherings, including (but not limited to) face-masks, hats, coloured make-up and full-bodied onesies.

A special task force of MTF Epsilon-11 (“Nine-Tailed Fox”) is to be deployed at future events to neutralise SCP-5254 instances that manifest in public spaces.

Further efforts will be made to disrupt The Pokémon Company’s global marketing and promotional infrastructure, with embedded agents discrediting the franchise’s popularity on social media, video game websites and within religious communities.

Manifesto

OPERATIONAL POLICIES MISSING ETA: TBD

Charter

FOUNDATION STANDARD ORIENTATION MANUAL
LOCKDOWN PROCEDURES
Revision 3.9 [Site-81]. Electronic copy.
——————————

Submitted to Foundation Records Database. Archived File.

All field personnel and Foundation staff have been issued a clearance-specific copy of this manual as of 15/03/17. Do not copy or re-distribute.
——————————
UTILISATION:

The purpose of this documentation is to inform personnel of basic procedures during an on-site lockdown following a compromise of security or containment. Advanced copies, including re-containment protocol manuals for involved personnel, may be accessed by requesting such from your immediate supervisor.

Refer to this manual as your most reliable source. Lockdown procedures must be fast in order to achieve effectiveness, utilising speed as an advantage over the adversary threat. Misunderstanding basic regulations can endanger you and everyone you work with. Due to this, site administration requires all personnel to be familiar with this manual.
DISTRIBUTION:

Unless directed otherwise, staff are reminded that the content of this manual is strictly classified, and remains site-specific in context. Distribution across sites is a Type-3a offence. Exchange/viewing of copies provided to separate personnel is also prohibited.

Staff suspecting a breach of this regulation are to contact administration immediately.
————————————————————-
FOREWORD

Over the years we have come to accept that an entirely secure facility, equally protected from both internal and external forces, is an impossible equilibrium to correctly achieve. This is why lockdowns are an integrated part of our Foundation system. Entering a mindset in which a goal of absolute control exists is a futile effort. It is important to consider that there is always more that can turn out wrong than right. Not relying on procedures such as these would be a complete denial of the wrong. The Foundation is built upon grounds of acceptance, not ignorance. Don’t be ignorant.

- Dr. Sawer, Head of Site Safety and Containment Regulations Board.
OVERVIEW

A lockdown is defined as a varying emergency procedure in response to a containment breach or loss of security. Lockdowns are requested using an LRC (Lockdown Response Code), and ordered by the O4 communications group. Once evaluated, lockdowns are classified using Lockdown Degrees, which provide pre-created guidance on the appropriate response, such as AMTF (Armed Mobile Task Force) units and Automated Response Initiatives (ARIs), commissioned when appropriate to suppress the apparent threat.
BACKGROUND

Lockdowns first became official standard regulations following the 1931/03/12 containment breach, and multiple on-site accidents resulting in the severe loss of Foundation personnel, material, and vital assets. Since then, the Foundation has made substantial efforts to re-integrate more secure, reliable and dependable methods of repressing internal instability among sites. Some of the first MTFs (Mobile Task Forces), such as Epsilon-11, were commissioned to advance against the increasing number of contained anomalous objects across the Foundation.

For a number of years, over the period known as the “deep waters”, the Foundation was prone to regular breaches and loss of vital assets, due to influencing opposing factions, falling containment standards and disobedience of Foundation personnel, including the creation of the Chaos Insurgency in 1928, where the lowering ethics of the Foundation provoked a unit to go A.W.O.L and re-form as an extremely hostile splinter-group. The response to containment breaches was eventually re-considered and altered by the O5 council in 1935.

Following the containment of multiple Keter-class anomalies in the 1980s, containment breach severity and frequency increased dramatically throughout certain Foundation facilities. New Armed Mobile Task Forces (AMTFs), such as Nu-7 and Eta-5, were founded with the goal of assisting in re-containment and repression of these new threats. Contemporary material science had not developed to a point that would allow for the effective economical containment of these entities. However, as technology advanced, the threats posed by these anomalies and the period known as the “reptile scares” were eventually mitigated by the mid-1990s.

One of the most recent periods involving a Foundation-wide lowering in containment safety involved the infamous “two-naught-seven strikes” throughout 2015, in which eighteen sites were attacked by the autonomously fast, possessive and senselessly lethal entity known as subject two-naught-seven, presumed to have been created by the Chaos Insurgency (CI) in 2011 as an uncontained and un-coordinated biological weapon against the Foundation. The strikes were most effective because they were governed by a complete lack of knowledge regarding a spontaneous attack, the loss of vital security MTF teams, and multiple encounters with civilian populations – attempting to expose Foundation secrecy. Subject two-naught-seven was last observed on the 8th September 2017 in a disused metro station, after assaulting 5 separate MTF divisions and subsequently disappearing under an approaching train.
————————————————————-
EVALUATION
O4 COMMAND

Originally, lockdowns were ordered manually by the O5 council, as a response to a distress call triggered from a select facility. Following the rapid scale of the Foundation expansion, registration and commission of any lockdown is now controlled by another group, known as the O4.

The O4 are responsible specifically for the handling of inbound LRCs and alerts from compromised sites, and the appropriate responses issued to these requests. Because of this, the O4 command is a communicative group, and serve as the organisation team for all lockdowns across the whole Foundation.
LOCKDOWN RESPONSE CODE

A Lockdown Response Code (LRC) is communication technique applied when calling for distress or assistance following a lockdown. A LRC will typically contain a super-compacted description of the situation, represented by 3 values: Site Number, Priority, Class. Understanding of an LRC is short and simple. An example would be “15/A/RED-AMBER, which would request an adequate response at site 15 with immediate action to combat at least one Large-Scale Aggressor (LSA) and possible memetic agents.

Not all members of staff are authorised to order a LRC request. Specifically: site directors, containment organisers responsible for the escaped threat, security teams, and all members of administration, are all authorised to issue an LRC code using specific landline communication routes, should an SCP object escape or hostile incursion occur.

For understanding of an LRC (Site Number, Priority, Class), see below.
SITE NUMBER:

The specific site number in which the situation is unfolding. May be multiple sites.
PRIORITY:

Options range from [A, B, C, D, E] with A requesting the highest priority. Priority levels act as a gauge on how fast and effective the response needs to be. For example, a E-priority lockdown for a memetic hazard may take several days for a response to be compiled, whereas an A-priority with the same threat will be enacted almost instantly with maximum efficiency to combat a maximum threat.

For measure, below are the approximated response times to each priority level.

A – <1 hrs
B – <2 hrs
C – <5 hrs
D – <24 hrs
E – <72 hrs

NOTE: Priority may be a key factor in determining whether response from an AMTF/MTF is necessary, or if the site should be destroyed, and may be used as evidence when arguing for destruction used by the Ethics Committee.
CLASSIFICATIONS:

Lockdowns happen in a multitude of ways, and there are an even larger multitude of things you need to consider as a response. Categorising stops people panicking, and conveys a clear description much faster and more effective than a conversation.

- Dr. Hayward, Retired Head of Site Safety Board.

The classification represents the origin of the threat (NOTE: not the severity — that is determined in the priority value) which will require possible tracking, liquidation or re-containment by foreign MTF teams from other sites. Due to the often unfamiliarity of different sites, AMTF/MTF teams require a way of understanding the threat and generating expectations before they reach the site.

Multiple classifications can be used to describe a more complex-origin threat.

Currently, there are 12 classifications, listed below.
CODE: AMBER

Synopsis: highlights the escape of at least one memetic1, infohazardous2 or cognitohazardous3 threat on-site staff are unable to currently suppress without foreign intervention.

Special Guidance: staff are advised to wait calmly for security to escort them and or otherwise remain still, avoid talking (or otherwise acting as a vector for the agent) and to close eyes/ears as best as possible. Do not evacuate by yourself, wait for security to direct you. Do not intervene with compromised staff affected by the agent. Do not attempt to leave the site.

Listed MTFs: MTF-Eta-10 (“See No Evil”), MTF-Eta-11 (“Savage Beasts”), both specialised in the control of memetic threats.
CODE: BLUE

Synopsis: suggests the escape of a sentient object below human intelligence capable of movement.

Special Guidance: N/A, follow orders from security.

Listed MTFs: MTF-Epsilon-11 (“Nine-Tailed-Fox”)
CODE: SUPERBLUE

Synopsis: suggests the escape of a sentient object equal or above human intelligence also capable of movement.

Special Guidance: identical evacuation plan to CODE: BLUE.

Listed MTFs: MTF-Epsilon-11 (“Nine-Tailed-Fox”)
CODE: GREEN

Synopsis: suggests any possible threat derived from a bio-hazardous4, infectious, or other contamination source5. These may include highly-infectious microorganisms6, biological weapons, or anomalous self-sustaining reactions7 capable of dramatically increasing in severity unless immediately countered. Not necessarily the escape of a single object, a CODE: GREEN may be often used in conjunction with another classification to signify a bio-hazardous threat.

Special Guidance: staff are to avoid contact with any sources of contamination or contaminated individuals above seeking evacuation. Do not leave the site. Staff should expect to be quarantined after the event.

Listed MTFs: Principal MTF deployed to all biohazards threats remains MTF-Beta-7 (“Maz Hatters”). In the case of an anomalous pandemic, MTF divisions will act rapidly in the containment and liquidation of areas affected by such anomalies, which may extend outside of the site if improperly contained. Incidents involving a catastrophic self-sustaining reaction are to be contained by possibly more teams so as to provide maximum efficiency to prevent further spread into an “unrecoverable” situation.
CODE: RED

Synopsis: defines the parameters in which a Large-Scale Aggressor (LSA) such as SCP-2059, has escaped containment and currently poses a substantial threat to the site and Foundation secrecy.

Special Guidance: N/A, follow orders from security.

Listed MTFs: responses are usually of upper priority and almost all available battalion-strength AMTFs are expected to be allocated, such as MTF-Nu-7 (“Hammer Down”) and MTF-Eta-5 (“Jaeger Bombers”). MTF-Gamma-5 (“Red Herrings”) may also be dispatched to liquidate incidents involving possible public exposure/sightings. Expect a high-resource response. CODE: RED lockdowns are frequent and often well-planned, such is a recurring threat from SCP-682, so staff are to remain aware that security teams are prepared.
CODE: BLACK

Synopsis: suggests the escape of a NTT (Non-Terminable Threat) such as SCP-096. A NTT is defined as a threat that, given the circumstances or present resources, is unable to be terminated by response teams during the incident, or are otherwise invulnerable to any form of attack.

Special Guidance: staff and security are advised to avoid confrontation with the NTT at all costs. Do not engage fire on the NTT unless it has been proven to slow/hinder the advance of the threat.

Listed MTFs: MTF-Epsilon-11 (“Nine-Tailed-Fox”), MTF-Sigma-23 (“Backup Required”).
CODE: WHITE

Synopsis: used to describe the assault of a highly-organised major/minor assimilation-force that on-site security are unable to combat.

Special Guidance: staff are advised to evacuate immediately. All SCP objects are to be put into lockdown, and doors/entrances to the site blocked. Data banks may be encrypted to prevent hostile acquisition of vital information. Do not attack hostile combatants unless absolutely necessary. Wait for AMTF battalions to arrive. Security are to protect staff and assets, not to repress the threat. Staff should be aware that defensive ARIs will be selected to combat human targets, and may be indiscriminately deployed during the holding of the site.

Listed MTFs: include all battalion-force AMTFs, such as MTF-Nu-7 (“Hammer Down”).
CODE: GRAY

Synopsis: identical to CODE: WHITE, however highlights that the hostile incursion force originated from within the site, often in the form of false staff members. Conveys that hostiles are already within the site, and that on-site security may be highly disordered and compromised.

Special Guidance: identical evacuation plan to CODE: WHITE

Listed MTFs: include all battalion-force AMTFs, such as MTF-Nu-7 (“Hammer Down”).
CODE: MAGENTA

Synopsis: used to designate a lockdown involving a dimensional threat, including a spatial or temporal alteration8, continuity error9, incorporeal objects10, trans-dimensional entities11, or objects capable of breaking fundamental natural laws and processes.

Special Guidance: Default evacuation plan, unless evacuation shelters are rendered unprotective due to the nature of the threat, in which case site-security will direct you accordingly. MTF teams may require extensive planning before entering the site, so prepare for a possible long wait.

Listed MTFs: MTF-Zeta-9 (“Mole Rats”), MTF-Lambda-5 (“White Rabbits”), MTF-Mu-13 (“Ghostbusters”).
CODE: BLANK

Synopsis: Defines an undescribed threat.

Special Guidance: N/A. Follow orders from security.

Listed MTFs: N/A
CODE: SUPERBLANK

Synopsis: Defines a threat which cannot be described.

Special Guidance: N/A. Follow orders from security.

Listed MTFs: N/A
CODE: COLDSILVER

Synopsis: Defines an event which has or will soon fatally damage the operation of the Foundation. Not for concern of general staff, and unlikely to ever be encountered during your career with the Foundation.

Special Guidance: N/A. Follow orders from security. Expect the eventual liquidation of your department, timescale unpredictable.

Listed MTFs: N/A
————————————————————-
RESPONSE
AUTOMATED RESPONSE INITIATIVES

Automated Response Initiatives (ARIs) are mechanised systems providing a specific counter-measure against a suspected breach.

Deployment of an ARI will recognise the Lockdown Degree issued to the breach. The higher the degree, the more prevalent the ARI.
AR-1: “SAFETY PIN

Initiative responsible for the manually-confirmed detonation of the on-site Alpha warheads located (in cases of subterranean sites) on the surface of the facility. Authorised only in high-threat situations reaching Priority-B, being an effective method of terminating all life directly above, while protecting most sites with underground blast-shielding and remaining mostly intact after deployment. Requires 04 lead operator’s approval for use.
AR-2: “EARLY RETIREMENT

Initiative authorised partial control in the autonomous detonation of the Omega kinetic warheads12 located underneath the main facility. Requires appropriate authorisation from the Ethics Committee.[Further information regarding the AR-200 protocol has been removed as of 03/11/██ by the Ethics Committee. Requesting access to this removed information can be attained through contact of your immediate supervisor.]
AR-3: “BAD OPTICIANS

Program used to apply sensory impairment, such as strobe lights and high-pitch audio to disorientate and repress hostile combatants. Most often utilised when facing external threats such as raids from hostile factions, or entities responding to a standard human sensual environment.
AR-4: “BIG TOASTER

Site-specific program responsible for utilising allocated electrostatic tesla-gates, electrocuting or stunning entities or objects moving at an irregular pace not similar to human movement. On a number of occasions, known to have resulted in the stunning of staff suffering from movement problems, disabilities, or other impairments causing a significant variation in movement speed. Due to this, AR-400 has gained an infamous reputation, and has been moved to requiring at minimum of a Class-C Lockdown Degree to prevent further unnecessary casualties. Disabled staff are continually reminded to ask a site administrator to close the tesla gates before proceeding through an active one.
AR-5: “CLOSING TIME

Issued control over the closure of all doors, communications, utilities and ventilation networks. Can be authorised on-site, and will automatically close select units, compounds and systems to varying intensities, including site gates, sewage systems, power lines, radio channels and issue Protocol 15-A on all data banks, causing most to enter deep-storage. AR-500 is effective due to the rate at which it can respond to a breach, and is one of the most essential response initiatives for any site.
AR-6: “GRANDMA’S ASTHMA

A further infamous response initiative (a common subject of the Ethics Committee) is in direct and full control over the release of gaseous agents into compounds affected by containment breaches. The AR-600 program utilises multiple agents, including sedatives, reversible-paralytics, nerve agents, vesicants and intoxicants. Separate agents are utilised for specific Lockdown Degrees and in varying states of emergency, or to combat specific evaluated threats. The most frequently applied are reversible-paralytics, allowing retrieval staff but not entire elimination of the threat. Areas flushed with vesicants or intoxicants are designed for repression, while nerve agents are used for direct and lethal results. Few sites are installed with AR-600, and complete deployment of nerve agents across the site requires approval from the Ethics Committee.
AR-7: “SINKING SHIP

Initiative program designed to effectively control the “reality anchors” influencing the hume level13 within sites containing trans-dimensional objects. These “reality anchors” essentially combine dimensions, “locking” dimensional entities into the same dimensional space as site guards and MTFs, limiting the effects of objects such as SCP-106.
————————————————————-
EVACUATION

Evacuation of a site is the practice in which staff will withdraw from affected facilities following a lockdown. Evacuations will proceed within the “Evacuation Phase”, the period in which threats are still mostly developing, and have not yet pertained an intensity requiring the closure of the evacuation shelters.
GUIDANCE

Staff involved in any lockdown are to seek evacuation as their highest priority. Detailed evacuation plans and prints can be found in Administration and Security. Smaller plans are also present in each compound. These will direct staff towards the nearest evacuation shelter.

Armed site security staff will also assist in the evacuation process, and divide a team for each affected compound. Teams will accompany personnel to evacuation shelters, and attempt to repress developing threats until MTF units arrive. Staff are advised to follow security teams.

Evacuation shelters can be closed manually if the threat reaches a substantial level, or otherwise given a timeout-lock for 2-3 minutes. Speed and arrival time is critical. Personnel not inside an evacuation shelter before closure are no longer a priority of security, and are handed to the responsibility of MTF units entering the facility. Staff in this situation are advised to hide and not retaliate against threats, or intervene in any way with a struggle or death of another member of staff. Self-preservation is required above the safety of others. Do not startle, distract or expose MTF teams.

Once inside evacuation shelters staff will be registered. Personnel unaccounted for will be added to a staff list for MTF units to retrieve and recover. Staff are reminded that they in the eyes of MTF units are of second priority. A list will also be sent to MTF teams of contained SCP objects and assets within the site that may or may not be an active threat.

Extraction of personnel will commence once all threats have been neutralised or re-contained. Personnel will be examined and quarantined for further evaluation until they are safe from possible contagions, memetic/obsessive effects or post-traumatic stress.
————————————————————-
RECOVERY

The recovery operation can last extended periods of time depending upon the extent of damage or public exposure. Recovery includes the restoration of the site, application of amnestics, re-containment of anomalous objects, registration of staff, evaluation of causes, and liquidation of events.
EVALUATED CAUSES

Causes of breaches and subsequent lockdowns can be categorised into the following classes:

Failure of automated systems, such as gate mechanics, specialised containment systems, or data corruption. Infiltration or incursion from a hostile Group of Interest, (GOI). Members of the Serpent’s Hand and Chaos Insurgency utilise this method of attack with terrorising effect. Disloyalties, unawareness, misjudgements or general faults of containment staff. Underestimated scale of threat and needs for containment of a specific object. Uncontainable anomalous objects. Direct assault or raids from a foreign force. Memetic/obsessive effects or manipulation of staff. This may include actions forced-upon staff members without consent.

Investigation teams will utilise electronic logs, security footage and witnesses among many methods to identify the cause.
INVOLVED PERSONNEL

Personnel involved in the recovery and liquidation operation following a breach are classified into specific teams, each identifiable by a select symbol. This symbol accounts for both colour-blind and visually-impaired staff, and will be found on the uniform of the personnel of interest.

MTF/AMTF units are identifiable from the triple-red lines symbol. Their role in the recovery process is in securing the facility from hostile combatants/anomalous objects, and in the evacuation of surviving staff members. Most MTF teams are armed, and those heavily-armed with military-grade vehicles and specialised weaponry known as AMTFs. MTF teams will only participate in the immediate response and recovery period after a lockdown.

Registration teams are identifiable from the blue ring symbol. Members are responsible for the accounting of surviving staff, lost assets, neutralised anomalous objects, and personnel mortalities/casualties.

Liquidation teams are the backbone of the recovery operation, identifiable from the yellow cross symbol. Members specialise into multiple sub-teams and roles, including application of amnestics on public exposure, clearance of destroyed facilities, treatment of injured personnel, and evaluation of the total damage.

Object-movement teams are identifiable for the orange dash symbol, responsible for the re-containment and movement of anomalous objects, and often work in-turn with MTF units and other field personnel/agents to secure and evaluate the threat. These teams will be present for the early part of the recovery operation.

Investigation teams are not widely recognised and often hide their role for security measures, but are most commonly attributed to a green triangle symbol, and are involved in the evaluation of events leading up to the lockdown, and the ultimate cause. Investigation teams utilise security footage, electronic logs and witnesses (among many methods) to identify the aforementioned.
RE-CONTAINMENT

Re-containment protocols are the methods object-movement teams should follow in order to obtain secure hold over a specific anomalous object. Each threat will have unique re-containment protocols, and the same method will not apply to all.

Large Scale Aggressors (LSAs) are some of the most fundamentally challenging objects to successfully acquire and re-contain with minimal loss. Multiple encounters with SCP-682 suggest the most effective method of securing is through distraction and luring. LSAs are known to rarely reach a docile state, and may have to be surrounded and forcibly constrained by multiple battalion-strength AMTFs once lured into an appropriate location for acquisition. LSAs may reach a critical level of public exposure, and require considerate re-directing away from a nearby civilian population. Evaluation and exploitation of the threat is critical. Sedatives, depending upon availability, are also a viable option. In almost all cases, total neutralisation of the threat should always be considered.

Dimensional threats are those that may involve a spatial or temporal alteration, space-time rupture, trans-dimensional entities, incorporeal objects, separate dimensional existences, or objects primarily un-constricted by natural laws and processes. Methods of securing include luring, such as the practice used on SCP-106, or reality-anchorage; the process in which reality anchors will merge dimensions, reducing, removing or halting the effects of a trans-dimensional entity, and merging the spatial existence of general dimensional anomalies. Dimensional threats are more often than not lost during a breach if not immediately prioritised, and at times are expendable. These threats are seen as being a damaging combination of complexity and severity, and require extensive background knowledge before intervening.

Non-Terminable Threats (NTTs) are defined by an inability to be terminated, and as such neutralisation is never an appropriate option. Escapes involving NTTs are complicated and require extensive evaluation before action while still accounting for maximum speed of response. Breaches involving that of SCP-096, suggest a docile state can be achieved if effectively dealt with. Converting a NTT into a docile state allows for a fast and clean acquisition. Methods include sedation, allowing the entity to achieve purpose (with relative consideration, if a purpose is required at all), manipulation, hypnosis, or other object-specific actions.

Memetic, infohazardous or cognitohazardous threats often meet the requirements for a well-evaluated and assessed plan of action with little account for response speed. Memetic objects may need handling from sensually-inept personnel invulnerable to the danger of viewing, hearing, or touching. By definition, these effects can spread if not well-contained and isolated from site staff unaware of the object. Mediums of transferring these memetic effects into a civilian population must also be removed where necessary and well-considered beforehand.

Contamination sources must be acted upon swiftly and resourcefully. Most teams will divide into separate roles, preventing the spreading of the contagion while also suppressing the initial source. These may include re-animated organisms, self-sustaining reactions, contagious/harmful entities or objects, anomalous infectious diseases, sources of anomalous toxins, carcinogens, ionised radiation, biological weapons or fungal species. Appropriate hazardous-materials suits should be worn corresponding with the apparent threat(s). Although the role of MTFs is in suppression and isolation of the source and affected areas from civilian populations, quarantining of contagious persons and re-containment of the initial source is a responsibility of the object-movement teams. Threats such as these must be dealt with through exact meticulous and remorseless action in remaining ahead of the risks involved.