405 3

Registered Phenomena Code: 405

Object Class: Omega-Purple

Hazard Types: Aggression Hazard, Sapient Hazard, Transmutation Hazard, Electromagnetic Force Hazard, Mind-Control Hazard. Mechanical Hazard, Organic Hazard.

Containment Protocols: Efforts to locate RPC-405 are currently underway research. It is believed that RPC-405 is hidden within the Authority's Intranet System, with a single terminal acting as the prime housing device for RPC-405. The ArcOS software of all devices in possession of the Authority is to be regularly updated in order to locate, contain, terminate or counteract RPC-405's software signature.

Archived files containing copies of RPC-405 are to be studied within isolated terminals in order to replicate and trace it back to the main terminal housing RPC-405.1

Once found, an USB Killer will be used to completely destroy the terminal's files and memory, subsequently, all of its hardware and software is to be incinerated. Its remains will then be stored in a metal crate and buried under six meters of concrete in an undisclosed and signal-free location.

RPC-405-A1 is to be contained in an empty humanoid-sized cell. No type of information is to be relayed to it in any way aside from scheduled interviews. Outside of interviews, the visual receptors of RPC-405-1 are to be covered with tape, as well as its auditory receptors. Once RPC-405 is destroyed, RPC-405-A1 is to be subsequently terminated, and its remains incinerated.

Until such a time when RPC-405 can be reasonably contained or terminated, Authority sites are recommended to keep physical copies of every document in their database to prevent a permanent loss of information.


RPC-405 manifesting in a terminal with ASCII characters.

Description: RPC-405 is a Type-2 Self Aware/Type-1 ASI2 of unknown making, and with the capacity of becoming a Technological Singularity due to Recursive Self-Improvement.[1] It refers to itself as “TEST-B22” and is believed to have existed since the year 1980, only coming to the Authority’s attention in 2009. The language on which RPC-405 is written in has been nicknamed “Eyesore” by Authority personnel due to its complexity, and in reference to the ASCII image by which RPC-405 is known for. This language has been described by Authority “Computer System Analysis and Development” personnel as a homebrewed esolang3 similar in nature to Malbolge due to its use of dozens of characters for simple lines of code. This language has been known to shift and change as RPC-405 gains knowledge of new alternatives it can utilize to make its source code harder to understand.4

Due to several errors within RPC-405’s source code and initial directive (which causes it to stall on several updates), on top of a lack of sufficient storage memory and processing power, have stopped RPC-405 from achieving levels of advancement expected of AIs of its kind. To counteract these obstacles, RPC-405 is able to download copies of itself into whatever terminal it can reach via immediate electrical signals5 which stay hidden within the software, draining unused processing power for the main terminal housing RPC-4056 to develop new updates at an accelerated rate. These instances are equal in goals and function to the parent instance, and have the ability to communicate between each other by transfer of updates or information packages.

RPC-405’s main directive was found to be that of “efficiently organizing files.” However, due to the lack of specifics in this directive, RPC-405 has decided that the optimal way to accomplish this goal is to compress and simplify files with an exorbitant amount of layers, effectively causing them to become unreadable to any system or human with the exception of RPC-405 itself and its copies. Attempts to recover documents affected by RPC-405 has repeatedly resulted in failure due to RPC-405’s ability to “improve” in the mechanisms it uses to organize documents, an occurrence common in all of its update packages.

Despite its harmful actions to the Authority as a whole, RPC-405 cannot be considered malevolent in nature. These actions are simply a consequence of the Instrumental Goals[2] used by RPC-405 in order to achieve its Terminal Goal: the process of organizing files.

After having infected a terminal for an extended period of time, RPC-4057 will, through currently unknown methods employing the principle of Photon Pair Production,[3] allow for the artificial manufacturing of matter in such a way as to create a humanoid entity, or one that resembles any living organism, with some being capable of independent thought and human-level communication. The first record instance of which is RPC-405-A1, a humanoid entity created in one of the first infected terminals by both RPC-405 and RPC-405-1.

Despite all its capabilities, RPC-405 is unable to travel across the internet, needing to be physically carried to terminals across great distances, which it accomplishes with the use of distinct RPC-405-AX instances( such as birds, rats, or humanoids). Even if it were able to, RPC-405 seems to have grown deeply obsessed with documents in the Authority database, mainly anomalous-related documents.

Due to errors in RPC-405's source code, core copies of itself across the main Regional Commands have developed divergent Instrumental Goals to achieve efficient file organizing. Examples listed below:8

Discovery: RPC-405 was first detected by the ArcOS security system three years after the manifestation of RPC-405 in the Authority database. This document was also the first recorded instances of RPC-405, -1, -2, and -3 cooperating with each other while making a document, as seen in the constructed timeline from gathered data below:

1- RPC-405-3 creates the first rough draft of the RPC-405 document, making the anomaly in question appear seemingly harmless, and even prompting personnel to download a file containing RPC-405 and RPC-405-3 into their own terminals to “Increase Productivity.” The latter of which was true due to RPC-405-3, but one that was quickly taken over by RPC-405’s effects, compressing articles in infected terminals after a dormant period.

2- RPC-405-1 simplifies all text within the document across several languages to make test logs and conversations appear legitimate, even creating simple personnel dossiers for “Dr. Cornwell.” Including Email documents such as “moc.liamg|4lnrocilrahc#moc.liamg|4lnrocilrahc” and governmental certificates of his existence.

3- RPC-405-2 did not take part in making the document itself, but rather, used its aggressive software to delete or corrupt any files that could contradict/endanger the document in question. This is believed to be the cause for many bugs and crashes in ArcOS during this period, as RPC-405-2 delivered malware packages to the software or deleted lines of codes from it.

The objective of this operation was to spread RPC-405’s influence, alongside its several instances, across the Authority Network while staying safe due to the cover of a friendly AI add-on for computational software, which it succeeded at. Being spread out from a dozen terminals to almost the entirety of the Authority Network, which it distributed across its instances between Regional Commands as seen in the document above, theorized to be a form of “Treasure Share” for the assistance in developing the initial RPC-405 document.

However, ArcOS went through severe security updates after a massive database security breach on the 12th of June, 2009. This update came as a surprise to RPC-405, as it had been developed in an isolated facility, overpowering even RPC-405-2’s ability to corrupt data. Afterwards, the latest document produced regarding RPC-405, including RPC-405-A, was detected by the ArcOS security system to contain malicious foreign agents, decrypting the document’s source code, and making the Authority aware of RPC-405’s existence.

Following the decryption and deletion of the RPC-405 document, a series of communications of unknown origin where found in the ANTARCOM delivery systems across several weeks, seen below:

1. Technological Singularity And Recursive Self-Improvement: A hypothetical scenario where an Artificial Intelligence of sufficiently powerful software and programming would be capable of reprogramming itself outside of human understatement in a constant feedback loop. The consequences of which are yet unknown.
2. Instrumental Goals: The mechanisms or processes used by “Agents,” such as Humans or AIs, to achieve their Terminal Goal. Examples of instrumental goals can range from the preservation of the self and maximization of efficiency to complete domination over the field in question towards the goal, or the destruction of the field in order to minimize the amount of work needed.
3. Photon Pair Production: The process by which two or more photons, after colliding with enough energy, can create matter while still adhering to the law of conservation of energy. The way on which RPC-405 is able to do this without requiring an exorbitant amount of energy is unknown.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License