Installation 00: Difference between revisions

Installation 00 (edit)

Revision as of 11:07, December 22, 2021

20 bytes added , 2 years ago

no edit summary

MikhailMCraft

67

edits

@@ Line 19: / Line 19: @@
 |atmosphere=1.0 ([[Wikipedia:Nitrogen|N<sub>2</sub>]], [[Oxygen|O<sub>2</sub>]], [[Argon|Ar]]){{Ref/Reuse|vis}}
 }}
-{{quote|multi=yes|Miranda Keyes|343 Guilty Spark|q1=Where would someone go to activate the other rings?|q2=...Why, the Ark, of course.|[[343 Guilty Spark]] to [[Commander]] [[Miranda Keyes]]}}
+{{quote|multi=yes|Miranda Keyes|343 Guilty Spark|q1=Where would someone go to activate the other rings?|q2=...Why, the Ark, of course.|[[343 Guilty Spark]] to [[Commander]] [[Miranda Keyes]].}}
 '''Installation 00''', also known as '''the Ark''', '''the Great Foundry''' by the Covenant {{Ref/Game|HI|Audio log (Halo Infinite)#Outpost Intel 9|Banished Audio log|Detail=Outpost Intel #09 - Unnatrual Defenses}} and sometimes translated as '''Waypoint''',<ref name="CatalogWaypoint">[https://web.archive.org/web/20141014090727/https://forums.halowaypoint.com/yaf_postst248110_Query--Catalog-old.aspx '''Halo Waypoint''': ''Query: Catalog (old)''], [https://web.archive.org/web/20141013192621/https://forums.halowaypoint.com/yaf_postsm2963929_Catalog-Interaction.aspx#post2963929 '''Halo Waypoint''': ''Catalog Interaction'']</ref> is a [[Forerunner]] installation from which the entirety of the [[Halo Array]] can be activated.<ref>'''[[Halo 2]]''', campaign level ''[[The Great Journey]]''</ref> Installation 00 also functions as a potential safe haven from the Halo Array's strategic pulse, and as a facility to construct replacement Halos if necessary. The Ark is situated [[Intergalactic space|outside]] the [[Milky Way|galaxy]], about 2<sup>18</sup> (262,144) light years from the galactic center.<ref name="The Ark">'''[[Halo 3]]''', campaign level ''[[The Ark (level)|The Ark]]''</ref> Although later universally known as "the Ark", Installation 00 was originally one of two installations identified as [[Ark]]s, the other being the older [[greater Ark]]. Due to this, Installation 00 was also referred to as the '''lesser Ark''' to differentiate it from the much larger greater Ark, whose foundry produced the original array of rings 30,000 kilometers in diameter, as opposed to the 10,000 kilometer-wide foundry of Installation 00.<ref>'''[[Halo: Primordium]]''', ''pages 343-344''</ref>
@@ Line 78: / Line 78: @@
 ===Forerunner-Flood war===
 [[File:Array.png|thumb|left|250px|Installation 00 sending the Halo Array through a [[slipspace portal]] during the [[Forerunner-Flood war]].]]
-{{quote|Every vessel we can fill, we send to the Ark. I dare not cease the mission. Not now, not until I've done all I can. Each one of these souls is finite and precious. And I'm close. Close to saving them all.|A message from the [[Librarian]] to the [[IsoDidact]]}}
+{{quote|Every vessel we can fill, we send to the Ark. I dare not cease the mission. Not now, not until I've done all I can. Each one of these souls is finite and precious. And I'm close. Close to saving them all.|A message from the [[Librarian]] to the [[IsoDidact]].}}
-Like the rest of the newer, more efficient Halo Array, Installation 00 was constructed sometime between [[98,445 BCE]] and [[97,445 BCE]] under orders of [[Master Builder]] [[Faber]], to address problems with the [[greater Ark]] and its larger Halos. While plans for the second Ark had existed for some time, its construction was delayed by the [[Old Council]] to avoid the Builders from gaining too much power.<ref>'''[[Halo: Silentium]]''', ''page 45''</ref> The lesser Ark, as it was known at the time, was designed to produce smaller but much more powerful Halo rings, which could be transported more efficiently and could deal far more widespread damage. Until the very last days of the [[Forerunner-Flood war]], the lesser Ark, its new Halos, and its location were kept a well-guarded secret; only the most top-tier Forerunners knew of its existence, and the only one who knew the exact coordinates of the installation was Faber. Whereas the greater Ark acted as the Forerunners' final line of defense and command center, the lesser Ark would serve the function of a last fallback point where its own array of rings could be swiftly distributed to their designated locations across the galaxy and fired to cleanse the galaxy of all sentient life as a last resort.<ref>'''[[Halo: Silentium]]''', ''String 33''</ref>
+Like the rest of the newer, more efficient Halo installations, Installation 00 was constructed sometime between [[98,445 BCE]] and [[97,445 BCE]] under orders of [[Master Builder]] [[Faber]], to address problems with the [[greater Ark]] and its larger Halos. While plans for the second Ark had existed for some time, its construction was delayed by the [[Old Council]] to avoid the Builders from gaining too much power.<ref>'''[[Halo: Silentium]]''', ''page 45''</ref> The lesser Ark, as it was known at the time, was designed to produce smaller but much more powerful Halo rings, which could be transported more efficiently and could deal far more widespread damage. Until the very last days of the [[Forerunner-Flood war]], the lesser Ark, its new Halos, and its location were kept a well-guarded secret; only the most top-tier Forerunners knew of its existence, and the only one who knew the exact coordinates of the installation was Faber. Whereas the greater Ark acted as the Forerunners' final line of defense and command center, the lesser Ark would serve the function of a last fallback point where its own array of rings could be swiftly distributed to their designated locations across the galaxy and fired to cleanse the galaxy of all sentient life as a last resort.<ref>'''[[Halo: Silentium]]''', ''String 33''</ref>
 [[File:HM-IsoDidact.png|thumb|150px|right|The IsoDidact activates the Halo Array from Installation 00's citadel.]]
@@ Line 101: / Line 101: @@
 In [[2553|March 2553]], the [[Office of Naval Intelligence]] deployed an automated probe-carrying spacecraft to the damaged Ark using advanced slipspace technology. The ship arrived in November and dispersed its probes, although all communications with the devices were cut off after initial transmissions confirming the Ark's survival. In response, the {{UNSCShip|Rubicon}} was sent from [[Luna]] in December 2553 to conduct a more thorough investigation of the installation's ravaged surface.<ref name="hitd c2">'''[[Halo: Hunters in the Dark]]''', ''Chapter 2''</ref> Due to the damage dealt to the Ark's life support systems and its artificial sun, heavily inclement weather became the norm.<ref name="EH">'''[[Eleventh Hour reports]]''', ''part 4''</ref>
-The [[ UNSC Rubicon]] carried several [[remote contact team]]s, who landed on the damaged Ark and attempted to find the source of the mysterious signal. After about eight days, contact with all teams was lost; only one team, [[RCT-06]], returned, having sustained heavy casualties and carrying with them a device of unknown nature. The armature's origin was subjected to debate, but it was believed by the team to be the source of the beacon picked up by the initial investigative group.{{Ref/Reuse|EH}} The device, actually a broken, barely active [[monitor]], began to relate its past life as a human: [[Chakas]]. Though the ship's ONI attaché initially doubted the veracity of the monitor's account, the science team leader pointed out that it was consistent with the "[[Halo: Cryptum|Bornstellar Relation]]" found on [[Onyx]].
+The {{UNSCShip|Rubicon}} carried several [[remote contact team]]s, who landed on the damaged Ark and attempted to find the source of the mysterious signal. After about eight days, contact with all teams was lost; only one team, [[RCT-06]], returned, having sustained heavy casualties and carrying with them a device of unknown nature. The armature's origin was subjected to debate, but it was believed by the team to be the source of the beacon picked up by the initial investigative group.{{Ref/Reuse|EH}} The device, actually a broken, barely active [[monitor]], began to relate its past life as a human: [[Chakas]]. Though the ship's ONI attaché initially doubted the veracity of the monitor's account, the science team leader pointed out that it was consistent with the "[[Halo: Cryptum|Bornstellar Relation]]" found on [[Onyx]].
 [[File:TSPL.png|250px|thumb|left|000 Tragic Solitude observes the heavily damaged Ark.]]
 Eventually, the monitor revealed that it was none other than [[343 Guilty Spark]] himself. Claiming that he knew the location of the [[Librarian]], whom he believed to be alive, Spark subsumed the ship's AI, knocked out the crew via the life support systems, and hijacked the ship.<ref>'''[[Halo: Primordium]]''', ''pages 377-379''</ref> Communications with the ''Rubicon'' halted within 48 hours of its last report. Search and rescue teams were then deployed to the site, but reported no findings.{{Ref/Reuse|EH}}
-The last of its ground team, [[Bobby Kodiak]], was left stranded when the ''Rubicon'' left, and mortally wounded by attacking [[chaefka]]. It was then that he was contacted by the Ark's monitor, [[000 Tragic Solitude]], who had survived the Ark's devastation and sought to repair the station and get revenge. Offering him a chance to live, Tragic Solitude rescued Kodiak and mended his body with cybernetics, turning him into a cyborg and putting him under the monitor's control. For the following two years, Tragic Solitude partially repaired the Ark and prepared for an attack on the galaxy. Tragic Solitude was able to repair the Ark end of the [[Portal at Voi]] and increase its power so that the portal would transport objects near-instantaneously between Earth and the Ark, but he couldn't activate the portal as the firing of Installation 08 had severed the monitor's control over it.<ref name="Hunters">'''''[[Halo: Hunters in the Dark]]'''</ref>{{clear}}
+The last of its ground team, [[Bobby Kodiak]], was left stranded when the ''Rubicon'' left, and mortally wounded by attacking [[chaefka]]. It was then that he was contacted by the Ark's monitor, [[000 Tragic Solitude]], who had survived the Ark's devastation and sought to repair the station and get revenge. Offering him a chance to live, Tragic Solitude rescued Kodiak and mended his body with cybernetics, turning him into a cyborg and putting him under the monitor's control. For the following two years, Tragic Solitude partially repaired the Ark and prepared for an attack on the galaxy. Tragic Solitude was able to repair the Ark end of the [[Portal at Voi]] and increase its power so that the portal would transport objects near-instantaneously between Earth and the Ark, but he could not activate the portal as the firing of Installation 08 had severed the monitor's control over it.<ref name="Hunters">'''''[[Halo: Hunters in the Dark]]'''''</ref>{{clear}}
 ===Operation: FAR STORM===
@@ Line 148: / Line 148: @@
 ===Defenses===
 [[File:FOR-ArkAI-logo2.png|thumb|left|240px|The avatar icon of [[000 Tragic Solitude]]{{Ref/Reuse|Terminals}}]]
-Similar to most Forerunner installations, the Ark had its own [[monitor]], [[000 Tragic Solitude]], charged with the facility's defenses. For the most part, Solitude reacted little when humanity and the Covenant arrived at the Ark, though when 343 Guilty Spark attempted to access the Ark's systems during the Battle of Installation 00, Tragic Solitude threatened to add the monitor to the facility's targeting ledger if he persisted.<ref>'''Halo 3''', ''Terminal 3''</ref> After the Ark was severely damaged by the destruction of Installation 08, the latest on a line of destroyed Forerunner relics, Solitude grew bitter and viewed all sentients in the galaxy as incapable of being peaceful.{{Ref/Reuse|Hunters}} The arrival of the Human-Covenant War to the installation additionally prompted the activation of [[Terminus]]', structures that are designed to perform tireless cataloging, recording of indexing of events in an attempt to prepare countermeasures and defences for future possible scenarios. These records are cross-references with existing records of historical events and battles to perform simulations and predictions of potential outcomes - losing a terminus would result in a massive loss of operational capability for the installation.<ref name="Terminus">'''[[Halo Wars 2]]''', ''[[Phoenix Logs]]'' - ''Terminus''</ref>
+Similar to most Forerunner installations, the Ark had its own [[monitor]], [[000 Tragic Solitude]], charged with the facility's defenses. For the most part, Solitude reacted little when humanity and the Covenant arrived at the Ark, though when 343 Guilty Spark attempted to access the Ark's systems during the Battle of Installation 00, Tragic Solitude threatened to add the monitor to the facility's targeting ledger if he persisted.<ref>'''Halo 3''', ''Terminal 3''</ref> After the Ark was severely damaged by the destruction of Installation 08, the latest on a line of destroyed Forerunner relics, Solitude grew bitter and viewed all sentients in the galaxy as incapable of being peaceful.{{Ref/Reuse|Hunters}} The arrival of the Human-Covenant War to the installation additionally prompted the activation of [[Terminus]]', structures that are designed to perform tireless cataloging, recording of indexing of events in an attempt to prepare countermeasures and defenses for future possible scenarios. These records are cross-references with existing records of historical events and battles to perform simulations and predictions of potential outcomes - losing a terminus would result in a massive loss of operational capability for the installation.<ref name="Terminus">'''[[Halo Wars 2]]''', ''[[Phoenix Logs]]'' - ''Terminus''</ref>
 The Ark's small defenses were [[Aggressor Sentinel]]s created by numerous [[Sentinel manufacturing facility|Sentinel factories]] just like at the rings. The [[Retriever Sentinel]]s could also be used offensively, though they were not usually outfitted with weapons until Solitude began arming them. The Ark was also guarded by [[armigers]], humanoid defense droids that were capable of attacking with energy rifles and staves. Tragic Solitude could also take control of the Ark's wildlife and even people through manipulating their brain waves.{{Ref/Reuse|Hunters}}
@@ Line 154: / Line 154: @@
 After the [[Battle of Installation 00]], Tragic Solitude had a [[containment shield]] erected around the ruins of the Covenant holy city of [[High Charity]] to contain any surviving [[Flood]] within. He also had the Ark's Sentinels raze the perimeter and modify the refugia so that no sentient life survives nearby to deprive the Flood of any host bodies in close proximity to their prison.<ref>'''[[Halo Wars 2]]''', ''[[Phoenix Logs]]'' - ''Idle Hands II''</ref>
-Another method of defense are [[particle cannon]]s upon the Ark's surface. After discovering the location of one through one of the Ark's Cartographers,{{Ref/Reuse|The Cartographer}} the smart AI [[Isabel]] had Professor [[Ellen Anders]] use it to attack the {{Class|CAS|assault carrier}} ''[[Enduring Conviction]]''. The cannon alone wasn't powerful enough to destroy the ship, but after thirty minutes of sustained fire could take down its shields and leave the ship vulnerable to other methods of attack.{{Ref/Reuse|Hold the Line}}<ref>'''[[Halo Wars 2]]''', ''[[Phoenix Logs]]'' - ''Enduring Conviction Battle Reports''</ref>
+Another method of defense are [[particle cannon]]s upon the Ark's surface. After discovering the location of one through one of the Ark's Cartographers,{{Ref/Reuse|The Cartographer}} the smart AI [[Isabel]] had Professor [[Ellen Anders]] use it to attack the {{Class|CAS|assault carrier}} ''[[Enduring Conviction]]''. The cannon alone was not powerful enough to destroy the ship, but after thirty minutes of sustained fire could take down its shields and leave the ship vulnerable to other methods of attack.{{Ref/Reuse|Hold the Line}}<ref>'''[[Halo Wars 2]]''', ''[[Phoenix Logs]]'' - ''Enduring Conviction Battle Reports''</ref>
-The Ark also possesses a Sentinel defense network that coordinates Sentinels to assemble and attack anything deemed a threat to the Ark. [[Isabel]] utilized the network to destroy the ''Enduring Conviction'' by firing the assault carrier's [[energy projector]] at the Ark, alerting the Sentinels in the area.<ref name="Under the Dark">'''[[Halo Wars 2]]''', campaign level ''[[Under The Dark]]''</ref> Prior to the launch of [[Installation 09]], the security protocols was heightened to finalize the preparation for the launch to its original site and as the part of protocol, the Sentinels release [[Retriever Sentinel]] to cleanse the Installation from the threat, including the UNSC and the Banished.<ref>'''[[Halo Wars 2]]''', campaign level ''[[The Halo]]''</ref> During [[Operation: SPEARBREAKER|an operation]] led by Major Vaughan, a Controller Sentinel attacked anyone it deemed a threat, even the UNSC, due to constant abuse of the teleportation network before the ''Spirit of Fire's'' arrival.<ref>'''[[Halo Wars 2: Operation: SPEARBREAKER]]''</ref> [[Voridus]] managed to shut down the Sentinel defense network around [[High Charity]]'s crash site, but at the price of the [[Flood]] being released from the ruined city after he breached the [[containment shield]] with a [[Banished Scarab]]. When the network was reactivated, the Sentinels resumed their duties and aided the Banished in defeating the Flood, enabling them to enact the containment protocol once again.{{Ref/Reuse|Awakening the Nightmare}}
+The Ark also possesses a Sentinel defense network that coordinates Sentinels to assemble and attack anything deemed a threat to the Ark. [[Isabel]] utilized the network to destroy the ''Enduring Conviction'' by firing the assault carrier's [[energy projector]] at the Ark, alerting the Sentinels in the area.<ref name="Under the Dark">'''[[Halo Wars 2]]''', campaign level ''[[Under The Dark]]''</ref> Prior to the launch of [[Installation 09]], the security protocols was heightened to finalize the preparation for the launch to its original site and as the part of protocol, the Sentinels release [[Retriever Sentinel]] to cleanse the Installation from the threat, including the UNSC and the Banished.<ref>'''[[Halo Wars 2]]''', campaign level ''[[The Halo]]''</ref> During [[Operation: SPEARBREAKER|an operation]] led by Major Vaughan, a Controller Sentinel attacked anyone it deemed a threat, even the UNSC, due to constant abuse of the teleportation network before the ''Spirit of Fire''{{'}}s arrival.<ref>''[[Halo Wars 2: Operation: SPEARBREAKER]]''</ref> [[Voridus]] managed to shut down the Sentinel defense network around [[High Charity]]'s crash site, but at the price of the [[Flood]] being released from the ruined city after he breached the [[containment shield]] with a [[Banished Scarab]]. When the network was reactivated, the Sentinels resumed their duties and aided the Banished in defeating the Flood, enabling them to enact the containment protocol once again.{{Ref/Reuse|Awakening the Nightmare}}
 ===Slipspace portals===