WINTER CONTINGENCY (protocol): Difference between revisions
From Halopedia, the Halo wiki
(I've subtly reworded a few lines so they don't read like a blatant copy-paste and have added a disambig for the level.) |
SPARTAN-177 (talk | contribs) No edit summary |
||
| Line 13: | Line 13: | ||
*Detection of multiple in-system [[Slipstream Space|Slipspace]] rupture events. | *Detection of multiple in-system [[Slipstream Space|Slipspace]] rupture events. | ||
*Engagement in combat with Covenant forces. | *Engagement in combat with Covenant forces. | ||
== Priority == | == Priority == | ||
Revision as of 14:22, July 17, 2010
This article is about the emergency plan. For the Halo: Reach level, see Winter Contingency (level).
- "Winter contingency has been declared. All units are mobilized and ready"
- — UNSC operator[1]
WINTER CONTINGENCY is an official United Nations Space Command emergency plan that deals with situations where Covenant forces have become aware of, or are present at, a UNSC colony.[2] It was enacted by the UNSC on March 10, 2526.
Classification
Events which may be classified as WINTER CONTINGENCY include:
- Intercepted Covenant communications that refer to a UNSC colony by name.
- Discovery of hard physical evidence of Covenant activity.
- Abandoned or discarded matériel.
- Residue and/or damage consistent with Directed Energy Weapon usage.
- Detection of multiple in-system Slipspace rupture events.
- Engagement in combat with Covenant forces.
Priority
WINTER CONTINGENCY holds the highest precedence in the OPREP-Γ reporting structure. All other reporting terms such as GOOSE CHASE, SNAKE PIT, et al, while very important, are considered secondary to a WINTER CONTINGENCY report.
