Standard Galactic Alphabet

A guide to SCP-XXXX.

Item #: SCP-XXXX

Object Class: Keter Thaumiel

Special Containment Procedures: All personnel assigned to SCP-XXXX must be completely fluent in its cipher. All instances of SCP-XXXX characters in digital media are to be flagged by Foundation webcrawlers, and then conceptually localized by an automated system1.

Description: SCP-XXXX refers to the Standard Galactic Alphabet, a simple substitution cypher originating from the Commander Keen video game series. SCP-XXXX consists of twenty-six characters, each of which is a substitute to an individual letter in the Latin alphabet2.

SCP-XXXX is an association-based infectious digital cipher, meaning that it will infect any text directly associated with it, as long as said text is within a digital medium. This primarily refers to text that is narratively linked to other SCP-XXXX characters. For instance, including a word written in SCP-XXXX in a computer document may begin to infect other words on the same paragraph, but will not be able to infect distant pages until it has spread a sufficient "distance" and infected pages in between them. Unusually, SCP-XXXX is unable to infect Latin characters if they are directly being used as translation references, such as those shown in the image above.

SCP-XXXX can also infect text referring to itself; however, the referential level required in order to infect said text must include some reference to its anomalous properties. Documentation simply referring to SCP-XXXX without any acknowledgement of its anomalous properties will not be affected in this manner.

SCP-XXXX is conceptually dependent to some degree, meaning that it is rendered non-anomalous with sufficient alterations to the style of its characters. The alterations required to render SCP-XXXX characters ineffective are relatively minor. For instance, the capital letter "J" in any script can be considered almost identical to the SCP-XXXX character for the letter "o" (see SCP-XXXX guide above), especially to individuals unfamiliar with SCP-XXXX, but subtle distinguishing factors mean that almost any styling of the letter "J" does not carry the properties of SCP-XXXX.

Discovery: SCP-XXXX was created in 1994 with the release of Commander Keen in the Invasion of the Vorticons, although it only included 15 characters3. Future games contained more characters, and the third installment of the series, Commander Keen in Goodbye, Galaxy contained a complete translation guide for translations from Latin characters to SCP-XXXX characters.

It is believed that SCP-XXXX's anomalous properties initially manifested at this point, although due to the narrative localization of SCP-XXXX characters4, it was mostly unable to manifest beyond the game itself.

SCP-XXXX's anomalous properties were first made known to the Foundation following internet references to the cipher infecting various system links and references on online forums, as a result of individuals utilizing the cipher within said forums. Forums with SCP-XXXX were subsequently deleted and witnesses were sent various antimemetic image agents, until stable containment procedures could be enacted.

Addendum XXXX.1: Following a cyber-attack by GoI-5018 ("Broken Rose"), various integral Foundation systems were compromised by SCP-XXXX, resulting in widespread conversion of documentation into the SCP-XXXX cipher. Protocol Cardstock5 was enacted, and infected systems were replaced. Infected systems were moved to a physical server, which is kept in Outpost 09 for research. SCP documentation and other sensitive files were purged from the servers, with the exception of some low-level SCP documents, for further experimentation.

Addendum XXXX.2: Outpost 09 ceased contact for unknown reasons on March 12th, 2012. Unit 3 of MTF Chi-64 ("Diamond Sword") was sent to investigate, but did not return. Further searches into Outpost 09 have yielded similar results. Exploration into Outpost 09 has been halted for the foreseeable future.

Research into SCP-XXXX's contribution to these events, and additional properties they may have, is ongoing.

Addendum XXXX.3: On March 23rd, 2012, the following transmissions were broadcasted from Outpost 09:

These transmissions were intercepted. No new transmissions have appeared since.

Addendum XXXX.4: On January 9th, 2018, SCP-████ breached containment. Foundation agents pursued the object for several miles before almost reaching it. However, before personnel could apprehend the object, a small squad of armored vehicles intercepted SCP-████, and attempted to capture it. The vehicles were adorned with the SCP Foundation logo, and individuals present were wearing Foundation-issued uniforms. Additionally, many of the individuals wore badges identifying them as members of MTF Chi-64. A brief firefight ensued between Foundation personnel and the other group, but SCP-████ was lost to them.

The vehicles were tracked to Outpost 09, where SCP-████ was taken in. Reports of the incident and research on events involving concluded the following regarding Outpost 09 personnel (henceforth designated SCP-XXXX-1, due to Outpost 09's likely relationship with SCP-XXXX):

  • SCP-XXXX-1 spoke in an unknown language.
  • Despite the fact that SCP-XXXX-1 consisted of former Foundation personnel, SCP-XXXX-1 did not enact proper protocol during the incident.
  • SCP-████'s documentation was one of the few provided to Outpost 09 for research purposes.
    • _

    The following report was sent to O5 Command by SCP-XXXX's research director:

    SCP-XXXX represents an unusual threat to normalcy. While research into its effects is still in its preliminary stage, we have concluded that SCP-XXXX possesses some kind of mind-affecting property. This property is linked to the amount of consistent exposure to SCP-XXXX, which is why it hasn't been detected before. Few to no people have ever spent consistent and extended lengths of time studying or interacting with SCP-XXXX as those within Outpost 09.

    The current hypothesis is that personnel within Outpost 09 were linguistically infected by SCP-XXXX. The full extent of this infection has not been determined, but it seems to have altered the memories of Outpost 09 personnel. How SCP-XXXX was then able to affect MTF Chi-64 so quickly is unknown, but may be a result of it having already affected other individuals, meaning that SCP-XXXX likely spreads in this manner at an exponential rate.

    It should be noted that they were successfully able to contain SCP-████. Apparently, the linguistic identification with SCP-XXXX meant that the initial documentation was somehow incorporated into SCP-XXXX-1. They were confused, judging from their initial transmissions, but they were familiar enough with SCP-████ to be able to contain it, and so that's what they did.

    Fortunately, this newfound discovery related to SCP-XXXX requires extenuating circumstances to occur, mostly only accessible by long-term research into its properties. Current containment procedures should be enough to prevent this from occurring in a civilian population. However, the question remains of how to deal with SCP-XXXX-1. Incursions into Outpost 09 have completely failed, due to SCP-XXXX's effects, and apprehension outside of Outpost 09 may be risky for similar reasons.

    As such, I am proposing a rather unorthodox procedure regarding SCP-XXXX-1. It is perfectly capable of detaining SCP objects, but likely only chose to act during the isolated situation, because SCP-XXXX was linked to that particular anomaly. SCP-XXXX-1 likely did not enact proper Foundation protocol for similar reasons, as it had no reference for how to operate. However, if provided direction and instructions using SCP-XXXX, they may incorporate that into its operations. Foundation protocol and directives could be applied to them simply by relaying it to them in their own language.

    In short, I propose that the SCP Foundation allow SCP-XXXX-1 to continue their operations, but that we use SCP-XXXX to make SCP-XXXX-1's methods and goals align with our own, by submitting Foundation procedures and protocols to them in SCP-XXXX.

    The O5 Council voted on the proposal, and chose to enact a modified version on a 6-5-2 vote. SCP-XXXX-1 would be provided with directives and then closely monitored for several years, in order to analyze their response and behavior. If any deviations occur, the project will be terminated.

    A message was transmitted to them, submitting directives on the mission statement and operations of SCP-XXXX-1. A preview of the message can be seen below.

    ╎ℸ ̣ ᒷᒲ #: ᓭᓵ!¡-ᓭ⊣ᔑ-001

    𝙹ʖ⋮ᒷᓵℸ ̣ ᓵꖎᔑᓭᓭ: !¡∷╎ᒲᒷ ↸╎∷ᒷᓵℸ ̣ ╎⍊ᒷ

    ᓭ!¡ᒷᓵ╎ᔑꖎ ᓵ𝙹リℸ ̣ ᔑ╎リᒲᒷリℸ ̣ !¡∷𝙹ᓵᒷ↸⚍∷ᒷᓭ: ᓭᓵ!¡-ᓭ⊣ᔑ-001 ᒲ⚍ᓭℸ ̣ ʖᒷ 𝙹ʖᒷ||ᒷ↸ ᔑℸ ̣ ᔑꖎꖎ ᓵ𝙹ᓭℸ ̣ ᓭ.

    ↸ᒷᓭᓵ∷╎!¡ℸ ̣ ╎𝙹リ:


    ||𝙹⚍ ᔑ∷ᒷ ℸ ̣ ⍑ᒷ ᓭᓵ!¡ ⎓𝙹⚍リ↸ᔑℸ ̣ ╎𝙹リ. ||𝙹⚍ ᔑ∷ᒷ ᔑリ 𝙹∷⊣ᔑリ╎⨅ᔑℸ ̣ ╎𝙹リ ℸ ̣ ᔑᓭꖌᒷ↸ ∴╎ℸ ̣ ⍑ ℸ ̣ ⍑ᒷ ᓵ𝙹リℸ ̣ ᔑ╎リᒲᒷリℸ ̣ ᔑリ↸ ᓵ𝙹リᓵᒷᔑꖎᒲᒷリℸ ̣ 𝙹⎓ ℸ ̣ ⍑ᒷ ᔑリ𝙹ᒲᔑꖎ𝙹⚍ᓭ ⎓∷𝙹ᒲ ℸ ̣ ⍑ᒷ !¡⚍ʖꖎ╎ᓵ ᒷ||ᒷ.

    ᔑリ𝙹ᒲᔑꖎ𝙹⚍ᓭ 𝙹ʖ⋮ᒷᓵℸ ̣ ᓭ, 𝙹∷ ᓭᓵ!¡ᓭ, ᒲ⚍ᓭℸ ̣ ʖᒷ ⊣╎⍊ᒷリ ᓭ!¡ᒷᓵ╎ᔑꖎ ᓵ𝙹リℸ ̣ ᔑ╎リᒲᒷリℸ ̣ !¡∷𝙹ᓵᒷ↸⚍∷ᒷᓭ, ╎リ 𝙹∷↸ᒷ∷ ℸ ̣ 𝙹 !¡∷𝙹!¡ᒷ∷ꖎ|| ᓵ𝙹リℸ ̣ ᔑ╎リ ℸ ̣ ⍑ᒷᒲ. ╎ℸ ̣ ╎ᓭ ||𝙹⚍∷ ↸⚍ℸ ̣ || ℸ ̣ 𝙹 ᓭᒷ!¡ᔑ∷ᔑℸ ̣ ᒷ ℸ ̣ ⍑ᒷ ∴𝙹∷ꖎ↸ 𝙹⎓ ℸ ̣ ⍑ᒷ ᔑリ𝙹ᒲᔑꖎ𝙹⚍ᓭ ⎓∷𝙹ᒲ ℸ ̣ ⍑ᒷ ∴𝙹∷ꖎ↸ 𝙹⎓ ℸ ̣ ⍑ᒷ ᒲ⚍リ↸ᔑリᒷ.

    ||𝙹⚍ ᓭᒷᓵ⚍∷ᒷ, ||𝙹⚍ ᓵ𝙹リℸ ̣ ᔑ╎リ, ||𝙹⚍ !¡∷𝙹ℸ ̣ ᒷᓵℸ ̣.

    Addendum XXXX.5: Three years after the aforementioned project was enacted, SCP-XXXX-1 has shown no signs of deviation from Foundation directives, and has been considered a success. SCP-XXXX-1 has attained complete self-sufficiency, even developing a rudimentary database and successfully containing previously unknown anomalous objects. SCP-XXXX has been reclassified as Thaumiel.

      • _

      Searching database…

      Match found.

      Item #: SCP-001

      Object Class: Prime Directive

      Special Containment Procedures: SCP-001 must be obeyed at all costs.



      You are the SCP Foundation. You are an organization tasked with the containment and concealment of the anomalous from the public eye.

      Anomalous objects, or SCPs, must be given special containment procedures, in order to properly contain them. It is your duty to separate the world of the anomalous from the world of the mundane.

      You secure, you contain, you protect.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License