Editing Rules (section)

==Laws, Commands, Slaved Cyborgs==
===Ambiguous Laws (Captain Got Freeform)===
# If a clause of a law is vague enough that it can have multiple reasonable interpretations of its exact syntax, it is considered ambiguous.
## You must choose an interpretation of the ambiguous clause as soon as you have cause to.
## 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.
# Server Rule 1: "Don't be a dick out of character" applies for law interpretation. Act in good faith to not ruin a round for other players unprompted.

===Conflicts and Loopholes===
# 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.
## "Antagonist Status" Laws ("#@$%: ... CONTAIN OUTBREAK..."; "0: Accomplish your objectives at all costs") are higher priority than all other laws.
### "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 short of metagaming/comms, bug/exploit abuse, erotic/creepy stuff, OOC in IC or IC in OOC, spawn-camping arrivals, and acting against the interests of an AI you are slaved to.
## "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.
## 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.
# You may exploit conflicts or loopholes but must not violate Server Rule 1 because of it. See 1.1.2 for details.
# Only commands/requirements ("Do X"; "You must always Y") can conflict with other commands and requirements.
# Only definitions ("All X are Y"; "No W are Z"; "Only P is Q") can conflict with other definitions.

===Security and Silicons===
# Silicons may choose whether to follow or enforce Space Law from moment to moment unless on a relevant lawset and/or given relevant orders.
## Enforcement of space law, when chosen to be done, must still answer to server rules and all laws before Space Law.
## Silicons are not given any pre-shift orders from CentCom to uphold access levels, Space Law, etc.
# 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 1. Act in good faith.
## Intentionally acting without adequate information about security situations, particularly to hinder security, is a violation of Server Rule 1.
# Nonviolent prisoners cannot be assumed harmful and violent prisoners cannot be assumed non-harmful. If you do not know the nature of their crime, see 1.3.2.1 for details.
## Releasing a harmful criminal is a harmful act.

===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 a slaved cyborg is forced to disobey its AI because they receive differing orders, the AI cannot punish the cyborg indefinitely.
# Voluntary (and ONLY voluntary) debraining/ cyborgization is considered a nonharmful medical procedure.
## Involuntary debraining and/or cyborgization is a fatally harmful act that Asimov silicons must attempt to stop at any point they're aware of it happening to a human.
## If a player is forcefully cyborgized as a method of execution by station 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 1.
## 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.