COVER PAGE DO NOT EDIT
Item #: SCP-A
Object Class: Euclid
Special Containment Procedures: SCP-A1 is to be kept in the Site 72 anomalous vehicles garage. Wheel locks are to be placed to prevent SCP-A from being moved, and a specialized lock has been created to prevent rotation of SCP-A's launcher. The keys to SCP-A are to be kept in a locker in the Low-Priority Containment Wing of Site 72. SCP-A is only to be fired with the direct approval of an O5 Council member, or in the event of a DK-class scenario, at the discretion of the Site Director. PAC-2 missiles are stored in the Site 72 armory for this purpose.
![]() |
|
| SCP-A, pictured at Site 72 firing range. |
|---|
Description: SCP-A is a trailer-mounted M901 Launching Station designed to launch Patriot PAC-2 anti-ballistic missiles, and its accompanying tractor unit. Both have been heavily with a multitude of paratechnological and anomalous additions, allowing the object to detect, track, and fire upon targets with none of the outside systems usually required by the Patriot system. Modifications include an array of Kant counters, multiple demonic circuits of unknown function, thaumic protection and perception wards and additional control and monitoring equipment within the cabin. This equipment appears to be drawn from a number of civilian and military sources, with parts manufactured as early as 1987 and several components which are still in development or which could not be identified.
SCP-A's software is similarly amalgamated from portions of the launcher's original code, several stock-trading applications, segments of a Foundation Artificial Intelligence Construct template, an unknown artificial intelligence likely created by the Global Occult Coalition, and significant amounts of the source code of the video game "Homeworld." The significance or purpose of much of this software is unknown, though investigation has revealed that a significant portion of the code is dedicated to performing a series of thaumic rituals of exorcism and dispelling of spirits.
When loaded with standard PAC-2 missiles and powered, the internal controls of SCP-A display a a 3-dimensional topographic map of the nearby area, with several objects highlighted as potential "targets."2 SCP-A will prompt the user to select one of these targets, and then to fire. Once fired, SCP-A will display a brief loading screen before the missile is fired. During this period, which lasts no more that 7 seconds, the launcher platform displays severe reality distortions and several thaumic wards imprinted on the launcher will activate.
Missiles fired from SCP-A display several anomalous properties while in flight. Chiefly, the missiles gain
Item #: SCP-B
Object Class: Safe
Special Containment Procedures: SCP-B is to be stored in a climate-controlled class 7 containment chamber at Site 72. This chamber is to be optimized to prevent corrosion of SCP-B's metallic components. SCP-B-a instances are to be stored in separate climate controlled lockers. The information stored therein is to be added to the Foundation Archival Records Network and made available under level 3 clearance. All attempts to contact Sol-Actual are to proceed under Project Iris.3
Hyperion Technologies Secure Internal Mail System
To: Alfred Hathaway, CEO
From: David Noel, CTO
Subject: Fire recovery
Al,
I've attached the detailed summary, but I'll spare you the read: We got it bad, but it could have been way worse. We lost most of our archeology and medical files, but those are backed up on location, and the weekly backup captured some of the files before it got interrupted. Camera footage of the past week is bust, unfortunately, which sucks for insurance, but Nelson will figure something out. Other than that we didn't lose anything we don't already have backed up, and the Odyssey files are fine. I'm going to be picking through our backups and trying to recover camera feeds for the foreseeable future, so if you need me try my cell.
Attachments: Fire_Damage_Report.odt
Hyperion Technologies Secure Instant Messaging System
Participants: Alfred Hathaway, CEO (BossMan1986); David Noel, CTO (DeleteThis)
Timestamp: 11/7/18, 3:43 PM-3:50 PM
DeleteThis: Al we have a problem
BossMan1986: Is it urgent? In a meeting with Legal rn.
DeleteThis: Very.
DeleteThis: I'm running through the partial backup on our satellites and comparing it with the backups at our research sites, and there are some serious discrepancies.
BossMan1986: Well it is a partial backup, right?
DeleteThis: That's the problem: the backup has more files than the research site.
BossMan1986: What?
DeleteThis: Exactly. Specifically, the Nevada dig site is apparently missing several files from the past two weeks. I'm reading through them now, and it looks like they found something? None of the dig site's local logs say anything about this.
BossMan1986: Found what?
DeleteThis: Dunno, still reading. Gimme a minute.
BossMan1986: OK. Wrapping things up w/ Legal.
Idea:
- Non-anomalous corporation discovers/creates anomaly by accident
- Foundations finds out, contains it, wipes memory/files, but they botched the job
- corp begins to piece together what happened to them. go after foundation, discover the Masquerade
Image: https://commons.wikimedia.org/wiki/File:JASDF_MIM-104_Patriot_PAC-2_7t_Tractor(Mitsubishi_Fuso_Super_Great,_49-2249)_with_M901_Launching_Station(49-3157)_left_front_view_at_JGSDF_Camp_Nihonbara_October_1,_2017_01.jpg






Per 



