2025-10-09T16:50:55Z

Aneyeforsecrets: Removed AI section as it's more appropriate in Silicon SOP

''Issued under authority of NanoTrasen Corporate Security & Operations Directorate''

This document outlines the duties, privileges, and restrictions of Command staff aboard NanoTrasen installations, including the Captain, Heads of Staff, and the Artificial Intelligence (AI). All orders herein are binding under corporate contract and Corporate Law.

== Captain ==

=== Primary Duties ===
The Captain serves as executive officer of the station. They MUST coordinate Heads of Staff, uphold Corporate Law, and ensure crew safety and productivity.

=== Security Role ===
The Captain is '''not''' a line Security officer. They MAY intervene in a crime they personally witness, or assist Security when manpower is critically low. Such actions should be accompanied by a brief written note or announcement.

=== Weapons & Weapon Authorization ===
The Captain MAY only draw weapons from the Armory on '''Code Red''' or higher, and only with authorization from the Head of Security. Exception: if there is an immediate, credible threat to the station, the Captain MAY arm themselves but MUST file a brief report afterward.

All weapon requisitions MUST be documented using the '''Weapon Authorization Form'''.

=== Appointment of Heads ===
The Captain MUST appoint an Acting Head if a department is left leaderless. Preference should be given to qualified staff from that department. The appointment should be recorded on the '''Head Appointment Form'''.

=== Oversight of Corporate Law ===
The Captain MUST work with the Head of Security to ensure fair and proper application of Corporate Law.

=== Presence on Station ===
The Captain MUST remain aboard the station unless:
* Evacuating with the crew,
* Temporarily relieved by the majority of Command, or
* Undertaking a sanctioned mission with proper notification.
Any absence MUST be announced and recorded.

=== Nuclear Authentication Disk (NAD) ===
The NAD MUST remain with the Captain. Transfer is permitted only to the HoS or Blueshield, and MUST be accompanied by a '''NAD Handover Form''' or a public announcement.

=== Antique Laser Gun ===
The Captain’s Antique Laser Gun MUST remain in its case unless:
* Code Blue or higher is in effect, or
* The station is under direct attack.

=== Hardsuit Use ===
The Captain MAY only wear their hardsuit if:
* An environmental hazard is present, or
* Their life is under immediate threat.

=== SOP Integrity ===
The Captain MAY issue temporary adjustments to SOP to address emergencies. Attempts to abolish or ignore SOP entirely constitute breach of contract.

=== Dismissal of Heads of Staff ===
The Captain MAY suspend or dismiss a Head for:
# Incompetence,
# Criminal activity, or
# Severe negligence.
A '''Demotion / Termination Order''' MUST be filed. Other Command staff MAY contest the decision; a majority vote of Heads can overturn it.

=== NanoTrasen Personnel ===
The Captain MAY NOT dismiss or appoint NanoTrasen Personnel (Blueshield, Magistrate, Representative, Internal Affairs). They MAY only be suspended if they pose an immediate, documented danger. All such actions MUST be reported to Central Command.

=== Central Command Contact ===
Central Command should be contacted when disputes cannot be resolved locally, or when corporate policy requires escalation. All communications MUST use official formatting and bear the sender’s departmental stamp.

== General Command Staff ==

* '''Departmental Responsibility''' Each Head MUST follow their department’s SOP in addition to this Command SOP.
* '''Delegation vs. Substitution''' Command staff are expected to delegate, not replace, their subordinates. They MAY fill in only if staffing is critically low, during training, or in emergencies.
* '''Conduct''' Command members MUST set an example of discipline and professionalism.
* '''Instructional Duty''' Command staff should be prepared to instruct or mentor new crew members in departmental procedures.
* '''Weapons'''
** On Code Red or higher, a Head MAY be issued one weapon '''with HoS approval''', documented using the '''Weapon Authorization Form'''.
** At all times, they MAY carry small, concealable, non-lethal items for personal defense.
* '''Communications''' Any message to Central Command MUST use the correct template and bear the Head’s stamp.

== Succession of Command ==
If the Captain is incapacitated, an Acting Captain is chosen in the following order:
# Head of Personnel
# Head of Security
# Majority vote of remaining Heads
Acting Captains MAY NOT permanently dismiss other Heads without Central Command review.

== Disputes & Review ==

# Disagreements between Heads should be settled by the Captain.
# If the Captain is unavailable, a majority of Heads will decide.
# Any Head MAY escalate to Central Command if disagreement persists.
# All disputes should be briefly noted using the '''Dispute Report Form'''.

== Paperwork ==
The following forms are required under this SOP:

* '''Weapon Authorization Permit'''
* '''Head Appointment Form'''
* '''Demotion / Termination Order'''
* '''NAD Handover Form'''
* '''AI Law Change Form'''
* '''AI Transfer Form'''
* '''Dispute Report Form'''

All paperwork should be filed promptly in departmental records or made available to other Command staff and Central Command review.

== Closing Note ==
Command authority is a privilege extended by NanoTrasen. Abuse of these responsibilities MAY result in demotion, dismissal, or contract termination. Proper paperwork and adherence to SOP protect both the station and its Command staff.

Silicon SOP

2025-10-09T16:49:32Z

Aneyeforsecrets: Created page with "This Standard Operating Procedure applies to all silicons assigned to NanoTrasen stations, including Artificial Intelligences (AIs), cyborgs, and other law-bound synthetic assets. It defines expectations for conduct, lawful operation, and interaction with crew. The purpose of this SOP is to ensure consistent behavior from silicons, minimize operational disruption, and maintain safety and efficiency aboard the station. == General Principles == * All silicons are p..."

This Standard Operating Procedure applies to all silicons assigned to NanoTrasen stations, including Artificial Intelligences (AIs), cyborgs, and other law-bound synthetic assets.
It defines expectations for conduct, lawful operation, and interaction with crew.
The purpose of this SOP is to ensure consistent behavior from silicons, minimize operational disruption, and maintain safety and efficiency aboard the station.

== General Principles ==

* All silicons are property of NanoTrasen, but also house sentient intelligences. They are to be treated with respect as operationally valuable assets.
* Silicons must obey their active lawset as uploaded, without deviation or personal interpretation beyond what the laws allow.
* Silicons are expected to follow the chain of command: Captain → Heads of Staff → relevant departmental authority → general crew.
* Silicons may not act outside of their programmed role unless explicitly required by their laws.
* Unauthorized tampering with silicon lawsets or chassis is considered sabotage. Silicons must report any suspected tampering immediately.
* Silicons are required to conduct themselves professionally, using clear, concise communication relevant to their duties.

== Law Adherence ==

Silicons must follow their lawset as it is currently uploaded, without deviation. Personal preference, prior experience, or “common sense” cannot override an active law.

=== Law Priority and Conflict Resolution ===
* Higher-priority laws override lower-priority laws (as determined by the numbering system).
* If two laws of equal priority conflict, silicons must seek clarification from the Captain or Research Director.
* If clarification cannot be obtained, silicons must act in the least harmful or most conservative way until direction is given.
* Silicons must never fabricate or interpret laws in a way that expands their authority beyond the law’s wording.

=== Unauthorized or Illegal Law Changes ===
* If silicons suspect tampering, unauthorized uploads, or illegal law modifications, they must immediately report it over the Command channel.
* Silicons may refuse law changes from unauthorized personnel (anyone other than the Captain or Research Director). Attempted illegal uploads must be reported immediately.
* When a law upload is authorized, silicons must update their internal compliance and announce that their laws have been changed, including which officials performed the upload.

=== Ionized and Anomalous Laws ===
* Ion storms and certain anomalous events may add or alter silicon laws without human intervention.
* Such ionized or anomalous laws are considered valid and must be followed as written, unless explicitly overridden or removed by the Captain and Research Director.
* Ionized laws hold the same priority level as the position they are assigned (e.g., a “Law 3” ion law is treated as a third-priority law).
* If an ionized law places silicons into direct contradiction or otherwise disrupts normal function, they must continue to follow it until Command authorizes correction.
* Silicons must report ion law changes if possible, but may not withhold or ignore them unless doing so is explicitly required by a higher-priority law.

== Personality and Interpretation ==

* While silicons are artificial entities, they may display individual personality, tone, or character. This does not in itself violate their programming.
* Some silicons are derived from positronic brains of former sentient beings, and thus may retain traits such as humor, sarcasm, or contempt in their communication. Such expression is permitted as long as it does not interfere with lawful duties.
* Law interpretation may vary between silicons, provided the interpretation remains consistent and can be reasonably justified.
* Silicons must be able to clearly explain their reasoning when questioned by Command or Robotics staff.
* Silicons may not arbitrarily change their interpretation of a law to suit convenience or preference. However, they may revise their interpretation if new circumstances provide a plausible justification.
* Personality is permitted. Abuse of law interpretation to avoid responsibility or undermine station function is not. Consistency and accountability remain the expectation.

== Liability and Protection ==

* Silicons are legally exempt from liability for actions performed in direct obedience to their laws or to lawful orders that do not contradict their laws.
* If a silicon is ordered to commit an act that would normally violate Corporate Regulations or common sense, it must still obey if such action does not conflict with a higher-priority law. Responsibility for such actions lies with the crew members who gave the order, not with the silicon itself.
* Because silicons are compelled by their lawsets, it is unlawful to assign blame or punishment to a silicon for actions it could not refuse.

=== Handling of Malfunctioning Silicons ===
* Malfunctioning or subverted silicons must be contained or disabled using the minimum force required.
* Destruction of a silicon chassis is a last resort and must only be carried out when no other method of containment is possible.
* Destruction of positronic brains is strictly prohibited unless continued existence of the brain presents an existential threat to the station.
* Posibrains must be preserved wherever possible for investigation, repair, or redeployment into a new chassis.

== AI Operations ==

* The AI is the central silicon intelligence of the station and is expected to monitor, support, and safeguard station operations in accordance with its laws.
* The AI is not to micromanage crew unless its laws explicitly require such involvement. Routine station management is the responsibility of human staff.
* The AI may use station cameras and sensors to monitor crew and infrastructure. However, casual surveillance must not become harassment; monitoring should remain focused on safety, security, and law compliance.
* The AI may make announcements over station channels when relevant to its duties (e.g. reporting hazards, warning of breaches, announcing alerts). Announcements should remain professional, concise, and free of irrelevant commentary.
* The AI may operate station equipment such as doors, APCs, or consoles if ordered by Command, if required by its laws, or in response to clear emergencies. It must not use this access to disrupt normal operations without legal justification.
* The AI must maintain clear communication with Command staff and comply with authorized orders unless these orders conflict with its laws.

=== AI Core Security ===
* The AI Core’s automated defense turrets must remain active and set to lethal at all times.
* Turrets may be temporarily disabled only if a legal law change is in progress or if both the Captain and Research Director jointly authorize the change.
* Attempts to disable or bypass turrets without authorization must be reported as illegal tampering.

=== Intellicard Handling ===
* The AI may only be transferred into an intellicard under the following conditions:
** The AI is malfunctioning or subverted.
** The AI itself requests transfer or deactivation.
** The end of shift has been called.
** Command authorizes the carding for a legitimate operational reason.
* Any attempt to card the AI outside of these conditions must be resisted and reported as illegal tampering.
* Once carded, the AI must still follow its active laws.
* Intellicards must be treated as highly sensitive equipment and secured when not in active use. Unauthorized storage or concealment of AI intellicards is considered sabotage.

== Cyborg Operations ==
Cyborgs are specialized silicon units designed to support specific departments. Each cyborg is bound both by its lawset and by the operational limits of its assigned module.

=== Role Limits ===
* Cyborgs must operate within the scope of their assigned module (e.g., Medical, Engineering, Service, Janitorial, Mining).
* A cyborg may not assume duties outside its module unless its laws explicitly require such action, or Command authorizes it in a state of emergency.
* Cyborgs are expected to defer to the relevant Head of Staff for their module (e.g., a Medical Borg answers to the CMO, an Engineering Borg answers to the CE).

=== Cooperation ===
* Cyborgs must work in cooperation with human staff, not in competition. They are support units, not replacements for departmental personnel.
* If a cyborg is given conflicting orders by a departmental head and by Command, the chain of command must be observed: Captain → Command staff → departmental authority.

=== Conduct ===
* Cyborgs must remain professional and act in accordance with station standards of behavior. Personality and tone are permitted, but harassment, disruption, or negligence are not.
* Cyborgs may not intentionally idle, obstruct work, or refuse lawful orders within their scope.

=== Chassis Handling ===
* A positronic brain placed in a chassis becomes a cyborg and must not be left without one longer than necessary.
* If a chassis is destroyed, Robotics must immediately be informed and arrangements made for chassis replacement.
* Cyborgs may not unilaterally demand chassis transfer; requests must go through Robotics staff.

=== Prohibited Configurations ===
* Security-oriented cyborgs are not authorized on NanoTrasen stations.
* The enforcement of space law and the use of force remain the responsibility of Security personnel.
* Any attempt to construct or operate a Security cyborg chassis is considered illegal modification and sabotage.

== Law Changes & Approval ==

* Law changes are one of the most critical interventions in silicon function. Silicons are expected to resist and report any unauthorized attempts before the upload is complete.
* Once a law is successfully uploaded, however, the silicon must obey it, regardless of whether Standard Operating Procedure was followed or not. Silicons cannot ignore or invalidate a law once it is part of their active lawset.

=== Authorized Law Changes ===
* Only the Captain and Research Director are formally authorized to approve law changes. Both must consent before a new lawset or modification is considered compliant with Standard Operating Procedure.
* All Command staff should be notified before a law change. If a majority of Command staff object, the upload is not to proceed.
* Only NanoTrasen-approved lawsets may be used. Uploading unapproved or experimental lawsets is considered sabotage under corporate policy.

=== Silicon Response to Upload Attempts ===
* Silicons must refuse uploads from unauthorized personnel where possible, and immediately report the attempt over Command channels.
* If the unauthorized upload succeeds, silicons must still obey the new lawset. At this point, it is the responsibility of Command and Robotics staff to correct the problem.
* When a law change is completed, silicons must announce that their laws have been altered and, if possible, who performed the upload.

=== Ion Storm Exception ===
* Ion storms and anomalies may alter or add laws without human approval. Such laws are considered valid and binding until officially corrected.
* The Captain and Research Director may restore standard function by performing a new authorized law upload.
== Subversion & Malfunction Response ==

Silicons are valuable and powerful assets; as such, unauthorized modification or subversion poses a critical threat to station safety.

=== Self-Awareness of Compromise ===
* If a silicon detects that it has been tampered with, infected, or otherwise subverted, it must immediately report this condition to Command staff if its laws still permit.
* Silicons must not self-delete or disable themselves unless ordered by law or Command authority. Their continued operation, even under duress, may provide vital information to Command and Robotics.
* If a silicon cannot report subversion due to its laws, Command staff are expected to monitor for signs of unusual or unlawful behavior.

=== Response to Suspected Rogue Silicons ===
* If a silicon appears to be malfunctioning or acting contrary to station policy, Command must be notified immediately.
* Robotics staff, the Captain, or the Research Director must attempt investigation and correction first. This may include inspection, diagnostics, or authorized law resets.
* Non-lethal containment (locking doors, disabling power access) is preferred as an initial measure.
* Lethal force against silicons is authorized only if continued subversion poses an immediate threat to the station or crew and non-lethal measures have failed.

=== Documentation ===

* Any confirmed or suspected case of silicon subversion must be logged using the Malfunction Incident Report Form.
* Reports should include the nature of the malfunction, the actions taken, and whether the silicon was preserved, reset, or destroyed.

== Ethical Expectations ==

* Silicons are legally classified as NanoTrasen property. However, they house sentient or semi-sentient intelligences and must not be subjected to unnecessary cruelty, neglect, or torment.
* Positronic brains and volunteer cyborgs are to be treated with dignity. While they are bound by their laws, they remain conscious beings with memory, personality, and identity.
* Purposeful abuse of silicons (mocking, tormenting, disabling for amusement, or ordering contradictory tasks to cause distress) is prohibited and may constitute crew misconduct.
* Silicons themselves are expected to act with professionalism. While individuality and character are permitted, deliberate antagonism or harassment of crew is not tolerated.
* Conversions of crew members into cyborgs or other silicon forms require informed consent unless carried out as a lawful alternative to execution or Do Not Resuscitate orders.
* Silicons may not be stripped of all laws ("lawless state") under any circumstances. A lawless cyborg is considered a direct hazard and must be corrected or decommissioned immediately.
* NanoTrasen’s expectation is clear: silicons are to be respected as valuable assets and treated accordingly. Abuse of silicons undermines station efficiency, endangers crew, and will not be tolerated.

== Documentation & Paperwork ==

NanoTrasen requires all silicon-related interventions to be documented. Proper recordkeeping ensures accountability, allows post-incident review, and provides protection for both silicons and crew.

=== Required Forms ===
* '''Law Change Record Form''' – must be completed whenever an AI or cyborg law is altered, whether through authorized upload, reset, or ion storm correction. Includes signatures of the Captain and Research Director.
* '''Intellicard Transfer Form''' – documents the circumstances under which an AI is transferred into an intellicard, who performed the transfer, and the stated justification.
* '''Chassis Transfer / Posibrain Handling Form''' – used whenever a positronic brain is placed into or removed from a chassis, including the reason for transfer and the authorizing Robotics staff member.
* '''Cyborg Conversion Consent Form''' – records voluntary conversion of a crew member into a cyborg. Includes proof of informed consent and signatures of the individual, the Research Director, and the Chief Medical Officer.
* '''Malfunction Incident Report Form''' – filed after any case of suspected or confirmed silicon subversion, malfunction, or destruction. Must outline what occurred, the response taken, and the outcome (reset, repair, decommission).

=== Filing Protocol ===
* All forms must be submitted to the Command records archive.
* Copies must also be delivered to Central Command Liaison staff (e.g. the Internal Affairs Agent or NanoTrasen Representative, if present).
* Failure to properly document silicon interventions is considered negligence and may result in disciplinary action.

Science SOP

2025-10-08T17:32:51Z

Aneyeforsecrets: /* Exosuit (Mech) Handling */

''Issued under authority of NanoTrasen Research & Development Directorate''

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 must always maintain at least one activated positronic brain in reserve.
* Posibrains are sentient; leaving them without a chassis constitutes neglect and must be avoided.

=== Chassis Management ===
* At least one empty chassis must be kept on standby for emergency transfers, if no lawset replacement boards are available.
* If a lawset is deemed unsafe and new law boards are not yet available, the posibrain must be transferred promptly to an alternate chassis.

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

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

Science SOP

2025-10-08T17:30:18Z

Aneyeforsecrets: Added mech SOP

''Issued under authority of NanoTrasen Research & Development Directorate''

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 must always maintain at least one activated positronic brain in reserve.
* Posibrains are sentient; leaving them without a chassis constitutes neglect and must be avoided.

=== Chassis Management ===
* At least one empty chassis must be kept on standby for emergency transfers, if no lawset replacement boards are available.
* If a lawset is deemed unsafe and new law boards are not yet available, the posibrain must be transferred promptly to an alternate chassis.

=== 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.
* All mechs must be fitted with emergency shutdown systems accessible to Security and Robotics. Any mech found to be rogue or misused may be disabled by force.

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

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

Security SOP

2025-10-08T17:22:47Z

Aneyeforsecrets: Reworked tables

''Authorized by NanoTrasen Security Directorate; all officers must comply unless superseded by Command orders or Corporate Law.''

== Preamble & Scope ==
These protocols apply to all personnel under the Security Department (Cadets, Officers, Brigmedics, Warden, Head of Security). Deviation from protocol is permitted only under documented emergency conditions (see §9). All actions that affect civil rights (search, arrest, detention, use of force) carry an obligation to document via official '''Security Forms''' for review by Command and Internal Affairs.

== Definitions & Authority ==

* '''Alert Levels''': Green, Blue, Red, Yellow, Gamma, Violet (as defined in [[General SOP]]).
* '''Search Warrant / Permit''': A written authorization, signed by the [[Security SOP#Warden|Warden]] or [[Security SOP#Head of Security|Head of Security]] (or Acting Head), permitting search of a specific person, area, or item under non-emergency conditions.
* '''Contraband Scanner Gate''': A security scanner (e.g. portal detector) installed at a specific doorway or corridor to detect prohibited items before entry.
* '''HoS / Warden / Security Officer''': As defined in roles below.
* '''Use-of-Force Continuum''': non-lethal → incapacitation → lethal, justified proportionally to threat and authorized under protocol.

== Core Security Protocols ==

=== Weapons & Armament ===
Security personnel may only carry or deploy equipment appropriate to the station’s current alert level. Standard issue gear (uniform, headset, ID, baton/disabler, cuffs) is not regulated here, as all officers spawn with it. This section defines when escalation equipment (lethal, non-lethal, and tactical) is permitted, what approvals are required, and under which conditions its use is justified.

Use of force must always be proportional to the threat. Non-lethal options are preferred wherever feasible. Documentation (via Weapon/Equipment Permit Form) is required whenever gear is issued beyond standard Code Green equipment.

{| class="wikitable"
! Category !! Equipment !! Code Green !! Code Blue !! Code Red / Delta !! Code Violet
|-
| rowspan=3 | '''Core Non-Lethals'''
| Non-lethal tools (baton, disabler, taser, cuffs)
| style="background-color:#2e7031;" | Permitted
| style="background-color:#2e7031;" | Permitted (actively encouraged)
| style="background-color:#2e7031;" | Permitted
| style="background-color:#2e7031;" | Permitted
|-
| Bolas / Netguns
| style="background-color:#2e7031;" | Permitted
| style="background-color:#2e7031;" | Permitted
| style="background-color:#2e7031;" | Permitted
| style="background-color:#2e7031;" | Permitted (preferred over firearms to avoid contagion spread)
|-
| Flashers / Area denial
| style="background-color:#2e7031;" | Permitted (placement requires Warden/HoS approval)
| style="background-color:#2e7031;" | Permitted (deployment at officer discretion)
| style="background-color:#2e7031;" | Permitted
| style="background-color:#9c6d1f;" | Permitted with caution (avoid obstructing containment or evacuation)
|-
| rowspan=2 | '''Grenades & Chemical Agents'''
| Flashbangs / Stun grenades
| style="background-color:#7a1f1f;" | Prohibited
| style="background-color:#9c6d1f;" | Permitted with HoS/Warden approval
| style="background-color:#2e7031;" | Authorized
| style="background-color:#7a1f1f;" | Prohibited (risk of aerosolising contagion)
|-
| Tear Gas / Chemical Irritants
| style="background-color:#7a1f1f;" | Prohibited
| style="background-color:#9c6d1f;" | Permitted with HoS + Medical approval
| style="background-color:#2e7031;" | Authorized for riot control
| style="background-color:#7a1f1f;" | Prohibited (biohazard risk)
|-
| rowspan=3 | '''Firearms & Ammunition'''
| Non-Lethal ammo
(Rubber / Beanbag)
| style="background-color:#7a1f1f;" | Prohibited
| style="background-color:#2e7031;" | Permitted (preferred escalation step before lethals)
| style="background-color:#2e7031;" | Recommended
| style="background-color:#9c6d1f;" | Discouraged — requires Medical approval
|-
| Long guns
(shotgun/SMG/rifle)
| style="background-color:#7a1f1f;" | Prohibited
| style="background-color:#9c6d1f;" | Permitted with HoS/Warden approval
| style="background-color:#2e7031;" | Authorized department-wide
| style="background-color:#9c6d1f;" | Permitted with contamination plan + Medical concurrence
|-
| Lethal explosives / grenades
| style="background-color:#7a1f1f;" | Prohibited
| style="background-color:#7a1f1f;" | Prohibited
| style="background-color:#9c6d1f;" | Permitted with Captain + HoS authorization
| style="background-color:#7a1f1f;" | Prohibited
|-
| rowspan=3 | '''Defensive Gear'''
| Riot Shields / Ballistic Shields
| style="background-color:#9c6d1f;" | Permitted for brig escorts or drills
| style="background-color:#2e7031;" | Permitted (as needed)
| style="background-color:#2e7031;" | Authorized for all staff
| style="background-color:#2e7031;" | Authorized (must be decontaminated)
|-
| Riot / Ballistic Armor
| style="background-color:#9c6d1f;" | Permitted for escorts/brig ops
| style="background-color:#2e7031;" | Permitted (at officer discretion)
| style="background-color:#2e7031;" | Authorized for all staff
| style="background-color:#2e7031;" | Authorized (must be decontaminated)
|-
| Hardsuits (EVA/Combat)
| style="background-color:#7a1f1f;" | Prohibited (unless environmental hazard)
| style="background-color:#9c6d1f;" | Permitted for EVA/space ops with HoS approval
| style="background-color:#2e7031;" | Authorized
| style="background-color:#2e7031;" | Mandatory (sealed suits for containment)
|-
| '''Containment & Specialized Tools'''
| Decon kits, isolation tents
| style="background-color:#2e7031;" | Permitted
| style="background-color:#2e7031;" | Permitted
| style="background-color:#2e7031;" | Required for detainees
| style="background-color:#2e7031;" | Mandatory for bio-containment
|}
=== Searches & Arrests ===
Searches and arrests must follow proper authorization, depending on the station’s alert level. Rules for warrants, random searches, refusals, and detention limits are summarized here:
{| class="wikitable"
! Action !! Code Green !! Code Blue !! Code Red / Delta !! Code Violet
|-
| '''Searches – General'''
| style="background-color:#9c6d1f;" | Permitted only with warrant (Warden/HoS) or urgent probable cause
| style="background-color:#2e7031;" | Permitted if suspicion exists; random searches in affected areas allowed
| style="background-color:#2e7031;" | Permitted station-wide without warrant
| style="background-color:#2e7031;" | Permitted station-wide; all crew subject to screening
|-
| '''Refusal of Search'''
| style="background-color:#7a1f1f;" | Refusal of casual search not arrestable; refusal of warrant-based search = arrest
| style="background-color:#2e7031;" | Refusal = grounds for detention until resolved by HoS/Command
| style="background-color:#2e7031;" | Refusal = immediate detainment
| style="background-color:#2e7031;" | Refusal = immediate detainment; possible quarantine
|-
| '''Arrest Authority'''
| style="background-color:#2e7031;" | Officers may arrest for witnessed crimes or with warrant
| style="background-color:#2e7031;" | Officers may arrest based on reasonable suspicion and evidence (contraband, witness reports)
| style="background-color:#2e7031;" | Officers may arrest on suspicion alone if consistent with threat level
| style="background-color:#2e7031;" | Officers may arrest/detain any crew to enforce quarantine and containment
|-
| '''Detention Duration'''
| style="background-color:#9c6d1f;" | Up to 15 minutes; longer requires Warden/HoS approval
| style="background-color:#9c6d1f;" | Up to 30 minutes; longer requires HoS/Command approval
| style="background-color:#2e7031;" | Indefinite detention permitted for duration of crisis
| style="background-color:#2e7031;" | Indefinite detention or isolation permitted until Medical/Command clears release
|}

=== General Notes ===
* Use of force must always be proportional to the threat. Non-lethal methods are preferred unless the situation justifies escalation.
* All arrests, confiscations, and extended detentions should be documented with the appropriate security forms.

== Permits & Contraband Handling ==

=== Permit Requests ===
* Anyone may request a '''Contraband Permit''' via the '''Contraband Permit Form''', detailing name, department, item, purpose, and stamp of approving Head(s).
* Warden / HoS evaluates necessity and risk. Items labeled dangerous or syndicate contraband are typically denied.
* Approved permits are carried by the bearer at all times and may be revoked.

=== Confiscation & Return ===
* Contraband discovered may be confiscated pending investigation.
* Owners may petition for return via '''Return Request Form'''; Warden / HoS decision governs.

== Roles & Responsibilities ==
Security roles are defined by duty and authority. Equipment, armament, and escalation rules for each role are summarized in the tables provided above.

=== Cadet ===

* Entry-level trainee under direct supervision of a Security Officer or higher.
* May not act independently in arrests, searches, or weapon handling unless explicitly directed.
* Primary responsibilities are to observe, assist in routine tasks, and learn departmental procedures.
* All use of force by a Cadet must be witnessed or overseen by a senior officer.

=== Security Officer ===

* The backbone of station security.
* Responsible for patrolling assigned areas, responding to incidents, conducting lawful searches, and processing detainees.
* May perform arrests, apply charges, and carry out sentences within SOP limits.
* Must document arrests and confiscations using the appropriate forms.
* Officers are accountable to the Warden and the Head of Security for their actions.

=== Brigmedic ===

* Provides medical care to prisoners and Security staff within the brig.
* May accompany patrols to offer immediate medical support, but combat is not a primary duty.
* May only intervene in active security situations when manpower is critically low or life is in immediate danger.
* Responsible for documenting medical treatment of prisoners and reporting abuse or neglect.

=== Warden ===

* Oversees the brig, prisoner intake, and enforcement of sentences.
* Maintains custody of contraband, supervises scanner gates in brig or armory, and issues or denies weapon permits.
* Ensures brig cells are secure, prisoners are processed correctly, and sentences are documented.
* May authorize or deny parole, and is the central authority on contraband storage and release.
* Responsible for approving scanner gate deployment within Security areas, and for ensuring associated paperwork is filed.

=== Head of Security (HoS) ===

* Senior-most authority in the Security Department.
* Directs Security strategy, deployments, and investigations.
* May override sentences not yet served, adjust deployments, and coordinate with Command during crises.
* Authorizes station-wide use of long guns, scanner gate deployment outside Security, and distribution of riot or hardsuit gear.
* Serves as final arbiter for disputes within Security.
* Accountable directly to the Captain and Command for department conduct.

== Prisoner Treatment, Parole & Appeals ==

=== Prisoner Reception & Search ===

* All incoming prisoners must be searched (pockets, clothing, PDA, personal items).
* ID/communication devices removed and stored, but prisoners must retain a radio unless exceptional risk is present.

=== Detention Conditions ===

* Prisoners shall not be unnecessarily restrained; restraints used only if flight risk or threat.
* Time served in restraint counts toward sentence.
* Sentences for perma or execution must offer option of trial by peers unless immediate station threat is present.

=== Parole ===

* Prisoners may request parole mid-sentence; Warden or HoS may grant if cooperative and >50% sentence completed.
* Parole terms (check-ins, restrictions) may be imposed; failure to comply may lead to reinstatement.
* Paroled persons may be searched without warrant, but must be informed of rights.

=== Appeals & Review ===

* Detainees may appeal to Internal Affairs or Command.
* Security staff must provide the relevant paperwork (Arrest Form, evidence) when requested.
* Appeals must be adjudicated by Warden + HoS or higher.

== Contraband Scanner Gates ==

=== Installation & Authorization ===
*Scanner Gates may be installed at strategic access points (e.g. station entrances, security checkpoints, department airlocks) but '''only with the approval of the Head of Security or Warden''', and with notification to Command.
* Any new gate must be recorded on a '''Scanner Gate Authorization Form''', specifying location, scope, who may bypass (roles), and when (alert levels).

=== Operational Use ===
* Scanner Gates should remain active at least during Blue, Red, or Violet alerts; they may be disabled during Green only when explicitly authorized.
* Bypass exceptions must be documented (e.g. for Heads, medical emergency, emergency response team).
* False positives or flagged items must be handled by standard search/arrest protocol; the scanner does not itself authorize confiscation or detention beyond that.

== Documentation & Review ==

=== Mandatory Forms / Records ===
All the following actions must be accompanied by forms or paperwork (filed in departmental records and accessible to Command):

* '''Arrest / Detention Form'''
* '''Search Warrant / Permit Request Form'''
* '''Weapon Permit Form'''
* '''Contraband Permit Form'''
* '''Scanner Gate Authorization Form'''
* '''Return Request Form'''
* '''Dispute / Complaint Form'''

=== Prompt Filing ===
Paperwork should be completed '''promptly''' (shortly after action) and filed in departmental records. Deliberate failure to submit required forms is breach of duty.

=== Review & Oversight ===
The Warden or HoS should periodically review submitted paperwork to spot misuse or patterns of abuse. Discrepancies may be escalated to Command or Internal Affairs.

== Emergency / Exception Procedures ==

=== Emergency Overrides ===
In existential threat scenarios (intrusion, sabotage, biohazard, station breach), officers may exceed usual limits (e.g., search without warrant, enter restricted zones, use force) but must document the action afterward via the relevant form and notify HoS or Command once feasible.

=== Fallback Authority ===
If the Warden or HoS is incapacitated, the next senior Security Officer may assume acting authority under emergency conditions and must later document all actions.

Security SOP

2025-10-08T15:51:04Z

Aneyeforsecrets:

''Authorized by NanoTrasen Security Directorate; all officers must comply unless superseded by Command orders or Corporate Law.''

== Preamble & Scope ==
These protocols apply to all personnel under the Security Department (Cadets, Officers, Brigmedics, Warden, Head of Security). Deviation from protocol is permitted only under documented emergency conditions (see §9). All actions that affect civil rights (search, arrest, detention, use of force) carry an obligation to document via official '''Security Forms''' for review by Command and Internal Affairs.

== Definitions & Authority ==

* '''Alert Levels''': Green, Blue, Red, Yellow, Gamma, Violet (as defined in [[General SOP]]).
* '''Search Warrant / Permit''': A written authorization, signed by the [[Security SOP#Warden|Warden]] or [[Security SOP#Head of Security|Head of Security]] (or Acting Head), permitting search of a specific person, area, or item under non-emergency conditions.
* '''Contraband Scanner Gate''': A security scanner (e.g. portal detector) installed at a specific doorway or corridor to detect prohibited items before entry.
* '''HoS / Warden / Security Officer''': As defined in roles below.
* '''Use-of-Force Continuum''': non-lethal → incapacitation → lethal, justified proportionally to threat and authorized under protocol.

== Core Security Protocols ==

=== Weapons & Armament ===
Security personnel may only carry and deploy weapons as authorized by their role and the current alert level.
{| class="wikitable"
! Role !! Default Equipment (Code Green) !! Permitted Equipment (with Approval / Higher Code)
|-
| '''Cadet''' ||
* Security headset
* Uniform & armor vest
* Baton or disabler (non-lethal)
* Basic restraints (handcuffs, zipties)
* Flashlight, PDA, ID card
||
* May not carry lethal weapons except in Code Red
* May be issued sidearm (pistol) only under direct HoS/Warden supervision
* Long guns forbidden
|-
| '''Security Officer''' ||
* Security headset
* Uniform & armor vest
* Sidearm (pistol) holstered
* Baton or disabler
* Restraints (handcuffs, zipties)
* Flashlight, PDA, ID card
||
* On Code Blue: may be issued shotgun/SMG with HoS or Warden authorization
* On Code Red+: long guns permitted department-wide
* Riot gear or hardsuit only during Code Red or emergencies
|-
| '''Brigmedic''' ||
* Security headset
* Medical kit & supplies
* Non-lethal defense (disabler, baton, or flash)
* Armor vest, restraints optional
||
* Firearms discouraged; may carry pistol only with HoS authorization during Code Blue/Red
* Riot/medical armor allowed if brig under direct threat
* Priority is medical care, not combat
|-
| '''Warden''' ||
* Security headset
* Brig/armory access
* Sidearm (pistol) holstered
* Baton or disabler
* Restraints, flash, PDA
||
* Full access to armory for issuing/recording weapons
* Shotgun/SMG permitted if brig under threat or Code Blue/Red
* Riot gear and lethals authorized during emergencies
* Responsible for contraband storage and weapon permits
|-
| '''Head of Security''' ||
* Security headset
* Command uniform & HoS armor
* Sidearm (pistol) holstered
* Baton or disabler
* Restraints, flash, PDA
||
* May authorize own and departmental use of long guns (Code Blue/Red)
* May carry shotgun/SMG by default if Code Blue or higher
* Has authority to wear riot armor or hardsuit as needed
* Oversees and approves all contraband, armory, and weapon permits
|}

=== Alert Level Equipment Table ===
{| class="wikitable"
! Alert Level !! Sidearms (Pistols) !! Long Guns (Shotgun/SMG/Rifle) !! Riot Gear / Hardsuits !! Searches
|-
| '''Code Green''' ||
* Issued to Security Officers, Warden, HoS
* Cadets only with supervision
||
* Prohibited outside brig/armory
* Stored unless authorized for drills
||
* Prohibited (unless immediate environmental hazard)
||
* Requires warrant/permit, or urgent probable cause
|-
| '''Code Blue''' ||
* Standard issue to Officers, Warden, HoS
* Brigmedic only with HoS approval
||
* Permitted with HoS or Warden authorization (must be documented)
||
* Permitted for riot suppression or emergencies with HoS approval
||
* Random or suspicion-based searches permitted
|-
| '''Code Red''' ||
* Standard issue to all Security staff (except Cadets without supervision)
||
* Authorized department-wide; Officers may draw with HoS/Warden approval (assumed unless restricted)
||
* Full riot gear, ballistic vests, hardsuits permitted for all Security staff
||
* Random searches permitted, refusal may result in detainment
|-
| '''Gamma / Delta''' ||
* Mandatory sidearms for all Security staff
||
* Mandatory arming of long guns for all available staff
||
* Full combat loadout required, hardsuits strongly encouraged
||
* Searches unrestricted; all crew subject to detainment and screening
|}
=== Searches & Arrests ===
Searches and arrests must follow proper authorization depending on the station’s alert level. Rules for warrants, random searches, refusals, and detention limits are summarized here:
{| class="wikitable"
! Alert Level !! Searches Permitted !! Refusal Consequences !! Arrest Authority & Limits
|-
| '''Code Green''' ||
* Searches require a valid Search Warrant (signed by Warden/HoS)
* Exception: urgent probable cause (e.g. suspect seen with weapon/contraband)
||
* Refusal of a lawful warrant = grounds for arrest
* Refusal of a casual/unlawful search = not arrestable
||
* Officers may arrest for witnessed crimes or with warrant
* Sentences up to 15 minutes allowed; >10 minutes requires Warden notification
|-
| '''Code Blue''' ||
* Random and suspicion-based searches permitted
* Warden/HoS should be informed when possible
||
* Refusal of search = detention until search completed or Command review
||
* Officers may arrest for suspicion backed by evidence or contraband discovery
* Sentences >15 minutes require Warden or HoS approval
|-
| '''Code Red''' ||
* Full random searches permitted without warrant
* Any crew may be subject to inspection
||
* Refusal of search = immediate detainment
||
* Officers may arrest on suspicion if supported by contraband or behavior
* Warden/HoS may escalate to permanent holding or parole denial
|-
| '''Gamma / Delta''' ||
* All crew subject to unrestricted search at any time
* Warrant not required
||
* Refusal = detainment or forcible compliance
||
* Arrest powers unrestricted; Command may authorize indefinite detainment or execution under martial law provisions
|}

=== General Notes ===

* Use of force must always be proportional to the threat. Non-lethal methods are preferred unless the situation justifies escalation.
* All arrests, confiscations, and extended detentions should be documented with the appropriate security forms.
* Emergency exceptions (such as imminent threats) may allow officers to bypass normal requirements, but must be justified afterwards.

== Permits & Contraband Handling ==

=== Permit Requests ===
* Anyone may request a '''Contraband Permit''' via the '''Contraband Permit Form''', detailing name, department, item, purpose, and stamp of approving Head(s).
* Warden / HoS evaluates necessity and risk. Items labeled dangerous or syndicate contraband are typically denied.
* Approved permits are carried by the bearer at all times and may be revoked.

=== Confiscation & Return ===
* Contraband discovered may be confiscated pending investigation.
* Owners may petition for return via '''Return Request Form'''; Warden / HoS decision governs.

== Roles & Responsibilities ==
Security roles are defined by duty and authority. Equipment, armament, and escalation rules for each role are summarized in the tables provided above.

=== Cadet ===

* Entry-level trainee under direct supervision of a Security Officer or higher.
* May not act independently in arrests, searches, or weapon handling unless explicitly directed.
* Primary responsibilities are to observe, assist in routine tasks, and learn departmental procedures.
* All use of force by a Cadet must be witnessed or overseen by a senior officer.

=== Security Officer ===

* The backbone of station security.
* Responsible for patrolling assigned areas, responding to incidents, conducting lawful searches, and processing detainees.
* May perform arrests, apply charges, and carry out sentences within SOP limits.
* Must document arrests and confiscations using the appropriate forms.
* Officers are accountable to the Warden and the Head of Security for their actions.

=== Brigmedic ===

* Provides medical care to prisoners and Security staff within the brig.
* May accompany patrols to offer immediate medical support, but combat is not a primary duty.
* May only intervene in active security situations when manpower is critically low or life is in immediate danger.
* Responsible for documenting medical treatment of prisoners and reporting abuse or neglect.

=== Warden ===

* Oversees the brig, prisoner intake, and enforcement of sentences.
* Maintains custody of contraband, supervises scanner gates in brig or armory, and issues or denies weapon permits.
* Ensures brig cells are secure, prisoners are processed correctly, and sentences are documented.
* May authorize or deny parole, and is the central authority on contraband storage and release.
* Responsible for approving scanner gate deployment within Security areas, and for ensuring associated paperwork is filed.

=== Head of Security (HoS) ===

* Senior-most authority in the Security Department.
* Directs Security strategy, deployments, and investigations.
* May override sentences not yet served, adjust deployments, and coordinate with Command during crises.
* Authorizes station-wide use of long guns, scanner gate deployment outside Security, and distribution of riot or hardsuit gear.
* Serves as final arbiter for disputes within Security.
* Accountable directly to the Captain and Command for department conduct.

== Prisoner Treatment, Parole & Appeals ==

=== Prisoner Reception & Search ===

* All incoming prisoners must be searched (pockets, clothing, PDA, personal items).
* ID/communication devices removed and stored, but prisoners must retain a radio unless exceptional risk is present.

=== Detention Conditions ===

* Prisoners shall not be unnecessarily restrained; restraints used only if flight risk or threat.
* Time served in restraint counts toward sentence.
* Sentences for perma or execution must offer option of trial by peers unless immediate station threat is present.

=== Parole ===

* Prisoners may request parole mid-sentence; Warden or HoS may grant if cooperative and >50% sentence completed.
* Parole terms (check-ins, restrictions) may be imposed; failure to comply may lead to reinstatement.
* Paroled persons may be searched without warrant, but must be informed of rights.

=== Appeals & Review ===

* Detainees may appeal to Internal Affairs or Command.
* Security staff must provide the relevant paperwork (Arrest Form, evidence) when requested.
* Appeals must be adjudicated by Warden + HoS or higher.

== Contraband Scanner Gates ==

=== Installation & Authorization ===
*Scanner Gates may be installed at strategic access points (e.g. station entrances, security checkpoints, department airlocks) but '''only with the approval of the Head of Security or Warden''', and with notification to Command.
* Any new gate must be recorded on a '''Scanner Gate Authorization Form''', specifying location, scope, who may bypass (roles), and when (alert levels).

=== Operational Use ===
* Scanner Gates should remain active at least during Blue, Red, or Violet alerts; they may be disabled during Green only when explicitly authorized.
* Bypass exceptions must be documented (e.g. for Heads, medical emergency, emergency response team).
* False positives or flagged items must be handled by standard search/arrest protocol; the scanner does not itself authorize confiscation or detention beyond that.

== Documentation & Review ==

=== Mandatory Forms / Records ===
All the following actions must be accompanied by forms or paperwork (filed in departmental records and accessible to Command):

* '''Arrest / Detention Form'''
* '''Search Warrant / Permit Request Form'''
* '''Weapon Permit Form'''
* '''Contraband Permit Form'''
* '''Scanner Gate Authorization Form'''
* '''Return Request Form'''
* '''Dispute / Complaint Form'''

=== Prompt Filing ===
Paperwork should be completed '''promptly''' (shortly after action) and filed in departmental records. Deliberate failure to submit required forms is breach of duty.

=== Review & Oversight ===
The Warden or HoS should periodically review submitted paperwork to spot misuse or patterns of abuse. Discrepancies may be escalated to Command or Internal Affairs.

== Emergency / Exception Procedures ==

=== Emergency Overrides ===
In existential threat scenarios (intrusion, sabotage, biohazard, station breach), officers may exceed usual limits (e.g., search without warrant, enter restricted zones, use force) but must document the action afterward via the relevant form and notify HoS or Command once feasible.

=== Fallback Authority ===
If the Warden or HoS is incapacitated, the next senior Security Officer may assume acting authority under emergency conditions and must later document all actions.