Initial results from Omicron-Rho operatives 
were outstanding. Despite only a basic 
grounding in military vehicle operations, the 
subjects outperformed even experienced 
operators in all aspects of testing and quickly 
became adept at simple "milk runs". The 
recommendation was made to advance to the 
weapons testing phase. Prior to the Omicron- 
Rho results, in-built vehicular weaponry had 
been disabled for safety reasons. Military 
advisors to the project had hopes of creating a 
small, specialised squadron of combat 
vehicles able to be operated across 
continental distances and in real time, allowing 
commanders all the benefits of manned 
vehicles without the limitations of modern 
drone technology and with zero risk of 
operator casualties. However, the project lead 
was unable to secure the co-operation of all 
Omicron-Rho recruits to this end. 


On 13/10/2016, Omicron-Rho operative 
Caroline Amina Rostam announced her 
departure from the project, following a series 
of incidents in regards to aquiring additional 
compensation for her position as a consultant 
and evidence of deteriorating mental health. 
Summarily, an additional three operatives 
followed suit over the following weeks, with 
only two operatives currently remaining on the 
project. 


As of 01/11/2016, the future of Project Driver is 
still in dispute. 


Access Addendum 2942-B-01 


Extract from official probe r.e. Project 
Driver d.d. 15/10/2016 


Interviewer: Senior Researcher J.D. Pollock 


Interviewed: Caroline Amina Rostam; MTF- 
Omicron-Rho operative, fmr. Project Driver 
consultant 


[begin log time 20:59.03 15/10/2016] 


Pollock: Some very important people have put 
a lot of money into this project, Rostam. You 
think they're just going to let this slide? 


Rostam: | won't say it again; / didn't sign up 
for what those people are suggesting, my 
colleagues didn't sign up for it, and we 
certainly didn't sign up knowing the real risks 
involved. And yes, Pollock, they are very real 
risks. The higher-ups can dish out whatever 
punishment they see fit, but I'm not putting my 
mind and body on the line for their ten-million- 
dollar obsession. 


antidote for the extremely recently exposed, but if the infection took 
place prior to the "cutoff point" of the amnestic used, (re)infection 
and memory alteration takes place rapidly. Class-B and Class-C 
amnestics are of moderate effectiveness in "curing" an infected 
individual, albeit with fairly high risk to the patient. Class-B are 
recommended when the time of infection is unknown, or for those 
individuals that Class-A drugs have failed to cure. Class-B drugs 
have a significant chance of erasing the memories which contain the 
agent (and all other long term memory), but anything still held in 
short-term memory poses a chance for re-infection; therefore, Class- 
B amnestics should be avoided if at all possible. While they will 
erase the memetic agent, the infectee will remain extremely 
vulnerable to re-infection until he is back to a normal functioning 
state and has been briefed regarding events transpired. 


Further testing and research into possible weaponization of 
SCP-351-1 is currently pending administrative approval. 


« SCP-350 | SCP-351 | SCP-352 » 


Pollock: Are you stil! going on about 2942? 


[scraping, footsteps as interviewed leaves 
chair and steps away from table] 


[no attempt at communication by either party 
for several seconds; protracted exhalation 
from interviewed] 


Rostam: Pollock. You listen closely to me 
now, you manipulative little prick. No more 
games. You /ied in that report. You lied by 
omission. It was me who told you that 2942 
was affecting us psychologically. When | said | 
should be being paid more for this, | wasn't 
demanding... perks for my consultancy. | said 
that because | wasn't told beforehand that I'd 
be melding minds with a mind-affecting 
anomaly. 


Pollock: Oh, come on! 


Rostam: No, you come on, Jeffery. I've told 
you that 2942 isn't just a projection 
phenomenon. | didn't realise it at first... 
Couldn't. | wasn't sensitive enough. But the 
dash-threes are living beings in their own right. 
Each one is a broken-off piece of a larger 
consciousness, distinct from our own. It's not 
human. It was born deep in that bug-ridden 
database, and it was smart enough and 
powerful enough to engineer a way out of 
there that was within its means. When | take 
control of that tank, | fee/ my dash-three's 
thoughts. It's a parasite with its roots snaking 
into the folds of my brain from across an 
ocean, using my mind as a fuel source to 
sustain its own physical form. The more | 
trained, the deeper its roots dug in. Getting 
stronger right along with me. The 
manifestations started becoming more real. 


[footsteps] 


Rostam: Have you seen them? They have 
organs now, for Christ's sake. 


[rustling of hair; laboured breathing from 
interviewed] 


Rostam: | keep seeing its face in my dreams. 
The face it'd like to have. The hands that give 
it the power to manipulate a world limited to a 
dark, cramped cockpit. Metallic-cold. It's 
becoming more and more like its own person - 
if you can call it that - and sometimes | feel like 
I'm fighting it for control. Like | don't know 
who's driving who anymore. 


Pollock: Rostam, please... don't- 


Rostam: I'm not comfortable with that, Jeffery. 
My head is my safe place, don't you 
understand? My only safe place. Now you're 
filling it with guns and bombs and all that thing 
ever thinks about is guns and bombs and 
screaming engines. And what it's like to taste 
fresh air. 


[brief click of intercom button being depressed] 


Pollock: [into mic] | think you need to send 
someone in here. 


Rostam: I'm not going back into that cockpit. 
Nuh uh. You hear me? Nuh uh. No more. 


[end log time 21:02.39 15/10/2016] 


Footnotes 

1. NaTIS stores, records and manages information pertaining to 
South African vehicle regulations, and serves as a national vehicle 
registry. 

2. The definition of what constitutes a vehicle appears to be broad in 


this case; see Document 2942-A. 

3. This category comprises common passenger vehicles, goods 
vehicles, trailers and agricultural tractors. 

4. In light of the events of Incident 2942-45-F, physical interference 
with instances of SCP-2942-3 is strongly discouraged. 

5. e.g. depressing the accelerator pedal of SCP-2942-2 will cause 
an instance of SCP-2942-3 to simultaneously increase the throttle in 
a light aircraft, regardless of the distance between the two vehicles. 
6. Research indicates that the phenomenon is more complicated 
than initially believed - see Document 2942-B. 

7. The written consent of the previous owner is required for this 
process, but need not be supplied voluntarily. 


« SCP-2941 | SCP-2942 | SCP-2943 » 


SCP-2943: In Case Of Emergency, Break Glass 


Item #: SCP-2943 
Object Class: Thaumiel 


Special Containment Procedures: SCP-2943-A is currently within 
the boundaries of Site-51. A digital display showing the current date 
and time is to be kept within visible range of this manifestation point 
at all times. A timer counting down until precisely 8,640 minutes 
have elapsed since the previous SCP-2943 manifestation is to be 
kept running at all times, and reset as required. Tests conducted 
with any SCP-2943 instances are to be catalogued in the SCP-2943 
Testing Log. 


All instances of SCP-2943-1 are to be catalogued according to 
manifestation time and stored accordingly. New instances of 
SCP-2943-1 are to be timestamped immediately for ease of 
cataloguing. 


Instances of SCP-2943-2 are to be processed similarly to 
SCP-2943-1 before being transported to Lunar Area-32, to facilitate 
satellite imagery of the Earth as depicted through each instance, to 
assist in determining the cause of their manifestations. SCP-2943-2 
are to be stored at Site-51 when not in use, separately from 
SCP-2943-1 instances. 


Additional procedures for Level 3 or higher personnel only. 


SCP-2943 storage areas are to be frequently inspected 
for the appearance of SCP-2943-3 instances. The 
content of SCP-2943-3 instances is to be recorded and 
available information utilised to prevent the reoccurance 
of any observed K-Class scenarios. Information 
regarding SCP-2943-3 instances is restricted to Level 3 
or higher clearance. 


In the event of an impending severe K-Class scenario, Procedure 
SATURN LAMENT is to be initiated as a last resort. Under no other 
circumstances whatsoever are any potentially destructive tests to be 
conducted on any SCP-2943 instances. 


Procedure SATURN LAMENT: Information detailing pivotal events 
regarding the imminent K-Class scenario, such as events that 
directly instigated the event or alternate outcomes that were not 
explored, are to be left exposed within reasonable distance of 
SCP-2943-A until an SCP-2943-1 or SCP-2943-2 instance 
manifests. Once this has occurred, an available SCP-2943-1 or 
SCP-2943-2 instance that manifested prior to the first event pivotal 
to the impending K-Class scenario the most recently manifested 
SCP-2943-1 or SCP-2943-2 instance is to be destroyed by any 
means necessary. 


Description: SCP-2943 is the collective designation for a group of 
glass octahedrons that manifest at a predefined point, designated 
SCP-2943-A, relative to the Earth's inner core. Looking through an 
SCP-2943 shows the observed environment as it was at the time of 
the instance’s manifestation. The instance is unable to pass through 
solids or liquids that are visible through it, which become permanent 
obstructions for the instance. No passage of time is observed in 
depicted locations, with the exclusion of detectable subatomic 
particles and energy, which do not suffer from any measuarble 
diminishment in quantity or energy. 


Testing performed utilising localised temporal distortion! has 
confirmed that SCP-2943 instances are immune to such effects — 
instances manifest precisely once every six days, following an 
indeterminate ‘rate’ of time theorised to be analogous to that of 
SCP-1485-A. Attempts to accelerate or decelerate the rate that 
SCP-2943 instances manifest at have universally failed. 


SCP-2943 instances are classified under one of three superficial 
designations: 


SCP-2943-1 are instances that manifest precisely six days following 
the most recent SCP-2943 manifestation, as expected. 


SCP-2943-2 are instances that superficially manifest at random 


periods of time, typically more than twenty-four hours earlier or later 
than expected. As the SCP-2943 phenomenon cannot be induced to 
manifest instances earlier or later than the six day period, the 
manifestation of SCP-2943-2 logically means that a large-scale 
temporal distortion was occuring prior to, or during the 
manifestation. Beyond this superficial difference, SCP-2943-2 are 
identical to SCP-2943-1. 


Information regarding instances of SCP-2943-3 is restricted to Level 
3 or higher personnel. 


+ Level 3 or higher only. 


SCP-2943-3 are instances that have manifested at a 
future date prior to a chronological rewind occuring. 
Inducing contradictions between observations and reality 
at the approximate time the instance manifested does 
not produce any expected detrimental effects, such as 
causal loops or paradoxes. SCP-2943-3 instances 
typically appear in locations where instances of 
SCP-2943-1 and -2 are stored, rather than manifesting at 
SCP-2943-A. 


The future states of locations observed through 
SCP-2943-3 instances have on average a 23%* 
probability of displaying prominent signs of various K- 
Class scenarios in effect, or their aftermath. The majority 
of remaining Foundation personnel are investigating 
events that directly contributed to the K-Class scenario, 
how they could have been prevented, and methods of 
inducing a chronological rewind? Several instances show 
a noteworthy proportion of Foundation personnel 
abandoning their assignments in order to partake various 
forms of self-indulgence. 


Addendum 1: Xyank/Anastasakos Project Overview 
Xyank/Anastasakos Project 


Synopsis: 
SCP-2943 instances enable us to actively observe the 


value of local tachyon fields as they were at the time of 
the instance’s manifestation. This, coupled with the 
recent discovery that tachyon fields can be manipulated 
by use of radio waves, presents the opportunity for the 
development of a device capable of diminishing, if not 
outright neutralising temporal distortions within an area 
of effect. 


Proposal: 
A device will be constructed that contains the following: 


¢ Two tachyon field detectors 

¢ An AM/FM radio transmitter capable of 
broadcasting at VHF/UHF 

¢ An internal processing unit 

* One instance of SCP-2943-1 


The device will be constructed as follows: 


* A tachyon field detector will be altered in order to 
enable it to record the intensity of a tachyon field 
via the SCP-2943-1 instance, giving an 
approximate ‘baseline’ value. 

The second detector will record the intensity of the 
tachyon field in the environment surrounding the 
device. 

The central processor will analyse the difference 
between the recorded values of each emitter, and 
utilise the built-in AM/FM radio transmitter to emit 
radio waves sufficient to manipulate the tachyon 
field of the surrounding environment to match the 
field recorded through the SCP-2943-1 instance. 


This would ideally result in a complete neutralisation of 
any temporal distortion within the device's area of effect, 
reverting the rate of time to the baseline that the 
SCP-2943-1 instance follows. 


Issues: 
The portability and effectiveness of this device would 
strongly depend upon its power source. A larger power 


source would ensure an extended lifetime for the device 
before replenishment or replacement is required, 
however would make it significantly more difficult to 
relocate and utilise; likewise, a smaller power source 
would make the device more portable and easier to 
rapidly deploy, but will significantly stint the effectiveness 
and lifetime of the device. 


Project approved by Foundation Administrative Council. 
High priority status granted by Overseer Council. 


Addendum 2: 
+ Level 4 or higher personnel only. 


Contact with Site-64T was unexpectedly lost on / / 
Video surveillance of SCP-2400 showed the door 
spontaneously closing between frames without any 
discernable cause. 


Contact was re-established with Site-64T once 
SCP-2400 was reopened. On-site staff reported that a 
chronological rewind event had just occurred, believed to 
have been caused by the destruction of an SCP-2943 
instance. Investigation of the backup database situated 
in Site-64T4 revealed several discrepancies in 
SCP-2943's records, as well as the following information 
appended to its primary documentation: 


Overseer verification: [DATA REDACTED BY 
O5 COMMAND] 


Current date is / / 


Weekly report of Site-64T (received hourly) 
was received several minutes early and 
purported the date external to SCP-2400 to be 
/ /  . On-site personnel insisted this dating 
should have been accurate; accurate 
predictions of imminent, minor issues 
supported the theory of a chronological rewind 


rather than a memetic/infohazardous anomaly. 


Comparison of backed up files showed several 
inconsistencies in storage records for 
SCP-2943; specifically, an instance of 
SCP-2943-1 was recorded to have manifested 
on this day, which did not occur. Multiple 
instances of SCP-2943-3 appeared in 
containment that have been confirmed to be 
recorded as -1 or -2 instances in the backup. 
Strongly suggests a relation.