343 Guilty Spark

Looking for 343 Guilty Spark, the Halo: Combat Evolved level, or The Oracle, the Halo 2 level?

"Greetings! I am the monitor of Installation 04. I am 343 Guilty Spark."

- Guilty Spark introducing himself to John-117.

04-343 Guilty Spark, known to the Covenant as "the Oracle", was a Forerunner monitor tasked with maintaining Installation 04. Guilty Spark played an important role in the Battle of Installation 04, the heretic uprising within the Covenant, and the events that transpired on the Ark during the Battle of Installation 00.

Forerunner-Flood war
Prior to the end of the Forerunner-Flood war, 343 Guilty Spark was created from the mind of a human named Chakas. Later, he oversaw the construction of the outbreak management systems of the Flood research facilities within a gas mine over Threshold. Immediately preceding the Halo Array's distribution across the galaxy, he was commanded by the Ecumene Council to abandon all connection with his former station. From that point forward, Spark became the designated guardian and custodian of Installation 04.

Intermediate period
During the eons he spent monitoring Installation 04, he began to display signs of rampancy due to facing crippling loneliness, especially after communications with the other Installations had ceased. During that time, he would begin to recollect his time spent with the Forerunner, their war with the Flood, decisions they made, and decisions he believes they should have made.

By the time the ring was re-discovered by human and Covenant forces, 343 Guilty Spark had been present on Installation 04 for 101,217 "local years", and during that time had conducted over one trillion simulated, and one actual firing of the installation. During his long isolation, Spark presumably had little to no contact with other intelligent beings, and spent most of his time maintaining his Installation.

In addition to his primary incarnation serving as the monitor of Installation 04, an unknown number of fragmented duplicates of Guilty Spark were created over time, performing different tasks and sometimes unaware of actions performed by the other duplicates.

Flood outbreak
"Oh dear. Containment protocols appear to have been violated."

- 343 Guilty Spark

After over one hundred thousand years without incident, Spark was faced with a crisis when the discovered Installation 04, pursued by the Covenant Fleet of Particular Justice. Fearing a containment breach, Spark warned the ship to jump at least one light-year away from the Installation or be destroyed. After remotely accessing the ship's systems, however, Spark realized that the ship is manned by Reclaimers after finding data on human history; he then deactivated the ring's defensive systems and instructed the ship to a docking facility - the Autumn crash-landed on the ringworld shortly afterwards.

During the subsequent UNSC - Covenant guerrilla war, Covenant troops stumbled upon a Flood containment facility, and after unwittingly deactivating the structure's containment measures, they unleashed the long-dormant Flood that had been stored inside. As per his protocols, Spark began to search for a Reclaimer to activate the installation, and came upon UNSC Staff Sergeant Marvin Mobuto. Using the Installation's slipspace translocation grid, Spark brought Mobuto to the Library in an effort to retrieve the Activation Index. Ultimately, the ill-equipped Marine was overwhelmed and killed by the Flood, forcing the Monitor to seek out another Reclaimer. Spark and a squad of Sentinels moved to the Flood containment facility, where they encountered a group of UNSC Marines and John-117, who were battling the Flood. The Monitor recruited the SPARTAN as another Reclaimer, who he quickly teleported to the Library and began guiding to the Index. With superior equipment and training, and despite overwhelming odds, the Master Chief succeeded in retrieving the Index.

Taking the Index for safe keeping, Guilty Spark teleported himself and the Master Chief back to the Control Room. The Monitor explained that activation protocols forbid him from personally uniting the Index with the Core to activate the ring; only a Reclaimer could be permitted to do so. Spark gave John the Index, and urged him to activate the Installation.

However, Cortana appeared and took the Index before it could merge with the Core, and explained to an ignorant John about Halo's purpose. Spark obligingly confirmed this information, claiming that he had believed the Master Chief to have been fully aware of his role and responsibility as a Reclaimer. With the Index in the possession of a hostile AI and protected by a now uncooperative Reclaimer, the Monitor turned the Sentinels against the Master Chief to attempt to retrieve the Index. John and Cortana escaped with the Index, with Spark and his Sentinels in pursuit.

During their escape through the Control Room's adjacent tunnels, Master Chief disabled the three phase pulse generators, forcing their repair and delaying the Installation from firing in the near future. Disappointed, the Monitor followed John-117 and Cortana to the Pillar of Autumn, which they planned to detonate in order to destroy the ring. Intrigued by the abundance of knowledge within the ship's data banks, Spark briefly put aside his concerns for the Installation and began downloading information from the Autumn's computers, being especially interested in the parts pertaining to human history. He then disabled the vessel's automated self-destruct system to preserve the repository of knowledge he had discovered.

Although the warship's engineering room was protected by many Sentinels, the Master Chief was successful in destabilizing the power cores. Realizing the implications of the ship's destruction, the Monitor immediately fled the doomed ring. Moments before the ring was destroyed, the Monitor consoled himself by asserting that he had done his utmost to fulfill his responsibilities. Later upon further reflection, when he was floating through space, Guilty Spark found himself happy as, ultimately, his purpose had been fulfilled: the Reclaimer had indeed succeeded in stopping the outbreak, even if it had been done in an "inelegant" fashion.

Post-activation
"Excellent! I believe I see assistance approaching..."

- 343 Guilty Spark After Halo's destruction, Spark escaped into space, reflecting upon what had happened to both himself and his Installation. He then traveled into a Forerunner gas mining facility in Threshold's atmosphere, whose refitting as a Flood research facility he had overseen eons past. There, he encountered a Covenant artifact retrieval group led by Sesa 'Refumee. After a brief confrontation with several members of the lower castes of the Covenant, a Sangheili recognized him as an "Oracle" and took him to their leader. Spark then proceeded educate these soldiers about the true purpose of Forerunner creations, including the Halo rings. Exposed to the truth, Sesa 'Refumee took a new, critical view on the Great Journey and, gathering other similarly minded Sangheili and Unggoy, founded a new sect that denounced the Prophets and their Great Journey as false. Setting up a base in the gas mine over Threshold, the group would soon be branded as "heretics" by the Hierarchs.

Such a state of affairs could not be tolerated for long by the Covenant and soon action was taken to eliminate the Heretics. This was accomplished quickly and quietly by the Arbiter and a team of special operations troops. In the aftermath, Guilty Spark was captured by Tartarus and given to the Prophets aboard High Charity.



Interrogated by the High Prophets, Guilty Spark revealed the nature of the Installations and the means to employ them, which made the Prophets send the Arbiter to retrieve Installation 05's "Sacred Icon". After it had been obtained, Tartarus took Guilty Spark and the Index to Installation 05’s Control Room, using Miranda Keyes as the new Reclaimer. However, Tartarus grew tired of Guilty Spark's constant warnings. When the Arbiter and Avery Junior Johnson arrived to deactivate the ring, they first questioned Guilty Spark, so that he'd reveal Halo's true purpose. However, the Brutes were too loyal to the Prophets to accept this truth. 343 Guilty Spark escaped Tartarus' clutches and stood by and watched the ensuing struggle, reminded of the one he had witnessed on the Pillar of Autumn.

After Tartarus and his Brute Captains were killed, the control panel for the Installation began to show a holographic display. 343 Guilty Spark translated the display to Johnson, Miranda Keyes, and the Arbiter. The rings were now on standby, meaning they could be activated from the Ark. The Arbiter asked Spark where it was, and he directed them to a specific location, which turned out to be Earth, the human homeworld.

On November 3rd, 2552, Spark was involving with assisting and coordinating efforts with Rtas 'Vadum and the Covenant separatist Fleet of Retribution in cleansing the surface of Delta Halo of the Flood while Johnson, Keyes, and the Arbiter traveled back to Earth to warn humanity of the coming invasion. When a single Flood-controlled cruiser escaped containment, seven ships of the Fleet of Retribution gave chase, among them the assault carrier Shadow of Intent.

Earth and the Ark
"John-117"

- 343 Guilty Spark

343 Guilty Spark and the Fleet of Retribution arrived on Earth shortly after a Flood-captured ship crashed in Voi. They had learned that the Flood vessel contained Cortana, last seen trapped on High Charity with the Gravemind. As Master Chief recovered the data module that stored her, Spark arrived in time to assist, destroying a Combat Form about to attack the Chief and attempting to begin repairs on the unstable module. After a tense exchange between the two, they put aside their past and proceeded to bring the device back to the ship, where Spark completed his repairs. It turned out the device did not contain Cortana, but was merely a data core storing a holographic message from the AI. In her message, she claimed she had discovered a way to stop the Flood without activating the other Halo rings. In order to discover the answer, the Chief, Johnson, Keyes and the Arbiter, along with Covenant separatist forces traveled through the recently-opened Portal; Spark joined them.

The fleet followed the Covenant forces through the portal, and arrived at Installation 00 - The Ark. Upon touchdown, Spark sent orders to all Sentinels that the incoming UNSC and separatist forces were allied, thereby preventing the Ark's security systems from turning on them. Searching for Truth's location, the Separatist Sangheili located the Installation's Cartographer. Spark followed the Chief and the Arbiter's platoons to penetrate the wall protecting the location, opening doors and providing Sentinels as backup for the assault. Once the Cartographer was found, Spark used the map system to pinpoint the Prophet of Truth's location several hundred kilometers away, but noted that the location was shielded by an energy barrier. At that moment, a Loyalist Phantom arrived, driving the trio back deeper into the hallways. Spark led them towards Johnson's location a few floors below. After the reunion, Johnson was nervous at the sudden appearance of hundreds of Sentinels, but Spark reassured him they meant no harm and were part of a primary task force, although he couldn't discern their goal.

UNSC and Sangheili forces moved to disable the shield barrier protecting Truth. However, as soon as the barrier was taken down, High Charity suddenly transitioned out of Slipspace above the area, nearly destroying Rtas 'Vadum's ship, and peppered the Ark with Flood dispersal pods and flaming debris. Terrified of a complete Flood takeover, Spark insisted that they focus their attention on the Flood. He was met with opposition from Keyes and the Separatist leaders, who made it clear that their first priority was to kill Truth before moving on to the parasite.

Once the Prophet of Truth was dead and the threat of the Halo Array neutralized, the Flood began their infestation under the command of the Gravemind. Spark met up with the Arbiter and Master Chief after their initial escape, and discovered that the Ark had been constructing a new Halo ring to replace Installation 04. John stated that he planned to fire the ring, and Spark happily set about preparing the ring for activation.

After rescuing Cortana from the Flood-infested High Charity, Master Chief, the Arbiter and Sergeant Major Johnson landed on the newly constructed ring. Spark aided their progress through the Installation by providing Sentinels to combat the Flood. Once the initial wave of Combat and Pure forms were destroyed, Spark opened the main blast door to the Control Room.

Return to Halo
"Unacceptable! Unacceptable! That is absolutely unacceptable! Protocol dictates action! I see now that helping you was wrong! You are a child of my makers, inheritors of all they left behind. You are Forerunner, but this ring... is mine!"

- 343 Guilty Spark turning rampant Spark was reunited with the Chief along with Johnson and the Arbiter in the new Installation 04's control room, where he informed them that the ring was almost complete, but not yet ready to fire. However, despite Spark's panicked warnings that a premature activation would result in the destruction of the Ark (and, more importantly to Spark, the new Halo ring), Johnson ignored him and proceeded to attempt to activate the ring anyway, determined to destroy the Gravemind and the Flood once and for all. Unable to accept that his new installation was about to be destroyed, an enraged Spark fired upon Johnson as he attempted to activate the ring, mortally wounding him. Seeing John run towards his fallen comrade, the Monitor then fired upon him and the Arbiter, knocking the Arbiter out of the room and sealing the door behind him. The Master Chief was left to face the Monitor alone.

With the Chief on the floor with his shields down, Spark declared that he would stop at nothing to follow protocol and ensure the safety of the ring and the Ark. The Chief engaged Spark in combat, but was unable to damage the Monitor's housing. Johnson, burned and bleeding out but still conscious, used his Spartan Laser to blast Spark before he could kill the Chief, cracking his protective casing. Johnson then gave his weapon to John, who fired on Spark repeatedly with the laser. Spark began to malfunction ever more erratically as he took damage, and after three blasts from the Spartan Laser, he finally lost all structural integrity and exploded.

Post Human-Covenant War duplicate
An unknown period of time after the end of the Human-Covenant War, a severely damaged duplicate of Spark was discovered by an ONI research group, who took it aboard their ship. Using an AI translator, the ONI team detected a Covenant language stream within the monitor, suggeting that it may have been in prior contact with the Covenant. After properly calibrating their AI translator, they began to interrogate the duplicate monitor, hoping to gain insight into the ancient human-Forerunner relations and the Didact.

The damaged duplicate, acknowledging the humans as "the true Reclaimers" and claiming that his duty was to eventually testify to Reclaimers when given the opportunity, proceeded to describe the events that led up to his former human self becoming a monitor. Over the course of his narrative, he constantly accessed the ship's information stores, breaching the firewalls without effort, much to the ONI team's dismay. After Spark had finished his story, the monitor finally powered down and was jettisoned into space by order of the ONI team commander. Before this, however, he had successfully managed to upload his data stream into the ship's computers, disabled its AI, and took full control of the ship. Claiming that he knew the Librarian was alive and that he had need for the ship and its crew, Spark put them to sleep and set course to where he believed the Librarian could be found.

Personality and traits
343 Guilty Spark was quirky and very well-humoured, although at the same time detached and analytical. For Spark, protocol dictated all; the slight emotion he showed for the death of an ally was truly grief only for the inconvenience of finding another to assist him. While he gladly assisted those who requested his help, if his allies decided to prevent him from completing necessary actions - such as the firing of his ring - he would turn on them without hesitation and dispatch them with lethal force.

Tens of thousands of years of monotonous duty spent monitoring his Installation and waiting for a Reclaimer appeared to have had an effect on the Monitor's sanity, and it is entirely possible that his long isolation was responsible for his rampancy. Spark showed many characteristics of rampancy. He loved to learn and to take records, even in the face of his Installation's imminent destruction. He also showed other behaviours that seemed to indicate that he was mentally unstable, such as constant, tuneless humming and singing. Typically, he was also unusually untroubled with what was going on around him. When Sesa 'Refumee and Tartarus were killed by the Arbiter, he appeared casual, although he was remorseful when Sesa 'Refumee was killed.

As with UNSC and Covenant artificial intelligences, Guilty Spark's programming prohibited him from carrying out certain actions. He cannot, for example, retrieve the Activation Index from the Library or use it to activate Installation 04, instead requiring a Reclaimer to carry out this task.

Spark's protocol bound him only to contain a Flood outbreak from Installation 04, so when Installation 04 was destroyed, his directives were also terminated. This means that he no longer had a priority prescribing his actions concerning the Flood - he was free to make choices concerning the Flood, as he did on Installation 05 when he assisted in the deactivation of its firing sequence, risking the containment of a flood outbreak. According to Spark, the loss of his ring left him with only one purpose: to aid the Chief as a Reclaimer, which Spark admitted was something he should have done from the beginning instead of trying to hinder him. This caused the two to put aside their differences and Spark to join forces with the Chief again against the Flood and the Covenant. Due to his abilities in connection with the Halo Array, Spark proved to be a powerful ally and seemed to take commands from Commander Keyes, Sergeant Johnson and the Master Chief and follow them without hesitation as part of his new function in life. When he discovered Installation 04B, his priority protocol reactivated, and he adopted the ring as his replacement. When Sgt. Maj. Johnson declared his intent to fire Halo, which would destroy it, Spark unhesitatingly killed him, despite their cooperation on the Ark.<!--

Speculation
There have been many elaborate speculations and analysis made regarding the origin of 343 Guilty Spark's name, history, and motives. The most notable question: what exactly is he "guilty" of? There have been many suggestions towards genocide of some form (one of his primary functions is, after all, initiating the eradication of all sentient life in the galaxy) but an alternate meaning of "spark" is to set in motion/activate, suggesting he is guilty of prematurely activating Halo, which might explain the absence of the Forerunners. However, due to Halo 3's explanation involving Mendicant Bias it's clear that whatever 343 Guilty Spark may or may not have done, he wasn't responsible for the destruction of the Forerunners.

An alternative theory is that the name Guilty Spark was given to monitor 343 when it was commissioned. Since the monitors of both Installation 04 and 05's names begin with words that represent regret in some way, the Forerunners may have named each monitor to describe their sadness due to the failure to contain the Flood through other methods.

In Halo 2, he is no longer an antagonist, but still plays an important role in the plot. In Halo 3, he isn't an antagonist for the majority of the game and assists the UNSC and Elite forces as they explore the Ark with the Sentinels, opening some passageways for them and guiding them. 343 Guilty Spark, is briefly mentioned in Halo 3's terminals as "04-343" (He was the Monitor of the 4th Installation, followed by his call sign, 343), and may have had a role in the previous Flood outbreak and Ring Activation. People are now claiming he "activated" the first Flood outbreak, which is what he is "guilty" of. He may have chosen Guilty Spark for himself, knowing this information. This is supported by his quote in Halo: Combat Evolved, "Last time, you asked me, if it were my choice, would I do it? Having had considerable time to ponder your query, my answer has not changed. There is no choice, we must activate the rings." Considering that until that point, no character in the game except Cortana knew Halo's true purpose; only a Forerunner could have asked Guilty Spark this question. Guilty Spark also had a conversation with Mendicant Bias through one of the terminals in and recognized an alias for the AI, although Guilty Spark claimed he had little or no knowledge of the working of the Ark prior to and after this conversation. Other theories state that Guilty Spark had undergone a similar rampancy as Mendicant Bias had.

It is also possible that, despite all of his knowledge, that 343 Guilty Spark may be the Forerunner equivalent of a UNSC "Dumb" Artificial Intelligence, since he only has his powers on Installation 04, and the fact that he said to the Master Chief when he was trying to recover what he thought was Cortana at the time, but was really a message. When the Chief asked him and the first part of the response was done, he said "You did destroy my Installation. Now I only have one function, to help you, Reclaimer." Since his primary function was destroyed, he could not branch out and learn about how to further his abilities, further increasing the chances that he is a "Dumb" AI, by Forerunner Standards. At the Cartographer, he said "My makers have wisely limited my knowledge of all other strategic facilities." So he may be a Smart AI, but not given the information.

A status report by Guilty Spark in the 2010 reprint of Halo: The Flood raises more questions about his origin. Most of the report is filed in his usual formal and analytic tone; He notes the presence of the various species in stages of post-Array recovery, as well as Reclaimers. He is concerned about the safety of the ring and decides that the adherence to containment protocols must take priority. However, in the latter part of the report, which is written in a more personal manner, he exhibits previously unseen characteristics and reveals new aspects about himself. One of his lines indicates that his task of protecting the Installation was originally taken up by a conscious decision: "Those of us who chose this path all understood it would be this lonely, but not this long." Another quote appears to be even more personal: "I was young when I chose this path and now I am suddenly very, very old. There is no one left to advise me. I will protect our legacy to the best of my ability and to the death, if need be, as I promised when I first took up this mantle." -->

General

 * 343 Guilty Spark was voiced by actor Tim Dadabo.
 * The only person who ever refers to 343 Guilty Spark as "343 Guilty Spark" is himself, when he is introducing himself. Others refer to him as "The Oracle", or "The Monitor" when speaking of him, or even shorten his name to "Spark", or once "Robot", to which 343 Guilty Spark protested against, and also "Tinker Bell" by Avery Johnson in Halo 2 after he asks about where to activate the rings while in standby mode and answered sarcastically. He has also been called "Light bulb" by Johnson in Halo 2 (to Tartarus: "Please...Don't shake the light-bulb.") and Halo 3 ("A tank's a tank, light bulb.").
 * 343 Guilty Spark is the only significant enemy character that appears in person in the last level of each game in the trilogy (excluding cutscenes).
 * After the Halo: Combat Evolved credits, the tune he hums is a portion of the Halo theme. Occasionally, in Halo 3, he will hum some parts of the MJOLNIR Mix.
 * In the cutscenes of Halo 2, when 343 Guilty Spark talks his light glows brighter, but during gameplay in Halo 2 when he talks his light grows dim. This is a programming glitch, where he was supposed to do the opposite, and is referred by Joseph Staten as "the most terrible glitch in Halo 2... and nobody cares about it."
 * In Halo 3, if the player kills his/her fellow Marines or teammates on Co-op, 343 Guilty Spark will sometimes become hostile and fire his laser at the player, and, despite having to fight him while he uses it later on, is much more powerful and can easily kill the player in one hit, even while in a Scorpion Tank.
 * 343 Guilty Spark shoots a beam similar to both the UNSC Spartan Laser and the Forerunner Sentinel Beam. When comparing power through hacking or modding, the beam is noticeably weaker than a Spartan Laser but much stronger than a Sentinel Beam.
 * In the final level of Halo 3, just before 343 Guilty Spark dies, he will make random statements such as Gollum's catchphrase from Lord of the Rings: "My Precious!" This is likely because Halo is also a "ring of great power", just like the Great Ring that Gollum possessed. Other similarities to the Lord of the Rings include that Guilty Spark is an ally for most of the third game, but turns against the main characters at the end, dying to try and stop the protagonists from destroying his beloved ring.
 * Players can gain an Xbox Live Avatar prop representation of 343 Guilty Spark just by using Halo Waypoint on the Xbox 360.
 * The Disembodied Soul, when asked about Guilty Spark, claims that "He's my progeny. He inherited my good looks and pleasant personality."
 * On the Firefight level Installation 04 he can be seen behind a transparent wall in the bunker near the cliff. He will float up to the door backwards and turn around to face outside. When standing in front of him the prompt "Hold x to take ally's..." and the icon for the Focus Rifle appears however you can't actually take it.
 * In Halo: Combat Evolved Anniversary, there is small covering on the top part of his eye. This covering is not present in the original game or in his appearance Halo 2 and Halo 3. It is also not present when he appears in the terminals nor seen on any other installation monitor shown. When it is present it makes him look quite sad or depressed. It is unknown why this change in design was made, although it may hint to his descending rampancy or loneliness.

List of appearances

 * Halo: Combat Evolved
 * Halo: Combat Evolved Anniversary
 * Halo 2
 * Halo 3
 * Halo: The Flood
 * Halo: First Strike
 * Halo: Ghosts of Onyx
 * Halo Legends
 * Origins
 * Halo: Primordium