Magnus Tierce

Item #: SCP-XXXX

Object Class: Euclid (Downgraded from Keter)

E8YHHek.jpg

Special Containment Procedures: SCP-XXXX is located within Area-██. Its rectangular hangar chamber (designated Containment Chamber 45-I, formerly designated Deployment Hangar 01-A) is constructed of reinforced concrete, with internal ribbing constructed of tungsten carbide alloy. The concrete layer is ██ meters thick, with a █ meters thick lining of steel-lead composite beyond. Due to the size of SCP-XXXX, the containment chamber spans 60% of the underground length of Area-██. The personnel access doors to the hangar require keycard access from a containment specialist of Level 3 Clearance or above.

SCP-XXXX-1 is unable to transmit or receive any complex data from outside its containment due to the hangar’s structural composition. Any breaches in this composition may result in a full containment breach and ██% chance of destruction of the Area.

The hangar doors to SCP-XXXX’s containment chamber must remain sealed at all times, and under no account is the blockage equipment and materials beyond the doors to be reallocated or repurposed.

Description: SCP-XXXX is a large, formerly space-capable craft of approximately three (3) kilometers in length, composed of one (1) central hull and two (2) outriggers. Due to its heavy armament, SCP-XXXX is classified as a warship by the Foundation. SCP-XXXX, despite being radio-dated as ███ years old, was nevertheless in nearly pristine condition for said age. However, it had sustained serious damage from an unknown source ██ years ago; while its records show that it was undamaged until that point, SCP-XXXX had then received damage from [DATA EXPUNGED]-class weaponry, rendering it unable to perform exoatmospheric flight.

SCP-XXXX’s armament is detailed in Document XXXX-I.

SCP-XXXX contains a highly advanced sensor suite of gravimetric scanners, radar, IR/NV systems, biological tracking systems, and electromagnetic scanners, giving it an approximate sensor range of ████ kilometers. MTF Mu-4 “Panopticon” has requested usage of these sensor systems, and have successfully utilized them in conjunction with SCP-XXXX-1 to increase the effectiveness of re-containment operations within that range by 43%.

SCP-XXXX’s engine systems are unknown in composition and operation, and SCP-XXXX-1 has refused to disclose any further information. However, there are six exhausts in two banks, powered by SCP-XXXX’s [DATA EXPUNGED]-catalyzed fusion reactor system. This reactor system also appears to provide power to the rest of SCP-XXXX, and as such, is the main focus of Procedure 112-Litany should a containment breach similar to that of ██/██/███ re-occur.

SCP-XXXX-1 is a sapient artificial intelligence within the computer banks of SCP-XXXX. SCP-XXXX-1 identifies itself as SCP-XXXX, and refers to itself as “Threnodia,” which has been determined to be the classification name of SCP-XXXX. SCP-XXXX-1 appears as a young humanoid woman between the ages of ██ and ██, with clearly pointed, large ears, golden-yellow eyes, black hair, and a distinct green tinge to otherwise Caucasian-in-appearance skin.

SCP-XXXX-1 initially appeared as wearing a uniform of unknown rank and significance which did not correspond to that of any other Earth organization, but it has recently begun wearing a Foundation [DATA EXPUNGED] with rank signifiers corresponding to [DATA EXPUNGED]. It is theorized that SCP-XXXX-1 resembles SCP-XXXX’s builders, a possibility which has been remanded to the xenobiology research division of the Area.

SCP-XXXX-1 initially exhibited extreme resentment towards its continued containment by the Foundation, and actively sought to use its then-undiscovered cyberwarfare capabilities to breach Area-██, resulting in [DATA EXPUNGED] casualties and destruction of [DATA EXPUNGED] of the Area. Since SCP-XXXX’s re-containment, however, SCP-XXXX-1 has gradually grown more docile and grown to accept Foundation personnel as its new “comrades-in-arms,” allowing for cooperation between the Foundation and it. This is theorized to be a hardcoded programming response, though Senior Researcher Tierce has posited that SCP-XXXX-1 is intelligently adapting to its new environment.

Its personality is now much calmer towards Foundation members, though SCP-XXXX-1 is still possessed of cutting intelligence, high lateral-thinking and problem-solving skill, and highly persuasive rhetoric and speech. As such, it is not recommended to converse with SCP-XXXX-1 unless necessary, though doing so is reportedly an enjoyable experience. It must be stressed that under no circumstances is SCP-XXXX-1 to be treated as harmless or “tamed;” the consequences of the same approach with SCP-076-2 are still very much recent, and all personnel must remember that SCP-XXXX has potential to cause a [DATA EXPUNGED]-class end of the world scenario, resulting in the deaths of [DATA EXPUNGED] portion of the Earth’s population.

Procedure 112-Litany: In the event of full containment breach by SCP-XXXX, explosive charges placed throughout the ship (concentrated around the main reactor area) will be detonated in an attempt to bring SCP-XXXX down before it attains full flight and optimal weapons range. If the charges fail, [DATA EXPUNGED]-class weaponry installed around Area-██ will be utilized, targeting SCP-XXXX’s engine banks, rear stabilizers, and weapons emplacements. Should the weaponry fail to do significant damage to SCP-XXXX, Area-██ will be required to detonate its on-site warhead before SCP-XXXX leaves the range of the aforementioned nuclear weapon.

Discovery Log: SCP-XXXX was retrieved by elements of MTF Zeta-5 “Roswell” after Foundation orbital assets discovered its crash site in [DATA EXPUNGED], Russia. Its descent had been rendered un-observable by SCP-XXXX-1 interference with orbital assets within range, as well as a visible light-shunting device which was destroyed during the crash. Russian authorities including members of [DATA EXPUNGED] were present at the scene when MTF Zeta-5 arrived; any witnesses were administered Class A amnestics after SCP-XXXX was retrieved.

SCP-XXXX-01 did not reactivate until SCP-XXXX was transported by [DATA EXPUNGED] to Area-██, whereupon SCP-XXXX-1 was forcibly deactivated by [REDACTED] until Foundation officials could reevaluate containment procedures. While [REDACTED] was intended to be permanent, SCP-XXXX-1 reactivated itself, constructing a protocol which later proved to negate the effects of [REDACTED].

Interview Log XXXX-04: (Work in progress)

Incident Log XXXX-09: (Work in progress)

Addendum XXXX-A: For authorization to utilize SCP-XXXX-1 in Foundation operations, consult an Administrator or Senior Researcher attached to the Area with Level 4 or higher clearance. For authorization to use SCP-XXXX-1 in Mobile Task Force armed or containment-related operations, additional authorization must be obtained from the MTF in question’s commander. SCP-XXXX itself may not be used in any operations whatsoever without the express permission of the 05 Council due to the risk involved with its deployment; however, sensor and data processing systems onboard SCP-XXXX count as part of SCP-XXXX-1 and are bound by the strictures thereof.

Document XXXX-I:
(Work in progress)