Containment protocol: Difference between revisions
From Halopedia, the Halo wiki
No edit summary |
mNo edit summary |
||
| (23 intermediate revisions by 13 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{Status|Canon}} | ||
[[File:ChiefSparkCEA.png|thumb|300px|[[343 Guilty Spark]] introduces himself to [[John-117]] upon the initiation of Containment Protocol on [[Installation 04]]]] | |||
'''Containment Protocols''' are series of protocols established by the [[Forerunner]]s for dealing with [[Flood]] outbreaks. They help [[Monitor]]s enforce the containment of the Flood parasite in the various [[Flood containment facility|Flood containment facilities]]. | |||
'''Containment | |||
==Background== | ==Background== | ||
On the [[Halo Array|Halo installations]], Containment Protocol is normally enforced by Monitors, but there have been cases of [[Sentinel]]s taking it upon themselves to enforce containment. There are different procedures about enforcing the protocol, judged by the size of the outbreak. If the outbreak is a minor one, the Monitor will deploy a number of [[Aggressor Sentinel]]s and [[Constructor]]s to eliminate the Flood present. In the event of a major outbreak, like that seen on [[Installation 05]]'s [[Quarantine Zone]], [[Sentinel Major|Major Sentinels]] and [[Enforcer]] drones will be mass deployed to eradicate all Flood and its vectors. Unburdened communication is crucial in the event of an outbreak; the protocols dictate that immediate reporting on the status of the outbreak be established among local forces.<ref>'''Halo 2 Anniversary''', ''[[Terminal (Halo 2: Anniversary)|Terminal 5]]''</ref> If containment is breached on a larger scale, then more drastic measures must be taken to ensure that the situation returns to stability, the final option being the use of a Halo installation. | |||
Protocol also includes the procedures involved in activating the Halo Array. It requires a [[Reclaimer]] to retrieve an [[Index]] for activation, that the Monitor store the Index within its own data arrays for transport, and that only the Reclaimer can use the Index to activate the system, because the Monitor is not able to activate Halo by itself.<ref>'''[[Halo: Combat Evolved]]''', level ''[[ | Protocol also includes the procedures involved in activating the Halo Array. It requires a [[Reclaimer]] to retrieve an [[Activation Index|Index]] for activation, that the Monitor store the Index within its own data arrays for transport, and that only the Reclaimer can use the Index to activate the system, because the Monitor is not able to activate Halo by itself.<ref>'''[[Halo: Combat Evolved]]''', campaign level ''[[Two Betrayals]]'' (343 Guilty Spark: "''Protocol does not permit units of my classification to perform a task as important as the reunification of the Index with the Core. That final step is reserved for ''you'', Reclaimer.''")</ref> | ||
The leadership of a Monitor is important, but not always necessary. The Sentinels and Enforcers of [[Delta Halo]] continued to [[Battle of the Quarantine Zone|enforce containment]] even after their monitor, [[2401 Penitent Tangent]], was captured by the [[Gravemind]],<ref>'''[[Halo 2]]''', campaign level ''[[Sacred Icon]]''</ref><ref>'''[[Halo 2]]''', campaign level ''[[Quarantine Zone]]''</ref> and despite their lack of a Monitor the Sentinels of [[Onyx]] abide by Containment Protocol by neutralizing local infection vectors - the [[UNSC Marine Corps|UNSC Marines]], [[SPARTAN-III program|Spartan-IIIs]] and the [[Joyous Exultation Covenant|Covenant forces]] on or near the planet.<ref>'''[[Halo: Ghosts of Onyx]]'''</ref> | |||
Containment protocols, however, cannot be activated or proceeded if the global Sentinel Defense Network is disabled. When [[Voridus]] disabled [[Installation 00]]'s Sentinel Defense Network, the Sentinels were unable to perform their duties, including conducting containment protocol. The containment protocols can only be reenacted if the global Defense Network is online.<ref>'''[[Halo Wars 2: Awakening the Nightmare]]'''</ref> | |||
==List of | ==List of procedures== | ||
When Flood outbreak appears imminent, the Containment Protocol becomes the principal priority. This is the reason that the monitor makes simulations of this event. | When Flood outbreak appears imminent, the Containment Protocol becomes the principal priority. This is the reason that the monitor makes simulations of this event. | ||
| Line 20: | Line 19: | ||
*Determine what, how, and where the problem is. | *Determine what, how, and where the problem is. | ||
*Initiate the Installation's [[Sentinel Production Facility]] to deploy Sentinels, Constructors and Enforcers, depending on the severity of the outbreak, to eradicate any Flood infection vectors and perform necessary maintenance. | *Initiate the Installation's [[Sentinel constructor factory|Sentinel Production Facility]] to deploy Sentinels, Constructors and Enforcers, depending on the severity of the outbreak, to eradicate any Flood infection vectors and perform necessary maintenance. | ||
*If the outbreak cannot be contained, or it looks likely that the Flood will escape, the Monitor will seek out an individual known as a [[Reclaimer]]. | *If the outbreak cannot be contained, or it looks likely that the Flood will escape, the Monitor will seek out an individual known as a [[Reclaimer]]. | ||
*Teleport that Reclaimer to the Library, to retrieve the [[Index]] for activation. | *[[Teleportation grid|Teleport]] that Reclaimer to the Library, to retrieve the [[Activation Index|Index]] for activation. | ||
*Once the Index has been retrieved, the monitor must store it internally to prevent it falling into the hands of the [[Flood]], and teleport itself and the Reclaimer to the [[Control Room]] to activate Halo. | *Once the Index has been retrieved, the monitor must store it internally to prevent it falling into the hands of the [[Flood]], and teleport itself and the Reclaimer to the [[Control Room]] to activate Halo. | ||
| Line 34: | Line 33: | ||
==Gallery== | ==Gallery== | ||
<gallery> | <gallery> | ||
File:Sacredicon1600.jpg|An Installation's [[Library]] is the main focus of containment, and houses the [[Activation Index|Index]]. | |||
File:H2-ThreeSentinelAggressors.png|Sentinel Majors initiating Containment Protocol on [[Installation 05]]. | |||
</gallery> | </gallery> | ||
==Sources== | ==Sources== | ||
{{Ref/Sources}} | |||
[[Category:Forerunner files and protocols]] | [[Category:Forerunner files and protocols]] | ||
[[Category: | [[Category:Halo Array]] | ||
Latest revision as of 00:01, September 29, 2023
Containment Protocols are series of protocols established by the Forerunners for dealing with Flood outbreaks. They help Monitors enforce the containment of the Flood parasite in the various Flood containment facilities.
Background[edit]
On the Halo installations, Containment Protocol is normally enforced by Monitors, but there have been cases of Sentinels taking it upon themselves to enforce containment. There are different procedures about enforcing the protocol, judged by the size of the outbreak. If the outbreak is a minor one, the Monitor will deploy a number of Aggressor Sentinels and Constructors to eliminate the Flood present. In the event of a major outbreak, like that seen on Installation 05's Quarantine Zone, Major Sentinels and Enforcer drones will be mass deployed to eradicate all Flood and its vectors. Unburdened communication is crucial in the event of an outbreak; the protocols dictate that immediate reporting on the status of the outbreak be established among local forces.[1] If containment is breached on a larger scale, then more drastic measures must be taken to ensure that the situation returns to stability, the final option being the use of a Halo installation.
Protocol also includes the procedures involved in activating the Halo Array. It requires a Reclaimer to retrieve an Index for activation, that the Monitor store the Index within its own data arrays for transport, and that only the Reclaimer can use the Index to activate the system, because the Monitor is not able to activate Halo by itself.[2]
The leadership of a Monitor is important, but not always necessary. The Sentinels and Enforcers of Delta Halo continued to enforce containment even after their monitor, 2401 Penitent Tangent, was captured by the Gravemind,[3][4] and despite their lack of a Monitor the Sentinels of Onyx abide by Containment Protocol by neutralizing local infection vectors - the UNSC Marines, Spartan-IIIs and the Covenant forces on or near the planet.[5]
Containment protocols, however, cannot be activated or proceeded if the global Sentinel Defense Network is disabled. When Voridus disabled Installation 00's Sentinel Defense Network, the Sentinels were unable to perform their duties, including conducting containment protocol. The containment protocols can only be reenacted if the global Defense Network is online.[6]
List of procedures[edit]
When Flood outbreak appears imminent, the Containment Protocol becomes the principal priority. This is the reason that the monitor makes simulations of this event.
When enforcing this protocol, the Monitor must:
- Determine what, how, and where the problem is.
- Initiate the Installation's Sentinel Production Facility to deploy Sentinels, Constructors and Enforcers, depending on the severity of the outbreak, to eradicate any Flood infection vectors and perform necessary maintenance.
- If the outbreak cannot be contained, or it looks likely that the Flood will escape, the Monitor will seek out an individual known as a Reclaimer.
- Once the Index has been retrieved, the monitor must store it internally to prevent it falling into the hands of the Flood, and teleport itself and the Reclaimer to the Control Room to activate Halo.
- Once Halo is on the firing process, make the final countdown.
Here, the Containment Protocol presumably finishes and the Halo Array is activated. If the firing is stopped for some reason, (Delta Halo for example) the Monitor must restart the Containment Protocol or activate the rings through the Ark.
Gallery[edit]
Sentinel Majors initiating Containment Protocol on Installation 05.
Sources[edit]
- ^ Halo 2 Anniversary, Terminal 5
- ^ Halo: Combat Evolved, campaign level Two Betrayals (343 Guilty Spark: "Protocol does not permit units of my classification to perform a task as important as the reunification of the Index with the Core. That final step is reserved for you, Reclaimer.")
- ^ Halo 2, campaign level Sacred Icon
- ^ Halo 2, campaign level Quarantine Zone
- ^ Halo: Ghosts of Onyx
- ^ Halo Wars 2: Awakening the Nightmare
