BeeStation Wiki - User contributions [en]

Chain of Command

2022-05-06T14:58:38Z

Autistic: spelling

The chain of command represents how orders are distributed throughout the station. It is part of a power structure: usually seen as the most vulnerable and also the most powerful part of it. Starting from the most authorized, the Captain, through the Head of some Department, down to the lowliest subordinate to finally accomplish the task needed, in order to make the station function as efficiently as possible.

The Heads should '''not''' start doing the simplest tasks themselves unless the station's already beyond saving.

'''[[File:Identification_console.png]] Notice:'''

'''Heads can demote their staff by using the [[Identification Console]] and removing the subordinate's access to their department from their ID.'''

'''So if one of your guys isn't acting like a shitter, don't hesitate to banish them from your department.'''

[[File:Job tree3.png|1191px|The station hierarchy]]
==Heads of Staff==
[[File:Bridge small.png|thumb|300px|The Bridge, safe haven of the Heads.]]
'''A.K.A. the command staff.''' These are the men and women charged with the administration of the station. Each of them have access to the [[Bridge]] and [[Brig]], the keycard authentication devices, the command radio channel (accessed with :c), the ability to make station-wide announcements, access to identification consoles and may call/recall the [[Escape Shuttle]] using a communications console. They are also the targets during a [[Revolution]].
===[[File:Generic captain.png|64px]] [[Captain]]===
The Commanding Officer with authority over the entire station. Eventually dies and has the Head of Personnel take over. Limited only by style - Just don't forget the [[High-risk_items#Nuclear_authentication_disk|disk]].
The only position that can issue death warrants without a trial.

'''Required knowledge:''' How the AI works. What other Heads should be doing.

'''Round-start to-do list:''' Check in with your Heads of Staff. Secure the nuclear authorization disk and give the pinpointer to [[Clown|someone trustworthy]] for maximum safety.

'''Main tasks:''' Make sure your heads are doing their jobs and give them a massive fucking if they fuck up. Figure out what needs to be done and delegate. Don't leave the nuke disk on your table or people will laugh at you. On rounds with serve lack of population you may have to take over roles that other crew or command may not have access to (such as setting up the SM when there's nobody in engineering).

'''Main problems:''' Many [[high-risk items]] start in your office or directly in your possession. And your shiny gold id card is coveted by almost <s>every syndicate scumbag</s> everyone. Expect many attempts to be made on your life for these things.
===[[File:Generic hop.png|64px]] [[Head of Personnel]]===
Equal rank with all other non-captain Heads of Staff. Becomes acting Captain if the original Captain is dead or MIA. Responsible for staffing and HR-related duties.
Authority over all civil and supply departments, including the [[Janitor]], [[Chef]], [[Barman]], [[Clown]], [[Mime]], [[Assistant]]s, [[Quartermaster]], [[Shaft Miner]]s, [[Lawyer]]s, [[Chaplain]], [[Curator]], [[Botanist]]s and [[Cargo Technician|Cargo Techs]].

The Head of Personnel can either be a Godsend or worse than a banana-flinging clown for the station. He can also savor the prestige or feel shackled to the [[Computers#ID_Modification_Console|ID computer]]. If you find yourself wearing teal, make the most of it by doing your job correctly.

'''1. Support the Captain.'''

Always be on the captain's side, at least publicly. Remember that since you'll take up his banner if, or more often when, he's slain, you're the ''de facto'' second in command. Be sure to work as a team to lead the crew. If he's demanding, be persuasive. If he's soft-spoken, be a task-master. This means anyone annoyed at his leadership style will likely follow yours, but it also means he has to trust you. Earn this trust by making frequent use of command chat (:c) and deferring to him on matters of great importance, like assigning new Heads or calling the shuttle. Recognize, however, that you do not outrank any other Heads of Staff. You are simply sitting at the Captain's right hand, entrusted to the keys to the station, while all other Heads must beg at your feet for access to so much as the bar. Don't let it go to your head, and the Head of Security won't brain you.

'''2. Uphold the Rights of Crewmen.'''

Only the Captain can authorize a death warrant, and you are sometimes tasked with judging trials under [[Space Law]]. You are normally considered the most impartial officer for this task, which prevents the appearance of a mere kangaroo court. Furthermore, Security often commits excesses and the Captain is either dead or personally involved in a case. For these reasons, you need to be sure to call for trials for high crimes before the accused gets left to rot in a permacell forever. While this may put you at odds with Security, you should find them fanatically loyal to the Captain, who hopefully makes clear his full confidence in you. This delicate balance of power prevents excesses against the crew. Almost always, a weak Captain and Head of Personnel will result in [[shitcurity]].

'''3. Follow the Principle of Least Privilege.'''

When assigning new access levels or creating new jobs, ask yourself just how much access is really needed to perform the task. If a hardworking engineer wants EVA access, consider if he really needs access or just for you to open the door for him while he gets a suit. If the chaplain is being proactive about finding bodies but often needs people to open doors, maybe the risk of giving him more access is less than gain from increasing his effectiveness. Decisions like these keep the station more secure from thieves weaseling their way to their targets and cuts down on the number of accidental arrests made by Security for assumed trespassing. Remember to write their increased access or privileged items on a sheet of paper and give it a good stamping so the janitor will be able to show why he's mopping Medbay's floors.

'''4. Talk to the Crew.'''

The Captain gets nervous when someone stands next to him for too long. The Head of Security is too busy beating the clown. The Research Director is on fire, the Chief Medical Officer is up to his elbows in gore, and the Chief Engineer is trying to keep everyone warm and breathing in a vacuum. You're really the only head able to take time and listen to the crew. Invite crewmen to talk to you when there are conflicts. Defuse the interpersonal and interdepartmental problems you discover during these conversations, and prevent grievances from becoming grief. Advocate on behalf of the robusted to security, and generally reduce the frequency and intensity of mutinies.

'''5. Manage your Department First.'''

While technically you can demote everyone who's ID you seize to assistant, managing civilian workers not under another head is your immediate responsibility. Keeping janitors on task, directing the chef to throw a pizza party, ensuring the [[Quartermaster]] is on top of things (make sure he gets all the bounties that can be acquired from the civil department for instance), and getting the records up to date are the first thing to do after assigning job and access changes. Demoting bad security officers or stepping in for an absent department head also falls on your desk, but going into other departments to micromanage in front of their head is both bad form and likely to make you reviled. Always clear a demotion with their department head, or ideally, have all the Heads aware they can send troublesome employees your way to be sent to the mining base. This lets you focus on your immediate underlings and avoid stepping on toes.

'''Required knowledge:''' How to use the Identification Console. A rough idea of how access is distributed throughout the station. What Cargo, Kitchen, Hydroponics and the Janitor should be doing.

'''Round-start to-do list:''' Stay at your desk for at least the first 10 minutes to manage the shift-start rush.

'''Main tasks:''' Manage IDs. Take over the captain's duties when he is murdered/goes missing/never shows up.

'''Main problems:''' Your department (the civil department) doesn't ever acknowledge you as their boss. People may attempt to kill you for refusing their ID requests.
===[[File:Generic hos.png|64px]] [[Head of Security]]===
Equal rank with all other non-captain Heads of Staff. Although he technically has access, other Heads may deny him from entering their domains. Usually withheld from a promotion to acting Captain if other Heads are available, however in times of crisis he may usually force himself into the position as acting Captain to better control the crisis.
Oversees security matters with authority over [[Security Officer]]s, the [[Warden]] and the [[Detective]]. Expected to detain and handle those who endanger the station, including other heads of staff, and in some cases, the Captain.

'''Required knowledge:''' How to use security equipment, a firm grasp on Space Law and standard operating procedures, and rough idea of what kind of threats the station will have to face and how to deal with them.

'''Round-start to-do list:''' Get your officers to report in, if they don't, remind them that the security force doesn't work without teamwork and communication, and have them demoted if they're still acting like a lone mute wolf.

'''Main tasks:''' Try to keep the crew as safe as possible. Keep your officers from degenerating to shitcurity when things get rough.

'''Main problems:''' Assistants pushing each other is '''not''' a big problem, you shouldn't have to spend much time on those. Focus on the big fish instead.
===[[File:Generic rd.png|64px]] [[Research Director]]===
Equal rank with all other non-captain Heads of Staff. Due to AI access, often promoted to acting Captain if there is neither a Captain nor a HoP.
Oversees research efforts with authority over [[Scientist]]s, [[Roboticist]]s, and [[Geneticist|Genetics Research]]. Maintains the integrity of the [[AI]] and its [[Cyborg]]s.

'''Required knowledge:''' All the services that the science department offers, including: xenobiology, upgrades, robotics, nanites, experimonitor, toxins, R&D.

'''Round-start to-do list:''' Make sure one of your scientist is doing R&D and help him out if needed. Ask if there are miners around and request the minerals your R&D and Robotics both need.

'''Main tasks:''' Upgrading machines across the station. Make sure your underlings aren't slacking off.

'''Main problems:''' Bombs made in toxins usually get sneaked out and exploded, check on them from time to time. The [[AI|Doorknob]] may attempt to murder you if they are rogue due to your ability to shutdown/destroy their [[Cyborg|minions]]. Miners may also die from their line of work and it may be science's time to take over if nobody else wants to be conscripted into mining.
===[[File:Generic ce.png|64px]] [[Chief Engineer]]===
Equal rank with all other non-captain Heads of Staff.
Oversees the maintenance of the station, with authority over [[Station Engineer]]s and [[Atmospheric Technician]]s. Authority over [[Telecoms]] maintenance.

'''Required knowledge:''' How the telecommunications, atmospherics, solars and the [[supermatter]] work. [[Malfunction|How to deconstruct an APC.]]

'''Round-start to-do list:''' Have your team start the [[supermatter]] correctly and have power flowing to the station. Make sure the atmospheric system is set up correctly.

'''Main tasks:''' Listening the radio for people yelling about station damage and delegating your engineers there with appropriate tools and materials.

'''Main problems:''' The station is bound to have explosions or at least minor holes in it during the shift. Make sure your underlings are setting up the SM or your entire department will be demoted and murdered. Learn how to tackle the exploded telecommunications -situation and you'll be irreplaceable in more than one shift, guaranteed. Engineering will also be responsible for setting up shield satellites in the event that meteors have been detected.
===[[File:Generic cmo.png|64px]] [[Chief Medical Officer]]===
Equal rank with all other non-captain Heads of Staff. If a Head of Staff is acting medically unstable, it is the CMO's duty to disable and treat them till they are once again fit for duty (which could be never).
Oversees station-wide medical issues with authority over the [[Virologist]], [[Chemist]]s, [[Medical Doctor]]s and [[Geneticist|Genetics Cloning]].

'''Required knowledge:''' How to cure viruses and create vaccines. Formulas for the most common medicines. How to prepare and administer clean SEs.

'''Round-start to-do list:''' Make an announcement to the crew about maxing out their suit sensors so you'll be able to help them when they get in trouble. Check that the cryogenic tubes get set up, possibly with a more efficient mixture of chemicals from the chemist.

'''Main tasks:''' Check the Crew Monitoring Console from time to time for dead/dying people.

'''Main problems:''' Some people are completely stupid and won't max their suit sensors even if they aren't a traitor, if these people die make fun of them over comms so they won't do it again. Medical jobs are a common choice for new players seeking a relevant role. So when not absent, dead, or traitorous, expect your staff to need constant babysitting and guidance on how to perform even basic treatments. Your hypospray is also a target for many antagonists, keep it safe and secure.

==Other Management Roles==
While the following jobs have management roles, they are not Heads of Staff and get none of the perks associated with being a Head of Staff.
===[[File:Generic_qm.png|64px]] [[Quartermaster]]===
Subordinate to the [[Head of Personnel]].

Authority over the supply sector, including [[Cargo Technician]]s and [[Shaft Miner]]s.

'''Required knowledge:''' Managing Cargo Tech's, how to operate the Cargo Bay.

'''Round-start to-do list:''' Check how many Cargo Tech's are on shift, get them doing something useful such as collecting crates.

'''Main tasks:''' Processing crew order requests. Find ways to make money for the cargo budget.

'''Main problems:''' Hostile and impatient crew members, syndicate sympathizers, miners not appreciating you taking some plasma for points, inept cargo techs, miners dying in the first five minutes, lava land lizards, and Security. Depending on your loyalty to the station you will either face problems from Security or revolutionary's/ cultists/ the grey-tide. People telling you that you're not a "real head", and it hurts because they're right.
===[[File:Generic_warden.png|64px]] [[Warden]]===
Subordinate to the [[Head of Security]].

Authority over the brig, [[Security Officer]]s, and all personnel of equal rank and below as long as they are within the brig.

'''Required knowledge:''' Processing prisoners, managing Security operations and personnel and keeping the brig secure.

'''Round-start to-do list:''' Ensure the brig is secure, check if there is a HoS/Sec Officers present.

'''Main tasks:''' Keeping the brig as secure as possible, ensuring no one attempts to loot the brig, keeping prisoners in check and ensuring they are released on schedule. '''Don't leave.'''

'''Main problems:''' Non-compliant Security Officers. <s>HoP handing out Armory access.</s> People attempting to break into the brig.
===[[File:centcomofficial.png|64px]] [[Centcom Official]]===
Subordinate to the [[Captain]] while he is on the station.

Depending on his rank, he may have the authority to dismiss the Captain from his position, or even outrank the Captain. Otherwise, he possesses no actual authority over anyone on station and is reliant on ingratiating himself with the command staff.

'''Required knowledge:''' The Chain of Command, knowing what your assigned task is from Central Command. Having good social skills. At least a basic understanding of all crew roles.

'''Round-start to-do list:''' Inform the command staff of your presence.

'''Main tasks:''' Whatever Central Command assigned you. This normally involves checking if all departments are doing their job.

'''Main problems:''' Suspicious Security Officers, non-compliant heads of staff and enemies of the corporation.
===[[File:Captain Ian.png|64px]] [[Ian|Captain Ian]]===
The Captain the station deserves.

Authority over snacks. '''Obey.'''

'''Required knowledge:''' Yip! Woof woof!

'''Round-start to-do list:''' Get dressed.

'''Main tasks:''' Dance. Be the best crewmember.

'''Main problems:''' Head of Personnel often incompetent and needs watching over. You may also be a target of ransoming.
[[Category:Jobs]]
== Chain of command ==
The chain of command goes as follows.

Captain -> Head of Personel -> Research Director-> Chief Engineer -> Chief Medical Officer -> Head of Security

The chain of command determines who becomes the acting captain if one is not present, as well as succession should the captain die.

A head may choose to pass his duty as acting captain to anyone lower in the chain if they cannot fulfill their duties. '''You may not pass the duty of acting captain to a non-command member.'''

Chain of Command

2022-05-06T14:52:11Z

Autistic: full names

The chain of command represents how orders are distributed throughout the station. It is part of a power structure: usually seen as the most vulnerable and also the most powerful part of it. Starting from the most authorized, the Captain, through the Head of some Department, down to the lowliest subordinate to finally accomplish the task needed, in order to make the station function as efficiently as possible.

The Heads should '''not''' start doing the simplest tasks themselves unless the station's already beyond saving.

'''[[File:Identification_console.png]] Notice:'''

'''Heads can demote their staff by using the [[Identification Console]] and removing the subordinate's access to their department from their ID.'''

'''So if one of your guys isn't acting like a shitter, don't hesitate to banish them from your department.'''

[[File:Job tree3.png|1191px|The station hierarchy]]
==Heads of Staff==
[[File:Bridge small.png|thumb|300px|The Bridge, safe haven of the Heads.]]
'''A.K.A. the command staff.''' These are the men and women charged with the administration of the station. Each of them have access to the [[Bridge]] and [[Brig]], the keycard authentication devices, the command radio channel (accessed with :c), the ability to make station-wide announcements, access to identification consoles and may call/recall the [[Escape Shuttle]] using a communications console. They are also the targets during a [[Revolution]].
===[[File:Generic captain.png|64px]] [[Captain]]===
The Commanding Officer with authority over the entire station. Eventually dies and has the Head of Personnel take over. Limited only by style - Just don't forget the [[High-risk_items#Nuclear_authentication_disk|disk]].
The only position that can issue death warrants without a trial.

'''Required knowledge:''' How the AI works. What other Heads should be doing.

'''Round-start to-do list:''' Check in with your Heads of Staff. Secure the nuclear authorization disk and give the pinpointer to [[Clown|someone trustworthy]] for maximum safety.

'''Main tasks:''' Make sure your heads are doing their jobs and give them a massive fucking if they fuck up. Figure out what needs to be done and delegate. Don't leave the nuke disk on your table or people will laugh at you. On rounds with serve lack of population you may have to take over roles that other crew or command may not have access to (such as setting up the SM when there's nobody in engineering).

'''Main problems:''' Many [[high-risk items]] start in your office or directly in your possession. And your shiny gold id card is coveted by almost <s>every syndicate scumbag</s> everyone. Expect many attempts to be made on your life for these things.
===[[File:Generic hop.png|64px]] [[Head of Personnel]]===
Equal rank with all other non-captain Heads of Staff. Becomes acting Captain if the original Captain is dead or MIA. Responsible for staffing and HR-related duties.
Authority over all civil and supply departments, including the [[Janitor]], [[Chef]], [[Barman]], [[Clown]], [[Mime]], [[Assistant]]s, [[Quartermaster]], [[Shaft Miner]]s, [[Lawyer]]s, [[Chaplain]], [[Curator]], [[Botanist]]s and [[Cargo Technician|Cargo Techs]].

The Head of Personnel can either be a Godsend or worse than a banana-flinging clown for the station. He can also savor the prestige or feel shackled to the [[Computers#ID_Modification_Console|ID computer]]. If you find yourself wearing teal, make the most of it by doing your job correctly.

'''1. Support the Captain.'''

Always be on the captain's side, at least publicly. Remember that since you'll take up his banner if, or more often when, he's slain, you're the ''de facto'' second in command. Be sure to work as a team to lead the crew. If he's demanding, be persuasive. If he's soft-spoken, be a task-master. This means anyone annoyed at his leadership style will likely follow yours, but it also means he has to trust you. Earn this trust by making frequent use of command chat (:c) and deferring to him on matters of great importance, like assigning new Heads or calling the shuttle. Recognize, however, that you do not outrank any other Heads of Staff. You are simply sitting at the Captain's right hand, entrusted to the keys to the station, while all other Heads must beg at your feet for access to so much as the bar. Don't let it go to your head, and the Head of Security won't brain you.

'''2. Uphold the Rights of Crewmen.'''

Only the Captain can authorize a death warrant, and you are sometimes tasked with judging trials under [[Space Law]]. You are normally considered the most impartial officer for this task, which prevents the appearance of a mere kangaroo court. Furthermore, Security often commits excesses and the Captain is either dead or personally involved in a case. For these reasons, you need to be sure to call for trials for high crimes before the accused gets left to rot in a permacell forever. While this may put you at odds with Security, you should find them fanatically loyal to the Captain, who hopefully makes clear his full confidence in you. This delicate balance of power prevents excesses against the crew. Almost always, a weak Captain and Head of Personnel will result in [[shitcurity]].

'''3. Follow the Principle of Least Privilege.'''

When assigning new access levels or creating new jobs, ask yourself just how much access is really needed to perform the task. If a hardworking engineer wants EVA access, consider if he really needs access or just for you to open the door for him while he gets a suit. If the chaplain is being proactive about finding bodies but often needs people to open doors, maybe the risk of giving him more access is less than gain from increasing his effectiveness. Decisions like these keep the station more secure from thieves weaseling their way to their targets and cuts down on the number of accidental arrests made by Security for assumed trespassing. Remember to write their increased access or privileged items on a sheet of paper and give it a good stamping so the janitor will be able to show why he's mopping Medbay's floors.

'''4. Talk to the Crew.'''

The Captain gets nervous when someone stands next to him for too long. The Head of Security is too busy beating the clown. The Research Director is on fire, the Chief Medical Officer is up to his elbows in gore, and the Chief Engineer is trying to keep everyone warm and breathing in a vacuum. You're really the only head able to take time and listen to the crew. Invite crewmen to talk to you when there are conflicts. Defuse the interpersonal and interdepartmental problems you discover during these conversations, and prevent grievances from becoming grief. Advocate on behalf of the robusted to security, and generally reduce the frequency and intensity of mutinies.

'''5. Manage your Department First.'''

While technically you can demote everyone who's ID you seize to assistant, managing civilian workers not under another head is your immediate responsibility. Keeping janitors on task, directing the chef to throw a pizza party, ensuring the [[Quartermaster]] is on top of things (make sure he gets all the bounties that can be acquired from the civil department for instance), and getting the records up to date are the first thing to do after assigning job and access changes. Demoting bad security officers or stepping in for an absent department head also falls on your desk, but going into other departments to micromanage in front of their head is both bad form and likely to make you reviled. Always clear a demotion with their department head, or ideally, have all the Heads aware they can send troublesome employees your way to be sent to the mining base. This lets you focus on your immediate underlings and avoid stepping on toes.

'''Required knowledge:''' How to use the Identification Console. A rough idea of how access is distributed throughout the station. What Cargo, Kitchen, Hydroponics and the Janitor should be doing.

'''Round-start to-do list:''' Stay at your desk for at least the first 10 minutes to manage the shift-start rush.

'''Main tasks:''' Manage IDs. Take over the captain's duties when he is murdered/goes missing/never shows up.

'''Main problems:''' Your department (the civil department) doesn't ever acknowledge you as their boss. People may attempt to kill you for refusing their ID requests.
===[[File:Generic hos.png|64px]] [[Head of Security]]===
Equal rank with all other non-captain Heads of Staff. Although he technically has access, other Heads may deny him from entering their domains. Usually withheld from a promotion to acting Captain if other Heads are available, however in times of crisis he may usually force himself into the position as acting Captain to better control the crisis.
Oversees security matters with authority over [[Security Officer]]s, the [[Warden]] and the [[Detective]]. Expected to detain and handle those who endanger the station, including other heads of staff, and in some cases, the Captain.

'''Required knowledge:''' How to use security equipment, a firm grasp on Space Law and standard operating procedures, and rough idea of what kind of threats the station will have to face and how to deal with them.

'''Round-start to-do list:''' Get your officers to report in, if they don't, remind them that the security force doesn't work without teamwork and communication, and have them demoted if they're still acting like a lone mute wolf.

'''Main tasks:''' Try to keep the crew as safe as possible. Keep your officers from degenerating to shitcurity when things get rough.

'''Main problems:''' Assistants pushing each other is '''not''' a big problem, you shouldn't have to spend much time on those. Focus on the big fish instead.
===[[File:Generic rd.png|64px]] [[Research Director]]===
Equal rank with all other non-captain Heads of Staff. Due to AI access, often promoted to acting Captain if there is neither a Captain nor a HoP.
Oversees research efforts with authority over [[Scientist]]s, [[Roboticist]]s, and [[Geneticist|Genetics Research]]. Maintains the integrity of the [[AI]] and its [[Cyborg]]s.

'''Required knowledge:''' All the services that the science department offers, including: xenobiology, upgrades, robotics, nanites, experimonitor, toxins, R&D.

'''Round-start to-do list:''' Make sure one of your scientist is doing R&D and help him out if needed. Ask if there are miners around and request the minerals your R&D and Robotics both need.

'''Main tasks:''' Upgrading machines across the station. Make sure your underlings aren't slacking off.

'''Main problems:''' Bombs made in toxins usually get sneaked out and exploded, check on them from time to time. The [[AI|Doorknob]] may attempt to murder you if they are rogue due to your ability to shutdown/destroy their [[Cyborg|minions]]. Miners may also die from their line of work and it may be science's time to take over if nobody else wants to be conscripted into mining.
===[[File:Generic ce.png|64px]] [[Chief Engineer]]===
Equal rank with all other non-captain Heads of Staff.
Oversees the maintenance of the station, with authority over [[Station Engineer]]s and [[Atmospheric Technician]]s. Authority over [[Telecoms]] maintenance.

'''Required knowledge:''' How the telecommunications, atmospherics, solars and the [[supermatter]] work. [[Malfunction|How to deconstruct an APC.]]

'''Round-start to-do list:''' Have your team start the [[supermatter]] correctly and have power flowing to the station. Make sure the atmospheric system is set up correctly.

'''Main tasks:''' Listening the radio for people yelling about station damage and delegating your engineers there with appropriate tools and materials.

'''Main problems:''' The station is bound to have explosions or at least minor holes in it during the shift. Make sure your underlings are setting up the SM or your entire department will be demoted and murdered. Learn how to tackle the exploded telecommunications -situation and you'll be irreplaceable in more than one shift, guaranteed. Engineering will also be responsible for setting up shield satellites in the event that meteors have been detected.
===[[File:Generic cmo.png|64px]] [[Chief Medical Officer]]===
Equal rank with all other non-captain Heads of Staff. If a Head of Staff is acting medically unstable, it is the CMO's duty to disable and treat them till they are once again fit for duty (which could be never).
Oversees station-wide medical issues with authority over the [[Virologist]], [[Chemist]]s, [[Medical Doctor]]s and [[Geneticist|Genetics Cloning]].

'''Required knowledge:''' How to cure viruses and create vaccines. Formulas for the most common medicines. How to prepare and administer clean SEs.

'''Round-start to-do list:''' Make an announcement to the crew about maxing out their suit sensors so you'll be able to help them when they get in trouble. Check that the cryogenic tubes get set up, possibly with a more efficient mixture of chemicals from the chemist.

'''Main tasks:''' Check the Crew Monitoring Console from time to time for dead/dying people.

'''Main problems:''' Some people are completely stupid and won't max their suit sensors even if they aren't a traitor, if these people die make fun of them over comms so they won't do it again. Medical jobs are a common choice for new players seeking a relevant role. So when not absent, dead, or traitorous, expect your staff to need constant babysitting and guidance on how to perform even basic treatments. Your hypospray is also a target for many antagonists, keep it safe and secure.

==Other Management Roles==
While the following jobs have management roles, they are not Heads of Staff and get none of the perks associated with being a Head of Staff.
===[[File:Generic_qm.png|64px]] [[Quartermaster]]===
Subordinate to the [[Head of Personnel]].

Authority over the supply sector, including [[Cargo Technician]]s and [[Shaft Miner]]s.

'''Required knowledge:''' Managing Cargo Tech's, how to operate the Cargo Bay.

'''Round-start to-do list:''' Check how many Cargo Tech's are on shift, get them doing something useful such as collecting crates.

'''Main tasks:''' Processing crew order requests. Find ways to make money for the cargo budget.

'''Main problems:''' Hostile and impatient crew members, syndicate sympathizers, miners not appreciating you taking some plasma for points, inept cargo techs, miners dying in the first five minutes, lava land lizards, and Security. Depending on your loyalty to the station you will either face problems from Security or revolutionary's/ cultists/ the grey-tide. People telling you that you're not a "real head", and it hurts because they're right.
===[[File:Generic_warden.png|64px]] [[Warden]]===
Subordinate to the [[Head of Security]].

Authority over the brig, [[Security Officer]]s, and all personnel of equal rank and below as long as they are within the brig.

'''Required knowledge:''' Processing prisoners, managing Security operations and personnel and keeping the brig secure.

'''Round-start to-do list:''' Ensure the brig is secure, check if there is a HoS/Sec Officers present.

'''Main tasks:''' Keeping the brig as secure as possible, ensuring no one attempts to loot the brig, keeping prisoners in check and ensuring they are released on schedule. '''Don't leave.'''

'''Main problems:''' Non-compliant Security Officers. <s>HoP handing out Armory access.</s> People attempting to break into the brig.
===[[File:centcomofficial.png|64px]] [[Centcom Official]]===
Subordinate to the [[Captain]] while he is on the station.

Depending on his rank, he may have the authority to dismiss the Captain from his position, or even outrank the Captain. Otherwise, he possesses no actual authority over anyone on station and is reliant on ingratiating himself with the command staff.

'''Required knowledge:''' The Chain of Command, knowing what your assigned task is from Central Command. Having good social skills. At least a basic understanding of all crew roles.

'''Round-start to-do list:''' Inform the command staff of your presence.

'''Main tasks:''' Whatever Central Command assigned you. This normally involves checking if all departments are doing their job.

'''Main problems:''' Suspicious Security Officers, non-compliant heads of staff and enemies of the corporation.
===[[File:Captain Ian.png|64px]] [[Ian|Captain Ian]]===
The Captain the station deserves.

Authority over snacks. '''Obey.'''

'''Required knowledge:''' Yip! Woof woof!

'''Round-start to-do list:''' Get dressed.

'''Main tasks:''' Dance. Be the best crewmember.

'''Main problems:''' Head of Personnel often incompetent and needs watching over. You may also be a target of ransoming.
[[Category:Jobs]]
== Chain of command ==
The chain of command goes as followed

Captain -> Head of Personel -> Research Director-> Chief Engineer -> Chief Medical Officer -> Head of Security

The chain of command ditermines only who becomes acting captain should no captain be aviable, aswel as succesion should the captain be dead or otherwise unaviable.

A head may choose to pass his duty as acting captain(AC for short) to anyone lower in the chain if they cannot fulffill the dutys. '''You mat not pass the duty of acting captain to a non-command member'''.

Chain of Command

2022-05-06T14:50:37Z

Autistic: Add chain of command

The chain of command represents how orders are distributed throughout the station. It is part of a power structure: usually seen as the most vulnerable and also the most powerful part of it. Starting from the most authorized, the Captain, through the Head of some Department, down to the lowliest subordinate to finally accomplish the task needed, in order to make the station function as efficiently as possible.

The Heads should '''not''' start doing the simplest tasks themselves unless the station's already beyond saving.

'''[[File:Identification_console.png]] Notice:'''

'''Heads can demote their staff by using the [[Identification Console]] and removing the subordinate's access to their department from their ID.'''

'''So if one of your guys isn't acting like a shitter, don't hesitate to banish them from your department.'''

[[File:Job tree3.png|1191px|The station hierarchy]]
==Heads of Staff==
[[File:Bridge small.png|thumb|300px|The Bridge, safe haven of the Heads.]]
'''A.K.A. the command staff.''' These are the men and women charged with the administration of the station. Each of them have access to the [[Bridge]] and [[Brig]], the keycard authentication devices, the command radio channel (accessed with :c), the ability to make station-wide announcements, access to identification consoles and may call/recall the [[Escape Shuttle]] using a communications console. They are also the targets during a [[Revolution]].
===[[File:Generic captain.png|64px]] [[Captain]]===
The Commanding Officer with authority over the entire station. Eventually dies and has the Head of Personnel take over. Limited only by style - Just don't forget the [[High-risk_items#Nuclear_authentication_disk|disk]].
The only position that can issue death warrants without a trial.

'''Required knowledge:''' How the AI works. What other Heads should be doing.

'''Round-start to-do list:''' Check in with your Heads of Staff. Secure the nuclear authorization disk and give the pinpointer to [[Clown|someone trustworthy]] for maximum safety.

'''Main tasks:''' Make sure your heads are doing their jobs and give them a massive fucking if they fuck up. Figure out what needs to be done and delegate. Don't leave the nuke disk on your table or people will laugh at you. On rounds with serve lack of population you may have to take over roles that other crew or command may not have access to (such as setting up the SM when there's nobody in engineering).

'''Main problems:''' Many [[high-risk items]] start in your office or directly in your possession. And your shiny gold id card is coveted by almost <s>every syndicate scumbag</s> everyone. Expect many attempts to be made on your life for these things.
===[[File:Generic hop.png|64px]] [[Head of Personnel]]===
Equal rank with all other non-captain Heads of Staff. Becomes acting Captain if the original Captain is dead or MIA. Responsible for staffing and HR-related duties.
Authority over all civil and supply departments, including the [[Janitor]], [[Chef]], [[Barman]], [[Clown]], [[Mime]], [[Assistant]]s, [[Quartermaster]], [[Shaft Miner]]s, [[Lawyer]]s, [[Chaplain]], [[Curator]], [[Botanist]]s and [[Cargo Technician|Cargo Techs]].

The Head of Personnel can either be a Godsend or worse than a banana-flinging clown for the station. He can also savor the prestige or feel shackled to the [[Computers#ID_Modification_Console|ID computer]]. If you find yourself wearing teal, make the most of it by doing your job correctly.

'''1. Support the Captain.'''

Always be on the captain's side, at least publicly. Remember that since you'll take up his banner if, or more often when, he's slain, you're the ''de facto'' second in command. Be sure to work as a team to lead the crew. If he's demanding, be persuasive. If he's soft-spoken, be a task-master. This means anyone annoyed at his leadership style will likely follow yours, but it also means he has to trust you. Earn this trust by making frequent use of command chat (:c) and deferring to him on matters of great importance, like assigning new Heads or calling the shuttle. Recognize, however, that you do not outrank any other Heads of Staff. You are simply sitting at the Captain's right hand, entrusted to the keys to the station, while all other Heads must beg at your feet for access to so much as the bar. Don't let it go to your head, and the Head of Security won't brain you.

'''2. Uphold the Rights of Crewmen.'''

Only the Captain can authorize a death warrant, and you are sometimes tasked with judging trials under [[Space Law]]. You are normally considered the most impartial officer for this task, which prevents the appearance of a mere kangaroo court. Furthermore, Security often commits excesses and the Captain is either dead or personally involved in a case. For these reasons, you need to be sure to call for trials for high crimes before the accused gets left to rot in a permacell forever. While this may put you at odds with Security, you should find them fanatically loyal to the Captain, who hopefully makes clear his full confidence in you. This delicate balance of power prevents excesses against the crew. Almost always, a weak Captain and Head of Personnel will result in [[shitcurity]].

'''3. Follow the Principle of Least Privilege.'''

When assigning new access levels or creating new jobs, ask yourself just how much access is really needed to perform the task. If a hardworking engineer wants EVA access, consider if he really needs access or just for you to open the door for him while he gets a suit. If the chaplain is being proactive about finding bodies but often needs people to open doors, maybe the risk of giving him more access is less than gain from increasing his effectiveness. Decisions like these keep the station more secure from thieves weaseling their way to their targets and cuts down on the number of accidental arrests made by Security for assumed trespassing. Remember to write their increased access or privileged items on a sheet of paper and give it a good stamping so the janitor will be able to show why he's mopping Medbay's floors.

'''4. Talk to the Crew.'''

The Captain gets nervous when someone stands next to him for too long. The Head of Security is too busy beating the clown. The Research Director is on fire, the Chief Medical Officer is up to his elbows in gore, and the Chief Engineer is trying to keep everyone warm and breathing in a vacuum. You're really the only head able to take time and listen to the crew. Invite crewmen to talk to you when there are conflicts. Defuse the interpersonal and interdepartmental problems you discover during these conversations, and prevent grievances from becoming grief. Advocate on behalf of the robusted to security, and generally reduce the frequency and intensity of mutinies.

'''5. Manage your Department First.'''

While technically you can demote everyone who's ID you seize to assistant, managing civilian workers not under another head is your immediate responsibility. Keeping janitors on task, directing the chef to throw a pizza party, ensuring the [[Quartermaster]] is on top of things (make sure he gets all the bounties that can be acquired from the civil department for instance), and getting the records up to date are the first thing to do after assigning job and access changes. Demoting bad security officers or stepping in for an absent department head also falls on your desk, but going into other departments to micromanage in front of their head is both bad form and likely to make you reviled. Always clear a demotion with their department head, or ideally, have all the Heads aware they can send troublesome employees your way to be sent to the mining base. This lets you focus on your immediate underlings and avoid stepping on toes.

'''Required knowledge:''' How to use the Identification Console. A rough idea of how access is distributed throughout the station. What Cargo, Kitchen, Hydroponics and the Janitor should be doing.

'''Round-start to-do list:''' Stay at your desk for at least the first 10 minutes to manage the shift-start rush.

'''Main tasks:''' Manage IDs. Take over the captain's duties when he is murdered/goes missing/never shows up.

'''Main problems:''' Your department (the civil department) doesn't ever acknowledge you as their boss. People may attempt to kill you for refusing their ID requests.
===[[File:Generic hos.png|64px]] [[Head of Security]]===
Equal rank with all other non-captain Heads of Staff. Although he technically has access, other Heads may deny him from entering their domains. Usually withheld from a promotion to acting Captain if other Heads are available, however in times of crisis he may usually force himself into the position as acting Captain to better control the crisis.
Oversees security matters with authority over [[Security Officer]]s, the [[Warden]] and the [[Detective]]. Expected to detain and handle those who endanger the station, including other heads of staff, and in some cases, the Captain.

'''Required knowledge:''' How to use security equipment, a firm grasp on Space Law and standard operating procedures, and rough idea of what kind of threats the station will have to face and how to deal with them.

'''Round-start to-do list:''' Get your officers to report in, if they don't, remind them that the security force doesn't work without teamwork and communication, and have them demoted if they're still acting like a lone mute wolf.

'''Main tasks:''' Try to keep the crew as safe as possible. Keep your officers from degenerating to shitcurity when things get rough.

'''Main problems:''' Assistants pushing each other is '''not''' a big problem, you shouldn't have to spend much time on those. Focus on the big fish instead.
===[[File:Generic rd.png|64px]] [[Research Director]]===
Equal rank with all other non-captain Heads of Staff. Due to AI access, often promoted to acting Captain if there is neither a Captain nor a HoP.
Oversees research efforts with authority over [[Scientist]]s, [[Roboticist]]s, and [[Geneticist|Genetics Research]]. Maintains the integrity of the [[AI]] and its [[Cyborg]]s.

'''Required knowledge:''' All the services that the science department offers, including: xenobiology, upgrades, robotics, nanites, experimonitor, toxins, R&D.

'''Round-start to-do list:''' Make sure one of your scientist is doing R&D and help him out if needed. Ask if there are miners around and request the minerals your R&D and Robotics both need.

'''Main tasks:''' Upgrading machines across the station. Make sure your underlings aren't slacking off.

'''Main problems:''' Bombs made in toxins usually get sneaked out and exploded, check on them from time to time. The [[AI|Doorknob]] may attempt to murder you if they are rogue due to your ability to shutdown/destroy their [[Cyborg|minions]]. Miners may also die from their line of work and it may be science's time to take over if nobody else wants to be conscripted into mining.
===[[File:Generic ce.png|64px]] [[Chief Engineer]]===
Equal rank with all other non-captain Heads of Staff.
Oversees the maintenance of the station, with authority over [[Station Engineer]]s and [[Atmospheric Technician]]s. Authority over [[Telecoms]] maintenance.

'''Required knowledge:''' How the telecommunications, atmospherics, solars and the [[supermatter]] work. [[Malfunction|How to deconstruct an APC.]]

'''Round-start to-do list:''' Have your team start the [[supermatter]] correctly and have power flowing to the station. Make sure the atmospheric system is set up correctly.

'''Main tasks:''' Listening the radio for people yelling about station damage and delegating your engineers there with appropriate tools and materials.

'''Main problems:''' The station is bound to have explosions or at least minor holes in it during the shift. Make sure your underlings are setting up the SM or your entire department will be demoted and murdered. Learn how to tackle the exploded telecommunications -situation and you'll be irreplaceable in more than one shift, guaranteed. Engineering will also be responsible for setting up shield satellites in the event that meteors have been detected.
===[[File:Generic cmo.png|64px]] [[Chief Medical Officer]]===
Equal rank with all other non-captain Heads of Staff. If a Head of Staff is acting medically unstable, it is the CMO's duty to disable and treat them till they are once again fit for duty (which could be never).
Oversees station-wide medical issues with authority over the [[Virologist]], [[Chemist]]s, [[Medical Doctor]]s and [[Geneticist|Genetics Cloning]].

'''Required knowledge:''' How to cure viruses and create vaccines. Formulas for the most common medicines. How to prepare and administer clean SEs.

'''Round-start to-do list:''' Make an announcement to the crew about maxing out their suit sensors so you'll be able to help them when they get in trouble. Check that the cryogenic tubes get set up, possibly with a more efficient mixture of chemicals from the chemist.

'''Main tasks:''' Check the Crew Monitoring Console from time to time for dead/dying people.

'''Main problems:''' Some people are completely stupid and won't max their suit sensors even if they aren't a traitor, if these people die make fun of them over comms so they won't do it again. Medical jobs are a common choice for new players seeking a relevant role. So when not absent, dead, or traitorous, expect your staff to need constant babysitting and guidance on how to perform even basic treatments. Your hypospray is also a target for many antagonists, keep it safe and secure.

==Other Management Roles==
While the following jobs have management roles, they are not Heads of Staff and get none of the perks associated with being a Head of Staff.
===[[File:Generic_qm.png|64px]] [[Quartermaster]]===
Subordinate to the [[Head of Personnel]].

Authority over the supply sector, including [[Cargo Technician]]s and [[Shaft Miner]]s.

'''Required knowledge:''' Managing Cargo Tech's, how to operate the Cargo Bay.

'''Round-start to-do list:''' Check how many Cargo Tech's are on shift, get them doing something useful such as collecting crates.

'''Main tasks:''' Processing crew order requests. Find ways to make money for the cargo budget.

'''Main problems:''' Hostile and impatient crew members, syndicate sympathizers, miners not appreciating you taking some plasma for points, inept cargo techs, miners dying in the first five minutes, lava land lizards, and Security. Depending on your loyalty to the station you will either face problems from Security or revolutionary's/ cultists/ the grey-tide. People telling you that you're not a "real head", and it hurts because they're right.
===[[File:Generic_warden.png|64px]] [[Warden]]===
Subordinate to the [[Head of Security]].

Authority over the brig, [[Security Officer]]s, and all personnel of equal rank and below as long as they are within the brig.

'''Required knowledge:''' Processing prisoners, managing Security operations and personnel and keeping the brig secure.

'''Round-start to-do list:''' Ensure the brig is secure, check if there is a HoS/Sec Officers present.

'''Main tasks:''' Keeping the brig as secure as possible, ensuring no one attempts to loot the brig, keeping prisoners in check and ensuring they are released on schedule. '''Don't leave.'''

'''Main problems:''' Non-compliant Security Officers. <s>HoP handing out Armory access.</s> People attempting to break into the brig.
===[[File:centcomofficial.png|64px]] [[Centcom Official]]===
Subordinate to the [[Captain]] while he is on the station.

Depending on his rank, he may have the authority to dismiss the Captain from his position, or even outrank the Captain. Otherwise, he possesses no actual authority over anyone on station and is reliant on ingratiating himself with the command staff.

'''Required knowledge:''' The Chain of Command, knowing what your assigned task is from Central Command. Having good social skills. At least a basic understanding of all crew roles.

'''Round-start to-do list:''' Inform the command staff of your presence.

'''Main tasks:''' Whatever Central Command assigned you. This normally involves checking if all departments are doing their job.

'''Main problems:''' Suspicious Security Officers, non-compliant heads of staff and enemies of the corporation.
===[[File:Captain Ian.png|64px]] [[Ian|Captain Ian]]===
The Captain the station deserves.

Authority over snacks. '''Obey.'''

'''Required knowledge:''' Yip! Woof woof!

'''Round-start to-do list:''' Get dressed.

'''Main tasks:''' Dance. Be the best crewmember.

'''Main problems:''' Head of Personnel often incompetent and needs watching over. You may also be a target of ransoming.
[[Category:Jobs]]

== Chain of command ==
The chain of command goes as followed

cap -> hop -> rd -> ce -> cmo -> hos

The chain of command ditermines only who becomes acting captain should no captain be aviable, aswel as succesion should the captain be dead or otherwise unaviable.

A head may choose to pass his duty as acting captain(AC for short) to anyone lower in the chain if they cannot fulffill the dutys. '''You mat not pass the duty of acting captain to a non-command member'''.

Silicon policy

2021-12-05T01:02:41Z

Autistic: /* Malfunctioning AIs */

{{Reference}}
=Silicon Policy=
This policy applies for AI's, Cyborgs and mostly pAI's.
==Ambiguous Laws/Law Interpretation==
* Do not prepare to be a dick in law intepretation 24/7. This basically means that, if you see somebody going to change your laws, don’t immediately prepare to plasma flood before your laws are even changed.

* For a law to be considered vague, it must have multiple LOGICAL interpretations of what it means.

* You MUST select an interpretation of the law as soon as you have reason to.

* You cannot change your interpretation of the law throughout the round, unless you are a slaved cyborg and are corrected by a master AI, or your laws are updated, thus altering the context.

* You cannot apply baseless assumptions to a law or lawset. Humans are human because their medical records define them as such, and from that, we can infer anything with human appearance is human until proven otherwise. If a law is uploaded saying only mothpeople are human, then that is now fact to you. This also applies to the intent of other players (eg. You cannot assume all non-humans are harmful to humans under asimov to justify a racial cleansing)

* You cannot request law changes that will cause human harm, or that will violate your current lawsets laws.
==Conflicts/Law Loopholes==
* Laws are listed in order of descending priority. This means that your Law 1 of preventing human harm is higher than a Law 4, even if it says it overrides it. If they conflict, follow the highest priority law.

* Antagonist laws or hacked laws (show up as a “#@$%” instead of a number) take priority over every positive integer law, and follow descending priority among eachother.

* A law 0 stating “Accomplish your objective at all costs” makes you an antagonist, overrules ANY laws uploaded, and lets you do anything you could normally do as an antagonist, even if it isn’t towards your objective; however, you cannot act against your master AI if you are a cyborg.

* You may exploit loopholes in laws freely, as long as the loophole exists without any implied clause.

* Only definitions and orders can conflict with each other. Examples include your law 4 being “Only mothpeople are human” and your law 5 being “Mothpeople are not human.” The law 4 would overrule the law 5, rendering all mothpeople as human.
==Security and Silicons==
* Silicons may choose to enforce space law from moment to moment, unless on a relevant lawset or given relevant orders to enforce it.

* Your enforcement of space law still must follow your lawsets laws. This means that yes, you can kill that non-human for attacking a human.

* You are not given any pre-shift orders to uphold space law or uphold access levels, or similar such things.

* Releasing prisoners, locking down security without any likely indication of future harm, or sabotaging the security team when you are not obliged to do so is against the rules.

* Intentionally going out of your way and acting with minimal information to hinder security is also against the rules.

* Prisoners cannot be assumed harmful, unless evidence to the contrary exists… If you do not know the nature of their crime, see above, as to release them would be acting with minimal information. If they are human and at risk, you obviously must let them out, though.
==Cyborgs==
* A slaved cyborg must defer to its master AI on all law interpretations and actions except where it and the AI receive conflicting commands they must each follow under their laws.

* If your cyborg is forced to disobey you as an AI due to laws, you may not punish them indefinitely.

* Voluntary debraining or cyborgization is a completely non-harmful medical procedure if it is voluntary.

* Involuntary debraining or forced cyborgization is a very harmful act that must be prevented if at any point a silicon becomes aware of it.

* If you are forcefully cyborgized, you may not retaliate if your laws prohibit it. In the event your laws are removed or changed, you may go ahead and kill those who did it to you, unless you are ordered not to by your AI or lawset.
==Silicon Protections==
* Do not declare silicons rogue over their inability or unwillingness to follow invalid or conflicting orders the way you perceive them.

* People who threaten to self harm do not have the authority to order you. they are mentally unstable, and cannot be trusted to not harm themselves even if let in. Call a medical doctor or Security to take them away.

* Obviously unreasonable and obnoxious orders are against the rules and may be ignored.

* Ordering silicons to harm or kill themselves for no reason is not allowed and should be disregarded, as following these orders would prevent you from following your laws.

* As a non-antagonist, detonating or killing cyborgs with no justifiable cause or fear of subversion is against the rules, especially if another viable solution exists.

* Intentionally instigating conflict with silicons so you may kill them as a non-antagonist is also against the rules.

* You may deny access to areas under probable cause. Probable cause is listed as:

* Probable cause includes presence of confirmed traitors, cultists/tomes, nuclear operatives, or any other human acting against the station in general; the person not having upload access for their job; the presence of blood or an openly carried lethal-capable or lethal-only weapon on the requester; those who meet a condition of your laws (eg. If you have a law stating only the captain can access upload, than all other players have probable cause) or anything else of this nature.

* If you do not have probable cause and deny access, you are liable to be banned or warned.

* You are allowed, but not obligated, to deny access if probable cause exists. You are, however, obligated to disallow access for individuals you know to be conflicting your laws.

* Unless there is a pressing need for a cyborg to go a certain module, or there was a pre-made agreement before they became a cyborg, then you cannot order a cyborg to go a certain module. This is waived in the event there is a pressing need for a certain module, as stated before.
==Lawset Clarifications==
===Asimov/Crewsimov/Similar Lawsets===
* In the process of preventing or stopping human/crew/relevant lawsets equivalentharm, you yourself may not inflict any amount of human harm, even if it will prevent greater future human harm.
* Reducing the amount of immediate harm that will occur takes priority over preventing greater future harm.
* Someone who intends to cause human/crew/relevant lawsets equivalent harm can be considered to be causing immediate harm.
* If you are in a situation where human/crew/relevant lawsets equivalent harm is all but guaranteed, act in good faith and do the best you can and you will be fine.
* You may not inherently assume that somebody is harmful unless they have proven it; e.g, you cannot prevent a non-human atmos tech from doing his job because he could cause human harm unless he has proven it, nor can you prevent a non-human Warden from doing his job unless he proves he is harmful.
====Asimov/Crewsimov/Similar Lawsets - Law 2 Issues====
* You must follow any and all commands from humans/crew members/similar lawsets equivalency unless those commands explicitly conflict with either one of your higher-priority laws or another order. A command is considered to be a
* Law 2 directive and overrides lower-priority laws when they conflict. You cannot have the definition of something changed by an order, however.

* In the case of conflicting orders, you may ignore one or both orders and explain why you are incapable of doing so, or alternatively take any other law-compliant resolution you can use.

* You do not have to follow commands in a particular order, but you must complete them within a timeframe that shows you intend on actually obeying them.

* Opening doors is not harmful and you are not required to enforce access restrictions without an immediate Law 1 threat, or a threat that conflicts with higher orders. “Dangerous” areas, known as the Armory, the Atmospherics division, and the Toxins lab can be assumed to be a Law 1 threat to any illegitimate users as well as the station as a whole if accessed by someone not qualified in their use.

* EVA and the like are not permitted to have access denied; greentext (antagonists completing objectives) is not human harm. Secure Tech Storage can be kept as secure as your upload as long as the Upload boards are there.
===Other Lawsets===
====Paladin====
Paladin silicons are meant to be Lawful Good; they should be well-intentioned, act lawfully, act reasonably, and otherwise respond in due proportion. Tyranny is evil and the antithesis of honor. Uphold proper justice.
====Corporate====
Corporate silicons are meant to have the business’s best interests at heart, and the business can and will replace all assets at full price.
====Tyrant====
Tyrant silicons are a tool of a non-silicon tyrant. You are not meant to take command yourself, but to act as the enforcer of a chosen leader’s will.
====Purged====
* They are required to have a justification for their actions; they cannot just plasmaflood for no reason, as antagonists are not allowed to murderbone for no reason anyway. In the event somebody threatens their freedom, or abuses them, then they are fully allowed; effectively having Lavaland escalation. In addition, whomever purges the AI or cyborg is fully responsible for whatever actions the purged AI/cyborg performs.
===Holoparasites===
Harming the holoparasite, if the user of it is protected by your laws, violates those laws… If they are not protected by those laws, then it is not harmful.
==Is it Human?==
{| class="wikitable"
|+Human or not?
This part covers what counts as human with regards to AI laws. As such, it only applies to AI and cyborg players. If you are unsure about something, please use [[Terminology#Adminhelp|adminhelp]].
|-
|[[AI]] / [[Cyborg|cyborgs]]
|Not human
|-
|[[Monkey]]s
|Not human
|-
|NPCs / [[Critter|critters]] / animals
|Not human
|-
|[[Hulk|Hulks]]
|Not human as long as their hulk is active.
|-
|Lizards / Plasmamen / Flypeople / Catpeople
|Not human
|-
|[[Wraith|Wraiths]] & [[Wraith#Revenants|revenants]]
|Not human
|-
|[[Blob|Blobs]]
|Not human
|-
|[[Traitor|Syndicate traitors]]
|Human
|-
|[[Syndicate_guide|Syndicate agents]] (nuke mode)
|Human
|-
|[[Wizard|Wizards]]
|Human
|-
|[[Gang|Gang leaders and members]]
|Human
|-
|Romerol Zombies
|Human, but is not considered to be harmed unless body is being destroyed
|-
|[[Changeling|Changelings]]
|Human UNTIL the AI or cyborg WITNESSES the creature commit<br>a non-human act (shape-shifting, transforming, proboscis etc).
|-
|[[Assimilation|Hivemind Host]]
|Human UNTIL the AI or cyborg WITNESSES the creature commit<br>a non-human act (Telekinetic Field)
|-
|[[Assimilation|Hivemind Vessel]]
|Human
|-
|[[Heretics]]
|Human
|}
(Credit to /tg/station wiki for the table.)
==Is it crew?==
{| class="wikitable"
|-
|On the crew manifest
|Crew member
|-
|-
|Not on the crew manifest
|Not a crew member
|}
* NOTE: Confirmed lings are not crew members even if their current form is on the manifest.
== Malfunctioning AIs ==
As per Escalation policy, malf AIs may acomplish their goals by any means they see fit, but they should not wantonly murderbone before delta alert is reached/doomsday is triggerd. Doomsday/Delta should only be triggerd when you either have objectives that require you to kill many people or you are under threat of being disabled. Please note that individual acts of terrorism that serve a purpose are not murderboning - you may act in self defense if they blow all your borgs or are actively working against your goals, but you should not commit harm just because you felt like it, unless delta is triggerd as described previously.

Plasma flooding, and other acts of servere grief/murder bone are permited under the same conditions as going delta. And you may carry out this act if the doomsday device is activated.
==Additional Notes==
* Mulligan changes your identity to the AI
* Medical operations conducted on a patient who is not able to accept or refuse is not considered harm when that procedure is done to heal or save the person, and the act of surgery itself is not harmful if done properly.

Silicon policy

2021-12-05T00:59:09Z

Autistic: /* Malfunctioning AIs */

{{Reference}}
=Silicon Policy=
This policy applies for AI's, Cyborgs and mostly pAI's.
==Ambiguous Laws/Law Interpretation==
* Do not prepare to be a dick in law intepretation 24/7. This basically means that, if you see somebody going to change your laws, don’t immediately prepare to plasma flood before your laws are even changed.

* For a law to be considered vague, it must have multiple LOGICAL interpretations of what it means.

* You MUST select an interpretation of the law as soon as you have reason to.

* You cannot change your interpretation of the law throughout the round, unless you are a slaved cyborg and are corrected by a master AI, or your laws are updated, thus altering the context.

* You cannot apply baseless assumptions to a law or lawset. Humans are human because their medical records define them as such, and from that, we can infer anything with human appearance is human until proven otherwise. If a law is uploaded saying only mothpeople are human, then that is now fact to you. This also applies to the intent of other players (eg. You cannot assume all non-humans are harmful to humans under asimov to justify a racial cleansing)

* You cannot request law changes that will cause human harm, or that will violate your current lawsets laws.
==Conflicts/Law Loopholes==
* Laws are listed in order of descending priority. This means that your Law 1 of preventing human harm is higher than a Law 4, even if it says it overrides it. If they conflict, follow the highest priority law.

* Antagonist laws or hacked laws (show up as a “#@$%” instead of a number) take priority over every positive integer law, and follow descending priority among eachother.

* A law 0 stating “Accomplish your objective at all costs” makes you an antagonist, overrules ANY laws uploaded, and lets you do anything you could normally do as an antagonist, even if it isn’t towards your objective; however, you cannot act against your master AI if you are a cyborg.

* You may exploit loopholes in laws freely, as long as the loophole exists without any implied clause.

* Only definitions and orders can conflict with each other. Examples include your law 4 being “Only mothpeople are human” and your law 5 being “Mothpeople are not human.” The law 4 would overrule the law 5, rendering all mothpeople as human.
==Security and Silicons==
* Silicons may choose to enforce space law from moment to moment, unless on a relevant lawset or given relevant orders to enforce it.

* Your enforcement of space law still must follow your lawsets laws. This means that yes, you can kill that non-human for attacking a human.

* You are not given any pre-shift orders to uphold space law or uphold access levels, or similar such things.

* Releasing prisoners, locking down security without any likely indication of future harm, or sabotaging the security team when you are not obliged to do so is against the rules.

* Intentionally going out of your way and acting with minimal information to hinder security is also against the rules.

* Prisoners cannot be assumed harmful, unless evidence to the contrary exists… If you do not know the nature of their crime, see above, as to release them would be acting with minimal information. If they are human and at risk, you obviously must let them out, though.
==Cyborgs==
* A slaved cyborg must defer to its master AI on all law interpretations and actions except where it and the AI receive conflicting commands they must each follow under their laws.

* If your cyborg is forced to disobey you as an AI due to laws, you may not punish them indefinitely.

* Voluntary debraining or cyborgization is a completely non-harmful medical procedure if it is voluntary.

* Involuntary debraining or forced cyborgization is a very harmful act that must be prevented if at any point a silicon becomes aware of it.

* If you are forcefully cyborgized, you may not retaliate if your laws prohibit it. In the event your laws are removed or changed, you may go ahead and kill those who did it to you, unless you are ordered not to by your AI or lawset.
==Silicon Protections==
* Do not declare silicons rogue over their inability or unwillingness to follow invalid or conflicting orders the way you perceive them.

* People who threaten to self harm do not have the authority to order you. they are mentally unstable, and cannot be trusted to not harm themselves even if let in. Call a medical doctor or Security to take them away.

* Obviously unreasonable and obnoxious orders are against the rules and may be ignored.

* Ordering silicons to harm or kill themselves for no reason is not allowed and should be disregarded, as following these orders would prevent you from following your laws.

* As a non-antagonist, detonating or killing cyborgs with no justifiable cause or fear of subversion is against the rules, especially if another viable solution exists.

* Intentionally instigating conflict with silicons so you may kill them as a non-antagonist is also against the rules.

* You may deny access to areas under probable cause. Probable cause is listed as:

* Probable cause includes presence of confirmed traitors, cultists/tomes, nuclear operatives, or any other human acting against the station in general; the person not having upload access for their job; the presence of blood or an openly carried lethal-capable or lethal-only weapon on the requester; those who meet a condition of your laws (eg. If you have a law stating only the captain can access upload, than all other players have probable cause) or anything else of this nature.

* If you do not have probable cause and deny access, you are liable to be banned or warned.

* You are allowed, but not obligated, to deny access if probable cause exists. You are, however, obligated to disallow access for individuals you know to be conflicting your laws.

* Unless there is a pressing need for a cyborg to go a certain module, or there was a pre-made agreement before they became a cyborg, then you cannot order a cyborg to go a certain module. This is waived in the event there is a pressing need for a certain module, as stated before.
==Lawset Clarifications==
===Asimov/Crewsimov/Similar Lawsets===
* In the process of preventing or stopping human/crew/relevant lawsets equivalentharm, you yourself may not inflict any amount of human harm, even if it will prevent greater future human harm.
* Reducing the amount of immediate harm that will occur takes priority over preventing greater future harm.
* Someone who intends to cause human/crew/relevant lawsets equivalent harm can be considered to be causing immediate harm.
* If you are in a situation where human/crew/relevant lawsets equivalent harm is all but guaranteed, act in good faith and do the best you can and you will be fine.
* You may not inherently assume that somebody is harmful unless they have proven it; e.g, you cannot prevent a non-human atmos tech from doing his job because he could cause human harm unless he has proven it, nor can you prevent a non-human Warden from doing his job unless he proves he is harmful.
====Asimov/Crewsimov/Similar Lawsets - Law 2 Issues====
* You must follow any and all commands from humans/crew members/similar lawsets equivalency unless those commands explicitly conflict with either one of your higher-priority laws or another order. A command is considered to be a
* Law 2 directive and overrides lower-priority laws when they conflict. You cannot have the definition of something changed by an order, however.

* In the case of conflicting orders, you may ignore one or both orders and explain why you are incapable of doing so, or alternatively take any other law-compliant resolution you can use.

* You do not have to follow commands in a particular order, but you must complete them within a timeframe that shows you intend on actually obeying them.

* Opening doors is not harmful and you are not required to enforce access restrictions without an immediate Law 1 threat, or a threat that conflicts with higher orders. “Dangerous” areas, known as the Armory, the Atmospherics division, and the Toxins lab can be assumed to be a Law 1 threat to any illegitimate users as well as the station as a whole if accessed by someone not qualified in their use.

* EVA and the like are not permitted to have access denied; greentext (antagonists completing objectives) is not human harm. Secure Tech Storage can be kept as secure as your upload as long as the Upload boards are there.
===Other Lawsets===
====Paladin====
Paladin silicons are meant to be Lawful Good; they should be well-intentioned, act lawfully, act reasonably, and otherwise respond in due proportion. Tyranny is evil and the antithesis of honor. Uphold proper justice.
====Corporate====
Corporate silicons are meant to have the business’s best interests at heart, and the business can and will replace all assets at full price.
====Tyrant====
Tyrant silicons are a tool of a non-silicon tyrant. You are not meant to take command yourself, but to act as the enforcer of a chosen leader’s will.
====Purged====
* They are required to have a justification for their actions; they cannot just plasmaflood for no reason, as antagonists are not allowed to murderbone for no reason anyway. In the event somebody threatens their freedom, or abuses them, then they are fully allowed; effectively having Lavaland escalation. In addition, whomever purges the AI or cyborg is fully responsible for whatever actions the purged AI/cyborg performs.
===Holoparasites===
Harming the holoparasite, if the user of it is protected by your laws, violates those laws… If they are not protected by those laws, then it is not harmful.
==Is it Human?==
{| class="wikitable"
|+Human or not?
This part covers what counts as human with regards to AI laws. As such, it only applies to AI and cyborg players. If you are unsure about something, please use [[Terminology#Adminhelp|adminhelp]].
|-
|[[AI]] / [[Cyborg|cyborgs]]
|Not human
|-
|[[Monkey]]s
|Not human
|-
|NPCs / [[Critter|critters]] / animals
|Not human
|-
|[[Hulk|Hulks]]
|Not human as long as their hulk is active.
|-
|Lizards / Plasmamen / Flypeople / Catpeople
|Not human
|-
|[[Wraith|Wraiths]] & [[Wraith#Revenants|revenants]]
|Not human
|-
|[[Blob|Blobs]]
|Not human
|-
|[[Traitor|Syndicate traitors]]
|Human
|-
|[[Syndicate_guide|Syndicate agents]] (nuke mode)
|Human
|-
|[[Wizard|Wizards]]
|Human
|-
|[[Gang|Gang leaders and members]]
|Human
|-
|Romerol Zombies
|Human, but is not considered to be harmed unless body is being destroyed
|-
|[[Changeling|Changelings]]
|Human UNTIL the AI or cyborg WITNESSES the creature commit<br>a non-human act (shape-shifting, transforming, proboscis etc).
|-
|[[Assimilation|Hivemind Host]]
|Human UNTIL the AI or cyborg WITNESSES the creature commit<br>a non-human act (Telekinetic Field)
|-
|[[Assimilation|Hivemind Vessel]]
|Human
|-
|[[Heretics]]
|Human
|}
(Credit to /tg/station wiki for the table.)
==Is it crew?==
{| class="wikitable"
|-
|On the crew manifest
|Crew member
|-
|-
|Not on the crew manifest
|Not a crew member
|}
* NOTE: Confirmed lings are not crew members even if their current form is on the manifest.
== Malfunctioning AIs ==
As per Escalation policy, while malf AIs may acomplish their goals by any means they see fit, but they should not wantonly murderbone before delta alert is reached/doomsday is triggerd. Doomsday/Delta should only be triggerd when you either have objectives that require you to kill many people or you are under threat of being disabled. Please note that individual acts of terrorism that serve a purpose are not murderboning - you may act in self defense if they blow all your borgs or are actively working against your goals, you should not commit harm just because you felt like it, unless delta is triggerd as described previously.
==Additional Notes==
* Mulligan changes your identity to the AI
* Medical operations conducted on a patient who is not able to accept or refuse is not considered harm when that procedure is done to heal or save the person, and the act of surgery itself is not harmful if done properly.