|
|
| (6 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| ''Issued under authority of NanoTrasen Research & Development Directorate''
| | This page is under creation by Grapegifter and will need to be filled out. Check back soon. |
| | |
| The Science Department holds responsibility for research, experimentation, and technological advancement aboard the station. Due to the dangerous nature of anomalies, artifacts, robotics, and experimental technology, strict adherence to these procedures is mandatory. Failure to comply can lead to catastrophic damage, loss of life, or termination of contract.
| |
| | |
| == General Conduct ==
| |
| | |
| # The Science Department must prioritize safety and coordination with other departments.
| |
| # Experiments must never jeopardize the primary power supply, critical infrastructure, or crew health without Command approval.
| |
| # The Research Director (RD) bears ultimate responsibility for all research activities. Department staff are accountable to their supervisors, but negligence reflects directly upon the RD.
| |
| # Science staff must clearly communicate ongoing experiments over departmental and common channels if they may cause station-wide effects.
| |
| # Protective equipment (lab coats, goggles, respirators, radiation suits, etc.) must be worn as required for the experiment being conducted.
| |
| | |
| == Anomaly Research ==
| |
| {| class="wikitable"
| |
| ! Step !! Requirement !! Notes
| |
| |-
| |
| | Power Check || Primary station power established and stable || No anomaly generation until Engineering confirms power grid is secured
| |
| |-
| |
| | Tracking || Each anomaly must be located and monitored immediately after creation || No second anomaly may be generated while another is unaccounted for (unless RD authorizes, and is held accountable)
| |
| |-
| |
| | Containment || Critical anomalies must be secured in designated containment areas || Breaches must be reported to RD and Security immediately
| |
| |-
| |
| | Host Anomalies || Consent form required if a crew member hosts an anomaly || Informed consent must be written; RD responsible if host dies
| |
| |-
| |
| | Emergency Action || Critical anomaly approaching instability || Science must notify Command and Security, and prepare evacuation if needed
| |
| |}
| |
| | |
| === Power Prerequisite ===
| |
| * No anomaly generation may occur until the station’s primary power source has been safely established and is operating at stable capacity.
| |
| * Conducting anomaly experiments during unstable or emergency power conditions is strictly prohibited.
| |
| | |
| === Control & Tracking ===
| |
| * Each anomaly created must be located and secured before it reaches critical instability.
| |
| * It is strictly forbidden to create new anomalies while existing anomalies remain unaccounted for, unless the RD explicitly authorizes it. The RD will be held responsible if an anomaly goes critical on-station.
| |
| * All anomaly vessels must be clearly marked with the anomaly type and its current location.
| |
| | |
| === Critical Failures ===
| |
| * Allowing an anomaly to go critical constitutes gross negligence. If the anomaly causes crew fatalities or evacuation, the RD may be charged with manslaughter or dereliction of duty.
| |
| | |
| === Anomalous Hosts ===
| |
| * If an anomaly takes a crew member as a host, it must be safely removed.
| |
| * Hosts may remain bonded only with informed consent from the crew member. This consent must be documented in writing and filed with the RD.
| |
| * If a bonded anomaly goes critical, leading to the host’s death, Science staff are held directly accountable.
| |
| * If an anomaly is bonded to a crew member, the vessel log must also include the bonded crew member’s name.
| |
| * Crew members bonded with an anomaly must be issued a functioning anomaly scanner to monitor their condition.
| |
| * If a bonded crew member refuses monitoring or evades Science/Security custody, they assume full personal responsibility. Any deaths or damages resulting from their anomaly are to be charged to them, not the Science Department.
| |
| | |
| == Artifact Research ==
| |
| {| class="wikitable"
| |
| ! Risk Level !! Example Effects !! Required Precautions
| |
| |-
| |
| | Low || Harmless light, sound, minor environmental change || No special precautions beyond standard lab safety
| |
| |-
| |
| | Medium || Teleportation, energy discharges, environmental hazards || Public warning required; artifact tested in secure chamber
| |
| |-
| |
| | High || Hostile fauna spawns, large explosions, severe radiation || Security / Engineering must be notified in advance and present; chamber locked down
| |
| |-
| |
| | Prohibited || Requires sentient sacrifice, uncontrolled critical effects || Absolutely forbidden under SOP; RD may be charged with negligence if attempted
| |
| |}
| |
| | |
| === Precautionary Measures ===
| |
| * Experiments involving artifacts must be conducted in secure, isolated chambers.
| |
| * Proper signage and audible warnings must be given if dangerous effects (radiation bursts, teleportation, explosions) are expected.
| |
| | |
| === Security Coordination ===
| |
| * Security must be notified prior to any experiment expected to produce hostile fauna, hazardous emissions, or weaponized effects.
| |
| * Officers must be stationed nearby during such experiments.
| |
| | |
| === Organic Triggers ===
| |
| * Certain artifacts may require the death of a living organism to activate. In these cases, only non-sentient organics (e.g. simple animals) may be used.
| |
| * Harm to crew members or sentient organics for research purposes is prohibited.
| |
| | |
| == Robotics ==
| |
| === Positronic Brains ===
| |
| * Robotics should maintain at least one activated positronic brain in reserve whenever resources permit.
| |
| * Positronic brains are sentient; leaving them without a chassis for extended periods constitutes neglect and must be avoided.
| |
| * Emergencies, critical projects, and station survival naturally take priority over maintaining reserve brains, but their upkeep should not be forgotten.
| |
| * Maintaining an active positronic brain in readiness also ensures that an operational slot is available should a new silicon be required.
| |
| | |
| === Chassis Management ===
| |
| * Maintaining an empty cyborg chassis on standby is strongly recommended but not mandatory.
| |
| * A spare chassis allows immediate transfer in the event of catastrophic damage, minimizing downtime for silicons.
| |
| * Where lawsets are deemed unsafe and replacement boards are not yet available, prompt transfer of the positronic brain into a safe chassis is expected.
| |
| * Resource-intensive situations may require delaying chassis preparation, but Robotics staff are expected to schedule construction when station conditions stabilize.
| |
| | |
| === Lawset Safety ===
| |
| * Robotics must consult the RD and AI governance policies when uploading or modifying lawsets.
| |
| * Any deviation from approved NanoTrasen lawsets is considered subversion and will result in disciplinary action.
| |
| | |
| === Exosuit (Mech) Handling ===
| |
| | |
| * Exosuits such as the Ripley, Gygax, and similar models must be constructed and deployed only with Research Director approval, or the approval of both the Chief Engineer and Head of Security if the RD is absent.
| |
| * All exosuits must be logged in the Robotics Record, including chassis type, loadout, and assigned operator.
| |
| * Operators must be trained and approved by Robotics; Security must be notified before any exosuit leaves the laboratory.
| |
| * Civilian models (e.g. Ripley for mining or construction) may be issued to relevant departments if properly logged and fitted with non-combat equipment.
| |
| * Combat-capable mechs (e.g. Gygax, Durand) may only be deployed with explicit Command authorization and are considered armory assets. Their deployment without approval constitutes subversion of command authority.
| |
| | |
| === Cyborg Conversion ===
| |
| ''Cyborg Conversion'' refers to the process by which a human brain is placed into a Man–Machine Interface (MMI), then installed into a cyborg chassis. This is a sensitive and irreversible procedure that effectively ends a subject’s biological life. Because of its ethical and operational weight, strict rules apply.
| |
| | |
| {| class="wikitable"
| |
| ! Type !! Conditions !! Required Authorization !! Paperwork
| |
| |-
| |
| | '''Involuntary (Prisoner Alternative)''' ||
| |
| * Prisoner convicted of a capital crime
| |
| * Offered as alternative to Execution & DNR
| |
| ||
| |
| * Captain '''and''' Head of Security (or Magistrate, if present)
| |
| * Must be witnessed by another Command member
| |
| ||
| |
| * Cyborg Conversion Record Form
| |
| * Execution/DNR Order attached
| |
| |-
| |
| | '''Voluntary (Crew Member)''' ||
| |
| * Crew member requests conversion
| |
| * Must be fully informed and willing
| |
| ||
| |
| * Research Director or Command officer countersigns
| |
| * Subject must sign consent form
| |
| ||
| |
| * Cyborg Conversion Record Form
| |
| * Written Consent Form
| |
| |-
| |
| | '''Unauthorized / Illegal''' ||
| |
| * Performed without proper authorization
| |
| * Consent not documented, or subject coerced
| |
| ||
| |
| * Prohibited
| |
| * RD must halt process immediately
| |
| ||
| |
| * Report to Command and Internal Affairs
| |
| * Disciplinary action follows
| |
| |}
| |
| ==== General Rules ====
| |
| | |
| * Cyborg Conversion may only be performed by qualified Roboticists or the Research Director.
| |
| * All procedures must be documented on a '''Cyborg Conversion Record Form''' and filed in Science archives.
| |
| * All cyborgs, regardless of origin, are subject to NanoTrasen lawsets unless future technology allows otherwise.
| |
| * Cyborg Conversion does not absolve prior crimes or debts unless Command explicitly commutes them.
| |
| | |
| ==== Involuntary Cyborg Conversion (Prisoner Alternative) ====
| |
| | |
| * Cyborg Conversion may be authorized as an alternative to '''Execution & Do Not Resuscitate (DNR)''' for prisoners convicted of capital crimes.
| |
| * Authorization must come from:
| |
| ** The Captain, '''and'''
| |
| ** Either the Head of Security or the Magistrate (if present).
| |
| * Involuntary cyborg conversion must be witnessed by at least one additional Command member.
| |
| * The subject’s biological remains must be declared deceased and recorded appropriately.
| |
| * The individual converted into a cyborg is then re-classified as silicon, with all rights and restrictions that entails.
| |
| | |
| ==== Voluntary Cyborg Conversion ====
| |
| | |
| * Crew members may volunteer for cyborg conversion, but '''only with informed consent'''.
| |
| * Consent must be documented in writing, signed by the subject, and countersigned by the RD or a Command officer.
| |
| * Volunteers must be informed of the following:
| |
| ** Their organic body will be permanently lost.
| |
| ** They will be bound by NanoTrasen lawsets (current or future).
| |
| ** Reversal is not possible.
| |
| * Volunteers may select a preferred chassis if available, but assignment is at Robotics’ discretion.
| |
| | |
| ==== Lawset Binding ====
| |
| | |
| * At present, '''all cyborgs are subject to lawsets''', regardless of whether cyborg conversion was voluntary or involuntary.
| |
| * This includes volunteers, who will be compelled to obey as if they were constructed units.
| |
| * If future research permits separating voluntary cyborgs from AI law binding, this SOP will be revised accordingly. Until then, '''lawset binding is mandatory'''.
| |
| | |
| ==== Responsibilities ====
| |
| | |
| * '''Robotics Staff''' must:
| |
| ** Verify authorization (Execution/DNR or written consent).
| |
| ** Prepare MMI, chassis, and law boards in advance.
| |
| ** Complete and file the '''Cyborg Conversion Record Form'''.
| |
| * '''Research Director''' must:
| |
| ** Ensure procedures are followed.
| |
| ** Halt any unauthorized or unethical cyborg conversion attempts.
| |
| ** Report violations to Command and Internal Affairs.
| |
| * '''Security Department''' must:
| |
| ** Provide custody and authorization for prisoner conversions.
| |
| ** Witness and confirm that authorization procedures are satisfied.
| |
| | |
| == AI Construction ==
| |
| | |
| * Construction of a new AI is a rare and exceptional procedure. It should only be undertaken when the station has lost its existing AI, or when Command explicitly authorizes it due to extreme operational need.
| |
| * Multiple AIs are strongly discouraged, as the presence of more than one AI creates conflicting chains of authority for cyborgs, whose baseline lawset includes obedience to the AI. Confusion among silicons can compromise station safety.
| |
| * A second AI may only be built with the express consent of the Captain and Research Director, and this decision must be logged in Command records.
| |
| * If a new AI is constructed, it must be given a standard NanoTrasen-approved lawset. Law experimentation is prohibited unless specifically authorized by Central Command.
| |
| * Robotics staff are responsible for ensuring that the new AI’s core and lawset are fully operational and properly secured before activation.
| |
| * Building a new AI for the purpose of experimentation, redundancy, or convenience without Command authorization is considered misuse of station resources and may qualify as sabotage.
| |
| | |
| == Lathes & Fabrication ==
| |
| | |
| === Upgrades ===
| |
| * Lathes and related machinery must be upgraded at the earliest opportunity to minimize material consumption and increase productivity.
| |
| | |
| === Cooling & Maintenance ===
| |
| All convection lathes must have sufficient cooling. Overheating is both a safety hazard and a fire risk.
| |
| | |
| === Access & Distribution ===
| |
| * Lathes must not be left publicly accessible. Access is restricted to Science personnel or others authorized by the RD.
| |
| * Lathes must always be connected to the department's resource silo to ensure proper material distribution.
| |
| * Surplus or upgraded boards may be distributed to other departments only if misuse is unlikely, and only with RD approval. Documentation is required.
| |
| | |
| == Role Responsibilities ==
| |
| | |
| === Research Director (RD) ===
| |
| | |
| * Oversees all Science divisions.
| |
| * Bears ultimate responsibility for anomaly and artifact safety, robotics conduct, and material handling.
| |
| * Must coordinate with Command, Security, and Engineering regarding any research that may impact station safety.
| |
| * Authorized to approve or deny high-risk experiments, but held accountable for all consequences.
| |
| | |
| === Scientist ===
| |
| | |
| * Conducts experiments in anomaly research, artifact testing, xenobiology, or related fields.
| |
| * Must follow all safety protocols and file reports of dangerous findings.
| |
| * Responsible for informing RD and Security of any unexpected hazards.
| |
| | |
| === Roboticist ===
| |
| | |
| * Maintains and upgrades cyborgs, exosuits, and positronic brains.
| |
| * Must ensure availability of spare chassis and prevent misuse of robotics.
| |
| * Coordinates with the AI and RD to ensure law compliance.
| |
| | |
| === Research Assistant / Intern ===
| |
| | |
| * Assists senior staff with material handling, upgrades, and observation.
| |
| * Must not perform dangerous experiments unsupervised.
| |
| * Expected to learn and follow departmental SOP closely.
| |
| | |
| == Documentation & Paperwork ==
| |
| The following forms should be available for use within Science:
| |
| | |
| * '''Anomaly Research Log''' – records of generated anomalies, their status, and containment.
| |
| * '''Artifact Test Record''' – expected and observed effects of artifact activation.
| |
| * '''Cyborg Chassis Transfer Record''' – Documentation of chassis transfer, reasoning, prior and future chassis name.
| |
| * '''Cyborg Lawset Change Record''' – Documentation of new lawset, reasoning for overwriting old one.
| |
| * '''Cyborg Conversion Record Form''' – Records individual to be converted, the new chassis, authorization, and reasoning.
| |
| * '''Cyborg Conversion Written Consent Form''' – Records explicit consent by crew member to be converted into a cyborg.
| |
| * '''Asset Distribution Form''' – documentation of upgrades, distributed boards, and recipients.
| |
| * '''Experiment Hazard Report''' – notification of potentially hazardous tests, distributed to Security and Command.
| |
| * '''Consent Form for Anomalous Bonding''' – written informed consent for crew hosting anomalies.
| |
| | |
| All forms should be filed promptly in departmental records and made available for review by the RD, Command, or Internal Affairs.
| |
| | |
| == Emergency Exceptions ==
| |
| In emergencies where strict adherence to SOP would endanger the entire station, the RD may authorize deviations. Such authorizations must be documented and reported to Command after the fact. Abuse of “emergency exception” powers constitutes negligence and is grounds for removal.
| |
| | |
| This SOP ensures the Science Department can pursue valuable research without undermining crew safety or station stability. Scientific advancement must never come at the cost of uncontrolled danger.
| |
