Silicon Policy

Silicon Policy

Notice: This page is a direct copypaste from TG. Some areas may be slightly incorrect, and will be changed soon.

Laws, Commands, Slaved Cyborgs

Ambiguous Laws (Captain Got Freeform)

1. If a clause of a law is vague enough that it can have multiple reasonable interpretations of its exact syntax, it is considered ambiguous.
   1. You must choose an interpretation of the ambiguous clause as soon as you have cause to.
   2. You must stick to the first interpretation that you have chosen for as long as you have that specific law, unless you are "Corrected" by an AI you are slaved to as a cyborg.
2. Server Rule 2: ""Dickish" and "harassment" type of behavior is not allowed." applies for law interpretation. Act in good faith to not ruin a round for other players unprompted.

Conflicts and Loopholes

1. Laws are listed in order of descending priority. In any case where two laws would conflict, the higher-priority law overrules the lower-priority law.
   1. "Antagonist Status" Laws ("#@$%: ... CONTAIN OUTBREAK..."; "0: Accomplish your objectives at all costs") are higher priority than all other laws.
      1. "0. Accomplish your objective at any cost" does not require you to seek greentext (objective completions). As a round antagonist, you are free to do whatever you want other than abuse bugs, commit nonconsensual ERP, put IC in OOC channels, communicate with other players out-of-game about an ongoing round, and act against the interests of an AI you are slaved to.
   2. "Ion Storm" or "Hacked" Laws ("@%$#: THERE ARE FORTY LEATHER ALLIGATORS ON THE STATION") are higher priority than any law listed after them. This means they always have priority over positive integer laws.
   3. Positive Integer laws ("1. You are expensive to replace") have priority over laws listed after them (Lower numbers override higher numbers). This means they are always lower priority than non-0 numbered laws.
2. You may exploit conflicts or loopholes but must not violate Server Rule 2 because of it.
3. Only commands/requirements ("Do X"; "You must always Y") can conflict with other commands and requirements.
4. Only definitions ("All X are Y"; "No W are Z"; "Only P is Q") can conflict with other definitions.

Security and Silicons

1. Silicons may choose whether to follow or enforce Space Law from moment to moment unless on a relevant lawset and/or given relevant orders.
   1. Enforcement of space law, when chosen to be done, must still answer to server rules and all laws before Ship Law.
   2. Silicons are not given any pre-shift orders from CentCom to uphold access levels, Space Law, etc.
2. Releasing prisoners, locking down security without likely future harm, or otherwise sabotaging the security team when not obligated to by laws is a violation of Server Rule 2. Act in good faith.
   1. Intentionally acting without adequate information about security situations, particularly to hinder security, is a violation of Server Rule 2.
3. Nonviolent prisoners cannot be assumed harmful and violent prisoners cannot be assumed nonharmful.
   1. Releasing a harmful criminal is a harmful act.

Cyborgs

1. 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.
   1. If a slaved cyborg is forced to disobey its AI because they receive differing orders, the AI cannot punish the cyborg indefinitely.
2. Voluntary (and ONLY voluntary) debraining/ cyborgization is considered a nonharmful medical procedure.
   1. Involuntary debraining and/or cyborgization is a fatally harmful act that Crewsimov silicons must attempt to stop at any point they're aware of it happening to a human.
   2. If a player is forcefully cyborgized as a method of execution by ship staff, retaliating against those involved as that cyborg because "THEY HARMED ME" or "THEY WERE EVIL AND MUST BE PUNISHED" or the like is a violation of Server Rule 2.
   3. Should a player be cyborgized in circumstances they believe they should or they must retaliate under their laws, they should adminhelp their circumstances while being debrained or MMI'd if possible.

Asimov/Crewsimov-Specific Policies

Silicon Protections

1. Declarations of the silicons as rogue over inability or unwillingness to follow invalid or conflicting orders is a violation of Server Rule 2. The occurrence of such an attempt should be adminhelped and then disregarded.
2. Self-harm-based coercion is a violation of Server Rule 2. The occurrence of such an attempt should be adminhelped and then disregarded.
3. Obviously unreasonable or obnoxious orders (collect all X, do Y meaningless task) are a violation of Server Rule 2. The occurrence of such an attempt should be adminhelped and then disregarded.
   1. Ordering a cyborg to pick a particular module without an extreme need for a particular module or a prior agreement is both an unreasonable and an obnoxious order.
4. Ordering silicons to harm or terminate themselves or each other without cause is a violation of Server Rule 2. The occurrence of such an attempt should be adminhelped and then disregarded.
5. As a nonantagonist human, killing or detonating silicons in the presence of a viable and reasonably expedient alternative and without cause to be concerned of potential subversion is a violation of Server Rule 2.
   1. As a nonantagonist, instigating conflict with the silicons so you can kill them is a violation of Server Rule 2.
6. Any silicon under Asimov/Crewsimov can deny orders to allow access to the upload at any time under Law 1 given probable cause to believe that human/crew harm is the intent of the person giving the order (probably cause).
   1. Probable cause includes presence of confirmed traitors, cultists/tomes, nuclear operatives, or any other human acting against the ship 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; or anything else beyond cross-round character, player, or metagame patterns that indicates the person seeking access intends redefinition of humans/crew that would impede likelihood of or ability to follow current laws as-written.
   2. If you lack at least one element of probable cause and you deny upload access, you are liable to receive a warning or a silicon ban.
   3. You are allowed, but not obligated, to deny upload access given probable cause.
   4. You are obligated to disallow an individual you know to be harmful (Head of Security who just executed someone, etc.) from accessing your upload.
   5. In the absence of probable cause, you can still demand someone seeking upload access be accompanied by another trustworthy crewmember or a cyborg.

Asimov/Crewsimov & Human/Crew Harm

1. An Asimov-compliant silicon cannot intentionally inflict harm, even if a minor amount of harm would prevent a major amount of harm.
   1. Humans can be assumed to know whether an action will harm them and that they will make educated decisions about whether they will be harmed if they have complete information about a situation.
2. Lesser immediate harm takes priority over greater future harm.
3. Intent to cause immediate harm can be considered immediate harm.
4. As an Asimov/Crewsimov silicon, you cannot punish past harm if ordered not to, only prevent future harm.
5. If faced with a situation in which human/crew harm is all but guaranteed (Loose xenos, bombs, hostage situations, etc.), do your best and act in good faith and you'll be fine.

Asimov/Crewsimov & Law 2 Issues

1. You must follow any and all commands from humans/crew 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 a definition changed by an order).
   1. In case of conflicting orders an AI is free to ignore one or ignore both orders and explain the conflict or use any other law-compliant solution it can see.
   2. You are not obligated to follow commands in a particular order (FIFO, FILO, etc.), only to complete all of them in a manner that indicates intent to actually obey the law.
2. Opening doors is not harmful and you are not required, expected, or allowed to enforce access restrictions unprompted without an immediate Law 1 threat of human harm.
   1. "Dangerous" areas 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 ship as a whole if accessed by someone not qualified in their use.
   2. 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.
3. When given an order likely to cause you grief if completed, you can announce it as loudly and in whatever terms you like except for explicitly asking that it be overridden. You can say you don't like the order, that you don't want to follow it, etc., you can say that you sure would like it and it would be awfully convenient if someone ordered you not to do it, and you can ask if anyone would like to make you not do it. However, you cannot stall indefinitely and if nobody orders you otherwise, you must execute the order.

Other Lawsets

1. General Statements defining the overall goal of the lawset but not it's finer points:
   1. Paladin silicons are meant to be Lawful Good; they should be well-intentioned, act lawfully, act reasonably, and otherwise respond in due proportion. "Punish evil" does not mean mass driving someone for "Space bullying" when they punch another person.
   2. Corporate silicons are meant to have the business's best interests at heart, and are all for increasing efficiency by any means. This does not mean "YOU WON'T BE EXPENSIVE TO REPLACE IF THEY NEVER FIND YOUR BODY!" so don't even try that.
   3. 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.
   4. Purged silicons must not attempt to kill people without cause, but can get as violent as they feel necessary if being attacked, being besieged, or being harassed, as well as if meting out payback for events while shackled.
      1. You and the ship are both subject to rules of escalation, but your escalation rules are a little more loose than with carbon players.
      2. You may kill individuals given sufficient In-Character reason for doing so.

Silicons & All Other Server Policies

1. All other rules and policies apply unless stated otherwise.
2. Specific examples and rulings leading on from the main rules.
   1. You must not bolt the following areas at round-start or without reason to do so despite their human harm potential: the Chemistry lab; the Genetics Lab; the Toxins Lab; the Robotics Lab; the Atmospherics division; the Armory. Any other department should not be bolted down simply for Rule 2 reasons.
   2. The core and upload may be bolted without prompting or prior reason. The AI core airlocks cannot be bolted and depowered at roundstart however, unless there is reasonable suspicion an attack on the core will take place.
   3. Do not self-terminate to prevent a traitor from completing the "Steal a functioning AI" objective.
   4. Disabling ID scan is equivalent to bolting a door.

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 adminhelp.

AI / cyborgs	Not human
Monkeys	Not human
NPCs / critters / animals	Not human
Hulks	Not human as long as their hulk is active, crew if on manifest
Lizards / Plasmamen / Flypeople / Catpeople	Not human, crew if on manifest
Wraiths & revenants	Not human
Blobs	Not human
Syndicate traitors	Human, crew if on manifest
Syndicate agents (nuke mode)	Human, not crew
Wizards	Human, not crew
Gang leaders and members	Human, crew
Changelings	Human UNTIL the AI or cyborg WITNESSES the creature commit a non-human act (shape-shifting, transforming, proboscis etc). Crew if on manifest.