Citadel Station
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    ###### tags: `Admin` # Standard Operating Procedures ## Disclaimer: This is under construction and is subject to change at any time. ## Foreword SoP is an IC document first and foremost, a guideline for most jobs to adhere to where reasonable and for heads of staff to use as a guiding principle in decisions. It is **not** OOC rules, and will not be enforced to the letter. If you find yourself consistently in breach of this, you may get into trouble for it - especially if your action derail the quality of rounds you participate in, or if you cause trouble for others. Security and command should especially pay heed to this, but even for them, this is **not absolute.** We do not expect everyone to behave all the time. Be reasonable, and things will turn out fine. **Organic, IC solutions to conflict is always preferred over warnings, notes, and bans. Do not abuse this. If you have to quote any of this at an admin, you are likely already in the wrong.** ## Organization This document does not yet contain the "usual" emergency response text to different events, e.g. blobs, meteors, etc that other servers have. Currently, it only contains guidelines for how departments should be operated. --- # Alert Levels - should we implement violet and yellow alerts for medical and engineering emergencies? also a maintainer question i suppose. might be too complicated, might not. - do we really want to implement something like a suit sensor policy because i can see that either being ignored (probably for the better??) or going really, really, really wrong with draconian enforcement from powergaming sec/command. with how the code works now, suit sensors are extremely powerful. (Justin) I vote against a suit sensor policy because you can 100% have people metagame "X doesn't have their suit sensors on, they're a badguy", which has happened, and will happen. (R) +1 ### Definitions Crew guidelines are applied in this order: Green --> Blue --> Amber --> Red. This means that things are overridden in that order; If something is not specifically overridden, it defaults to the lower standard. ### Green ### Usage All clear; No major threats to the station, as defined by departments able to deal with any problems with "routine" procedures, whether security or otherwise. #### Crew guidelines ##### Security -All searches must have reasonable cause and may need to be cleared by the Head of Security or Warden, if either is present. Security is not allowed to have weapons visible without cause. ##### General - Crew movement is not restricted. Standard access/trespassing regulations obviously apply. Suit sensors are not mandatory -- WIP ### Blue #### Usage **Reasonable** and likely suspicion of threat to station operation, general unrest, *or* situation which requires high utilization of certain departments to resolve. May use instead of amber during confirmed threat if it is able to be resolved with routine measures without danger. (? is this a good idea?) ##### Security -Type of searches at this point? >Search with probable cause or suspicion w/ Superior's Permission. >Pat-down search (restricted to pockets) w/o Permission >Security may have guns visible, but are cautioned from carrying them. #### Crew guidelines ### Amber #### Usage Confirmed threat to station, or multiple factors of Blue Alert in play at once, or or/any situation requiring an elevated security response. #### Examples - Syndicate infiltrators, minor changeling presence, confirmed vampire, etc. If situation starts to spiral out of hand, elevate to red. - Non-emergency but highly contagious viral outbreak - Multiple hull breaches from meteors - Mass power grid failure without loss or threat of loss of life. - Unavoidable Delamination #### Crew guidelines ### Red #### Usage Major threat to station, or confirmed threat is external (e.g. hostile/armed boarders), security emergency, or any situation where station integrity/function is under severe threat. #### Examples: - Hostile boarders - Large bombs, catastrophic meteor storms, or any other situation where significant hull integrity or life support are severely compromised - Lethal and uncontained viral outbreak - Armed and dangerous criminals unable to be raesonably contained by security in a timely manner. (wikilink: gang war) (see: "syndicate agents, changelings, vampires that spiral out of hand") - Mass mutiny (wikilink: revolution) - Hostile paracausal incursion (wikilink: wizard, cult) - Major atmospherics contamination (Plasma flood) #### Crew guidelines ##### Security - Not required to follow arrest guidelines, however priorities are still nonlethal detainment when in conflict with Nanotrasen crewmembers if reasonable to do so. (???) - Searches are permitted **for any reason.** (???) - Weapons are allowed to be openly carried or held. (Not that holding weapons in hand is particularly recommended) ##### Command - The usage of departmental lockdowns is recommended **where appropriate.** ##### General - **All crew should remain inside their departments, within reason and without a reason to not do so.** (? is this a good idea?). This is enforceable by security if activities in public spaces are disruptive, up to and including detention until cooperation. - Any non-hallway public area is considered acceptable for those without a proper departmental space. Non essential departmental staff may also congregate there unless ordered otherwise by any member of command or security. - Crew should not be in maintenance shafts without good reason. - All crew **must** respond to location inquiries by their department head, or, if none exists, any member of command or security. ### Delta #### Usage Not triggerable by station crew at the moment. Generally means the station is under imminent threat of destruction. #### Crew guidelines - Listen to command and security - **Command staff, and, by extension, security, are authorized to reserve station life and integrity with *any means necessary*!** ## Departmental - After reading Paradise's SoP I'd .. rather keep ours as short as possible. Maybe a set of guidelines rather than exhaustive and overcomplicated procedures to fit our server? - And yes, easier said than done! ### Command ### Engineering ### Security #### Arrest Procedures - so who wants to open the can of worms on shoot first ask later vs ask first get shot by traitor mcrevolverocelot? #### Use of Force - **Nonlethal detainment is to be expected in general.** - **Lethal force** - **USE COMMON SENSE.** "May" does not translate to "100% of the time with no exception." If someone agrees to surrender, I'm sure it doesn't have to be said to not shotgun them. - This means if they are downed from lethal force and can be **reasonably and safely detained**, DO SO. Lethal force is not the same as shoot until dead. - **Raiding the armory:** Anyone breaking into, out of, trespassing in, stealing from, or having already broken out of after stealing weapons from the armory may be dealt with using lethal force for whatever reason. (Justin: This sentence is /fucked/) - **Space Threats:** Anyone actively attacking the station from space, or darting in and out of space to flee from security, or any threats that are encountered in space, may be dealt with using lethal force for whatever reason. - **Anyone breaking out of or into the security department proper (brig, etc)** may be dealt with using lethal force **after non-lethal detainment methods fail.** - **Anyone, or in some cases, any entity unable to be detained with nonlethal methods reasonably available may be dealt with using lethal force.** - This means it is not reasonable and safe to nonlethally detain them. - This is not an excuse to be lazy. - **Hostile and/or armed non-crew individuals may be detained with lethal force.** - **Immediate danger to life:** If an officer or other crewmember will be at severe risk of death without the application of lethal force, it is permitted to do so. - Examples: - Someone shooting a lethal weapon at an officer who cannot be properly detained without lethalling back. - Multiple people applying lethal force to an officer. - Armed mutinies - Extraordinary situations as permitted by the Warden/HoS/Captain if one is available. #### Sentencing See: Space Law (wikilink: Space Law) #### Brig Procedures - Prisoners are to be stripped of anything **reasonably usable** as a weapon or escape tool - A toolbelt, yes. - Necessary internals? **NO.** - Knives, highly damaging weapons, yes. - Their backpacks if it contains anything usable to escape? Probably. - Their headsets and PDAs? **NO.** - *Prescription glasses?* - If convicted of a violent crime, prisoners are recommended to be put in the cell while still cuffed, their gear confiscated, and then uncuffed and flashed if necessary after being buckled to the bed as the officer is leaving. - **Prisoners are never to be buckle-cuffed during their sentence** - This guideline is waived if they attempt to break out of their cell. - **Prisoners are never to be denied headset, PDA, or other communications devices unless they attempt to facilitate escape or slander the security team.** - Example: Ordering the AI to let them out of a fair sentence - Example: Screaming SHITCURITY!! over the radio, lying about being harmbatonned or mistreatment in general in an attempt to rouse unrest - NOT AN EXAMPLE: Yelling for help when in danger if the security team is unable to mitigate said danger. This includes if an officer actually harmbatons them, as an example. - Prisoners are not to be fullstripped of their regular clothes (searching is permitted) unless they are in for a long (>= 10 minutes) sentence. - Explain how Brig sentences can be escalated to Permabrig ones, such as in EOC or highly combative or otherwise violent cases. ~~Also touch on Changelings, briefly?~~ #### Permabrig procedures - [High Prio] Define treatment requirements for EOC. - Medical treatment requirements - How, where and when to be treated. Should EOC be cloned in the event of their death, either at the hands of NT or outside forces. - If medical treatment should be applied at all. Violent prisoners obviously need to be sedated to be treated. - General requirements - How food and other necessities should be supplied, when necessary. Dwarves need alcohol, plasmemes need plasma, etc. Worth including conditions for visitors and sanctioned parole. (No gay baby jailing plz) ### Science ### Engineering - Prioritize engine types for stations with multiple engine types. TEG > Supermatter > Tesla > Singulo > Turbine where available. Explicitly state not to order a new engine. - Priotity of tasks; Engine > Solars > Asteroid Shield > Whatever - Procedures for engine failure (Singloose, Tesloose, Delamination) - Utility of Solars and Turbine until Shuttle can arrive - Determining whether situations can be Salvaged - Making sure it doesn't happen again - General voltage requirements for main circuit, as well as recommended voltages for SMES and hazards against wiring Engine directly into Grid. - How to deal with a power sink(?) - Emphasize SMES not just being set to maximum output. Some discourse on limiting output to grid requirement. ### Atmospherics - Prioritize roles; Atmos exists as the fire brigade as well as the air/space hull integrity department. - Procedures for atmos contamination; - Local solutions, such as air scrubbers, air pumps, holo airlocks - Alternatives, like the Large scrubbers from science and venting unsalvagable situations to space. - Macro solutions like turning off plasma input valves, turning on the loop's waste valve or using a Cooler to reduce volume in waste pipe. ### Medbay - Might be messy but worth getting into 'triage/treatment priority' though it might go above the head of some players.(Big Maybe) - Code : Red - Patients who are severely wounded and cannot walk or act or speak. Highest priority, as these are the patients who can live or die in moments. Organ damage, extreme exsanguination, threatening toxins. - Code : Yellow - Concious and could, theoretically, survive waiting an hour. Any patient that can talk or move around on their own. Patients that are bleeing out but concious fall under this category, though can move into Red. Inflamed appendix, bleeding, in shock, moderate radiation. - Code : Green - Any patient that doesn't have any likelyhood of deteriorating or has low chance of doing so. Someone with 80 burn damage or a broken limb/bone. - Code : Black - Any patient that's dead or nearly dead. Lowest priority. Patients that can't be saved, and would either need to be cloned or already need to be defibbed, anyway. Major organ failure and gentic damage could fall into this category, but DEAD PEOPLE ARE LESS IMPORTANT THAN DYING PEOPLE. - Include procedures for dealing with each Code! Black and Red will survive on ice (cryo) but die otherwise. - How to address violent patients/EOC patients and when to call security. - Expand on Role of the CMO in the day-to-day. Meant to be the most competent doctor on the floor. - Address rights of the crew/players, being able to ask the CMO for a 'second opinion' and slip away from incompetent doctors and have security intervene otherwise. ### Supply - Define limitations of 'stockpiling' and hoarding. While it's expected Cargo may want to stock up on materials beforehand, they shouldn't be ordering 30 crates of Isulated Gloves 'because lol'. - Figure out where the authority of the QM ends and the authority of the HOP starts, in regards to cargonia. - Add conditions for using MULEs, since Disposals shipping is usually quicker, safer and less annoying(?) -~~Emphasize paperwork?~~ ### Service ### Other/Assistants - Try not to get in the way. ## Situational Response Guidelines **Command staff are recommended to adjust to the particular context of a situation as necessary.** ### Disease Outbreak - A disease outbreak is defined by a disease being uncontrollably transmitted amongst the crew. - All infected staff are to report to medbay for treatment. - Medical staff are required to wear gear protective against biohazardous agents - Forceful quarantine may be permitted if disease is lethal. - Elevate code accordingly if necessary. - **If disease is considered extremely disabling, or, lethal, all staff are to isolate themselves and avoid contact with other crewmembers. The enactment of a stationwide quarantine is recommended.** ### h3### - We can fill *most* of this out later, just babble like "oh go to the inside of the station during a meteor storm" "go hide in maint in a radstorm"

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully