WINTER CONTINGENCY (protocol): Difference between revisions

From Halopedia, the Halo wiki

mNo edit summary
Line 14: Line 14:


==Trivia==
==Trivia==
*This term is a report that has the highest precedence in the OPREP-Γ reporting structure. All other reporting terms such as GOOSE CHASE, SNAKE PIT, et al, while very important, should be considered secondary to this report.
*The term WINTER CONTINGENCY is a report with 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 10:06, July 9, 2010

Template:Ratings

"Winter contingency has been declared. All units are mobilized and ready"
— UNSC Operator[1]

WINTER CONTINGENCY is an official UNSC emergency plan that deals with situation where Covenant forces became 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 WINTER CONTINGENCY include:

  • Intercepted Covenant communications that refer to a UNSC Colony by name.
  • Discovery of hard physical evidence of Covenant activity.
  • Detection of multiple in-system Slipstream Space rupture events.
  • Engaged in combat by Covenant forces.

Trivia

  • The term WINTER CONTINGENCY is a report with 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