FOUNDATION STANDARD ORIENTATION MANUAL

1. Scp Containment Breach Door Codes
2. Scp Entrance Zone Code

Msd8 @ Jul 18 2012, 08:23 PM wrote: okay i was playing scp containment breach and i stumbled Apon the doctors offices. I dont know anyone of the access codes though. I was wondering if you guys found them? SCP - Containment Breach. Contribute to Regalis11/scpcb development by creating an account on GitHub.

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 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.

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.

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/Iota-Gamma, 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 memetic¹, infohazardous² or cognitohazardous³ 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-hazardous⁴, infectious, or other contamination source⁵. These may include highly-infectious microorganisms⁶, biological weapons, or anomalous self-sustaining reactions⁷ 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 alteration⁸, continuity error⁹, incorporeal objects¹⁰, trans-dimensional entities¹¹, 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

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-100: '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-200: 'EARLY RETIREMENT'

Initiative authorised partial control in the autonomous detonation of the Omega kinetic warheads¹² 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-300: '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-400: '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-500: '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-600: '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-700: 'SINKING SHIP'

Initiative program designed to effectively control the 'reality anchors' influencing the hume level¹³ 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 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.

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.

END OF MATERIAL

All anomalous objects, entities, and phenomena requiring Special Containment Procedures are assigned an Object Class. An Object Class is a part of the standard SCP template and serves as a rough indicator for how difficult an object is to contain. In universe, Object Classes are for the purposes of identifying containment needs, research priority, budgeting, and other considerations. An SCP's Object Class is determined by a number of factors, but the most important factors are the difficulty and the purpose of its containment.

These are the most common Object Classes used in SCP articles, and make up the bulk of the objects.

Safe

Safe-class SCPs are anomalies that are easily and safely contained. This is often due to the fact that the Foundation has researched the SCP well enough that containment does not require significant resources or that the anomalies require a specific and conscious activation or trigger. Classifying an SCP as Safe, however, does not mean that handling or activating it does not pose a threat.

For a complete list of Safe-class articles on the site, click here.

Euclid

Euclid-class SCPs are anomalies that require more resources to contain completely or where containment isn't always reliable. Usually this is because the SCP is insufficiently understood or inherently unpredictable. Euclid is the Object Class with the greatest scope, and it's usually a safe bet that an SCP will be this class if it doesn't easily fall into any of the other standard Object Classes.

As a note, any SCP that's autonomous, sentient and/or sapient is generally classified as Euclid, due to the inherent unpredictability of an object that can act or think on its own.

For a complete list of Euclid-class articles on the site, click here.

Keter

Keter-class SCPs are anomalies that are exceedingly difficult to contain consistently or reliably, with containment procedures often being extensive and complex. The Foundation often can't contain these SCPs well due to not having a solid understanding of the anomaly, or lacking the technology to properly contain or counter it. A Keter SCP does not mean the SCP is dangerous, just that it is simply very difficult or costly to contain.

For a complete list of Keter-class articles on the site, click here.

Thaumiel

Thaumiel-class SCPs are anomalies that the Foundation specifically uses to contain other SCPs. Even the mere existence of Thaumiel-class objects is classified at the highest levels of the Foundation and their locations, functions, and current status are known to few Foundation personnel outside of the O5 Council.

For a complete list of Thaumiel-class articles on the site, click here.

Neutralized

Neutralized SCPs are anomalies that are no longer anomalous, either through having been intentionally or accidentally destroyed, or disabled.

For a complete list of Neutralized-class articles on the site, click here.

The following Object Classes are sub-classes that supplement the object's primary (or former) classification.

Explained

Explained SCPs are commonly articles about anomalies that are completely and fully understood to the point where their effects are now explainable by mainstream science or phenomena that have been debunked or falsely mistaken as an anomaly.

For a complete list of Explained-class articles on the site, click here.

Esoteric/Narrative Classes

Esoteric Object Classes, also occasionally referred to as Narrative classes, are Object classes that do not fall into any of the above sections. They are generally only used once and are created to further the narrative in a particular SCP. It is highly recommended that SCPs use one of the standard Object Classes listed here. While some authors choose to introduce exceptions to these rules, they are only very rarely done and need to justify their existence and placement. Many site members will downvote for non-standard Object Classes if used without merit.

For a comprehensive list of Esoteric Object Classes and the articles that use them, click here.

Decommissioned

Scp Containment Breach Door Codes

Decommissioned SCPs are an Object Class that was used by senior staff in the past to not only delete unwanted articles but place them in a sort of 'Wall of Shame' to serve as examples of what not to do. This Object Class is not used anymore.

Decommissioning articles is not done anymore, partly because such heavy-handed edits by SCP staff are no longer allowed and partly because decommissioning ended up backfiring. See the History of the Universe Hub for more historical information about Decommissioned SCPs and their usage in the past.

What is the Locked Box Test?
The Locked Box Test is an informal guideline used to determine an object's most appropriate Object Class. It goes like this:

• If you lock it in a box, leave it alone, and nothing bad will happen, then it's probably Safe.
• If you lock it in a box, leave it alone, and you're not entirely sure what will happen, then it's probably Euclid.
• If you lock it in a box, leave it alone, and it easily escapes, then it's probably Keter.
• If it is the box, then it's probably Thaumiel.

Note that as a special consideration, something that is autonomous, alive, and/or sapient is almost always at least Euclid-class. That is, if you lock a living thing in a box and forget about it, it will eventually suffocate or starve to death, and that's not a good outcome. Something that is intelligent could also end up being smart enough to outwit its containment procedures and/or stop cooperating with the Foundation's attempts to contain it, making it more dangerous than it otherwise might be.

What if I find an SCP that is the wrong Object Class?

The Object Classes are intentionally left vague as to not limit the author's creative freedom; a rigid, defined system of classes might hinder an author's ability to write the way they would want to, and as such multiple proposals to create better-defined systems in the past have been turned down by SCP Wiki staff.

If you find an SCP article that you feel might be inappropriately classified, feel free to raise discussion on the topic and see what other community members think. If the explanation is not to your satisfaction, then feel free to express your opinion on the matter and vote accordingly on the page.

Scp Entrance Zone Code

If an SCP is very dangerous should its Object Class be higher?

No, danger does not really affect an SCP's Object Class. As has been reiterated several times above this, an item's Object Class is more based on the difficulty of containment rather than the danger it otherwise poses. For example, a button that can destroy the entire universe when it's pressed would be safe, whereas a cat who randomly switches places with another cat anywhere on earth would be considered Keter.

If you have any other questions about Object Classes, feel free to ask in the discussion.