2401 Penitent Tangent: Difference between revisions
From Halopedia, the Halo wiki
mNo edit summary |
mNo edit summary |
||
| Line 22: | Line 22: | ||
===Flood outbreak=== | ===Flood outbreak=== | ||
In [[97,227 BCE|May 97,227 BCE]], [[Unidentified Monitor (Installation 05)|another artificial intelligence construct]] warned 2401 Penitent Tangent of a pending outbreak in one the installation's [[Flood]] [[Flood containment facility|containment facilities]]. The monitor continued to ignore this warning, and those that followed, for millenia. Within [[2552|99,779 years]], the containment facility, as well as much of the Halo, had been overrun by the Flood.<ref>'''[[Halo 3]]''', ''[[Cold Storage]]'' transmissions</ref> Eventually, the [[Quarantine Zone]] was established and the full force of the installation's [[Sentinel]]s and [[Enforcer]]s was mobilized.<ref>'''Halo 2''', campaign level ''[[Sacred Icon]]''</ref><ref>'''Halo 2''', campaign level ''[[Quarantine Zone]]''</ref> | In [[97,227 BCE|May 97,227 BCE]], [[Unidentified Monitor (Installation 05)|another artificial intelligence construct]] warned 2401 Penitent Tangent of a pending outbreak in one the installation's [[Flood]] [[Flood containment facility|containment facilities]]. The monitor continued to ignore this warning, and those that followed, for millenia. Within [[2552|99,779 years]], the containment facility, as well as much of the Halo, had been overrun by the Flood.<ref>'''[[Halo 3]]''', ''[[Cold Storage]]'' transmissions</ref> Eventually, the [[Quarantine Zone]] was established and the full force of the installation's [[Sentinel]]s and [[Enforcer]]s was mobilized.<ref>'''Halo 2''', campaign level ''[[Sacred Icon]]''</ref><ref>'''Halo 2''', campaign level ''[[Quarantine Zone]]''</ref> | ||
===Installation 05 containment failure reports=== | |||
{{scroll box | {{scroll box | ||
|width=600px | |||
|content= | |content= | ||
REPORT: CONTAINMENT FAILURE | REPORT: CONTAINMENT FAILURE | ||
LF.Xx.3273 research and containment facility; [delta site] has experienced catastrophic specimen containment failure. All apertures into facility will be locked until further notice. Atmosphere evacuation and [reduction of ambient temperature] protocols have already been enacted. Request maintenance and security detail [at earliest opportunity]. [8 minutes] elapsed since initial containment failure. | LF.Xx.3273 research and containment facility; [delta site] has experienced catastrophic specimen containment failure. All apertures into facility will be locked until further notice. Atmosphere evacuation and [reduction of ambient temperature] protocols have already been enacted. Request maintenance and security detail [at earliest opportunity]. [8 minutes] elapsed since initial containment failure. | ||
REPORT: CONTAINMENT FAILURE | REPORT: CONTAINMENT FAILURE | ||
| Line 37: | Line 35: | ||
Waiting for maintenance and security detail. [32 minutes, 9 seconds] elapsed since request. | Waiting for maintenance and security detail. [32 minutes, 9 seconds] elapsed since request. | ||
REPORT: CONTAINMENT FAILURE | REPORT: CONTAINMENT FAILURE | ||
Still waiting for maintenance and security detail. [24 hours] elapsed since request. | Still waiting for maintenance and security detail. [24 hours] elapsed since request. | ||
REPORT: SECURITY BREACH | REPORT: SECURITY BREACH | ||
| Line 47: | Line 43: | ||
LF.Xx.3273 research and containment facility; [delta site] has experienced a security breach via emergency [slip stream space] transportation conduits. Emergency [slip stream space] transportation conduits have been placed in recursive mode to contain unauthorized hostile life forms. Request emergency security detail. Still waiting for primary maintenance and security detail. [2512332 hours, 14 minutes, 6 seconds]elapsed since initial request. | LF.Xx.3273 research and containment facility; [delta site] has experienced a security breach via emergency [slip stream space] transportation conduits. Emergency [slip stream space] transportation conduits have been placed in recursive mode to contain unauthorized hostile life forms. Request emergency security detail. Still waiting for primary maintenance and security detail. [2512332 hours, 14 minutes, 6 seconds]elapsed since initial request. | ||
REPORT: DERELICTION OF DUTY | REPORT: DERELICTION OF DUTY | ||
| Line 55: | Line 50: | ||
LF.Xx.3273 research and containment facility [alpha, beta, gamma, epsilon, zeta, and kappa sites] have all replied [systems normal] within expected constraints. This would tend to signify that the containment failure was purely mechanical in nature; perhaps a manufacturing flaw. As no [outside agent] has accessed [delta site] in the past [874068942 hours, 4 minutes, 46 seconds]—[allowing for a 61360 hour, 54, minute, 2 second margin of error]—sabotage would seem unlikely. | LF.Xx.3273 research and containment facility [alpha, beta, gamma, epsilon, zeta, and kappa sites] have all replied [systems normal] within expected constraints. This would tend to signify that the containment failure was purely mechanical in nature; perhaps a manufacturing flaw. As no [outside agent] has accessed [delta site] in the past [874068942 hours, 4 minutes, 46 seconds]—[allowing for a 61360 hour, 54, minute, 2 second margin of error]—sabotage would seem unlikely. | ||
LOG: REQUEST UNANSWERED | |||
LF.Xx.3273 research and containment facility; [delta site] is currently being held at [.01 atm] / [184K]. Local maintenance and security hubs have failed to reply within expected constraints. [Bumping maintenance and security request up] to [quadrant oversight]. | LF.Xx.3273 research and containment facility; [delta site] is currently being held at [.01 atm] / [184K]. Local maintenance and security hubs have failed to reply within expected constraints. [Bumping maintenance and security request up] to [quadrant oversight]. | ||
LOG: REQUEST UNANSWERED | |||
LF.Xx.3273 research and containment facility; [delta site] is currently being held at [1 atm] / [278K] as atmospheric seals were showing signs of stress. [Quadrant oversight] has failed to reply within expected constraints. [Bumping maintenance and security request all the way up] to 2401 [PENITENT TANGENT]. | LF.Xx.3273 research and containment facility; [delta site] is currently being held at [1 atm] / [278K] as atmospheric seals were showing signs of stress. [Quadrant oversight] has failed to reply within expected constraints. [Bumping maintenance and security request all the way up] to 2401 [PENITENT TANGENT]. | ||
LOG: UNAUTHORIZED ACCESS TO FACILITIES | |||
LF.Xx.3273 research and containment facility; [delta site] emergency [slip stream space] transportation conduits have been accessed by unauthorized parties. | LF.Xx.3273 research and containment facility; [delta site] emergency [slip stream space] transportation conduits have been accessed by unauthorized parties. | ||
LOG: FILED COMPLAINT TO INSTALLATION 00 | |||
2401 [PENITENT TANGENT], monitor of Installation 05, has been lax in the areas of maintenance and security. Requests for aid in said areas have gone unanswered by both 2401 and [subservient] systems well beyond expected constraints.<ref>[http://www.bungie.net/news/content.aspx?type=topnews&cid=14034 Bungie.net Weekly Update] (2008-06-06) Archived on 2009-03-19 at [http://www.webcitation.org/5fP4PTGw7 WebCite]</ref> | 2401 [PENITENT TANGENT], monitor of Installation 05, has been lax in the areas of maintenance and security. Requests for aid in said areas have gone unanswered by both 2401 and [subservient] systems well beyond expected constraints.<ref>[http://www.bungie.net/news/content.aspx?type=topnews&cid=14034 Bungie.net Weekly Update] (2008-06-06) Archived on 2009-03-19 at [http://www.webcitation.org/5fP4PTGw7 WebCite]</ref> | ||
}} | }} | ||
==Battle of Installation 05== | ===Battle of Installation 05=== | ||
{{Main|Battle of Installation 05}} | {{Main|Battle of Installation 05}} | ||
By [[2552#November|November 2, 2552]], 2401 Penitent Tangent had been captured by the Flood and was held captive by the [[Gravemind]] that had manifested on Installation 05. After the battle on the ring had raged for some time, the Gravemind absorbed and reanimated the [[Prophet of Regret]], one of the [[Hierarchs]] of the [[Covenant Empire|Covenant]]. Later, [[SPARTAN-II Program|SPARTAN]] [[John-117]] and [[Arbiter]] [[Thel 'Vadam]]ee were also captured by the Gravemind. Upon seeing John, a [[Reclaimer]], the monitor urged the SPARTAN to activate the ring. Penitent Tangent was immediately defied by Regret, who insisted that nothing could be done until he had completed his sermon of in preparation for the [[Covenant religion|Great Journey]]. The monitor countered that the installation had been tested trillions of times and was ready to fire on demand. The Hierarch then torted that the "Oracles" were the most worthless artifacts that had been left by the Forerunners, prompting the monitor to berate Regret for his lack of regard for protocol. Amid the argument, the Gravemind insisted that the four factions represented in the meeting shared a common goal: preventing the ring from being activated. Shortly thereafter, the Gravemind used the monitor's control of Installation 05's [[teleportation grid]] to send the SPARTAN and 'Vadamee to ''[[High Charity]]'' and the Halo's [[Control Room|control room]], respectively, in an attempt to stop the activation of the Halo array.<ref>'''Halo 2''', campaign level ''[[Gravemind (level)|Gravemind]]''</ref> | By [[2552#November|November 2, 2552]], 2401 Penitent Tangent had been captured by the Flood and was held captive by the [[Gravemind]] that had manifested on Installation 05. After the battle on the ring had raged for some time, the Gravemind absorbed and reanimated the [[Prophet of Regret]], one of the [[Hierarchs]] of the [[Covenant Empire|Covenant]]. Later, [[SPARTAN-II Program|SPARTAN]] [[John-117]] and [[Arbiter]] [[Thel 'Vadam]]ee were also captured by the Gravemind. Upon seeing John, a [[Reclaimer]], the monitor urged the SPARTAN to activate the ring. Penitent Tangent was immediately defied by Regret, who insisted that nothing could be done until he had completed his sermon of in preparation for the [[Covenant religion|Great Journey]]. The monitor countered that the installation had been tested trillions of times and was ready to fire on demand. The Hierarch then torted that the "Oracles" were the most worthless artifacts that had been left by the Forerunners, prompting the monitor to berate Regret for his lack of regard for protocol. Amid the argument, the Gravemind insisted that the four factions represented in the meeting shared a common goal: preventing the ring from being activated. Shortly thereafter, the Gravemind used the monitor's control of Installation 05's [[teleportation grid]] to send the SPARTAN and 'Vadamee to ''[[High Charity]]'' and the Halo's [[Control Room|control room]], respectively, in an attempt to stop the activation of the Halo array.<ref>'''Halo 2''', campaign level ''[[Gravemind (level)|Gravemind]]''</ref> | ||
Revision as of 18:40, March 3, 2011
| 2401 Penitent Tangent | |
|---|---|
| File:PenitentTangent01.jpg | |
| Biographical information | |
|
Began service: |
More than 100,000 years ago |
|
Gender: |
N/A (Male characteristics) |
|
Color(s): |
Likely blue; red while in proximity to the Gravemind |
| Political and military information | |
|
Affiliation: |
Forerunner |
|
Functionality: |
Monitor of Installation 05 |
- "And you know nothing about containment! You have demonstrated a complete disregard for even the most basic protocols!"
- — 2401 Penitent Tangent rebuking the Prophet of Regret
2401 Penitent Tangent is the monitor of Halo Installation 05.[1]
Biography
Flood outbreak
In May 97,227 BCE, another artificial intelligence construct warned 2401 Penitent Tangent of a pending outbreak in one the installation's Flood containment facilities. The monitor continued to ignore this warning, and those that followed, for millenia. Within 99,779 years, the containment facility, as well as much of the Halo, had been overrun by the Flood.[2] Eventually, the Quarantine Zone was established and the full force of the installation's Sentinels and Enforcers was mobilized.[3][4]
Installation 05 containment failure reports
Battle of Installation 05
- Main article: Battle of Installation 05
By November 2, 2552, 2401 Penitent Tangent had been captured by the Flood and was held captive by the Gravemind that had manifested on Installation 05. After the battle on the ring had raged for some time, the Gravemind absorbed and reanimated the Prophet of Regret, one of the Hierarchs of the Covenant. Later, SPARTAN John-117 and Arbiter Thel 'Vadamee were also captured by the Gravemind. Upon seeing John, a Reclaimer, the monitor urged the SPARTAN to activate the ring. Penitent Tangent was immediately defied by Regret, who insisted that nothing could be done until he had completed his sermon of in preparation for the Great Journey. The monitor countered that the installation had been tested trillions of times and was ready to fire on demand. The Hierarch then torted that the "Oracles" were the most worthless artifacts that had been left by the Forerunners, prompting the monitor to berate Regret for his lack of regard for protocol. Amid the argument, the Gravemind insisted that the four factions represented in the meeting shared a common goal: preventing the ring from being activated. Shortly thereafter, the Gravemind used the monitor's control of Installation 05's teleportation grid to send the SPARTAN and 'Vadamee to High Charity and the Halo's control room, respectively, in an attempt to stop the activation of the Halo array.[5]
List of appearances
- Halo 2 (First appearance)
Trivia
- 2401 Penitent Tangent was voiced by John Michael Higgins.
- Like all monitors, 2401 Penitent Tangent's numerical designation is derived from seven raised to one less than the number of his installation (7n-1). This is one of Bungie's numerous references to the number seven in the Halo series.
- "Penitent" means feeling or expressing sorrow for sin or wrongdoing and [being] disposed to atonement and amendment" and is synonymous with "repentant".[6] "Tangent" is part of the idiom "off on a tangent", which refers to digressing suddenly from one course of action or thought and turning to another.[7] This name may reflect the Monitor's actions; it could be described as sorrowfully digressing from one course of action (neglecting its installation) and turning to another (wishing to activate the Halo). This is interesting, as Penitent is a synonym for Guilty, and Tangent is similar to Spark. It has been theorized that all Monitors were named following this pattern.
- 2401 Penitent Tangent appears in the Halo 2 multiplayer map Backwash. He hovers around the map and is invernerable to damage.
Sources
- ^ Halo 2 level Gravemind. "Greetings! I am 2401 Penitent Tangent. I am the monitor of Installation 05."
- ^ Halo 3, Cold Storage transmissions
- ^ Halo 2, campaign level Sacred Icon
- ^ Halo 2, campaign level Quarantine Zone
- ^ Halo 2, campaign level Gravemind
- ^ Dictionary.com: penitent
- ^ Dictionary.com: tangent
| ||||||||||||||||||||||
