User blog comment:WolfgangBSC/The Random Chat Room/@comment-24142455-20160903232644

Currently wrote a draft for the new "Cole Protocol" based off of the UAC's AI Directives. Spelling errors, lope hole corrections, and constructive criticism would be most appreciated.

-UAC Emergency Priority Order 098831A-1-

This new UAC Directive has been ordered to all members of the UAC to abide by this system to prevent the retrieval of UAC information and equipment.

Admiral Parangosky/Office of Naval Intelligence/Routing Sequence: Hypodermic-FXT-J CODE NAME CLASSIFIED: Pied Piper (Continued from previous page)...

Based on the data recorded over the course of the UAC History, these new protocols must be immediately implemented: .ALL Human vessels fleeing from hostile forces must do so on a randomly generated vector away from UAC core world locations.
 * 1) All UAC and civilian which come in contact with hostile assets must have NAV computer/AI erased--destroyed if necessary--to prevent capture of core world locations, equipment, or data.
 * 1) ONI Section II to immediately begin Slipstream space attenuated broadcast of pre-recorded human carrier signals from antiquity to prevent triangulation of friendly forces.

-Article One-

United Aerospace Command Emergency Priority Order 098831A-1

Encryption Code: Red

Public Key: file/ First light/

From: UNSC/NAVCOM Fleet H.T. Ward

To: ALL UAC PERSONNEL

Subject: General Order 098831A-1 ("The Cole Protocol")

Classification: RESTRICTED (BGX Directive)

The Cole Protocol

To safeguard and protect the Inner Colonies and Earth, all UAC vessels or stations must not be captured with intact navigation databases that may lead hostile forces to human civilian population centers.

If any Hostile forces are detected:


 * 1) Activate selective purge of databases on all ship-based and planetary data networks.


 * 1) Initiate triple-screen check to ensure all data has been erased and all backups neutralized.


 * 1) Execute viral data scavengers (Download from UACTTP://EPWW:COLEPROTOCOL/Virtualscav/fbr.091)


 * 1) If retreating from hostile forces, all ships must enter Slipstream space with randomized vectors NOT directed toward Earth, the Inner Colonies, or any other human population center.


 * 1) In case of imminent capture by Covenant forces and boarders, all UAC ships MUST self-destruct.

-Article Two-

When abandoning a vessel, if Article One cannot be invoked, or can not be completed entirely.

1. The capture of an intact and functioning shipboard Artificial Intelligence is unacceptable

2. Activate selective purge of databases on all ship-based and planetary data networks.

3. Initiate triple-screen check to ensure all data has been erased and all backups neutralized.

4. Execute viral data scavengers

5. Set ship for self destruction with time for all surviving crew members to evacuate if possible.

-Article Three-

For when a UAC warship is within a combat scenario. All orders may be overridden by a Commanding Officer.

1. When a UAC ship is boarded by hostile forces, and Article One or Two cannot be invoked, the shipboard AI can be given the order from the commanding officer to self destruct the ship when 75% of all crew have been captured, killed, or incapacitated.

1b. A Commanding Officer may override the 75% rule should the combat scenario be different.

2. If a UAC ship Artificial Intelligence's security systems are breached and the ship is hacked, the Commanding Officer may purge all systems and shut down the Artificial Intelligence and initiate manual overrides.

3. If a UAC ship's computer security systems are breached and the ship is hacked, the Commanding Officer must purge all systems and shut down Artificial Intelligence and initiate manual overrides.

3b. If a UAC ship's computer or Artificial Intelligence's security systems are breached and the ship is hacked and turned against the UAC, the Commanding Officer can initiate a manual override for disabling all weapon systems, rendering the ship incapable of attack.

3c. Should the manual override be destroyed or disabled, the Commanding Officer may initiate a self destruct sequence by overloading the ship's fusion reactor or slipspace drive.

3d. Should self destruction of the ship's fusion reactors or slipspace drive be unavailable, data purging must be done by any means necessary.

4. If a UAC vessel is incapacitated and damaged beyond repair in the middle of combat, the Commanding Officer may give the order to initiate a self destruct sequence.

4b. If a UAC vessel is incapacitated and damaged beyond repair, and is incapable of initiating its self destruction sequence, then any nearby UAC vessel must destroy it to prevent it from being taken into enemy hands if necessary.

-Article Four-

For the capture or boarding of a hostile ship, attacking forces must

1. Kill, capture, or incapacitate ALL hostile crew.

1b. If hostile crew cannot be eliminated, sealing members off in specific areas can be applied if necessary

2. Purge databases of any hostile artificial intelligence

3. Sterilize all areas of the ship to prevent possible contamination of unknown organisms.

4. Install a certified Infiltration Artificial Intelligence to give manual control to boarding crew.

5. Once hostile craft is secure, the vessel must make a random jump for further examination.

6. Following the jump, all hostile data must be thoroughly examined and stored properly. Any data that may compromise the crew's mission, the captured ship, or friendly forces nearby must be purged from the database.

7. Following the capture of a hostile craft, the vessel must have an IFF tag placed on before heading to UAC controlled space.

7b. No captured hostile craft may be taken to UAC controlled space without an exhaustive search for tracking systems that could lead Hostile forces to UAC bases

Violation of this directive will be considered an act of TREASON and pursuant to UNSC Military law articles JAG 845-P and JAG 7556-L, such violations are punishable by life imprisonment or execution.