Link to article: SCP-8667.
component:preview
footer-wikiwalk-nav
===== [[include component:preview text=No procedures currently exist for restoration of containment following a breach of SCP-8667. ]] ===== [[>]] [[module Rate]] [[/>]] **Item №:** SCP-8667 **Anomaly Class:** Keter **Special Containment Procedures:** SCP-8667 is currently held in Isolation Unit 2 on the premises of the now-decommissioned Site-D4. Six generators have been installed in the facility’s remaining outbuildings to provide continuous power to the containment system, at least four of which must be kept continually operational. Servicing of Isolation Unit 2 and its supporting infrastructure is to be conducted by Maintenance Team 8667B on the 1st and 14th of every month according to the technical specifications outlined in the Site-D4 archive. In cases where containment failure is deemed likely without emergency repair, Isolation Unit 2 may be left without power for no longer than 80 seconds. Any abnormalities observed by MT-8667B must be immediately logged with Oversight. No procedures currently exist for restoration of containment following a breach of SCP-8667. **Description:** The nature of SCP-8667 is not known at the present time. ----- **Addendum I—Incident KY6-THETA:** The vast majority of documentation concerning SCP-8667, including original containment procedures, testing logs, and URA material, was lost following a cascading failure of the Foundation’s digital record system on 1979-02-23, subsequently termed KY6-THETA. This incident, while unprecedented, was non-anomalous, and resulted in the loss of most or all data on at least 15 contained anomalies and anomalous objects besides SCP-8667, as well as more than 800 individual files relating to unregistered anomalies. In the months following KY6-THETA, recovery hearings eventually resulted in the creation of Directive 8667-1, which constituted a strict maintenance of existing //status quo// procedures as they pertained to Isolation Unit 2. While fragmentary data suggests these procedures were intended to be temporary holding measures, no means of constructing an alternative can be devised without allowing a containment breach. The reason Isolation Unit 2 was originally deemed non-viable for long-term containment is unknown. Due to SCP-8667’s clandestine recovery, high initial clearance requirements, and interment in a containment unit designed to prevent external interference and observation, it is no longer possible to deduce the form and capabilities of the anomaly. Nor is it possible to surmise the level of threat posed should it be allowed to breach containment. With the exception of Incident IR8667-KAPPA (see Addendum II), Directive 8667-1 has been upheld for the entire duration of the containment project. ----- **Addendum II—Incident IR8667-KAPPA:** At 15:12 UTC on 2001-01-20, a failure of the Site-D4 containment system occurred due to accumulated corrosion on the external power connectors. Isolation Unit 2 lost power for a total of 163 seconds. Investigation by the containment tribunal identified the root cause as "persistent negligence on the part of Maintenance Team 8667A", and resolved to increase operational oversight on the SCP-8667 containment project. This suggestion was taken under advisement by Containment Ops, though no resolution to alter existing special containment procedures has yet been reached. It is unknown whether IR4-KAPPA constituted a containment breach of SCP-8667. As of the current date, Directive 8667-1 remains in effect. [[footnoteblock]] [[div class="footer-wikiwalk-nav"]] [[=]] << [[[SCP-8666]]] | SCP-8667 | [[[SCP-8668]]] >> [[/=]] [[/div]]