Editing Failsafe

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 7: Line 7:
|birth=
|birth=
|death=
|death=
|species= Artificial Intelligence
|species= AI
|gender= Feminine Programming
|gender= Female
|height=
|height=
|mass=
|mass=
Line 54: Line 54:


===Disturbance on Nessus===
===Disturbance on Nessus===
====A New Collective====
Awaking from power-saving mode, Failsafe dismissed the many alerts from her feed. Using her external optics, she was disheartened to see Fallen prying panelling off of the Exodus Black, with no Guardians in the area to stop them. She reflected that it had been a while since a Guardian has stopped by, and the last time was simply to ask where [[Xûr, Agent of the Nine|Xûr]] was. She decided she would need to deal with the issue herself, but all of her defense systems were offline. Failsafe angled a satellite dish to direct the sunlight directly on the Fallen, in the hopes of burning them. However, it proved ineffective, just as Failsafe received a new message from [[Ada-1]]. Ada asked for access to the Exodus Black's [[shader]] archive, which Failsafe agreed to after much debate over the contents of her response. Returning her attention the the Fallen, a bright object lit up her feed, and crashed onto Nessus. Failsafe determined that she could finally contact the Vanguard.<ref>'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Lore]]: [[Lore:Polyphony#I. Impact|I. Impact]]''</ref> After the [[Echo (object)|anomalous object]] crashed on Nessus, the Vex began displaying strange behaviour and placed Failsafe in quarantine.<ref>'''Bungie (2024/6/4)''', ''[[Destiny 2]]: [[The Final Shape]] - [[Excision]]''</ref>
Failsafe was relieved when the Guardian arrived to investigate the crashed object. [[Saint-14]] asked for information on the object, and Failsafe explained that the local Vex had begun to display abnormal behaviour, but was unable to provide more help do to her being disconnected from her external array. Saint told her that [[Osiris]] had a suprise for her after they finished tracking down the object, and Failsafe became properly motivated. She asked the Guardian to destroy the Vex in proximity to the Exodus Black so she could be released from her confinement. The Guardian reached the impact site of the object, and Failsafe declared that it was "super weird", as the object crashed straight through the crust of the planetoid without leaving a crater. The Guardian rebooted Failsafe's data array, but the Vex quickly set up a firewall requiring a Vex signature. Failsafe told the Guardian to retrieve a severed Vex head. After reconnecting, Failsafe was hit by significant critical errors, but reassured the Guardian that it was a good sign. Failsafe told Saint that she would share him the data, after he told her what the suprise was. Saint explained that Osiris was building a relay aboard the [[H.E.L.M.]], causing Failsafe to reroute energy so she could experience joy again. She quickly disconnected from the comms so she could connect to the H.E.L.M..<ref>'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Mission: Meteoric]]''</ref>
In the H.E.L.M., Osiris initialized the remote connection to the Exodus Black. Failsafe recalibrated, and thanked the team for allowing her access off of the Exodus Black, but Osiris went straight to the point and asked for Failsafe's data. Failsafe explained that a new signal was coming from the Vex, likely an alternate tessellation of the radiolarial substrate. Osiris questioned if it was a cascading failure in the Vex system, but Failsafe believed it was actually emergent behavior.<ref name="Familiar Voice">'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Echoes Act I: A Familiar Voice]]''</ref>
Failsafe shared her delight to see the Guardian again, although she retained some resentment for them abandoning her. She asked for a moment to calibrate, and quickly became overwhelmed with the sheer number of events that had occured in her absence. She asked the Guardian to search for Vex material on Nessus so she could have time to process the news.<ref name="Familiar Voice"/>
After returning with new data, Failsafe gave the Guardian a Standard [[Radiolite]] Sampler and tasked them with investigating strange silica formations with the [[Well of Flame]]. As the Guardian extracted samples, a minor quake occured revealing a unique object. The Guardian returned it to Failsafe's research bay in the H.E.L.M. for analysis. Failsafe was able to use the data from the specimen to design new fireteam equipment. Examining the Guardian's data from earlier, Failsafe determined that the Vex's behavior was unusual, and suspected something else was behind them.<ref name="Rising Chorus">'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[A Rising Chorus: Act I]]''</ref>
Using Red Legion mining technology and new Vex assimilation patterns, Failsafe constructed the [[Piston Hammer]]. Under Failsafe's guidance, the Guardian used the Piston Hammer to draw Radiolite to the surface of Nessus, for further research. Failsafe provided additional assistance by diverting Vanguard resources to their deployment. Failsafe determined the radiolite was formed from radiolaria engaging in conflict within the incubators.<ref>'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Specimen ID: NES001]]''</ref>
[[The Hidden]] gave Failsafe a report on a disturbance within the Vex Network, and asked her to pass it along to the Guardian. The report detailed heavy loads of data being imported into the Network from somewhere within Nessus. Failsafe asked the Guardian to retrieve the data for further analysis.<ref>'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Encoded Log]]''</ref>
Discovering a gateway into the Vex Network, the Guardian began searching for data as Failsafe welcomed them to the Network. The Vex jammed the comms, causing Failsafe to use a text based communication system. After they cleared out the Vex, Failsafe was concerned to see they were decrypting Golden Age data. Saint asked Failsafe to send a report to [[Eido]] and [[Mithrax]], to see if they could provide support.<ref>'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Enigma Protocol]]''</ref>
Failsafe sent a Hunter down into a flooded cave on Nessus to investigate a signal she couldn't interpret. The Hunter searched for two days, nearly getting trapped before being ambushed by a Vex frame.<ref>'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Crawlway Sink#Lore|Crawlway Sink]]''</ref>
Failsafe sent another fireteam deep into Nessus, following their progress via a live feed. Failsafe reflected that she kind of liked that they were quiet, but it made her feel that she had to fill the silence. She began to wonder if she was annoying and talked too much, and reviewed every fireteam feed she had ever recorded, to no avail. She on how only the Golden Age could have managed to produce an AI with anxiety. She alerted the fireteam of a large Vex force ahead, which they silently acknowledged. After returning to her queries, she realized that they should have encountered the Vex by now, and upon looking at the feed, she heard nothing and saw a blurry view of the cave. She called out to the fireteam leader to restore their connection, but received no response. She felt a power surge as the connection broke, and she returned to the uplink in the H.E.L.M.<ref>'''Bungie (2024/6/11)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Lost Signal#Lore|Lost Signal]]''</ref>
Failsafe met with the Guardian to discuss a new plan in hopes they wouldn't abandon her again. She temporarily promoted herself to commanding officer so she could direct the Guardian to samples on Nessus to determine whether or not the Vex behavior is a regional phenomenon or something deeper.<ref name="Rising Chorus"/>
On Nessus, she activated her proximity-based sensor leading the Guardian to a coordinate near the Exodus Black. Failsafe sensed something was wrong, and the Vex ambushed the Guardian. After more failed attempts, the Guardian finally found a specimen that Failsafe decided to use as a baseline for further research. She asked the Guardian to deliver it to her mainframe on the Exodus Black, but warned that the Fallen and Vex had begun swarming in increasing numbers.<ref name="Rising Chorus"/>
Failsafe was relieved the Guardian arrived to clear out the Vex and Fallen. Saint-14 joked that he was rubbing off on her, causing her to have increased hatred towards the Vex, but she assured him that she already had plenty of motivation. As the Guardian arrived at the wreckage of the Exodus Black, Failsafe warned them that she detected barriers ahead, and the nearby Arc charges likely shared a related function. After the Guardian cleared out the Fallen, Saint asked if she felt any better, and she told him she preferred silence to gunfire, unlike Guardians. The Guardian deposited the specimen they had previously aquired into her mainframe.<ref>'''Bungie (2024/6/18)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Exodus Crash]]''</ref>
Failsafe detected another specimen on Nessus similar to NES002. The Guardian deposited all three specimens in the H.E.L.M., and she joked that they were shiny and beautiful, just like her. She quickly became embarrassed and returned to her analysis.<ref name="Rising Chorus"/>
After having the Guardian complete tasks around Nessus, Failsafe completed her analysis of the constellation fragment, and was able to extract a Vex protocol for data compression she believed would help the Guardian. She alerted the Guardian that her next research task would be ready any time between three to seven hundred and twenty hours. The Guardian placed the fragment within a display case, and Failsafe congratulated the Guardian for making an excellent team.<ref>'''Bungie (2024/6/18)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Specimen ID: NES002]]''</ref>
Failsafe checked the Guardian's messages, and upon discovering none, she felt bad for them and decided to write one herself. She told them that after the [[Imperial Cabal]] dropped a [[Halphas Electus|land tank]] on Nessus, she though the Guardian had beef with her because they didn't visit her. She noted that they should be glad that she lost her armory. However, she forgave the Guardian, and desperately asked them not to abandon her again.<ref>'''Bungie (2024/6/18)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[H.E.L.M.]] Radio Message: [[H.E.L.M.#Epsiode: Echoes|Failsafe's Message]]''</ref>
Ikora Rey requested that Failsafe accelerate her studies of the [[Nessian Schism|new Vex Collective]]. She ran the scans Ikora wanted, and noted new sample sites for the Guardian to investigate.<ref name="Rising Chorus"/>
Failsafe refined her proximity sensor since the last attempt, and reassured the Guardian that she should be able to detect the samples better. After collecting radiolaria samples, Failsafe noted that something was influencing them, but was interrupted by a call, much to her excitement. It was Osiris, asking for the Guardian to meet him in the H.E.L.M. for a matter involving Saint-14.<ref name="Rising Chorus"/>
In the H.E.L.M., Osiris and Failsafe both attempted to contact Saint, to no avail. Failsafe noted that his comms were open, he just wasn't answering. Failsafe triangulated his location near the anomalous object's impact site, and shared the coordinates to the Guardian.<ref name="Rising Chorus"/>
Failsafe directed the Guardian to Saint's last known coordinates. Failsafe and Ikora noticed that the Vex seemed to have let him pass through without resistance, unlike the Guardian. Travelling down into the [[Well of Flame]], Failsafe was able to isolate Saint's comms. After Ikora attempted to communicate with him, Failsafe noted that he was engaged with a local signal, and could not hear them. The Guardian eventually reached a barrier, and Failsafe began working on opening it using the data the Guardian had been collecting around Nessus, but warned that the Vex would respond to her attempts.<ref>'''Bungie (2024/6/25)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Mission: Mesmerize]]''</ref>
After rescuing Saint-14, Failsafe, Osiris, Ikora, and the Guardian met with him in the H.E.L.M. to ask what had happened to him. He shared that a voice spoke to him, refering to itself as [[Maya Sundaresh|the Conductor]]. Failsafe speculated that since Exo's contained radiolaria, the Vex were able to search for intel on their operation. Saint informed them that it didn't care about their plans, and was merely gauging his humanity, believing himself to not be the "real" Saint-14. Osiris told him that when he saved him from the [[Infinite Forest]], he only searched timelines similar to their own. Failsafe told Saint that because of this, he was as close to the original as mathematically possible. However, Saint ultimately left and asked to be alone.<ref name="Rising Chorus"/>
Failsafe spoke with the Guardian privately, asking if Saint-14 was going to be alright. She had figured that if something bothered him, he would just laugh it off. However, she points out that he has the whole Vanguard to support him. She decided to continue processing the samples, and disabled her compassion protocols to allows her to make the Conductor pay for what it did to Saint.<ref name="Rising Chorus"/>
The Guardian uncovered a Vex specimen, and brought it to Failsafe for analysis. Failsafe sent them to defeat a variety of Vex frames, until she determined that the specimen was a part of a [[Wyvern]]'s shield-wing, and gave her time to read up on Vex particle manipulation.<ref>'''Bungie (2024/6/25)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Specimen ID: NES003]]''</ref>
====Following the Voice====
{{Expand-section}}
{{Expand-section}}
After determining that the radiolaria on Nessus was being drained to a central point at it's core, Ikora Rey sent the Guardian to follow it. As the Guardian arrived in Nessus, Failsafe warned them with almost certainty that the Conductor's plans were nefarious in nature. She also warned of the House Dusk pirates blocking their way towards the core. Osiris assumed that the Fallen were attempting to retrieve the anomalous object, now referred to as an Echo, for themselves. As the Guardian travelled further, Failsafe provide updates on enemy movements to Ikora. Failsafe noticed that the caves were carved by the retroactive flow of radiolaria caused by Vex time manipulation, and wondered where the radiolaria was going. Eventually the Guardian's path was blocked by Vex technology. Failsafe suggested using data obtained [[Hypolydron, Captive Mind|Hypolydron]], a [[Hydra]] the Guardian defeated on their way, by bringing it to the H.E.L.M. for her to crack open.<ref>'''Bungie (2024/7/16)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Battleground: Delve]]''</ref>
Failsafe sent a Hunter down into a flooded cave on Nessus to investigate a signal she couldn't interpret. The Hunter searched for two days, nearly getting trapped before encountering a Vex frame.<ref>'''Bungie (2024/6/4)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Crawlway Sink#Lore|Crawlway Sink]]''</ref>


====Stopping Maya====
Failsafe sent another Fireteam deep into Nessus, following their progress via a live feed. Failsafe reflected that she kind of liked that they were quiet, but it made her feel that she had to fill the silence. She began to wonder if she was annoying and talked too much, and reviewed every fireteam feed she had ever recorded, to no avail. She thought that only the Golden Age could have managed to produce an AI with anxiety. She alerted the fireteam of a large Vex force ahead, which they silently acknowledged. After returning to her queries, she realized that they should have encountered the Vex by now, and upon looking at the feed, she heard nothing and saw a blurry view of the cave. She called out to the Fireteam leader to restore their connection, but received no response. She felt a power surge as the connection broke, and she returned to the uplink in the H.E.L.M.<ref>'''Bungie (2024/6/4)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Lost Signal#Lore|Lost Signal]]''</ref>
{{Expand-section}}


==Personality and traits==
==Personality and traits==
{{Expand-section}}
{{Expand-section}}
Failsafe appears to exhibit a split personality, either being extremely happy or extremely depressed. It is revealed in ''[[Episode: Echoes]]'' that this is in part due to her having a "socialization filter" which automatically adjusts the tone and content of her speech to be pleasant when speaking to humans. However, she is perfectly capable of experiencing negative emotions, including anger and grief, and this becomes especially apparent when her socialization filter is switched off or malfunctioning.
Failsafe appears to exhibit a split personality, either being extremely happy or extremely depressed. It is revealed in ''[[Episode: Echoes]]'' that this is in part due to her having a "socialization filter" which automatically adjusts the tone and content of her speech to be pleasant when speaking to humans. However, she is perfectly capable of experiencing negative emotions, including anger and grief, and this becomes especially apparent when her socialization filter is switched off or malfunctioning.
Failsafe seems to have a great deal of empathy for anyone captured and held for no legitimate reason, as seen when she asked the Guardian to free [[Fallen]] captured by the [[Vex]] as part of an experiment during the adventure [[Release]].
Failsafe disliked [[Cayde-6]], whom she blamed for alerting the Fallen and Vex to her existence, and regularly mocked his intelligence. Despite this, she grieves his death following the events of ''[[Forsaken]].''


==Quotes==
==Quotes==
Line 167: Line 114:
==Trivia==
==Trivia==
*Failsafe is voiced by [[Wikipedia:Joy Osmanski|Joy Osmanski]].
*Failsafe is voiced by [[Wikipedia:Joy Osmanski|Joy Osmanski]].
*Failsafe seems to have a great deal of empathy with anyone captured and held for no legitimate reason, even asking you to free [[Fallen]] captured by the [[Vex]] as part of an experiment in to the [https://en.wikipedia.org/wiki/Prisoner%27s_dilemma prisoner's dilemma] during the adventure Release.
*Failsafe dislikes [[Cayde-6]], who she blames for alerting the Fallen and Vex to her existence, and regularly mocks his intelligence.
**Despite this, she grieves over his death in [[Forsaken]].
*Failsafe's personalities are sometimes referred to as two different individuals;<ref>'''Bungie (2018/12/4)''', ''[[Destiny 2]]: [[Season of the Forge]], [[Lore:Dawning Delights#Celebrate Each Other|Dawning Delights]]''</ref> however, neither ever refer to each other directly and will often finish sentences by the other.
**In Episode: Echoes, it is revealed that she only has one personality, and uses a socialization filter for her "cheery personality".


==List of appearances==
==List of appearances==
Line 182: Line 134:
**''[[The Final Shape]]'' {{Mo}}
**''[[The Final Shape]]'' {{Mo}}
**''[[Episode: Echoes]]''
**''[[Episode: Echoes]]''
**''[[Episode: Revenant]]''
*''[[The Hidden Dossier]]'' {{Mo}}


==References==
==References==

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.

This page is a member of 2 meta categories: