Protest regulations

src/design-proposals/Protest-regulations.md

@@ -0,0 +1,103 @@
+# Protest/riot regulations
+
+| Designers | Implemented | GitHub Links |
+|---|---|---|
+| IdemFromidemland | :x: No | TBD |
+
+
+## Overview
+
+This design document aims to add new regulations that concern protests, riots and even revolts. As there it is likely we will see more protests with the addition of unions into forky it is good to ensure security has in character regulations and protocols to deal with these.
+
+## Background
+
+Although these regulations cover more than protests it will be named "Protest Regulations" as an all incompassing term including protests, riots and if anarchy breaks out revolts.
+
+The following protest regulations consist of three things which will each have their own seperate section in this document, however Protest protocols and Riot protocols will be in the same guidebook entry under the Security Training Manual. The revolt protocol will be put as it's own guidebook entry under Captain SOP
+
+
+#### Protest protocols
+
+Important definitions:
+
+> Protest: A non violent gathering of people, usually protesting something that has or will occur.
+> Unlawful assembly: An unlawful gathering of people.
+> Non-harmful crowd control measures: Crowd control measures that do not cause permanent damage such as tear gas grenades, flashes and pepper spray.
+> Ranking security member on scene: The security member of the highest rank that is currently assigned to the scene, ranking from the Head of Security, Warden and if neither of these are present any security officer. It should be clearly communicated who is the ranking officer on scene.
+
+In the scenario that a protest occurs security is to ensure it does not get out of hand by peacefully observing it.
+
+in the scenario that a protest impedes station function the ranking security member on scene may declare it an unlawful assembly, this should be done by using the following steps: 
+1. Radio and prepare your fellow officers that you are about to declare an unlawful assembly.
+2. Clearly and loudly announce that the assembly is hereby declared unlawful, It is adviced this is also announced on an announcement console.
+3. Inform the now unlawful assembly members to disperse and give them reasonable time to do so.
+
+If all of the above steps above are followed and a reasonable timeframe has passed to allow the members of the unlawful assembly to desperse and said members have not dispersed the ranking officer on scene may authorize the deployment of Non-harmful crowd control measures.
+
+
+#### Riot protocols
+
+Important Definitions:
+
+> Riot: A gathering of uncontrolled people that may pose a danger to others.
+> Less-than-lethal crowd control measures: Measures that may cause harm but are not explicitedly lethal such as nightsticks, stinger grenades and flashbangs.
+
+Riots may be declared by the ranking officer on scene if one of the following conditions are met: 
+A. After declaring an unlawful assembly the assembly fails to disperse
+B. A protest turns violent, for example protestors start shoving and or punching officers.
+
+If either of these conditions are met the following steps should be followed by the ranking officer on scene to declare a riot:
+1. Communicate with other officers you are about declare a riot.
+2. Request any available officers to your location.
+3. Loudly and clearly announce to the members of the unlawful assembly that this is hereby declared a riot and appropriate force will be used to quell it. It is HEAVILY suggested this is also announced via a communications console.
+
+If the riot has been officially declared all available officers are required to move and assist with it.
+Security should not arm themselves with lethal weapons but should equip riot suits and other appropriate equipment.
+The ranking officers on scene may authorize the usage of Less-than-lethal crowd control measures.
+All members of the riot may be arrested for rioting and it's leaders should be arrested for inciting a riot.
+
+
+
+
+
+
+
+
+#### Revolt protocols
+
+Important definitons
+> Revolt: A station wide movement to overthrow the NanoTrasen command team using force
+> Lethal weaponry: Weaponry that is designed to inflict lethal harm for example a rifle or shrapnel grenade.
+
+In the extreme event of a revolt occuring the captain of the station may declare a revolt in progress if one of the following conditions have been met:
+A. A considerable amount of the crew has taken up arms against NanoTrasen and it's employees
+B. A considerable amount of the crew fails to comply with NanoTrasen or Central Command orders
+C. A declared riot escelates to uncontained violence occuring over multiple parts of the station
+
+If the station's captain wishes to declare a revolt after the aformentioned conditions are met they should follow the folloeing steps:
+1. Communicate with Command and Security about their intend to declare a revolt in progress.
+2. Announce station wide in plain words that they are declaring a Revolt in progress and include in this announcement any revolt orders they may wish to use.
+3. Move the station to the highest alert condition available if not already the case.
+4. Have security equip themselves with lethal weaponry
+
+When a revolt in progress is declared the captain has multiple "Revolt orders" they may use, each are extrondary acts that should only be used in case of dire emergencies.
+
+Martial law: All crew is to report to go into a department, people that do not belong to any department should move to the bar. Anyone who fails to comply with this order may be brigged until martial law is lifted.
+
+Suspension of Standard Operating Procedures: This order suspends all usual SOP to allow security to use any means neccesary to contain and quell the revolt.
+
+Execution of instigators: The captain may decide to authorize the immediate field execution of leaders of the revolt.
+
+
+Revolts mean the total breakdown of public relations, if a revolt is declared maximum force should be used by security to get the crew back in line without care for any public relation actions. 
+
+## Administrative & Server Rule Impact (if applicable)
+
+These changes are unlikely to result in any server rule impacts.
+
+## Technical Considerations
+
+This would purely consist of YAML additions, and this section of the guidebook would be made a child of the Security Training Manual
+
+## Notes
+Please always remember that this entire document is here for feedback and changes, remember to keep feedback constructive!