Alert Level - HackMD

###### tags: `wip` `design-document` # Alert Level Drawing inspiration from [Lockdown Protocols](https://scp-wiki.wikidot.com/lockdown-procedures), we change our Alert Level system to integrate MTF deployment requests and Area/Secure Bunker lockdowns. The new Lockdown system will include: - A new interface in the Command & Control Program, which can generate a Lockdown Response Code. - A specific builder for the LRCs, with the Priority and Threat classification. - Priority will range on a scale of A-C, with response times changing from: - A: Immediate response required, multiple SCPs breached, mass casualty event among the staff, risk of total loss of containment. - B: MTF response required, but limited risk of total loss of containment on the Site. - C: No MTF response required at this time. - MTF deployment will not be automated when priorities A or B are chosen, and Admins will be notified to deploy an MTF if they deem the situation requires it. - Classifications include a range of threats, to inform Site Personnel and responding MTFs as to the risk found at the site, with up to 3 being able to be selected: - Amber: Memetic, infohazardous or cognitohazardous threat (eg, SCP-096). - Blue: Escape of a sentient SCP with intelligence less than humans (eg, SCP-173). - Navy: Escape of a sentient SCP with intelligence equal to humans (eg, SCP-049). - Green: Bio-hazardous threat (eg, SCP-008). - Black: Human threat, external to the site (eg, a GOI platoon assaulting via the surface). - Grey: Human threat, internal to the site (traitors, Class D escape). - Orange: Failure of Site system integrity, such as networked systems, comms or literal structural integrity. - Yellow: SCP breach imminent. - Blank: A threat that either shouldn't or can't be described. - Clear: Set when no current LRC is set, indicates no ongoing threats. - Similar to the current Alert system, the Priority and Classification of the LRC will determine the announcement made to the Site, eg: - 53/A/AMBER: "An infohazardous SCP has escaped containment, posing a risk of total containment loss at Site 53, requiring MTF intervention. Staff are advised to wait for Security personnel to escort them to safety, and to otherwise remain in place, covering your eyes and ears." - 53/C/GREY: "A threat internal to the Site has been confirmed, with Site Security capable of preventing containment loss. Staff are advised to listen to all orders from Security personnel, with SCPs being placed on lockdown and entrances secured." - 53/B/BLACK-BLUE: "A threat external to the Site has been confirmed and a bio-hazardous threat has broken containment, with Site Security likely capable of preventing containment loss, with an MTF deployment requested. Staff are advised to listen to all orders from Security personnel, with SCPs being placed on lockdown and entrances secured, and to avoid contact with any sources of contamination, being aware that a quarantine is likely to be imposed." - 53/C/AMBER-BLUE-GREY: "An infohazardous SCP has escaped containment, a bio-hazardous threat has broken containment and a threat internal to the Site has been confirmed, with Site Security capable of preventing containment loss. Staff are advised to wait for Security personnel to escort them to safety, and to otherwise remain in place, covering your eyes and ears, to avoid contact with any sources of contamination, being aware that a quarantine is likely to be imposed, and to listen to all orders from Security personnel, with SCPs being placed on lockdown and entrances secured." - The format for the Alert message will be, eg: - AMBER: - threattype = "an infohazardous SCP has escaped containment" - threatdescription = "staff are advised to wait for Security personnel to escort them to safety, and to otherwise remain in place, covering your eyes and ears" - Sending an LRC allows for further activating of an Automated Response Initiative, also via the Command & Control app. All lockdowns cannot be overriden without someone of the same or greater Admin access level overriding via the Command & Control app. - ARI-DELTA: Activation of the on-Site nuclear device, provides nuclear codes to the one requesting the ARI, requires two IDs with Admin Access of 5 or above. - ARI-LCZ: Initiates a full lockdown of the LCZ, cannot be overriden from inside the LCZ. - ARI-HCZ: The same, but for the HCZ. - ARI-SITE: Activates the facility lockdown. - Activation of an ARI sends a further message to the facility, eg: - ARI-DELTA: "Lockdown [LRC-CODE] has activated ARI-DELTA. The Site Self Destruct mechanism may be engaged at any time. All staff are advised to obey orders from Security and Class A personnel. Failure to comply can result in immediate termination." - Access of the Command & Control app will need to be modified, so that only people with Admin Level 3 or above can set LRCs, and only those with Admin Level 4 or above can set ARIs. See [Access Refactor](/fJjbQuQTSrSPQphPydyXvQ) for who should have these Access levels. - The full LRC can be seen at any status display, with the color on the edge of the green being determined by the Classification, and the symbol in the center being determined by the Priority. - Activation of the Self Destruct outside of this process will automatically set an alert level of 53/A/GREY, otherwise, when the Self Destruct is activated as a result of ARI-DELTA, it will remain on the previous LRC. - When no LRC is set, the "Code Green" will be 53/C/CLEAR.