Following the trail of Gunt, Cockroach discovered a log from terminal WS-243, colloquially known as the Humming Machine. This server was installed in an abandoned office inside the old Sanctum HQ, whose installations were repurposed as top-secret storage.
WS-243 acted for 10 years as an experimental server for what was then known as Project Neverending, an obscure precursor of the Endless Warrior Program.
metadata
code: 3-1479
type: log
filename: gregis-12309.log
creation date: march 12, 2009
modification date: march 12, 2009
data
original text
user: gregis
pass:
$ never scan
Scanning subjects for matching patterns...
Scan completed.
Check logfile to see the results.
$ cat /var/log/never/sub24/24-never-12309.log
_________
_______
______
_______
_________
n e v e r
e n d i n g
p r o j e c t
/\/\/\/\/\/\/\/\
sanctum protects
\/\/\/\/\/\/\/\/
subjects: 24
date: 12/3/2009
preconditions: ok
scan results:
no subjects found
$ never range 200
$ never scan
Scanning subjects for matching patterns...
Scan completed.
Check logfile to see the results.
$ cat /var/log/never/sub24/24-never-12309_2.log
_________
_______
______
_______
_________
n e v e r
e n d i n g
p r o j e c t
/\/\/\/\/\/\/\/\
sanctum protects
\/\/\/\/\/\/\/\/
subjects: 37
date: 12/3/2009
preconditions: ok
scan results:
2 subjects founds
*****
subject #1:
- presence of astarte: positive
- presence of cain: positive
- presence of mara: negative
- presence of loki: negative
- presence of amateratsu: positive
success probability: 25%
*****
subject #2:
- presence of astarte: negative
- presence of cain: positive
- presence of mara: negative
- presence of loki: negative
- presence of amateratsu: negative
success probability: %80
$ never range 500
$ never scan -d
Scanning subjects for matching patterns...
Scan completed.
2 previously scanned subjects discarded.
Check logfile to see the results.
$ cat /var/log/never/sub24/24-never-12309_3.log
_________
_______
______
_______
_________
n e v e r
e n d i n g
p r o j e c t
/\/\/\/\/\/\/\/\
sanctum protects
\/\/\/\/\/\/\/\/
subjects: 152
date: 12/3/2009
preconditions: ok
scan results:
3 subjects founds
2 previously scanned subjects discarded
*****
subject #3:
- presence of astarte: negative
- presence of cain: negavive
- presence of mara: negative
- presence of loki: negative
- presence of amateratsu: positive
success probability: 98%
$ never call -f sub24 3
calling subject #3 from sub24
call SUCCESSFUL
$ echo "subject 3 prepared for extraction \
12/3/2009 \
98% success probability \
NEVER SEEN BEFORE" > sub24-3-success.txt
$ exit
Session closed
user:
code: 0-2203
type: memo
unofficial name: homiletics initiative
date of publication: february 2, 2012
responsible: lore keepers
data
original text
DATE: February 2, 2012
TO: All Sanctum Keepers Personnel
FROM: Gunther R., Leader, Lore Keepers
SUBJECT: Homiletics Initiative
Due to the importance of our role as keepers of Sanctum's knowledge, it's of utmost importance to inform everyone about the so-called Homiletics Initiative.
Since last December, our team has worked in intercepting and deecrypting unauthorized messages inside our organization. Both senders and receivers remain unknown. However, the content of these messages has been fully uncovered.
In what appears to be an attempt to dismantle the Five Pointed Star, a part of our personnel is inserting fabricated data inside our body of knowledge. The affected data has not been identified, but Lore Keepers is working closely with Order Keepers to track the responsible people.
While we ignore the motivation for this attack, what we do know is that what they call the Homiletics Initiative is an inside job.
We require all the five points to collaborate in this matter immediately. His Master has been informed of the perpetrators and their initiative, and has summoned the Sacred Star Council on February 3rd.
Along with 2-4872, there was another plain text file which contained a seemingly work-related message. However, some words were encrypted.
The decoded words revealed a not-so-cryptic message, probably addressed to the same Boston individual, due to the date and owner of the file.
If Gunt is part of Sanctum's personnel, remains to be confirmed.
metadata
code: 2-4873
type: file
filename: pending_tasks
creation date: june 25, 2012
modification date: june 25, 2012
owner: mmorrison
data
original text
Pending tasks
[x] Replace missing assistance kitt (8)
[ ] Take 6 matz to washing room
[ ] Tell fily: 20 degrees is too hot for starting the process
[ ] Prepare the 4 prospects for the xlvii EQ run
decoded text
Pending tasks
[x] Replace missing assistance call (8)
[ ] Take 6 gunt to washing room
[ ] Tell lore: 20 degrees is too hot for starting the process
[ ] Prepare the 4 prospects for the three AM run
A file created by mmorrison was found in terminal WS-02, in the megadrive laboratory, addressed to a certain Boston individual. It's unknown if this person is part of Sanctum's personnel, but the nomenclature does not follow institutional communication protocols, so it's assumed the file pertains to a personal affair.
metadata
code: 2-4872
type: file
filename: .higgs
creation date: june 25, 2012
modification date: june 26, 2012
owner: mmorrison
data
original text
Boston,
This is a desperate plea for you to stop.
Stop this, right now!
I know I'll get excommed soon, so I'll just disappear and leave no trace for them to find me.
After what happened, the keepers will ditch anyone who seems a potential danger to the integrity of Sanctum.
Please, I beg you, don't go any further.
I write this with the hope that you read it before they do, delete it as soon as you can, and come back home, to me.
My past is always one step behind me, so that's something I've learned to live with. Starting back in 2006, the actions in which I incurred were always borderline illegal, borderline being the keyword that has kept me safe.
The June 2012 operation (code-name: in-fest), was my first important job, and one I take pride in because it was all my work, regardless of being unseen until... well, until a few days ago.
I always thought the operation had 0 witnesses, until someone emailed me last night.
Cockroach,
It's nice to finally see the results of your hard work.
I remember staring at my screen in awe back that night, trying to follow your steps as you sneaked in their network, almost unnoticed.
Almost.
Waren
Whoever this is, it's clear they were watching meresearching me since way back.
This terminal log from tramos user session, documents an intrusion into the megadrive process. Cockroach has not found any other evidence that corroborates this event, or the circumstances behind it, but acknowledges its rather alarming nature.
It's assumed the intrusion was controlled, or at the very least, its consequences were mitigated.
metadata
code: 3-2533
type: log
filename: tramos-2052011.log
creation date: may 20, 2012
modification date: may 20, 2012
data
original text
user: tramos
pass:
Login successful.
% su tradmin
pass:
Incorrect credentials.
% su tradmin
pass:
Login successful. Entering admin shell.
$ ls
elfador
ramirez
simba
vadr
vadr_280311
$ mkdir barca
$ cd barca
$ megadrive prep
...
Confirm fluid release into the "alchemy" tagged tank (y/N) y
Releasing fluids. Please wait...
Fluids released.
Sealing tubes...
Tubes sealed.
Discarding tubes...
Tubes discarded.
Fluid preparation successful.
$ megadrive mix
Unknown command: 'mix' (run 'megadrive help' for more information)
$ megadrive help
megadrive v1.5-b2
Maintained by @spopper and @galvin, under supervision of @aturman
Property of sanctum 2011
syntax: megadrive <command> <parameter> (<comp>)
List of available commands:
prep: release the fluids in to the alchemy tank
help: shows this screen
start: start the mixing process
transfer: transfer fluids into the vessel
dry: dry run
List of available parameters:
--vv: void vessel
--tv: test vessel
--av: animal vessel
--hv: homo sapiens vessel
--dv: dead vessel
--fe: force end
--p: panic
$ megadrive start #fuck you steve
Beginning mixing process...
Wait for the process to end, please.
Process ended.
$ megadrive transfer
Fluid transfer initiated.
----------------------------------
VESSEL CODE: BARCA
name: not available
age: 35
residence: not available
priority: 2
risk: 888
----------------------------------
Process:
=10%
===30%
=====50%
========%85
=========%90
PROCESS INTERRUPTED. CONNECTOR UNPLUGGED.
PLEASE PLUG THE CONNECTOR(S) NOW
Press any key to continue...
Process does not need to be restarted.
=========%95
==========%100
Process completed.
You may proceed with disconnecting the plugs.
BE CAREFUL. DAMAGED VESSELS WILL BE REJECTED.
$ donlmñck{p+},
Command not found: donlmñc{p+},
$ ves release.
Disassembling...
Vessel released.
$ ves adm wake
Vessel awakened.
$ ss ves
Shell switched successfully. You are now in vessel mode.
=/ order 63578
=/ order 6789963 -pre 456
=/ close
$ echo "Your vessel is mine now. The game is on." > 13579.log
$ done
Process done. Exiting admin mode.
$ exit
Exiting terminal mode. Operating system shutting down...
Cen-OS 4025@xxxed
Sanctum
The file megadrive_man was extracted during Cockroach's operation in June 2012, along with extensive files and logs related to the project.
metadata
code: 2-4529
type: file
filename: megadrive_man
creation date: april 23, 2011
modification date: april 26, 2011
owner: apearson
data
original text
Megadrive Manual
First plug the wires into the vessel. Any part will work, just make sure the connectors are completely under the skin. Heat will take care of any blood flow, if any.
Start the process by running megadrive prep in the administrator shell. This command will release the fluids from their temporary vessels and store them in the alchemy tagged tank.
Then run megadrive start to begin the mixing of the chemicals. This will not start the megadrive process, only the mixing*.
Finally, run megadrive transfer to start the transfer of the chemical compound into the final vessel. The prompt will show a progress marker after running the command**.
The vessel may start to move during the first five minutes. Although it may seem so, this does not mean the vessel feels anything. The movements are reflexes caused by the interaction with the chemicals Still, be aware of any aggressive motion, as it can cause the wires to unplug.
After the process is done, the vessel will be ready for the next stage of the Megadrive process. Make sure you unplug the wires carefully, so the skin won't receive any unintended damage.
Exit the administrator shell by running done.
Run exit.
*: Change the command to something that reflects the process. It can lead to confusion and has already cost us a few vessels.
**: This is an example of an aptly named command. Get your shit together, Steve.
Document excerpt from the protocol 0-134679, known as Exegesis, sent to all of Sanctum's personnel, including HQ and international branches.
It's unknown if this protocol was published as part of the cover up plan for Cockroach's successful extraction of megadrive project documents.
metadata
code: 0-134679
type: protocol
unofficial name: exegesis
date of publication: 4, 2012
responsible: lore keepers
data
original text
July 4, 2012, 22:55:00
Sanctum Lore Keepers, under commandment of His Master's will, hereby declare:
The body of knowledge comprised by the archive documents, files, and logs is to be treated as absolute secret, starting from the publication of this document on.
To achieve this, all personnel, including officers, assistants, reviewers, and maintainers, must secure the keys to their repositories, both private and internal.
Methods of encryption are available in protocol 0-001356, which is available under Lore Keepers authorization.