WINTER CONTINGENCY (protocol): Difference between revisions
From Halopedia, the Halo wiki
No edit summary |
SPARTAN-118 (talk | contribs) (Highly unlikely, Citation Needed.) |
||
| Line 16: | Line 16: | ||
== Priority == | == 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. | 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. | ||
==Sources== | ==Sources== | ||
<references/> | <references/> | ||
[[Category:UNSC Protocols]] | [[Category:UNSC Protocols]] | ||
Revision as of 00:47, August 7, 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.
