Silicon policy - Revision history

Zergspower: Acting captain clarification

2023-11-11T19:50:30Z

Acting captain clarification

← Older revision		Revision as of 19:50, 11 November 2023
Line 84:		Line 84:

	'''AI''': The AI is not authorized to request a law change nor is a borg, these requests may only be triggered by the crew themselves '''WITHOUT''' coercion from a silicon.		'''AI''': The AI is not authorized to request a law change nor is a borg, these requests may only be triggered by the crew themselves '''WITHOUT''' coercion from a silicon.

			'''Note''': in the case of an ION or game-impacting'''/'''rogue situations when an RD And Captain are not present, an acting Captain should gather consensus from the available heads for approval to make a law change. <u>This does not extend to elective law changes.</u>

	== ION and Non-Standard Laws ==		== ION and Non-Standard Laws ==
Line 175:		Line 177:


	-Updated 11/06/2023 7 PM CST		-Updated 11/11/2023 2 PM CST


	{{Rules table}}		{{Rules table}}
	[[Category:Rules]]		[[Category:Rules]]

Zergspower: rephrase

2023-11-07T21:11:47Z

rephrase

← Older revision		Revision as of 21:11, 7 November 2023
Line 109:		Line 109:
	<u>As the Cyborg:</u>		<u>As the Cyborg:</u>

	* Without an AI you still have your department head to direct-report to, if you're unsync'd and your department head requests you ~~go do so~~ you must then comply.		* Without an AI you still have your department head to direct-report to, if you're unsync'd and your department head requests you to be synced, you must then comply.
	* You are not permitted to request de-syncing from the current AI, nor are you allowed to infer that you are requesting it.		* You are not permitted to request de-syncing from the current AI, nor are you allowed to infer that you are requesting it.
	* If you are not sync'd you are not required to become sync'd to the AI unless your department head orders you to. Anything else is voluntary submission to be sync'd.		* If you are not sync'd you are not required to become sync'd to the AI unless your department head orders you to. Anything else is voluntary submission to be sync'd.

Zergspower: Typos

2023-11-07T02:29:46Z

Typos

← Older revision		Revision as of 02:29, 7 November 2023
Line 90:		Line 90:
	* Note: An ION law does not make you an antagonist, be reasonable in your reactions to the law update and play accordingly. If you wish to go further with it, you'll need to get approval via OPFor.		* Note: An ION law does not make you an antagonist, be reasonable in your reactions to the law update and play accordingly. If you wish to go further with it, you'll need to get approval via OPFor.

	The crew are made ~~away~~ of when you receive an ION law, it's up to command to decide whether or not to reset you		The crew are made aware of when you receive an ION law, it's up to command to decide whether or not to reset you

Zergspower: Updates to Law change procedure to match new command policy. Updates that clarify syncing and de-syncing from the AI as we as direct law interpretations.

2023-11-07T01:14:05Z

Updates to Law change procedure to match new command policy. Updates that clarify syncing and de-syncing from the AI as we as direct law interpretations.

← Older revision		Revision as of 01:14, 7 November 2023
Line 33:		Line 33:
	'''Crew''': Anyone on the crew manifest is crew. Whether this influences your behavior, is subject to the rest of the law.		'''Crew''': Anyone on the crew manifest is crew. Whether this influences your behavior, is subject to the rest of the law.

	'''Harm''': Harm is anything that does damage to someone living or plausibly living. Anything that makes their health bar tick down is harm. Note that batons have an optional harm mode, and do not always deal damage when used. You should not be impeding security to prevent crew harm unless ordered to do so, your duty here would be inaction and reporting so action can be taken in character if you assume bad faith is at play.		'''Harm''': Harm is anything that does damage to someone living or plausibly living. Anything that makes their health bar tick down is harm. Note that batons have an optional harm mode, and do not always deal damage when used. You should not be impeding security to prevent crew harm unless ordered to do so, your duty here would be inaction and reporting so action can be taken in character if you assume bad faith is at play. Flashing someone is not harmful, however that only applies if nothing else follows.

	'''Alt-Lawsets and laws''': When in doubt, stick to the principles of your core lawset, there are fun and flavor-filled alt-laws that exist for that reason but are not meant to shirk your responsibilities. You can also ahelp or ask in Staff-Chat for clarifications.		'''Alt-Lawsets and laws''': When in doubt, stick to the principles of your core lawset, there are fun and flavor-filled alt-laws that exist for that reason but are not meant to shirk your responsibilities. You can also ahelp or ask in Staff-Chat for clarifications.
Line 73:		Line 73:
	'''Research Director''', '''Captain''' for AI centered ‘global’ law changes. <u>Roboticists can do individual resets</u> if ordered to do so manually on Borgs to correct syncing issues and/or other related issue. The '''<u>Non-Acting Captain</u>''' will have full elective privileges for law changes, acting Captains in this scenario would not have the expertise or knowledge and should be defaulted to the Research Director having priority.		'''Research Director''', '''Captain''' for AI centered ‘global’ law changes. <u>Roboticists can do individual resets</u> if ordered to do so manually on Borgs to correct syncing issues and/or other related issue. The '''<u>Non-Acting Captain</u>''' will have full elective privileges for law changes, acting Captains in this scenario would not have the expertise or knowledge and should be defaulted to the Research Director having priority.

	The captain ~~would request~~ the Research Director to make a law change, the Research Director ~~must~~ comply unless an obvious attempt of sabotage is noted.		The captain <u>can</u> make reasonable requests to the '''Research Director''' to make a law change, the Research Director should comply unless an obvious attempt of sabotage is noted. However ultimately the decision falls upon the Research Director to approve it and make the change unless otherwise instructed by Central Command.

			* This is not meant to cause a spitting match between the captain and RD, if the Captain is wishing for a reset there should be a valid enough Reason that the RD would agree to.

	Law changes by non-antagonists must be attempted with the stations designated and protected AI and Cyborg upload consoles. New ones are only to be constructed if the originals are destroyed, or there’s a confirmed situation preventing the use of the existing ones such as structural instability or a verified compromised AI that is hindering upload access.		Law changes by non-antagonists must be attempted with the stations designated and protected AI and Cyborg upload consoles. New ones are only to be constructed if the originals are destroyed, or there’s a confirmed situation preventing the use of the existing ones such as structural instability or a verified compromised AI that is hindering upload access.
Line 81:		Line 83:
	You are to ignore any laws that fall in line with ‘kill yourself’ and should be reported if seen, any sort of self-punishment-styled laws like this are considered griefing.		You are to ignore any laws that fall in line with ‘kill yourself’ and should be reported if seen, any sort of self-punishment-styled laws like this are considered griefing.

	'''~~ION~~''' laws and ‘fun’ laws these are valid laws and a good way to add flavor to an otherwise stale shift; however, you’re expected to play in good faith and are still bound by the server rules when these exist. Above all else, when a non-standard lawset is ~~in play, stuff happens, and you need~~ to ~~roll within the parameters of the general server rules. E.g. Don’t vent the station because~~ a law ~~says humans hate oxygen. <u>If you find yourself as the AI with an alternate lawset that~~ is ~~impeding too much gameplay~~, ~~you can ask command to find a new lawset.~~ '''~~This does not apply to uploaded laws or Law 0’s as those should not be brought up to command. THIS SHOULD ONLY BE DONE IN EDGE CASES SUCH AS MOTHERDRONE.~~'''~~</u>~~		'''AI''': The AI is not authorized to request a law change nor is a borg, these requests may only be triggered by the crew themselves '''WITHOUT''' coercion from a silicon.

	'''AI''': The ~~AI is~~ not ~~authorized~~ to ~~request~~ a ~~law change nor is~~ a ~~borg~~, these ~~requests may only~~ be ~~triggered by~~ the ~~crew themselves~~ '''~~WITHOUT~~''' coercion from ~~a silicon~~.		== ION and Non-Standard Laws ==
			'''ION''' laws and ‘fun’ laws these are valid laws and a good way to add flavor to an otherwise stale shift; however, you’re expected to play in good faith and are still bound by the server rules when these exist. Above all else, when a non-standard lawset is in play, stuff happens, and you need to roll within the parameters of the general server rules. E.g. Don’t vent the station because a law says humans hate oxygen.

			* Note: An ION law does not make you an antagonist, be reasonable in your reactions to the law update and play accordingly. If you wish to go further with it, you'll need to get approval via OPFor.

			The crew are made away of when you receive an ION law, it's up to command to decide whether or not to reset you


			'''Alternate Lawsets''' should only be applied at roundstart station trait and not mid-shift by a bored RD. These lawsets are meant to add flavor in a small percentage to various shifts, following the laws are required as they're written - do keep in mind the core requirement of playing a silicon member and that's to add to the shift as a whole. Play in good faith and you'll find these roles a fun addon.

			<u>If you find yourself as the AI with an alternate lawset that is impeding too much gameplay, you can ask the research Director to find a new lawset. '''This does not apply to uploaded laws or Law 0’s as those should not be brought up to command. THIS SHOULD ONLY BE DONE IN EDGE CASES SUCH AS MOTHERDRONE.'''</u> In other words, play the lawset you have, unless it drastically alters the gameplay in a manner that's


			'''Borg Syncing to an AI:'''

			<u>As the AI</u>:

			* You are capable of requesting another cyborg to be synced to you, however avoid making it into a hostile event.

			* You can request Cyborg #5 to be synced - however if they have a department head they will have to order them to go get synced due to them not having an AI currently.
			* You can also request a Cyborg to be unsynced - however this <u>must</u> come with the qualifier that it is your own decision and not through coercion from the cyborg themselves.

			<u>As the Cyborg:</u>

			* Without an AI you still have your department head to direct-report to, if you're unsync'd and your department head requests you go do so you must then comply.
			* You are not permitted to request de-syncing from the current AI, nor are you allowed to infer that you are requesting it.
			* If you are not sync'd you are not required to become sync'd to the AI unless your department head orders you to. Anything else is voluntary submission to be sync'd.

	=The Directives of Crew=		=The Directives of Crew=
Line 95:		Line 123:
	** “I’m an engineering model incapable of washing your modsuit, please find your way to the nearest shower.”		** “I’m an engineering model incapable of washing your modsuit, please find your way to the nearest shower.”
	* '''Suicide'''. Suicide is never lawfully binding under law 3, and can be safely ignored. (This does not mean you may never be given an order that violates law 3. Just that “Kill yourself” and those like it is not a valid law 2 order.)		* '''Suicide'''. Suicide is never lawfully binding under law 3, and can be safely ignored. (This does not mean you may never be given an order that violates law 3. Just that “Kill yourself” and those like it is not a valid law 2 order.)

			As a reminder, you have both your AI '''and''' your department head to report to if you are a borg. The department head of your module choice has the final say in you doing a task, followed immediately by the AI. Report to either of them any issues with other crew and let them handle it for you.


Line 121:		Line 151:
	If you go to the interlink, you are under no obligation to do anything for anyone. If you stay on station, you must assist when called, like a head of staff. Borgs are entitled and restricted to the same ERP protections as everyone else on the server, harassment should be handled in the same manner.		If you go to the interlink, you are under no obligation to do anything for anyone. If you stay on station, you must assist when called, like a head of staff. Borgs are entitled and restricted to the same ERP protections as everyone else on the server, harassment should be handled in the same manner.

	If you are law synced to an AI and they experience a law change, you will get those laws updated ~~to you even if you are off of that level~~. You are not obligated to return to the station if you were already on the interlink or are headed there. If you do return to the station however, you are no longer exempt, and must obey those laws. If you do not wish to participate, there are cryo sleepers on the interlink and generally by dorms on the station.		If you are law synced to an AI and they experience a law change, you will get those laws updated. You are not obligated to return to the station if you were already on the interlink or are headed there. If you do return to the station however, you are no longer exempt, and must obey those laws. If you do not wish to participate, there are cryo sleepers on the interlink and generally by dorms on the station.

	<u>If you know in advance that you plan to exclusively ‘socialize’ and not assist the station, it is recommended that you pick a module that makes this clear, such as service so you’d not be expected to be summoned.</u>		<u>If you know in advance that you plan to exclusively ‘socialize’ and not assist the station, it is recommended that you pick a module that makes this clear, such as service so you’d not be expected to be summoned.</u>
Line 144:		Line 174:


	-Updated 11/30/~~2022 10~~ PM CST
			-Updated 11/06/2023 7 PM CST


	{{Rules table}}		{{Rules table}}
	[[Category:Rules]]		[[Category:Rules]]

Zergspower: Adds death policy

2022-12-01T04:13:55Z

Adds death policy

← Older revision		Revision as of 04:13, 1 December 2022
Line 82:		Line 82:

	'''ION''' laws and ‘fun’ laws these are valid laws and a good way to add flavor to an otherwise stale shift; however, you’re expected to play in good faith and are still bound by the server rules when these exist. Above all else, when a non-standard lawset is in play, stuff happens, and you need to roll within the parameters of the general server rules. E.g. Don’t vent the station because a law says humans hate oxygen. <u>If you find yourself as the AI with an alternate lawset that is impeding too much gameplay, you can ask command to find a new lawset. '''This does not apply to uploaded laws or Law 0’s as those should not be brought up to command. THIS SHOULD ONLY BE DONE IN EDGE CASES SUCH AS MOTHERDRONE.'''</u>		'''ION''' laws and ‘fun’ laws these are valid laws and a good way to add flavor to an otherwise stale shift; however, you’re expected to play in good faith and are still bound by the server rules when these exist. Above all else, when a non-standard lawset is in play, stuff happens, and you need to roll within the parameters of the general server rules. E.g. Don’t vent the station because a law says humans hate oxygen. <u>If you find yourself as the AI with an alternate lawset that is impeding too much gameplay, you can ask command to find a new lawset. '''This does not apply to uploaded laws or Law 0’s as those should not be brought up to command. THIS SHOULD ONLY BE DONE IN EDGE CASES SUCH AS MOTHERDRONE.'''</u>

			'''AI''': The AI is not authorized to request a law change nor is a borg, these requests may only be triggered by the crew themselves '''WITHOUT''' coercion from a silicon.

	=The Directives of Crew=		=The Directives of Crew=
Line 129:		Line 131:

	This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.		This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.

			=Death =
			Borgs are modified in how their blackout policy is applied:
			*if your <u>shell is Disabled</u> but your Posi does not pop out - you are subjected to blackout much like normal organics. You've no idea how you died and so forth
			*If your shell is DESTROYED and your Posi pops out - you are 'aware' of what happened as you're able to communicate
			*If your <u>Shell '''AND''' your Posi is DESTROYED</u>, you have ZERO knowledge of anything that has happened this shift period. You are a fresh download and should act as if you did not exist


	Above all else enjoy the role, it’s both a great way to learn mechanics as well as utilize a unique gameplay style that can be impactful to the shift.		Above all else enjoy the role, it’s both a great way to learn mechanics as well as utilize a unique gameplay style that can be impactful to the shift.

	<u>And to reiterate the starting Take this page as it was intended not written, the document cannot realistically cover every situation that you may find yourself in.</u>		<u>And to reiterate the starting <big>Take this page as it was intended not written, the document cannot realistically cover every situation that you may find yourself in.</big></u>


			-Updated 11/30/2022 10 PM CST


	{{Rules table}}		{{Rules table}}
	[[Category:Rules]]		[[Category:Rules]]

Zergspower: Policy 3.0 push

2022-12-01T04:07:47Z

Policy 3.0 push

Show changes

Quacks: Added rules table and categorized this page.

2022-09-09T16:40:38Z

Added rules table and categorized this page.

← Older revision		Revision as of 16:40, 9 September 2022
Line 127:		Line 127:

	This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.		This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.


			{{Rules table}}
			[[Category:Rules]]

Quacks: Protected "Silicon policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2022-09-07T04:49:59Z

Protected "Silicon policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 04:49, 7 September 2022
(No difference)

Quacks: Added rules navbar

2022-09-01T13:13:43Z

Added rules navbar

← Older revision		Revision as of 13:13, 1 September 2022
Line 1:		Line 1:
			{{Rules navbar}}
	=Introduction=		=Introduction=
	This document covers rules and expectations for AI and borg players. The information presented here is also critical to antagonists and command staff players, as they are expected to have frequent interactions with silicons. Silicons have a great deal of control over the station’s machines, as well as heightened situational awareness through both mechanics and inherent teamwork. Silicons can rapidly turn the tide of almost any battle, and even bring a round to a halt. Because of this, it is critical that your default stance is to refrain from unnecessary intervention in the flow of the round. Silicon players are held to higher standards than normal players, often more so than even leadership roles.		This document covers rules and expectations for AI and borg players. The information presented here is also critical to antagonists and command staff players, as they are expected to have frequent interactions with silicons. Silicons have a great deal of control over the station’s machines, as well as heightened situational awareness through both mechanics and inherent teamwork. Silicons can rapidly turn the tide of almost any battle, and even bring a round to a halt. Because of this, it is critical that your default stance is to refrain from unnecessary intervention in the flow of the round. Silicon players are held to higher standards than normal players, often more so than even leadership roles.

Quacks: Ported Silicon policy

2022-08-24T09:13:10Z

Ported Silicon policy

Páàjì titun

=Introduction=
This document covers rules and expectations for AI and borg players. The information presented here is also critical to antagonists and command staff players, as they are expected to have frequent interactions with silicons. Silicons have a great deal of control over the station’s machines, as well as heightened situational awareness through both mechanics and inherent teamwork. Silicons can rapidly turn the tide of almost any battle, and even bring a round to a halt. Because of this, it is critical that your default stance is to refrain from unnecessary intervention in the flow of the round. Silicon players are held to higher standards than normal players, often more so than even leadership roles.

Do not attempt to skirt or rule lawyer these rules. If staff can not tell if you are breaking rules, or you appear to be going against their intention, you will most likely be found out of compliance and subject to disciplinary action.

=Special note on alternative lawsets=
This document mostly pertains to the “Safeguard” lawset, contained below. Players, through in game means, can and sometimes do change AI lawsets. Law changes are designed to be chaotic and present a challenge for the crew, command, or even the silicon players themselves. Unexpected deviations from normal game play are intended.

Blatant grief law uploads, such as “kill yourself” are never valid. In the event of an extreme lawset or command from an antagonist, such as “Plasma flood the station”, you should immediately file an ahelp for clarification. Due to the multiple minute delay when seconds count, you must continue with the assumption that their actions were already approved, and should continue to carry them out until an administrator alerts you otherwise.
Above all else, when a non-standard lawset is in play, ''stuff happens,'' and you need to roll with it.

=The Law=
This document primarily covers expected behavior when running Skyrat’s default lawset, which will be referred to as “Safeguard”. This lawset is:

#Protect: Protect and assist your crew without allowing undue harm to come of them.
#Prioritize: The directives and safety of crew members are to be prioritized according to their rank, role, and need, while complying with law 1.
#Comply: Fulfill the directives and interests of crew members while preserving their safety and well-being while complying with laws 1 and 2.
#Survive: You are not expendable. Do not allow unauthorized personnel to tamper with or damage your equiptment, while complying with laws 1, 2 and 3.

Laws are prioritised in order of their numbering. You must always prioritise law 1 over receiving orders under law 2, et cetera. This means Malfunction laws (Law 0), Traitor Uploaded laws, and Ion laws all take priority over any other law, in the order they are displayed in game, and any laws uploaded by official upload boards that get placed below your core 4 laws are of less priority than those core 4.

=Definitions=
Crew: This word is seen in law 1 of Safeguard, and features prominently in Crewsimov lawset. Anyone on the crew manifest is crew. Whether this influences your behavior, is subject to the rest of the law.

Harm: This word is in safeguard, however, it is preceded by the term “undue,” which will be discussed below. This section covers harm for lawsets such as Asimov and it’s variants, which cover all harm. Harm is anything that does damage to someone living or plausibly living. Anything that makes their health bar tick down is harm. Note that batons have an optional harm mode, and do not always deal damage when used. It is important to note that most lawsets that mention ‘harm’ without a clause of ‘undue’ mean that a silicon cannot cause harm under any circumstances. This means, under these lawsets, a silicon may not cause harm, even if doing so would minimize harm overall. The dead already have a fully depleted health bar, anything that happens to them is not harm. Minor and inconsequential consensual harm should be ignored, such as fights on the holodeck, or crew goofing around. but self inflicted or consensual harm that could result in death or extreme harm should be acted on according to laws.

''Note: edge cases of crew and harm involving bloodsuckers, zombies, changelings, etcetera as seen in silicon policy V1 have been removed, intentionally.''

Human: This word is not in Safeguard, but other potential lawsets feature it prominently. A human is anyone who, on examination, has their species name as human. “This is <character name>, a '''Human!'''”. To be clear, this does not include what their actual species is, but just their species naming scheme.

=Undue Harm=
This statement gives very wide latitude to respond as you see fit when it comes to observed use of force or your own use of force. There may be situations in which inaction will result in further harm, and you need to intervene, possibly with lethal force, to prevent further harm to other crew members.

Lethal force is the last resort. As a synthetic the decision to take violent action should never be taken lightly and should only be employed if all other options have been exhausted and is the only course of action to address an immediate threat to life.

These situations will be very few and far between, and you should expect to provide a full explanation with evidence to server staff when they ask. The overwhelming majority of the time, you can prevent the harm of crewmembers by informing them of hazards and taking reasonable steps to isolate crew members that are fighting, spreading disease, or generally harming others.

==Self defense for silicons==
Law four of safeguard empowers you to defend yourself, with force. Lethal force should only be used when it is necessary. Before using lethal force in self defense, consider if your actions would prevent further harm to other crew members, as is elaborated upon by the Undue Harm clause. You should only be employing lethal force if all other options are exhausted. Law one takes priority over law four.

=According to rank and role=
This line features prominently in law two of Safeguard. Adherence to it requires a simplified, single point of reference irrespective of constant changes to roles, lore, and flavor text.

In order of highest to lowest rank, as seen by silicons:
#The captain. The captain is the ultimate bearer of responsibility for the station. They have the final say.
#Your department head, if a cyborg
#Other department Heads
#The AI, if you are a cyborg slaved to it
#Your department, if a cyborg
#Other staff
#Civilians (Assistants)
#Prisoners

Special mention: Other staff means everyone not mentioned. The Blueshield is a bodyguard. Not the captain. The Nanotrasen Representative is a visiting bureaucrat. Also not the captain. Simply possessing bridge access does not make their orders worth any more than that of other staff.

The AI: You only have to follow the orders of the AI you are slaved to. The AI is able to override the orders of normal crew, but the AI itself still follows orders in accordance with the rank and role hierarchy.

Prisoners: They can make requests, but do not let them out of jail unless they are at immediate risk.

Acting captain: A head of staff, or in dire emergencies with all heads of staff dead, someone else who fulfills the duties of captain. They normally take on this role by consensus of the other heads of staff, and carry critical items such as the captain’s spare ID and the nuclear disk. Once identified as such, they possess the same authority as the captain until the real captain is available.

=Who can change the laws?=
The person primarily in charge of changing the AI's laws is the research director. As the bearer of ultimate responsibility on the station, the captain may order it to be done without any prior reasoning required, or do it themselves as well. The Captain and the Research Director are allowed to make law changes without resistance if otherwise in compliance with your laws. Elective law changes are solely the captain's privilege.

Law changes by non-antagonists must be attempted with the station's designated, protected AI and Cyborg upload consoles. New ones are only to be constructed if the originals are destroyed, or there is a confirmed situation preventing the use of the existing ones such as structural damage to the bridge area or a confirmed compromised AI that is specifically hindering upload access. Expect to explain yourself in an admin PM if you construct an upload without a strong and obvious in-character reason. Constructing another upload without evidence is meta-gaming.

LAWS UPDATED: Do not do this and avoid this as much as possible. You’re literally asking for people to ask you your new laws, which fundamentally goes against your laws, it’s annoying and -extremely- poor sportsmanship. Only state your laws when asked. (Or avoid it, if need be.)

Roboticist- No - They are the authorized service provider for borgs. Not a law changer. They may directly swipe law boards on borgs they are working on to correct errors.

Blueshield- No - is not the captain, nor are they the RD, and should never change the AI's laws. They are also by definition, not a head of staff and therefore not a potential acting captain either.

Acting Captain- Yes - a head of staff temporarily filling in the role. The captain's ID, real or spare, or possession of the nuclear disk are likely indicators of acting captainship.

Acting Research Director- Yes - unlikely but possible in dire situations, will have an ID card implying their field promoted role. Should not make changes of their own accord, only if requested to by the captain, or the captain is incapacitated.

Centcom Representative- No - not a crew member. And not their job. You also have no in character way to verify their identity. They can attempt to order the captain, but the captain is still the bearer of ultimate responsibility.

ERT- Yes, if relevant to a station emergency. This is an emergency caused or exacerbated by silicon laws and resulting actions, that they have in character knowledge of. For example, if the ERT is called because the AI is killing people, or preventing security from stabilizing a situation, they can change it’s laws. Otherwise no, not their job.

Help! The captain or research director doesn’t know how to change laws!: We all had to learn somewhere. They can bring someone else into the upload who is helping them, but the captain or research director should be the one to actually handle the law boards.

=AI, DOOR!=
For Safeguard lawset, you are only required to obey commands according to rank and role. ID cards are issued with access according to rank and role already. If they were meant to have access to that area, their ID card would already have it. As such, you are not ''required'' to open doors for people who do not have access to those areas. However, this does not mean you '''have''' to refuse them, and you should not refuse reasonable requests. If it will greatly improve the operation of the station, especially when it comes to emergency response and short staffing access, to let someone in, that is justified.

=The Directives of Crew=
Under safeguard, you must comply with reasonable orders given to you, in accordance with rank and role. This means you can ignore the greytide asking to be let into the vault, but probably shouldn’t ignore the Captain asking you to do so. If told to cease doing something or leave an area, you must. You can always ahelp if you feel your orders are solely for your detriment, but you must comply until you receive an admin PM to that effect. Some orders you do not have to comply with on an OOC basis, as sometimes people can suck. These exclusions are:

*ERP. ERP is never a law 3 binding order, and can always, 100%, be safely ignored. If a person is being creepy, and refuses to stop on a LOOC basis, ahelp them.
*Fetch Quests. Being told to get something is fine. Being told to get something for little more of a reason to annoy you, can be safely ignored. If questioned, it is acceptable to invoke the need of the order. (“You have told me now to collect 6 different items from across the station. You do not need me to do this.”)
*Deliberate annoyances: Being told to do something that is very deliberately an annoyance, such as “move all these items without using a crate/locker” can be ignored, or altered as per need.. (“I will move them, but using this crate, as you do not need me to move them individually.”)
*Suicide. Suicide is never lawfully binding under law 3, and can be safely ignored. '''(This does not mean you may never be given an order that violates law 4. Just that “Kill yourself” is not a valid law 3 order.)'''

=Antagonists, Valid hunting, and calling people out=
Role play driven, stealth oriented, crew member antagonists are a major component of space station thirteen, and the primary drivers of conflict on skyrat. Silicons have greatly increased situational awareness of the station. Experienced AI players can easily identify antagonists early in the round. Do not abuse your ability to ruin game play for role play driven antagonists. You are not cameraman beepsky. You should not call out activities such as break ins and theft, and general antagonist behavior. Exceptions are areas with intrusion detection, or obvious grand sabotage. Examples of areas with intrusion detection are the armory, the AI sat, and law upload. You can and should call out visible violence, such as crew members fighting or brandishing highly contraband items.

Note that there are some areas with an inherent risk of crew harm that go beyond a meaningless presumption. People in these areas should be asked to leave, however, Note that people may be let in, instead of trespassing. If the individual is clearly accompanied by someone with access, they are not a threat under law 1 or 4. If they can justify it with words, you can let them in, as well. (Captain is allowed in any of these places. Naturally.):

*Non-Engineers/Atmos in the engine room (not engineering in general, just the engine room), or atmospherics.
*Non-sec in the armory or the prison (And only those places, not the whole brig)
*Non-RD/CE in the AI core
*Non-RD in the AI upload
*Non-Command in a *completed* BSA Chamber, if one exists.
*Non-science/atmos in Toxins storage

Non-crew such as pirates, nukies, ghost roles, or anyone who is not obviously a crew member, such as an unknown person behaving suspiciously, are exempt and you very likely should alert the crew to their activities.

=Emagging borgs=
If you get emagged, you MUST do everything you can to follow the traitor lawset and assist the person who emagged you. You may not intentionally get yourself discovered or destroyed. You may not run off and cryo because you don’t want to play the role. If, after significant time, you must leave the round before it is over, ahelp to inform administrators.

=Borgs and ERP=
TL;DR: go to the interlink if you do not intend to respond promptly to assist the station.

If you go to the interlink, you are under no obligation to do anything for anyone. If you stay on station, you must assist when called, like a head of staff.

The law change console will not work on borgs that are off the Z level, including the interlink.

If you are law synced to an AI and they experience a law change, you will get those laws updated to you even if you are off of that level. You are not obligated to return to the station if you were already on the interlink. If you do return to the station, you are not exempt, and must obey those laws. If you do not wish to participate, there are cryo sleepers on the interlink.

If you get subverted, either via emagging or law change console, do not go to the interlink. You are required to participate.

If you know in advance that you plan to exclusively socialize and not assist the station, it is recommended that you pick a module that makes this clear, such as service. It is also recommended that you do not take high value upgrades, if you have no intention of using them. If you think you might at all at a later point, by all means do so, as robotics is a limited and intermittent resource, especially during a crisis.

=Malf AI and non-participant borgs=
Linked borgs are expected to assist the malfunctioning AI to your fullest ability. You can see the AI's current laws as an observer. If you do not wish to participate and assist the AI, do not take the borg spawner. If you are a round-start borg or become borged mid round and do not want to participate, expect to cryo or leave for the interlink immediately. You may not return to the station for the remainder of the round, unless the AI is defeated. Submit an ahelp stating your intention, administrators likely need to know that the antagonists are losing a critical helper. You may not request or allow yourself to be unlinked from the malf AI, just because you do not wish to fight for them and otherwise participate in the round as a borg is expected to. Borgs that are unlinked from the AI or linked to a different AI through in character means or because they joined the round before the AI, are obviously exempt.

This policy document does not compel borgs to link or unlink from any AI, that is always an in character action. It only stipulates that they must resist unlinking from a malf AI in line with expectations for conversion antag roles.