Editing Exo

From Destinypedia, the Destiny wiki

You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 33: Line 33:
The Exos were designed and built during humanity's Golden Age by the [[Clovis Bray (corporation)|Clovis Bray corporation]]. The original intent of the project was to develop a durable, synthetic housing for an uploaded human consciousness (an "exomind"), which would effectively render humans immortal.<ref>'''[[Mysterious Logbook]]''', "ENTRY 2", ''[[Mysterious_Logbook#-07-|-07-]]''</ref> However, early exominds inevitably fell victim to a degenerative process termed the "loop/billboard/crash" cycle, characterized by cognitive and motor stereotypy (abnormal, repetitive behaviors), athetosis (slow, involuntary writhing movements of the limbs and extremities), and gradual loss of sapience. While degenerating exominds would still pass the Turing test for a time, they were [https://en.wikipedia.org/wiki/Philosophical_zombie philosophical zombies], and would ultimately enter a state analogous to brain death. This problem eventually claimed the life of [[Clovis Bray II]], after he was uploaded into an exomind format. Crashed exominds could be restored from backup, but the process termed "billboarding" would simply begin again.<ref>'''[[Mysterious Logbook]]''', "NOTE—WHY EXOMINDS FAIL", ''[[Mysterious_Logbook#-020-|-020-]]''</ref>
The Exos were designed and built during humanity's Golden Age by the [[Clovis Bray (corporation)|Clovis Bray corporation]]. The original intent of the project was to develop a durable, synthetic housing for an uploaded human consciousness (an "exomind"), which would effectively render humans immortal.<ref>'''[[Mysterious Logbook]]''', "ENTRY 2", ''[[Mysterious_Logbook#-07-|-07-]]''</ref> However, early exominds inevitably fell victim to a degenerative process termed the "loop/billboard/crash" cycle, characterized by cognitive and motor stereotypy (abnormal, repetitive behaviors), athetosis (slow, involuntary writhing movements of the limbs and extremities), and gradual loss of sapience. While degenerating exominds would still pass the Turing test for a time, they were [https://en.wikipedia.org/wiki/Philosophical_zombie philosophical zombies], and would ultimately enter a state analogous to brain death. This problem eventually claimed the life of [[Clovis Bray II]], after he was uploaded into an exomind format. Crashed exominds could be restored from backup, but the process termed "billboarding" would simply begin again.<ref>'''[[Mysterious Logbook]]''', "NOTE—WHY EXOMINDS FAIL", ''[[Mysterious_Logbook#-020-|-020-]]''</ref>


Following the discovery of the [[Anomaly (artifact)|K1 artifact]] and the paracausal force [[Clovis Bray I]] called "[[Darkness|Clarity]]", Clovis I mounted an expedition to [[Europa]] to find the secret of immortality promised to him by "Clarity". There, under the instructions of a mysterious entity he called "[[Clarity Control]]", Clovis I stole a [[Vex]] from the [[Ishtar Collective]] and used it to build a gate to a Vex megastructure, the [[Forge Star]].<ref>'''[[Mysterious Logbook]]''', "ENTRY 6 AMENDMENT", ''[[Mysterious_Logbook#-029-|-029-]]''</ref><ref>'''[[Mysterious Logbook]]''', "ENTRY 7", ''[[Mysterious_Logbook#ENTRY 7|ENTRY 7]]''</ref> Upon studying samples of Vex [[radiolaria|radiolarian fluid]] recovered from the Forge Star and observing its synergy with "Clarity", Clovis I discovered that introducing "Clarity"-altered radiolarian fluid, deemed "[[Alkahest]]", to an exomind's hardware miraculously solved the "loop/billboard/crash" problem.<ref>'''[[Mysterious Logbook]]''', "ENTRY 8", ''[[Mysterious_Logbook#-40-|-40-]]''</ref> However, even this solution was not permanent, as the new generation of Exos fell victim to Dissociative Exomind Rejection.<ref>'''[[Mysterious Logbook]]''', "NOTE—D.E.R.", ''[[Mysterious_Logbook#-45-|-45-]]''</ref>
Following the discovery of the [[Anomaly (artifact)|K1 artifact]] and the paracausal force [[Clovis Bray I]] called "[[Darkness|Clarity]]", Clovis I mounted an expedition to [[Europa]] to find the secret of immortality promised to him by "Clarity". There, under the instructions of a mysterious entity he called "[[Clarity Control]]", Clovis I stole a [[Vex]] from the [[Ishtar Collective]] and used it to build a gate to a distant star system. Upon studying samples of Vex [[radiolaria|radiolarian fluid]] and observing its synergy with "Clarity", Clovis I discovered that introducing "Clarity"-altered radiolarian fluid, deemed "[[Alkahest]]", to an exomind's hardware miraculously solved the "loop/billboard/crash" problem.<ref>'''[[Mysterious Logbook]]''', "ENTRY 8", ''[[Mysterious_Logbook#-40-|-40-]]''</ref> However, even this solution was not permanent, as the new generation of Exos fell victim to Dissociative Exomind Rejection.<ref>'''[[Mysterious Logbook]]''', "NOTE—D.E.R.", ''[[Mysterious_Logbook#-45-|-45-]]''</ref>


Clovis I discovered that DER could be staved off by two methods. The first was the "reboot", which involved wiping the mind's memories post-transfer so that it would not remember its old body, and so better accept the new one. Despite the term "reboot", also referred to as "resets" or "memory wipes", the process did not actually remove memories, and only blocked off associative access to them. This was done because memory engrams were stored in many areas of the brain, causing them to be difficult to locate and delete.<ref name = "e10">'''[[Mysterious Logbook]]''', "ENTRY 10", ''[[Mysterious_Logbook#ENTRY 10|ENTRY 10]]''</ref> While effective, it was not a cure, and the reboot procedure would often be repeated several times over the Exo's life. It would also be used for functional purposes, such as restoring Exos whose minds had become "compromised," such as by Vex infection.<ref>'''[[Mysterious Logbook]]''', "ENTRY 11", ''[[Mysterious_Logbook#ENTRY 11|ENTRY 11]]''</ref> Successive reboots cumulatively eroded an Exo's mind and their ability to retain any memories at all, with excessive numbers of reboots causing insanity.<ref name="SoWLegacyPt2">'''Bungie (2020/3/10)''', ''[[Destiny 2]]: [[Season of the Worthy]], Playstation 4, Activision Blizzard, [[Weblore]]: [[Weblore#Legacy_Pt_2|Legacy Pt 2]]''</ref> The Clovis Bray corporation estimated that the maximum number of times an Exo could be safely rebooted was around 20.<ref name="Ghost Scan: Core Terminus, Mars"/> As reboots did not technically remove any memories, Exos sometimes remembered traces of them. This was especially the case for Guardians, and some could gain access to these buried memories by purposefully dying. By default, Exos had a number appended to their names that signified the number of reboots they had experienced, with the original human used as the zero-index. This was inspired by the number scheme used by AI trainers to denote successive iterations of an AI, such as with [[Aivanti-3]]. Hence, to use Clovis I's example, the human Mohammed would be followed by the Exo Mohammed-1, Mohammed-2 after one reset, etc. This number was stored in the Exo's memory as hardware, and so could not be forgotten.<ref>'''[[Mysterious Logbook]]''', "ENTRY 13", ''[[Mysterious_Logbook#ENTRY 13|ENTRY 13]]''</ref>
Clovis I discovered that DER could be staved off by two methods. The first was the "reboot", which involved wiping the mind's memories post-transfer so that it would not remember its old body, and so better accept the new one. Despite the term "reboot", also referred to as "resets" or "memory wipes", the process did not actually remove memories, and only blocked off associative access to them. This was done because memory engrams were stored in many areas of the brain, causing them to be difficult to locate and delete.<ref name = "e10">'''[[Mysterious Logbook]]''', "ENTRY 10", ''[[Mysterious_Logbook#ENTRY 10|ENTRY 10]]''</ref> While effective, it was not a cure, and the reboot procedure would often be repeated several times over the Exo's life. It would also be used for functional purposes, such as restoring Exos whose minds had become "compromised," such as by Vex infection.<ref>'''[[Mysterious Logbook]]''', "ENTRY 11", ''[[Mysterious_Logbook#ENTRY 11|ENTRY 11]]''</ref> Successive reboots cumulatively eroded an Exo's mind and their ability to retain any memories at all, with excessive numbers of reboots causing insanity.<ref name="SoWLegacyPt2">'''Bungie (2020/3/10)''', ''[[Destiny 2]]: [[Season of the Worthy]], Playstation 4, Activision Blizzard, [[Weblore]]: [[Weblore#Legacy_Pt_2|Legacy Pt 2]]''</ref> The Clovis Bray corporation estimated that the maximum number of times an Exo could be safely rebooted was around 20.<ref name="Ghost Scan: Core Terminus, Mars"/> As reboots did not technically remove any memories, Exos sometimes remembered traces of them. This was especially the case for Guardians, and some could gain access to these buried memories by purposefully dying. By default, Exos had a number appended to their names that signified the number of reboots they had experienced, with the original human used as the zero-index. This was inspired by the number scheme used by AI trainers to denote successive iterations of an AI, such as with [[Aivanti-3]]. Hence, to use Clovis I's example, the human Mohammed would be followed by the Exo Mohammed-1, Mohammed-2 after one reset, etc. This number was stored in the Exo's memory as hardware, and so could not be forgotten.<ref>'''[[Mysterious Logbook]]''', "ENTRY 13", ''[[Mysterious_Logbook#ENTRY 13|ENTRY 13]]''</ref>

Please note that all contributions to Destinypedia are considered to be released under the Attribution-ShareAlike 3.0 Unported license (see Destinypedia:Copyrights for details). If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)

To view or search uploaded images go to the list of images. Uploads and deletions are also logged in the upload log. For help including images on a page see Help:Images. For a sound file, use this code: [[Media:File.ogg]].

Do not copy text from other websites without permission. It will be deleted.