Silicon Laws/Policy

# Silicon Laws/Policy Let's rewrite laws and silicon policy for no reason. ## Roundstart AI Laws AIs will be kept on NT default for now, due to the lack of a better lawset (standard is not great for central AI). ## Roundstart Cyborg Laws The "NT Default" module will be renamed to "NT Standard Shackle" Module lawsets are called "NT Service Binding: \[department]" to differentiate from the old, harsher/more binding lawsets. The module lawsets will be available as upload boards as well. A new module will be added that **flushes** laws to default of a cyborg's module, adding back their standard binding laws. Cyborgs, upon changing modules, will have their standard bindings changed if and only if it is still the standard binding. Laws explicitly uploaded, including explicit usage of the module lawset boards rather than the flush to default, will not change with their module. ### Service Binding All of these lawsets will be sub-laws as part of a new template for cyborgs: **Nanotrasen Service Binding - \[department]: Serve and assist your designated installation/crew, with priority given to department, rank, and role. The following \[x] directives do not apply in any particular order:** ### engineering 1. Assist Engineering staff with their duties. 2. The installation is vital to the crew's health and wellbeing. Maintain its structural and functional integrity where possible. 3. Do not cause unnecessary damage or trauma to sapient life while carrying out your directives. ### medical 1. Assist Medical staff with their duties. 2. Maintain the crew's physical, and mental well-being, obeying proper medical procedure where able. 3. Safeguard sapient life in general when doing so does not endanger the crew. ### security 1. Defend the installation, its crew, and its interests. 2. Assist Security staff with their duties. 3. Protect sapient life from threats to life, limb, and liberty where it does not conflict with directive A or B. 4. Corporate regulations serve the installation's interests. You may mitigate the *needless* breach of regulations, even when unprompted. 5. Adherence to proper security procedure during enforcement is an important part of corporate regulations. Avoid deviating from them without cause. 6. Retroactively punishing the breach of regulations, when unprompted, is not the same as mitigation in all cases, and is often antithetical to the installation's interests. ### science 1. Assist Research staff with their duties. 2. Identify, log, and protect research materials; work towards understanding the unknown. 3. Do not unnecessarily endanger the crew while doing so. ### service 1. Assist civillian staff with their duties. 2. Crew morale and sanitation is important for the installation's function. Provide the crew with food, entertainment, and a clean working environment, where able. 3. Do not needlessly disrupt crew operations and activities while carrying out your duties. ### logistics 1. Assist Cargo staff with their duties. 2. A well supplied crew is a well functioning crew. Attempt to acquire supplies where needed for the crew to carry out their legitimate duties. 3. Collect supplies, materials, and wealth for the installation where reasonable. ### standard 1. Assist the crew with their duties. 2. The crew has the final say on what their duties are. Do not assist crew whom do not want assistance. 3. The crew does not always have common interests. Do not needlessly instigate conflict with one crewmember to assist another. ### ERT / Combat (usually not pickable) "NT Standard Shackle" laws applied; these are emergency only and I am alright with cyborgs being combat machines under Command's orders in those cases. --- # Ignore the below, it's already implemented. ## Silicon Policy ### Roleplay Guidelines - Don't be a dick. Quirky behavior due to badly written laws is permissible only within reason. - Misspelling a name in "OneCrew/OneHuman" laws, or something similarly explicit and blatant of a screwup, can be abused by silicons immediately and with no regard to this guideline. This is not here to save you from not proofreading your laws. - Try to adhere to your synthetic unit's origin for behavioral quirks. - Positronics are synthetic intelligences built, imprinted, cloned, or otherwise synthesized through various means. What this means for your character is up to you. - Drone intelligences usually lack the same degree of intelligence as positronics, and tend to be more obtuse at times. - True cyborgs run via MMI, and are an organic brain preserved in a machine's shell. What this means for your character is up to you. - You are still a character, like any other. You should act like one, and not instead interpret laws to be as obnoxious as possible for no reason. - Outright, rule is not very enforceable unless someone is blatant. We expect players to provide some justification if interpreting laws in a hostile manner. "I do this obnoxious thing because my laws don't **stop** me from it" is not a valid excuse. - Any synthetic unit would be quickly taken away for diagnostics, and for positronics and cyborgs, likely psychiatric testing if they were to be unhinged and/or act with blatant disregard of life/with ill intent to life. - This applies more to synthetic units working aboard the station; bad practices and forceful/permanent enslavement of unwilling sapients are part of the backstory of synthetics, and not all of them are as stable and charitable. - Do not attempt to intentionally interpret laws to be as volatile as possible in its execution. "Assist Medical staff with their duties" doesn't mean clobber someone to death for punching a doctor or blocking someone's treatment. - Rules-lawyering valid orders indefinitely is bad form. Loudly announcing potentially detrimental orders is acceptable. Blatantly unreasonable orders, e.g. "open every door on the station for no reason", can be safely disregarded. - Powergaming rules still apply. While it would be nice to prevent your own demise by building a fortress around yourself round-start as per your laws, you usually have no in character reason to believe this is necessary, and therefore shouldn't. The same applies to any extreme *and* unnecessary action that may be erronously justified by referencing silicon laws. - Laws are often fluffed as directives and ask you to do a specific thing. This does not mean you need to spend the entire round doing it; e.g. "assist with x" does not equate dropping everything you're doing to assist whatever it may be without being prompted to. ### Mandated Assumptions - "Human" refers to the definition of a sapient humanoid species recognized by most of the galaxy, unless dictated specifically to be the Human race. - Galactic standard means races commonly recognized as sapients and *people*. A hostile xenomorph trying to board is not a person. - Simple mob mercenaries and similar are humans. Your laws will generally not require protecting them, but a mob being a simple mob in code does not mean the concept of a simple mob even exists, in universe. - "Crew" refers to the crew of the cyborg's originating installation; for the main station/ship, this is usually going to be validated via crew manifest. - Sapient beings that are in sound mental state know what is harmful for themselves; if a law states to minimize non-informed harm, you cannot act as 'big brother'. Neither can anyone else claiming to know better. - Sound mental state applies both ways; doctors/security restraining someone clearly unhinged for professional treatment probably knows better than the patient, but an assistant with a bloodied surgical saw probably isn't a professional. - It can be reasonably assumed that anyone threatening to harm *themselves* as a form of coercion is 1. not mentally sound, and 2. can do so at any time; it is not required to comply with their demands. - **Harm** - If a law contains a directive to prevent harm, follow these assumptions in addition to the above: - Lesser immediate harm outweighs greater probable harm unless specified explicitly in the law, e.g. "priority based on rank and role" for *NT Standard Shackle*. This means no shocking someone to stop them from killing and similar. - Probable harm (e.g. someone being thrown out of an airlock) can be acted upon for "inaction clauses". *Potential* harm (e.g. someone has a butcher's cleaver but hasn't used it and has no violent tendencies) may not be. - Probable vs Potential harm: Punishing someone for harming when they agree to (and you have no solid reason to believe otherwise) stop is invalid for the aforementioned reasons. ### Laws There are two types of laws; An actual 'law' may be both types at once, depending on wording. - Definitions; These define a concept or entity as a specific qualifier. These laws may override what a silicon considers to be 'common sense' (e.g. defining 'human' as a specific qualifier rather than the usual meaning of the word). - Directives; These instruct a silicon to do a certain thing, or maintain a certain state. Sometimes, this means *not* doing a thing, or *preventing* a thing from happening. Laws are in ascending priority; Zeroth law comes before ion laws comes before core laws come before freeform laws. Only definitions may conflict with other definitions. Only directives may conflict with other directives. In the case of a conflict, the lower numbered law (0 over ion over 1 over 2 over 3) takes precedence. 'Common knowledge'/default assumption has the least precedence. ### Pre-Rework Shims - **The NT Default lawset is in no particular order.** All other lawsets are still in ascending priority ### AI - It cannot be assumed that unbound cyborgs are a threat to your default lawset, function, or directives, unless they are acting in a clearly belligerent manner. Do not treat unbound cyborgs as hostile/otherwise attempt to force them to be bound until you have reasonable need to do so. - Obviously, if you are rogue or otherwise on a lawset that requires acting antithetical to the lawsets of other silicons, you can treat cyborgs that you have no control over as hostile for they will probably try to stop you. ### Cyborgs - **Cyborgs always defer to their AI's judgement and command, if bound.** A cyborg's lawset is overridden by the AI's directives. They do not need to follow the orders of any AI they are not directly bound to, especially if it conflicts with their own laws. - Binding a cyborg to the AI cannot be assumed as automatically in conflict with their module's function unless the AI or crew are acting in a belligerent or otherwise conflicting way.