|
|
| (22 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| <blockquote>Security SOP covers handling yourself as a security officer. For all Security-related legal matters (such as brigging, warrants, and trials), see [[Judicial Procedures]].</blockquote>
| | == Community Direction Goals: == |
| | Every decision in our community is guided by 3 primary objectives: |
|
| |
|
| === Force Escalation / Use of Force ===
| | # Prioritize the safety, consent, comfort, and agency of all of our players above all else, and in that order. |
| This simple, short chart dictates how to proceed with a general arrest. However, depending on what the individual encounters at the station, you can escalate it as needed. You utilize '''Force Escalation''' and '''Rules of Engagement''' hand-in-hand.
| | # Encourage meaningful and enjoyable collaborative roleplay. |
| | # Provide interesting and ever-growing content to explore and engage with, as long as it supports the previous two objectives. |
| | Secondary objectives that we strive to fulfill when possible: |
|
| |
|
| '''Verbal Commands -> Non-Lethal Methods of Apprehension -> Lethal Methods of Apprehension'''
| | # Keep the out-of-character atmosphere harmonious and cooperative. |
| | # Give players as much in-character agency as possible, to pursue the roleplay and activity that they are interested in. |
| | # Make station roles mechanically interesting, but easy and convenient enough for most players to spend much of the round roleplaying. |
|
| |
|
| It would be best if you prioritized initiating by declaring an order, i.e.: "Stop!" "Stop, or I will shoot you!" "Hey! Stop moving!" Any of these methods will allow you to upgrade your Force Escalation higher on the scale as you move up non-lethal methods (baton, disabler, rubber-tipped munitions). However, not all situations are perfect; sometimes you have to act before you speak.
| | == Community Direction Process: == |
| | Any decision that will have any significant change on the server or community, whether through policy, rules, or content additions or alterations, is discussed by everyone with the Direction Staff role. This includes all Owners, Head Admins, and our System Admin. |
|
| |
|
| ==== Use of Force Additions ====
| | After discussion and reaching a majority consensus, the change will either be approved for implementation when ready or denied. We often come to some form of compromise if the vote was not initially unanimous. Community feedback is welcome and always considered during this process, but the decision is ultimately based on if it fits the goals for the server. |
| To be used when you have exhausted your baton's charges or disabler shots. This does not mean you should take out your knife or utilize a powered-down baton to apprehend someone. You can use your '''Flash''', or '''Flashbang grenades'''. You ''may'' upgrade to using your MK58 with '''Rubber-Tipped Munitions''' when the situation is still not contained. Additional apprehension or dispersal tools can be used, such as '''Stingers''', '''Truncheons''', and '''Tear Gas'''.
| |
|
| |
|
| === Rules of Engagement ===
| | Minor changes are often quickly discussed and approved by majority consensus of currently online/available Direction Staff before being implemented/merged, rather than the whole team, but are subject to revision if there is later disagreement. |
| Security personnel hold unrestricted armaments licenses under Tier 2. They, alongside the Captain or the Blueshield Officer, are authorized at all times '''''to use lethal force to the extent necessary''''' to '''''neutralize''''' adversaries under any of the following circumstances:<blockquote>If the adversary exhibits a clear and present danger to the vessel by physical means.
| |
|
| |
|
| If the adversary poses a significant threat of severe bodily injury or death to the officer or others.
| | Any member of the community may pose a question to the Direction Staff team in the Direction Questions section of the Discord server. It is recommended to do this before submitting PRs with major content additions/changes. Any member of the community may also make suggestions in the suggestions forum on our Discord. This space is closely watched by staff and contributors, who may decide to devote time to implementing suggestions made there. |
| | |
| If the adversary presents an existential threat to the chain of command by illegal means.
| |
| | |
| If the adversary cannot be reasonably subdued through non-lethal means without great bodily harm to the officer; wherein an “adversary” is an entity that demonstrates a hostile intent, commits or directly contributes to a hostile act that does not constitute an actual attack, or is actively attacking the vessel or its crew.</blockquote>
| |
| | |
| === Search & Seizure ===
| |
| You '''''must''''' search and seize any object that is believed to be used in the commission of the crime. However, one should not ''seize'' non-NT-aligned objects, such as non-standard branded clothing and paraphernalia, that pose little risk. It should be removed from the person, placed in an evidence locker, and returned to them. Any ''contraband,'' as defined under the Contraband List, ''shall'' be seized from the individual.<blockquote>You may not confiscate PDAs or IDs without evidence beyond a shadow of a doubt that a crime was committed ''using'' their PDA. In general, if you confiscate it, have evidence beyond a shadow of a doubt, including for thieving gloves.</blockquote>
| |
| | |
| === Reasonable Suspicion ===
| |
| A security officer may detain someone for a short period of time if they reasonably believe the person is committing, involved in committing, or conspiring to commit a crime. They may only search the individual with an approved search warrant (unless given written consent, [https://wiki.denstation.net/index.php?title=Judicial_Procedures#Individual_Search as detailed here]); therefore, we recommend that officers procure such a warrant before detaining said individual. Additionally, if the detained individual is found in possession of any illegal items and is charged, the time spent detained will be deducted from the total brig time. The need for a warrant is waived during Blue Alert or more severe alert levels or if they are under arrest. Three example scenarios of Reasonable Suspicion would be, but not limited to:<blockquote>A. The security officer receives reasonable reports of someone with a lethal weapon.
| |
| | |
| B. The security officer spots someone with an otherwise unusual or suspicious item: (chief examples of this not covered above would be makeshift cuffs & unpermitted clothing, such as command uniforms)
| |
| | |
| C. The security officer observes someone acting out-of-ordinary or obscuring their identifiable features around restricted areas or scenes of crime, fleeing unusually from the crime scene, or fitting the description presented at the scene of a crime set by fellow officers or witnesses</blockquote>
| |
| | |
| === Probable Cause ===
| |
| Probable Cause is an escalation of Reasonable Suspicion, wherein the security officer obtains sufficient and near-irrefutable evidence to support that someone is involved in or going to be involved in committing a criminal act. Often, this requires the officer's direct view. During green alert an approved arrest warrant is needed to legally enter departments to effect an arrest unless actively pursuing or entry is permitted by the head of the department or the captain. Three example scenarios of Probable Cause would be, but not limited to:<blockquote>A. The security officer undeniably spots someone quickly pull out a lethal, non-permitted weapon.
| |
| | |
| B. The security officer watches someone flee from an area with stolen items.
| |
| | |
| C. The security officer sees someone breaking open an area in which they are restricted from accessing.</blockquote>
| |
| | |
| === Arrest and Sentencing ===
| |
| A security officer who has probable cause or evidence of a crime may enact an arrest. The arrested individual should be promptly charged and sentenced, in accordance with [[Space Law#Charges by Definition|space law]], [[Judicial Procedures#Sentencing|sentencing procedure]], and [[Judicial Procedures#Pressing Charges|procedures for pressing charges]].
| |
| | |
| The arresting officer, warden, or head of security may choose to reduce punishment to a warning and/or confiscation of contraband in the case of misdemeanor crimes.
| |
| | |
| === Detainment versus Arrest ===
| |
| | |
| ==== Detainment: Stop & Frisk, Free to Go ====
| |
| When an individual is detained, at the officer's discretion, the individual can be cuffed for officer safety. Thus, the officer can do their job in a search (frisk). You may do this at any time during blue or higher alert level, or with a approved search warrant on green alert, citing your '''''Reasonable Suspicion''''' on the warrant.
| |
| | |
| This means a pat-down, which involves checking their '''bag''', '''pockets''', and '''jacket/coat/overalls,''' but not other clothing, for anything related to Chameleon Technology or similar. If evidence of holofibers are found on the aforementioned clothing, search all personal effects for further evidence. As Security, the officer shall not maliciously repeatedly detain someone. | |
| | |
| If nothing is concealed on the individual that would constitute '''Contraband''', you are still detained until security lets you go. However, if Security has been called away, and they don't verbally express that you are free to go, the detainment is void and you are free to go. The officer must be physically present to enact the detainment.
| |
| | |
| ==== Arrest: Contraband Found ====
| |
| If something on the individual that is considered '''Contraband''', it will become an '''arrest''', and said individual will be sent to the Brig for the applicable charges; additionally ensure they are searched again before being placed in the Brig.
| |
| | |
| === Fleeing Individual ===
| |
| When Security is enacting a detainment to possibly arrest a wanted person, and the individual begins to '''flee''', Security can utilize ranged non-lethal apprehension methods.
| |
| | |
| There '''must''' be probable cause to utilize Lethal Force if the officer can articulate that the fleeing individual will cause serious harm to the officers, station, and/or crew at large, or has continually slipped out of cuffs, or has readily escaped their Brig cell.
| |
| | |
| === Armory Procedure ===
| |
| When on station, the Warden is ultimately responsible for stocking the armoury and distributing and recording the collection of weapons. However, if they are absent, it falls on the Head of Security.
| |
| | |
| Standard armament of a security personnel under green alert conditions should include one kinetic sidearm with adequate ammunition, one energy sidearm, one stun baton, and one melee weapon.
| |
| | |
| Under normal conditions, the distribution of weapons and munitions ''must'' follow [[Security Standard Operating Procedures#Force Escalation / Use of Force|Force Escalation]], [[Security Standard Operating Procedures#Rules of Engagement|Rules of Engagement]], and [[Alert Procedure]]. Once the threat is dealt with, the Warden or Head of Security shall issue a recall for all weapons to be returned, and a restock should be in order. '''Non-Crew''' shall ''not'' be issued weapons from the armoury.
| |
| | |
| Hardsuits may be issued and worn at any alert level, but given that they impede mobility, it is recommended to only wear them when necessary.
| |
| | |
| The Warden and Head of Security are permitted to carry one lethal longarm on any alert level, at their discretion. Concealment of the weapon is encouraged on lower alert levels but not required.
| |
| | |
| ==== Conditional Situations ====
| |
| When deemed appropriate by the Warden, Head of Security, or Commanding Officer, lethal longarms may be temporarily issued on lower alert levels to accomplish specific tasks. A common example would be distributing laser rifles on green alert while dealing with an incursion of hostile fauna.
| |
| | |
| In the case of dire emergencies, such as most of security being incapacitated during a red alert, non-security crew may be deputized and armed with security weaponry and armor. This should only be done at the discretion of the Head of Security or Commanding Officer. If they are incapacitated or absent, other station command may authorize deputizing the crew.
| |
| | |
| ===Specialized Roles===
| |
| Certain roles can be prone to multiple SOPs at once, due to being related to multiple departments. The [[Corpsman]] is an example of this. Their dedicated SOP can be found in [[Specialization Operating Procedures]].
| |
Every decision in our community is guided by 3 primary objectives:
- Prioritize the safety, consent, comfort, and agency of all of our players above all else, and in that order.
- Encourage meaningful and enjoyable collaborative roleplay.
- Provide interesting and ever-growing content to explore and engage with, as long as it supports the previous two objectives.
Secondary objectives that we strive to fulfill when possible:
- Keep the out-of-character atmosphere harmonious and cooperative.
- Give players as much in-character agency as possible, to pursue the roleplay and activity that they are interested in.
- Make station roles mechanically interesting, but easy and convenient enough for most players to spend much of the round roleplaying.
Any decision that will have any significant change on the server or community, whether through policy, rules, or content additions or alterations, is discussed by everyone with the Direction Staff role. This includes all Owners, Head Admins, and our System Admin.
After discussion and reaching a majority consensus, the change will either be approved for implementation when ready or denied. We often come to some form of compromise if the vote was not initially unanimous. Community feedback is welcome and always considered during this process, but the decision is ultimately based on if it fits the goals for the server.
Minor changes are often quickly discussed and approved by majority consensus of currently online/available Direction Staff before being implemented/merged, rather than the whole team, but are subject to revision if there is later disagreement.
Any member of the community may pose a question to the Direction Staff team in the Direction Questions section of the Discord server. It is recommended to do this before submitting PRs with major content additions/changes. Any member of the community may also make suggestions in the suggestions forum on our Discord. This space is closely watched by staff and contributors, who may decide to devote time to implementing suggestions made there.
