TullyBBurnalot

"Non-Hostile"

Following discussion, this happened:

Second one is covered in Sec SOP. First one falls under the "you are expected to know this going in " category.

As it is currently worded, no, Vandalism does not cover killing random animals. It covers Departmental Pets (like Ian, Pun-Pun and Runtime). That said, as Neca mentioned, it would not be difficult to add a "all animals killed" thing to Vandalism.

Nar-Sie Summoning Situational SOP stricken for not being something that Situational SOP should cover. Seriously, its Nar-Sie being summoned. Kiss your ass goodbye.

What it says on the tin. Came out of a discussion on Discord, wanted to see the opinion of everyone on it.

Added: To ERT Crew Procedures. And: To ERT Procedures. NEXT! Very true. Changed to: NEXT! Entire section changed to: Changes in bold

Fucking bees.

THE TIME FOR QUOTE WALLS IS NOW. LINE BEGINS HERE. --- Added: To before Code Green. NEXT! I agree. Changed to: Changes in bold. NEXT! The original intent was to follow suit in the whole "relocation" thing. That said, logistics make this pointless, so stricken. Woops, forgot the Grav Gen. Armory is irrelevant, as it is already locked to hell behind several access-levels and can only normally be accessed via space, unless Security is utterly incompetent. NEXT! As is currently permitted. Basic Decency stops that, however. People can, people still do not. No real need for change there (huzzah!) NEXT! Added. NEXT! Stricken. See above. NEXT! Interesting. Added: And: To Code Blue General Crew. And that rhymes. NEXT! Already covered in Sec SOP. That said, cannot hurt to remind non-Sec of that. Added: To Code Blue, Red and Gamma. NEXT! Stricken. See above. NEXT! This, I maintain is not necessary, as it is already done mainly by the AI on a roundly basis. NEXT! Excellent point. Added: To Code Gamma. NEXT! Love it. Added. NEXT! Removed the "absolutely" from "absolutely necessary". NEXT! Stricken. See above. NEXT! In practice, it is the same thing. I will strike it from the Conditions, however. NEXT! *nod Added: To Code Delta Security. NEXT! If the nuke is armed, odds are you do not have the time to do anything about that, and securing the disk is pointless. Better to cut losses and get everyone out. Praying is a waste of company time and, therefore, company money. You are therefore stealing money from NanoTrasen A Deathsquad (there is no Deathsquad) police team has been dispatched to your location. NEXT! It gets the point across. NEXT! *BANG BANG BANG* NEXT! I have a great idea for this. See the initial post for how it was changed. NEXT! Your pain. It feeds me. Seriously though, stricken, see above. NEXT! Added: Because I am lazy. NEXT! Yes. NEXT! I fear the day we get an ERT that does not know how to click their buttons. Added: *shiver NEXT! Hence me calling it a 7-10 Blob Organism. NEXT! I find your pedantry to be incredibly sexy. Fixed. NEXT! Because I am a nerd and my apostrophe key was broken. Changed. NEXT! Command SOP says otherwise NEXT! Bloody rules lawyers... *grumble Added. Also added the Security Pod Pilot (thanks Pinata). NEXT! I still maintain this is relevant enough to be kept here. I am certain Sec regulars will agree. NEXT! Good point. Added. NEXT! That was the intention. Changed to: Changes in bold. NEXT! ... Meh, sure, why not. Changed to: Changes in bold. NEXT! This should be a given with Space Law, not SOP. NEXT! It happens. NEXT! Added: NEXT! See above, Ruskie. NEXT! Ammended Code Epsilon. Also, Wizards and Blobs are not that exceptional. OSHA inspectors would cry. NEXT! See above. NEXT! Good point. Added: To Code Red and Gamma Secure Areas. COFFEE BREAK! . .. ... .... ..... ...... NEXT! I would rather not add actual round types to "Situational" SOP. That said, considering it is no longer in rotation, how about: NEXT! See above. NEXT! Stricken. See above. NEXT! ... Oh, nothing more. AWESOME.

General SOP will encompass not only the Alert Level system, but also safety regulations and firing/hiring procedures. Enjoy. Foreword: Generally, the Captain or Acting Captain should be in charge of calling/setting Alert Levels. An exception is made for Code Red, where any two members of Command should call it regardless of what the Captain commands, if there is an active emergency. Code Green Status: All Clear Called by: Anyone with Captain-Level Access at a working Communications Console. Conditions: Default Alert Code at the start of the shift. Do not change unless a threat is suspected/confirmed OR All confirmed/suspected threats to the station and/or crew have been handled, or simply vanished on their own. It is recommended that, after 15+ minutes on Code Blue without any hostile activity, Code Green be called Security: All weapons must be holstered or kept in pockets/suit storage slots unless absolutely required; Random searches are not permitted without express permission by either the Head of Security, Captain or Magistrate. However, searches are still permitted if there is reasonable suspicion of a crime Secure Areas: EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used While it is not recommended that Secure Areas be bolted down if unused, it is not prohibited. EVA, in particular, should be left unbolted due to its use by Engineers and Atmospheric Technicians. Exceptions are below; The Gateway is not to be opened without permission from the Captain or Acting Captain; The Vault is not to be opened unless repairs are required, gold is required for Research and Development (in case Mining fails to deliver) or a critical item needs to be hidden in the safe General Crew: While not required, it is recommended that the crew activate and maximize their Suit Sensors, due to the potential for workplace accidents; Free transit through the station is permitted for the crew, outside of Secure Areas Code Blue Status: There is a suspected threat on-board/near the station Called by: Anyone with Captain-Level Access at a working Communications Console. Conditions: There is a suspected threat on-board the station, or at a nearby location in space. This includes any signs of hostile activity that have not caused any damage to station or crew, but nonetheless seem present OR Confirmed Code Red threats have been properly handled or subsided on their own. It is recommended that, after 15+ minutes on Code Red without any hostile activity, Code Blue be called Security: Weapons do not need to be holstered. However, it is recommended that Security personnel follow Security SOP in order to prevent accidents and to be fully aware of armament procedure; Random searches are fully permitted. Security personnel may detain any personnel refusing a random search in order to conduct said search; Secure Areas: EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used It is recommended that all Secure Areas be bolted down unless their use is necessary; Excursions into the Gateway are not recommended, unless they are rescue parties General Crew: All personnel are highly recommended to maximize their Suit Sensors; Personnel are to report any suspicious activity to the nearest member of Security, or use their PDA or Headsets if required; Personnel are highly encouraged to exercise caution, even if the threat is only suspected. Following simple safety procedures (such as not going through Maintenance alone) can prevent needless accidents; Visitors to the station (anyone with Civilian-level access) are recommended to stay in public areas, for their safety Code Red Status: There is a confirmed, hostile threat on-board/near the station Called by: Any two personnel with Command-Level Access, at a Card Swiper. Requires close timing. Condition: There is a confirmed, hostile threat on-board the station or nearby in space. This threat should pose recognizable danger to the station and/or crew at large Security: Security personnel should read Security SOP for armament, armory and safety procedures; Random searches are fully permitted and recommended. Security personnel may detain any personnel refusing a random search in order to conduct said search; Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station Secure Areas: EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used All Secure Areas are to be bolted down. Secure Areas may be left unbolted at the discretion of Command personnel; Excursions into the Gateway are prohibited, unless they are rescue parties General Crew: All personnel are required to maximize their Suit Sensors; All personnel are to remain inside their Departments for the duration of Code Red, unless specifically requested by Security and/or Command; Visitors to the station (anyone with Civilian-level access) are to remain inside the Bar, Library or Dormitories for the duration of Code Red; Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. Failure to do so may lead to their arrest for Creating a Workplace Hazard Code Gamma Status: There is a massive threat to the safety of the station and crew Called by: Central Command. Use a Communications Console or Fax Machine in order to explain the situation. Remember, Gamma is rarely called, for good reason. Having a well-written, concise fax that explains the situation to the best of your ability, as well as why it deserves Code Gamma being called, signed and stamped by the Captain or Acting Captain, goes a long way towards ensuring Gamma is provided. Remember, this is for extreme emergencies only. Conditions: There is a massive threat to the continued safety of the station and crew, threatening the very existence of the Cyberiad; However, this threat is not yet big enough to warrant the destruction of the Cyberiad, and Central Command may still want to protect their assets Security: Martial Law is enacted. Security personnel have full permission to do whatever it takes to ensure that the safety of the station and crew is maintained, up to and including detaining any personnel interfering with emergency procedures; Random searches are fully permitted, allowed and encouraged. Security personnel may detain any personnel refusing a random search in order to conduct said search; Security is to secure the contents of the Gamma Armory and distribute it to Security personnel in order to handle the threat. Non-Security personnel (including members of the Legal Sub-Department) are not to receive these weapons unless necessary; Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station Secure Areas: EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used All Secure Areas are to be bolted down. Secure Areas may be left unbolted at the discretion of Command personnel; Excursions into the Gateway are fully prohibited General Crew: All personnel are required to maximize their Suit Sensors; All personnel are to remain inside their Departments until such a point as Code Gamma has passed, unless specifically requested by Security and/or Command, or their particular skills can help resolve the situation (such as Field Medics or Engineers); Visitors to the station (anyone with Civilian-level access) are to remain inside the Bar, Library or Dormitories until such a point as Code Gamma has passed; Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. Failure to do so may lead to their arrest for Creating a Workplace Hazard Code Delta Status: The station is about to be consumed by nuclear fire Called by: Malfunctioning AI Units, Nuclear Operatives, or the on-board Nuclear Fission Device being activated Conditions: A Malfunctioning AI Unit has dropped all semblance of stealth and activated their Override Mechanism OR The on-board Nuclear Fission Device has been activated by Command or Central Command personnel Security: In the case of a Malfunctioning AI Unit, all Security personnel are required to drop whatever it is they are doing, and proceed to neutralize the AI Unit. Any relevant help from station personnel (such as Engineers or Scientists) is not to be turned down; In the case of Nuclear Operatives, defusing the bomb is not recommended. Security personnel are to escort all other personnel off-station; In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all Security personnel are to stand down Secure Areas: EVA Storage, Tech Storage, Gravity Generator, Engineering Secure Storage, AI Upload, Teleporter, Vault, Gateway, anywhere else requiring a restricted level of access that does not get regularly used Procedures are irrelevant General Crew: In the case of a Malfunctioning AI Unit or Nuclear Operatives, all non-vital personnel are to evacuate off-station immediately; In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all personnel are to stand down Code Epsilon Status: "The hypothetical "Code Epsilon" has somehow persisted in rumors for the past several several years among NanoTrasen crews. For the last time, no, we do not operate "Death Squads", no, we do not suddenly terminate your contracts and send heavily trained mercenaries after you, and no, I do not care what your "buddy in the ERT camp" said. There is no such thing as a Code Epsilon. Now get back to work." - Commodore Martin Treyan, NAS Odin "The NAS Odin has since been stricken from company records. Please do not refer to the NAS Odin" - CEO [REDACTED] Emergency Response Teams Crew Procedures: Emergency Response Teams are only to be called when there is a Code Red-level threat or above; Emergency Response Teams are not to be called concurrently with the NTV Charon (Escape Shuttle). Pick one or the other; Emergency Response Teams are to be called when there is a major emergency aboard the station that the crew does not have the resources to fight properly. This includes, but is not limited to, any hostile threat present without an active Security force, or massive station damage without an active Engineering force; Emergency Response Teams are not to be called without majority approval from Command; Emergency Response Teams officially outrank anyone short of a Central Command Officer. Unless their actions are blatantly illegal and against the best interest of NanoTrasen, the station and its crew, their orders are to be followed above anyone else's Emergency Response Team Procedures: The Emergency Response Team Leader is to ensure that all members of the Team are present before boarding the Cyberiad; The Emergency Response Team Leader is to be considered the top authority inside the Emergency Response Team. Unless their orders are blatantly illegal and against the best interest of NanoTrasen, the station and its crew, they are to be followed above anyone else's; All members of the Emergency Response Team are to activate their helmet cameras (by clicking the button next to their helmet) and maintain open lines of communication between them; The Emergency Response Team is to prioritize whatever it was they were called over. Digressions are not permitted; The Emergency Response Team is to ensure that none of its equipment falls in the hands of either the crew or hostile forcesl NTV Charon --- The Escape Shuttle The NTV Charon is not to be called concurrently with an Emergency Response Team. Pick one or the other; In the event of hostile biohazard lifeforms appearing on the station (such as Xenomorphs or Class 7-10 Blob Organisms), Central Command is to be notified before the NTV Charon is called. Failure to do so may lead to the Charon being recalled in order to enforce quarantine. Similarly, Central Command may prohibit calling the Charon in order to handle the biohazard; In the event that the NTV Charon is called, all personnel are to wrap up their current task and head to the Escape Lobby within, at most, five minutes before departure; Forcing an early departure of the NTV Charon is not permitted unless the structural integrity of the Charon is endangered (such as a nearby Gravitational Singularity, or a Meteor Storm), or the safety of the crew aboard the Charon is threatened (such as nearby hostile Ascendants or Nar-Sie Constructs); All currently brigged personnel are to be kept in the Shuttle Brig; All personnel in critical medical condition are to be kept inside Stasis Bags, or given emergency medical aid Hiring/Transfer Procedures: No new hires or transfers are permitted without contacting the relevant Head of Staff. If one is not available, promoting an Acting Head of Staff is recommended. If none is available, the Head of Personnel/Captain are to utilize their best judgement (see Command SOP for any exceptions); Promotion to Acting Head of Staff requires authorization by the Captain or Acting Captain; The following jobs require permission from Central Command before hiring/transfer is done: Blueshield, NanoTrasen Representative, Magistrate, Security Pod Pilot, Brig Physician, Mechanic and Barber. The same applies to any functionally identical job with another title; All new hires to the Security Department, and Legal Sub-Department, are to be loyalty implanted and fully checked for unauthorized materials or suspicious communications Firing/Demotion Procedures: In the case of a full dismissal, the relevant ID is to be terminated; In the case of a demotion, Civilian-level access is recommended. Alternatively, jobs such as Janitor or Clown may also be used; No dismissals or demotions are to be performed without authorization from the relevant Head of Staff or Captain. See Chain of Command for how to handle dismissing a member of Command; Personnel are to report to the Head of Personnel for dismissal/demotion. Failure to do so will lead to Security detaining them forcefully; After a legal dismissal/demotion order is given to the person dismissed/demoted (e.g: by radio), any activity inside the previously assigned Department is to be considered Trespassing/Major Trespassing, and any item kept from said Department is to be considered Petty Theft/Theft. It is, as such, highly recommended that dismissed/demoted personnel willingly turn in all restricted items and cooperate with the process if they wish to avoid being brigged Causes for Dismissal: Refer to the above for dismissal authority. Ultimately, the decision to fire/demote any personnel falls to the relevant Head of Staff or Captain. This is merely a list of reasons to fire someone over. Any medium-severe breach of Standard Operating Procedure without proper cause; Any medium crime or higher; Critical incompetence at a given job; Refusal to follow legal and relevant orders by the respective Head of Staff. Legality and relevance of said orders are to be judged by the Captain or Head of Personnel; Creation of an abusive and/or unsafe work environment. Personnel consistently berating, insulting, belittling, or otherwise treating their coworkers like dirt, should be immediately disciplined Situational SOP Defined as any situation that falls so far out of conventional operation, that special procedures must be drawn up for it. Fires/Gas Spills All personnel are to vacate the affected area; Hazard Lock systems are to be left untouched. Deliberately opening Hazard Locks during a Fire/Gas Spill in order to open way to the Hazard is to be considered Sabotage/Grand Sabotage; Engineering and Atmospherics personnel are to restore the affected area to working and livable condition Meteor Storm Personnel are to head to the Central Primary Hallway for the duration of the storm; No repair activities are to be performed until the end of the storm, for safety reasons; All personnel performing EVA duty are to return to the station post haste; In the case of a short storm, Engineering is to repair any damage done ASAP; In the case of a prolonged storm, no repair activities on non-critical components are to be performed. Personnel are to remain in the Central Primary Hallway, and all efforts focused on maintaining the integrity of the area. The NTV Charon is to be called when possible (at the discretion of Command), and an early launch is permitted Singularity Containment Failure Gravitational Singularity is to be tracked at all costs. If the Gravitational Singularity heads towards the main station, the NTV Charon is to be called. If the Gravitational Singularity heads off-station, damage done to the station should be taken into consideration. See below; In the case of massive station damage, the NTV Charon is to be called; In the case of light-medium station damage, an ERT is recommended, or, in the case of a competent Engineering team, merely extensive repairs Tesla Containment Failure The Tesla Matrix is to be tracked at all costs, and its current location announced to the crew; If the Tesla Matrix remains inside the Cyberiad rather than arcing into space, the Charon is to be called Supermatter Delamination Event The Supermatter Crystal is to be vented to space; In such a case as the Supermatter Crystal containment was not equipped with a way to space the Crystal, the area around the Crystal is to be evacuated, and all personnel involved in the construction fired and brigged for Sabotage Syndicate Declaration of War All weapons restrictions are lifted. Beepsky, and any other Security Bots, should have their protocols updated to reflect this; Supply should focus on requesting as many weapons as possible. Security is to be prioritized for distribution, but regular personnel may also be armed; Research and Development is to be manned. This is not negotiable. Science should work in tandem with Mining in order to fabricate weapons and equipment to fight the Syndicate Attack Team; Erecting barricades in critical locations is highly recommended; The NTV Charon may be called at the discretion of Command. If the station is not damaged after the fighting has subsided, it is recommended that the crew finish the shift Confirmed Revolution All personnel are to comply with orders from Security personnel, so long as said orders are lawful. Failure to do so is grounds for detainment and inspection of possessions, as well as possible Loyalty Implantation, at the discretion of the Head of Security, or Acting Head of Security; All personnel that are brigged for Medium Crimes or higher are to receive Loyalty Implantation. Similarly, if the number of active revolutionaries is more than twice the number of loyalists, the Head of Security or Acting Head of Security may order random implantation of crew members; Lethal force is fully authorized if the number of active revolutionaries is more than twice the number of loyalists, and said revolutionaries are actively hostile

Created the Command Job SOP page.

General SOP: Complete! Greetings, aspiring SOP writers. If you've clicked this thread, then you're either interested in contributing to Standard Operating Procedure, or are merely interested in seeing how it's going. Therefore, I shall begin by explaining what this (soon-to-be) megathread is all about: Part 1: What is this? Approximately 4 months ago, Necaladun approached me with a personal project of his: a complete overhaul of Standard Operating Procedure, meant to centralize SOP in such a way that allowed for more interaction with the Legal sub-Department, more actual guidelines on how to conduct one's performance, and generally formalize what was once only nebulous guidelines in an effort to get everyone on the same page. This was the project that led to the current version of Security SOP. However, it was left half done, as Necaladun took his leave shortly after Sec SOP was added, and the project crumbled from lack of interest/time. However, I continued the project, but only recently picked it back up in full. The point of this megathread will be to, at the end of the line, have a single, well-defined, centralized Standard Operating Procedure that everyone can look at and fully comprehend, without any self-contradictory information. This, of course, will be changed in the Wiki, which is still the main source of information for the playerbase. Part 2: How does it work? Seeing as I actually have most of this stuff already written down, the process will be quite simple, and I'll break it down in stages: Stage 1: Selection of which part of SOP to look at, out of provided options (because we have to start somewhere). This will be done via poll; Stage 2: Proposal of new SOP. This will come from myself, again, because I have pretty much most of it already written down, so we have a solid base to go from; Stage 3: General feedback from the community. This is the main part of the process, as it will be the one where everyone can pitch in, say which parts are right, which parts are wrong, what should be changed, etc; Stage 4: Amendments made to SOP based on this feedback, and continued discussion, until a finalized version is produced; Stage 5: SOP is posted on the Wiki; Stage 6: Refer to Stage 1 Do keep in mind the following: everyone is permitted to pitch in. If you believe you have anything to add to the discussion, please do, but do try to keep this on track and problem-oriented, otherwise we'll never get off the drawing board. Part 3: What does it entail? The following are the proposed additions to this new, centralized SOP: Security Job SOP; (added by Necaladun before he took his leave) Engineering Job SOP; (finalized!) Medical Job SOP; (finalized!) Service Job SOP; (finalized!) Supply Job SOP; (finalized!) Science Job SOP (finalized!) In addition to the basic SOP for each Department, I also propose: Departmental SOP (as in, general guidelines for each Department that everyone should follow); (stricken to avoid bloat) Command SOP; (finalized!) Legal SOP (standardization of Legal procedures and the action of the Legal sub-Department); A revised General SOP, for each Color Code. This will include Safety Regulations As you can see, this is a rather big project and, as such, will be tackled in small stages. At each point, the completed section of SOP will be crossed out, and a notification written. At the end of the journey, a single, massive Standard Operating Procedure page will be added to the wiki, with all the above SOPs for everyone to look at. In addition, of course, to their own specific pages. And now, you've reached the end of the page. It's time to start, ladies and gentlemen.

Or not, considering the fact that no one touched this in a month. MERGING!

There is already a sentiment of "point-and-laugh" on the part of some people regarding denied appeals. Those, at least, are usually people that never set foot here again. Everything that could be said, has been said. Just. No.

You are a fucking monster, Vivalas. Shame.

Changed regarding what Ping said. Guideline 6 was merged into Guideline 2. Giving this another week before officializing it. Chip in while ya can.

I COULD wait two more days for a clean month, but fuck it. TIMING. I shall return to this post haste.

Hmm... Striking the first one. That is specified in the Revised CoC down below. My Cronbach's Alpha appears low today. Yes, ask the HoS. If no HoS, ask the Cappy. If neither, no recruitment for Security. I legitimately hate this stalemate at this point. How does the following sound: Emphasis added. As for: This reminds me. The following has been added to Revised CoC: Next up: Rare Case =/= Standard Operating Procedure. Also, yes it is, or should be, but it should still be written down, just in case. Due to tzo's contribution, Guideline has been changed to: Next up: Yes they would. Just making sure the HoP knows the QM exists. Guideline changed to: On to tzo: See above. Guideline changed to: Emphasis added. Next up: That one was on me. Stricken. Woop, forgot about that. Not my intention to overrule it, I will be formalizing it in General SOP, but for now: Emphasis added. Next up: See above. Actually, I may just strike this entirely. Swiping half a Department's worth of material for no reason will normally end up in them getting their ass thrown out anyway. Supply is a full Department, darnit. #makeCargoniagreatagain2016 Due to being specified in Revised CoC, this one is getting stricken. Muh malapropers. Also, it was just stricken by myself, so durr. Changed. Guideline changed to: Emphasis added. Next up: Intriguing. Changed to: Emphasis added. Next up: It's entirely possible that there simply are no Heads, but everything else is fine. Not really necessary, since if the whole of Command died, it's blatantly obvious that a shuttle call may be required.

If the Blueshield is overstepping their bounds and being Bluecurity, it never hurts to alert us.

2 words: Ahelp it.

After giving it some thought, how does the following sound: I would presume that anyone wanting to play Captain would know what CC VIPs are. That said... *scribble* How's the following sound: Good catch. Fused together in Guideline 2: Next up: This idea was initially conceived during the early stages of this project (back before Neca left, actually), but considering how much I've been pushing the whole "STANDARD Operating Procedure asdasdasd!!!!111!!!" thing, I think it can be stricken. The actual intention was the "No assigning anyone to Security if there is no HoS". How's this sound: Emphasis added. Next up: Good point. Changed to: Next up: I would very much like to keep this one, if only to remind Heads of Personnel not to get in everyone's way when half the station is blown up. See above. Although to be honest, I think that this can sort of be just removed all together, since it's stressed that the HoP is equal to all other heads of staff already. Of course the HoP doesn't have the authority. I agree with the first point, not the second. Heads of Personnel often forget that their authority begins and ends in their office, just because they have an ID machine, but they are, nominally, the second-in-command. As such, changed to: Next up: Actually a good point. Changed to: Next up: Form is as important as the message. Changed. Good point. Stricken. This Guideline refers mostly to direct authority over the crew. It's important to remind Representatives that no, they do not have any authority unless CC says so. Agreed on redundancy. Stricken. Yessssss, let the nitpick flow through you.... In all seriousness, changed to: Next up: Muh redundancy. Stricken. I should point out, this was put here to formalize what the Blueshield can/can't do in terms of arrests. Some people say sure, others say no, I say "Why not as long as it's relevant?". It's less of a restriction, and more of a specification. To that, I say: Then again... Stricken. Next up: The intent of AI Maint was to deal with the people doing it, lemme rephrase that: Emphasis added. Next up: Hmm.... Changed to: Emphasis added. Next up: Woops. Changed to: Emphasis added. Next up: That's what the "Chain of Command is to be followed" part is.

That's a legitimately good point. How's the following sound: Emphasis added. Next up: I can see your point. The redundancy of it kinda does make sense now. How's the following sound: Next up: The Blueshield is most often around Command areas and is better armed (and trained). Heads of Personnel more often than not faff off to somewhere else but their office, not to mention that they are not nominally in charge of anything but Cargo and Command until there's no Captain. HoS and Blueshield are safer options. And as for the secure location, well, no location on the station is secure. Keeping it on your person severely reduces the risk of it getting stolen. Badly worded on my end. My bad. How's the following sound: In addition, the following was added to HoP SOP:

Alright, apologies for the late reply to everyone, time to restart the conversation.

Already handled, Pinata (will look into the thread soonish).

Honestly belongs more in the Server Rules than SOP. It's accepted protocol that if a Head logs off, all sensitive equipment stays behind. Why not both? Changed it to: Next up: I have to say I disagree. Letting the Captain fire someone "with good reason" allows for a tad bit too much wriggle room. Whose good reason? What's a good reason? Keep in mind, the vote is only for situations where the Head isn't being openly incompetent, ie, situations where conflicts may arise. Having the whole of Command on board what may very well be a controversial decision saves a lot of hassle. I was honestly thinking about collusion between shitter Captain and RDs when I wrote that, but I suppose you do have a point. Plus, there's the whole vote thing where the rest of Command can shut down shit law changes. Changed. I find your pedantry refreshing. Changed. I'll echo Spacemanspark here. Freeform Laws are fun for the people that upload them. Frequently, the AI has absolutely no control over when a Captain randomly uploads a Freeform, and may very well be forced to RP in a way they don't want to because the Captain wants keks. That said, I'll add the following to the Guideline: That way, everyone can have fun. Right? Right?! I actually hadn't considered that. I'll add the following to Revised CoC: Next up: Once more, if the Head is blatantly breaking procedure/law and/or being absolutely incompetent at their job, the Captain may just fire them. Voting is required in situations that don't outright provide an obvious reason. See above. Changed to: Next up: I'll repeat myself for the millionth time: STANDARD Operating Procedure. Nuke Ops, Meteor Storms and Blobs are not standard. Anyone who complains about the HoP giving people increased access during those situations can rightfully be ignored. The Blueshield has general access to all departments. In fact, the rule is "Blueshield gets enough access to reach Department Head Offices". Any further access is a luxury, not a necessity. If there's an emergency, see the above point in large, bold, underlined, italic letters. Well, most of the time, the Blueshield has to protect Heads outside their offices, seeing as that's where most crimes happen. However, I'll change it to this: Emphasis added. Next up: Basically this. See above.