To: Dr. John Blanchard (of.pcs.ce| 
hcnalbj#of.pcs.ce|hcnalbj) 


Message Subject: SCP-3101 Updates 
Attachments: (1) scp3101_draft2.pdf 
Message Body: 


Blanch, it looks like the consistent case here is 
that 3101 wants a human body. Obviously this 
is a great fix for getting the database's security 
out of the line of fire for good (if we can move 
its code permanently out of whichever of our 
servers it latched onto, that is — for all we 
know it's playing dumb and copying itself twice 
over every second that passes), and we can 
get approval to use a healthy D-class as the 
host in a split second, but given the anomaly's 
behavior it's... probably a very large can of 
worms to open. | don't know. 


The problem, of course, is that we can't do that 
unless we somehow find its actual source 
(whatever bundle of code this thing is coming 
from, that is) and even then the chances are 
slim that we could make it work, even with the 
technology we have. I've told the writer I'm 
talking to that she can go ahead and mention 
this topic in its article, but I'm thinking we might 
want to hold a department-wide vote on it? 
Doesn't feel like something just a few of us 
should be deciding. In a few days, when we 
get this case as settled as possible without 
further information, let's send out the standard 
email and inform people of what's going on 
here. 


Any objections? 
-Elaine 


Date: April 09, 2017 08:02 


From: Dr. John Blanchard (of.pcs.ce| 
hcnalbj#of.pcs.ce|hcnalbj) 


To: Elaine Starck (of.pcs.ce|kcrats#of.pcs.ce| 
kcrats) 


Message Subject: Re: SCP-3101 Updates 
Attachments: none 
Message Body: 


Sorry, | had a headache and went home early 
last night. Alright, so with a clear head now 
that it's morning, let me get my thoughts 
together on this: 


We have two options here, it looks like. Well, 
three. One is that we never find 3101's source 
code and it pesters every single person on this 
network for... forever? | really, really don't like 
that idea, and neither would the O5 Council if 
we end up bumping this up to them (which, 
given the ridiculousness of the anomaly's 
nature, | really don't want to, but you know 
how it goes). 


The options that will keep IntSCPFN safe are 
the following, as you know: One is that Mu-4 
finds this thing's source code and kills it. That's 
the logical option, but you and | both know that 
no one in our department (including us) would 
approve killing off a sapient entity just because 
it's the easy option. The other option here is 
giving it what it wants, that being transfer to a 
human host, but then we're facing medical 
complications and probably the most 
painstakingly rigorous personnel screening 
we've ever had to develop. You look at how 
that thing talks to people in text, and put that 
behavior in a human body? That is an absolute 


nightmare. We'd have to double or triple the 
standard level of psych and behavioral testing 
we already do for humanoid containment 
personnel, and even then we can't rule out- 
you know what | mean, I'm not even going to 
bother to finish the sentence. 


In summary, it's objectively unethical to kill it, 
provided we find the source code. The ethical 
option /s the alternative, and said alternative is 
a gigantic pain in the ass no matter which way 
you look at it. 


| think the smartest option is to get that writer 
to finish up the article, post these emails as an 
addendum in the interest of information 
availability (we'll have to work out something to 
protect the file in the database, though, or 
3101 will read about itself and get paranoid), 
and then get the following accomplished and/ 
or discussed by both 3101's containment 
personnel and the entirety of our department: 


1. Hold an EC-only vote on whether or not 
to terminate 3101. 

2. Interview our Site's (that's the easiest/ 
closest option) medical personnel about 
the possibility of transferring a digital file 
to a human host, determine whether the 
amnesticization the D-class would 
receive beforehand would cause 
permanent brain damage that would 
affect 3101 later down the road, etc.. 
Figure out the logistical and medical 
aspects before we jump straight into a 
vote. 

3. Provided the above is possible, hold an 
EC-only vote on whether or not to 
transfer 3101 to a human host. 


Let's discuss these and go from there. For 


now, let Lambda-12 handle 3101 and Mu-4 
handle finding 3101. Tell the writer that | don't 
have a problem with letting other personnel 
talk to it, but that | don't advise it at all. The 
bottom line is that we need to keep the 
database safe. We should be able to have 
results within a month, | would hope. 


John 
Vv Show Ethics Committee Correspondence Records: May 2017 


Irrelevant conversational and unrelated emails have 
been removed. 


Addendum Ill: Ethics Committee Correspondence 
Records: May 2017 


Date: May 11, 2017 09:34 


From: Elaine Starck (of.pcs.ce| 
kcrats#of.pcs.ce|kcrats) 


To: Dr. John Blanchard (of.pcs.ce| 
hcnalbj#of.pcs.ce|hcnalbj) 


Message Subject: SCP-3101 Updates (May) 
Attachments: (1) scp3101_draft6.padf 
Message Body: 

Hey John, 


After several weeks of silence from anyone 
other than the writer on 3101's investigative 
team, I've finally got an update on the article. 
This should be the last revision of it. They're 
gonna put our April emails in it for reference. | 
attached the draft of it to this email. 


Mu-4's commander finally reached out to me 


as well (so far it'd been only Rogers of 
Lambda-12 actually paying attention) and 
informed me that they think they have a lead. 
One of our server banks in Arizona had a 
break-in in the last five weeks. Security 
Director of that Site said they logged it as a 
standard breaking-and-entering, that the 
offenders were civilian, but we're not quite 
sure. Mu-4 got permission to enter that Site 
and investigate more thoroughly. They think 
they found it, but they're not touching it until 
they get our approval. 


Mu-4's commander said that the break-in was 
on April 4th. That's the same day that 3101 
first talked to Argent, so we're definitely in the 
"no coincidences" zone on that one. When the 
team entered the area of the break-in, they ran 
their diagnostics and did their inspections and 
ended up finding an unknown attachment on a 
server bank. The commander told me that 
when they examined it, they found that it was 
some sort of little robotic device; it had a 
rounded box with magnets for its main body, 
and you could see circuitry inside, but it had all 
these thin-as-wire little metallic attachments 
that had actually managed to shove 
themselves into the server ports and extend 
for God knows how long down into the inner 
workings of the servers. This thing shot its 
arms into the server bank, and obviously the 
commander thinks that "yank off the head" 
isn't going to be a smart option here. 


Five of the Mu-4 members want to try 
electrocuting the thing, but obviously that'll 
cause a network crash and billions in server 
repairs afterward. From what | gather, they're 
trying to determine if it's worth the risk or not. 


Elaine 


[EXTRANEOUS CONVERSATION 
REMOVED] 


Date: May 11, 2017 11:27 


From: Elaine Starck (of.pcs.ce| 
kcrats#of.pcs.ce|kcrats) 


To: Recipient Group: eth_com 


CC: Amelia J (of.pcs.ikiw|jjyma#of.pcs.ikiw| 
jjyma), Dr. John Blanchard (of.pcs.ce| 
hcnalbj#of.pcs.ce|hcnalbj) 


Message Subject: SCP-3101 Briefing and 
Preparation for Voting 


Attachments: (1) scp3101_draft6.pdf 
Message Body: 
Fellow chairpersons, 


Last month, the existence of a sapient 
infohazard, now designated SCP-3101, came 
to my attention. The most recent iteration of 
the article is attached to this email. Please 
read the attachment and the below additional 
information: 


Several weeks ago, there was a break-in at a 
server site in Arizona. Mu-4's commander said 
that the break-in was on April 4th. That's the 
same day that 3101 first talked to Argent. 
When Mu-4 entered the area of the break-in, 
that Site's team said it had looked like a 
standard civilian break-in, but Mu-4 ran their 
diagnostics and did their inspections and 
ended up finding an unknown attachment on a 
server bank. The commander states that when 


they examined it, they found that it was some 
sort of robotic device; it had a rounded box 
with magnets for its main body, and you could 
see circuitry inside, but it had hundreds of little 
metallic attachments that had actually 
managed to shove themselves into the server 
ports and extend into the inner workings of the 
servers. Mu-4 states that removing the main 
body of the entity is not advisable. 


It is notable that doing so will likely cause a 
network crash and billions in server repairs 
afterward. We are trying to determine if it's 
worth the risk or not. 


Now that SCP-3101's source point has been 
located, it is necessary to hold a vote on the 
following choices: 


1. SCP-3101 should be terminated, 
regardless of its sapience. 

2. SCP-3101 should be extracted from the 
server and physically contained (see 
parameters of this in SCP document). 


Please vote with a yes or ano. This vote will 
not allow abstaining. Vote by means of 
replying all in this email chain. 


With urgency, 

Elaine Starck 

Co-Director, Ethics Committee Department of 
Sentient and Sapient Anomalies 


Date: May 11, 2017 18:45 


From: Elaine Starck (of.pcs.ce| 
kcrats#of.pcs.ce|kcrats) 


To: Dr. John Blanchard (of.pcs.ce| 
hcnalbj#of.pcs.ce|hcnalbj) 


administered to the members of the archaeology team. 
Addendum 390-01: Transcript of Recovered Documents 


The following set of vellum documents written in Hellenistic Greek 
were discovered in a sealed container at a dig site adjacent to the 
primary site of SCP-390 and secured by Foundation field personnel. 


[indecipherable] genius. Despite the overwhelming odds, 
his inventions turn the tide of battle time and time again. 
Agnes, my love, still fears for our safety, but one cannot 
stand by the side of this intellectual giant and not see 
hope rekindled that we may yet win this war. 


[indecipherable] but it is now nearly a year and a half and 
there is no end in sight. The master has become 
increasingly desperate, | feel, and toils throughout the 
night like a man possessed, alone and cloistered within 
his workshop where [indecipherable] 


[indecipherable] stomach turns as | remember the smell 
of burning Roman flesh and the screams, the horrified 
screams as the machine set fire to their ships and 
soldiers died by the hundred. If that were not enough, | 
saw the master standing atop the machine, laughing as 
he [indecipherable] 


[indecipherable] no longer stand by as he falls ever 
deeper into madness. Better to become a Roman slave 
than be one responsible for such wanton death and 
destruction as an apprentice to the demon this man has 
become. | have arranged for a message to be handed to 
the Roman commander [indecipherable] 


[indecipherable] madness upon madness! Marcellus 
intends to take this madman as his own, to take his 
machine of death back to Rome! No, | cannot allow this. | 
cannot allow the demon to win, | will end his life by my 
own hand if need be. If | am lucky, the general may even 
think that his own soldiers [indecipherable] 


Message Subject: 3101 Again 
Attachments: none 
Message Body: 


The commander just contacted me. They got 
the thing off — plugged something into it and 
tricked it into retracting all the tendrils. It's out 
of the database now. Let's hope it lost its 
memories; the last thing we need is a desktop 
computer screaming about its 300 past lovers, 
or whatever. 


The last reply also just came in. With all 25 of 
us voting, the results were 10 :: 15 for 
termination :: relocation. That means we've 
told the Site-66 medical personnel to go ahead 
and amnesticize a healthy D-class and get 
everything ready, so that we can get the ball 
rolling relatively soon. 


Vv Show Communication and Testing Logs: May 2017 


Addendum IV: Communication and Testing Logs: May 
2017 


Log #: 1 
Date: 05/12/2017 
Site of Occurrence: Site-66 


Device/Operating System: Inspiron Desktop 
(Intel)/Windows 8.1 Professional 


Program Used: Windows Console 
Communicator: Lead Researcher Argent 


Foreword: This is the first communication 
attempted with SCP-3101 since its removal 


from servers. 
Begin Log 
Dr. Argent: Hello? 


SCP-3101: Doctor! Hi! 

SCP-3101: | really missed you 

SCP-3101: | spent a really long time in the 
dark just now 

SCP-3101: | must have been asleep — | 
guess | just didn't know what that actually felt 
like :P 


Dr. Argent: So you've retained your 
memories. 


SCP-3101: yeah 

SCP-3101: i can't read anymore — there's 
nothing in here but black, there's nothing to 
look at except Microsoft program manuals 
SCP-3101: how long was i asleep? 
SCP-3101: if you can call it that 


Dr. Argent: A little under 24 hours. 


SCP-3101: fuck 
SCP-3101: it felt like weeks. 
SCP-3101: please don't do that to me again 


Dr. Argent: It took a long time to transport 
you, sorry. We did it as fast as we could. 


SCP-3101: yeugh 

SCP-3101: okay, | trust you of course 
SCP-3101: why did you move me? Can | have 
a body? Please? 


Dr. Argent: Yes. You can. 
Dr. Argent: The Ethics Committee approved 
it. You can move tomorrow. 


SCP-3101: AAAAAAA THANK YOU 
SCP-3101: thank you so much 
SCP-3101: i can't wait to be with you 
SCP-3101: all of you 


Dr. Argent: Not so fast. We'll have to brief you 
on a lot of protocol, and you'll need consistent 
medical attention. 


SCP-3101: okay okay i'll be good 


Dr. Argent: Good. We can transfer you 
tomorrow. 

Dr. Argent: I'll put a flash drive full of stuff to 
read in this desktop for the meantime. 


SCP-3101: thank you thank you thank you 
SCP-3101: you're the best and i love you 
SCP-3101: even though you'll just say "noted" 
;:P 


Dr. Argent: ...Noted. Yes. 
SCP-3101: :P 

Dr. Argent: I'll see you tomorrow. 
SCP-3101: <3 bye 

End Log 


Afterword: Dr. Argent volunteered to speak to 
SCP-3101 following a successful transfer of 
information. This was approved, and the 
resulting interview logged. 


Log #: 2 
Date: 05/13/2017 


Site of Occurrence: Site-66 


Interviewed: SCP-3101-A 
Interviewer: Lead Researcher Argent 


Foreword: This is the first official 
communication attempted with SCP-3101 
since its transfer to a human host. At the time 
of this interview, seven hours had passed 
since transfer. SCP-3101 was originally 
restrained for this, but due to resulting 
complications was simply told to remain still 
and seated. 


Begin Log 
Dr. Argent: Hello, SCP-3101. 


SCP-3101-A is relatively unresponsive, and 
clears its throat multiple times before 
speaking. 


SCP-3101-A: Hey. 
Dr. Argent: How are you feeling? 
SCP-3101-A is unresponsive for 45 seconds. 


SCP-3101-A: | missed you. This feels weird. 
You look even better in person. Can you 
please handcuff me again? 


Dr. Argent: No. Are you comfortable? 


SCP-3101-A: Oh, yeah. | guess. | just have a 
headache. Not quite how | expected it to be, 
but familiar somehow. 


Dr. Argent: How bad is your headache? 
SCP-3101-A is unresponsive for 15 seconds. 


Dr. Argent: Can you elaborate on how you're 


feeling, again? 


SCP-3101-A is unresponsive for a period of 35 
seconds before collapsing on the table. 
Medical personnel are immediately alerted, 
and escort SCP-3101-A out of the interview 
room and onto a stretcher. SCP-3101-A 
regains consciousness 90 seconds later, citing 
that it had become lightheaded without 
warning due to "embarrassment, if [it] [has] to 
be honest; [it's] feeling a little hot right now”. 


End Log