All works that have been uploaded as an article to the Authority website are located here.
The J 2020 event RPC can be found here here.
Terminal theme used for the 2020 Operations article: http://rpcsandbox.wikidot.com/terminal-theme-jokah
Cosmic Embers articles here: http://rpcsandbox.wikidot.com/jokahcosmicember
TODO: Write a Cosmic Embers AU article. Maybe.
NEVER write FF. It was an awful idea.
Links for shit i'll probably need:
manual hazard guide
RPC-XXX
|
0 |
0 |
| Registered Phenomena Code: XXX Containment Rating: Alpha Lethality Rating: Yellow |
|
Containment Protocols: RPC-XXX is currently contained on a server blade within Google's cloud computing database, identifier [REDACTED] at OL-Site [REDACTED]. Co-operation with Google via an affiliate data protection group has been secured and have been made vaguely aware of the threat of the file on an affiliate basis. Protection personnel have been inserted in security, maintenance and technology-relevant roles with and without their approval and oversight. Authority reach currently extends to server block management and administration.
RPC-XXX is to be locked within an archive secured using AES-256 encryption - the password is to be held by two Level 3P or 3R staff members and updates to the password must be relayed to the other staff and relevant Head Researcher. If the password is to be distributed to lower level staff members, this must be granted on a short-term affiliate basis regardless of the reason. Any personnel who will be accessing RPC-XXX for any reason must submit to Class P-1 amnestics prior to use.
Digital access to the file outside of the archive is to be remotely monitored by Authority administration staff via an onsite provided personal computer that is disconnected from any network. The provided PC will have no connections for Wifi, Bluetooth or arbitrary wavelength communication platforms of any kind. This also includes wired broadband or dialup connections. Attempts to modify the PC to enable any external transmission will result in removal of the staff member from RPC-XXX handling, immediate Class A-1 or P-2 amnestics administration as relevant and permanent reduction in clearance level. Reduction of clearance level to Level 0 will result in the offending staff member being immediately adminstered Class P-2 amnestics if relevant, A-2 amnestics instead if the Class P amnestics do not cover up to 20 hours and being reclassified as CSD personnel.
Physical access to the server blade itself should be limited within reason and observed on a 24/7 basis. If the server blade is removed without permission from a Level 4 or higher staff member, staff are to refer to Protocol Hagedorn-Trojan-XXX. The server blade itself is infected with a virus that, on failure to load in the assigned server chassis and slot, will proceed to corrupt every partition of the server blade's long term storage before attempting to wipe the server blade via overloading [REDACTED], magnetically disabling the hard disk memory and subsequently rendering device recovery impossible. It will then trigger a separate program to attempt to ping specific IP addresses using multiple OS-level services in order to making tracking the offender for incarceration and applying amnestics easier before self deleting.
If RPC-XXX is wiped from the server blade mentioned above in any capacity, Protocol Guilty-Trojan-XXX is to be active and this RPC is to be reclassified as Beta-Yellow until RPC-XXX is relocated. RPC-XXX's priority for remanifesting is in following priority:
- Any device closest to Mountain Yudono or the original site that held RPC-XXX-A.
- Any device located North, then East, then South, then West of the above.
- Any device with sufficient space to store a minimum of [REDACTED] terrabytes of data.
Description: [Paragraphs explaining the description]
Addendum: and/or Discovery: [Optional additional paragraphs]