From 7fac37c66921f04d3eff80610176a8d42c61311f Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Sun, 26 Apr 2026 00:28:40 -0300 Subject: [PATCH 01/53] Created the main doc for the rework Filled out the Title section Created a basic skeleton for the Features to be added section Set the technical considerations section to mention it's just yaml --- .../station_protocol_rework.md | 65 +++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 src/design-proposals/station_protocol_rework.md diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md new file mode 100644 index 00000000..3fcced64 --- /dev/null +++ b/src/design-proposals/station_protocol_rework.md @@ -0,0 +1,65 @@ +# Station Protocol Rework / Nanotrasen Colonial Law and Procedure +| Designers | Implemented | GitHub Links | +|---|---|---| +| SOP Workgroup | :x: | TBD | + +Leader: Catty +Members: Joaco545, Alicios, Scrambledking, Gamercodeleo1/funkycmm, Goobie (and many other that I need to read chat to get) +Many thanks to the Admin team and Tay for pitching in + +## Overview + +A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". + +## Background + +Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. + +Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. + +## Features to be added + +Add a series of books and gudebook entries under the name of Nanotrasen Colonial Law and Procedure + +Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: +### Article 1 - Station Regulations +Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more + +### Article 2 - Corporate law +To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. +While a name change may not seem that important, it set's the tone of what to expect. + +### Article 3 - Standard Operating Procedure + + +### Article 4 - Unions + + +### Article 5 - Trials and Hearings + + +### Extra considerations +"Behavior follows incentives" +While this PR focuses only on the regulations themselves, many supporting changes will need to be done to mechanically enforce the vision Funky station has. +The SOP workgroup is working on other design docs that should help change that situation and align mechanics with the text and intent behind them. + +## Game Design Rationale + +Consider addressing: +- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? + +## Roundflow & Player interaction + +Consider addressing: +- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? +- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? + +## Administrative & Server Rule Impact (if applicable) + +- Does this feature introduce any new rule enforcement challenges or additional workload for admins? +- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? +- How are the rules enforced mechanically by way the feature will be implemented? + +# Technical Considerations + +This are all text / yaml changes, no technical considerations From 6d7db68e45657dacd234c0be4814705727377d63 Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Sun, 26 Apr 2026 00:40:31 -0300 Subject: [PATCH 02/53] Created the station_protocol_rework folder Copied the template, one for each article Added the Article files for each article --- .../Article 1 - Station Regulations.md | 0 .../Article 2 - Corporate law.md | 0 ...rticle 3 - Standard Operating Procedure.md | 0 .../Article 4 - Unions.md | 0 .../Article 5 - Trials and Hearings.md | 0 .../article-1_design_doc.md | 53 +++++++++++++++++++ .../article-2_design_doc.md | 53 +++++++++++++++++++ .../article-3_design_doc.md | 53 +++++++++++++++++++ .../article-4_design_doc.md | 53 +++++++++++++++++++ .../article-5_design_doc.md | 53 +++++++++++++++++++ 10 files changed, 265 insertions(+) create mode 100644 src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md create mode 100644 src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md create mode 100644 src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md create mode 100644 src/design-proposals/station_protocol_rework/Article 4 - Unions.md create mode 100644 src/design-proposals/station_protocol_rework/Article 5 - Trials and Hearings.md create mode 100644 src/design-proposals/station_protocol_rework/article-1_design_doc.md create mode 100644 src/design-proposals/station_protocol_rework/article-2_design_doc.md create mode 100644 src/design-proposals/station_protocol_rework/article-3_design_doc.md create mode 100644 src/design-proposals/station_protocol_rework/article-4_design_doc.md create mode 100644 src/design-proposals/station_protocol_rework/article-5_design_doc.md diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md new file mode 100644 index 00000000..e69de29b diff --git a/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md b/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md new file mode 100644 index 00000000..e69de29b diff --git a/src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md b/src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md new file mode 100644 index 00000000..e69de29b diff --git a/src/design-proposals/station_protocol_rework/Article 4 - Unions.md b/src/design-proposals/station_protocol_rework/Article 4 - Unions.md new file mode 100644 index 00000000..e69de29b diff --git a/src/design-proposals/station_protocol_rework/Article 5 - Trials and Hearings.md b/src/design-proposals/station_protocol_rework/Article 5 - Trials and Hearings.md new file mode 100644 index 00000000..e69de29b diff --git a/src/design-proposals/station_protocol_rework/article-1_design_doc.md b/src/design-proposals/station_protocol_rework/article-1_design_doc.md new file mode 100644 index 00000000..571655af --- /dev/null +++ b/src/design-proposals/station_protocol_rework/article-1_design_doc.md @@ -0,0 +1,53 @@ +# Short, Properly Capitalized Title + +Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. + +| Designers | Implemented | GitHub Links | +|---|---|---| +| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | + +`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: + +- This acknowledges credit where it is due +- People who are confused about the written intent can use this information to contact the authors + +`Implemented` is the status of the feature. + +Github links can include multiple PRs, if relevant. + +## Overview + +A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". + +## Background + +Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. + +Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. + +## Features to be added + +Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. + +## Game Design Rationale + +Consider addressing: +- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? + +## Roundflow & Player interaction + +Consider addressing: +- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? +- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? + +## Administrative & Server Rule Impact (if applicable) + +- Does this feature introduce any new rule enforcement challenges or additional workload for admins? +- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? +- How are the rules enforced mechanically by way the feature will be implemented? + +# Technical Considerations + +- Are there any anticipated performance impacts? +- Does the feature require new systems, UI elements, or refactors of existing ones? +- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file diff --git a/src/design-proposals/station_protocol_rework/article-2_design_doc.md b/src/design-proposals/station_protocol_rework/article-2_design_doc.md new file mode 100644 index 00000000..571655af --- /dev/null +++ b/src/design-proposals/station_protocol_rework/article-2_design_doc.md @@ -0,0 +1,53 @@ +# Short, Properly Capitalized Title + +Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. + +| Designers | Implemented | GitHub Links | +|---|---|---| +| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | + +`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: + +- This acknowledges credit where it is due +- People who are confused about the written intent can use this information to contact the authors + +`Implemented` is the status of the feature. + +Github links can include multiple PRs, if relevant. + +## Overview + +A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". + +## Background + +Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. + +Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. + +## Features to be added + +Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. + +## Game Design Rationale + +Consider addressing: +- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? + +## Roundflow & Player interaction + +Consider addressing: +- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? +- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? + +## Administrative & Server Rule Impact (if applicable) + +- Does this feature introduce any new rule enforcement challenges or additional workload for admins? +- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? +- How are the rules enforced mechanically by way the feature will be implemented? + +# Technical Considerations + +- Are there any anticipated performance impacts? +- Does the feature require new systems, UI elements, or refactors of existing ones? +- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file diff --git a/src/design-proposals/station_protocol_rework/article-3_design_doc.md b/src/design-proposals/station_protocol_rework/article-3_design_doc.md new file mode 100644 index 00000000..571655af --- /dev/null +++ b/src/design-proposals/station_protocol_rework/article-3_design_doc.md @@ -0,0 +1,53 @@ +# Short, Properly Capitalized Title + +Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. + +| Designers | Implemented | GitHub Links | +|---|---|---| +| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | + +`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: + +- This acknowledges credit where it is due +- People who are confused about the written intent can use this information to contact the authors + +`Implemented` is the status of the feature. + +Github links can include multiple PRs, if relevant. + +## Overview + +A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". + +## Background + +Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. + +Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. + +## Features to be added + +Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. + +## Game Design Rationale + +Consider addressing: +- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? + +## Roundflow & Player interaction + +Consider addressing: +- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? +- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? + +## Administrative & Server Rule Impact (if applicable) + +- Does this feature introduce any new rule enforcement challenges or additional workload for admins? +- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? +- How are the rules enforced mechanically by way the feature will be implemented? + +# Technical Considerations + +- Are there any anticipated performance impacts? +- Does the feature require new systems, UI elements, or refactors of existing ones? +- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file diff --git a/src/design-proposals/station_protocol_rework/article-4_design_doc.md b/src/design-proposals/station_protocol_rework/article-4_design_doc.md new file mode 100644 index 00000000..571655af --- /dev/null +++ b/src/design-proposals/station_protocol_rework/article-4_design_doc.md @@ -0,0 +1,53 @@ +# Short, Properly Capitalized Title + +Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. + +| Designers | Implemented | GitHub Links | +|---|---|---| +| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | + +`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: + +- This acknowledges credit where it is due +- People who are confused about the written intent can use this information to contact the authors + +`Implemented` is the status of the feature. + +Github links can include multiple PRs, if relevant. + +## Overview + +A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". + +## Background + +Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. + +Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. + +## Features to be added + +Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. + +## Game Design Rationale + +Consider addressing: +- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? + +## Roundflow & Player interaction + +Consider addressing: +- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? +- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? + +## Administrative & Server Rule Impact (if applicable) + +- Does this feature introduce any new rule enforcement challenges or additional workload for admins? +- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? +- How are the rules enforced mechanically by way the feature will be implemented? + +# Technical Considerations + +- Are there any anticipated performance impacts? +- Does the feature require new systems, UI elements, or refactors of existing ones? +- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file diff --git a/src/design-proposals/station_protocol_rework/article-5_design_doc.md b/src/design-proposals/station_protocol_rework/article-5_design_doc.md new file mode 100644 index 00000000..571655af --- /dev/null +++ b/src/design-proposals/station_protocol_rework/article-5_design_doc.md @@ -0,0 +1,53 @@ +# Short, Properly Capitalized Title + +Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. + +| Designers | Implemented | GitHub Links | +|---|---|---| +| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | + +`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: + +- This acknowledges credit where it is due +- People who are confused about the written intent can use this information to contact the authors + +`Implemented` is the status of the feature. + +Github links can include multiple PRs, if relevant. + +## Overview + +A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". + +## Background + +Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. + +Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. + +## Features to be added + +Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. + +## Game Design Rationale + +Consider addressing: +- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? + +## Roundflow & Player interaction + +Consider addressing: +- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? +- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? + +## Administrative & Server Rule Impact (if applicable) + +- Does this feature introduce any new rule enforcement challenges or additional workload for admins? +- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? +- How are the rules enforced mechanically by way the feature will be implemented? + +# Technical Considerations + +- Are there any anticipated performance impacts? +- Does the feature require new systems, UI elements, or refactors of existing ones? +- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file From 9582b107e1f998547955c0799f1a3ae9ed08be42 Mon Sep 17 00:00:00 2001 From: Alicios Date: Sat, 25 Apr 2026 21:09:34 -0700 Subject: [PATCH 03/53] Renamed Article V --- ...earings.md => Article 5 - Sentencing, Trials, and Hearings.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename src/design-proposals/station_protocol_rework/{Article 5 - Trials and Hearings.md => Article 5 - Sentencing, Trials, and Hearings.md} (100%) diff --git a/src/design-proposals/station_protocol_rework/Article 5 - Trials and Hearings.md b/src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md similarity index 100% rename from src/design-proposals/station_protocol_rework/Article 5 - Trials and Hearings.md rename to src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md From f763a6e29144cf5bd74cabeb1857afa669634d5a Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Thu, 30 Apr 2026 17:03:22 -0600 Subject: [PATCH 04/53] Regulations V1 Initial writeup for regulations. --- .../Article 1 - Station Regulations.md | 156 ++++++++++++++++++ 1 file changed, 156 insertions(+) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index e69de29b..e4b5b80f 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -0,0 +1,156 @@ +# Station Regulations + +Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. + +| Designers | Implemented | GitHub Links | +|---|---|---| +| SOP workgroup, Written by Scrambleking | :x: No | TBD | + +## Overview + +This document will cover NanoTrasen Station Regulations. These generaly dont fit specificaly in other catagories such as SOP and Law and so are gathered here. + + +## Background + +Station regulations includes Alert Levels, the Corporate Espionage Act, Permits and Paperwork, Fines, Extracorporate Entities, Insurance, and Order of Succession. + +None of this section is intended to be server level rules, and are mean to enrich the RP experiance for crew, along with providing guidance for characters in non-standard scenarios. + + +#Corporte Espionage Act +This section is intended to be in direct relation to the metashield on an OOC level along with IC justifications for the Crew/Security metashields and NDAs. +In character the majority of crew would understand this as related to NT's R&D into bluespace, genetics, artifacts, and anomolies, building off of the syndicate being a known orginisation that works against NT. +Security's addendum would be focused on the possiblity of additional threats past the syndicate or the like. + +## Administrative & Server Rule Impact +This section will be written under the explicit perview of, or by the hand of, the head admins. + + +#Permits and Paperwork +Permits and Paperwork cover what paperwork to use, when to use it, and what utensils to use with it. +EG: +To hire person X use Hiring Form 4.23, along with adendum 2 for hiring non-NT members +Access is only granted after filling out Access Form 6.23 C +Construction or modification of maints should be done with Construction Form 32.45 +All paperwork must be filled with a black-ink pen unless specified in... +Copies of official paperwork should be stamped by the relevant head + +## Game Design Rationale +By codifying the forms and permits it should make the system easier to navigate for newer players, and prevent abusive forms from making their way into printer files (I am personaly guilty of some of these). +Additionaly the Codification of paperwork is more authentic to a corprate experiance where files are flying about the home office every day. + +## Roundflow & Player interaction +In a round a player (just like anyone in a corporation) will know generaly what they will be required to fill out should they be asked for paperwork, and may even print and fill it out themselves, or with the help of the local librarian. + +## Technical Considerations +This section will require the implimentation of the Printing Machine. +The printing machine provides players with a way to quickly print forms in-round without needing a folder of documents they must search through. +2 versions of the printing machine should be avalible, a "secure" version for command/security use, and a "regular" version for crew use. +The "regular" version will contain documents that normal crew may need such as hiring applications, access requests, and construction permits. It will be kept in the library or simular areas. +The "secure" version will additionaly contain documents such as command/security hiring forms, NDAs, police reports ect. It will be kept behind access locked doors. + +This section will not require, but would greatly benefit from, the implimentation of fillable form fields. +This will make filling forms easier to understand for players without having to interprit rundown text. + + +#Fines +Fines are for when things are not fine. When you commit an SOP infraction or Corprate Law based infraction you may be ordered to pay a fine. +This section explains the who, how, and why of fines. It does not explain how this is diffrent from a governmentaly approved bribe. +Who can give them +Why they can be given +How to give them +How to pay them +It also covers the courses of action that the IAA can take. Primarily issuing a fine or asking the head of staff to take greater actions. + +## Game Design Rationale +This maintains authenticity because it provides a way for security to punish negative behavior without needing to haul the person all the way to security which would lower nantotrasen's profits. +This maximises RP potential because instead of a simple warning there is direct action taken against the person who can then chose to escalate, not pay, or dispute the fine. + +## Roundflow & Player interaction +This will provide a way for players to interact and begin escalation with security outside of reciving a warning, which is unsatisfying, and jail time, which could be over the top. + +It also provides the IAA with a more explicit path for punishments outside of taking possibly vital equiptment, or simply firing the person. + +## Administrative & Server Rule Impact (if applicable) +This section should have no administrative impact aside from role abuse, which generaly should be able to be dealt with in character with unions and escaltation. + +## Technical Considerations +Scrip is required. +We cant take away the money of someone without money. + +A fine computer/printer is not required, but could greatly benefit the system. +This would alow the security officer to print the fine recipt quickly, and the recipiant to pay it at the designated point. + + +#Extracorporate Entities +This section covers interactions with visitors to the station. Visitors are an under-used RP mechanic, and while this will by no means fix that, it will provide a direction to take the interactions with them. +The sections contained within include: +Shuttle rights +Docking +Trading +Treatment of visitors +Refugees +External hiring (temporary and complete contracts) + +## Game Design Rationale +Authenticaly, any large port will also have regulations for how to interact and treat visitors from other orginisations. This would be especialy true for a corprate research colony that knows of spies. + +## Roundflow & Player interaction +This is not intended to effect the flow of most rounds, but should alow for rounds that do interact with visitors to have more guidance than "oh ok, I geuss your visiting now" +Idealy this will make even mundane visitors have a level of impact with the personel on the station through things such as medical checkups and acnowladgement of visitation. + +## Technical Considerations +Maps will require a designated "visitor" dock. + +Visitor shuttles will need some way to broadcast their pressence. + +While not required, IDs and PDAs can be removed from non-NT/infiltration aligned visitors. This will also provide a noticable distinction between roles that are part of NT (such as a CMO in an escape pod), and visitation roles that are simply visiting. + +#Insurance +NOTE: Insurance is something that will not be directly added by this workgroup as it is outside of our intended scope, it is merely here as an example that could be added in the future. +This would create a codified explanation of what each insurance level entails: +What premiums you may have to pay each shift +Coverage of injuries +Coverage of non-health related surgeries +Cybernetics + +# Alert Levels +Not exactly new, alert levels have been moved from SOP to regulations as they are called for situations that are not standard. +Most alert levels are the same, however in a more specific PR we will likely be looking at changes to what leads to calling a blue alert. +Additionaly RED alert now alows the captain to deem specific SOP as suspended, this replaces the SOP per alert level SOP. +This is also being done to reduce confusion about alert levels being SOP, and possibly making it enforceable by security instead of the CCVIPs which was always an odd position for them. + + +# Order of Succession and Martial Law +The Order of Succession determins who will be next in line for the captain position. +EG: +Captain +HoP +RD +QM +CMO +CE +HD (Hospitality director, expended on in job changes) +Acting command with the above order +HoS + +This can be triggered via a vote of no confidance amongst command. This is started by the CCVIPs, or by the CMO deeming the captain as unfit for duty. + +The Head of Security will take over the station until a suitable captain replacement can be found, at which point power will be relinquished to them. +Martial law can be declared by the HoS once no other suitable replacements for the captain can be made. + +Under martial law security’s orders are final, personnel are to immediately return to their departments or bar unless given explicit permission otherwise, and failure to do so leaves punishment at the discretion of the witnessing officer. +This includes engineering and medical personnel who are responding to emergencies, and scientists responding to anomalies. + +## Game Design Rationale +This goes mostly to authenticity, in an emergancy the HoS is intended to have an overview of the security situation, while the captain has an overview of the station as a whole. +Given this is the case, the HoS should not be focused on the extrenous duties of the captain. +Additionaly the station is a Corporate orginisation who's focus is on profit, not simply "catching the bad guy" and this change is meant to highlight this. +Should all command and potential command die, the only authority on the station is the HoS and security, who should not be treating the station as lightly as a regular command member. +The reason the martial law power was specificaly granted is, should the situation become dire enough to require the HoS to become captain, they will likely be in a situation more severe than red alert. + +Martial law is not automaticaly called upon the HoS's promotion due to outlier shifts such as lowpop, or no other command in a lobby willing to play capatain. + +## Technical Considerations +Possibly an alert level for "Martial Law" can be made, or taken from an existing alert level. From ea0658473fd60794f43d27633b6b4077a4a919e8 Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Thu, 30 Apr 2026 17:03:59 -0600 Subject: [PATCH 05/53] Small update to Regulations --- .../station_protocol_rework/Article 1 - Station Regulations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index e4b5b80f..bdc39892 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -107,7 +107,7 @@ Visitor shuttles will need some way to broadcast their pressence. While not required, IDs and PDAs can be removed from non-NT/infiltration aligned visitors. This will also provide a noticable distinction between roles that are part of NT (such as a CMO in an escape pod), and visitation roles that are simply visiting. -#Insurance +# Insurance NOTE: Insurance is something that will not be directly added by this workgroup as it is outside of our intended scope, it is merely here as an example that could be added in the future. This would create a codified explanation of what each insurance level entails: What premiums you may have to pay each shift From 21e77ba976ded2b56379ac10a3fc2272b3e2dd67 Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Thu, 30 Apr 2026 17:04:33 -0600 Subject: [PATCH 06/53] ACH one more to Regulations --- .../station_protocol_rework/Article 1 - Station Regulations.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index bdc39892..24a6dad3 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -109,6 +109,7 @@ While not required, IDs and PDAs can be removed from non-NT/infiltration aligned # Insurance NOTE: Insurance is something that will not be directly added by this workgroup as it is outside of our intended scope, it is merely here as an example that could be added in the future. + This would create a codified explanation of what each insurance level entails: What premiums you may have to pay each shift Coverage of injuries From f85f073719168421e4308229986819c9cbb459fc Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Thu, 30 Apr 2026 17:05:34 -0600 Subject: [PATCH 07/53] I swear last one to Regulations --- .../Article 1 - Station Regulations.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index 24a6dad3..5206eaf3 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -126,15 +126,15 @@ This is also being done to reduce confusion about alert levels being SOP, and po # Order of Succession and Martial Law The Order of Succession determins who will be next in line for the captain position. EG: -Captain -HoP -RD -QM -CMO -CE -HD (Hospitality director, expended on in job changes) -Acting command with the above order -HoS +1. Captain +2. HoP +3. RD +4. QM +5. CMO +6. CE +7. HD (Hospitality director, expended on in job changes) +8. Acting command with the above order +9. HoS This can be triggered via a vote of no confidance amongst command. This is started by the CCVIPs, or by the CMO deeming the captain as unfit for duty. From fba5689b45a59b4edf7c6b3a2507cec739dc7f1f Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Thu, 30 Apr 2026 17:07:22 -0600 Subject: [PATCH 08/53] Ok for real this time Regulations --- .../Article 1 - Station Regulations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index 5206eaf3..afa1c3f1 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -18,7 +18,7 @@ Station regulations includes Alert Levels, the Corporate Espionage Act, Permits None of this section is intended to be server level rules, and are mean to enrich the RP experiance for crew, along with providing guidance for characters in non-standard scenarios. -#Corporte Espionage Act +# Corporte Espionage Act This section is intended to be in direct relation to the metashield on an OOC level along with IC justifications for the Crew/Security metashields and NDAs. In character the majority of crew would understand this as related to NT's R&D into bluespace, genetics, artifacts, and anomolies, building off of the syndicate being a known orginisation that works against NT. Security's addendum would be focused on the possiblity of additional threats past the syndicate or the like. @@ -27,7 +27,7 @@ Security's addendum would be focused on the possiblity of additional threats pas This section will be written under the explicit perview of, or by the hand of, the head admins. -#Permits and Paperwork +# Permits and Paperwork Permits and Paperwork cover what paperwork to use, when to use it, and what utensils to use with it. EG: To hire person X use Hiring Form 4.23, along with adendum 2 for hiring non-NT members @@ -54,7 +54,7 @@ This section will not require, but would greatly benefit from, the implimentatio This will make filling forms easier to understand for players without having to interprit rundown text. -#Fines +# Fines Fines are for when things are not fine. When you commit an SOP infraction or Corprate Law based infraction you may be ordered to pay a fine. This section explains the who, how, and why of fines. It does not explain how this is diffrent from a governmentaly approved bribe. Who can give them @@ -83,7 +83,7 @@ A fine computer/printer is not required, but could greatly benefit the system. This would alow the security officer to print the fine recipt quickly, and the recipiant to pay it at the designated point. -#Extracorporate Entities +# Extracorporate Entities This section covers interactions with visitors to the station. Visitors are an under-used RP mechanic, and while this will by no means fix that, it will provide a direction to take the interactions with them. The sections contained within include: Shuttle rights From 14e7fca07cbade58377c67a97b51649f14390928 Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Sat, 2 May 2026 02:12:50 -0600 Subject: [PATCH 09/53] Regulations, Final Final Final Final The final one for sure --- .../Article 1 - Station Regulations.md | 24 ++++++++++++++----- 1 file changed, 18 insertions(+), 6 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index afa1c3f1..9c1e0139 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -8,20 +8,22 @@ Your title should convey the basic jist of your proposed changes. It should be s ## Overview -This document will cover NanoTrasen Station Regulations. These generaly dont fit specificaly in other catagories such as SOP and Law and so are gathered here. +This document establishes a comprehensive framework for in-character station regulations intended to enhance roleplay depth, structure player interactions, and provide clear guidance in non-standard scenarios. +Rather than functioning as enforceable server rules, these systems are designed to simulate the bureaucratic, procedural, and corporate realities of a Nanotrasen-operated facility. +The regulations outlined here expand on existing mechanics by formalizing processes such as corporate security protocols, administrative paperwork, fines, visitor interactions, and command hierarchy. +Each section is supported by game design rationale, roundflow considerations, and (where applicable) technical implementation notes to ensure both usability and immersion. -## Background +While not all features are required for immediate implementation, this document serves as both a design foundation and a roadmap for future development, prioritizing systems that improve clarity, consistency, and player engagement without overburdening gameplay. -Station regulations includes Alert Levels, the Corporate Espionage Act, Permits and Paperwork, Fines, Extracorporate Entities, Insurance, and Order of Succession. +## Background -None of this section is intended to be server level rules, and are mean to enrich the RP experiance for crew, along with providing guidance for characters in non-standard scenarios. +Not everything that *was* SOP or law perfectly fits within the older sections of them, as such we are creating the "station regulations" to be a catch all for NT's rules that dont quite fit into our other primary catagories. # Corporte Espionage Act This section is intended to be in direct relation to the metashield on an OOC level along with IC justifications for the Crew/Security metashields and NDAs. -In character the majority of crew would understand this as related to NT's R&D into bluespace, genetics, artifacts, and anomolies, building off of the syndicate being a known orginisation that works against NT. -Security's addendum would be focused on the possiblity of additional threats past the syndicate or the like. +In character the majority of crew would understand this as related to NT's R&D into bluespace, genetics, artifacts, and anomolies, building off of the syndicate being a known orginisation that conducts espionage. ## Administrative & Server Rule Impact This section will be written under the explicit perview of, or by the hand of, the head admins. @@ -53,6 +55,16 @@ The "secure" version will additionaly contain documents such as command/security This section will not require, but would greatly benefit from, the implimentation of fillable form fields. This will make filling forms easier to understand for players without having to interprit rundown text. +# Building/Construction code + +This section would define what is a "baseline" room via atmosphere, construction, types of walls/windows to use when, firelocks and air alarms, ect. + +## Game Design Rationale +In game this would serve as an effective tutorial to building and room construction for newer engineers/players, and can be referenced in the permits system for construction. +This creates a more authentic experiance to newer players and intergrates the guidebook further into the world as a "real" learning tool. + +## Roundflow & Player interaction +This should have minimal impact on roundflow outside of obtaining permits and teaching/learning construction. # Fines Fines are for when things are not fine. When you commit an SOP infraction or Corprate Law based infraction you may be ordered to pay a fine. From cf590a80020906fd6efe3df4abbca92e42a6167c Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Mon, 4 May 2026 13:27:59 -0300 Subject: [PATCH 10/53] Filled out the main doc a bit more --- .../station_protocol_rework.md | 31 +++++++++++++------ 1 file changed, 21 insertions(+), 10 deletions(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index 3fcced64..4dfc2b4a 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -27,7 +27,6 @@ Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Prom ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. -While a name change may not seem that important, it set's the tone of what to expect. ### Article 3 - Standard Operating Procedure @@ -40,7 +39,7 @@ While a name change may not seem that important, it set's the tone of what to ex ### Extra considerations "Behavior follows incentives" -While this PR focuses only on the regulations themselves, many supporting changes will need to be done to mechanically enforce the vision Funky station has. +While this PR focuses only on the regulations themselves, many supporting changes will need to be done to mechanically enforce the new vision Funky Station has. The SOP workgroup is working on other design docs that should help change that situation and align mechanics with the text and intent behind them. ## Game Design Rationale @@ -48,18 +47,30 @@ The SOP workgroup is working on other design docs that should help change that s Consider addressing: - How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? +Mention: +New Theming +Escalation Oportunities by non antags, and more options for antags +Seriously Silly (clown exemption :godo:) +Autenticity increased with: +- The use of some legaleese +- More atuned to the theme and NT's opression +Take things slow (point at trials) +Maximixing RP Potential is all over the place in this doc +Dynamic Environment respected, as it all depends on where players want to take this + ## Roundflow & Player interaction -Consider addressing: -- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? -- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? +All of the changes done here will affect every shift. The players will have to interact with all the changes proposed here as SOP, Corporate Law, Trials, and Unions will permiate every round on Forky. +While how much each individual part affects each round varies, it all depends on the players roleplaying to see the direction the round will take. +Mechanically speaking Sec, IAAs, and Department Heads will be the ones enforcing the changes proposed here, as they have the power to enact IC punishment on the people who break SOP or Corpo Law. ## Administrative & Server Rule Impact (if applicable) -- Does this feature introduce any new rule enforcement challenges or additional workload for admins? -- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? -- How are the rules enforced mechanically by way the feature will be implemented? +We expect the workload for the admins to increase for a bit while the players get used to the new changes, but it should go back to baseload after that +Most things done here are expected to be broken by players with a "play your character" mindset. The proposed changes add more ways for escalation to happen, and that may cause some OOC player friction, but we trust Funky Station players are mature enough to interact with this and enjoy the storylines formed on a round + -# Technical Considerations +## Technical Considerations -This are all text / yaml changes, no technical considerations +Check each individual PR to see the technical considerations. +95% of the changes proposed here are YAML or FTL/Text changes From 2da0cad75f48f8d37f7c6f36726e09d6c24d2a97 Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Mon, 4 May 2026 14:42:33 -0300 Subject: [PATCH 11/53] Initial draft for Article 2 Design Doc --- .../article-2_design_doc.md | 112 +++++++++++++----- 1 file changed, 82 insertions(+), 30 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/article-2_design_doc.md b/src/design-proposals/station_protocol_rework/article-2_design_doc.md index 571655af..dbf47dcd 100644 --- a/src/design-proposals/station_protocol_rework/article-2_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-2_design_doc.md @@ -1,53 +1,105 @@ -# Short, Properly Capitalized Title - -Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. +# Nanotrasen Colonial Law and Procedure: Corporate Law | Designers | Implemented | GitHub Links | |---|---|---| -| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | +| SOP Workgroup, design doc authored by Joaco545 | :x: | TBD | -`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: +## Overview -- This acknowledges credit where it is due -- People who are confused about the written intent can use this information to contact the authors +This proposal aims to revamp Space Law completely, while keeping the new theme direction in mind. -`Implemented` is the status of the feature. +Space law has been revised to conform to the style of a legal document. +The crime list has been expanded, and sentencing guidelines have been simplified. +Contraband has been vaguelawed. -Github links can include multiple PRs, if relevant. +## Background -## Overview +Funky Station has been changed to have a Corporation vs Crew / Class Conflict theme. This requires updating Space Law as it no longer fits the theme. +Currently, space law feels like something an external entity that is not Nanotrasen has set in place, and is forcing NT to comply with it; We aim to change that feeling completely. +We also took this opportunity to add some things to increase the RP potential, coupled with the [sentencing changes](article-5_design_doc.md). -A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". -## Background +## Features to be added -Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. +To see all the new proposed changes to Corporate Law, please check out the [supporting doc](Article%202%20-%20Corporate%20law.md) with the draft (Still not up at the time of commiting this, for now, the things can be found on the [Google doc under the Article 2 tab](https://docs.google.com/document/d/1HhQ9L_5KLPLiYH3W9_V8gIqyjH2lBxOt-W90n76cLtY/edit?tab=t.ushwxj8tclf6#heading=h.x3qf6opli0z2). Yes Tay, this link is temporary) -Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. +### Space Law rename +While it may not seem like much, Space Law has been renamed to Corporate Law to better fit the theme of NT owning you, the station, and all surrounding space. You are in their house, you play under their rules. -## Features to be added +### Corporate Law: Searches +The way searches are conducted has been reworded with a bit more legalese, and in the case of departmental searches, they have been made clearer as to what is included, and especially what's NOT included (personnel). + +### Corporate Law: Detainment and Arrests +There is now a difference between being detained and being arrested: +Detained means the person is not free to go. It is here mostly for the investigation part, not letting suspects go free until you have the evidence you need. +Arested means that the person will be guided to security for search and a subsequent trial. +In both cases, the detainees or arrestees should not be cuffed if they are complying. + +### Corporate Law: Chain of Custody +This specifies how Security is expected to play out each of the steps from arrest to the brig. This is mostly a supporting change for [Sentencing, Trials, and Hearings](article-5_design_doc.md). +This ups the standards Security personnel are held toin-character, while giving good lawyers more tools to finagle their clients out of a sentence, or at least enter a reduced one. + +### Corporate Law: Treatment of Arrestees and Prisoners +This section is kept mostly the same as the old treatment of prisoners. + +### Corporate Law: Implantation +This section is kept mostly the same as before, with a bit more legalese. + +### Corporate Law: List of Crimes +This area has been majorly reworked and expanded. NT now has more ways to get employees who are not behaving. + +#### Crime Categories +The tier system has been revamped into 4 named crime tiers: +- Infraction: They cover minor offenses, which do not lead to brig time. +- Misdomenor: They cover more serious offenses, which can lead to brig time. +- Felony: They cover serious crimes, can lead to more brig time. +- Capital Offenses: They deal with the most serious crimes against NT, can lead to permanent confinement, contract termination, or execution. + +Note: Execution requires Captain and XO (HOP) approval + +Big times have been standardized so that sentencing gets easier. They now directly depend on their category, instead of the individual crime. + +The crime list has also been expanded to give NT more power over how people and unions behave. The line between a strike and a riot is a thin one. +We expect security vs crew to increase the friction between NT-Command and the Crew, giving more opportunities for escalation should the players choose to do so. + +#### Infraction enforment +Infractions are not meant to be something everyone needs to go to a judge for; They will be handed out by Security. +These two new things will need to be implemented: +- Sec will need to get a new device capable of printing fines, and; +- An ATM-like device near the courtroom that allows players to pay the fine, or page the judge to dispute it. + As a perverse incentive, fines will go to the Security department’s budget, and the Head of Security will be able to use those funds to buy things for the team or increase the pay of Security employees. + + +### Corporate Law: Contraband Classifications +Old Contraband has been replaced by Vaguelawed Contraband. To support this change, contraband markers will need to be removed from the game. +These changes were made to increase the RP potential, as now, confiscating something is a choice to be made by players, and not by a marker. +This also makes meteshielded components harder to identify, as again, there is no marker, making confiscation a must (Syndicate pajamas, anyone?) +It is also another way for escalation to happen is Sec confiscates too much or too little with the crew and command, respectively + +### Corporate Law: Legal Exemptions +Certain jobs may be except of certain laws under certain conditions, this includes security's monopoly on violence, or more mundane things like engi breaking into places to fix a fire. + +#### Clown Exception +The clown crime exception has been re-added for some Seriously Silly points. +It has a couple more caveats to reduce the scope of what the clown can do, while also requiring the judge to find it funny for the exemption to apply. -Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. ## Game Design Rationale -Consider addressing: -- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? +A lot of these changes have been done with two pillars in mind: -## Roundflow & Player interaction +- New Theming / Authenticity + Working on an NT Space Station will now feel more oppressive for the normal workers, while unions act as a small reprieve, NT still has a lot of power inside and outside the station. It makes the story being told more coherent. -Consider addressing: -- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? -- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? +- Escalation / Maximising roleplay potential + The features mentioned in this doc all aim to keep the same level of RP or increase it. -## Administrative & Server Rule Impact (if applicable) -- Does this feature introduce any new rule enforcement challenges or additional workload for admins? -- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? -- How are the rules enforced mechanically by way the feature will be implemented? +## Roundflow & Player interaction + +Corporate Law is something that will permeate each round from roundstart, and all players will have to engage with it. +While common sense will keep most players outside of Securities radar, it will still be something present. -# Technical Considerations +## Administrative & Server Rule Impact (if applicable) -- Are there any anticipated performance impacts? -- Does the feature require new systems, UI elements, or refactors of existing ones? -- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file +As mentioned on the main doc, with so many changes we think players will AHelp more to ask for clarification on said changes. From ec94d3da9e32f66c62b9665ffcf3201c40a26c6a Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Mon, 4 May 2026 21:49:24 -0300 Subject: [PATCH 12/53] Initial export of the law itself. Kinda need Githubs MD viewer to adjust now --- .../Article 2 - Corporate law.md | 399 ++++++++++++++++++ 1 file changed, 399 insertions(+) diff --git a/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md b/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md index e69de29b..df3abf12 100644 --- a/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md +++ b/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md @@ -0,0 +1,399 @@ +# NanoTrasen Corporate Law +## Table of Contents: +Legal Definitions +Searches +Detainment & Arrests +Chain of Custody +Treatment of Arrestees +Implantion +List of Crimes +Contraband Classifications +Legal Exemptions + +--- + +## 1. Definitions: +NT: NanoTrasen +Charge: Accused Crimes. +Sentence: Officially recognized crimes by a Judge, with accompanying punishment. +Arrest: Under restraint by Security, in order to press charges before a judge. +Custody: Under restraint by Security, during or after receiving a sentence. +Detainee: Any being who is being temporarily held. +Arrestee: Any being either arrested or in custody. +Excessive Force: More than needed for the situation. (eg. gibbing) +Criminal Offense: Charges/Sentences that can result in arrests and/or brig time. +Sentient Being: A living entity capable of thought. +Sapient Being: A living entity that is capable of fully comprehending itself, its surroundings, and other sapient beings. +Privileged Individuals: Referees to Command Members and Central Command VIP’s +Death: Fully deceased. Critical condition does not count as death. +Operational Safety: The ability for the station, departments, and crew as a whole to perform work unimpeded. +Reasonable Suspicion: Enforcement personnel either directly witnessing or receiving credible information about potential illegal activity. Valid Reasonable Suspicion is more than a simple hunch or instinct, and must be based on clear facts. +Probable Cause: Enforcement personnel either directly witnessing or receiving credible information about an actual crime committed. + +--- + +## 2. Searches + +### Personnel Searches +Security personnel are allowed to search personnel under the following conditions: +1. There is reasonable suspicion of a crime +2. There is a search warrant for the being +3. The station’s alert level allows for random searches + +The search could lead to the seizure of the objects in a person's backpack, hands, coat, belt, pockets, headset, and hat. This includes any bags, boxes or other containers the person has in the immediate vicinity. + +A crewmate may legally decline any search conducted without reasonable suspicion while the alert level is green. + +If any contraband is found during a search the officer may choose to further the search into an arrest, or confiscate the restricted items and issue a fine. After the search is conducted all legal items are to be returned to the person. + +#### Invasive confiscation +Sometimes crewmembers may have contraband that requires surgery to remove. +Removal of body augmentation contraband should be done by medical personnel and not cause excessive harm or leave the person's body nonfunctional. + +### Department searches +Security personnel are allowed to search a department under the following conditions +1. There is a search warrant signed by the appropriate Department Head, Head of Personnel or Captain +2. The station’s alert level allows for the departmental search + +Security personnel should minimize the interruption of work from the department +- Personnel should be able to work +- Search time should be kept to a minimum + +Secure Areas are not be searched unless otherwise EXPLICITLY authorized by the head of that department, or higher + +Anything, excluding personnel, within the areas defined on the searched warrant can be searched. This includes but is not limited to: +- Crates +- Lockers +- Machines +- Plants + +The Head of Personnel may issue ID’s with temporary access for the purposes of fulfilling a search warrant. + +--- + +## 3. Detainment & Arrests +Security personnel are allowed to temporarily detain anyone with only a reasonable suspicion of a crime. +Detainment reasons include: +1. Performing a search +2. Investigating a crime +3. Handing out a fine + +Security Personnel are allowed to arrest only with probable cause of a crime. +Arrest reasons include: +1. Directly witnessing a crime. +2. Having suitable forensic evidence of a crime. +3. Eyewitness report from a trustworthy individual. + +Detained and arrested individuals should not be handcuffed, provided they are cooperating. +Cuffing of a detainee or arrestee should only happen if: +1. The subject poses a clear threat towards: + * Command staff + * Security officers + * Station assets +2. The subject is non-cooperative, or resisting enforcement authority. + +--- + +## 4. Chain of Custody +All enforcement personnel are held to a high standard when interacting with the public. +Proper protocol is to be followed, in order to ensure that subjects of legal enforcement are given due process, and retain any and all rights they may hold. + +Enforcement Personnel are to follow the following procedure with any arrest. +Failure to follow this procedure may result in formal Disciplinary Actions by onboard CC staff, or in extreme cases, charges of negligence and/or endangerment. + +1. Given Probable Cause, the officer must state their intent to arrest, and for what crimes, before taking any forceful action. + * Proper intent includes using a security voice mask, calling their name or job, and/or pointing at them and telling them to stop. + * This step may be waived if the target is the subject of a Red Alert, or if they are declared “Arrest on Sight” by the Head of Security. +2. If the subject fails to stop when asked, or attempts to evade lawful arrest, forceful action and restraints may be used to take them in. + * Batons, flashes, and handcuffs should be prioritized first, but if all less-lethal options are disabled, stolen, or otherwise ineffective, lethal force is authorized and encouraged. + * Heavy weaponry is only permitted to perform an arrest if the subject is the target of a Red Alert, or is a clear militarized danger to the station. +3. After successful detainment, the officer is to alert the Head of Security and Judicial Officer as soon as possible, so that all involved parties may prepare for a Hearing or Trial. +4. Recovery of the arrestee’s bodily health is to be ensured before any other enforcement actions. + * Any further legal actions taken before the arrestee is stabilized are to be considered invalid. +5. The arrestee may optionally be brought to security to remove and confiscate any immediately dangerous contraband, before moving on to the Hearing or Trial. +6. In the case of a Formal Hearing or Trial, the arrestee must be informed of their right to a lawyer, and be provided one upon request. + * For Summary Hearings, the arrestee does not have to be offered a lawyer, but still must be provided one upon request. +7. The arrestee is to be brought to court, before the Judicial Officer, where they receive their official sentence via Hearing or Trial. +8. Should their sentence result in brig time, the officer is to transport and hand the prisoner off to the Warden. +9. The Warden performs a thorough search of the prisoner’s belongings, and ensures they are properly stored in their locker before handing them their prisoner ID and transporting them to the brig. + +At any point during a prisoner’s arrest or confinement, the Detective is permitted to bring them into interrogation and question them. +* The prisoner may ask for consultation with a Lawyer, during which their sentence is to be paused. +* The prisoner’s sentence is not to be paused during interrogation. + +--- + +## 5. Treatment of Arrestees and Prisoners +Personnel in custody are to be ensured the following rights: + +### Arrestees +Arrestees must be provided with: +1. Adequate medical care +2. Access to communications equipment so long as they are not abused +3. Access to a lawyer, should they request it + * This includes during interrogations and the subsequent hearing + +### Prisoners +On top of the arrestee’s protections, prisoners must be provided with: +1. Clothing, food, water, shelter and safety + * Should the Brig be rendered unsafe, confinement must be established in another location +2. Psychiatric and spiritual counselling if requested +3. Access to their shift mandated PDA after confinement has finished + * Unless there is solid proof of PDA tampering, in which case the PDA is to be secured and replaced with a fresh one before confinement ends +4. Freedom of movement. +5. Prisoners should not be restrained with handcuffs or other devices after incarceration unless there is an undue risk to life and limb + +--- + +## 6. Implantation +Any crewmate can be implanted if they give their clear permission. + +Any prisoner in custody can be subjected to implantation or implant removal procedures, so long as it's within reason. The process of adding an implant should not prolong the detainees sentence, or prevent them from leaving the brig to administer the implantation procedure. + +### Implantation +MindShields: MindShields can be administered to any inmate who has had their free will suppressed. Unlike standard implantation, you may hold a prisoner until they are issued a MindShield, so long as it's done in a timely fashion. If a suspect refuses to cooperate or the implant fails to function they can be charged with Refusal of Mental Shielding. + +While under normal circumstances a crewmate can refuse a Mind Shield if they are not imprisoned, when there is a known threat to the station that utilizes mass brainwashing or mind control, crewmates must submit to a MindShield if ordered by Security. Failure to comply is to be treated as Refusal of Lawful Implantation. + +### Removal +A suspect can be forced to receive implant removal if there is probable cause that they have an illegal implant, such as an officer witnessing them use an implantation device or their biological information being found on a discarded injector. + +Unlike the implantation procedure a prisoner can have their sentence entirely delayed or extended until they comply with the removal, as long as security are actively making attempts to perform it. Akin to implanting, if an inmate gives their clear permission, implant removal can proceed without proof. + +--- + +## 7. List of Crimes + +### Crime Tiers: +* **Infraction** + * Minor, non-criminal offenses, especially if they are easily reversible. + * Possible Punishments: + * Tickets/Fines, Pay Docking, Formal Warnings. + * Explicitly do not result in brig time. + * Punishments for Infractions aren’t supposed to majorly interrupt the offender’s productivity. + +* **Misdemeanor** + * Crimes that cause harm to others or asset loss, and aren’t as easily reversible. + * Possible Punishments: + * 10-15 Minute Brig Time. + * Demotion within the department. + +* **Felony** + * Crimes that cause major harm, major asset loss, and/or are a major threat to operational safety. + * Possible Punishments: + * 20+ Minute Brig Time. + * Demotion out of department. + +* **Capital Offense** + * Crimes that cause irreversible harm or asset loss, and/or majorly disrupt the operational safety. + * Possible Punishments: + * Permanent Brig Sentence. + * Contract Termination. + * Execution + + +### NanoTrasen defines the following Infractions and Criminal Offenses: +| Infractions | Misdemeanors | Felonies | Capital Offenses | +| :---- | :---- | :---- | :---- | +| Loitering (A) | Trespass (A) | Secure Trespass (A) | | +| Possession of Minor Contraband (C) | Possession of Moderate Contraband (C) | Possession of Major Contraband (C) | | +| Substance Abuse (C) | | | | +| Vandalism (D) | Destruction of Property (D) | Mass Destruction (D) | Sabotage (D) | +| Refusal to Identify (F) | Impersonation (F) | | Impersonation of Central Command (F) | +| Mail Fraud (F) | | Fraud (F) | | +| | Contempt of Court (J) | Perjury (J) | Subversion of Court (J) | +| Harassment (M) | | Extortion (M) | Terrorism (M) | +| Negligence (N) | Endangerment (N) | Manslaughter (N) | Capital Negligence (N) | +| Operation without Permit (O) | | Black Marketeering (O) | | +| Disturbance (R) | | Rioting (R) | | +| Failure to Comply (S) | Breach of Detainment (S) | Breach of Arrest (S) | Breach of Custody (S) | +| Petty Theft (T) | Theft (T) | Grand Theft (T) | | +| Slander (U) | | Libel (U) | Sedition (U) | +| Insubordination (U) | | | | +| | Battery (V) | Incapacitation (V) | Murder (V) | +| | Assault (V) | Mutilation (V) | Prevention of Revival (V) | +| | | Kidnapping (W) | Suppression of Free Will (W) | +| Cannibalism | Animal Cruelty | Bribery | Refusal of Lawful Implantation | +| | | Tax Evasion | Breach of NT Contract | + +### Crime Specifications: +| A | Access | Existing where you are not allowed. | +| :---- | :---- | :---- | +| Infraction | Loitering | Existing near a restricted area for an extended time, with no reasonable purpose. | +| Misdemeanor | Trespass | Entering a restricted area without express permission. | +| Felony | Secure Trespass | Entering a station-critical restricted area without express permission. | + +| C | Contraband | Possession or use of controlled, restricted, or illegal contraband. | +| :---- | :---- | :---- | +| Infraction | Substance Abuse | Consumption or usage of contraband substances. | +| Infraction | Possession of Minor Contraband | See Contraband Classifications. | +| Misdemeanor | Possession of Moderate Contraband | See Contraband Classifications. | +| Felony | Possession of Major Contraband | See Contraband Classifications. | + +| D | Destruction | Causing intentional damage to station functions. | +| :---- | :---- | :---- | +| Infraction | Vandalism | Superficially damaging or defacing station property. | +| Misdemeanor | Destruction of Property | Causing substantial structural damage, requiring repairs. | +| Felony | Mass Destruction | Causing substantial structural damage to a large area of the station. | +| Capital Offense | Sabotage | Intentionally rendering critical station infrastructure inoperable. | + +| F | Fraud | Lying about yourself or your actions for personal gain. | +| :---- | :---- | :---- | +| Infraction | Refusal to Identify | Not wearing your shift-assigned ID, and/or hiding your identity with facial coverings, and refusing to present your identity when asked by an authority. | +| Infraction | Mail Fraud | The unauthorized opening or tampering of mail intended for another individual. | +| Misdemeanor | Impersonation | Hiding your true identity and posing as someone you are not for personal gain. | +| Felony | Fraud | Intentionally lying about promised actions for personal gain, or not following through with non-NT contracts. | +| Capital Offense | Impersonation of Central Command | Hiding your true identity and posing as Central Command, including CCVIP staff. | + +| J | Obstruction of Legal Justice | Impeding or abusing the legal justice system. | +| :---- | :---- | :---- | +| Misdemeanor | Contempt of Court | Needlessly interrupting or delaying official court proceedings. | +| Felony | Perjury | Lying under oath of court, or delivering false reports to Security. | +| Capital Offense | Subversion of Court | Obstructing court to the point where official court proceedings have to pause or stop altogether. | + +| M | Manipulation | Manipulating a sapient being through tactics of fear and/or aggression. | +| :---- | :---- | :---- | +| Infraction | Harassment | Unwelcome, knowing, and repeated negative conduct toward a sapient being, causing them to feel seriously uncomfortable, annoyed, or afraid. | +| Felony | Extortion | Forcing another sapient being to do something unwillingly, by means of threats, force or aggression. | +| Capital Offense | Terrorism | Causing mass station panic, or completely disrupting station operations by means of fear and/or lethal force. | + +| N | Negligence | Causing harm to the station or its crew through vocational incompetence. | +| :---- | :---- | :---- | +| Infraction | Negligence | Unintentionally performing your assigned job’s duties in a way that creates unnecessary risk or harm. | +| Misdemeanor | Endangerment | Willfully performing your assigned job’s duties in a way that creates unnecessary risk or harm. | +| Felony | Manslaughter | Killing another sapient being without intent. | +| Capital Offense | Capital Negligence | Performing a Command position’s duties in a way that causes unnecessary risk or harm, to the point of causing mass station-destruction, or rendering a department mostly inoperable, even temporarily. | + +| O | Operation | Performing works or transactions not sanctioned by NanoTrasen. | +| :---- | :---- | :---- | +| Infraction | Operation without Permit | Performing another department’s duties, or some other business venture without a legal permit of operation. | +| Felony | Black Marketeering | Engaging in the buying and/or selling of contraband. | + +| R | Rowdiness | Causing public disturbances and unrest. | +| :---- | :---- | :---- | +| Infraction | Disturbance | Catch-all for public disruptive or obnoxious behavior. | +| Felony | Rioting | Participating in unlawful protests, especially in the cases where damages are incurred. | + +| S | Obstruction of Security | Going against or obstructing lawful Security actions. | +| :---- | :---- | :---- | +| Infraction | Failure to Comply | Refusing to comply with lawful demands of Security personnel. | +| Misdemeanor | Breach of Detainment | Escaping from custody while not being free to go. | +| Felony | Breach of Arrest | Breaking free of restraints during an arrest. | +| Capital Offense | Breach of Custody | Escaping from custody during or after receiving a legal sentence. | + +| T | Theft | Taking that which belongs to others. | +| :---- | :---- | :---- | +| Infraction | Petty Theft | Taking something that is mostly worthless or easily replaceable. | +| Misdemeanor | Theft | Taking something of meaningful value. | +| Felony | Grand Theft | Taking something that is critical to the person’s job or role. | + +| U | Undermining NanoTrasen Authority | Spreading dissent about or disrespecting NanoTrasen authority. | +| :---- | :---- | :---- | +| Infraction | Slander | Speaking false and harmful statements about Command or NanoTrasen. | +| Infraction | Insubordination | Disobeying Command’s orders without reasonable justification. | +| Felony | Libel | Publishing false and harmful written statements about Command or NanoTrasen. | +| Capital Offense | Sedition | Conspiring to overthrow or otherwise dismantle NanoTrasen public trust and authority. | + +| V | Intentional Violence | Causing intentional bodily harm to another sapient being. | +| :---- | :---- | :---- | +| Misdemeanor | Assault | Threatening or attempting to cause bodily harm to another sapient being. | +| Misdemeanor | Battery | Causing superficial bodily harm to another sapient being. | +| Felony | Incapacitation | Inflicting bodily harm or administering a chemical agent upon another sapient being, resulting in critical condition or unconsciousness, but not death. | +| Felony | Mutilation | Causing permanent or otherwise long-lasting damage to another sapient being’s body parts, organs, or appendages. | +| Capital Offense | Murder | Intentionally killing another sapient being. | +| Capital Offense | Prevention of Revival | Rendering a dead body unrevivable by common medical practice. | + +| W | Free Will | Depriving another sapient being of their free will and autonomy. | +| :---- | :---- | :---- | +| Felony | Kidnapping | To unlawfully restrain or transport another sapient being against their will. | +| Capital Offense | Suppression of Free Will | Permanently depriving another sapient being of their free will and autonomy. | + +| \- | Other | Independent crimes with no classification. | +| :---- | :---- | :---- | +| Infraction | Cannibalism | To consume a portion of another sapient being, without express consent. | +| Misdemeanor | Animal Cruelty | Inflicting excessive harm on a living being, except when required for medical treatment, scientific research, or the preparation of food. | +| Felony | Bribery | Offering or giving gifts, money, or favors to influence Command to act outside of their allowed duties. | +| Felony | Tax Evasion | Not paying NanoTrasen-mandated scrip taxes, or using non-scrip currencies to avoid paying taxes. | +| Capital Offense | Refusal of Lawful Implantation | Refusing to accept a lawful implant from Security personnel while in custody. | +| Capital Offense | Breach of NT Contract | Violating the terms of an NT-issued, signed contract. | + +--- + +## 8. Contraband Classifications + +### Contraband Confiscation Procedures +Contraband Classifications follow broad categorizations based on object purpose, rather than a strict, specific list. Higher ranking personnel can override or specify contraband with the following chain of authority: +* Central Command Officials +* Captain +* Head of Personnel +* Judicial Officer + +Enforcement personnel are to avoid unreasonable confiscation of items in order to maintain positive public relations between crew, security, and command. + +### Contraband Classifications +A single item may have more than one contraband classification, but only the highest charge is applied per item. + +**Weapon** +Objects with a heightened effectiveness for violence or killing. +Minor: Improvised item used as a weapon. +Moderate: Items that are purpose-made to be a weapon. +Major: Highly lethal weapon. + +**Unsanctioned Equipment** +Equipment that is restricted to a certain department or job. +Minor: Common, departmental equipment. +Moderate: Equipment that is critical to the department’s function. +Major: Command-Exclusive, unique equipment. + +**Operational Hazards** +Objects that pose a heightened threat to the operational safety of the station, that are not explicitly issued by a department to do one’s job. +Minor: Common, mostly harmless equipment. +Moderate: Local scale threat to operational safety. +Major: Large scale threat to operational safety. + +**Chemical** +Substances capable of influencing the mind or harming the body when metabolized or used in a reaction. +Minor: Restricted Recreational Drugs & Medicines with Low-Risk ODs. +Moderate: Exploitable Stimulants, Medicines with High-Risk ODs, & Minorly Dangerous Reactive Substances. +Major: Lethal Poisons, Highly Inhibiting Chemicals, & Highly Dangerous Reactive Substances. + +**Propaganda** +Objects that support non-NT entities, or paints NT and its subsidiaries in a false light. +Minor: Items that carry branding from Non-NT organizations, with low-risk of exposure to other crew. +Moderate: Items that carry branding from enemies of NT, paint NT as an organization in a false light, or lesser items with wide exposure to other crew. +Major: Items that carry branding from terrorist organizations, paint NT Command in a false light, or lesser items with station-wide exposure to other crew. + +**Classified Media** +Media containing information from above the carrier’s clearance level. +Any classified media is Major Contraband. + +--- + +## 9. Legal Exemptions + +### Security Exemptions +Security personnel are explicitly exempt from the following crime categories, so long as the action is following standard protocol and taken to perform enforcement duties: +Access: For the case of legal, necessary searches of a department. +Contraband: For their standard-issue service weapons and security equipment. +Theft: For legal confiscations of contraband. +Violence: For necessary force to carry out arrests. +Free Will: For restraining detainees and holding prisoners in custody. + +### Medical Exemptions +The Paramedic is explicitly exempt from the following crime categories, so long as the action is done following standard protocol and taken to perform life saving operations: +Access: For the case of medical emergency + +### Engineering Exemptions +Engineering personnel are explicitly exempt from the following crime categories, so long as the action is following standard protocol and taken to perform emergency repairs: +Access: For the case of effecting emergency repairs + +### Clown Exception +The clown gets a privilege to be able to commit Infraction or Misdemeanor level crimes for pranks, as long that: +The pranks do not cause bodily harm. +Damages caused are reversed at the end of the bit. +In case the clown gets taken to court, the presiding judge determines if the bit was funny and the clown exception holds. + +### Loss of Free Will +In the event that a sapient being is under the influence of effects that completely suppress or control the being’s free will, any charges should be dropped upon the removal of said influence. + +--- \ No newline at end of file From e1730cc518cd928e38f4341ce1a6b78b506596c9 Mon Sep 17 00:00:00 2001 From: Alicios Date: Tue, 5 May 2026 04:26:17 -0700 Subject: [PATCH 13/53] Article 5 Doc --- .../article-5_design_doc.md | 179 +++++++++++++++--- 1 file changed, 156 insertions(+), 23 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/article-5_design_doc.md b/src/design-proposals/station_protocol_rework/article-5_design_doc.md index 571655af..5ab5d7f3 100644 --- a/src/design-proposals/station_protocol_rework/article-5_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-5_design_doc.md @@ -4,50 +4,183 @@ Your title should convey the basic jist of your proposed changes. It should be s | Designers | Implemented | GitHub Links | |---|---|---| -| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | +| Alicios + SOP Workgroup | :warning: Partially | PR Links or TBD | -`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: +## Overview -- This acknowledges credit where it is due -- People who are confused about the written intent can use this information to contact the authors +This proposal provides a major overhaul of the current legal system, including Sentencing, Trial, and Hearing procedures. It majorly restructures the current legal job's power dynamics and role, creating a clear distinction between the "Enforcement" of Security, and the "Sentencing" of Legal jobs. -`Implemented` is the status of the feature. +The main intent of this overhaul is to make the procedures surrounding committing crimes open to many more roleplay opportunities. Crimes are less cut and dry, and have much more room to argue, create drama, and foster better roleplaying scenarios. -Github links can include multiple PRs, if relevant. +## Background -## Overview +There are many issues with Funky's current legal system. -A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". +The Warden is currently primarily responsible for sentencing, despite also having to keep an eye on the brig, handle armory access, watch monitors, and relay information from Emergency channels. Current SOP tries to emulate real-life legal systems, such as giving prisoners a right to a lawyer, giving them a chance to plead not guilty, and potentially escalating to trial. All of this is fundamentally impossible while the Warden is the only one in charge of sentencing. -## Background +The Magistrate is the ultimate authority on Space Law verdicts, but is never present for any sentencing procedures. The only time the Magistrate is allowed to get invovled is when a case gets escalated to a full-on trial, which is an extreme rarity, and totally optional. Additionally, the Magistrate sits outside the normal Command power structure, and supersedes even the Captain and Head of Security. This does not align with Funky's future vision of the Captain being the ultimate authority on the station, and instead makes existing Non-CCVIP Command members feel impotent. -Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. +Lawyers feel like they have no purpose. Security SOP and current Space Law barely supports Lawyers actually escalating charges to a court case. Brig times are far too short, and any amount of argument or legal battle would take far longer than the unmodified sentence. Lawyers do not even have security comms, so they cannot know if there is a client unless they physically sit in Security and ask every incoming detainee. -Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. +Trials are rare, and when they do happen, they are incredibly long, unfocused, and have no clear points to fight for. There are no clear procedures to determine what is necessary to come to a verdict, and what consequences can even come from it. Often times, the main participants of a Trial are characters with Jobs that are much more important to the operation of the station, like a Command Member or Security Officer, which almost certainly results in the Trial having to get cut short without a satisfying conclusion. + +Punishments for breaking the law are intentionally short and inconsequential, because they were designed for a much shorter round length than what Funky has. There is no room for alternative punishments, and the Warden is encouraged to keep brig times low, because there is little to no interaction while in the brig, and players have a fear of "ruining someone else's round" + +Essentially, any and all interaction with legal battles in the game's current state is unwieldy, and completely voluntary. This proposal aims to push the legal system to the forefront of any criminal charges, in a way that is still efficient for gameplay's sake, but also allows for much more depth and nuance with every interaction. ## Features to be added -Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. +### Job Restructuring: + +Many of these changes are part of the larger design proposals from the SOP Workgroup, but I will highlight the ones that are vital for the Legal System. + +Head of Personnel (Head of Service) -> Executive Officer (Head of Legal) +Magistrate (CCVIP) -> Judicial Officer (Legal Deputy) +Internal Affairs Agent (CCVIP) -> Internal Affairs Agent (Legal) +Lawyer (Civilian) -> Lawyer (Legal) + +There is a new clear division between Security, and Legal staff. This will come with a comms channel specifically for Legal staff, to help the Legal team facilitate court cases, and hearings. + +Ideally, Legal would become its own department. Existing maps can just reuse the current Lawyer, Magistrate, and IAA offices, as well as the Court. However, it is also very possible to just have these roles remain civilian, and just give them the Legal comms channel. + + +### Job Responsibilities & Authority: + +Power shifts as follows: +The Magistrate's ultimate authority on legal matters goes to the Captain, with the Executive Officer second in line. +The Warden's authority and responsibility in sentencing goes to the Judicial Officer, who is not Command/CCVIP, but instead a Deputy of the Executive Officer. +Internal Affairs Agents are now able to audit Space Law misinterpretations, much like how the Magistrate was previously. +(As part of a wider change from the SOP workgroup, audits are less powerful in general, but the authority to audit still falls upon IAAs) +The Executive Officer is now the Command member primarily responsible for the Legal team, and the one that all Legal members directly answer to. + + +### Expanded Sentencing +Since Sentencing is fully the responsibility of a single job, with a level of trust and authority, this brings the opportunity to expand punishments and sentencing as a whole. + +#### Crime Tiers +This is also part of the SOP Workgroup's Corporate Law proposal, but it is worth going over here. + +There are now only 4 tiers of crimes, each with FIXED punishment lengths in each tier. + +Infractions: Warning/Tickets +Misdemeanor: 10 minutes. +Felony: 20 minutes. +Capital Offense: Permanent. + +Permanent Brig time threshold is 40 minutes, instead of 20. + +Base brig time is generally higher, specifically to create opportunities for legal battles, and to create incentives to argue for Extenuating Circumstances, Alternative Punishments, and Parole. + +Long and Permanent sentences will become more common, but this does NOT mean actual time served will be higher. There will be opportunity to fight your way out of a long sentence, or prove your worth and get out early. + +#### Extenuating and Aggravating Circumstances +Circumstances make differences in sentence length a point to argue about, and create roleplaying opportunities, rather than being entirely up to Warden fiat. + +The Prosecution can argue for Aggravating circumstances, which increase the severity of the punishment. +Examples include: Brutality, Evasion of Enforcement, Privileged Victim, Repeat Offenses + +The Defense can argue for Extenuating circumstance, which reduce the severity of the punishment. +Examples include: Cooperation with Enforcement, First Offense, Self-Defense, Self-Report + +#### Alternative Punishments +Alternative Punishments are NT-approved alternatives to brig time, which create a clear target for either side to argue for. This makes sentences potentially much more interesting than "time out" in the brig. + +Examples include: Community Service/Forced Labor, Demotion, Whistleblowing, Financial Compensation, Reversing Damages + +#### Parole +Parole is the opportunity for a criminal to be freed from their brig sentence early, giving prisoners incentives to have good behavior, as well as providing opportunities for interesting roleplay scenarios. + +Examples include: Community Service/Station Labor, Appointments with the Chaplain/Psychologist, Parole with Tracking implants, bodycams, electropacks, etc. + +(This also gives Chaplains and Psychologists perfect opportunities to roleplay with criminals, with mechanical incentives as well) + + +### Court Procedures + +All arrests above a minor infraction must take the detained to court, to formally receive a sentence before the Judicial Officer. +Here, the defendant is given the opportunity to plead "not guilty", which initiates a formal legal procedure to determine their guilt, as well as what punishments they should receive. + +It is to be made VERY clear, that the intent is NOT to make every simple crime and sentence a full-blown trial that takes dozens of minutes. Your typical criminal charge with clear-cut evidence and/or low severity in punishments are supposed to be swift, and take only a few minutes at most. The intent is to allow criminals to negotiate alternative punishments, or smooth-talk their way out of punishments, and create meaningful legal roleplaying scenarios, NOT to add unnecessary bureaucracy and moving parts to every criminal interaction. + +It is also worth noting, that any Court Procedure above a Summary Hearing exclusively involves jobs that are fully committed to Legal scenarios. This means that those roles can put 100% of their attention to a legal procedure, without risk of interruption. They are also able to gather a level of expertise and knowledge of legal procedures, making the system much more efficient and interesting than otherwise. + +There are 3 levels of court procedures, which scale according to the potential punishment and crime severity. + +#### Summary Hearings +Quick, efficient legal procedure. 1-2 minutes. These are held for simple misdemeanor crimes, and anything of low severity. + +There is not supposed to be a ton of back and forth, just the opportunity for the defendant to state their case, or bring to attention details that may have been missed. The Prosecution is simply the officer who performed the arrest, to make it as quick and efficient as possible. The Judicial Officer opens with a proposed sentence, and gives the defense the opportunity to accept their charges with no pushback. + +Summary Hearings are largely reminiscent of the way the Warden used to determine brig times. + +#### Formal Hearings +Lengthier, proper hearing for crimes with a big enough punishment to warrant it. Could take up to 15 minutes, but they are only held for crimes that could potentially result in a punishment more severe than the time it takes to hold the hearing. Felonies and Capital Offenses receive Formal Hearings. + +Formal Hearings are the when legal representation comes into the picture. Security consults with an IAA, who will act as prosecution. The Defendant consults with a Lawyer, who acts as the defense. + +Each side presents their case, and potentially questions up to one witness, if necessary. After the Judicial Officer makes their verdict, the both sides are given the opportunities to argue for Extenuating and Aggravating circumstances, or make deals for alternative punishments. + +Formal Hearings are supposed to still be quick, but they just give both sides a bit more opportunity to explore all options, and utilize or exploit the legal system to their advantage. + +#### Trials +Extremely in-depth, highly formal procedure only for the most severe of crimes. Trials can take as long as necessary, and stop only when the Judicial Officer can confidently come to a verdict. Trials can only be held for Capital Offense charges, and only if the Judicial Officer approves it is worthy of a Trial. + +Trials consist of a formalized procedure, multiple witness and evidence examinations, and plenty of opportunity for roleplay and drama. + +Trials are capable of, and intended to, consume a Legal role's entire round. This is why they are entirely opt-in, and case-by-case. A Trial will NEVER be standard procedure for any crime, and only happen if all players involved wish to engage in formalized legal scenarios. + ## Game Design Rationale -Consider addressing: -- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? +### Seriously Silly: +All levels of authority and importance with Legal jobs creates many opportunities for interesting and fun characters. +JOs and IAAs will be uptight, formal, and NT-loyalists. Lawyers may be "aligned with the people", and sympathetic. + +A proper framework for legal procedures opens the door for frivolous, humorous cases and lawsuits. + +### There is no Winning or Losing: +Currently, getting brigged is just about the most glaring instance of "clearly losing" in the game. There's barely any opportunity to fight it, there's nothing to do inside the brig, and the rules are structured in a way to just put you in "time out", and move on. + +This Legal overhaul creates opportunities for gray areas and ways to fight back against getting arrested at every opportunity. Even a permanent brig sentence is just an opportunity to consult a Lawyer and ask for parole. Getting arrested shouldn't feel like you "lost", it should just be the next chapter in your story. + +### Maintaining Authenticity: +Real-life Legal procedures are incredibly pedantic, formal, and take ages. I am not trying to emulate legal procedures for realism's sake. I am taking inspiration from real courts of law, and seeing which parts meaningfully create opportunity for conflict and roleplay, and condensing it into a manageable amount of rules for use in game. + +Many people are familiar with legal stories and dramas, with court cases in TV shows, and video games. The goal is to take that larger-than-life, dramaticized version of court, and inject that into the game. + +### Take Things Slow: +The old brig system is built for rapid-fire, in-and-out sentences. Brig times are incredibly short, and there is no room for argument or formal procedures. This is because the servers these rules originated from are also short. + +This system takes advantage of the extra time we have in Funky rounds to meaningfully expand upon what happens after you get arrested. Short, inconsequential crimes remain fast and efficient, but more severe, round-defining crimes are given the proper amount of attention and time to play out a scenario. + +### Maximizing Roleplay Potential (Avoid QOL Slop): +Adding in a human element to sentencing and legal procedures greatly encourages roleplay. Every player is given the opportunity to argue their case in their own way, and Legal jobs are given the opportunity to completely explore their role. + +### Dynamic Enviroment: +Every major crime becomes it's own story and fight in court. More moving parts creates more opportunities for breakouts, elaborate plans, and individual judgement. No two murder cases will ever feel the same. + ## Roundflow & Player interaction -Consider addressing: -- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? -- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? +This is a major change to sentencing and criminal interactions. It will affect every single arrest, impact almost any antagonist role that commits a crime. +This is why I have intentionally designed Summary Hearings to be quick and efficient, and emulate the old Warden quick sentencing. Not every crime needs a full on procedure; we should be putting time and effort into places where it matters, like major crimes. + +There will be a large variation in how Legal players interpret their role. Some JOs will be extremely strict and overly harsh, and create tons of conflict. Some will be incredibly lenient and get in trouble with the XO. This is intentional, and welcomed. + +I mentioned it in the relevant section, but Trials are entirely opt-in. No one will be forced into an hour-long legal battle unless they want to. All players who are charged with a crime will have to interact with the legal system in some capacity, but it should never completely consume their round unless they want it to. ## Administrative & Server Rule Impact (if applicable) -- Does this feature introduce any new rule enforcement challenges or additional workload for admins? -- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? -- How are the rules enforced mechanically by way the feature will be implemented? +Admins may have to monitor problematic players being too harsh or abusive with their power over punishment. However, this is no different than the way Security and Command are held to a higher standard for the exact same reasons. + +Players will still have all the normal avenues for expresing themselves through in-character conflict, whether that is reporting to their Head of Staff, the Captain, or getting a Lawyer to represent them. + +That being said, much like the Magistrate already is, the JO will likely have to have a sizeable playtime requirement, and a decent amount of monitoring for abusive behavior. # Technical Considerations -- Are there any anticipated performance impacts? -- Does the feature require new systems, UI elements, or refactors of existing ones? -- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file +Legal Comms key for relevant parties. +Existing Legal offices will need access changes. +Job icons will need changes to accomodate the departmental shifts and hierarchy adjustments. + +The rest is purely guidebook entries. From 6ddabb8d534ab87adc98eefe31af0f1ae2e789a5 Mon Sep 17 00:00:00 2001 From: Alicios Date: Tue, 5 May 2026 04:29:50 -0700 Subject: [PATCH 14/53] Article 5 Entry (WIP) --- ...le 5 - Sentencing, Trials, and Hearings.md | 354 ++++++++++++++++++ .../article-5_design_doc.md | 6 +- 2 files changed, 356 insertions(+), 4 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md b/src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md index e69de29b..fc230b4b 100644 --- a/src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md +++ b/src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md @@ -0,0 +1,354 @@ +# Sentencing, Trials, and Hearings + +## Table of Contents: + +1\. Legal Definitions +2\. Sentencing +3\. Court Proceedings +4\. Classified Court Proceedings +5\. Captain’s Mast +--- + +## **1\. Definitions** + +Judge: The current legal arbiter of a trial or hearing. +Prosecution: The party pressing charges. +Defendant: The party being accused. +Defense: The party representing the defendant: May be the defendant themselves. +Charge: An accusation of a crime. +Sentence: An official judgment of a crime committed and accompanying punishment to serve. +Plea: An official statement in court from the Defendant about whether they are guilty or innocent. +Verdict: An official determination of guilt, by the presiding Judge. + +--- + +## **2\. Sentencing** + +Sentencing is the act of determining a suitable punishment for convicted criminals. +The presiding Judge determines the sentence after they have made an official verdict. + +### **Processing Priority** + +At any given time, at least one legal authority must be in charge of sentencing aboard the station. +Typically, this is the Judicial Officer, but in their absence, the responsibility falls upon the following order of succession: + +1\. Judicial Officer +2\. Executive Officer +3\. Captain + +The Judge is responsible for: + +* Determining which level of hearing is suitable for the charges. +* Delivering a verdict: Whether or not the defendant is guilty. +* Determining a sentence: The amount of brig time and/or alternative punishments to assign. + +The Captain still holds the most legal authority aboard the station, and has the final say in any legal matters. + +### **Standard Punishment Lengths** + +The following times are to be used as a baseline, based on the severity of crime committed: + +* Infraction: No brig time. +* Misdemeanor: 10 minutes. +* Felony: 20 minutes. +* Capital Offense: Permanent. + +### **Executions** + +At the Judge’s discretion, a permanent sentence may be raised to an execution. +Any executions need express permission from the presiding Captain, and cannot be authorized in the absence of one. + +Executions are recommended only when multiple Capital Offense charges have stacked, or if a single Capital Offense has been aggravated multiple times. + +### **Crime Categories and Stacking Crimes** + +Charges from the same Crime Category cannot be stacked for the same sentence. Only the highest offense in that category will be counted. + +Multiple crimes from different categories can stack freely, up to a maximum time of 40 minutes. +If the brig time exceeds 40 minutes, the Judge is recommended, but not required, to elevate the punishment to Permanent Confinement. + +The Judge may choose to elevate a permanent sentence to Execution, if multiple Capital Offenses were committed at the same time. + +### **Aggravating Circumstances** + +Aggravating circumstances increase the severity of a punishment. +At their discretion, the Judge may decide to simply increase the punishment, or to elevate the crime tier by one level. + +**Attempted/Planned Crime**: +Attempted or planned crimes are to be charged as the full crime committed, so long as there is clear evidence. A crime should not be charged as attempted if there is a more fitting lesser crime. + +**Alert Level**: +Committing a crime that directly goes against restrictions placed during a heightened alert level, or directly goes against a public announcement made by Command. + +**Brutality**: +The crime was committed recklessly, with no regard for collateral damage, and/or with a complete lack of remorse. + +**Evasion of Enforcement**: +The defendant greatly resisted arrest, or otherwise evaded and obstructed security from charging them. + +**Parole Violation**: +The crime was committed while the defendant was on parole, or serving an alternative sentence. + +**Privileged Victim**: +The crime was committed, and concerns a member of high ranking or authority under NanoTrasen. + +**Repeat Offense**: +The Defendant has already been sentenced for the same crime this shift. + +### **Extenuating Circumstances** + +Extenuating circumstances decrease the severity of a punishment. +At their discretion, the Judge may decide to simply decrease the punishment, or demote the crime tier by one level. +The Judge may also decide to waive punishment entirely, but the Judge is recommended to use this power sparingly. + +**Cooperation**: +The defendant cooperated with Security personnel and did not resist. + +**First Offense**: +The defendant has no criminal record this shift, and only committed the single charged crime. + +**Enforcement Incompetence**: +Security used excessive force to perform the arrest, took excessive time to process the defendant, or otherwise greatly inconvenienced the justice process. + +**Self-Defense**: +The crime was committed in self-defense. + +**Self-Reported**: +The defendant turned themselves into Security, and/or willingly returned any stolen property. + +**Necessity** +The defendant has shown that the crime they committed was necessary to prevent some greater harm. + +**Victim Involvement**: +The victim personally requested that the charges should be dropped or reduced. + +### **Alternative Punishments** + +Alternative punishments may be offered as a replacement or reduction to brig time. +The Defense can argue for alternative punishments, but the sentence is ultimately up to the Judge. +Possible alternative punishments are listed below: + +**Community Service/Station Labor**: +The detainee agrees to serve some time performing hard labor for the station while under watch by Security, or while in confinement. + +**Demotion**: +The defendant loses their current job and is hired to the position below them. + +**Disclosure**: +The defendant agrees to reveal incriminating information about their accomplices, or any other critical information relevant to station security. + +**Financial Compensation**: +The defendant agrees to pay scrip to the victims, to cover the cost of the crimes committed. + +**Reverse Damages**: +The defendant promises to reverse damages, or reveal the location of stashed stolen goods. + +### **Parole** + +The Judge may offer parole if they deem the defendant capable of genuine reform. +Parole can be discussed with a representative lawyer, after the prisoner has served at least half of their sentence, or 20 minutes in the case of permanent sentences. +The Judge is highly recommended to consider parole offers that result in increased productivity and profits to NanoTrasen. +The Judge, with the Warden’s express approval, is highly encouraged to have a Security Officer assigned as the defendant’s parole officer. +Parole may have additional conditions, as listed below: + +**Community Service/Station Labor**: +The detainee agrees to serve some time performing hard labor for the station while under watch by Security, or while in confinement. + +**Character Reform**: +The detainee agrees to an appointment with a station Psychologist or Chaplain, who evaluates their level of remorse and likelihood to reform. + +**Free Parole**: +Detainees expressed good behavior while in custody, and may be tentatively freed from their sentence, so long as they check up with security regularly. Security may choose to require them to use a Bodycam, Electropack, and/or Tracking Implanter. + +--- + +## **3\. Court Proceedings** + +There are multiple types of court proceedings, held based on the severity of the charges. +It is up to the Judge to select which proceeding should be held, and to determine which cases are sufficient to go to Trial. + +### **Summary Hearings** + +A quick, informal judgment for minor offenses. +Held for Misdemeanors. +Also held when protesting an Infraction. +Target time is 1-2 minutes. + +### Prosecution: + +* Arresting Officer +* No one, in the case of a protested Infraction. + +### Defense: + +* Defendant self-representation. +* The defendant may request a lawyer, but their sentence will be paused until the lawyer arrives, and during any consultation. + +### Witnesses: + +* Witnesses are not allowed. NT will not waste valuable productive time on a Summary Hearing. + +### Procedure: + +1\. Prosecution reads their charges. +2\. The Judge proposes a sentence for these charges, and asks if the defense pleads guilty. +3\. If the defense pleads not guilty, they state their case and present any relevant evidence. +4\. The Judge reviews the defendant’s case, and adjusts their sentence if necessary. +5\. The Judge closes the case with their verdict, and the officer either lets them go free or escorts them to the brig to serve, as necessary. + +### **Formal Hearings** + +Lengthier, formal hearings for more severe crimes. +Held for Felonies. +Also held for Capital Offenses that do not wish to escalate into a Trial. +Target time is around 15 minutes. + +### Prosecution: + +* Arresting Officers must have an Internal Affairs Agent represent them as prosecution, so that they may return to their duties should it be needed. + +### Defense: + +* A lawyer must be offered to represent the defendant. +* The defendant can still choose to self-represent, but it is not recommended. + +### Witnesses: + +* Witnesses are only allowed if it is absolutely essential to the determination, and to a maximum of one per side. +* Witnesses may not be allowed to be Command, Security, or other essential jobs that cannot afford to be away from their post. + +### Procedure: + +Pre-Hearing Consultation: + +* Both sides may briefly consult with their representation, before the Trial officially begins. +* Consultations are confidential. Statements said in consultation never have to be disclosed. +* There is no strict time limit on consultation, but time spent consulting does not reduce any eventual sentence. +* Both sides are recommended to plan for and consider: + * Whether they will plead guilty or not guilty. + * What witnesses, if any, they intend to call. + * Whether any aggravating or extenuating circumstances apply. + * Whether a plea deal for an alternative punishment is worth pursuing. + +1\. Opening + +* The Judge identifies all participating parties, and reads the formal charges aloud. + +2\. Plea + +* The Judge formally asks: “How does the Defendant Plea?” +* If the Defense pleads guilty, skip to step 5 (Sentencing) +* If the Defense pleads not guilty, proceed. + +3\. Presenting Cases + +* The Prosecution presents their case in its entirety, followed by the Defense in its entirety. +* Any physical evidence must be formally presented before the Judge, and entered into the record before it can be referenced in argument. +* Each side may bring their witnesses to the stand and question them directly. + * After each witness, the opposing side may briefly cross-examine. +* The Defendant may choose to testify. If they do, they are subject to cross-examination. + +4\. Verdict + +* The Judge delivers a verdict on each charge. +* If the Defense is found Not Guilty on all charges, the hearing closes immediately. + +5\. Sentencing + +* Both sides may now argue for aggravating or extenuating circumstances that should influence the sentence. +* Either side may also propose a plea deal, for an alternative punishment in lieu of standard brig sentencing. +* The Judge considers these arguments and issues their final sentence. + +6\. Closing + +* The arresting officer either releases the defendant or escorts them to serve their sentence, as appropriate. + +### **Trials** + +Extremely in-depth, formal procedure, only for the most severe crimes. +Held only when the defense chooses to escalate a Capital Offense charge to a Trial. +May only be held with a NanoTrasen-approved Judicial Officer, not an acting Judge. +No target time. May be as long or as short as necessary for the Judicial Officer to come to a verdict. + +### Prosecution: + +* Arresting Officers must have an Internal Affairs Agent represent them as prosecution, so that they may return to their duties. + +### Defense: + +* A Lawyer must be offered to act as the accused’s defense. +* The accused can still choose to self-represent, but it is not recommended. + +### Witnesses: + +* Witnesses are allowed and encouraged. +* Witnesses can be anyone, including Security and Command. + +### Procedure: + +Pre-Trial Consultation: + +* Both sides may briefly consult with their representation, before the Trial officially begins. +* Consultations are confidential. Statements said in consultation never have to be disclosed. +* There is no strict time limit on consultation, but time spent consulting does not reduce any eventual sentence. +* Both sides are recommended to plan for and consider: + * Whether they will plead guilty or not guilty. + * What witnesses, if any, they intend to call. + * Whether any aggravating or extenuating circumstances apply. + * Whether a plea deal for an alternative punishment is worth pursuing. + +1\. Opening + +* The Judicial Officer identifies all participating parties, and reads the formal charges aloud. + +2\. Plea + +* The Judicial Officer formally asks: “How does the Defendant Plea?” +* If the Defense pleads guilty, skip to step 9 (Allocution) +* If the Defense pleads not guilty, proceed. + +3\. Opening Statements + +* The Prosecution gives a brief summary of what they intend to prove, and how. +* The Defense gives a brief summary of their argument or facts they intend to dispute. + +4\. Presenting Cases + +* The Prosecution presents their case in its entirety, followed by the Defense in its entirety. +* Any physical evidence must be formally presented before the Judicial Officer, and entered into the record before it can be referenced in argument. +* Each side may bring their witnesses to the stand and question them directly. + * After each witness, the opposing side may cross-examine. +* The Defendant may choose to testify. If they do, they are subject to cross-examination. + +7\. Closing Arguments + +* The Prosecution presents their closing argument, then the Defense. + +8\. Verdict + +* The Judicial Officer determines Guilty or Not Guilty for each charge. +* If the Defendant is found Not Guilty on all charges, the Trial closes immediately. + +9\. Allocution + +* The Defendant is given the floor to address the court directly and personally. +* They are not to be interrupted, cross-examined, or objected to in any way. +* This is the Defendant’s opportunity to explain themselves, apologize, or appeal to the court’s mercy. + +10\. Sentencing + +* Both sides may now argue for aggravating or extenuating circumstances that should influence the sentence. +* Either side may also propose a plea deal, for an alternative punishment in lieu of standard brig sentencing. +* The Judicial Officer considers these arguments and issues their final sentence. + +11\. Closing + +* The arresting officer either releases the defendant or escorts them to serve their sentence, as appropriate. + +--- + +## **4\. Classified Court Cases** + +--- + +## **5\. Captain’s Mast** diff --git a/src/design-proposals/station_protocol_rework/article-5_design_doc.md b/src/design-proposals/station_protocol_rework/article-5_design_doc.md index 5ab5d7f3..96bbc7cf 100644 --- a/src/design-proposals/station_protocol_rework/article-5_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-5_design_doc.md @@ -1,10 +1,8 @@ -# Short, Properly Capitalized Title - -Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. +# Station Protocol Rework: Sentencing, Trials, and Hearings | Designers | Implemented | GitHub Links | |---|---|---| -| Alicios + SOP Workgroup | :warning: Partially | PR Links or TBD | +| Alicios + SOP Workgroup | :warning: Partially | TBD | ## Overview From 00929134d3f0fdc116ee192f3789f5f1251130bf Mon Sep 17 00:00:00 2001 From: Alicios Date: Tue, 5 May 2026 04:31:38 -0700 Subject: [PATCH 15/53] Added link to guidebook in Article 5 Design Doc --- .../station_protocol_rework/article-5_design_doc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework/article-5_design_doc.md b/src/design-proposals/station_protocol_rework/article-5_design_doc.md index 96bbc7cf..623d5a5e 100644 --- a/src/design-proposals/station_protocol_rework/article-5_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-5_design_doc.md @@ -2,7 +2,7 @@ | Designers | Implemented | GitHub Links | |---|---|---| -| Alicios + SOP Workgroup | :warning: Partially | TBD | +| Alicios + SOP Workgroup | :warning: Partially | https://github.com/Joaco545/Funky-Station-Docs/blob/6ddabb8d534ab87adc98eefe31af0f1ae2e789a5/src/design-proposals/station_protocol_rework/Article%205%20-%20Sentencing%2C%20Trials%2C%20and%20Hearings.md | ## Overview From 638dcf115a8ce6b21c5c22b3cfb67ab791739a78 Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Tue, 5 May 2026 12:06:11 -0600 Subject: [PATCH 16/53] Update Article 1 - Station Regulations.md --- .../Article 1 - Station Regulations.md | 46 ++++++++++++++++++- 1 file changed, 44 insertions(+), 2 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index 9c1e0139..e45a6671 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -32,10 +32,15 @@ This section will be written under the explicit perview of, or by the hand of, t # Permits and Paperwork Permits and Paperwork cover what paperwork to use, when to use it, and what utensils to use with it. EG: + To hire person X use Hiring Form 4.23, along with adendum 2 for hiring non-NT members + Access is only granted after filling out Access Form 6.23 C + Construction or modification of maints should be done with Construction Form 32.45 + All paperwork must be filled with a black-ink pen unless specified in... + Copies of official paperwork should be stamped by the relevant head ## Game Design Rationale @@ -69,10 +74,15 @@ This should have minimal impact on roundflow outside of obtaining permits and te # Fines Fines are for when things are not fine. When you commit an SOP infraction or Corprate Law based infraction you may be ordered to pay a fine. This section explains the who, how, and why of fines. It does not explain how this is diffrent from a governmentaly approved bribe. + Who can give them + Why they can be given + How to give them + How to pay them + It also covers the courses of action that the IAA can take. Primarily issuing a fine or asking the head of staff to take greater actions. ## Game Design Rationale @@ -98,11 +108,17 @@ This would alow the security officer to print the fine recipt quickly, and the r # Extracorporate Entities This section covers interactions with visitors to the station. Visitors are an under-used RP mechanic, and while this will by no means fix that, it will provide a direction to take the interactions with them. The sections contained within include: + Shuttle rights + Docking + Trading + Treatment of visitors + Refugees + External hiring (temporary and complete contracts) ## Game Design Rationale @@ -123,17 +139,43 @@ While not required, IDs and PDAs can be removed from non-NT/infiltration aligned NOTE: Insurance is something that will not be directly added by this workgroup as it is outside of our intended scope, it is merely here as an example that could be added in the future. This would create a codified explanation of what each insurance level entails: + What premiums you may have to pay each shift + Coverage of injuries + Coverage of non-health related surgeries + Cybernetics # Alert Levels Not exactly new, alert levels have been moved from SOP to regulations as they are called for situations that are not standard. -Most alert levels are the same, however in a more specific PR we will likely be looking at changes to what leads to calling a blue alert. -Additionaly RED alert now alows the captain to deem specific SOP as suspended, this replaces the SOP per alert level SOP. + +General: Most alerts are un-changed in their cause/response with the following exeptions: + +Blue alert is called for a duration of up to 10 minuets while a Felony class or higher crime is under investigation (See Law Document). + +Starting at blue alerts the HoS will be slated for overwatch from security (See the Command document for more information on the HoS rework) + +Events may be canceled without warning should the situation require it. + +Violet alert grants the CMO and Captain the ability to quarantine areas of the station which may only be lifted by the CMO or Captain’s orders. +Security is given permission to enforce this quarantine through any method the captain allows. +This also requires sensors set to show health at a minimum to better track the spread of the infection + +Events may be canceled without warning should the situation require it. + +Red Alert: +RED alert now alows the captain to deem specific SOP as suspended, this replaces the SOP per alert level SOP. This is also being done to reduce confusion about alert levels being SOP, and possibly making it enforceable by security instead of the CCVIPs which was always an odd position for them. +Security’s restrictions on heavy weapons are also lifted and it is expected that the Head of Security and/or Warden keep track of what weapons are taken by who to account for their return when the situation is resolved. + +Departmental breaks and crew events such as in the theatre and chapel are paused for the duration of the alert. Gatherings may be broken up as needed. + +HoS will still be religated to their department outside of immediate station ending threats that will require a full response force (EG god summoning) (again see the Command document for more information on the HoS rework) + + # Order of Succession and Martial Law The Order of Succession determins who will be next in line for the captain position. From d69dfc17f29468b2eb75b57a902b2ebe3d87fec4 Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Tue, 5 May 2026 12:09:13 -0600 Subject: [PATCH 17/53] Rename article-3_design_doc.md to Command_And_Security.md Reserving the doc as I edit --- .../{article-3_design_doc.md => Command_And_Security.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename src/design-proposals/station_protocol_rework/{article-3_design_doc.md => Command_And_Security.md} (98%) diff --git a/src/design-proposals/station_protocol_rework/article-3_design_doc.md b/src/design-proposals/station_protocol_rework/Command_And_Security.md similarity index 98% rename from src/design-proposals/station_protocol_rework/article-3_design_doc.md rename to src/design-proposals/station_protocol_rework/Command_And_Security.md index 571655af..8c55995c 100644 --- a/src/design-proposals/station_protocol_rework/article-3_design_doc.md +++ b/src/design-proposals/station_protocol_rework/Command_And_Security.md @@ -50,4 +50,4 @@ Consider addressing: - Are there any anticipated performance impacts? - Does the feature require new systems, UI elements, or refactors of existing ones? -- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file +- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) From a6fd7e6a2083e974bcfb0eca47b18ba8a82a849a Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Tue, 5 May 2026 14:26:00 -0600 Subject: [PATCH 18/53] Rename Command_And_Security.md to article-3_design_doc.md Undoing my fuckup --- .../{Command_And_Security.md => article-3_design_doc.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename src/design-proposals/station_protocol_rework/{Command_And_Security.md => article-3_design_doc.md} (100%) diff --git a/src/design-proposals/station_protocol_rework/Command_And_Security.md b/src/design-proposals/station_protocol_rework/article-3_design_doc.md similarity index 100% rename from src/design-proposals/station_protocol_rework/Command_And_Security.md rename to src/design-proposals/station_protocol_rework/article-3_design_doc.md From b23172b53bc1b8c608f330a99b17c0368bbfb1bd Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Tue, 5 May 2026 14:26:28 -0600 Subject: [PATCH 19/53] Update article-1_design_doc.md Moving --- .../article-1_design_doc.md | 210 +++++++++++++++--- 1 file changed, 184 insertions(+), 26 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/article-1_design_doc.md b/src/design-proposals/station_protocol_rework/article-1_design_doc.md index 571655af..3e3cf3c9 100644 --- a/src/design-proposals/station_protocol_rework/article-1_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-1_design_doc.md @@ -1,53 +1,211 @@ -# Short, Properly Capitalized Title +# Station Regulations Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. | Designers | Implemented | GitHub Links | |---|---|---| -| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | +| SOP workgroup, Written by Scrambleking | :x: No | TBD | -`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: +## Overview -- This acknowledges credit where it is due -- People who are confused about the written intent can use this information to contact the authors +This document establishes a comprehensive framework for in-character station regulations intended to enhance roleplay depth, structure player interactions, and provide clear guidance in non-standard scenarios. +Rather than functioning as enforceable server rules, these systems are designed to simulate the bureaucratic, procedural, and corporate realities of a Nanotrasen-operated facility. -`Implemented` is the status of the feature. +The regulations outlined here expand on existing mechanics by formalizing processes such as corporate security protocols, administrative paperwork, fines, visitor interactions, and command hierarchy. +Each section is supported by game design rationale, roundflow considerations, and (where applicable) technical implementation notes to ensure both usability and immersion. -Github links can include multiple PRs, if relevant. +While not all features are required for immediate implementation, this document serves as both a design foundation and a roadmap for future development, prioritizing systems that improve clarity, consistency, and player engagement without overburdening gameplay. -## Overview +## Background -A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". +Not everything that *was* SOP or law perfectly fits within the older sections of them, as such we are creating the "station regulations" to be a catch all for NT's rules that dont quite fit into our other primary catagories. -## Background -Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. +# Corporte Espionage Act +This section is intended to be in direct relation to the metashield on an OOC level along with IC justifications for the Crew/Security metashields and NDAs. +In character the majority of crew would understand this as related to NT's R&D into bluespace, genetics, artifacts, and anomolies, building off of the syndicate being a known orginisation that conducts espionage. + +## Administrative & Server Rule Impact +This section will be written under the explicit perview of, or by the hand of, the head admins. + + +# Permits and Paperwork +Permits and Paperwork cover what paperwork to use, when to use it, and what utensils to use with it. +EG: + +To hire person X use Hiring Form 4.23, along with adendum 2 for hiring non-NT members + +Access is only granted after filling out Access Form 6.23 C + +Construction or modification of maints should be done with Construction Form 32.45 + +All paperwork must be filled with a black-ink pen unless specified in... + +Copies of official paperwork should be stamped by the relevant head + +## Game Design Rationale +By codifying the forms and permits it should make the system easier to navigate for newer players, and prevent abusive forms from making their way into printer files (I am personaly guilty of some of these). +Additionaly the Codification of paperwork is more authentic to a corprate experiance where files are flying about the home office every day. + +## Roundflow & Player interaction +In a round a player (just like anyone in a corporation) will know generaly what they will be required to fill out should they be asked for paperwork, and may even print and fill it out themselves, or with the help of the local librarian. + +## Technical Considerations +This section will require the implimentation of the Printing Machine. +The printing machine provides players with a way to quickly print forms in-round without needing a folder of documents they must search through. +2 versions of the printing machine should be avalible, a "secure" version for command/security use, and a "regular" version for crew use. +The "regular" version will contain documents that normal crew may need such as hiring applications, access requests, and construction permits. It will be kept in the library or simular areas. +The "secure" version will additionaly contain documents such as command/security hiring forms, NDAs, police reports ect. It will be kept behind access locked doors. -Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. +This section will not require, but would greatly benefit from, the implimentation of fillable form fields. +This will make filling forms easier to understand for players without having to interprit rundown text. -## Features to be added +# Building/Construction code -Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. +This section would define what is a "baseline" room via atmosphere, construction, types of walls/windows to use when, firelocks and air alarms, ect. ## Game Design Rationale +In game this would serve as an effective tutorial to building and room construction for newer engineers/players, and can be referenced in the permits system for construction. +This creates a more authentic experiance to newer players and intergrates the guidebook further into the world as a "real" learning tool. -Consider addressing: -- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? +## Roundflow & Player interaction +This should have minimal impact on roundflow outside of obtaining permits and teaching/learning construction. + +# Fines +Fines are for when things are not fine. When you commit an SOP infraction or Corprate Law based infraction you may be ordered to pay a fine. +This section explains the who, how, and why of fines. It does not explain how this is diffrent from a governmentaly approved bribe. + +Who can give them + +Why they can be given + +How to give them + +How to pay them + +It also covers the courses of action that the IAA can take. Primarily issuing a fine or asking the head of staff to take greater actions. + +## Game Design Rationale +This maintains authenticity because it provides a way for security to punish negative behavior without needing to haul the person all the way to security which would lower nantotrasen's profits. +This maximises RP potential because instead of a simple warning there is direct action taken against the person who can then chose to escalate, not pay, or dispute the fine. ## Roundflow & Player interaction +This will provide a way for players to interact and begin escalation with security outside of reciving a warning, which is unsatisfying, and jail time, which could be over the top. -Consider addressing: -- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? -- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? +It also provides the IAA with a more explicit path for punishments outside of taking possibly vital equiptment, or simply firing the person. ## Administrative & Server Rule Impact (if applicable) +This section should have no administrative impact aside from role abuse, which generaly should be able to be dealt with in character with unions and escaltation. + +## Technical Considerations +Scrip is required. +We cant take away the money of someone without money. + +A fine computer/printer is not required, but could greatly benefit the system. +This would alow the security officer to print the fine recipt quickly, and the recipiant to pay it at the designated point. + + +# Extracorporate Entities +This section covers interactions with visitors to the station. Visitors are an under-used RP mechanic, and while this will by no means fix that, it will provide a direction to take the interactions with them. +The sections contained within include: + +Shuttle rights + +Docking + +Trading + +Treatment of visitors -- Does this feature introduce any new rule enforcement challenges or additional workload for admins? -- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? -- How are the rules enforced mechanically by way the feature will be implemented? +Refugees + +External hiring (temporary and complete contracts) + +## Game Design Rationale +Authenticaly, any large port will also have regulations for how to interact and treat visitors from other orginisations. This would be especialy true for a corprate research colony that knows of spies. + +## Roundflow & Player interaction +This is not intended to effect the flow of most rounds, but should alow for rounds that do interact with visitors to have more guidance than "oh ok, I geuss your visiting now" +Idealy this will make even mundane visitors have a level of impact with the personel on the station through things such as medical checkups and acnowladgement of visitation. + +## Technical Considerations +Maps will require a designated "visitor" dock. + +Visitor shuttles will need some way to broadcast their pressence. + +While not required, IDs and PDAs can be removed from non-NT/infiltration aligned visitors. This will also provide a noticable distinction between roles that are part of NT (such as a CMO in an escape pod), and visitation roles that are simply visiting. + +# Insurance +NOTE: Insurance is something that will not be directly added by this workgroup as it is outside of our intended scope, it is merely here as an example that could be added in the future. + +This would create a codified explanation of what each insurance level entails: + +What premiums you may have to pay each shift + +Coverage of injuries + +Coverage of non-health related surgeries + +Cybernetics + +# Alert Levels +Not exactly new, alert levels have been moved from SOP to regulations as they are called for situations that are not standard. + +General: Most alerts are un-changed in their cause/response with the following exeptions: + +Blue alert is called for a duration of up to 10 minuets while a Felony class or higher crime is under investigation (See Law Document). + +Starting at blue alerts the HoS will be slated for overwatch from security (See the Command document for more information on the HoS rework) + +Events may be canceled without warning should the situation require it. + +Violet alert grants the CMO and Captain the ability to quarantine areas of the station which may only be lifted by the CMO or Captain’s orders. +Security is given permission to enforce this quarantine through any method the captain allows. +This also requires sensors set to show health at a minimum to better track the spread of the infection + +Events may be canceled without warning should the situation require it. + +Red Alert: +RED alert now alows the captain to deem specific SOP as suspended, this replaces the SOP per alert level SOP. +This is also being done to reduce confusion about alert levels being SOP, and possibly making it enforceable by security instead of the CCVIPs which was always an odd position for them. + +Security’s restrictions on heavy weapons are also lifted and it is expected that the Head of Security and/or Warden keep track of what weapons are taken by who to account for their return when the situation is resolved. + +Departmental breaks and crew events such as in the theatre and chapel are paused for the duration of the alert. Gatherings may be broken up as needed. + +HoS will still be religated to their department outside of immediate station ending threats that will require a full response force (EG god summoning) (again see the Command document for more information on the HoS rework) + + + +# Order of Succession and Martial Law +The Order of Succession determins who will be next in line for the captain position. +EG: +1. Captain +2. HoP +3. RD +4. QM +5. CMO +6. CE +7. HD (Hospitality director, expended on in job changes) +8. Acting command with the above order +9. HoS + +This can be triggered via a vote of no confidance amongst command. This is started by the CCVIPs, or by the CMO deeming the captain as unfit for duty. + +The Head of Security will take over the station until a suitable captain replacement can be found, at which point power will be relinquished to them. +Martial law can be declared by the HoS once no other suitable replacements for the captain can be made. + +Under martial law security’s orders are final, personnel are to immediately return to their departments or bar unless given explicit permission otherwise, and failure to do so leaves punishment at the discretion of the witnessing officer. +This includes engineering and medical personnel who are responding to emergencies, and scientists responding to anomalies. + +## Game Design Rationale +This goes mostly to authenticity, in an emergancy the HoS is intended to have an overview of the security situation, while the captain has an overview of the station as a whole. +Given this is the case, the HoS should not be focused on the extrenous duties of the captain. +Additionaly the station is a Corporate orginisation who's focus is on profit, not simply "catching the bad guy" and this change is meant to highlight this. +Should all command and potential command die, the only authority on the station is the HoS and security, who should not be treating the station as lightly as a regular command member. +The reason the martial law power was specificaly granted is, should the situation become dire enough to require the HoS to become captain, they will likely be in a situation more severe than red alert. -# Technical Considerations +Martial law is not automaticaly called upon the HoS's promotion due to outlier shifts such as lowpop, or no other command in a lobby willing to play capatain. -- Are there any anticipated performance impacts? -- Does the feature require new systems, UI elements, or refactors of existing ones? -- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file +## Technical Considerations +Possibly an alert level for "Martial Law" can be made, or taken from an existing alert level. From 75621daf3b127deb74408a0114177869ed5a1a72 Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Tue, 5 May 2026 14:30:40 -0600 Subject: [PATCH 20/53] Update Article 1 - Station Regulations.md Initial update from Google Docs --- .../Article 1 - Station Regulations.md | 336 +++++++----------- 1 file changed, 136 insertions(+), 200 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index e45a6671..2724ac2a 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -1,211 +1,147 @@ -# Station Regulations +# NanoTrasen Station Regulations +## Alert Levels +Green +There is no major threat to operational safety. +SOP and Corporate Law remain in full effect. +Blue +**Called for the reason of un unsolved Felony -Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. - -| Designers | Implemented | GitHub Links | -|---|---|---| -| SOP workgroup, Written by Scrambleking | :x: No | TBD | - -## Overview - -This document establishes a comprehensive framework for in-character station regulations intended to enhance roleplay depth, structure player interactions, and provide clear guidance in non-standard scenarios. -Rather than functioning as enforceable server rules, these systems are designed to simulate the bureaucratic, procedural, and corporate realities of a Nanotrasen-operated facility. - -The regulations outlined here expand on existing mechanics by formalizing processes such as corporate security protocols, administrative paperwork, fines, visitor interactions, and command hierarchy. -Each section is supported by game design rationale, roundflow considerations, and (where applicable) technical implementation notes to ensure both usability and immersion. - -While not all features are required for immediate implementation, this document serves as both a design foundation and a roadmap for future development, prioritizing systems that improve clarity, consistency, and player engagement without overburdening gameplay. - -## Background - -Not everything that *was* SOP or law perfectly fits within the older sections of them, as such we are creating the "station regulations" to be a catch all for NT's rules that dont quite fit into our other primary catagories. - - -# Corporte Espionage Act -This section is intended to be in direct relation to the metashield on an OOC level along with IC justifications for the Crew/Security metashields and NDAs. -In character the majority of crew would understand this as related to NT's R&D into bluespace, genetics, artifacts, and anomolies, building off of the syndicate being a known orginisation that conducts espionage. - -## Administrative & Server Rule Impact -This section will be written under the explicit perview of, or by the hand of, the head admins. - - -# Permits and Paperwork -Permits and Paperwork cover what paperwork to use, when to use it, and what utensils to use with it. -EG: - -To hire person X use Hiring Form 4.23, along with adendum 2 for hiring non-NT members - -Access is only granted after filling out Access Form 6.23 C - -Construction or modification of maints should be done with Construction Form 32.45 - -All paperwork must be filled with a black-ink pen unless specified in... - -Copies of official paperwork should be stamped by the relevant head - -## Game Design Rationale -By codifying the forms and permits it should make the system easier to navigate for newer players, and prevent abusive forms from making their way into printer files (I am personaly guilty of some of these). -Additionaly the Codification of paperwork is more authentic to a corprate experiance where files are flying about the home office every day. - -## Roundflow & Player interaction -In a round a player (just like anyone in a corporation) will know generaly what they will be required to fill out should they be asked for paperwork, and may even print and fill it out themselves, or with the help of the local librarian. - -## Technical Considerations -This section will require the implimentation of the Printing Machine. -The printing machine provides players with a way to quickly print forms in-round without needing a folder of documents they must search through. -2 versions of the printing machine should be avalible, a "secure" version for command/security use, and a "regular" version for crew use. -The "regular" version will contain documents that normal crew may need such as hiring applications, access requests, and construction permits. It will be kept in the library or simular areas. -The "secure" version will additionaly contain documents such as command/security hiring forms, NDAs, police reports ect. It will be kept behind access locked doors. - -This section will not require, but would greatly benefit from, the implimentation of fillable form fields. -This will make filling forms easier to understand for players without having to interprit rundown text. - -# Building/Construction code - -This section would define what is a "baseline" room via atmosphere, construction, types of walls/windows to use when, firelocks and air alarms, ect. - -## Game Design Rationale -In game this would serve as an effective tutorial to building and room construction for newer engineers/players, and can be referenced in the permits system for construction. -This creates a more authentic experiance to newer players and intergrates the guidebook further into the world as a "real" learning tool. - -## Roundflow & Player interaction -This should have minimal impact on roundflow outside of obtaining permits and teaching/learning construction. - -# Fines -Fines are for when things are not fine. When you commit an SOP infraction or Corprate Law based infraction you may be ordered to pay a fine. -This section explains the who, how, and why of fines. It does not explain how this is diffrent from a governmentaly approved bribe. - -Who can give them - -Why they can be given - -How to give them - -How to pay them - -It also covers the courses of action that the IAA can take. Primarily issuing a fine or asking the head of staff to take greater actions. - -## Game Design Rationale -This maintains authenticity because it provides a way for security to punish negative behavior without needing to haul the person all the way to security which would lower nantotrasen's profits. -This maximises RP potential because instead of a simple warning there is direct action taken against the person who can then chose to escalate, not pay, or dispute the fine. - -## Roundflow & Player interaction -This will provide a way for players to interact and begin escalation with security outside of reciving a warning, which is unsatisfying, and jail time, which could be over the top. - -It also provides the IAA with a more explicit path for punishments outside of taking possibly vital equiptment, or simply firing the person. - -## Administrative & Server Rule Impact (if applicable) -This section should have no administrative impact aside from role abuse, which generaly should be able to be dealt with in character with unions and escaltation. - -## Technical Considerations -Scrip is required. -We cant take away the money of someone without money. - -A fine computer/printer is not required, but could greatly benefit the system. -This would alow the security officer to print the fine recipt quickly, and the recipiant to pay it at the designated point. - - -# Extracorporate Entities -This section covers interactions with visitors to the station. Visitors are an under-used RP mechanic, and while this will by no means fix that, it will provide a direction to take the interactions with them. -The sections contained within include: - -Shuttle rights - -Docking - -Trading - -Treatment of visitors - -Refugees - -External hiring (temporary and complete contracts) - -## Game Design Rationale -Authenticaly, any large port will also have regulations for how to interact and treat visitors from other orginisations. This would be especialy true for a corprate research colony that knows of spies. - -## Roundflow & Player interaction -This is not intended to effect the flow of most rounds, but should alow for rounds that do interact with visitors to have more guidance than "oh ok, I geuss your visiting now" -Idealy this will make even mundane visitors have a level of impact with the personel on the station through things such as medical checkups and acnowladgement of visitation. - -## Technical Considerations -Maps will require a designated "visitor" dock. - -Visitor shuttles will need some way to broadcast their pressence. - -While not required, IDs and PDAs can be removed from non-NT/infiltration aligned visitors. This will also provide a noticable distinction between roles that are part of NT (such as a CMO in an escape pod), and visitation roles that are simply visiting. - -# Insurance -NOTE: Insurance is something that will not be directly added by this workgroup as it is outside of our intended scope, it is merely here as an example that could be added in the future. - -This would create a codified explanation of what each insurance level entails: - -What premiums you may have to pay each shift - -Coverage of injuries - -Coverage of non-health related surgeries - -Cybernetics - -# Alert Levels -Not exactly new, alert levels have been moved from SOP to regulations as they are called for situations that are not standard. - -General: Most alerts are un-changed in their cause/response with the following exeptions: - -Blue alert is called for a duration of up to 10 minuets while a Felony class or higher crime is under investigation (See Law Document). - -Starting at blue alerts the HoS will be slated for overwatch from security (See the Command document for more information on the HoS rework) +A crime is being actively investigated by security. Crew are to have their IDs ready and comply with security search orders. Events may be canceled without warning should the situation require it. -Violet alert grants the CMO and Captain the ability to quarantine areas of the station which may only be lifted by the CMO or Captain’s orders. -Security is given permission to enforce this quarantine through any method the captain allows. -This also requires sensors set to show health at a minimum to better track the spread of the infection - -Events may be canceled without warning should the situation require it. +HoS is locked to Security. +Red +All crew members are to follow the instructions given by their Commanding members. Unless declared otherwise, they should remain in their departments. +Anyone who is not currently part of a department should head to the Bar -Red Alert: -RED alert now alows the captain to deem specific SOP as suspended, this replaces the SOP per alert level SOP. -This is also being done to reduce confusion about alert levels being SOP, and possibly making it enforceable by security instead of the CCVIPs which was always an odd position for them. +Captains may suspend any Standard Operating Procedure they deem necessary. +This includes removing restrictions on command or crew arming and the creation or purchase of weapons, mechs, and armour. Security’s restrictions on heavy weapons are also lifted and it is expected that the Head of Security and/or Warden keep track of what weapons are taken by who to account for their return when the situation is resolved. Departmental breaks and crew events such as in the theatre and chapel are paused for the duration of the alert. Gatherings may be broken up as needed. -HoS will still be religated to their department outside of immediate station ending threats that will require a full response force (EG god summoning) (again see the Command document for more information on the HoS rework) - - - -# Order of Succession and Martial Law -The Order of Succession determins who will be next in line for the captain position. -EG: -1. Captain -2. HoP -3. RD -4. QM -5. CMO -6. CE -7. HD (Hospitality director, expended on in job changes) -8. Acting command with the above order -9. HoS - -This can be triggered via a vote of no confidance amongst command. This is started by the CCVIPs, or by the CMO deeming the captain as unfit for duty. - -The Head of Security will take over the station until a suitable captain replacement can be found, at which point power will be relinquished to them. -Martial law can be declared by the HoS once no other suitable replacements for the captain can be made. - -Under martial law security’s orders are final, personnel are to immediately return to their departments or bar unless given explicit permission otherwise, and failure to do so leaves punishment at the discretion of the witnessing officer. -This includes engineering and medical personnel who are responding to emergencies, and scientists responding to anomalies. - -## Game Design Rationale -This goes mostly to authenticity, in an emergancy the HoS is intended to have an overview of the security situation, while the captain has an overview of the station as a whole. -Given this is the case, the HoS should not be focused on the extrenous duties of the captain. -Additionaly the station is a Corporate orginisation who's focus is on profit, not simply "catching the bad guy" and this change is meant to highlight this. -Should all command and potential command die, the only authority on the station is the HoS and security, who should not be treating the station as lightly as a regular command member. -The reason the martial law power was specificaly granted is, should the situation become dire enough to require the HoS to become captain, they will likely be in a situation more severe than red alert. - -Martial law is not automaticaly called upon the HoS's promotion due to outlier shifts such as lowpop, or no other command in a lobby willing to play capatain. +Maintenance areas are to be considered off limits; Anyone found inside will be arrested and charged with trespassing. -## Technical Considerations -Possibly an alert level for "Martial Law" can be made, or taken from an existing alert level. +Suit sensors are required to be set to coordinates; Anyone without their suit sensors set on the requested level will be arrested and charged with endangerment. + +Warden is mobile command. +Yellow +There is an active atmospheric or power related issue upon the station that may place crewmembers at risk. Crew should move about with caution and are advised to enable suit sensors in case of injury. +Opening firelocks and spreading the atmospheric issues will be met with an endangerment charge. +Cyan +There is a malfunctioning silicone upon the station. Please use caution when interacting with silicone based lifeforms and inform the roboticist or security should you notice anything unusual. +Violet +In the case of an active viral threat on station, crew are required to have sensors set to show their health to better track the spread of the infection. + +The CMO may declare portions of the ship under quarantine which may only be lifted by the CMO or Captain’s orders. Security is given permission to enforce this quarantine through any method the captain allows. + +Gamma +Delta +Epsilon + + +Corporate Espionage Act +Bluespace research +Genetics research +Artifacts research +Anomalous research +(CTM materials) +## Permits and Paperwork +Paperwork + +Permits + +Hiring Process (Internal) + +Service Department Expensing +All expenses implicitly approved by a position's SOP should be under X scrip. +All other expenses must be approved by the Hospitality Director or Quartermaster. +Any unapproved expenses that are charged to the service budget will be taken from the personnel’s pay. +Any alterations to service department locations must be minor in scope, unless otherwise approved by the Hospitality Director. +Science Distribution +No weapons are to be created or handed out to non-security staff. +All items created must be paid for by personnel in scrip. +The value charged should not be changed between requests without approval from the Research Director. +Department Specific items and machines should only be handed out to personnel with such access, or a stamped form from the relevant authority. + +## Fines +Corporate Disciplinary Actions +Internal Affair Agents are allowed to generate a Corporate Disciplinary Action for crew members that violate SOP. +Corporate Disciplinary Actions may result in a formal warning and/or a fine. + + +If many Corporate Disciplinary Actions are levied against someone, IAA's are advised to inform the head of the department with the proper paperwork detailing the past infractions incurred and requesting the head to take punitive actions against this individual. + +The punitive actions taken are at the sole discretion of the relevant Head of Staff. +The punitive actions are as follow: +A permanent reduction in salary +A temporary suspension +A demotion +A dismissal + +An appeal for the CEA and/or fine can be made to the NanoTrasen Representative, Head of Personnel, or Captain + +### Infractions +Security personnel are allowed to issue infractions to crew members committing infraction level crimes. +The infraction may result in a formal warning and/or a fine. + +If many infractions are levied against someone, security is advised to approach the head of the department with the proper paperwork detailing the past infractions incurred and requesting the head to take punitive actions against this individual. +Punitive actions taken are at the sole discretion of the relevant Head of Staff. + +An appeal for the Infraction and/or fine can be made to the Judicial Officer, Head of Personnel, or Captain. +## Extracorporate Entities +### Docking Regulations +Extracorporate shuttles are required to request docking permission from the station before docking to the station itself. +### Trading Regulations +Trading should be done through the Quartermaster with the NanoTrasen Representative’s permission, or presence. +### Treatment of Visitors +Visitors should be checked by NanoTrasen Medical staff for infections that may risk NanoTrasen Personnel. Should they be cleared by medical personnel + +Visitors should be treated with the same level of dignity they treat NanoTrasen station staff. They must however provide funds for purchase of benefits such as healthcare, drinks, food, and other amenities. +### Refugees +Refugees are to be treated the same as Visitors, however they are to be brought back to NanoTrasen for further processing. (interrogation, Extracorporate secrets, ect) + +### Visitor Restrictions +All visitors are subject to NanoTrasen Laws and Regulations while within NanoTrasen owned territory. +### Hiring Process (external) + +#### Temporary Contracts +Contracts given for the specified duration, usually in relation to shift length or specific task. Can be given by command members on the station with the captain’s permission. + +#### Complete Contracts +Standard NanoTrasen hiring contracts. Requires NTR approval to be completed. + +## Insurance +### Medical Insurance +Deductibles, shift start costs (eg lowered scrip payments/starting amount), insurance levels, minimum insurance for jobs and discounts +### Shuttle insurance +This section is more about contacting CC to report the loss of a shuttle, and what to do in that situation. + +## Order of Succession +Should a captain be incapacitated or deemed unable to perform their duties the order of succession determines who is next in line for the position. + +Captain +Head of Personnel +Research Director +Quartermaster +Chief Medical Officer +Chief Engineer +Hospitality Director +Acting Command in the same order as above +Head of Security + +Should no command member able to be promoted to command remain, the HoS may declare a level of martial law over the station until a new captain can be appointed. + +### Vote of No Confidence +A vote of no confidence can be triggered in two ways: +Central Command VIPs can call a vote of no confidence should they believe the captain is unable to perform their duties. This can only be called by a vote with a majority of Central Command VIP’s approval. +The Chief Medical Officer may call a vote of no confidence should they deem the Captain to be unfit for duty. + +When a vote is called all members of command should report to the bridge or another secure location immediately. The Head of Security is not permitted to cast a vote. The vote requires a simple majority required to pass. The vote should be overseen by a Central Command VIP, and then the results verified by them. Central Command should be notified of the vote, but do not expect a response. Approval from Central Command is not required for any part of the vote.The transition of power should be enforced by the Head of Security. + +### Martial law +Martial law is declared once no suitable replacements for the captain can be made. The Head of Security will take over the station until a suitable captain replacement can be found, at which point power will be relinquished to them. + +Under martial law security’s orders are final, personnel are to immediately return to their departments or bar unless given explicit permission otherwise, and failure to do so leaves punishment at the discretion of the witnessing officer. This includes engineering and medical personnel who are responding to emergencies, and scientists responding to anomalies. From 49177ca37d0e72d22695f67fbd655907bf97b160 Mon Sep 17 00:00:00 2001 From: Alicios Date: Tue, 5 May 2026 18:25:21 -0700 Subject: [PATCH 21/53] Article 5 Updates --- .../article-5_design_doc.md | 54 +++++++++++++++---- 1 file changed, 43 insertions(+), 11 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/article-5_design_doc.md b/src/design-proposals/station_protocol_rework/article-5_design_doc.md index 623d5a5e..5b86983d 100644 --- a/src/design-proposals/station_protocol_rework/article-5_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-5_design_doc.md @@ -30,16 +30,17 @@ Essentially, any and all interaction with legal battles in the game's current st ### Job Restructuring: -Many of these changes are part of the larger design proposals from the SOP Workgroup, but I will highlight the ones that are vital for the Legal System. +Many of these changes are part of the larger design proposals from the SOP Workgroup, but it is important to highlight the ones that are vital for the Legal System. -Head of Personnel (Head of Service) -> Executive Officer (Head of Legal) -Magistrate (CCVIP) -> Judicial Officer (Legal Deputy) -Internal Affairs Agent (CCVIP) -> Internal Affairs Agent (Legal) +Head of Personnel (Head of Service) -> Executive Officer (Head of Legal)\ +Magistrate (CCVIP) -> Judicial Officer (Legal Deputy)\ +Internal Affairs Agent (CCVIP) -> Internal Affairs Agent (Legal)\ Lawyer (Civilian) -> Lawyer (Legal) There is a new clear division between Security, and Legal staff. This will come with a comms channel specifically for Legal staff, to help the Legal team facilitate court cases, and hearings. -Ideally, Legal would become its own department. Existing maps can just reuse the current Lawyer, Magistrate, and IAA offices, as well as the Court. However, it is also very possible to just have these roles remain civilian, and just give them the Legal comms channel. +Legal becomes its own department, with its own comms channel to facilitate smooth court operations, but it does not need major mapping changes. +Existing maps can just reuse the current Lawyer, Magistrate, HOP, and IAA offices, as well as the Court. ### Job Responsibilities & Authority: @@ -60,9 +61,9 @@ This is also part of the SOP Workgroup's Corporate Law proposal, but it is worth There are now only 4 tiers of crimes, each with FIXED punishment lengths in each tier. -Infractions: Warning/Tickets -Misdemeanor: 10 minutes. -Felony: 20 minutes. +Infractions: Warning/Tickets\ +Misdemeanor: 10 minutes.\ +Felony: 20 minutes.\ Capital Offense: Permanent. Permanent Brig time threshold is 40 minutes, instead of 20. @@ -128,6 +129,37 @@ Trials consist of a formalized procedure, multiple witness and evidence examinat Trials are capable of, and intended to, consume a Legal role's entire round. This is why they are entirely opt-in, and case-by-case. A Trial will NEVER be standard procedure for any crime, and only happen if all players involved wish to engage in formalized legal scenarios. +## Addressing Common/Anticipated Concerns +### Sentencing criminals will take too long. +Summary hearings are designed in such a way to directly replace the old "Warden-style" quick sentencing. For minor, inconsequential crimes, the criminal will be processed in hardly any time at all. The process is simply formalized and opens the floor for the defense to escalate into a more lengthy legal battle if they so desire. + +Even for Capital Offenses, the escalating to a full-on trial is a fully voluntary affair, and also up to the discretion of the Judicial Officer. Lengthy trials are an opportunity for players who WANT long trials to have them, without hurting the necessary efficiency of your everyday sentences. + +### There is no way a court hearing can happen in such a short amount of time. +The procedure for each type of Hearing is a formalized step-by-step process, and is intentionally designed to keep hearings brief and efficient. It reduces as much back-and-forth as possible, and focuses only on key facts and agreed upon talking points. + +Having jobs/roles that are knowledgeable and primarily responsible for Legal procedures will also dramatically cut down on rambling/unfocused court cases that we have now. Since Trials are so rare in current Funky, there is no common consensus on how they should be run, which leads them to be unfocused and inefficient. + +### Role bloat with a new department and/or new department will have nothing to do. +Every "new" Job in this proposal is a job that already existed. The things that a "Legal team" would do are already happening, it is just not formalized as a separate entity. It is simply reinforcing their responsibilities and reframing them as a team that works together, instead of disparate individuals from separate departments and power scales dysfunctionally trying to work together. +Each job other than the Judicial Officer is also intentionally designed to have alternative, lesser tasks when hearings/trials are not happening. Legal Jobs to not only exist within the court, they have their own tasks and assemble when necessary. + +XO -> Help the Captain enforce corporate policy, manage ID access, handle paperwork/permits\ +JO -> Participate in civil suits, or more casual Legal RP scenarios.\ +IAA -> Perform SOP audits, provide legal counsel, measure productivity quotas.\ +Lawyer -> Help draft civil suits, consult with brigged criminals, propose parole\ + +Once Unions are implemented, the Legal team will play a big part as correspondants between the general Crew, Unions, and Command. + +### Not everyone wants to participate in Legal RP. +Every Hearing/Trial procedure has a path of least resistance, so that if the arrested criminal does not wish to engage with Legal RP whatsoever, they have that choice. They can refuse consultation or legal representation. They can accept any charges without any pushback. The pipeline of arrest -> sentence -> brig -> continue still exists, it is just an option, rather than the only choice. Trials are completely optional, and no one will be forced into it if they do not wish to. + +### Brig times will be too long. +Brig times should be longer in general, to accompany Funky Station's inherently longer round time. Going through the whole process of an arrest only for someone to get a 5 minute sentence is a complete waste of time. There is no incentive to fight back or engage in any meaningful RP when there is no gameplay incentive to do so. + +Brig times are longer, but with the additions of Alternative Punishments and Parole, those who actually engage with the Legal System will be given opportunities to circumvent their "time out" time with RP scenarios. Talking with Lawyers, the Judicial Officer, the Warden, getting a new Job, consultations with Chaplains and Psychologists are all avenues to reduce your brig time, and result in much more interesting scenarios post-arrest. + + ## Game Design Rationale ### Seriously Silly: @@ -142,7 +174,7 @@ Currently, getting brigged is just about the most glaring instance of "clearly l This Legal overhaul creates opportunities for gray areas and ways to fight back against getting arrested at every opportunity. Even a permanent brig sentence is just an opportunity to consult a Lawyer and ask for parole. Getting arrested shouldn't feel like you "lost", it should just be the next chapter in your story. ### Maintaining Authenticity: -Real-life Legal procedures are incredibly pedantic, formal, and take ages. I am not trying to emulate legal procedures for realism's sake. I am taking inspiration from real courts of law, and seeing which parts meaningfully create opportunity for conflict and roleplay, and condensing it into a manageable amount of rules for use in game. +Real-life Legal procedures are incredibly pedantic, formal, and take ages. We are not trying to emulate legal procedures for realism's sake. We are taking inspiration from real courts of law, and seeing which parts meaningfully create opportunity for conflict and roleplay, and condensing it into a manageable amount of rules for use in game. Many people are familiar with legal stories and dramas, with court cases in TV shows, and video games. The goal is to take that larger-than-life, dramaticized version of court, and inject that into the game. @@ -161,11 +193,11 @@ Every major crime becomes it's own story and fight in court. More moving parts c ## Roundflow & Player interaction This is a major change to sentencing and criminal interactions. It will affect every single arrest, impact almost any antagonist role that commits a crime. -This is why I have intentionally designed Summary Hearings to be quick and efficient, and emulate the old Warden quick sentencing. Not every crime needs a full on procedure; we should be putting time and effort into places where it matters, like major crimes. +This is why we have intentionally designed Summary Hearings to be quick and efficient, and emulate the old Warden quick sentencing. Not every crime needs a full on procedure; we should be putting time and effort into places where it matters, like major crimes. There will be a large variation in how Legal players interpret their role. Some JOs will be extremely strict and overly harsh, and create tons of conflict. Some will be incredibly lenient and get in trouble with the XO. This is intentional, and welcomed. -I mentioned it in the relevant section, but Trials are entirely opt-in. No one will be forced into an hour-long legal battle unless they want to. All players who are charged with a crime will have to interact with the legal system in some capacity, but it should never completely consume their round unless they want it to. +It is mentioned in the relevant section, but Trials are entirely opt-in. No one will be forced into an hour-long legal battle unless they want to. All players who are charged with a crime will have to interact with the legal system in some capacity, but it should never completely consume their round unless they want it to. ## Administrative & Server Rule Impact (if applicable) From 2eefdee10d69f0979bf8bdb4adf49b61fdafb1a6 Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Wed, 6 May 2026 16:44:23 -0300 Subject: [PATCH 22/53] Added Failure to Pay a Fine as a Misdemeanor Crime --- .../station_protocol_rework/Article 2 - Corporate law.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md b/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md index df3abf12..d448c988 100644 --- a/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md +++ b/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md @@ -214,7 +214,7 @@ Unlike the implantation procedure a prisoner can have their sentence entirely de | | Assault (V) | Mutilation (V) | Prevention of Revival (V) | | | | Kidnapping (W) | Suppression of Free Will (W) | | Cannibalism | Animal Cruelty | Bribery | Refusal of Lawful Implantation | -| | | Tax Evasion | Breach of NT Contract | +| | Failure to Pay a Fine | Tax Evasion | Breach of NT Contract | ### Crime Specifications: | A | Access | Existing where you are not allowed. | @@ -312,6 +312,7 @@ Unlike the implantation procedure a prisoner can have their sentence entirely de | :---- | :---- | :---- | | Infraction | Cannibalism | To consume a portion of another sapient being, without express consent. | | Misdemeanor | Animal Cruelty | Inflicting excessive harm on a living being, except when required for medical treatment, scientific research, or the preparation of food. | +| Misdemeanor | Failure to Pay a Fine | Failure to pay a legally imposed fine within the required timeframe. | | Felony | Bribery | Offering or giving gifts, money, or favors to influence Command to act outside of their allowed duties. | | Felony | Tax Evasion | Not paying NanoTrasen-mandated scrip taxes, or using non-scrip currencies to avoid paying taxes. | | Capital Offense | Refusal of Lawful Implantation | Refusing to accept a lawful implant from Security personnel while in custody. | From efc7ab5ca65ba8b9b2c087603b665c76adbe082a Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Wed, 6 May 2026 22:20:32 -0600 Subject: [PATCH 23/53] Update Article 1 - Station Regulations.md --- .../Article 1 - Station Regulations.md | 182 ++++++++++++++---- 1 file changed, 146 insertions(+), 36 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md index 2724ac2a..91c6a704 100644 --- a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md +++ b/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md @@ -1,18 +1,30 @@ # NanoTrasen Station Regulations + ## Alert Levels -Green + +### Green There is no major threat to operational safety. + SOP and Corporate Law remain in full effect. -Blue -**Called for the reason of un unsolved Felony + +### Blue + +Called for the reason of un-unsolved Felony A crime is being actively investigated by security. Crew are to have their IDs ready and comply with security search orders. +Security may carry concealed longarms + Events may be canceled without warning should the situation require it. -HoS is locked to Security. -Red +HoS is to remain in security to collate officer reports and the detective's evidance, directing security's responses and patrols as needed. + +### Red + +There is an active lethal threat on station that security is preparing to combat/currently combating. + All crew members are to follow the instructions given by their Commanding members. Unless declared otherwise, they should remain in their departments. + Anyone who is not currently part of a department should head to the Bar Captains may suspend any Standard Operating Procedure they deem necessary. @@ -22,63 +34,121 @@ Security’s restrictions on heavy weapons are also lifted and it is expected th Departmental breaks and crew events such as in the theatre and chapel are paused for the duration of the alert. Gatherings may be broken up as needed. -Maintenance areas are to be considered off limits; Anyone found inside will be arrested and charged with trespassing. +Maintenance areas are to be considered off limits; Anyone found inside may be arrested and charged with trespassing. Suit sensors are required to be set to coordinates; Anyone without their suit sensors set on the requested level will be arrested and charged with endangerment. -Warden is mobile command. -Yellow +Warden takes over the position of local squad command for larger scale combats. + +HoS provides overwatch and directions from security. + +### Yellow + There is an active atmospheric or power related issue upon the station that may place crewmembers at risk. Crew should move about with caution and are advised to enable suit sensors in case of injury. -Opening firelocks and spreading the atmospheric issues will be met with an endangerment charge. -Cyan -There is a malfunctioning silicone upon the station. Please use caution when interacting with silicone based lifeforms and inform the roboticist or security should you notice anything unusual. -Violet -In the case of an active viral threat on station, crew are required to have sensors set to show their health to better track the spread of the infection. +Opening firelocks and spreading the atmospheric issues may be met with an endangerment charge. + +### Cyan + +There is a malfunctioning silicone upon the station. Please use caution when interacting with silicone based lifeforms and inform the RD and/or security should you notice anything unusual. + +### Violet + +There is an active viral threat on station, crew are required to have sensors set to show their health to better track the spread of the infection. The CMO may declare portions of the ship under quarantine which may only be lifted by the CMO or Captain’s orders. Security is given permission to enforce this quarantine through any method the captain allows. -Gamma -Delta -Epsilon +### Other +Other station alerts are tied to admin events/automatic calls and are left alone at the current moment. + +## Corporate Espionage Act + +### Standard (crew): + +Knowladge of research classifications -Corporate Espionage Act Bluespace research + Genetics research + Artifacts research + Anomalous research -(CTM materials) + +Standard NDAs that only mention research being classified to the company. + +### Prepared (Security): + +Additional knowladge of Overwatch classification's existance. + +The existance of need-to-know information. + +Security class NDA. + +### Privladged (Command/CCVIP): + +Standard CTM knowladge. + +### Overlord (CCO/I): + +Admin level knowladge, they know what they decide they know. + ## Permits and Paperwork + Paperwork Permits -Hiring Process (Internal) +### Hiring Process (Internal) + +How to go about hiring from the NT personel pool of employees for standard, security, or command positions. + +## Departmental SOP + +### Nanotrasen Building Code + +A standard code for building room types and procedures. + +### Service Department Expensing Regulations -Service Department Expensing All expenses implicitly approved by a position's SOP should be under X scrip. + All other expenses must be approved by the Hospitality Director or Quartermaster. + Any unapproved expenses that are charged to the service budget will be taken from the personnel’s pay. + Any alterations to service department locations must be minor in scope, unless otherwise approved by the Hospitality Director. -Science Distribution + +### Science Distribution Regulations + No weapons are to be created or handed out to non-security staff. + All items created must be paid for by personnel in scrip. + The value charged should not be changed between requests without approval from the Research Director. + Department Specific items and machines should only be handed out to personnel with such access, or a stamped form from the relevant authority. -## Fines -Corporate Disciplinary Actions + +## Regulatory Fines + +### Corporate Disciplinary Actions + Internal Affair Agents are allowed to generate a Corporate Disciplinary Action for crew members that violate SOP. Corporate Disciplinary Actions may result in a formal warning and/or a fine. - If many Corporate Disciplinary Actions are levied against someone, IAA's are advised to inform the head of the department with the proper paperwork detailing the past infractions incurred and requesting the head to take punitive actions against this individual. The punitive actions taken are at the sole discretion of the relevant Head of Staff. + The punitive actions are as follow: + A permanent reduction in salary + A temporary suspension + A demotion + A dismissal An appeal for the CEA and/or fine can be made to the NanoTrasen Representative, Head of Personnel, or Captain @@ -91,57 +161,97 @@ If many infractions are levied against someone, security is advised to approach Punitive actions taken are at the sole discretion of the relevant Head of Staff. An appeal for the Infraction and/or fine can be made to the Judicial Officer, Head of Personnel, or Captain. + ## Extracorporate Entities + ### Docking Regulations -Extracorporate shuttles are required to request docking permission from the station before docking to the station itself. + +Shuttles are required to request docking permission from the station before docking to the station itself. + +After reciving docking permission they may dock at the designated location and proced with standard medical checks before disembarking. + ### Trading Regulations -Trading should be done through the Quartermaster with the NanoTrasen Representative’s permission, or presence. + +Trading should be done through the Quartermaster with the Captain’s permission, or presence. + ### Treatment of Visitors -Visitors should be checked by NanoTrasen Medical staff for infections that may risk NanoTrasen Personnel. Should they be cleared by medical personnel -Visitors should be treated with the same level of dignity they treat NanoTrasen station staff. They must however provide funds for purchase of benefits such as healthcare, drinks, food, and other amenities. +Visitors should be treated with the same level of dignity they treat NanoTrasen station staff. +They must however provide funds for purchase of benefits such as healthcare, drinks, food, and other amenities. + +Visitors must be kept away from the research computers and servers, along with any artifacts or anomolies that may be on station. +This is to prevent the accidental leak of classified material to non-NT personel. + +Visitors are held subject to the same laws as Nanotrasen Personel while docked or on board a Nanotrasen station. + ### Refugees -Refugees are to be treated the same as Visitors, however they are to be brought back to NanoTrasen for further processing. (interrogation, Extracorporate secrets, ect) -### Visitor Restrictions -All visitors are subject to NanoTrasen Laws and Regulations while within NanoTrasen owned territory. +Refugees are to be treated the same as Visitors, however they are to be brought back to NanoTrasen for further processing. + ### Hiring Process (external) #### Temporary Contracts -Contracts given for the specified duration, usually in relation to shift length or specific task. Can be given by command members on the station with the captain’s permission. + +Contracts given for the specified duration, usually in relation to shift length or specific task. +Can be given by command members on the station with the captain’s permission. #### Complete Contracts -Standard NanoTrasen hiring contracts. Requires NTR approval to be completed. + +Standard NanoTrasen hiring contracts. +Requires NTR approval to be completed. ## Insurance + ### Medical Insurance + Deductibles, shift start costs (eg lowered scrip payments/starting amount), insurance levels, minimum insurance for jobs and discounts + ### Shuttle insurance -This section is more about contacting CC to report the loss of a shuttle, and what to do in that situation. + +This section is more about contacting CC to report the loss of all shuttles, and what to do in that situation. ## Order of Succession + Should a captain be incapacitated or deemed unable to perform their duties the order of succession determines who is next in line for the position. Captain + Head of Personnel + Research Director + Quartermaster + Chief Medical Officer + Chief Engineer + Hospitality Director + Acting Command in the same order as above + Head of Security -Should no command member able to be promoted to command remain, the HoS may declare a level of martial law over the station until a new captain can be appointed. +Should no command member be able to be promoted to command remain, the HoS may declare a level of martial law over the station until a new captain can be appointed. ### Vote of No Confidence + A vote of no confidence can be triggered in two ways: + Central Command VIPs can call a vote of no confidence should they believe the captain is unable to perform their duties. This can only be called by a vote with a majority of Central Command VIP’s approval. + The Chief Medical Officer may call a vote of no confidence should they deem the Captain to be unfit for duty. -When a vote is called all members of command should report to the bridge or another secure location immediately. The Head of Security is not permitted to cast a vote. The vote requires a simple majority required to pass. The vote should be overseen by a Central Command VIP, and then the results verified by them. Central Command should be notified of the vote, but do not expect a response. Approval from Central Command is not required for any part of the vote.The transition of power should be enforced by the Head of Security. +When a vote is called all members of command should report to the bridge or another secure location immediately. +The Head of Security is not permitted to cast a vote. +The vote requires a simple majority required to pass. +The vote should be overseen by a Central Command VIP, and then the results verified by them. +Central Command should be notified of the vote, but do not expect a response. +Approval from Central Command is not required for any part of the vote. +The transition of power should be enforced by the Head of Security. ### Martial law + Martial law is declared once no suitable replacements for the captain can be made. The Head of Security will take over the station until a suitable captain replacement can be found, at which point power will be relinquished to them. Under martial law security’s orders are final, personnel are to immediately return to their departments or bar unless given explicit permission otherwise, and failure to do so leaves punishment at the discretion of the witnessing officer. This includes engineering and medical personnel who are responding to emergencies, and scientists responding to anomalies. From 7624fb8e0bb768d9ba008e26a13d7b197ab99962 Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Thu, 7 May 2026 18:20:50 -0300 Subject: [PATCH 24/53] Article 2, adressing initial feedback --- .../article-2_design_doc.md | 34 +++++++++++++------ 1 file changed, 23 insertions(+), 11 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/article-2_design_doc.md b/src/design-proposals/station_protocol_rework/article-2_design_doc.md index dbf47dcd..6cd22623 100644 --- a/src/design-proposals/station_protocol_rework/article-2_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-2_design_doc.md @@ -2,7 +2,7 @@ | Designers | Implemented | GitHub Links | |---|---|---| -| SOP Workgroup, design doc authored by Joaco545 | :x: | TBD | +| SOP Workgroup, Design Doc written by Joaco545 | :x: No | TBD | ## Overview @@ -12,9 +12,10 @@ Space law has been revised to conform to the style of a legal document. The crime list has been expanded, and sentencing guidelines have been simplified. Contraband has been vaguelawed. + ## Background -Funky Station has been changed to have a Corporation vs Crew / Class Conflict theme. This requires updating Space Law as it no longer fits the theme. +Funky Station has been changed to have a Corporation vs Crew, Class Conflict theme. This requires updating Space Law as it no longer fits the theme. Currently, space law feels like something an external entity that is not Nanotrasen has set in place, and is forcing NT to comply with it; We aim to change that feeling completely. We also took this opportunity to add some things to increase the RP potential, coupled with the [sentencing changes](article-5_design_doc.md). @@ -60,20 +61,17 @@ Note: Execution requires Captain and XO (HOP) approval Big times have been standardized so that sentencing gets easier. They now directly depend on their category, instead of the individual crime. The crime list has also been expanded to give NT more power over how people and unions behave. The line between a strike and a riot is a thin one. -We expect security vs crew to increase the friction between NT-Command and the Crew, giving more opportunities for escalation should the players choose to do so. +We expect security vs crew to increase the friction between Command and the Crew, giving more opportunities for escalation should the players choose to do so. #### Infraction enforment Infractions are not meant to be something everyone needs to go to a judge for; They will be handed out by Security. -These two new things will need to be implemented: -- Sec will need to get a new device capable of printing fines, and; -- An ATM-like device near the courtroom that allows players to pay the fine, or page the judge to dispute it. - As a perverse incentive, fines will go to the Security department’s budget, and the Head of Security will be able to use those funds to buy things for the team or increase the pay of Security employees. - +Fines can be disputed, but that requires the player to say they want to do that (See [Technical Considerations](#technical-considerations)). +As a perverse incentive, fines made by Security will go to the Security department’s budget, and the Head of Security will be able to use those funds to buy things for the team or increase the pay of Security employees. ### Corporate Law: Contraband Classifications Old Contraband has been replaced by Vaguelawed Contraband. To support this change, contraband markers will need to be removed from the game. These changes were made to increase the RP potential, as now, confiscating something is a choice to be made by players, and not by a marker. -This also makes meteshielded components harder to identify, as again, there is no marker, making confiscation a must (Syndicate pajamas, anyone?) +This also makes meteshielded components harder to identify, unlike the old system which made confiscation a must (Syndicate pajamas, anyone?) It is also another way for escalation to happen is Sec confiscates too much or too little with the crew and command, respectively ### Corporate Law: Legal Exemptions @@ -97,9 +95,23 @@ A lot of these changes have been done with two pillars in mind: ## Roundflow & Player interaction -Corporate Law is something that will permeate each round from roundstart, and all players will have to engage with it. -While common sense will keep most players outside of Securities radar, it will still be something present. +Corporate Law is something that will permeate each round from roundstart till evac docs on CC, and all players will have to engage with it. +Common sense will keep most players outside of Securities radar, but it will still be something present. + +Example of Non-Antag Escalation Oportunities: +As an example an assitant could get fined by security for Loitering, the assistant, not able to get the Scrip to pay the fine, gets charged with Failure to Pay a Fine. This builds up resentment, and once they are out of the brig, the look for other people wronged by sec and start a strike. +As the strike was not approved, Security tries to split up the strike. First peacefully, then by using Tear Gas. Then the thing turns violent and now there is a partial riot on the station. + +Example of Antag Shielded Contra: +A wizard appears on the station, a security officer stops them for a random search. They see some clothing and an orb, think nothing of it, and let them go. Half an hour later the wizard has killed 3 people and is captured, this time command gets involved and recognizes that the orb and clothes are used for casting the dangerous spells the wizard has been using per the CTMs info. They decide to confiscate the items saying that their combined use is like that of a major weapon + ## Administrative & Server Rule Impact (if applicable) As mentioned on the main doc, with so many changes we think players will AHelp more to ask for clarification on said changes. + +## Techincal Considerations + +For infraction enfocement, two new things will need to be implemented: +- Sec will need to get a new device capable of printing fines, and; +- An ATM-like device near the courtroom that allows players to pay the fine, or give the option to page the judge for it to be disputed. From ee71ebefd874128bebbafd27946a98fdd5e553e8 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 19:38:34 -0400 Subject: [PATCH 25/53] Version 1.1 --- .../article-3_design_doc.md | 116 +++++++++++++----- 1 file changed, 88 insertions(+), 28 deletions(-) diff --git a/src/design-proposals/station_protocol_rework/article-3_design_doc.md b/src/design-proposals/station_protocol_rework/article-3_design_doc.md index 8c55995c..9d034758 100644 --- a/src/design-proposals/station_protocol_rework/article-3_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-3_design_doc.md @@ -1,53 +1,113 @@ -# Short, Properly Capitalized Title -Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. -| Designers | Implemented | GitHub Links | -|---|---|---| -| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | - -`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: -- This acknowledges credit where it is due -- People who are confused about the written intent can use this information to contact the authors -`Implemented` is the status of the feature. +# Nanotrasen Colonial Law and Procedures, Article 3: Standard Operating Procedure -Github links can include multiple PRs, if relevant. +| Designers | Implemented | GitHub Links | +|---|---|---| +| SOP Workgroup, Authored by Gamercodeleo1 |:x: No | TBD | ## Overview -A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". +This doc will cover the Standard Operating Procedures Section of the new Nanotrasen Colonial Law and Procedures. The reasoning for the changes and the guidelines for the new SOP that has been written. ## Background +This section of the Nanotrasen Colonial Law and Procedures (I'll refer to it at NCLP from now on) is designed to rework SOP to fit better with the new vision of the game post-forky. Current SOP tends towards being very oddly written, very inconsistent, and is not aligned with the new vision for the game. SOP also has a bad habit of simply being server rules, which is very counteractive to the point of SOP, which is to cause conflict. SOP that is also a rule, and thus cannot be broken, should be avoided at all costs. There has also been a focus on making command further from the regular crew, to play further into our theme of class conflict. -Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. +## Features to be added +There are many things planned to be changed in SOP so I will give each their own section. A large part of the SOP has already been drafted. This section will cover the proposed changes and use examples from that draft. If you would like to see the draft, check the related drafts of the document: +[Article 1 - Station Regulations](./Article\ 1\ -\ Station\ Regulations.md) +[Article 2 - Corporate Law](./Article\ 2\ -\ Corporate\ law.md) + +[Article 4- Unions](./Article\ 1\ -\ Unions.md) +[Article 5 - Sentencing, Trials, and Hearings](./Article\ 5\ -\ Sentencing,\ Trials,\ and\ Hearings.md) + +### SOP Requirements +These are guidelines for drafting the SOP that cover how we expect SOP to be written, and things to be included. +*This section is based off of a version created by Catty.* +#### Minimum Job Requirements +This type of SOP is more about results rather than process, and is what would be expected should a player being performing their job properly. This type of SOP should cover what you do to do your job properly, and failing to do it would be a failure to perform said job, normally resulting in punishment. This is, of course, just SOP, which is ***explicitly allowed*** to be broken (OOC and server rules-wise, of course). These SOP shouldn't be made as the primary incentive for a playstyle, any changes to that should be encouraged mechanically (with a seperate design document), and then have SOP changed to match. +##### Examples (from the draft): +**Chef 3:** *[The Chef is] to ensure that food for all species on board is available to be produced should it be ordered.* +**Janitor 1:** *[Janitors are to] ensure all public parts of the stations are properly maintained according to Nanotrasen Cleanliness Regulations.* +**Engineer 1:** *[Engineers are to] ensure that the distribution air is a steady mix breathable for a majority of species on the station.* +##### Examples (from current SOP): +**Security Officer [Green] 2:** *Security Officers are required to state the reasons behind an arrest before any further action is taken. Exception is made if the suspect refuses to stop;* + +#### Roleplay and Conflict Creation +This type of SOP is more about creating opportunities for conflict or other roleplay. Ideally each job should have one or more of these. This SOP is meant to align very well with our themes of class conflict and corporate dystopia, and as such can be over the top or unreasonable (but doesn't have to be). +##### Examples (from the draft): +**Clown 3:** *[The Clown is] to attempt to be legitimately funny or entertaining at least once every fifteen (15) minutes.* +**Scientist 4:** *[Scientists are] to document anomalies and artifacts and submit the documentation to the Research Director.* +**Engineer 6:** *[Engineers are to] urgently respond to any request for work from command.* +##### Examples (from current SOP): +**Engineer 10:** *Engineers must ensure there is at least one (1) engineering hardsuit available on station at all times, unless there is an emergency that requires the use of all suits.* + +#### Basically Server Rules +Sometimes the minimum job requirements SOP veers into effectively being server rules, which isn't ideal for SOP (which is meant to be broken), while this type of SOP *can* exist, you should first consider two things: One, can this be communicated in another way (actual rule, space law, mechanics, ect), Two, How can this be made clear it has to be followed. This type of SOP should be avoided if possible, and made clear how important it is, especially with the soon to come removal of Command and CCvip OOC rules (Source: [Catty, SOP Workgroup Head/Community Manager](https://ptb.discord.com/channels/1276640157511979008/1484259495130566656/1501258020435267618)). +##### Examples (from the draft): +**Captain 6:** *[The Captain is to] ensure the safety of the station's nuclear authentication disk at all costs.** +**This is technically a rule break, counting as a play your character rule break.* +##### Examples (from current SOP): +**Captain 5:** *The captain must keep the Nuclear Authentication Disk on their person at all times or failing that, in the possession of the Head of Security;* + +#### MetaSOP +This is SOP that covers how SOP is to be enforced or instructing the following of other SOP. This type of SOP is redundant and arduous. Any SOP that acts as MetaSOP should be moved to either a general SOP chapter or to another article such as Regulations or Corporate Law. + +There are no proper examples from the draft, but there is an example of a solution, there is a General Command SOP that covers what is normally expected of command from Nanotrasen. +##### Examples (from the draft): +**Command 2:** *[All Command Personnel are to] ensure the wellbeing and dignity of Nanotrasen and its related assets.* +**Command 4:** *[All Command Personnel are to] never use any language towards Nanotrasen that may be considered defamatory or overtly negative.* +##### Examples (from current SOP): +**Detective [Green] 6:** *When not undercover, the Detective must follow the same guidelines as Security Officers for attire, with the exception that their own assigned attire is also acceptable for any of the attire mentioned for Security Officers.* + +#### Space Law +Space Law should not be in SOP, if it is a space law issue, it should be put in the space law article. This includes things that give crew special protections or regulations (like arrest procedures). A good example of this is how most command SOP (currently) covers how they are permitted to carry a flash. This is space law, and so should go into space law and it's rules about contraband. Any SOP that is space law should be removed and not added in at all. +##### Examples (from current SOP): +**Chief Medical Officer 2:** *The Chief Medical Officer is permitted to carry a flash and their hypospray;* + +#### Escalation +Escalation is SOP that changes or is altered based on the alert level. This type of SOP is counteractive to how SOP is meant to operate and the very definition of SOP. SOP is **Standard** Operating Procedure, if you are on red alert, you should not expect to be following SOP anymore, this isn't a standard shift. SOP should also be a driver of conflict, let us say a doctor is getting punished for an SOP violation they committed on blue alert due to the chaos in the medical bay, this is good RP, the kind SOP is meant to encourage. Is it wrong to punish a doctor for doing the right thing while under pressure and in an emergency, probably, but it causes that conflict. SOP that relies on alert level should be removed and not added in at all. +##### Examples (from current SOP): +**Scientist [Blue] 2:** *Scientists are permitted to produce weapons and grenades from the protolathe provided they get delivered to security.* -Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. +## Game Design Rationale -## Features to be added +### Seriously Silly +SOP will now be changed to play into more of the serious aspects of our theming, class conflict and corporate dystopia, but there will still be room for the more silly aspects one would expect from Space Station 14. The serious aspects will be more about the punishments and cost of violating SOP and incurring the higher-ups wrath, while the sillier aspects would be finding strange and funny loopholes to SOP, to stick it to those same higher-ups. While SOP will likely play more into a serious tone, there will still be opportunities for the silly aspects we all love. -Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. +### There is no Winning or Losing +SOP as a feature is intended to be broken, nobody is expected to be perfect at following SOP, it's a natural thing. So whether you are good or bad at SOP, there isn't a win condition or a loss condition, merely a system that is always there to drive conflict. -## Game Design Rationale +### Maintaining Authenticity +This is what SOP has been focused on in the draft. Trying to play more into our themes we had to reconsider everything about SOP and what it is. While I have already covered what we use to write SOP above, here I will go into more detail about keeping it authentic. + +We have made a lot of changes to try and fit SOP better into the roles and into the other changes we are planning to make in the NCLP. A perfect example is the changes adding in considerations for Scrip and Unions (features we have been told to take into consideration): Scrip has had some major changes to the service department's SOP, with roles like the bartender not only expected to take payment but also now allowed to open a tab for customer. This is both authentic and a good vector for roleplay, allowing for new interactions that wouldn't have occurred before. Imagine a bartender having to report someone to sec for not paying their tab, that's new, interesting roleplay created by a mix of scrip, SOP, and authenticity. Roles like engineering have also had changes made, with them having a more urgent response required for work from command compared to regular crew. Of course Nanotrasen would want it's command to be prioritized, they are the most trusted and likely have a better reason for calling engineering compared to a bartender. That's authentic too, and that's the type of SOP that can really help drive home that class conflict as well. By using existing systems and considering how to make it not real, but authentic, we can drive home our themes in major and minor ways. + +### Take Things Slow +Most SOP has been altered to match more of a slower round flow, although SOP rarely covers time, it does cover another part of this Design Principal, which is making more of an engaging story. *"When designing other features, consider the story you want to tell, and ask yourself if it is a worthwhile story a player wants to engage with for more than 15 minutes."* SOP is a tool to create conflict, and making SOP that can cause an interesting conflict that could last or even change the whole round is something heavily considered when the SOP is written. Ideally SOP should be there as a way to truly cause an interesting story that can play properly into the themes of Funky Station. -Consider addressing: -- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? +### Maximizing Roleplay Potential (Avoid QOL slop) +When the IAA walks into the department, you aren't worried you'll get in trouble because you aren't doing your job, you're worried you'll get in trouble because you forgot to keep an extra hardsuit around as per the SOP (Engi SOP 10). Is that a mechanical issue with your gameplay? No. But it can create that conflict between players, and further that tension between the crew and the higher ups. You may feel it's stupid, and your character may agree, but that is the POINT! You are meant to hate the stupid pedantry of the corporate environment, the rules that you know don't matter, because you're the one who actually does the work, puts in the effort to get things done, and some pencil pusher comes in and decides to tell you that you are the one who's wrong? That, that right there is the point of SOP. The creation of conflict between players, and that is why it aligns so well with this principal. ## Roundflow & Player interaction +SOP isn't guaranteed to come into effect every round, but it should be expected that it will occur often, with the most major conflicts being less common, of course. SOP can come in at almost any point, all it takes is someone to notice an opportunity (like a SOP Violation) and run with it. Most SOP interactions won't effect the whole round, but there can be some times where it boils over and changes the whole round. I would expect us to see more of this as Unions are added and used, as they would be an amplifier to the conflict created by SOP (worker vs. boss). In cases where this happens, SOP can genuinely change the course of the round, causing chaos and protests, and maybe even riots should the conflict grow large enough. Of course, some SOP conflicts might go nowhere, but that is fine as well, as long as some roleplay value was had. -Consider addressing: -- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? -- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? +As for the second part of this, the player interaction, we would hope that players are able to play into the conflict creation potential of SOP, either intentionally or unintentional. Players who don't know SOP will be more likely to break it, and thus get punished by the relevant authorities. This will lead to conflict. Players who do know SOP will likely break the "stupider" parts of it, and get in trouble anyways, just less often and less frequently. Of course we don't expect every player to break SOP, but it should happen unless someone is *perfect* at their job. SOP should remain a constant chance to get in trouble, even if you are working hard. ## Administrative & Server Rule Impact (if applicable) +**1.** Does this feature introduce any new rule enforcement challenges or additional workload for admins? +Yes, this is a feature built on conflict so rules based around conflict (like escalation) will need more attention to them. This is a concern for all of the related changes as well. The one benefit is that SOP is player enforced, and thus, only the actions that violate rules need to be enforced, not anything relating to SOP as well. -- Does this feature introduce any new rule enforcement challenges or additional workload for admins? -- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? -- How are the rules enforced mechanically by way the feature will be implemented? +**2.** Could this feature increase the likelihood of griefing, rule-breaking, or player disputes +Griefing? Not likely. Rule-Breaking? Possibly (see above). Player Disputes? Absolutely. +**3.** How are the rules enforced mechanically by way the feature will be implemented? +They will be enforced by certain positions on the station being encouraged to pressure the positions beneath them to follow the SOP, less they themselves become even more pressured from those above them. Cargo Technicians pressured by IAAs and the QM, who are pressured by their bosses, and at the highest level, Central Command pressuring roles like the captain (Minimum Admin intervention, however). # Technical Considerations +**1.** Are there any anticipated performance impacts? +No. -- Are there any anticipated performance impacts? -- Does the feature require new systems, UI elements, or refactors of existing ones? -- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) +**2.** Does the feature require new systems, UI elements, or refactors of existing ones? +Yes, however there are other design documents being made for those changes, and is out of the scope of this document. However, it will require changes to the guidebook and the addition and change of books that exist as items. From c1088e9120ca0d1adcdcf3362cd2735447692af8 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:31:30 -0400 Subject: [PATCH 26/53] Version 1.2 --- .../station_protocol_rework.md | 17 +- ...rticle 3 - Standard Operating Procedure.md | 378 ++++++++++++++++++ 2 files changed, 391 insertions(+), 4 deletions(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index 4dfc2b4a..aea0d112 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -1,3 +1,4 @@ + # Station Protocol Rework / Nanotrasen Colonial Law and Procedure | Designers | Implemented | GitHub Links | |---|---|---| @@ -24,18 +25,26 @@ Add a series of books and gudebook entries under the name of Nanotrasen Colonial Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: ### Article 1 - Station Regulations Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more - +*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc)* +*[Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. - +*[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc)* +*[Article 2 - Corporate Law](./station_protocol_rework/Article\ 2\ -\ Corporate\ Law.md)* ### Article 3 - Standard Operating Procedure +SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. - +*[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc)* +*[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article\ 3\ -\ Standard\ Operating\ Procedure.md)* ### Article 4 - Unions - +*[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc)* +*[Article 4 - Unions](./station_protocol_rework/Article\ 4\ -\ Unions.md)* ### Article 5 - Trials and Hearings +*[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc)* +*[Article 5 - Trials and Hearings](./station_protocol_rework/Article\ 5\ -\ Sentencing,\ Trials,\ and\ Hearings.md)* + ### Extra considerations "Behavior follows incentives" diff --git a/src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md b/src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md index e69de29b..5c6a5700 100644 --- a/src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md @@ -0,0 +1,378 @@ + +# Article III - Standard Operating Procedures + +## Table of Contents: +1. Command +3. Central Command +3. General Crew +4. Security +5. Logistics +6. Engineering +7. Medical +8. Science +9. Service + +--- +## 1 | Command: + +### All Command Personnel are to: + +1. Ensure the operational efficiency and safety of the station, primarily for their own department. + 1. Command is to ensure that their subordinate crew members and departmental assets are in working condition, and up to NanoTrasen Standards. +2. Uphold NanoTrasen’s authority and dignity upon their station. + 1. Command staff must never use any language or outwardly express opinions about NanoTrasen that may be considered defamatory or overtly negative. +3. Maintain confidentiality concerning NanoTrasen Corporate Secrets. + 1. Command is to report any breaches of confidentiality to Internal Affairs. +4. Communicate and coordinate with other departments, primarily through their respective Heads of Staff. + +### The Captain is to: + +1. oversee all Command Personnel to ensure that the station’s departments are operating as intended. +2. coordinate with Command Personnel and Central Command VIPs about any ongoing situation on station. +3. ensure that any issues arising between Command Personnel are resolved. +4. ensure that the satisfaction of the crew does not rise to levels that could interfere with Nanotrasens objectives. +5. ensure that Nanotrasen Colonial Law and Procedure is being enforced, in conjunction with Central Command VIPs. +6. ensure the safety of the station's nuclear authentication disk at all costs. + +### The Head of Personnel is: + +1. to not provide higher levels of access to personnel without receiving authorization from the relevant Command Personnel for that access. If an access is not restricted to a department or position, the HoP may use their discretion. +2. to issue warrants to security should there be a valid reason for the warrant. + 1. Temporary IDs may be created for the servicing of a departmental search warrant. +3. to not leave their office unmanned if there are personnel waiting in line. +4. to respond to all requests for processing in fifteen (15) minutes or less. +5. to monitor the crew for any complaints that may agitate the crew as a whole and report them to the rest of the Command Personnel. +6. permitted to run advertising campaigns for services and products across the station.Campaigns should: + 1. avoid being disruptive to essential station activities + 2. promote products in a manner consistent with Nanotrasen Values. + 3. avoid becoming an expense greater than the value provided by the campaign. + 4. take payment for any services advertised that are not provided officially by Nanotrasen. + +### The Head of Security is: + +1. to take orders directly from the Captain (and nobody else) and ensure the station remains safe and secure. +2. to ensure that the conduct of security officers is within the bounds of Corporate Law and their Standard Operating Procedure. +3. to ensure a smooth transition of power between Captains, as a result of either a Vote of No Confidence or the Captain stepping down. +4. permitted to deputize members of the crew should their skills be required for a specific assignment. +5. to monitor any hostile actions taken by unions and properly respond. +6. to ensure the gear used by security personnel is properly stored away. + 1. Weapons must be stored inside of the armory unless they are a standard issued sidearm. + 2. Lockers and EVA suits must be locked. +7. not to permit unauthorized security personnel into the armory unsupervised. + 1. The armory doors should not be set to emergency access. + +### The Research Director is: + +1. to keep a log of all anomalies and artifacts. +2. to dispose of any anomalies or artifacts that pose a risk to the station or Nanotrasen assets at a large scale. + 1. The actual disposal may be handed off to a Scientist. +3. permitted to change the onboard artificial intelligence’s laws, permitted they receive approval from the captain. +4. permitted to change any cyborg’s laws, so long as this is done for purposes of experimentation. + 1. Re-lawing a Cyborg is always permitted should they be considered compromised. +5. In conjunction with the Chief Engineer, ensure telecommunications is properly maintained. +6. to decommission the onboard artificial intelligence at the end of the shift, ideally securing it to an Intellicard. +7. to announce the generation of any anomalies to the crew. + +### The Chief Medical Officer is to: + +1. ensure that all personnel capable of being recovered and resuscitated are. + 1. prioritizing personnel based on rank. +2. ensure that all crew who come to the medical bay are treated to the point they can return to work. +3. ensure that no narcotics or otherwise illegal substances are produced in the chemistry laboratory. +4. prevent any dangerous chemical substances or biohazards from being released outside of the chemistry laboratory or virology wing. +5. ensure insurance information is being properly collected and processed. +6. ensure that the medical bay and related facilities are adhering to Nanotrasen Cleanliness Regulations. + +### The Chief Engineer is to: + +1. ensure that the station is maintained by the engineers, prioritizing the repairs of critical areas. +2. mark any areas that are unsafe and too damaged or unsafe to repair as condemned. +3. ensure that all engines powering the station are adequately maintained by the engineers. +4. ensure that distribution air is set to a safe mixture and pressure. +5. ensure that engineers prevent and contain any fires or other hazards that may appear. +6. inspect new constructions to ensure they adhere to the Nanotrasen Building & Expansion Regulation. + +### The Quartermaster is to: + +1. ensure that all approved orders are delivered within fifteen (15) minutes of being approved. +2. deny all requests for security equipment unless the proper requisition form is submitted with the Head of Security’s stamp. +3. ensure that any requests for non-standard equipment are either authorized by the order's Head of Staff or approved by the relevant Head of Staff for the order in question. +4. ensure that materials collected by the salvage team or produced by botany are distributed to departments based on their need for materials. +5. oversee the Hospitality Director to ensure that service is functioning properly. + 1. The Quartermaster should act only as a supervisory body to the service department. + +### The Hospitality Director is: + +1. to ensure the service department runs properly and profitably. +2. to keep all areas of the service department stocked to the necessary levels. +3. to ensure that all available services are provided to the crew as a whole while they are on a union-mandated break. +4. to schedule events strategically to bolster crew morale. +5. permitted to prohibit any non-Command patron from entering the Service area in response to any abusive, inappropriate, and/or unsanitary behaviour. + 1. This prohibition does not cover hallways in or around the area. +6. to ensure that both the Bar and the Kitchen are staffed. In the event that they are not, the Hospitality Director must make an active effort to fill that position, with either service workers or new hires. + 1. Service workers are preferred for staffing internal positions. +7. to review all expenses submitted to them, and deny any that are not cost effective. + +## Adjustments for Acting Command + +Acting Command, while still held to the same SOP as the standard position, are allowed more lenient treatment under most SOP. Acting Command are, however, expected to ensure that the department functions to the proper standards. + +--- + +## 2 | Central Command: + +### NanoTrasen Representative SOP: + +--- + +## 3 | General Crew: + +### Assistants are to: + +1. apply for open positions with the Head of Personnel. + - a. Assistants are not required to take positions that they have no skill in, but they should make an effort to help any short-staffed departments. +2. make themselves available to assist working staff with any unskilled or menial labor. + - a. Assistants answer directly to the Head of Personnel, and should work with them to find tasks throughout the shift. +3. undertake unorthodox business ventures only if they receive express approval and a permit, from the Head of Personnel. + - a. Business ventures should benefit the station in some way, and not undertaken purely for personal profit. + +--- + +## 4 | Security: + +### All Security Staff are to: + +1. Answer directly to the Head of Security and Warden. +2. Enforce the law in accordance with NanoTrasen Corporate Law Protocol. +3. Uphold and maintain NanoTrasen’s authority. +4. Follow the Security Rules of Conduct. + +### The Judicial Officer is to: + +1. Hold court hearings and trials in accordance with NanoTrasen Court Protocol. +2. Ensure that hearings and trials are fast and efficient, but still as thorough as necessary. + - a. The Judicial Officer is to ensure that time and resources are not spent on frivolous cases, and that the type of proceeding is held in accordance with severity and importance. + - b. The Judicial Officer is to ensure that lesser court proceedings do not overly interrupt or impede more important station functions. + +### The Warden is to: + +1. Maintain the safety and security of the brig. +2. Ensure proper treatment of prisoners, in accordance with Corporate Law protocol. +3. Manage and maintain the armory. + - a. The Warden should keep stock of the number and type of weapons within the Armory. + - b. The Warden is responsible for ordering and maintaining material stockpiles for ammunition and weaponry production. + - c. The Warden is responsible for issuing weapons, and ensuring their safe return upon orders on the orders from the Head of Security. +4. Log and update criminal records. +5. Coordinate with the Head of Security to help monitor and direct officers. +6. Avoid performing normal officer duties unless absolutely necessary. + +### The Detective is to: + +1. Focus on gathering evidence for ongoing investigations, or court determinations. +2. Use disguises or alternate IDs only for the sake of investigation, and with permission from the Head of Security. +3. Avoid performing normal officer duties unless absolutely necessary. + +### Security Cadets are to: + +1. Read all of Corporate Law before doing any field work. +2. Request that the Head of Security assigns them a partner for practical training. + +### Lawyers are to: + +--- + +## 5 | Logistics: + +### Cargo Technicians are: + +1. ensure that all approved orders are delivered within fifteen (15) minutes of being approved. + -a. Items produced on station should be delivered in ten (10) minutes. +2. to contact the Quartermaster for approval should there be any requests for security equipment or other departmental equipment. +3. to charge a value in scrip for any requests made from the lathes. + -a. The value charged should not be changed between requests without approval from the Quartermaster. +4. to keep a copy of all order forms are stored inside cargo or with the Quartermaster. +5. to deliver by mail, all packages can be delivered by mail and do not require the signing of a blue slip. +6. to ensure that incoming mail from other departments is sorted and processed. +7. to ensure that at least one person is handling personal mail delivery, should the mail teleporter be turned on. +8. not to order non-essential items using the station's supply account, unless otherwise authorized by the Quartermaster. + +### Salvage Technicians are: + +1. to ensure that all materials and resources collected are transferred to the station's cargo department promptly. +2. to preserve the integrity of the team and prevent losses to fauna and mining accidents. +3. to avoid dangerous areas when identified, unless rescuing a fellow crew member. +4. to coordinate shuttle movements in order to prevent marooning. + -a. There should be an in-person headcount before moving locations. +5. to communicate their team’s GPS coordinates before beginning salvage operations. +6. not permitted to hand over contraband found on expeditions to the crew. +7. to not utilize any contraband found on expeditions while on station. + +### Botanists are: + +1. permitted to grow experimental plants, but may only distribute them with the approval of the Quartermaster. + - a. Poisons may not be created under any circumstances. +2. provide other service department locations with produce on request. + - a. Botanists are not to charge for the produce unless it would be an undue burden to produce. +3. not to allow unregulated plant life outside of botany. + - a. Exceptions may be made by the Quartermaster. + +--- + +## 6 | Engineering: + +### Engineers are to: + +1. ensure the station is maintained to the point where all in use or non-condemned areas are habitable and functional. +2. ensure that the distribution air is a steady mix breathable for a majority of species on the station. + - a. This should be completed within ten (10) minutes of shift start. +3. ensure that power is supplied to the station. + - a. Initial engines should be online within twenty (20) minutes. +4. ensure that all engines that are activated during the shift are either maintained and refueled or properly decommissioned. +5. ensure that one (1) engineering hardsuit is available inside of engineering for use at all times. +6. not create any hazardous environments outside of engineering secured areas. +7. ensure backup power sources are ready for use should there be a need for additional power production. + - a. This does not include the SMES or other battery power. +8. urgently respond to any request for work from command. +9. respond to any reasonable requests for repairs from the crew. + +--- + +## 7 | Medical: + +### Doctors are: + +1. to ensure the proper and effective treatment of all injuries sustained by the crew. + - a. Command members should be treated first, then security officers, then regular crew. +2. to collect payment or insurance information before discharging a patient. +3. required to treat any crew who are admitted to the medical bay. + - a. This excludes any patients who are actively and intentionally self-harming. +4. to treat patients in private rooms unless they have only minor injuries. + - a. Command members should always be admitted to a private room. +5. to place any unrevivable patients into the morgue or a body bag inside of the morgue. + - a. The head of their department should be notified of their passing. + - b. Items from said patients should be returned to their respective departments. + - c. Post mortem instructions should be followed. +6. to keep at least one (1) defibrillator charged and inside of the medical bay at all times. +7. to ensure all clothing they are wearing is clean and sterile. +8. to ensure the medical bay and related facilities, and all equipment in use is clean and sterile, or otherwise in a hygienic state as defined by the Nanotrasen Cleanliness Regulations. +9. not permitted to leave the medical bay if there are patients that need to be treated. + - a. Patients should never be left unattended, even if they are properly treated. + +### Paramedics are to: + +1. prioritize the retrieval of patients based on rank. +2. cooperate with the relevant crew for the retrieval of patients in a dangerous location. + - a. Areas cordoned off by security may be entered if the rescue is located inside of that area. +3. stabilize all patients before transporting them. +4. transport dead patients to the medical bay should revival in the field be impractical. +5. carry requisite medicines and equipment for treatment of patients at all times. + +### Chemists are to: + +1. ensure that the medical bay is stocked with medication to handle Brute, Burn, Airloss/Bloodloss, and Toxin damage. + - a. Chemists are not permitted to exit the medical bay until this is fulfilled. +2. receive approval from the CMO before creating any experimental mixes. +3. not provide the crew with dangerous chemicals outside of bounties. +4. charge for any chemicals handed out to crew that are not related to bounties. +5. report any strange, unusual, or unknown chemicals they create or receive to the CMO. + - a. Such chemicals are not to be distributed. +6. ensure the chemistry laboratory and related facilities, and all equipment in use is clean and sterile, or otherwise in a hygienic state as defined by the Nanotrasen Cleanliness Regulations. + +### Psychologists are: + +1. not permitted to force treatment upon a patient unless it is required as part of a criminal sentence. +2. to not share a patient's mental condition or trusted information to anyone other than the patient. + - a. This does not include evaluations that are made for prisoners. +3. to report to the relevant command member should they find any non-command crew unfit for duty. +4. permitted to prescribe any medicines they find necessary for a patient. + +--- + +## 8 | Science: + +### Scientists are: + +1. not permitted to bring artifacts outside of science without the use of an artifact container. +2. to ensure that every anomaly created is either destroyed or properly contained. + - a. Contained anomalies must be checked whenever there is a change in the vessel's status. + - a. This does not apply if the containment is automated. +3. not to generate anomalies without approval from the research director. +4. to document anomalies and artifacts and submit the documentation to the Research Director. +5. to ensure a member of science personnel (or an assistant hired by science) is manning the front desk. + - a. Whoever is manning the front desk must adhere to the Science Distribution Regulations. + +--- + +## 9 | Service: + +### Service Workers are to: + +1. assist other members of the service department when requested. +2. fill in for other positions in the service department when needed. + - a. Service Workers should follow a positions SOP when acting as that position +3. promote a collaborative atmosphere in the service department. +4. only begin side tasks after checking with other members to see if they require aid. +5. oversee the work of any assistants that are aiding the department. + +### Bartenders are to: + +1. ensure that orders are properly taken and served in a timely manner. + - a. ensure that all beverages are made fresh or stored inside of a dispenser or smart fridge. +2. collect payment or open a tab on all orders before serving the patron. + - a. collect all payments on all tabs open within an hour of that tab opening. +3. not serve potentially dangerous drinks to patrons without a waiver of liability reviewed by a lawyer. +4. keep the bar open during all union-mandated breaks, except for breaks of the service department. +5. not consume any beverages within view of customers while on-duty. +6. ensure the bar complies with the Nanotrasen Health Regulations. + +### The Chef is: + +1. to ensure that orders are properly taken and served in a timely manner. +2. to collect payment on all orders before serving the patron or before they leave the service area. + - a. Discounts may be offered for large orders. +3. to ensure that food for all species on board is available to be produced should it be ordered. +4. to keep the kitchen open during all union-mandated breaks, except for breaks of the service department. +5. not consume any food within view of customers while on-duty. +6. to ensure the kitchen complies with the Nanotrasen Health Regulations. +7. to dispose of food that is not consumed within 15 minutes of it being produced. +8. permitted to produce food using light narcotics as long as they are legal and will not impede the work of the station. +9. permitted to leave the kitchen unattended for the purpose of catering an event. + - a. This is not permitted if the event is during a union-mandated break, unless it is catering for that break. + - a. Payment must be collected for services rendered, along with a catering fee. + - a. a Bartender may be asked to provide drinks for the event, the cost of which should be included in the charge to the customer. +10. to not serve dangerous food to patrons without a waiver of liability reviewed by a lawyer. + +### Janitors are to: + +1. ensure all public parts of the stations are properly maintained according to Nanotrasen Cleanliness Regulations. +2. report any damage to the station to engineers as soon as possible. +3. assist any department with cleaning within 15 minutes of the request being made. + - a. Janirots should ensure that any cleaning made to a department is done in accordance with the relevant regulations. +4. restock any vending machines that are low on supplies or out of a particular item. + - a. The cost of restocks may be taken from the service department’s account. +5. prioritize any possible biohazards over other duties. +6. charge for any cleanings made in private, non-department locations. + + +### The Clown is: + +1. not permitted to remove their Clown Shoes or Clown Mask. + - a. an exception is made should it be truly necessary for the sake of their performance. (such as a satire of bad clowns) +2. to not endanger other personnel with pranks. +3. to attempt to be legitimately funny or entertaining at least once every fifteen (15) minutes. +4. permitted to expense the following to the service department account for pranks or performances: + - a. Special Talent or Hires + - b. Props + - c. Alterations to the stage + +### The Mime is: + +1. to never speak. Any mimes that speak are to be removed from their position post haste. +2. to use written words or AAC tablets only as a last resort or in an emergency. + - a. this includes other non-miming forms of communication. +3. expected to perform an act of Mimery at least once every fifteen (15) minutes. +4. permitted to hire special talent or side performers for plays. +5. permitted to expense the following to the service department account for performances: + - a. Special Talent or Hires + - b. Props + - c. Alterations to the stage From 06179a1a22777bdb566c6bb558aff2b316020de5 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:38:25 -0400 Subject: [PATCH 27/53] Hotfix 1 --- src/design-proposals/station_protocol_rework.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index aea0d112..af60464e 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -1,4 +1,5 @@ + # Station Protocol Rework / Nanotrasen Colonial Law and Procedure | Designers | Implemented | GitHub Links | |---|---|---| @@ -25,24 +26,24 @@ Add a series of books and gudebook entries under the name of Nanotrasen Colonial Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: ### Article 1 - Station Regulations Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more -*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc)* +*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* *[Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. -*[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc)* +*[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-1_design_doc.md)* *[Article 2 - Corporate Law](./station_protocol_rework/Article\ 2\ -\ Corporate\ Law.md)* ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. -*[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc)* +*[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc.md)* *[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article\ 3\ -\ Standard\ Operating\ Procedure.md)* ### Article 4 - Unions -*[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc)* +*[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc.md)* *[Article 4 - Unions](./station_protocol_rework/Article\ 4\ -\ Unions.md)* ### Article 5 - Trials and Hearings -*[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc)* +*[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)* *[Article 5 - Trials and Hearings](./station_protocol_rework/Article\ 5\ -\ Sentencing,\ Trials,\ and\ Hearings.md)* From c6ee60877ffc1c5c2aa2d92c875e6ab6ed5f34a9 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:41:31 -0400 Subject: [PATCH 28/53] Hotfix 2 --- src/design-proposals/station_protocol_rework.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index af60464e..9250c6bf 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -26,10 +26,12 @@ Add a series of books and gudebook entries under the name of Nanotrasen Colonial Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: ### Article 1 - Station Regulations Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more -*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* + +*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* *[Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. + *[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-1_design_doc.md)* *[Article 2 - Corporate Law](./station_protocol_rework/Article\ 2\ -\ Corporate\ Law.md)* ### Article 3 - Standard Operating Procedure From a70b427f5a21ee5ee87b745fc0721193c71fad71 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:42:23 -0400 Subject: [PATCH 29/53] Hotfix 3 --- src/design-proposals/station_protocol_rework.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index 9250c6bf..f688cd21 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -28,24 +28,29 @@ Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more *[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* + *[Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. *[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-1_design_doc.md)* + *[Article 2 - Corporate Law](./station_protocol_rework/Article\ 2\ -\ Corporate\ Law.md)* ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. *[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc.md)* + *[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article\ 3\ -\ Standard\ Operating\ Procedure.md)* ### Article 4 - Unions *[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc.md)* + *[Article 4 - Unions](./station_protocol_rework/Article\ 4\ -\ Unions.md)* ### Article 5 - Trials and Hearings *[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)* + *[Article 5 - Trials and Hearings](./station_protocol_rework/Article\ 5\ -\ Sentencing,\ Trials,\ and\ Hearings.md)* From 43bf2d1dfb272ce97afc3eb7de807291f9f73f14 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:43:47 -0400 Subject: [PATCH 30/53] Hotfix 4 --- src/design-proposals/station_protocol_rework.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index f688cd21..0ad27a8d 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -27,7 +27,7 @@ Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: ### Article 1 - Station Regulations Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more -*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* +*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/Article 1 - Station Regulations.md)* *[Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* ### Article 2 - Corporate law From a65db1be4978ecf7239f6001d603633df8bf1828 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:47:36 -0400 Subject: [PATCH 31/53] Hotfix 5 --- src/design-proposals/station_protocol_rework.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index 0ad27a8d..d973bcf7 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -28,29 +28,24 @@ Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more *[Design Document: Article 1 - Station Regulations](./station_protocol_rework/Article 1 - Station Regulations.md)* - -*[Article 1 - Station Regulations](./station_protocol_rework/Article\ 1\ -\ Station\ Regulations.md)* +*[Article 1 - Station Regulations](./station_protocol_rework/Article 1 - Station Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. -*[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-1_design_doc.md)* - +*[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc.md)* *[Article 2 - Corporate Law](./station_protocol_rework/Article\ 2\ -\ Corporate\ Law.md)* ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. *[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc.md)* - *[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article\ 3\ -\ Standard\ Operating\ Procedure.md)* ### Article 4 - Unions *[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc.md)* - *[Article 4 - Unions](./station_protocol_rework/Article\ 4\ -\ Unions.md)* ### Article 5 - Trials and Hearings *[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)* - *[Article 5 - Trials and Hearings](./station_protocol_rework/Article\ 5\ -\ Sentencing,\ Trials,\ and\ Hearings.md)* From 69d00485d473c7fcc6f14f44393baeaa84c5fa0f Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:49:11 -0400 Subject: [PATCH 32/53] Hotfix 6 --- src/design-proposals/station_protocol_rework.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index d973bcf7..e4711d33 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -27,7 +27,7 @@ Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: ### Article 1 - Station Regulations Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more -*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/Article 1 - Station Regulations.md)* +*[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* *[Article 1 - Station Regulations](./station_protocol_rework/Article 1 - Station Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. From e85457bb8180fb08c465e5105d425bf1c175f7db Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 20:51:29 -0400 Subject: [PATCH 33/53] Hotfix 7 --- src/design-proposals/station_protocol_rework.md | 7 +------ .../station_protocol_rework/article-3_design_doc.md | 7 +------ 2 files changed, 2 insertions(+), 12 deletions(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index e4711d33..2ba7f2e8 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -28,25 +28,20 @@ Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more *[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* -*[Article 1 - Station Regulations](./station_protocol_rework/Article 1 - Station Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. *[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc.md)* -*[Article 2 - Corporate Law](./station_protocol_rework/Article\ 2\ -\ Corporate\ Law.md)* ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. -*[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc.md)* -*[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article\ 3\ -\ Standard\ Operating\ Procedure.md)* +*[Design Document: Article 3 - Standard Operating Procedure](./station_protocol_rework/article-3_design_doc.md)* ### Article 4 - Unions *[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc.md)* -*[Article 4 - Unions](./station_protocol_rework/Article\ 4\ -\ Unions.md)* ### Article 5 - Trials and Hearings *[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)* -*[Article 5 - Trials and Hearings](./station_protocol_rework/Article\ 5\ -\ Sentencing,\ Trials,\ and\ Hearings.md)* ### Extra considerations diff --git a/src/design-proposals/station_protocol_rework/article-3_design_doc.md b/src/design-proposals/station_protocol_rework/article-3_design_doc.md index 9d034758..ed17261a 100644 --- a/src/design-proposals/station_protocol_rework/article-3_design_doc.md +++ b/src/design-proposals/station_protocol_rework/article-3_design_doc.md @@ -16,12 +16,7 @@ This doc will cover the Standard Operating Procedures Section of the new Nanotra This section of the Nanotrasen Colonial Law and Procedures (I'll refer to it at NCLP from now on) is designed to rework SOP to fit better with the new vision of the game post-forky. Current SOP tends towards being very oddly written, very inconsistent, and is not aligned with the new vision for the game. SOP also has a bad habit of simply being server rules, which is very counteractive to the point of SOP, which is to cause conflict. SOP that is also a rule, and thus cannot be broken, should be avoided at all costs. There has also been a focus on making command further from the regular crew, to play further into our theme of class conflict. ## Features to be added -There are many things planned to be changed in SOP so I will give each their own section. A large part of the SOP has already been drafted. This section will cover the proposed changes and use examples from that draft. If you would like to see the draft, check the related drafts of the document: -[Article 1 - Station Regulations](./Article\ 1\ -\ Station\ Regulations.md) -[Article 2 - Corporate Law](./Article\ 2\ -\ Corporate\ law.md) - -[Article 4- Unions](./Article\ 1\ -\ Unions.md) -[Article 5 - Sentencing, Trials, and Hearings](./Article\ 5\ -\ Sentencing,\ Trials,\ and\ Hearings.md) +There are many things planned to be changed in SOP so I will give each their own section. A large part of the SOP has already been drafted. This section will cover the proposed changes and use examples from that draft. If you would like to see the draft, check the related drafts of the document under `station_protocol_rework`. ### SOP Requirements These are guidelines for drafting the SOP that cover how we expect SOP to be written, and things to be included. From 30feede9fb1e1ccf84789f83c53980b1ad73bf6d Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 21:06:03 -0400 Subject: [PATCH 34/53] Hotfix 8 --- src/design-proposals/station_protocol_rework.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index 2ba7f2e8..f6c5a088 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -1,5 +1,6 @@ + # Station Protocol Rework / Nanotrasen Colonial Law and Procedure | Designers | Implemented | GitHub Links | |---|---|---| @@ -28,20 +29,25 @@ Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more *[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* +*[Article 1 - Station Regulations](./station_protocol_rework/Article%201%20-%20Station Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. *[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc.md)* +*[Article 2 - Corporate Law](./station_protocol_rework/Article%202%20-%20Corporate%20Law.md)* ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. -*[Design Document: Article 3 - Standard Operating Procedure](./station_protocol_rework/article-3_design_doc.md)* +*[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc.md)* +*[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article%203%20-%20Standard%20Operating%20Procedure.md)* ### Article 4 - Unions *[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc.md)* +*[Article 4 - Unions](./station_protocol_rework/Article%204%20-%20Unions.md)* ### Article 5 - Trials and Hearings *[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)* +*[Article 5 - Trials and Hearings](./station_protocol_rework/Article%205%20-%20Sentencing,%20Trials,%20and%20Hearings.md)* ### Extra considerations From 3e59d7a6baadabd31a324a821aa29597d7ddf5e8 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 21:08:12 -0400 Subject: [PATCH 35/53] Hotfix 9 --- src/design-proposals/station_protocol_rework.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index f6c5a088..830036e9 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -1,6 +1,7 @@ + # Station Protocol Rework / Nanotrasen Colonial Law and Procedure | Designers | Implemented | GitHub Links | |---|---|---| @@ -29,24 +30,29 @@ Nanotrasen Colonial Law and Procedure is split into 5 parts, called articles: Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Promotions and more *[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* -*[Article 1 - Station Regulations](./station_protocol_rework/Article%201%20-%20Station Regulations.md)* + +*[Article 1 - Station Regulations](./station_protocol_rework/Article%201%20-%20Station%20Regulations.md)* ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. *[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc.md)* + *[Article 2 - Corporate Law](./station_protocol_rework/Article%202%20-%20Corporate%20Law.md)* ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. *[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc.md)* + *[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article%203%20-%20Standard%20Operating%20Procedure.md)* ### Article 4 - Unions *[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc.md)* + *[Article 4 - Unions](./station_protocol_rework/Article%204%20-%20Unions.md)* ### Article 5 - Trials and Hearings *[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)* + *[Article 5 - Trials and Hearings](./station_protocol_rework/Article%205%20-%20Sentencing,%20Trials,%20and%20Hearings.md)* From 5c204b88fbf52fabb50e700347602a756666a664 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 7 May 2026 21:10:28 -0400 Subject: [PATCH 36/53] Hotfix 10 --- src/design-proposals/station_protocol_rework.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index 830036e9..40ff9c8f 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -37,7 +37,7 @@ To better realize the idea of NT's opression, Space Law has been re-written, exp *[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc.md)* -*[Article 2 - Corporate Law](./station_protocol_rework/Article%202%20-%20Corporate%20Law.md)* +*[Article 2 - Corporate Law](./station_protocol_rework/Article%202%20-%20Corporate%20law.md)* ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. From 30c0a31888adde129015a57b9219e686f989995a Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Thu, 7 May 2026 22:34:39 -0300 Subject: [PATCH 37/53] Added more atributions to main doc --- src/design-proposals/station_protocol_rework.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/station_protocol_rework.md index 40ff9c8f..830544fb 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/station_protocol_rework.md @@ -5,10 +5,10 @@ # Station Protocol Rework / Nanotrasen Colonial Law and Procedure | Designers | Implemented | GitHub Links | |---|---|---| -| SOP Workgroup | :x: | TBD | +| SOP Workgroup | :x: No | TBD | Leader: Catty -Members: Joaco545, Alicios, Scrambledking, Gamercodeleo1/funkycmm, Goobie (and many other that I need to read chat to get) +Members: Alicios, Catz, Dusty\_Plant, Fish Chief-cap, Gamercodeleo1, Goobie, IdemFromidemland, Joaco545, Scrambledking Many thanks to the Admin team and Tay for pitching in ## Overview From 00662f20f5b56b54399ba9cb6fce9247449b8698 Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Fri, 8 May 2026 11:31:08 -0300 Subject: [PATCH 38/53] Renamed main doc and supporting folder Touched up the hedears of each doc to be consistant --- .../Article 1 - Station Regulations.md | 0 .../Article 2 - Corporate law.md | 0 .../Article 3 - Standard Operating Procedure.md | 0 .../Article 4 - Unions.md | 0 ...icle 5 - Sentencing, Trials, and Hearings.md | 0 .../article-1_design_doc.md | 6 ++---- .../article-2_design_doc.md | 2 +- .../article-3_design_doc.md | 8 ++------ .../article-4_design_doc.md | 15 ++------------- .../article-5_design_doc.md | 2 +- ...=> nanotrasen_colonial_law_and_procedure.md} | 17 +++++++++++------ 11 files changed, 19 insertions(+), 31 deletions(-) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/Article 1 - Station Regulations.md (100%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/Article 2 - Corporate law.md (100%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/Article 3 - Standard Operating Procedure.md (100%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/Article 4 - Unions.md (100%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/Article 5 - Sentencing, Trials, and Hearings.md (100%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/article-1_design_doc.md (98%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/article-2_design_doc.md (99%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/article-3_design_doc.md (99%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/article-4_design_doc.md (75%) rename src/design-proposals/{station_protocol_rework => nanotrasen-colonial-law-and-procedure}/article-5_design_doc.md (98%) rename src/design-proposals/{station_protocol_rework.md => nanotrasen_colonial_law_and_procedure.md} (97%) diff --git a/src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md similarity index 100% rename from src/design-proposals/station_protocol_rework/Article 1 - Station Regulations.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md diff --git a/src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 2 - Corporate law.md similarity index 100% rename from src/design-proposals/station_protocol_rework/Article 2 - Corporate law.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 2 - Corporate law.md diff --git a/src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md similarity index 100% rename from src/design-proposals/station_protocol_rework/Article 3 - Standard Operating Procedure.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md diff --git a/src/design-proposals/station_protocol_rework/Article 4 - Unions.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 4 - Unions.md similarity index 100% rename from src/design-proposals/station_protocol_rework/Article 4 - Unions.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 4 - Unions.md diff --git a/src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 5 - Sentencing, Trials, and Hearings.md similarity index 100% rename from src/design-proposals/station_protocol_rework/Article 5 - Sentencing, Trials, and Hearings.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 5 - Sentencing, Trials, and Hearings.md diff --git a/src/design-proposals/station_protocol_rework/article-1_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-1_design_doc.md similarity index 98% rename from src/design-proposals/station_protocol_rework/article-1_design_doc.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/article-1_design_doc.md index 3e3cf3c9..2604face 100644 --- a/src/design-proposals/station_protocol_rework/article-1_design_doc.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-1_design_doc.md @@ -1,10 +1,8 @@ -# Station Regulations - -Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. +# Nanotrasen Colonial Law and Procedure: Station Regulations | Designers | Implemented | GitHub Links | |---|---|---| -| SOP workgroup, Written by Scrambleking | :x: No | TBD | +| SOP workgroup, Document written by Scrambleking | :x: No | TBD | ## Overview diff --git a/src/design-proposals/station_protocol_rework/article-2_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-2_design_doc.md similarity index 99% rename from src/design-proposals/station_protocol_rework/article-2_design_doc.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/article-2_design_doc.md index 6cd22623..fbf759eb 100644 --- a/src/design-proposals/station_protocol_rework/article-2_design_doc.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-2_design_doc.md @@ -2,7 +2,7 @@ | Designers | Implemented | GitHub Links | |---|---|---| -| SOP Workgroup, Design Doc written by Joaco545 | :x: No | TBD | +| SOP Workgroup, Document written by Joaco545 | :x: No | TBD | ## Overview diff --git a/src/design-proposals/station_protocol_rework/article-3_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-3_design_doc.md similarity index 99% rename from src/design-proposals/station_protocol_rework/article-3_design_doc.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/article-3_design_doc.md index ed17261a..21787b86 100644 --- a/src/design-proposals/station_protocol_rework/article-3_design_doc.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-3_design_doc.md @@ -1,12 +1,8 @@ - - - - -# Nanotrasen Colonial Law and Procedures, Article 3: Standard Operating Procedure +# Nanotrasen Colonial Law and Procedures: Standard Operating Procedure | Designers | Implemented | GitHub Links | |---|---|---| -| SOP Workgroup, Authored by Gamercodeleo1 |:x: No | TBD | +| SOP Workgroup, Document written by Gamercodeleo1 |:x: No | TBD | ## Overview diff --git a/src/design-proposals/station_protocol_rework/article-4_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-4_design_doc.md similarity index 75% rename from src/design-proposals/station_protocol_rework/article-4_design_doc.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/article-4_design_doc.md index 571655af..d87c2314 100644 --- a/src/design-proposals/station_protocol_rework/article-4_design_doc.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-4_design_doc.md @@ -1,19 +1,8 @@ -# Short, Properly Capitalized Title - -Your title should convey the basic jist of your proposed changes. It should be short because the text will be linked in the sidebar. +# Nanotrasen Colonial Law and Procedure: Unions | Designers | Implemented | GitHub Links | |---|---|---| -| Your Names Here | :white_check_mark: Yes or :warning: Partially or :information_source: Open PR or :x: No | PR Links or TBD | - -`Designers` should be the names that you use on GitHub and/or Discord. This is optional but strongly recommended, since: - -- This acknowledges credit where it is due -- People who are confused about the written intent can use this information to contact the authors - -`Implemented` is the status of the feature. - -Github links can include multiple PRs, if relevant. +| SOP Workgroup | :x: No | TBD | ## Overview diff --git a/src/design-proposals/station_protocol_rework/article-5_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-5_design_doc.md similarity index 98% rename from src/design-proposals/station_protocol_rework/article-5_design_doc.md rename to src/design-proposals/nanotrasen-colonial-law-and-procedure/article-5_design_doc.md index 5b86983d..91954a1c 100644 --- a/src/design-proposals/station_protocol_rework/article-5_design_doc.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-5_design_doc.md @@ -2,7 +2,7 @@ | Designers | Implemented | GitHub Links | |---|---|---| -| Alicios + SOP Workgroup | :warning: Partially | https://github.com/Joaco545/Funky-Station-Docs/blob/6ddabb8d534ab87adc98eefe31af0f1ae2e789a5/src/design-proposals/station_protocol_rework/Article%205%20-%20Sentencing%2C%20Trials%2C%20and%20Hearings.md | +| SOP Workgroup, Document written by Alicios| :x: No | TBD | ## Overview diff --git a/src/design-proposals/station_protocol_rework.md b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md similarity index 97% rename from src/design-proposals/station_protocol_rework.md rename to src/design-proposals/nanotrasen_colonial_law_and_procedure.md index 830544fb..c80c1334 100644 --- a/src/design-proposals/station_protocol_rework.md +++ b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md @@ -1,26 +1,25 @@ +# Nanotrasen Colonial Law and Procedure - - - -# Station Protocol Rework / Nanotrasen Colonial Law and Procedure | Designers | Implemented | GitHub Links | |---|---|---| | SOP Workgroup | :x: No | TBD | Leader: Catty Members: Alicios, Catz, Dusty\_Plant, Fish Chief-cap, Gamercodeleo1, Goobie, IdemFromidemland, Joaco545, Scrambledking -Many thanks to the Admin team and Tay for pitching in +Many thanks to Tay, the Admin team, and members of the discord for pitching in ## Overview A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". + ## Background Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. + ## Features to be added Add a series of books and gudebook entries under the name of Nanotrasen Colonial Law and Procedure @@ -32,35 +31,39 @@ Covers general station behaviour: Alert levels, Permits, Paperwork, Hiring, Prom *[Design Document: Article 1 - Station Regulations](./station_protocol_rework/article-1_design_doc.md)* *[Article 1 - Station Regulations](./station_protocol_rework/Article%201%20-%20Station%20Regulations.md)* + ### Article 2 - Corporate law To better realize the idea of NT's opression, Space Law has been re-written, expanded, and rebranded as Corporate Law. *[Design Document: Article 2 - Corporate Law](./station_protocol_rework/article-2_design_doc.md)* *[Article 2 - Corporate Law](./station_protocol_rework/Article%202%20-%20Corporate%20law.md)* + ### Article 3 - Standard Operating Procedure SOP has to be overhauled to better fit the themes and expectations of Funky Station. All SOP is to receive a rewrite and new guiding principals. *[Design Document: Article 3 - Standard Operating Prodedure](./station_protocol_rework/article-3_design_doc.md)* *[Article 3 - Standard Operating Procedure](./station_protocol_rework/Article%203%20-%20Standard%20Operating%20Procedure.md)* + ### Article 4 - Unions *[Design Document: Article 4 - Unions](./station_protocol_rework/article-4_design_doc.md)* *[Article 4 - Unions](./station_protocol_rework/Article%204%20-%20Unions.md)* + ### Article 5 - Trials and Hearings *[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)* *[Article 5 - Trials and Hearings](./station_protocol_rework/Article%205%20-%20Sentencing,%20Trials,%20and%20Hearings.md)* - ### Extra considerations "Behavior follows incentives" While this PR focuses only on the regulations themselves, many supporting changes will need to be done to mechanically enforce the new vision Funky Station has. The SOP workgroup is working on other design docs that should help change that situation and align mechanics with the text and intent behind them. + ## Game Design Rationale Consider addressing: @@ -77,12 +80,14 @@ Take things slow (point at trials) Maximixing RP Potential is all over the place in this doc Dynamic Environment respected, as it all depends on where players want to take this + ## Roundflow & Player interaction All of the changes done here will affect every shift. The players will have to interact with all the changes proposed here as SOP, Corporate Law, Trials, and Unions will permiate every round on Forky. While how much each individual part affects each round varies, it all depends on the players roleplaying to see the direction the round will take. Mechanically speaking Sec, IAAs, and Department Heads will be the ones enforcing the changes proposed here, as they have the power to enact IC punishment on the people who break SOP or Corpo Law. + ## Administrative & Server Rule Impact (if applicable) We expect the workload for the admins to increase for a bit while the players get used to the new changes, but it should go back to baseload after that From 75da28618d9f0a18b74b09718c12dee28b14a922 Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Fri, 8 May 2026 11:55:54 -0300 Subject: [PATCH 39/53] Added a mention to Goobies "Logistics & Service Restructuring" side doc o the main doc --- src/design-proposals/nanotrasen_colonial_law_and_procedure.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md index c80c1334..2dba6d67 100644 --- a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md +++ b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md @@ -63,6 +63,7 @@ SOP has to be overhauled to better fit the themes and expectations of Funky Stat While this PR focuses only on the regulations themselves, many supporting changes will need to be done to mechanically enforce the new vision Funky Station has. The SOP workgroup is working on other design docs that should help change that situation and align mechanics with the text and intent behind them. +[Logistics & Service Restructuring](https://github.com/funky-station/docs/pull/96) ## Game Design Rationale From d7caa976651e20282dba16efad22b91968bd708b Mon Sep 17 00:00:00 2001 From: Alicios Date: Fri, 8 May 2026 12:01:51 -0700 Subject: [PATCH 40/53] Article 5 Legal revision --- .../.article-5_design_doc.md.kate-swp | Bin 0 -> 24469 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/.article-5_design_doc.md.kate-swp diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/.article-5_design_doc.md.kate-swp b/src/design-proposals/nanotrasen-colonial-law-and-procedure/.article-5_design_doc.md.kate-swp new file mode 100644 index 0000000000000000000000000000000000000000..f2a6d73d1b196fd007c218f937fadcc0b29ea13b GIT binary patch literal 24469 zcmeI2cd*}8mB90*C$tcHf25EELV(aAKq@5!0!ipCp_kCRAfN(@3J8jT^bS%4RP2hq zVwVnnuNKK!e_=UsgBygkdx2IXt@^3@H@ ze3jRLH%?x&x4srUJJ;8Sk4;_&K0bL}cwzE-@S^1PVd=-FZbq(e2uuC|e0r{L1WW!% z_{>}%1)rTf8a^d?3@rH@!>8u@*n0lJ^7pv%HDqvUJpU|zx>3npkC*82l09AuuC60* zX}E?KUIwnF!OOxmwD59pbsZiG*U-YlV98$|uAyap1z7S|gllM7UkR4{mEjs%)`!D2 zwD2l$4J|wZmi$%W8d}y@gX{TC%fC;6i@kHp-;Gb4IgiK(4*qjO!J354_-Fak%^yqx z97#AKIg(I~U_Fvhg91kqYS7_Gg7!xeYS3AaB-Eh5k%Ss_cxd@*PBb1i=u_K1G!bdb zC8BKEL~L0m5mT2=#FM2GadgQ<;;=+wp&?yHC2(qTL`_kNsGXea5j906qIN;9N7Qsa zqIOKKN7QsaqIOoUN7PEL_bi4HrYK!SJxaHh4(n06(zjyyzfSt1bfqs!SMsBDk4}A2 zx@DcxLq0qrk?pG_B5imc4&f3O!lf*P%h~7)tw&#+mhz%6)MZl?w^KN6PyQN8uiu;h(_ z<=@7z&X0xF!sB}Txog_Ji9MUZYGE#yc5kxI4P*KIU%NN?_e5CsY!26Zll3iN$=?!I zJ|@A6$5wE?H#xsGEcx5Os)udia=sNSyj>#Ox6Nvb)6y2F6}|0{rtEJIEBiaZ+P@<# zYj%QFy^~?-+ZopRUEq__zFpySlBdAZKNXg|X>gI(yoaYJvVB_Ol!E1+YnxFvB@tV8 zP1RwVREKGD4Ph>nFinXH(=-dFvtPI53|OI<2_KjGcY~#GcUTw89=gQf3qSl%B2%ljjH`xn5nZy~I z!K%H}VVyq%E`8g)JrhE_)u69oERW7?$^!^!8s0%bRz=x)k3Dt2W;SE83UA^8RvI@~(i@ zJMV^d{yngwdnK&ed~a|6`(S0~{jmJI3O*y_cXd7Aq77e@(PsPAxjRnF+IG4{`x>Ol zyAM?9ZT(tU_vm%-Q7Qj}u)O^cENidto&Rue{|&IRb7Ng^-oZDex>#0lZeqL4`v|OH z-wZ1`x4^pCZiOZ9Hdx8Hy|@1kSjBTEtm3>2mOFRD6Vm>BVA*qTZ~uL;-gEcE()R$Y z^AEzaQ~pQcnaK~q`f%_ttaLvDmtt?>h96C2`y+`+dpHqg52dcqEn8o&?pA7#7IF6N zWAKcW{}?R!kHd=n6R>>yIIN506R>jgNmy^mCt=C|6s%hKbUoi3i( ziuAU7amx}OeYRO{hp$U%v8=pbhb{6o+OXuY#WLDZ9BnA^wBZf8J-Sk^M_0eQaF z*EN1;XRyxf$&2x;D>lZjauwrO&Y#P9)n$xd1^;~3bw0+gav9@S@?!i-UJOtLCkCkG z#{eyNW(yX4NxB!yQWx`8FY`-#=EZ!~6&&+bxr+I!T*iFWOFrhS)?>cP+?cO=9mRZA zc&@}Ag+J!26?;|BpO}!U?U<1AFB)6nUTkZs_Mf#{4zmt=D6|Di|?eWqiz671LtptCH~`&MMe3y`8=#a@da4+eGyhMe+ibpr(oIpWmxg}3at2j6;?dH1}mOlhjsoNus+&-6PA77 zf@R;gVafXrEP3CBrT=?yk=KeHemcuJmSz6aY?rw2!wTOIV2S@BEOUPZs~mp}%iN#9 zlK)d!<^3~Q=bwS4?^#&(JO?XX&-eHRSm}Ea)?NG(EdO7IbyvIsEBrr)W&bZ=wc{^g z$@>*7{r>>#{6E5y|7%$B_zkSP3jS?olkLArMB1-2xglJ}g>dy^2v;xv7G*N-cd&x> zdsxo>0akMV2rC(Xf|bla!^OE)i|}6(+5YE5r2Q!oWq(Y>mOmt7>hBZr734BkA~4~M5G9|6mpBYWo;z`79@!V1Sxu!`_#Smwc{L7TN~ zFVY$!txTha3ks?mv1LK7V(O8JcydHK5{}JF4##9@I3`CHl;gfy!!bD$jwx^9nDTxM z=gTv>+0NgGCGJ;nZdwES5yftYaUQITaXzf7+8TcsJx z_8Zf>IISXx(~=fX&LXW9RXjOmZ9F-({}!y3yjx+7vD;u>!?(j@Q~n*Wdf-ktZ_aMH z9uI}{RnrZFQ(w0{oVn{(=$&5?&S-Zl!5QstWjO8WhQsM!w+bx#M)cNKg|o-I)$0D5 z4!B$W)$DX-d$(F*k=Cu6Sd?`m5{oTe{`?hFyWzQ7Jn2?WERJ?7y&C5({FWc#x9kkR zL@2ztOPHkAW4hjp2OGbYo$i9|!CF_}>0a z;QTbwZ3^cd)=hw=kJ;h%iLmN?b69<|1*~{%3Co^Iz5QFk(!Vu)Zq{E6E9GZf*5&VZ zu;Q^jtbFeP%f209>DvjG{K;_fuk~HwZs)|Zy_=j^q;)$b7G>RziN%&~hs0uPw|!#q zq}wjBINFt;J2$;04&641B~0Dci6x5NR*5CZ-K4~lgKo>jlA>;l#F9a#eN$8t%#YO? zmi%{{C6@BwWzkkk^>mvimg4F*Ni4P3jZZA4*^NsqmCFU*M3utk7v&n3y6?s$mbU0d zCzh_^SH;@q(p25Z#DRhvC6<nE1$pj$7o+!o!siRCis z)=4aPO}BQIYFs@k^|*RensN20_2TMLDaO^K){CpBtT#vAe9N2Ua*1|prJ{1jc55b< zE4W)D@lBXS?Xr$xp@_wh)a5>+He=f#!$QL-hJ`MJ7#3QOVWEgFc34RNo0YLMA!!m}2uf2+%SuQl^yS>c$3xe7BKKpKs9a)} zNPWx_l}pSLHE_A!hj{kHERj2loh5n;?c59RF0jgdS6KE;f#vU1Smiwpmj3Cm-WD@p z-GqhtL12q++0M_>8Ww4M>T6h(b<+~36r7q^Ozoy57EikJn?UVsakSed@paA6mgESk zk`O_a(?ys+J$7$gxFYuVnz0s)nK-Ko+znQP?GCF#_JGw9$nooD7OV?tFL>hMZwB)a zm_7JU`gX|RwL#1Br~Q&}v@l$MJOD2N*J}Y@60Us)F9nyv!y0&L`26H$V4YtUu6@k@ z_$*hwhKI6Vy@rRu)oXZpxL%8Je3p~^6kE5UQpo|WPH9c|9Xm=edBlD-k_m%TBj zq%X!)tvckzn3Db&Q}vTN>oKNk$;0umkpD5J>b=2wJS=LJ!11t<{CHT@tg{{u3&k(S zl>CV?CHVv8OuMHzA7iS>r`;RZ=NLG^mRv=eHlwUQ$C@qmIR;{CeU5>6Ql4Y2a2D%W z30yOzo^IRUD!-fj7|(TlVr`6Pd};Gx*KJ{`i2bVjqt^k{@p#)hk>-@^GB(^&?M{Ha^3SvigyS)&DyQeG6`fRxp24 zm*{qiglgJELY44Hs0uC;s)CAy>h_ICtO_6=vGrpaNsC9U3NRkAI?tZ=%HrSgh?V|$ zrRw}7_UrbJSE~GrSE~GrSE_FRc%@2zyi#R!k^ITnrv`{u zs`i(+-K(!sv#M5{ttZBL%toZB>E57mOk^R(N z`#w4L&Vpr6ym@5LY}O~_kl7oS|NFr8=flXG11o;}!nzRmgLR(U-S*FemB0D0^1FX; z{Qy}09SGM?71(nSEPoD$<^T%xe;fuYK8M4y=LlH+aU?AJ7r?5&g|PG;1?xgS z8kYQHVCC~zSX1&iSn`jDrT+w2@i`Gzd`^NDkCWkIUz@scdF(V~d;O^h(M4KGep^LZ z(cKVRN@+I4)S|f|o)kwK;%JF;L*h`v(vUEfs&7aXOHnmkP_V?PAvsu(NQ&x@y|9@K zmLGey%_R8nMDkyL3Pqc+Im$udk8)5rqa2jJCQu-DJ=iuC8YE564L&73Dwp^Kjm-x_`mj> zY5Y50Lh^SK>xxIbgw!AL5|Y315~^1V^5P{Vd*US|`{N~~dW@Hl;u9|+?cWJ|>Q#jN z$*}C*8CE=YfmMII!m@V?toTfYW$!dt{!E8eZ!=)oHxpL8c7tW_?y%(V0n1+c+UIA% z(zh3^`iqy4{E3&4_Qy-8zGR8l9L~$%ePP8fUP7{;f#m*(myqS=UaJSWd?fmGl^*waHnJAzA|q4=-P>$>A8HIzNK-l9;*W zZ`R>e6WKl@t&7vLuAOey#R!&mk6@(72(BXyjuEW=F@j~?T4hhWg4iD;xV9|p5e$0- z!!d#-KSppZbJk-7*OrH41k1jG@_+40WIaZ3y>j6g!Lm0-u(A;&SnDx@WlxM?#WO~5 zy+V)=kIV4469ML{O$`1W6I$|PLf7xCvmO&#;fM*X^u&Z#`nN}Zogkc#2`&3#LQ7vvXvvQW zE&pOdOJ7WA#WyB&{mwf2rl4QzF`?`CN?4!9y5z-#uD34hp3rbiXqBfYH0!&UFUyMw zJw5A#x@f;@$^Mwo2jqH8=slBXv%gL-_Q!-)JYqsm$o(;)1v(}EB-N| z>l8s>Ola+o2`%|Cp%vel&}y%klFDaHXq}GHK9RGXb@#(LeDLKf!K0T zBBmagh$kiRZ8MJUpGX|$C$ei^B2k>1NRanSBnKsBO)@DeZ<2;&aGyjHymun`FO#rs zrabmaq zSgm_1EP1EF3eV}VuHG|X$v+d8zh}Wp&)Kl#ode6Cb9?LO!P0j=toU63OaI$o`EwyG z{TIQC&)Z?0zZllldtjIe9%Se?AOL-wm+j-w4aUn_v~sM_?uQW?1rXfhGS|Sn_X! z6_49t`FjT}|L%m9-@9PV^}Auk`yN>NxEGfG`(T~FA6EPxfc1`ju*V;TrSBnF@p%|l zd>(AijtoryGEc?C=s~*15<8Q*Mzi+{^ z_uH`I{~cKVeixR%--G4f)3Dz4On*^7jQ;`d{qrf2p_sWw^wrUGDHJiEMv45os?aqU^;)Y*wC%dtI++DYZ>mGb4l{2VT?_O|{Dcuw*!;fZhEPh-mS8r55rucc8{ zYZzVzt~CoU3)j%V%fYqB;GwvC>&wHn$KVy4;SFK=GXU%SMsV$6_K$??%z{V3b>_pPVaXcijF7f9MLN>f@BHOn~MB3Jg zDBCJ~DRj%X(5>DI-LfTg%a(16IM>2S1^d9NvN^D-YF}9L_k(rgkYHEIJh;BH$<};W^7n^Tl?TA8vIF6<>Hk5n zs`Ox3{u~0!o Date: Fri, 8 May 2026 12:06:25 -0700 Subject: [PATCH 41/53] Legal Department Clarifications --- .../.article-5_design_doc.md.kate-swp | Bin 24469 -> 0 bytes .../article-5_design_doc.md | 10 +++++++++- 2 files changed, 9 insertions(+), 1 deletion(-) delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/.article-5_design_doc.md.kate-swp diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/.article-5_design_doc.md.kate-swp b/src/design-proposals/nanotrasen-colonial-law-and-procedure/.article-5_design_doc.md.kate-swp deleted file mode 100644 index f2a6d73d1b196fd007c218f937fadcc0b29ea13b..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 24469 zcmeI2cd*}8mB90*C$tcHf25EELV(aAKq@5!0!ipCp_kCRAfN(@3J8jT^bS%4RP2hq zVwVnnuNKK!e_=UsgBygkdx2IXt@^3@H@ ze3jRLH%?x&x4srUJJ;8Sk4;_&K0bL}cwzE-@S^1PVd=-FZbq(e2uuC|e0r{L1WW!% z_{>}%1)rTf8a^d?3@rH@!>8u@*n0lJ^7pv%HDqvUJpU|zx>3npkC*82l09AuuC60* zX}E?KUIwnF!OOxmwD59pbsZiG*U-YlV98$|uAyap1z7S|gllM7UkR4{mEjs%)`!D2 zwD2l$4J|wZmi$%W8d}y@gX{TC%fC;6i@kHp-;Gb4IgiK(4*qjO!J354_-Fak%^yqx z97#AKIg(I~U_Fvhg91kqYS7_Gg7!xeYS3AaB-Eh5k%Ss_cxd@*PBb1i=u_K1G!bdb zC8BKEL~L0m5mT2=#FM2GadgQ<;;=+wp&?yHC2(qTL`_kNsGXea5j906qIN;9N7Qsa zqIOKKN7QsaqIOoUN7PEL_bi4HrYK!SJxaHh4(n06(zjyyzfSt1bfqs!SMsBDk4}A2 zx@DcxLq0qrk?pG_B5imc4&f3O!lf*P%h~7)tw&#+mhz%6)MZl?w^KN6PyQN8uiu;h(_ z<=@7z&X0xF!sB}Txog_Ji9MUZYGE#yc5kxI4P*KIU%NN?_e5CsY!26Zll3iN$=?!I zJ|@A6$5wE?H#xsGEcx5Os)udia=sNSyj>#Ox6Nvb)6y2F6}|0{rtEJIEBiaZ+P@<# zYj%QFy^~?-+ZopRUEq__zFpySlBdAZKNXg|X>gI(yoaYJvVB_Ol!E1+YnxFvB@tV8 zP1RwVREKGD4Ph>nFinXH(=-dFvtPI53|OI<2_KjGcY~#GcUTw89=gQf3qSl%B2%ljjH`xn5nZy~I z!K%H}VVyq%E`8g)JrhE_)u69oERW7?$^!^!8s0%bRz=x)k3Dt2W;SE83UA^8RvI@~(i@ zJMV^d{yngwdnK&ed~a|6`(S0~{jmJI3O*y_cXd7Aq77e@(PsPAxjRnF+IG4{`x>Ol zyAM?9ZT(tU_vm%-Q7Qj}u)O^cENidto&Rue{|&IRb7Ng^-oZDex>#0lZeqL4`v|OH z-wZ1`x4^pCZiOZ9Hdx8Hy|@1kSjBTEtm3>2mOFRD6Vm>BVA*qTZ~uL;-gEcE()R$Y z^AEzaQ~pQcnaK~q`f%_ttaLvDmtt?>h96C2`y+`+dpHqg52dcqEn8o&?pA7#7IF6N zWAKcW{}?R!kHd=n6R>>yIIN506R>jgNmy^mCt=C|6s%hKbUoi3i( ziuAU7amx}OeYRO{hp$U%v8=pbhb{6o+OXuY#WLDZ9BnA^wBZf8J-Sk^M_0eQaF z*EN1;XRyxf$&2x;D>lZjauwrO&Y#P9)n$xd1^;~3bw0+gav9@S@?!i-UJOtLCkCkG z#{eyNW(yX4NxB!yQWx`8FY`-#=EZ!~6&&+bxr+I!T*iFWOFrhS)?>cP+?cO=9mRZA zc&@}Ag+J!26?;|BpO}!U?U<1AFB)6nUTkZs_Mf#{4zmt=D6|Di|?eWqiz671LtptCH~`&MMe3y`8=#a@da4+eGyhMe+ibpr(oIpWmxg}3at2j6;?dH1}mOlhjsoNus+&-6PA77 zf@R;gVafXrEP3CBrT=?yk=KeHemcuJmSz6aY?rw2!wTOIV2S@BEOUPZs~mp}%iN#9 zlK)d!<^3~Q=bwS4?^#&(JO?XX&-eHRSm}Ea)?NG(EdO7IbyvIsEBrr)W&bZ=wc{^g z$@>*7{r>>#{6E5y|7%$B_zkSP3jS?olkLArMB1-2xglJ}g>dy^2v;xv7G*N-cd&x> zdsxo>0akMV2rC(Xf|bla!^OE)i|}6(+5YE5r2Q!oWq(Y>mOmt7>hBZr734BkA~4~M5G9|6mpBYWo;z`79@!V1Sxu!`_#Smwc{L7TN~ zFVY$!txTha3ks?mv1LK7V(O8JcydHK5{}JF4##9@I3`CHl;gfy!!bD$jwx^9nDTxM z=gTv>+0NgGCGJ;nZdwES5yftYaUQITaXzf7+8TcsJx z_8Zf>IISXx(~=fX&LXW9RXjOmZ9F-({}!y3yjx+7vD;u>!?(j@Q~n*Wdf-ktZ_aMH z9uI}{RnrZFQ(w0{oVn{(=$&5?&S-Zl!5QstWjO8WhQsM!w+bx#M)cNKg|o-I)$0D5 z4!B$W)$DX-d$(F*k=Cu6Sd?`m5{oTe{`?hFyWzQ7Jn2?WERJ?7y&C5({FWc#x9kkR zL@2ztOPHkAW4hjp2OGbYo$i9|!CF_}>0a z;QTbwZ3^cd)=hw=kJ;h%iLmN?b69<|1*~{%3Co^Iz5QFk(!Vu)Zq{E6E9GZf*5&VZ zu;Q^jtbFeP%f209>DvjG{K;_fuk~HwZs)|Zy_=j^q;)$b7G>RziN%&~hs0uPw|!#q zq}wjBINFt;J2$;04&641B~0Dci6x5NR*5CZ-K4~lgKo>jlA>;l#F9a#eN$8t%#YO? zmi%{{C6@BwWzkkk^>mvimg4F*Ni4P3jZZA4*^NsqmCFU*M3utk7v&n3y6?s$mbU0d zCzh_^SH;@q(p25Z#DRhvC6<nE1$pj$7o+!o!siRCis z)=4aPO}BQIYFs@k^|*RensN20_2TMLDaO^K){CpBtT#vAe9N2Ua*1|prJ{1jc55b< zE4W)D@lBXS?Xr$xp@_wh)a5>+He=f#!$QL-hJ`MJ7#3QOVWEgFc34RNo0YLMA!!m}2uf2+%SuQl^yS>c$3xe7BKKpKs9a)} zNPWx_l}pSLHE_A!hj{kHERj2loh5n;?c59RF0jgdS6KE;f#vU1Smiwpmj3Cm-WD@p z-GqhtL12q++0M_>8Ww4M>T6h(b<+~36r7q^Ozoy57EikJn?UVsakSed@paA6mgESk zk`O_a(?ys+J$7$gxFYuVnz0s)nK-Ko+znQP?GCF#_JGw9$nooD7OV?tFL>hMZwB)a zm_7JU`gX|RwL#1Br~Q&}v@l$MJOD2N*J}Y@60Us)F9nyv!y0&L`26H$V4YtUu6@k@ z_$*hwhKI6Vy@rRu)oXZpxL%8Je3p~^6kE5UQpo|WPH9c|9Xm=edBlD-k_m%TBj zq%X!)tvckzn3Db&Q}vTN>oKNk$;0umkpD5J>b=2wJS=LJ!11t<{CHT@tg{{u3&k(S zl>CV?CHVv8OuMHzA7iS>r`;RZ=NLG^mRv=eHlwUQ$C@qmIR;{CeU5>6Ql4Y2a2D%W z30yOzo^IRUD!-fj7|(TlVr`6Pd};Gx*KJ{`i2bVjqt^k{@p#)hk>-@^GB(^&?M{Ha^3SvigyS)&DyQeG6`fRxp24 zm*{qiglgJELY44Hs0uC;s)CAy>h_ICtO_6=vGrpaNsC9U3NRkAI?tZ=%HrSgh?V|$ zrRw}7_UrbJSE~GrSE~GrSE_FRc%@2zyi#R!k^ITnrv`{u zs`i(+-K(!sv#M5{ttZBL%toZB>E57mOk^R(N z`#w4L&Vpr6ym@5LY}O~_kl7oS|NFr8=flXG11o;}!nzRmgLR(U-S*FemB0D0^1FX; z{Qy}09SGM?71(nSEPoD$<^T%xe;fuYK8M4y=LlH+aU?AJ7r?5&g|PG;1?xgS z8kYQHVCC~zSX1&iSn`jDrT+w2@i`Gzd`^NDkCWkIUz@scdF(V~d;O^h(M4KGep^LZ z(cKVRN@+I4)S|f|o)kwK;%JF;L*h`v(vUEfs&7aXOHnmkP_V?PAvsu(NQ&x@y|9@K zmLGey%_R8nMDkyL3Pqc+Im$udk8)5rqa2jJCQu-DJ=iuC8YE564L&73Dwp^Kjm-x_`mj> zY5Y50Lh^SK>xxIbgw!AL5|Y315~^1V^5P{Vd*US|`{N~~dW@Hl;u9|+?cWJ|>Q#jN z$*}C*8CE=YfmMII!m@V?toTfYW$!dt{!E8eZ!=)oHxpL8c7tW_?y%(V0n1+c+UIA% z(zh3^`iqy4{E3&4_Qy-8zGR8l9L~$%ePP8fUP7{;f#m*(myqS=UaJSWd?fmGl^*waHnJAzA|q4=-P>$>A8HIzNK-l9;*W zZ`R>e6WKl@t&7vLuAOey#R!&mk6@(72(BXyjuEW=F@j~?T4hhWg4iD;xV9|p5e$0- z!!d#-KSppZbJk-7*OrH41k1jG@_+40WIaZ3y>j6g!Lm0-u(A;&SnDx@WlxM?#WO~5 zy+V)=kIV4469ML{O$`1W6I$|PLf7xCvmO&#;fM*X^u&Z#`nN}Zogkc#2`&3#LQ7vvXvvQW zE&pOdOJ7WA#WyB&{mwf2rl4QzF`?`CN?4!9y5z-#uD34hp3rbiXqBfYH0!&UFUyMw zJw5A#x@f;@$^Mwo2jqH8=slBXv%gL-_Q!-)JYqsm$o(;)1v(}EB-N| z>l8s>Ola+o2`%|Cp%vel&}y%klFDaHXq}GHK9RGXb@#(LeDLKf!K0T zBBmagh$kiRZ8MJUpGX|$C$ei^B2k>1NRanSBnKsBO)@DeZ<2;&aGyjHymun`FO#rs zrabmaq zSgm_1EP1EF3eV}VuHG|X$v+d8zh}Wp&)Kl#ode6Cb9?LO!P0j=toU63OaI$o`EwyG z{TIQC&)Z?0zZllldtjIe9%Se?AOL-wm+j-w4aUn_v~sM_?uQW?1rXfhGS|Sn_X! z6_49t`FjT}|L%m9-@9PV^}Auk`yN>NxEGfG`(T~FA6EPxfc1`ju*V;TrSBnF@p%|l zd>(AijtoryGEc?C=s~*15<8Q*Mzi+{^ z_uH`I{~cKVeixR%--G4f)3Dz4On*^7jQ;`d{qrf2p_sWw^wrUGDHJiEMv45os?aqU^;)Y*wC%dtI++DYZ>mGb4l{2VT?_O|{Dcuw*!;fZhEPh-mS8r55rucc8{ zYZzVzt~CoU3)j%V%fYqB;GwvC>&wHn$KVy4;SFK=GXU%SMsV$6_K$??%z{V3b>_pPVaXcijF7f9MLN>f@BHOn~MB3Jg zDBCJ~DRj%X(5>DI-LfTg%a(16IM>2S1^d9NvN^D-YF}9L_k(rgkYHEIJh;BH$<};W^7n^Tl?TA8vIF6<>Hk5n zs`Ox3{u~0!o Lawyer (Legal) There is a new clear division between Security, and Legal staff. This will come with a comms channel specifically for Legal staff, to help the Legal team facilitate court cases, and hearings. +#### Legal Department Legal becomes its own department, with its own comms channel to facilitate smooth court operations, but it does not need major mapping changes. Existing maps can just reuse the current Lawyer, Magistrate, HOP, and IAA offices, as well as the Court. +A key design decision here is that the Legal Department is not solely focused on Legal/Security concerns. As SOP and Law are largely unified with our workgroup's proposal, the Legal department would be focused not just on court proceedings and law interpretations, but on also on administrative, bureaucratic, and regulatory duties. + +The Executive Officer would still be the primary authority on access changes, job hirings, and permit drafting. +The Judicial Officer gaining the power of legal regulation expands the Legal department's regulatory authority. +The Internal Affairs Agents are still concerned with performing departmental audits and SOP enforcement. + +The Legal Department stands to separate administrative duties away from CCVIPs, which should be an outside, third party entity, and solidify regulatory power under normal command structures, and especially under the Captain and XO. ### Job Responsibilities & Authority: From 9736a70b54c02aa1f4c53ac14a418da70989dbcf Mon Sep 17 00:00:00 2001 From: unknown Date: Fri, 8 May 2026 15:34:19 -0400 Subject: [PATCH 42/53] NTR SOP --- .../Article 3 - Standard Operating Procedure.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md index 5c6a5700..57ddcd8e 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md @@ -122,7 +122,14 @@ Acting Command, while still held to the same SOP as the standard position, are a ## 2 | Central Command: ### NanoTrasen Representative SOP: - +1. coordinate with the Captain and Executive Officer to ensure that Standard Operating Procedure is being followed and adequately enforced. +2. assist and advise any Command members on the proper enforcement of Standard Operating Procedure. +3. advise any local Internal Affairs Agents on Standard Operating Procedure. +4. Communicate and advocate for NanoTrasen Policy aboard the station. +5. produce regular reports about station happenings, and fax them to Central Command +6. act as oversight for any proposed votes of no confidence. + - This includes ensuring that all votes are properly counted and recorded. +7. resolve any Standard Operating Procedure related disputes locally if possible. --- ## 3 | General Crew: From 087e1eaef73e64ed4c22b48a80adb388fa9aa2fb Mon Sep 17 00:00:00 2001 From: unknown Date: Fri, 8 May 2026 15:35:09 -0400 Subject: [PATCH 43/53] NTR SOP --- .../Article 3 - Standard Operating Procedure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md index 57ddcd8e..ac6e277c 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md @@ -121,7 +121,7 @@ Acting Command, while still held to the same SOP as the standard position, are a ## 2 | Central Command: -### NanoTrasen Representative SOP: +### The NanoTrasen Representative is to: 1. coordinate with the Captain and Executive Officer to ensure that Standard Operating Procedure is being followed and adequately enforced. 2. assist and advise any Command members on the proper enforcement of Standard Operating Procedure. 3. advise any local Internal Affairs Agents on Standard Operating Procedure. From 6a74c2618acac24e521c4af24193435ea8367a34 Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Fri, 8 May 2026 16:31:39 -0300 Subject: [PATCH 44/53] Added Overview, Background, and Game Design Rationale to the main doc --- .../nanotrasen_colonial_law_and_procedure.md | 38 +++++++++++-------- 1 file changed, 23 insertions(+), 15 deletions(-) diff --git a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md index 2dba6d67..86dd2904 100644 --- a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md +++ b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md @@ -10,15 +10,17 @@ Many thanks to Tay, the Admin team, and members of the discord for pitching in ## Overview -A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". +Nanotrasen Colonial Law and Procedure is a large-scale overhaul of Funky's in-character legal, procedural, and bureaucratic framework. +The project restructures Space Law and Standard Operating Procedure into a unified framework intended to better support the themes of class conflict, corporate oppression, and roleplay. ## Background -Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. +Much of Funky's current SOP and Space Law originates from Wizden or Goob, whoose directions no longer align with the servers identity and round pacing. -Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. +Existing text often blurs the line between roleplay guidelines and enforceable server expectations, not allowing for meaningful conflict due to fears of admin intervention and limiting player options. +This proposal also serves as groundwork for future mechanical and organizational changes intended to better align gameplay incentives with Funky's roleplay direction. ## Features to be added @@ -66,21 +68,27 @@ The SOP workgroup is working on other design docs that should help change that s [Logistics & Service Restructuring](https://github.com/funky-station/docs/pull/96) ## Game Design Rationale +Nanotrasen Colonial Law and Procedure exists to reinforce Funky Station's identity as a roleplay-focused server where conflict, corporate hierarchy, and absurdity permeate every round. The proposal is not intended to create rigid rules, but rather to provide players with more believable structures to push against, exploit, or weaponize during a round. -Consider addressing: -- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? +The proposals aims to allow player-driven escalation, slower and more deliberate pacing, and emergent storytelling by using systems with additional layers of interaction through procedure, hearings, negotiations, union disputes, paperwork, and internal politics. -Mention: -New Theming -Escalation Oportunities by non antags, and more options for antags -Seriously Silly (clown exemption :godo:) -Autenticity increased with: -- The use of some legaleese -- More atuned to the theme and NT's opression -Take things slow (point at trials) -Maximixing RP Potential is all over the place in this doc -Dynamic Environment respected, as it all depends on where players want to take this +### New Themeing +The NTCLP has be written to promote a stronger corporate/colonial identity fitting of Nanotrasen; All helping to establish the feeling of an oppressive corporate environment. +### Escalation Oportunities +The proposal increases opportunities for escalation for both antagonists and non-antagonists. + +Bureaucratic Procedure, Trials, Hearings, SOP Disputes, and Union Activity create new forms of engament where violence is not needed (at first at least). Players gain more opportunities to abuse or resist authority, manipulate procedure, organize collectively, or escalate situations socially. + +### Take Things Slow +Taking advantage of the 2 hour shifts of Funky, we have pushed for changes to how sentencing works, rather than immediately resolving incidents through violence or instant punishment, players are encouraged to interact through dialogue, negotiation, and a more formal process. + +### Maximising RP Potential +Every article included in this proposal is intended to create additional opportunities for roleplay. + +### Dynamic Enviroment +We have taken care to not limit player options when doing things, for example making SOP a basic job description rather than a step by step process of how to do your job. +Different people may enforce regulations differently, leading to more authoritarian or corrupt themes, a more negotiative and compasionate command member trapped on the middle of the war of crew vs NT profits, or more chaotic shifts where people openly rebeel ## Roundflow & Player interaction From 8625a2c70fdadf659365ac5d581469376d6a3157 Mon Sep 17 00:00:00 2001 From: Alicios Date: Fri, 8 May 2026 12:44:08 -0700 Subject: [PATCH 45/53] SOP Update to include Legal --- ...rticle 3 - Standard Operating Procedure.md | 59 +++++++++++++------ 1 file changed, 40 insertions(+), 19 deletions(-) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md index ac6e277c..eb14556a 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md @@ -3,14 +3,15 @@ ## Table of Contents: 1. Command -3. Central Command +2. Central Command__ 3. General Crew 4. Security -5. Logistics -6. Engineering -7. Medical -8. Science -9. Service +5. Legal__ +6. Logistics +7. Engineering +8. Medical +9. Science__ +10. Service --- ## 1 | Command: @@ -34,7 +35,7 @@ 5. ensure that Nanotrasen Colonial Law and Procedure is being enforced, in conjunction with Central Command VIPs. 6. ensure the safety of the station's nuclear authentication disk at all costs. -### The Head of Personnel is: +### The Executive Officer is: 1. to not provide higher levels of access to personnel without receiving authorization from the relevant Command Personnel for that access. If an access is not restricted to a department or position, the HoP may use their discretion. 2. to issue warrants to security should there be a valid reason for the warrant. @@ -46,7 +47,8 @@ 1. avoid being disruptive to essential station activities 2. promote products in a manner consistent with Nanotrasen Values. 3. avoid becoming an expense greater than the value provided by the campaign. - 4. take payment for any services advertised that are not provided officially by Nanotrasen. + 4. take payment for any services advertised that are not provided officially by Nanotrasen.__ +7. monitor major legal decisions in order to raise necessary concerns and authorizations to the Captain. ### The Head of Security is: @@ -130,6 +132,7 @@ Acting Command, while still held to the same SOP as the standard position, are a 6. act as oversight for any proposed votes of no confidence. - This includes ensuring that all votes are properly counted and recorded. 7. resolve any Standard Operating Procedure related disputes locally if possible. + --- ## 3 | General Crew: @@ -154,12 +157,6 @@ Acting Command, while still held to the same SOP as the standard position, are a 3. Uphold and maintain NanoTrasen’s authority. 4. Follow the Security Rules of Conduct. -### The Judicial Officer is to: - -1. Hold court hearings and trials in accordance with NanoTrasen Court Protocol. -2. Ensure that hearings and trials are fast and efficient, but still as thorough as necessary. - - a. The Judicial Officer is to ensure that time and resources are not spent on frivolous cases, and that the type of proceeding is held in accordance with severity and importance. - - b. The Judicial Officer is to ensure that lesser court proceedings do not overly interrupt or impede more important station functions. ### The Warden is to: @@ -184,11 +181,35 @@ Acting Command, while still held to the same SOP as the standard position, are a 1. Read all of Corporate Law before doing any field work. 2. Request that the Head of Security assigns them a partner for practical training. +--- + +## 5 | Legal: + +### The Judicial Officer is to: + +1. Hold court hearings and trials in accordance with NanoTrasen Court Protocol. +2. Ensure that hearings and trials are fast and efficient, but still as thorough as necessary. + - a. The Judicial Officer is to ensure that time and resources are not spent on frivolous cases, and that the type of proceeding is held in accordance with severity and importance. + - b. The Judicial Officer is to ensure that lesser court proceedings do not overly interrupt or impede more important station functions.__ +3. Communicate with the Executive Officer regarding major court decisions. + +### Internal Affairs Agents are to: + +1. Prioritize answering court summons and requests for representation above other duties.__ + - a. IAAs are primarily to represent the side of NanoTrasen in court, whether it be prosecution or defense.__ + - b. IAAs may only represent a party against NanoTrasen in the complete absence of a Lawyer. +2. Ensure Standard Operating Procedure is being properly followed, and to report breaches and concerns to the relevant Head of Staff.__ +3. Produce regular departmental audits and reports, and send them to the Executive Officer for review.__ + ### Lawyers are to: +1. Prioritize answering court summons and requests for representation above other duties. + - a. Lawyers may represent the side of NanoTrasen if they necessary, but should defer the responsibility to Internal Affairs Agents.__ +2. Avoid obstructing Security duties, unless specifically requested by an enforcement officer.__ +2. Provide legal advice upon request. --- -## 5 | Logistics: +## 6 | Logistics: ### Cargo Technicians are: @@ -225,7 +246,7 @@ Acting Command, while still held to the same SOP as the standard position, are a --- -## 6 | Engineering: +## 7 | Engineering: ### Engineers are to: @@ -244,7 +265,7 @@ Acting Command, while still held to the same SOP as the standard position, are a --- -## 7 | Medical: +## 8 | Medical: ### Doctors are: @@ -295,7 +316,7 @@ Acting Command, while still held to the same SOP as the standard position, are a --- -## 8 | Science: +## 9 | Science: ### Scientists are: @@ -310,7 +331,7 @@ Acting Command, while still held to the same SOP as the standard position, are a --- -## 9 | Service: +## 10 | Service: ### Service Workers are to: From b83d6f4ef2be533a726c659d6353ea50ae21a23e Mon Sep 17 00:00:00 2001 From: Alicios Date: Fri, 8 May 2026 12:46:29 -0700 Subject: [PATCH 46/53] Legal section typos/rephrasing. --- .../Article 3 - Standard Operating Procedure.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md index eb14556a..86f60eb5 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md @@ -187,7 +187,7 @@ Acting Command, while still held to the same SOP as the standard position, are a ### The Judicial Officer is to: -1. Hold court hearings and trials in accordance with NanoTrasen Court Protocol. +1. Hold court hearings and trials in accordance with NTCLP Article 5. 2. Ensure that hearings and trials are fast and efficient, but still as thorough as necessary. - a. The Judicial Officer is to ensure that time and resources are not spent on frivolous cases, and that the type of proceeding is held in accordance with severity and importance. - b. The Judicial Officer is to ensure that lesser court proceedings do not overly interrupt or impede more important station functions.__ @@ -199,12 +199,12 @@ Acting Command, while still held to the same SOP as the standard position, are a - a. IAAs are primarily to represent the side of NanoTrasen in court, whether it be prosecution or defense.__ - b. IAAs may only represent a party against NanoTrasen in the complete absence of a Lawyer. 2. Ensure Standard Operating Procedure is being properly followed, and to report breaches and concerns to the relevant Head of Staff.__ -3. Produce regular departmental audits and reports, and send them to the Executive Officer for review.__ +3. Produce regular departmental audits and reports, and present them to the Executive Officer for review.__ ### Lawyers are to: 1. Prioritize answering court summons and requests for representation above other duties. - - a. Lawyers may represent the side of NanoTrasen if they necessary, but should defer the responsibility to Internal Affairs Agents.__ -2. Avoid obstructing Security duties, unless specifically requested by an enforcement officer.__ + - a. Lawyers may represent the side of NanoTrasen if necessary, but should defer the responsibility to any present Internal Affairs Agents.__ +2. Avoid obstructing Security duties, unless specifically requested by an enforcement authority.__ 2. Provide legal advice upon request. --- From 7701f3dfb8eb1bcd1f4f1ec9a715f0410988171b Mon Sep 17 00:00:00 2001 From: Alicios Date: Fri, 8 May 2026 12:50:51 -0700 Subject: [PATCH 47/53] Markdown format fixes on SOP --- ...rticle 3 - Standard Operating Procedure.md | 27 ++++++++++--------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md index 86f60eb5..fafcd6f9 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md @@ -3,14 +3,14 @@ ## Table of Contents: 1. Command -2. Central Command__ +2. Central Command 3. General Crew 4. Security -5. Legal__ +5. Legal 6. Logistics 7. Engineering 8. Medical -9. Science__ +9. Science 10. Service --- @@ -190,21 +190,22 @@ Acting Command, while still held to the same SOP as the standard position, are a 1. Hold court hearings and trials in accordance with NTCLP Article 5. 2. Ensure that hearings and trials are fast and efficient, but still as thorough as necessary. - a. The Judicial Officer is to ensure that time and resources are not spent on frivolous cases, and that the type of proceeding is held in accordance with severity and importance. - - b. The Judicial Officer is to ensure that lesser court proceedings do not overly interrupt or impede more important station functions.__ + - b. The Judicial Officer is to ensure that lesser court proceedings do not overly interrupt or impede more important station functions. 3. Communicate with the Executive Officer regarding major court decisions. ### Internal Affairs Agents are to: -1. Prioritize answering court summons and requests for representation above other duties.__ - - a. IAAs are primarily to represent the side of NanoTrasen in court, whether it be prosecution or defense.__ - - b. IAAs may only represent a party against NanoTrasen in the complete absence of a Lawyer. -2. Ensure Standard Operating Procedure is being properly followed, and to report breaches and concerns to the relevant Head of Staff.__ -3. Produce regular departmental audits and reports, and present them to the Executive Officer for review.__ - +1. Prioritize answering court summons and requests for representation above other duties. + - a. IAAs are primarily to represent the side of NanoTrasen in court, whether it be prosecution or defense. + - b. IAAs may only represent a party against NanoTrasen in the complete absence of a Lawyer. +2. Ensure Standard Operating Procedure is being properly followed, and to report breaches and concerns to the relevant Head of Staff. +3. Produce regular departmental audits and reports, and present them to the Executive Officer for review. + ### Lawyers are to: -1. Prioritize answering court summons and requests for representation above other duties. - - a. Lawyers may represent the side of NanoTrasen if necessary, but should defer the responsibility to any present Internal Affairs Agents.__ -2. Avoid obstructing Security duties, unless specifically requested by an enforcement authority.__ + +1. Prioritize answering court summons and requests for representation above other duties. + - a. Lawyers may represent the side of NanoTrasen if necessary, but should defer the responsibility to any present Internal Affairs Agents. +2. Avoid obstructing Security duties, unless specifically requested by an enforcement authority. 2. Provide legal advice upon request. --- From 4bd54bb83993109f10fe686eb07555ab9e5e742c Mon Sep 17 00:00:00 2001 From: joaco545 <38332230+Joaco545@users.noreply.github.com> Date: Sat, 9 May 2026 17:22:46 -0300 Subject: [PATCH 48/53] A new sidedoc was added to the extra considerations section --- src/design-proposals/nanotrasen_colonial_law_and_procedure.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md index 86dd2904..aa6fb8e2 100644 --- a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md +++ b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md @@ -60,13 +60,15 @@ SOP has to be overhauled to better fit the themes and expectations of Funky Stat *[Article 5 - Trials and Hearings](./station_protocol_rework/Article%205%20-%20Sentencing,%20Trials,%20and%20Hearings.md)* -### Extra considerations +### Extra Considerations "Behavior follows incentives" While this PR focuses only on the regulations themselves, many supporting changes will need to be done to mechanically enforce the new vision Funky Station has. The SOP workgroup is working on other design docs that should help change that situation and align mechanics with the text and intent behind them. [Logistics & Service Restructuring](https://github.com/funky-station/docs/pull/96) +[Command and their Paperwork](https://github.com/funky-station/docs/pull/98) + ## Game Design Rationale Nanotrasen Colonial Law and Procedure exists to reinforce Funky Station's identity as a roleplay-focused server where conflict, corporate hierarchy, and absurdity permeate every round. The proposal is not intended to create rigid rules, but rather to provide players with more believable structures to push against, exploit, or weaponize during a round. From e1689ee5a1c5b165e2fcfea679f8b4066e5bf5f3 Mon Sep 17 00:00:00 2001 From: Dusty Plant <34702649+Dusty-Plant@users.noreply.github.com> Date: Tue, 26 May 2026 19:27:00 +0200 Subject: [PATCH 49/53] Update Article 3 - Standard Operating Procedure.md adds librarian SOP! --- .../Article 3 - Standard Operating Procedure.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md index fafcd6f9..daf36b98 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md @@ -145,6 +145,17 @@ Acting Command, while still held to the same SOP as the standard position, are a - a. Assistants answer directly to the Head of Personnel, and should work with them to find tasks throughout the shift. 3. undertake unorthodox business ventures only if they receive express approval and a permit, from the Head of Personnel. - a. Business ventures should benefit the station in some way, and not undertaken purely for personal profit. + +### The librarian is to: + +1. Keep a log of any and all loaned out books. +2. Keep the library organised. + - a. The floor of the library must be free of loose books. + - b. Shelves must be labeled according to a sorting system. +3. Ensure the quiet and sanctity of the library are preserved. +4. Ensure there is no drinking or eating within the confines of the library. +5. Ensure members of the crew have access to the library. +6. Ensure the wellbeing of all books on station. --- From a88db85f6ad28376b7384ebf087f9df4bd86d41f Mon Sep 17 00:00:00 2001 From: Dusty Plant <34702649+Dusty-Plant@users.noreply.github.com> Date: Tue, 26 May 2026 19:47:07 +0200 Subject: [PATCH 50/53] Update Article 3 - Standard Operating Procedure.md oops moved librarian from general crew to service --- ...rticle 3 - Standard Operating Procedure.md | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md index daf36b98..e545fc0f 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md @@ -145,17 +145,7 @@ Acting Command, while still held to the same SOP as the standard position, are a - a. Assistants answer directly to the Head of Personnel, and should work with them to find tasks throughout the shift. 3. undertake unorthodox business ventures only if they receive express approval and a permit, from the Head of Personnel. - a. Business ventures should benefit the station in some way, and not undertaken purely for personal profit. - -### The librarian is to: -1. Keep a log of any and all loaned out books. -2. Keep the library organised. - - a. The floor of the library must be free of loose books. - - b. Shelves must be labeled according to a sorting system. -3. Ensure the quiet and sanctity of the library are preserved. -4. Ensure there is no drinking or eating within the confines of the library. -5. Ensure members of the crew have access to the library. -6. Ensure the wellbeing of all books on station. --- @@ -416,3 +406,14 @@ Acting Command, while still held to the same SOP as the standard position, are a - a. Special Talent or Hires - b. Props - c. Alterations to the stage + +### The Librarian is to: + +1. Keep a log of any and all loaned out books. +2. Keep the library organised. + - a. The floor of the library must be free of loose books. + - b. Shelves must be labeled according to a sorting system. +3. Ensure the quiet and sanctity of the library are preserved. +4. Ensure there is no drinking or eating within the confines of the library. +5. Ensure members of the crew have access to the library. +6. Ensure the wellbeing of all books on station. From 9affe2d22bf4115fa806e25d0e9fc2a0400a17ff Mon Sep 17 00:00:00 2001 From: Scrambledking <118861382+Scrambledking@users.noreply.github.com> Date: Thu, 4 Jun 2026 11:53:36 -0600 Subject: [PATCH 51/53] Update Article 1 - Station Regulations.md Uniform Regs --- .../Article 1 - Station Regulations.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md index 91c6a704..5794ce82 100644 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md +++ b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md @@ -93,6 +93,10 @@ Standard CTM knowladge. Admin level knowladge, they know what they decide they know. +## Uniform Regulaions + +Nanotrasen personel are expected to wear uniforms from their job associated vend during working hours. Failure to do so without their command member's direct permission will result in administrative actions. + ## Permits and Paperwork Paperwork From 57f455e4be70d11f8c59d80a877065fcbc61d152 Mon Sep 17 00:00:00 2001 From: unknown Date: Fri, 5 Jun 2026 13:29:26 -0400 Subject: [PATCH 52/53] NCLR-MAIN-PR --- .../Article 1 - Station Regulations.md | 261 ----------- .../Article 2 - Corporate law.md | 400 ----------------- ...rticle 3 - Standard Operating Procedure.md | 419 ------------------ .../Article 4 - Unions.md | 0 ...le 5 - Sentencing, Trials, and Hearings.md | 354 --------------- .../article-1_design_doc.md | 209 --------- .../article-2_design_doc.md | 117 ----- .../article-3_design_doc.md | 104 ----- .../article-4_design_doc.md | 42 -- .../article-5_design_doc.md | 224 ---------- 10 files changed, 2130 deletions(-) delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 2 - Corporate law.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 4 - Unions.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 5 - Sentencing, Trials, and Hearings.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/article-1_design_doc.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/article-2_design_doc.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/article-3_design_doc.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/article-4_design_doc.md delete mode 100644 src/design-proposals/nanotrasen-colonial-law-and-procedure/article-5_design_doc.md diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md deleted file mode 100644 index 5794ce82..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 1 - Station Regulations.md +++ /dev/null @@ -1,261 +0,0 @@ -# NanoTrasen Station Regulations - -## Alert Levels - -### Green -There is no major threat to operational safety. - -SOP and Corporate Law remain in full effect. - -### Blue - -Called for the reason of un-unsolved Felony - -A crime is being actively investigated by security. Crew are to have their IDs ready and comply with security search orders. - -Security may carry concealed longarms - -Events may be canceled without warning should the situation require it. - -HoS is to remain in security to collate officer reports and the detective's evidance, directing security's responses and patrols as needed. - -### Red - -There is an active lethal threat on station that security is preparing to combat/currently combating. - -All crew members are to follow the instructions given by their Commanding members. Unless declared otherwise, they should remain in their departments. - -Anyone who is not currently part of a department should head to the Bar - -Captains may suspend any Standard Operating Procedure they deem necessary. -This includes removing restrictions on command or crew arming and the creation or purchase of weapons, mechs, and armour. - -Security’s restrictions on heavy weapons are also lifted and it is expected that the Head of Security and/or Warden keep track of what weapons are taken by who to account for their return when the situation is resolved. - -Departmental breaks and crew events such as in the theatre and chapel are paused for the duration of the alert. Gatherings may be broken up as needed. - -Maintenance areas are to be considered off limits; Anyone found inside may be arrested and charged with trespassing. - -Suit sensors are required to be set to coordinates; Anyone without their suit sensors set on the requested level will be arrested and charged with endangerment. - -Warden takes over the position of local squad command for larger scale combats. - -HoS provides overwatch and directions from security. - -### Yellow - -There is an active atmospheric or power related issue upon the station that may place crewmembers at risk. Crew should move about with caution and are advised to enable suit sensors in case of injury. -Opening firelocks and spreading the atmospheric issues may be met with an endangerment charge. - -### Cyan - -There is a malfunctioning silicone upon the station. Please use caution when interacting with silicone based lifeforms and inform the RD and/or security should you notice anything unusual. - -### Violet - -There is an active viral threat on station, crew are required to have sensors set to show their health to better track the spread of the infection. - -The CMO may declare portions of the ship under quarantine which may only be lifted by the CMO or Captain’s orders. Security is given permission to enforce this quarantine through any method the captain allows. - -### Other - -Other station alerts are tied to admin events/automatic calls and are left alone at the current moment. - -## Corporate Espionage Act - -### Standard (crew): - -Knowladge of research classifications - -Bluespace research - -Genetics research - -Artifacts research - -Anomalous research - -Standard NDAs that only mention research being classified to the company. - -### Prepared (Security): - -Additional knowladge of Overwatch classification's existance. - -The existance of need-to-know information. - -Security class NDA. - -### Privladged (Command/CCVIP): - -Standard CTM knowladge. - -### Overlord (CCO/I): - -Admin level knowladge, they know what they decide they know. - -## Uniform Regulaions - -Nanotrasen personel are expected to wear uniforms from their job associated vend during working hours. Failure to do so without their command member's direct permission will result in administrative actions. - -## Permits and Paperwork - -Paperwork - -Permits - -### Hiring Process (Internal) - -How to go about hiring from the NT personel pool of employees for standard, security, or command positions. - -## Departmental SOP - -### Nanotrasen Building Code - -A standard code for building room types and procedures. - -### Service Department Expensing Regulations - -All expenses implicitly approved by a position's SOP should be under X scrip. - -All other expenses must be approved by the Hospitality Director or Quartermaster. - -Any unapproved expenses that are charged to the service budget will be taken from the personnel’s pay. - -Any alterations to service department locations must be minor in scope, unless otherwise approved by the Hospitality Director. - -### Science Distribution Regulations - -No weapons are to be created or handed out to non-security staff. - -All items created must be paid for by personnel in scrip. - -The value charged should not be changed between requests without approval from the Research Director. - -Department Specific items and machines should only be handed out to personnel with such access, or a stamped form from the relevant authority. - - -## Regulatory Fines - -### Corporate Disciplinary Actions - -Internal Affair Agents are allowed to generate a Corporate Disciplinary Action for crew members that violate SOP. -Corporate Disciplinary Actions may result in a formal warning and/or a fine. - -If many Corporate Disciplinary Actions are levied against someone, IAA's are advised to inform the head of the department with the proper paperwork detailing the past infractions incurred and requesting the head to take punitive actions against this individual. - -The punitive actions taken are at the sole discretion of the relevant Head of Staff. - -The punitive actions are as follow: - -A permanent reduction in salary - -A temporary suspension - -A demotion - -A dismissal - -An appeal for the CEA and/or fine can be made to the NanoTrasen Representative, Head of Personnel, or Captain - -### Infractions -Security personnel are allowed to issue infractions to crew members committing infraction level crimes. -The infraction may result in a formal warning and/or a fine. - -If many infractions are levied against someone, security is advised to approach the head of the department with the proper paperwork detailing the past infractions incurred and requesting the head to take punitive actions against this individual. -Punitive actions taken are at the sole discretion of the relevant Head of Staff. - -An appeal for the Infraction and/or fine can be made to the Judicial Officer, Head of Personnel, or Captain. - -## Extracorporate Entities - -### Docking Regulations - -Shuttles are required to request docking permission from the station before docking to the station itself. - -After reciving docking permission they may dock at the designated location and proced with standard medical checks before disembarking. - -### Trading Regulations - -Trading should be done through the Quartermaster with the Captain’s permission, or presence. - -### Treatment of Visitors - -Visitors should be treated with the same level of dignity they treat NanoTrasen station staff. -They must however provide funds for purchase of benefits such as healthcare, drinks, food, and other amenities. - -Visitors must be kept away from the research computers and servers, along with any artifacts or anomolies that may be on station. -This is to prevent the accidental leak of classified material to non-NT personel. - -Visitors are held subject to the same laws as Nanotrasen Personel while docked or on board a Nanotrasen station. - -### Refugees - -Refugees are to be treated the same as Visitors, however they are to be brought back to NanoTrasen for further processing. - -### Hiring Process (external) - -#### Temporary Contracts - -Contracts given for the specified duration, usually in relation to shift length or specific task. -Can be given by command members on the station with the captain’s permission. - -#### Complete Contracts - -Standard NanoTrasen hiring contracts. -Requires NTR approval to be completed. - -## Insurance - -### Medical Insurance - -Deductibles, shift start costs (eg lowered scrip payments/starting amount), insurance levels, minimum insurance for jobs and discounts - -### Shuttle insurance - -This section is more about contacting CC to report the loss of all shuttles, and what to do in that situation. - -## Order of Succession - -Should a captain be incapacitated or deemed unable to perform their duties the order of succession determines who is next in line for the position. - -Captain - -Head of Personnel - -Research Director - -Quartermaster - -Chief Medical Officer - -Chief Engineer - -Hospitality Director - -Acting Command in the same order as above - -Head of Security - -Should no command member be able to be promoted to command remain, the HoS may declare a level of martial law over the station until a new captain can be appointed. - -### Vote of No Confidence - -A vote of no confidence can be triggered in two ways: - -Central Command VIPs can call a vote of no confidence should they believe the captain is unable to perform their duties. This can only be called by a vote with a majority of Central Command VIP’s approval. - -The Chief Medical Officer may call a vote of no confidence should they deem the Captain to be unfit for duty. - -When a vote is called all members of command should report to the bridge or another secure location immediately. -The Head of Security is not permitted to cast a vote. -The vote requires a simple majority required to pass. -The vote should be overseen by a Central Command VIP, and then the results verified by them. -Central Command should be notified of the vote, but do not expect a response. -Approval from Central Command is not required for any part of the vote. -The transition of power should be enforced by the Head of Security. - -### Martial law - -Martial law is declared once no suitable replacements for the captain can be made. The Head of Security will take over the station until a suitable captain replacement can be found, at which point power will be relinquished to them. - -Under martial law security’s orders are final, personnel are to immediately return to their departments or bar unless given explicit permission otherwise, and failure to do so leaves punishment at the discretion of the witnessing officer. This includes engineering and medical personnel who are responding to emergencies, and scientists responding to anomalies. diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 2 - Corporate law.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 2 - Corporate law.md deleted file mode 100644 index d448c988..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 2 - Corporate law.md +++ /dev/null @@ -1,400 +0,0 @@ -# NanoTrasen Corporate Law -## Table of Contents: -Legal Definitions -Searches -Detainment & Arrests -Chain of Custody -Treatment of Arrestees -Implantion -List of Crimes -Contraband Classifications -Legal Exemptions - ---- - -## 1. Definitions: -NT: NanoTrasen -Charge: Accused Crimes. -Sentence: Officially recognized crimes by a Judge, with accompanying punishment. -Arrest: Under restraint by Security, in order to press charges before a judge. -Custody: Under restraint by Security, during or after receiving a sentence. -Detainee: Any being who is being temporarily held. -Arrestee: Any being either arrested or in custody. -Excessive Force: More than needed for the situation. (eg. gibbing) -Criminal Offense: Charges/Sentences that can result in arrests and/or brig time. -Sentient Being: A living entity capable of thought. -Sapient Being: A living entity that is capable of fully comprehending itself, its surroundings, and other sapient beings. -Privileged Individuals: Referees to Command Members and Central Command VIP’s -Death: Fully deceased. Critical condition does not count as death. -Operational Safety: The ability for the station, departments, and crew as a whole to perform work unimpeded. -Reasonable Suspicion: Enforcement personnel either directly witnessing or receiving credible information about potential illegal activity. Valid Reasonable Suspicion is more than a simple hunch or instinct, and must be based on clear facts. -Probable Cause: Enforcement personnel either directly witnessing or receiving credible information about an actual crime committed. - ---- - -## 2. Searches - -### Personnel Searches -Security personnel are allowed to search personnel under the following conditions: -1. There is reasonable suspicion of a crime -2. There is a search warrant for the being -3. The station’s alert level allows for random searches - -The search could lead to the seizure of the objects in a person's backpack, hands, coat, belt, pockets, headset, and hat. This includes any bags, boxes or other containers the person has in the immediate vicinity. - -A crewmate may legally decline any search conducted without reasonable suspicion while the alert level is green. - -If any contraband is found during a search the officer may choose to further the search into an arrest, or confiscate the restricted items and issue a fine. After the search is conducted all legal items are to be returned to the person. - -#### Invasive confiscation -Sometimes crewmembers may have contraband that requires surgery to remove. -Removal of body augmentation contraband should be done by medical personnel and not cause excessive harm or leave the person's body nonfunctional. - -### Department searches -Security personnel are allowed to search a department under the following conditions -1. There is a search warrant signed by the appropriate Department Head, Head of Personnel or Captain -2. The station’s alert level allows for the departmental search - -Security personnel should minimize the interruption of work from the department -- Personnel should be able to work -- Search time should be kept to a minimum - -Secure Areas are not be searched unless otherwise EXPLICITLY authorized by the head of that department, or higher - -Anything, excluding personnel, within the areas defined on the searched warrant can be searched. This includes but is not limited to: -- Crates -- Lockers -- Machines -- Plants - -The Head of Personnel may issue ID’s with temporary access for the purposes of fulfilling a search warrant. - ---- - -## 3. Detainment & Arrests -Security personnel are allowed to temporarily detain anyone with only a reasonable suspicion of a crime. -Detainment reasons include: -1. Performing a search -2. Investigating a crime -3. Handing out a fine - -Security Personnel are allowed to arrest only with probable cause of a crime. -Arrest reasons include: -1. Directly witnessing a crime. -2. Having suitable forensic evidence of a crime. -3. Eyewitness report from a trustworthy individual. - -Detained and arrested individuals should not be handcuffed, provided they are cooperating. -Cuffing of a detainee or arrestee should only happen if: -1. The subject poses a clear threat towards: - * Command staff - * Security officers - * Station assets -2. The subject is non-cooperative, or resisting enforcement authority. - ---- - -## 4. Chain of Custody -All enforcement personnel are held to a high standard when interacting with the public. -Proper protocol is to be followed, in order to ensure that subjects of legal enforcement are given due process, and retain any and all rights they may hold. - -Enforcement Personnel are to follow the following procedure with any arrest. -Failure to follow this procedure may result in formal Disciplinary Actions by onboard CC staff, or in extreme cases, charges of negligence and/or endangerment. - -1. Given Probable Cause, the officer must state their intent to arrest, and for what crimes, before taking any forceful action. - * Proper intent includes using a security voice mask, calling their name or job, and/or pointing at them and telling them to stop. - * This step may be waived if the target is the subject of a Red Alert, or if they are declared “Arrest on Sight” by the Head of Security. -2. If the subject fails to stop when asked, or attempts to evade lawful arrest, forceful action and restraints may be used to take them in. - * Batons, flashes, and handcuffs should be prioritized first, but if all less-lethal options are disabled, stolen, or otherwise ineffective, lethal force is authorized and encouraged. - * Heavy weaponry is only permitted to perform an arrest if the subject is the target of a Red Alert, or is a clear militarized danger to the station. -3. After successful detainment, the officer is to alert the Head of Security and Judicial Officer as soon as possible, so that all involved parties may prepare for a Hearing or Trial. -4. Recovery of the arrestee’s bodily health is to be ensured before any other enforcement actions. - * Any further legal actions taken before the arrestee is stabilized are to be considered invalid. -5. The arrestee may optionally be brought to security to remove and confiscate any immediately dangerous contraband, before moving on to the Hearing or Trial. -6. In the case of a Formal Hearing or Trial, the arrestee must be informed of their right to a lawyer, and be provided one upon request. - * For Summary Hearings, the arrestee does not have to be offered a lawyer, but still must be provided one upon request. -7. The arrestee is to be brought to court, before the Judicial Officer, where they receive their official sentence via Hearing or Trial. -8. Should their sentence result in brig time, the officer is to transport and hand the prisoner off to the Warden. -9. The Warden performs a thorough search of the prisoner’s belongings, and ensures they are properly stored in their locker before handing them their prisoner ID and transporting them to the brig. - -At any point during a prisoner’s arrest or confinement, the Detective is permitted to bring them into interrogation and question them. -* The prisoner may ask for consultation with a Lawyer, during which their sentence is to be paused. -* The prisoner’s sentence is not to be paused during interrogation. - ---- - -## 5. Treatment of Arrestees and Prisoners -Personnel in custody are to be ensured the following rights: - -### Arrestees -Arrestees must be provided with: -1. Adequate medical care -2. Access to communications equipment so long as they are not abused -3. Access to a lawyer, should they request it - * This includes during interrogations and the subsequent hearing - -### Prisoners -On top of the arrestee’s protections, prisoners must be provided with: -1. Clothing, food, water, shelter and safety - * Should the Brig be rendered unsafe, confinement must be established in another location -2. Psychiatric and spiritual counselling if requested -3. Access to their shift mandated PDA after confinement has finished - * Unless there is solid proof of PDA tampering, in which case the PDA is to be secured and replaced with a fresh one before confinement ends -4. Freedom of movement. -5. Prisoners should not be restrained with handcuffs or other devices after incarceration unless there is an undue risk to life and limb - ---- - -## 6. Implantation -Any crewmate can be implanted if they give their clear permission. - -Any prisoner in custody can be subjected to implantation or implant removal procedures, so long as it's within reason. The process of adding an implant should not prolong the detainees sentence, or prevent them from leaving the brig to administer the implantation procedure. - -### Implantation -MindShields: MindShields can be administered to any inmate who has had their free will suppressed. Unlike standard implantation, you may hold a prisoner until they are issued a MindShield, so long as it's done in a timely fashion. If a suspect refuses to cooperate or the implant fails to function they can be charged with Refusal of Mental Shielding. - -While under normal circumstances a crewmate can refuse a Mind Shield if they are not imprisoned, when there is a known threat to the station that utilizes mass brainwashing or mind control, crewmates must submit to a MindShield if ordered by Security. Failure to comply is to be treated as Refusal of Lawful Implantation. - -### Removal -A suspect can be forced to receive implant removal if there is probable cause that they have an illegal implant, such as an officer witnessing them use an implantation device or their biological information being found on a discarded injector. - -Unlike the implantation procedure a prisoner can have their sentence entirely delayed or extended until they comply with the removal, as long as security are actively making attempts to perform it. Akin to implanting, if an inmate gives their clear permission, implant removal can proceed without proof. - ---- - -## 7. List of Crimes - -### Crime Tiers: -* **Infraction** - * Minor, non-criminal offenses, especially if they are easily reversible. - * Possible Punishments: - * Tickets/Fines, Pay Docking, Formal Warnings. - * Explicitly do not result in brig time. - * Punishments for Infractions aren’t supposed to majorly interrupt the offender’s productivity. - -* **Misdemeanor** - * Crimes that cause harm to others or asset loss, and aren’t as easily reversible. - * Possible Punishments: - * 10-15 Minute Brig Time. - * Demotion within the department. - -* **Felony** - * Crimes that cause major harm, major asset loss, and/or are a major threat to operational safety. - * Possible Punishments: - * 20+ Minute Brig Time. - * Demotion out of department. - -* **Capital Offense** - * Crimes that cause irreversible harm or asset loss, and/or majorly disrupt the operational safety. - * Possible Punishments: - * Permanent Brig Sentence. - * Contract Termination. - * Execution - - -### NanoTrasen defines the following Infractions and Criminal Offenses: -| Infractions | Misdemeanors | Felonies | Capital Offenses | -| :---- | :---- | :---- | :---- | -| Loitering (A) | Trespass (A) | Secure Trespass (A) | | -| Possession of Minor Contraband (C) | Possession of Moderate Contraband (C) | Possession of Major Contraband (C) | | -| Substance Abuse (C) | | | | -| Vandalism (D) | Destruction of Property (D) | Mass Destruction (D) | Sabotage (D) | -| Refusal to Identify (F) | Impersonation (F) | | Impersonation of Central Command (F) | -| Mail Fraud (F) | | Fraud (F) | | -| | Contempt of Court (J) | Perjury (J) | Subversion of Court (J) | -| Harassment (M) | | Extortion (M) | Terrorism (M) | -| Negligence (N) | Endangerment (N) | Manslaughter (N) | Capital Negligence (N) | -| Operation without Permit (O) | | Black Marketeering (O) | | -| Disturbance (R) | | Rioting (R) | | -| Failure to Comply (S) | Breach of Detainment (S) | Breach of Arrest (S) | Breach of Custody (S) | -| Petty Theft (T) | Theft (T) | Grand Theft (T) | | -| Slander (U) | | Libel (U) | Sedition (U) | -| Insubordination (U) | | | | -| | Battery (V) | Incapacitation (V) | Murder (V) | -| | Assault (V) | Mutilation (V) | Prevention of Revival (V) | -| | | Kidnapping (W) | Suppression of Free Will (W) | -| Cannibalism | Animal Cruelty | Bribery | Refusal of Lawful Implantation | -| | Failure to Pay a Fine | Tax Evasion | Breach of NT Contract | - -### Crime Specifications: -| A | Access | Existing where you are not allowed. | -| :---- | :---- | :---- | -| Infraction | Loitering | Existing near a restricted area for an extended time, with no reasonable purpose. | -| Misdemeanor | Trespass | Entering a restricted area without express permission. | -| Felony | Secure Trespass | Entering a station-critical restricted area without express permission. | - -| C | Contraband | Possession or use of controlled, restricted, or illegal contraband. | -| :---- | :---- | :---- | -| Infraction | Substance Abuse | Consumption or usage of contraband substances. | -| Infraction | Possession of Minor Contraband | See Contraband Classifications. | -| Misdemeanor | Possession of Moderate Contraband | See Contraband Classifications. | -| Felony | Possession of Major Contraband | See Contraband Classifications. | - -| D | Destruction | Causing intentional damage to station functions. | -| :---- | :---- | :---- | -| Infraction | Vandalism | Superficially damaging or defacing station property. | -| Misdemeanor | Destruction of Property | Causing substantial structural damage, requiring repairs. | -| Felony | Mass Destruction | Causing substantial structural damage to a large area of the station. | -| Capital Offense | Sabotage | Intentionally rendering critical station infrastructure inoperable. | - -| F | Fraud | Lying about yourself or your actions for personal gain. | -| :---- | :---- | :---- | -| Infraction | Refusal to Identify | Not wearing your shift-assigned ID, and/or hiding your identity with facial coverings, and refusing to present your identity when asked by an authority. | -| Infraction | Mail Fraud | The unauthorized opening or tampering of mail intended for another individual. | -| Misdemeanor | Impersonation | Hiding your true identity and posing as someone you are not for personal gain. | -| Felony | Fraud | Intentionally lying about promised actions for personal gain, or not following through with non-NT contracts. | -| Capital Offense | Impersonation of Central Command | Hiding your true identity and posing as Central Command, including CCVIP staff. | - -| J | Obstruction of Legal Justice | Impeding or abusing the legal justice system. | -| :---- | :---- | :---- | -| Misdemeanor | Contempt of Court | Needlessly interrupting or delaying official court proceedings. | -| Felony | Perjury | Lying under oath of court, or delivering false reports to Security. | -| Capital Offense | Subversion of Court | Obstructing court to the point where official court proceedings have to pause or stop altogether. | - -| M | Manipulation | Manipulating a sapient being through tactics of fear and/or aggression. | -| :---- | :---- | :---- | -| Infraction | Harassment | Unwelcome, knowing, and repeated negative conduct toward a sapient being, causing them to feel seriously uncomfortable, annoyed, or afraid. | -| Felony | Extortion | Forcing another sapient being to do something unwillingly, by means of threats, force or aggression. | -| Capital Offense | Terrorism | Causing mass station panic, or completely disrupting station operations by means of fear and/or lethal force. | - -| N | Negligence | Causing harm to the station or its crew through vocational incompetence. | -| :---- | :---- | :---- | -| Infraction | Negligence | Unintentionally performing your assigned job’s duties in a way that creates unnecessary risk or harm. | -| Misdemeanor | Endangerment | Willfully performing your assigned job’s duties in a way that creates unnecessary risk or harm. | -| Felony | Manslaughter | Killing another sapient being without intent. | -| Capital Offense | Capital Negligence | Performing a Command position’s duties in a way that causes unnecessary risk or harm, to the point of causing mass station-destruction, or rendering a department mostly inoperable, even temporarily. | - -| O | Operation | Performing works or transactions not sanctioned by NanoTrasen. | -| :---- | :---- | :---- | -| Infraction | Operation without Permit | Performing another department’s duties, or some other business venture without a legal permit of operation. | -| Felony | Black Marketeering | Engaging in the buying and/or selling of contraband. | - -| R | Rowdiness | Causing public disturbances and unrest. | -| :---- | :---- | :---- | -| Infraction | Disturbance | Catch-all for public disruptive or obnoxious behavior. | -| Felony | Rioting | Participating in unlawful protests, especially in the cases where damages are incurred. | - -| S | Obstruction of Security | Going against or obstructing lawful Security actions. | -| :---- | :---- | :---- | -| Infraction | Failure to Comply | Refusing to comply with lawful demands of Security personnel. | -| Misdemeanor | Breach of Detainment | Escaping from custody while not being free to go. | -| Felony | Breach of Arrest | Breaking free of restraints during an arrest. | -| Capital Offense | Breach of Custody | Escaping from custody during or after receiving a legal sentence. | - -| T | Theft | Taking that which belongs to others. | -| :---- | :---- | :---- | -| Infraction | Petty Theft | Taking something that is mostly worthless or easily replaceable. | -| Misdemeanor | Theft | Taking something of meaningful value. | -| Felony | Grand Theft | Taking something that is critical to the person’s job or role. | - -| U | Undermining NanoTrasen Authority | Spreading dissent about or disrespecting NanoTrasen authority. | -| :---- | :---- | :---- | -| Infraction | Slander | Speaking false and harmful statements about Command or NanoTrasen. | -| Infraction | Insubordination | Disobeying Command’s orders without reasonable justification. | -| Felony | Libel | Publishing false and harmful written statements about Command or NanoTrasen. | -| Capital Offense | Sedition | Conspiring to overthrow or otherwise dismantle NanoTrasen public trust and authority. | - -| V | Intentional Violence | Causing intentional bodily harm to another sapient being. | -| :---- | :---- | :---- | -| Misdemeanor | Assault | Threatening or attempting to cause bodily harm to another sapient being. | -| Misdemeanor | Battery | Causing superficial bodily harm to another sapient being. | -| Felony | Incapacitation | Inflicting bodily harm or administering a chemical agent upon another sapient being, resulting in critical condition or unconsciousness, but not death. | -| Felony | Mutilation | Causing permanent or otherwise long-lasting damage to another sapient being’s body parts, organs, or appendages. | -| Capital Offense | Murder | Intentionally killing another sapient being. | -| Capital Offense | Prevention of Revival | Rendering a dead body unrevivable by common medical practice. | - -| W | Free Will | Depriving another sapient being of their free will and autonomy. | -| :---- | :---- | :---- | -| Felony | Kidnapping | To unlawfully restrain or transport another sapient being against their will. | -| Capital Offense | Suppression of Free Will | Permanently depriving another sapient being of their free will and autonomy. | - -| \- | Other | Independent crimes with no classification. | -| :---- | :---- | :---- | -| Infraction | Cannibalism | To consume a portion of another sapient being, without express consent. | -| Misdemeanor | Animal Cruelty | Inflicting excessive harm on a living being, except when required for medical treatment, scientific research, or the preparation of food. | -| Misdemeanor | Failure to Pay a Fine | Failure to pay a legally imposed fine within the required timeframe. | -| Felony | Bribery | Offering or giving gifts, money, or favors to influence Command to act outside of their allowed duties. | -| Felony | Tax Evasion | Not paying NanoTrasen-mandated scrip taxes, or using non-scrip currencies to avoid paying taxes. | -| Capital Offense | Refusal of Lawful Implantation | Refusing to accept a lawful implant from Security personnel while in custody. | -| Capital Offense | Breach of NT Contract | Violating the terms of an NT-issued, signed contract. | - ---- - -## 8. Contraband Classifications - -### Contraband Confiscation Procedures -Contraband Classifications follow broad categorizations based on object purpose, rather than a strict, specific list. Higher ranking personnel can override or specify contraband with the following chain of authority: -* Central Command Officials -* Captain -* Head of Personnel -* Judicial Officer - -Enforcement personnel are to avoid unreasonable confiscation of items in order to maintain positive public relations between crew, security, and command. - -### Contraband Classifications -A single item may have more than one contraband classification, but only the highest charge is applied per item. - -**Weapon** -Objects with a heightened effectiveness for violence or killing. -Minor: Improvised item used as a weapon. -Moderate: Items that are purpose-made to be a weapon. -Major: Highly lethal weapon. - -**Unsanctioned Equipment** -Equipment that is restricted to a certain department or job. -Minor: Common, departmental equipment. -Moderate: Equipment that is critical to the department’s function. -Major: Command-Exclusive, unique equipment. - -**Operational Hazards** -Objects that pose a heightened threat to the operational safety of the station, that are not explicitly issued by a department to do one’s job. -Minor: Common, mostly harmless equipment. -Moderate: Local scale threat to operational safety. -Major: Large scale threat to operational safety. - -**Chemical** -Substances capable of influencing the mind or harming the body when metabolized or used in a reaction. -Minor: Restricted Recreational Drugs & Medicines with Low-Risk ODs. -Moderate: Exploitable Stimulants, Medicines with High-Risk ODs, & Minorly Dangerous Reactive Substances. -Major: Lethal Poisons, Highly Inhibiting Chemicals, & Highly Dangerous Reactive Substances. - -**Propaganda** -Objects that support non-NT entities, or paints NT and its subsidiaries in a false light. -Minor: Items that carry branding from Non-NT organizations, with low-risk of exposure to other crew. -Moderate: Items that carry branding from enemies of NT, paint NT as an organization in a false light, or lesser items with wide exposure to other crew. -Major: Items that carry branding from terrorist organizations, paint NT Command in a false light, or lesser items with station-wide exposure to other crew. - -**Classified Media** -Media containing information from above the carrier’s clearance level. -Any classified media is Major Contraband. - ---- - -## 9. Legal Exemptions - -### Security Exemptions -Security personnel are explicitly exempt from the following crime categories, so long as the action is following standard protocol and taken to perform enforcement duties: -Access: For the case of legal, necessary searches of a department. -Contraband: For their standard-issue service weapons and security equipment. -Theft: For legal confiscations of contraband. -Violence: For necessary force to carry out arrests. -Free Will: For restraining detainees and holding prisoners in custody. - -### Medical Exemptions -The Paramedic is explicitly exempt from the following crime categories, so long as the action is done following standard protocol and taken to perform life saving operations: -Access: For the case of medical emergency - -### Engineering Exemptions -Engineering personnel are explicitly exempt from the following crime categories, so long as the action is following standard protocol and taken to perform emergency repairs: -Access: For the case of effecting emergency repairs - -### Clown Exception -The clown gets a privilege to be able to commit Infraction or Misdemeanor level crimes for pranks, as long that: -The pranks do not cause bodily harm. -Damages caused are reversed at the end of the bit. -In case the clown gets taken to court, the presiding judge determines if the bit was funny and the clown exception holds. - -### Loss of Free Will -In the event that a sapient being is under the influence of effects that completely suppress or control the being’s free will, any charges should be dropped upon the removal of said influence. - ---- \ No newline at end of file diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md deleted file mode 100644 index e545fc0f..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 3 - Standard Operating Procedure.md +++ /dev/null @@ -1,419 +0,0 @@ - -# Article III - Standard Operating Procedures - -## Table of Contents: -1. Command -2. Central Command -3. General Crew -4. Security -5. Legal -6. Logistics -7. Engineering -8. Medical -9. Science -10. Service - ---- -## 1 | Command: - -### All Command Personnel are to: - -1. Ensure the operational efficiency and safety of the station, primarily for their own department. - 1. Command is to ensure that their subordinate crew members and departmental assets are in working condition, and up to NanoTrasen Standards. -2. Uphold NanoTrasen’s authority and dignity upon their station. - 1. Command staff must never use any language or outwardly express opinions about NanoTrasen that may be considered defamatory or overtly negative. -3. Maintain confidentiality concerning NanoTrasen Corporate Secrets. - 1. Command is to report any breaches of confidentiality to Internal Affairs. -4. Communicate and coordinate with other departments, primarily through their respective Heads of Staff. - -### The Captain is to: - -1. oversee all Command Personnel to ensure that the station’s departments are operating as intended. -2. coordinate with Command Personnel and Central Command VIPs about any ongoing situation on station. -3. ensure that any issues arising between Command Personnel are resolved. -4. ensure that the satisfaction of the crew does not rise to levels that could interfere with Nanotrasens objectives. -5. ensure that Nanotrasen Colonial Law and Procedure is being enforced, in conjunction with Central Command VIPs. -6. ensure the safety of the station's nuclear authentication disk at all costs. - -### The Executive Officer is: - -1. to not provide higher levels of access to personnel without receiving authorization from the relevant Command Personnel for that access. If an access is not restricted to a department or position, the HoP may use their discretion. -2. to issue warrants to security should there be a valid reason for the warrant. - 1. Temporary IDs may be created for the servicing of a departmental search warrant. -3. to not leave their office unmanned if there are personnel waiting in line. -4. to respond to all requests for processing in fifteen (15) minutes or less. -5. to monitor the crew for any complaints that may agitate the crew as a whole and report them to the rest of the Command Personnel. -6. permitted to run advertising campaigns for services and products across the station.Campaigns should: - 1. avoid being disruptive to essential station activities - 2. promote products in a manner consistent with Nanotrasen Values. - 3. avoid becoming an expense greater than the value provided by the campaign. - 4. take payment for any services advertised that are not provided officially by Nanotrasen.__ -7. monitor major legal decisions in order to raise necessary concerns and authorizations to the Captain. - -### The Head of Security is: - -1. to take orders directly from the Captain (and nobody else) and ensure the station remains safe and secure. -2. to ensure that the conduct of security officers is within the bounds of Corporate Law and their Standard Operating Procedure. -3. to ensure a smooth transition of power between Captains, as a result of either a Vote of No Confidence or the Captain stepping down. -4. permitted to deputize members of the crew should their skills be required for a specific assignment. -5. to monitor any hostile actions taken by unions and properly respond. -6. to ensure the gear used by security personnel is properly stored away. - 1. Weapons must be stored inside of the armory unless they are a standard issued sidearm. - 2. Lockers and EVA suits must be locked. -7. not to permit unauthorized security personnel into the armory unsupervised. - 1. The armory doors should not be set to emergency access. - -### The Research Director is: - -1. to keep a log of all anomalies and artifacts. -2. to dispose of any anomalies or artifacts that pose a risk to the station or Nanotrasen assets at a large scale. - 1. The actual disposal may be handed off to a Scientist. -3. permitted to change the onboard artificial intelligence’s laws, permitted they receive approval from the captain. -4. permitted to change any cyborg’s laws, so long as this is done for purposes of experimentation. - 1. Re-lawing a Cyborg is always permitted should they be considered compromised. -5. In conjunction with the Chief Engineer, ensure telecommunications is properly maintained. -6. to decommission the onboard artificial intelligence at the end of the shift, ideally securing it to an Intellicard. -7. to announce the generation of any anomalies to the crew. - -### The Chief Medical Officer is to: - -1. ensure that all personnel capable of being recovered and resuscitated are. - 1. prioritizing personnel based on rank. -2. ensure that all crew who come to the medical bay are treated to the point they can return to work. -3. ensure that no narcotics or otherwise illegal substances are produced in the chemistry laboratory. -4. prevent any dangerous chemical substances or biohazards from being released outside of the chemistry laboratory or virology wing. -5. ensure insurance information is being properly collected and processed. -6. ensure that the medical bay and related facilities are adhering to Nanotrasen Cleanliness Regulations. - -### The Chief Engineer is to: - -1. ensure that the station is maintained by the engineers, prioritizing the repairs of critical areas. -2. mark any areas that are unsafe and too damaged or unsafe to repair as condemned. -3. ensure that all engines powering the station are adequately maintained by the engineers. -4. ensure that distribution air is set to a safe mixture and pressure. -5. ensure that engineers prevent and contain any fires or other hazards that may appear. -6. inspect new constructions to ensure they adhere to the Nanotrasen Building & Expansion Regulation. - -### The Quartermaster is to: - -1. ensure that all approved orders are delivered within fifteen (15) minutes of being approved. -2. deny all requests for security equipment unless the proper requisition form is submitted with the Head of Security’s stamp. -3. ensure that any requests for non-standard equipment are either authorized by the order's Head of Staff or approved by the relevant Head of Staff for the order in question. -4. ensure that materials collected by the salvage team or produced by botany are distributed to departments based on their need for materials. -5. oversee the Hospitality Director to ensure that service is functioning properly. - 1. The Quartermaster should act only as a supervisory body to the service department. - -### The Hospitality Director is: - -1. to ensure the service department runs properly and profitably. -2. to keep all areas of the service department stocked to the necessary levels. -3. to ensure that all available services are provided to the crew as a whole while they are on a union-mandated break. -4. to schedule events strategically to bolster crew morale. -5. permitted to prohibit any non-Command patron from entering the Service area in response to any abusive, inappropriate, and/or unsanitary behaviour. - 1. This prohibition does not cover hallways in or around the area. -6. to ensure that both the Bar and the Kitchen are staffed. In the event that they are not, the Hospitality Director must make an active effort to fill that position, with either service workers or new hires. - 1. Service workers are preferred for staffing internal positions. -7. to review all expenses submitted to them, and deny any that are not cost effective. - -## Adjustments for Acting Command - -Acting Command, while still held to the same SOP as the standard position, are allowed more lenient treatment under most SOP. Acting Command are, however, expected to ensure that the department functions to the proper standards. - ---- - -## 2 | Central Command: - -### The NanoTrasen Representative is to: -1. coordinate with the Captain and Executive Officer to ensure that Standard Operating Procedure is being followed and adequately enforced. -2. assist and advise any Command members on the proper enforcement of Standard Operating Procedure. -3. advise any local Internal Affairs Agents on Standard Operating Procedure. -4. Communicate and advocate for NanoTrasen Policy aboard the station. -5. produce regular reports about station happenings, and fax them to Central Command -6. act as oversight for any proposed votes of no confidence. - - This includes ensuring that all votes are properly counted and recorded. -7. resolve any Standard Operating Procedure related disputes locally if possible. - ---- - -## 3 | General Crew: - -### Assistants are to: - -1. apply for open positions with the Head of Personnel. - - a. Assistants are not required to take positions that they have no skill in, but they should make an effort to help any short-staffed departments. -2. make themselves available to assist working staff with any unskilled or menial labor. - - a. Assistants answer directly to the Head of Personnel, and should work with them to find tasks throughout the shift. -3. undertake unorthodox business ventures only if they receive express approval and a permit, from the Head of Personnel. - - a. Business ventures should benefit the station in some way, and not undertaken purely for personal profit. - - ---- - -## 4 | Security: - -### All Security Staff are to: - -1. Answer directly to the Head of Security and Warden. -2. Enforce the law in accordance with NanoTrasen Corporate Law Protocol. -3. Uphold and maintain NanoTrasen’s authority. -4. Follow the Security Rules of Conduct. - - -### The Warden is to: - -1. Maintain the safety and security of the brig. -2. Ensure proper treatment of prisoners, in accordance with Corporate Law protocol. -3. Manage and maintain the armory. - - a. The Warden should keep stock of the number and type of weapons within the Armory. - - b. The Warden is responsible for ordering and maintaining material stockpiles for ammunition and weaponry production. - - c. The Warden is responsible for issuing weapons, and ensuring their safe return upon orders on the orders from the Head of Security. -4. Log and update criminal records. -5. Coordinate with the Head of Security to help monitor and direct officers. -6. Avoid performing normal officer duties unless absolutely necessary. - -### The Detective is to: - -1. Focus on gathering evidence for ongoing investigations, or court determinations. -2. Use disguises or alternate IDs only for the sake of investigation, and with permission from the Head of Security. -3. Avoid performing normal officer duties unless absolutely necessary. - -### Security Cadets are to: - -1. Read all of Corporate Law before doing any field work. -2. Request that the Head of Security assigns them a partner for practical training. - ---- - -## 5 | Legal: - -### The Judicial Officer is to: - -1. Hold court hearings and trials in accordance with NTCLP Article 5. -2. Ensure that hearings and trials are fast and efficient, but still as thorough as necessary. - - a. The Judicial Officer is to ensure that time and resources are not spent on frivolous cases, and that the type of proceeding is held in accordance with severity and importance. - - b. The Judicial Officer is to ensure that lesser court proceedings do not overly interrupt or impede more important station functions. -3. Communicate with the Executive Officer regarding major court decisions. - -### Internal Affairs Agents are to: - -1. Prioritize answering court summons and requests for representation above other duties. - - a. IAAs are primarily to represent the side of NanoTrasen in court, whether it be prosecution or defense. - - b. IAAs may only represent a party against NanoTrasen in the complete absence of a Lawyer. -2. Ensure Standard Operating Procedure is being properly followed, and to report breaches and concerns to the relevant Head of Staff. -3. Produce regular departmental audits and reports, and present them to the Executive Officer for review. - -### Lawyers are to: - -1. Prioritize answering court summons and requests for representation above other duties. - - a. Lawyers may represent the side of NanoTrasen if necessary, but should defer the responsibility to any present Internal Affairs Agents. -2. Avoid obstructing Security duties, unless specifically requested by an enforcement authority. -2. Provide legal advice upon request. - ---- - -## 6 | Logistics: - -### Cargo Technicians are: - -1. ensure that all approved orders are delivered within fifteen (15) minutes of being approved. - -a. Items produced on station should be delivered in ten (10) minutes. -2. to contact the Quartermaster for approval should there be any requests for security equipment or other departmental equipment. -3. to charge a value in scrip for any requests made from the lathes. - -a. The value charged should not be changed between requests without approval from the Quartermaster. -4. to keep a copy of all order forms are stored inside cargo or with the Quartermaster. -5. to deliver by mail, all packages can be delivered by mail and do not require the signing of a blue slip. -6. to ensure that incoming mail from other departments is sorted and processed. -7. to ensure that at least one person is handling personal mail delivery, should the mail teleporter be turned on. -8. not to order non-essential items using the station's supply account, unless otherwise authorized by the Quartermaster. - -### Salvage Technicians are: - -1. to ensure that all materials and resources collected are transferred to the station's cargo department promptly. -2. to preserve the integrity of the team and prevent losses to fauna and mining accidents. -3. to avoid dangerous areas when identified, unless rescuing a fellow crew member. -4. to coordinate shuttle movements in order to prevent marooning. - -a. There should be an in-person headcount before moving locations. -5. to communicate their team’s GPS coordinates before beginning salvage operations. -6. not permitted to hand over contraband found on expeditions to the crew. -7. to not utilize any contraband found on expeditions while on station. - -### Botanists are: - -1. permitted to grow experimental plants, but may only distribute them with the approval of the Quartermaster. - - a. Poisons may not be created under any circumstances. -2. provide other service department locations with produce on request. - - a. Botanists are not to charge for the produce unless it would be an undue burden to produce. -3. not to allow unregulated plant life outside of botany. - - a. Exceptions may be made by the Quartermaster. - ---- - -## 7 | Engineering: - -### Engineers are to: - -1. ensure the station is maintained to the point where all in use or non-condemned areas are habitable and functional. -2. ensure that the distribution air is a steady mix breathable for a majority of species on the station. - - a. This should be completed within ten (10) minutes of shift start. -3. ensure that power is supplied to the station. - - a. Initial engines should be online within twenty (20) minutes. -4. ensure that all engines that are activated during the shift are either maintained and refueled or properly decommissioned. -5. ensure that one (1) engineering hardsuit is available inside of engineering for use at all times. -6. not create any hazardous environments outside of engineering secured areas. -7. ensure backup power sources are ready for use should there be a need for additional power production. - - a. This does not include the SMES or other battery power. -8. urgently respond to any request for work from command. -9. respond to any reasonable requests for repairs from the crew. - ---- - -## 8 | Medical: - -### Doctors are: - -1. to ensure the proper and effective treatment of all injuries sustained by the crew. - - a. Command members should be treated first, then security officers, then regular crew. -2. to collect payment or insurance information before discharging a patient. -3. required to treat any crew who are admitted to the medical bay. - - a. This excludes any patients who are actively and intentionally self-harming. -4. to treat patients in private rooms unless they have only minor injuries. - - a. Command members should always be admitted to a private room. -5. to place any unrevivable patients into the morgue or a body bag inside of the morgue. - - a. The head of their department should be notified of their passing. - - b. Items from said patients should be returned to their respective departments. - - c. Post mortem instructions should be followed. -6. to keep at least one (1) defibrillator charged and inside of the medical bay at all times. -7. to ensure all clothing they are wearing is clean and sterile. -8. to ensure the medical bay and related facilities, and all equipment in use is clean and sterile, or otherwise in a hygienic state as defined by the Nanotrasen Cleanliness Regulations. -9. not permitted to leave the medical bay if there are patients that need to be treated. - - a. Patients should never be left unattended, even if they are properly treated. - -### Paramedics are to: - -1. prioritize the retrieval of patients based on rank. -2. cooperate with the relevant crew for the retrieval of patients in a dangerous location. - - a. Areas cordoned off by security may be entered if the rescue is located inside of that area. -3. stabilize all patients before transporting them. -4. transport dead patients to the medical bay should revival in the field be impractical. -5. carry requisite medicines and equipment for treatment of patients at all times. - -### Chemists are to: - -1. ensure that the medical bay is stocked with medication to handle Brute, Burn, Airloss/Bloodloss, and Toxin damage. - - a. Chemists are not permitted to exit the medical bay until this is fulfilled. -2. receive approval from the CMO before creating any experimental mixes. -3. not provide the crew with dangerous chemicals outside of bounties. -4. charge for any chemicals handed out to crew that are not related to bounties. -5. report any strange, unusual, or unknown chemicals they create or receive to the CMO. - - a. Such chemicals are not to be distributed. -6. ensure the chemistry laboratory and related facilities, and all equipment in use is clean and sterile, or otherwise in a hygienic state as defined by the Nanotrasen Cleanliness Regulations. - -### Psychologists are: - -1. not permitted to force treatment upon a patient unless it is required as part of a criminal sentence. -2. to not share a patient's mental condition or trusted information to anyone other than the patient. - - a. This does not include evaluations that are made for prisoners. -3. to report to the relevant command member should they find any non-command crew unfit for duty. -4. permitted to prescribe any medicines they find necessary for a patient. - ---- - -## 9 | Science: - -### Scientists are: - -1. not permitted to bring artifacts outside of science without the use of an artifact container. -2. to ensure that every anomaly created is either destroyed or properly contained. - - a. Contained anomalies must be checked whenever there is a change in the vessel's status. - - a. This does not apply if the containment is automated. -3. not to generate anomalies without approval from the research director. -4. to document anomalies and artifacts and submit the documentation to the Research Director. -5. to ensure a member of science personnel (or an assistant hired by science) is manning the front desk. - - a. Whoever is manning the front desk must adhere to the Science Distribution Regulations. - ---- - -## 10 | Service: - -### Service Workers are to: - -1. assist other members of the service department when requested. -2. fill in for other positions in the service department when needed. - - a. Service Workers should follow a positions SOP when acting as that position -3. promote a collaborative atmosphere in the service department. -4. only begin side tasks after checking with other members to see if they require aid. -5. oversee the work of any assistants that are aiding the department. - -### Bartenders are to: - -1. ensure that orders are properly taken and served in a timely manner. - - a. ensure that all beverages are made fresh or stored inside of a dispenser or smart fridge. -2. collect payment or open a tab on all orders before serving the patron. - - a. collect all payments on all tabs open within an hour of that tab opening. -3. not serve potentially dangerous drinks to patrons without a waiver of liability reviewed by a lawyer. -4. keep the bar open during all union-mandated breaks, except for breaks of the service department. -5. not consume any beverages within view of customers while on-duty. -6. ensure the bar complies with the Nanotrasen Health Regulations. - -### The Chef is: - -1. to ensure that orders are properly taken and served in a timely manner. -2. to collect payment on all orders before serving the patron or before they leave the service area. - - a. Discounts may be offered for large orders. -3. to ensure that food for all species on board is available to be produced should it be ordered. -4. to keep the kitchen open during all union-mandated breaks, except for breaks of the service department. -5. not consume any food within view of customers while on-duty. -6. to ensure the kitchen complies with the Nanotrasen Health Regulations. -7. to dispose of food that is not consumed within 15 minutes of it being produced. -8. permitted to produce food using light narcotics as long as they are legal and will not impede the work of the station. -9. permitted to leave the kitchen unattended for the purpose of catering an event. - - a. This is not permitted if the event is during a union-mandated break, unless it is catering for that break. - - a. Payment must be collected for services rendered, along with a catering fee. - - a. a Bartender may be asked to provide drinks for the event, the cost of which should be included in the charge to the customer. -10. to not serve dangerous food to patrons without a waiver of liability reviewed by a lawyer. - -### Janitors are to: - -1. ensure all public parts of the stations are properly maintained according to Nanotrasen Cleanliness Regulations. -2. report any damage to the station to engineers as soon as possible. -3. assist any department with cleaning within 15 minutes of the request being made. - - a. Janirots should ensure that any cleaning made to a department is done in accordance with the relevant regulations. -4. restock any vending machines that are low on supplies or out of a particular item. - - a. The cost of restocks may be taken from the service department’s account. -5. prioritize any possible biohazards over other duties. -6. charge for any cleanings made in private, non-department locations. - - -### The Clown is: - -1. not permitted to remove their Clown Shoes or Clown Mask. - - a. an exception is made should it be truly necessary for the sake of their performance. (such as a satire of bad clowns) -2. to not endanger other personnel with pranks. -3. to attempt to be legitimately funny or entertaining at least once every fifteen (15) minutes. -4. permitted to expense the following to the service department account for pranks or performances: - - a. Special Talent or Hires - - b. Props - - c. Alterations to the stage - -### The Mime is: - -1. to never speak. Any mimes that speak are to be removed from their position post haste. -2. to use written words or AAC tablets only as a last resort or in an emergency. - - a. this includes other non-miming forms of communication. -3. expected to perform an act of Mimery at least once every fifteen (15) minutes. -4. permitted to hire special talent or side performers for plays. -5. permitted to expense the following to the service department account for performances: - - a. Special Talent or Hires - - b. Props - - c. Alterations to the stage - -### The Librarian is to: - -1. Keep a log of any and all loaned out books. -2. Keep the library organised. - - a. The floor of the library must be free of loose books. - - b. Shelves must be labeled according to a sorting system. -3. Ensure the quiet and sanctity of the library are preserved. -4. Ensure there is no drinking or eating within the confines of the library. -5. Ensure members of the crew have access to the library. -6. Ensure the wellbeing of all books on station. diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 4 - Unions.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 4 - Unions.md deleted file mode 100644 index e69de29b..00000000 diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 5 - Sentencing, Trials, and Hearings.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 5 - Sentencing, Trials, and Hearings.md deleted file mode 100644 index fc230b4b..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/Article 5 - Sentencing, Trials, and Hearings.md +++ /dev/null @@ -1,354 +0,0 @@ -# Sentencing, Trials, and Hearings - -## Table of Contents: - -1\. Legal Definitions -2\. Sentencing -3\. Court Proceedings -4\. Classified Court Proceedings -5\. Captain’s Mast ---- - -## **1\. Definitions** - -Judge: The current legal arbiter of a trial or hearing. -Prosecution: The party pressing charges. -Defendant: The party being accused. -Defense: The party representing the defendant: May be the defendant themselves. -Charge: An accusation of a crime. -Sentence: An official judgment of a crime committed and accompanying punishment to serve. -Plea: An official statement in court from the Defendant about whether they are guilty or innocent. -Verdict: An official determination of guilt, by the presiding Judge. - ---- - -## **2\. Sentencing** - -Sentencing is the act of determining a suitable punishment for convicted criminals. -The presiding Judge determines the sentence after they have made an official verdict. - -### **Processing Priority** - -At any given time, at least one legal authority must be in charge of sentencing aboard the station. -Typically, this is the Judicial Officer, but in their absence, the responsibility falls upon the following order of succession: - -1\. Judicial Officer -2\. Executive Officer -3\. Captain - -The Judge is responsible for: - -* Determining which level of hearing is suitable for the charges. -* Delivering a verdict: Whether or not the defendant is guilty. -* Determining a sentence: The amount of brig time and/or alternative punishments to assign. - -The Captain still holds the most legal authority aboard the station, and has the final say in any legal matters. - -### **Standard Punishment Lengths** - -The following times are to be used as a baseline, based on the severity of crime committed: - -* Infraction: No brig time. -* Misdemeanor: 10 minutes. -* Felony: 20 minutes. -* Capital Offense: Permanent. - -### **Executions** - -At the Judge’s discretion, a permanent sentence may be raised to an execution. -Any executions need express permission from the presiding Captain, and cannot be authorized in the absence of one. - -Executions are recommended only when multiple Capital Offense charges have stacked, or if a single Capital Offense has been aggravated multiple times. - -### **Crime Categories and Stacking Crimes** - -Charges from the same Crime Category cannot be stacked for the same sentence. Only the highest offense in that category will be counted. - -Multiple crimes from different categories can stack freely, up to a maximum time of 40 minutes. -If the brig time exceeds 40 minutes, the Judge is recommended, but not required, to elevate the punishment to Permanent Confinement. - -The Judge may choose to elevate a permanent sentence to Execution, if multiple Capital Offenses were committed at the same time. - -### **Aggravating Circumstances** - -Aggravating circumstances increase the severity of a punishment. -At their discretion, the Judge may decide to simply increase the punishment, or to elevate the crime tier by one level. - -**Attempted/Planned Crime**: -Attempted or planned crimes are to be charged as the full crime committed, so long as there is clear evidence. A crime should not be charged as attempted if there is a more fitting lesser crime. - -**Alert Level**: -Committing a crime that directly goes against restrictions placed during a heightened alert level, or directly goes against a public announcement made by Command. - -**Brutality**: -The crime was committed recklessly, with no regard for collateral damage, and/or with a complete lack of remorse. - -**Evasion of Enforcement**: -The defendant greatly resisted arrest, or otherwise evaded and obstructed security from charging them. - -**Parole Violation**: -The crime was committed while the defendant was on parole, or serving an alternative sentence. - -**Privileged Victim**: -The crime was committed, and concerns a member of high ranking or authority under NanoTrasen. - -**Repeat Offense**: -The Defendant has already been sentenced for the same crime this shift. - -### **Extenuating Circumstances** - -Extenuating circumstances decrease the severity of a punishment. -At their discretion, the Judge may decide to simply decrease the punishment, or demote the crime tier by one level. -The Judge may also decide to waive punishment entirely, but the Judge is recommended to use this power sparingly. - -**Cooperation**: -The defendant cooperated with Security personnel and did not resist. - -**First Offense**: -The defendant has no criminal record this shift, and only committed the single charged crime. - -**Enforcement Incompetence**: -Security used excessive force to perform the arrest, took excessive time to process the defendant, or otherwise greatly inconvenienced the justice process. - -**Self-Defense**: -The crime was committed in self-defense. - -**Self-Reported**: -The defendant turned themselves into Security, and/or willingly returned any stolen property. - -**Necessity** -The defendant has shown that the crime they committed was necessary to prevent some greater harm. - -**Victim Involvement**: -The victim personally requested that the charges should be dropped or reduced. - -### **Alternative Punishments** - -Alternative punishments may be offered as a replacement or reduction to brig time. -The Defense can argue for alternative punishments, but the sentence is ultimately up to the Judge. -Possible alternative punishments are listed below: - -**Community Service/Station Labor**: -The detainee agrees to serve some time performing hard labor for the station while under watch by Security, or while in confinement. - -**Demotion**: -The defendant loses their current job and is hired to the position below them. - -**Disclosure**: -The defendant agrees to reveal incriminating information about their accomplices, or any other critical information relevant to station security. - -**Financial Compensation**: -The defendant agrees to pay scrip to the victims, to cover the cost of the crimes committed. - -**Reverse Damages**: -The defendant promises to reverse damages, or reveal the location of stashed stolen goods. - -### **Parole** - -The Judge may offer parole if they deem the defendant capable of genuine reform. -Parole can be discussed with a representative lawyer, after the prisoner has served at least half of their sentence, or 20 minutes in the case of permanent sentences. -The Judge is highly recommended to consider parole offers that result in increased productivity and profits to NanoTrasen. -The Judge, with the Warden’s express approval, is highly encouraged to have a Security Officer assigned as the defendant’s parole officer. -Parole may have additional conditions, as listed below: - -**Community Service/Station Labor**: -The detainee agrees to serve some time performing hard labor for the station while under watch by Security, or while in confinement. - -**Character Reform**: -The detainee agrees to an appointment with a station Psychologist or Chaplain, who evaluates their level of remorse and likelihood to reform. - -**Free Parole**: -Detainees expressed good behavior while in custody, and may be tentatively freed from their sentence, so long as they check up with security regularly. Security may choose to require them to use a Bodycam, Electropack, and/or Tracking Implanter. - ---- - -## **3\. Court Proceedings** - -There are multiple types of court proceedings, held based on the severity of the charges. -It is up to the Judge to select which proceeding should be held, and to determine which cases are sufficient to go to Trial. - -### **Summary Hearings** - -A quick, informal judgment for minor offenses. -Held for Misdemeanors. -Also held when protesting an Infraction. -Target time is 1-2 minutes. - -### Prosecution: - -* Arresting Officer -* No one, in the case of a protested Infraction. - -### Defense: - -* Defendant self-representation. -* The defendant may request a lawyer, but their sentence will be paused until the lawyer arrives, and during any consultation. - -### Witnesses: - -* Witnesses are not allowed. NT will not waste valuable productive time on a Summary Hearing. - -### Procedure: - -1\. Prosecution reads their charges. -2\. The Judge proposes a sentence for these charges, and asks if the defense pleads guilty. -3\. If the defense pleads not guilty, they state their case and present any relevant evidence. -4\. The Judge reviews the defendant’s case, and adjusts their sentence if necessary. -5\. The Judge closes the case with their verdict, and the officer either lets them go free or escorts them to the brig to serve, as necessary. - -### **Formal Hearings** - -Lengthier, formal hearings for more severe crimes. -Held for Felonies. -Also held for Capital Offenses that do not wish to escalate into a Trial. -Target time is around 15 minutes. - -### Prosecution: - -* Arresting Officers must have an Internal Affairs Agent represent them as prosecution, so that they may return to their duties should it be needed. - -### Defense: - -* A lawyer must be offered to represent the defendant. -* The defendant can still choose to self-represent, but it is not recommended. - -### Witnesses: - -* Witnesses are only allowed if it is absolutely essential to the determination, and to a maximum of one per side. -* Witnesses may not be allowed to be Command, Security, or other essential jobs that cannot afford to be away from their post. - -### Procedure: - -Pre-Hearing Consultation: - -* Both sides may briefly consult with their representation, before the Trial officially begins. -* Consultations are confidential. Statements said in consultation never have to be disclosed. -* There is no strict time limit on consultation, but time spent consulting does not reduce any eventual sentence. -* Both sides are recommended to plan for and consider: - * Whether they will plead guilty or not guilty. - * What witnesses, if any, they intend to call. - * Whether any aggravating or extenuating circumstances apply. - * Whether a plea deal for an alternative punishment is worth pursuing. - -1\. Opening - -* The Judge identifies all participating parties, and reads the formal charges aloud. - -2\. Plea - -* The Judge formally asks: “How does the Defendant Plea?” -* If the Defense pleads guilty, skip to step 5 (Sentencing) -* If the Defense pleads not guilty, proceed. - -3\. Presenting Cases - -* The Prosecution presents their case in its entirety, followed by the Defense in its entirety. -* Any physical evidence must be formally presented before the Judge, and entered into the record before it can be referenced in argument. -* Each side may bring their witnesses to the stand and question them directly. - * After each witness, the opposing side may briefly cross-examine. -* The Defendant may choose to testify. If they do, they are subject to cross-examination. - -4\. Verdict - -* The Judge delivers a verdict on each charge. -* If the Defense is found Not Guilty on all charges, the hearing closes immediately. - -5\. Sentencing - -* Both sides may now argue for aggravating or extenuating circumstances that should influence the sentence. -* Either side may also propose a plea deal, for an alternative punishment in lieu of standard brig sentencing. -* The Judge considers these arguments and issues their final sentence. - -6\. Closing - -* The arresting officer either releases the defendant or escorts them to serve their sentence, as appropriate. - -### **Trials** - -Extremely in-depth, formal procedure, only for the most severe crimes. -Held only when the defense chooses to escalate a Capital Offense charge to a Trial. -May only be held with a NanoTrasen-approved Judicial Officer, not an acting Judge. -No target time. May be as long or as short as necessary for the Judicial Officer to come to a verdict. - -### Prosecution: - -* Arresting Officers must have an Internal Affairs Agent represent them as prosecution, so that they may return to their duties. - -### Defense: - -* A Lawyer must be offered to act as the accused’s defense. -* The accused can still choose to self-represent, but it is not recommended. - -### Witnesses: - -* Witnesses are allowed and encouraged. -* Witnesses can be anyone, including Security and Command. - -### Procedure: - -Pre-Trial Consultation: - -* Both sides may briefly consult with their representation, before the Trial officially begins. -* Consultations are confidential. Statements said in consultation never have to be disclosed. -* There is no strict time limit on consultation, but time spent consulting does not reduce any eventual sentence. -* Both sides are recommended to plan for and consider: - * Whether they will plead guilty or not guilty. - * What witnesses, if any, they intend to call. - * Whether any aggravating or extenuating circumstances apply. - * Whether a plea deal for an alternative punishment is worth pursuing. - -1\. Opening - -* The Judicial Officer identifies all participating parties, and reads the formal charges aloud. - -2\. Plea - -* The Judicial Officer formally asks: “How does the Defendant Plea?” -* If the Defense pleads guilty, skip to step 9 (Allocution) -* If the Defense pleads not guilty, proceed. - -3\. Opening Statements - -* The Prosecution gives a brief summary of what they intend to prove, and how. -* The Defense gives a brief summary of their argument or facts they intend to dispute. - -4\. Presenting Cases - -* The Prosecution presents their case in its entirety, followed by the Defense in its entirety. -* Any physical evidence must be formally presented before the Judicial Officer, and entered into the record before it can be referenced in argument. -* Each side may bring their witnesses to the stand and question them directly. - * After each witness, the opposing side may cross-examine. -* The Defendant may choose to testify. If they do, they are subject to cross-examination. - -7\. Closing Arguments - -* The Prosecution presents their closing argument, then the Defense. - -8\. Verdict - -* The Judicial Officer determines Guilty or Not Guilty for each charge. -* If the Defendant is found Not Guilty on all charges, the Trial closes immediately. - -9\. Allocution - -* The Defendant is given the floor to address the court directly and personally. -* They are not to be interrupted, cross-examined, or objected to in any way. -* This is the Defendant’s opportunity to explain themselves, apologize, or appeal to the court’s mercy. - -10\. Sentencing - -* Both sides may now argue for aggravating or extenuating circumstances that should influence the sentence. -* Either side may also propose a plea deal, for an alternative punishment in lieu of standard brig sentencing. -* The Judicial Officer considers these arguments and issues their final sentence. - -11\. Closing - -* The arresting officer either releases the defendant or escorts them to serve their sentence, as appropriate. - ---- - -## **4\. Classified Court Cases** - ---- - -## **5\. Captain’s Mast** diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-1_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-1_design_doc.md deleted file mode 100644 index 2604face..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-1_design_doc.md +++ /dev/null @@ -1,209 +0,0 @@ -# Nanotrasen Colonial Law and Procedure: Station Regulations - -| Designers | Implemented | GitHub Links | -|---|---|---| -| SOP workgroup, Document written by Scrambleking | :x: No | TBD | - -## Overview - -This document establishes a comprehensive framework for in-character station regulations intended to enhance roleplay depth, structure player interactions, and provide clear guidance in non-standard scenarios. -Rather than functioning as enforceable server rules, these systems are designed to simulate the bureaucratic, procedural, and corporate realities of a Nanotrasen-operated facility. - -The regulations outlined here expand on existing mechanics by formalizing processes such as corporate security protocols, administrative paperwork, fines, visitor interactions, and command hierarchy. -Each section is supported by game design rationale, roundflow considerations, and (where applicable) technical implementation notes to ensure both usability and immersion. - -While not all features are required for immediate implementation, this document serves as both a design foundation and a roadmap for future development, prioritizing systems that improve clarity, consistency, and player engagement without overburdening gameplay. - -## Background - -Not everything that *was* SOP or law perfectly fits within the older sections of them, as such we are creating the "station regulations" to be a catch all for NT's rules that dont quite fit into our other primary catagories. - - -# Corporte Espionage Act -This section is intended to be in direct relation to the metashield on an OOC level along with IC justifications for the Crew/Security metashields and NDAs. -In character the majority of crew would understand this as related to NT's R&D into bluespace, genetics, artifacts, and anomolies, building off of the syndicate being a known orginisation that conducts espionage. - -## Administrative & Server Rule Impact -This section will be written under the explicit perview of, or by the hand of, the head admins. - - -# Permits and Paperwork -Permits and Paperwork cover what paperwork to use, when to use it, and what utensils to use with it. -EG: - -To hire person X use Hiring Form 4.23, along with adendum 2 for hiring non-NT members - -Access is only granted after filling out Access Form 6.23 C - -Construction or modification of maints should be done with Construction Form 32.45 - -All paperwork must be filled with a black-ink pen unless specified in... - -Copies of official paperwork should be stamped by the relevant head - -## Game Design Rationale -By codifying the forms and permits it should make the system easier to navigate for newer players, and prevent abusive forms from making their way into printer files (I am personaly guilty of some of these). -Additionaly the Codification of paperwork is more authentic to a corprate experiance where files are flying about the home office every day. - -## Roundflow & Player interaction -In a round a player (just like anyone in a corporation) will know generaly what they will be required to fill out should they be asked for paperwork, and may even print and fill it out themselves, or with the help of the local librarian. - -## Technical Considerations -This section will require the implimentation of the Printing Machine. -The printing machine provides players with a way to quickly print forms in-round without needing a folder of documents they must search through. -2 versions of the printing machine should be avalible, a "secure" version for command/security use, and a "regular" version for crew use. -The "regular" version will contain documents that normal crew may need such as hiring applications, access requests, and construction permits. It will be kept in the library or simular areas. -The "secure" version will additionaly contain documents such as command/security hiring forms, NDAs, police reports ect. It will be kept behind access locked doors. - -This section will not require, but would greatly benefit from, the implimentation of fillable form fields. -This will make filling forms easier to understand for players without having to interprit rundown text. - -# Building/Construction code - -This section would define what is a "baseline" room via atmosphere, construction, types of walls/windows to use when, firelocks and air alarms, ect. - -## Game Design Rationale -In game this would serve as an effective tutorial to building and room construction for newer engineers/players, and can be referenced in the permits system for construction. -This creates a more authentic experiance to newer players and intergrates the guidebook further into the world as a "real" learning tool. - -## Roundflow & Player interaction -This should have minimal impact on roundflow outside of obtaining permits and teaching/learning construction. - -# Fines -Fines are for when things are not fine. When you commit an SOP infraction or Corprate Law based infraction you may be ordered to pay a fine. -This section explains the who, how, and why of fines. It does not explain how this is diffrent from a governmentaly approved bribe. - -Who can give them - -Why they can be given - -How to give them - -How to pay them - -It also covers the courses of action that the IAA can take. Primarily issuing a fine or asking the head of staff to take greater actions. - -## Game Design Rationale -This maintains authenticity because it provides a way for security to punish negative behavior without needing to haul the person all the way to security which would lower nantotrasen's profits. -This maximises RP potential because instead of a simple warning there is direct action taken against the person who can then chose to escalate, not pay, or dispute the fine. - -## Roundflow & Player interaction -This will provide a way for players to interact and begin escalation with security outside of reciving a warning, which is unsatisfying, and jail time, which could be over the top. - -It also provides the IAA with a more explicit path for punishments outside of taking possibly vital equiptment, or simply firing the person. - -## Administrative & Server Rule Impact (if applicable) -This section should have no administrative impact aside from role abuse, which generaly should be able to be dealt with in character with unions and escaltation. - -## Technical Considerations -Scrip is required. -We cant take away the money of someone without money. - -A fine computer/printer is not required, but could greatly benefit the system. -This would alow the security officer to print the fine recipt quickly, and the recipiant to pay it at the designated point. - - -# Extracorporate Entities -This section covers interactions with visitors to the station. Visitors are an under-used RP mechanic, and while this will by no means fix that, it will provide a direction to take the interactions with them. -The sections contained within include: - -Shuttle rights - -Docking - -Trading - -Treatment of visitors - -Refugees - -External hiring (temporary and complete contracts) - -## Game Design Rationale -Authenticaly, any large port will also have regulations for how to interact and treat visitors from other orginisations. This would be especialy true for a corprate research colony that knows of spies. - -## Roundflow & Player interaction -This is not intended to effect the flow of most rounds, but should alow for rounds that do interact with visitors to have more guidance than "oh ok, I geuss your visiting now" -Idealy this will make even mundane visitors have a level of impact with the personel on the station through things such as medical checkups and acnowladgement of visitation. - -## Technical Considerations -Maps will require a designated "visitor" dock. - -Visitor shuttles will need some way to broadcast their pressence. - -While not required, IDs and PDAs can be removed from non-NT/infiltration aligned visitors. This will also provide a noticable distinction between roles that are part of NT (such as a CMO in an escape pod), and visitation roles that are simply visiting. - -# Insurance -NOTE: Insurance is something that will not be directly added by this workgroup as it is outside of our intended scope, it is merely here as an example that could be added in the future. - -This would create a codified explanation of what each insurance level entails: - -What premiums you may have to pay each shift - -Coverage of injuries - -Coverage of non-health related surgeries - -Cybernetics - -# Alert Levels -Not exactly new, alert levels have been moved from SOP to regulations as they are called for situations that are not standard. - -General: Most alerts are un-changed in their cause/response with the following exeptions: - -Blue alert is called for a duration of up to 10 minuets while a Felony class or higher crime is under investigation (See Law Document). - -Starting at blue alerts the HoS will be slated for overwatch from security (See the Command document for more information on the HoS rework) - -Events may be canceled without warning should the situation require it. - -Violet alert grants the CMO and Captain the ability to quarantine areas of the station which may only be lifted by the CMO or Captain’s orders. -Security is given permission to enforce this quarantine through any method the captain allows. -This also requires sensors set to show health at a minimum to better track the spread of the infection - -Events may be canceled without warning should the situation require it. - -Red Alert: -RED alert now alows the captain to deem specific SOP as suspended, this replaces the SOP per alert level SOP. -This is also being done to reduce confusion about alert levels being SOP, and possibly making it enforceable by security instead of the CCVIPs which was always an odd position for them. - -Security’s restrictions on heavy weapons are also lifted and it is expected that the Head of Security and/or Warden keep track of what weapons are taken by who to account for their return when the situation is resolved. - -Departmental breaks and crew events such as in the theatre and chapel are paused for the duration of the alert. Gatherings may be broken up as needed. - -HoS will still be religated to their department outside of immediate station ending threats that will require a full response force (EG god summoning) (again see the Command document for more information on the HoS rework) - - - -# Order of Succession and Martial Law -The Order of Succession determins who will be next in line for the captain position. -EG: -1. Captain -2. HoP -3. RD -4. QM -5. CMO -6. CE -7. HD (Hospitality director, expended on in job changes) -8. Acting command with the above order -9. HoS - -This can be triggered via a vote of no confidance amongst command. This is started by the CCVIPs, or by the CMO deeming the captain as unfit for duty. - -The Head of Security will take over the station until a suitable captain replacement can be found, at which point power will be relinquished to them. -Martial law can be declared by the HoS once no other suitable replacements for the captain can be made. - -Under martial law security’s orders are final, personnel are to immediately return to their departments or bar unless given explicit permission otherwise, and failure to do so leaves punishment at the discretion of the witnessing officer. -This includes engineering and medical personnel who are responding to emergencies, and scientists responding to anomalies. - -## Game Design Rationale -This goes mostly to authenticity, in an emergancy the HoS is intended to have an overview of the security situation, while the captain has an overview of the station as a whole. -Given this is the case, the HoS should not be focused on the extrenous duties of the captain. -Additionaly the station is a Corporate orginisation who's focus is on profit, not simply "catching the bad guy" and this change is meant to highlight this. -Should all command and potential command die, the only authority on the station is the HoS and security, who should not be treating the station as lightly as a regular command member. -The reason the martial law power was specificaly granted is, should the situation become dire enough to require the HoS to become captain, they will likely be in a situation more severe than red alert. - -Martial law is not automaticaly called upon the HoS's promotion due to outlier shifts such as lowpop, or no other command in a lobby willing to play capatain. - -## Technical Considerations -Possibly an alert level for "Martial Law" can be made, or taken from an existing alert level. diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-2_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-2_design_doc.md deleted file mode 100644 index fbf759eb..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-2_design_doc.md +++ /dev/null @@ -1,117 +0,0 @@ -# Nanotrasen Colonial Law and Procedure: Corporate Law - -| Designers | Implemented | GitHub Links | -|---|---|---| -| SOP Workgroup, Document written by Joaco545 | :x: No | TBD | - -## Overview - -This proposal aims to revamp Space Law completely, while keeping the new theme direction in mind. - -Space law has been revised to conform to the style of a legal document. -The crime list has been expanded, and sentencing guidelines have been simplified. -Contraband has been vaguelawed. - - -## Background - -Funky Station has been changed to have a Corporation vs Crew, Class Conflict theme. This requires updating Space Law as it no longer fits the theme. -Currently, space law feels like something an external entity that is not Nanotrasen has set in place, and is forcing NT to comply with it; We aim to change that feeling completely. -We also took this opportunity to add some things to increase the RP potential, coupled with the [sentencing changes](article-5_design_doc.md). - - -## Features to be added - -To see all the new proposed changes to Corporate Law, please check out the [supporting doc](Article%202%20-%20Corporate%20law.md) with the draft (Still not up at the time of commiting this, for now, the things can be found on the [Google doc under the Article 2 tab](https://docs.google.com/document/d/1HhQ9L_5KLPLiYH3W9_V8gIqyjH2lBxOt-W90n76cLtY/edit?tab=t.ushwxj8tclf6#heading=h.x3qf6opli0z2). Yes Tay, this link is temporary) - -### Space Law rename -While it may not seem like much, Space Law has been renamed to Corporate Law to better fit the theme of NT owning you, the station, and all surrounding space. You are in their house, you play under their rules. - -### Corporate Law: Searches -The way searches are conducted has been reworded with a bit more legalese, and in the case of departmental searches, they have been made clearer as to what is included, and especially what's NOT included (personnel). - -### Corporate Law: Detainment and Arrests -There is now a difference between being detained and being arrested: -Detained means the person is not free to go. It is here mostly for the investigation part, not letting suspects go free until you have the evidence you need. -Arested means that the person will be guided to security for search and a subsequent trial. -In both cases, the detainees or arrestees should not be cuffed if they are complying. - -### Corporate Law: Chain of Custody -This specifies how Security is expected to play out each of the steps from arrest to the brig. This is mostly a supporting change for [Sentencing, Trials, and Hearings](article-5_design_doc.md). -This ups the standards Security personnel are held toin-character, while giving good lawyers more tools to finagle their clients out of a sentence, or at least enter a reduced one. - -### Corporate Law: Treatment of Arrestees and Prisoners -This section is kept mostly the same as the old treatment of prisoners. - -### Corporate Law: Implantation -This section is kept mostly the same as before, with a bit more legalese. - -### Corporate Law: List of Crimes -This area has been majorly reworked and expanded. NT now has more ways to get employees who are not behaving. - -#### Crime Categories -The tier system has been revamped into 4 named crime tiers: -- Infraction: They cover minor offenses, which do not lead to brig time. -- Misdomenor: They cover more serious offenses, which can lead to brig time. -- Felony: They cover serious crimes, can lead to more brig time. -- Capital Offenses: They deal with the most serious crimes against NT, can lead to permanent confinement, contract termination, or execution. - -Note: Execution requires Captain and XO (HOP) approval - -Big times have been standardized so that sentencing gets easier. They now directly depend on their category, instead of the individual crime. - -The crime list has also been expanded to give NT more power over how people and unions behave. The line between a strike and a riot is a thin one. -We expect security vs crew to increase the friction between Command and the Crew, giving more opportunities for escalation should the players choose to do so. - -#### Infraction enforment -Infractions are not meant to be something everyone needs to go to a judge for; They will be handed out by Security. -Fines can be disputed, but that requires the player to say they want to do that (See [Technical Considerations](#technical-considerations)). -As a perverse incentive, fines made by Security will go to the Security department’s budget, and the Head of Security will be able to use those funds to buy things for the team or increase the pay of Security employees. - -### Corporate Law: Contraband Classifications -Old Contraband has been replaced by Vaguelawed Contraband. To support this change, contraband markers will need to be removed from the game. -These changes were made to increase the RP potential, as now, confiscating something is a choice to be made by players, and not by a marker. -This also makes meteshielded components harder to identify, unlike the old system which made confiscation a must (Syndicate pajamas, anyone?) -It is also another way for escalation to happen is Sec confiscates too much or too little with the crew and command, respectively - -### Corporate Law: Legal Exemptions -Certain jobs may be except of certain laws under certain conditions, this includes security's monopoly on violence, or more mundane things like engi breaking into places to fix a fire. - -#### Clown Exception -The clown crime exception has been re-added for some Seriously Silly points. -It has a couple more caveats to reduce the scope of what the clown can do, while also requiring the judge to find it funny for the exemption to apply. - - -## Game Design Rationale - -A lot of these changes have been done with two pillars in mind: - -- New Theming / Authenticity - Working on an NT Space Station will now feel more oppressive for the normal workers, while unions act as a small reprieve, NT still has a lot of power inside and outside the station. It makes the story being told more coherent. - -- Escalation / Maximising roleplay potential - The features mentioned in this doc all aim to keep the same level of RP or increase it. - - -## Roundflow & Player interaction - -Corporate Law is something that will permeate each round from roundstart till evac docs on CC, and all players will have to engage with it. -Common sense will keep most players outside of Securities radar, but it will still be something present. - -Example of Non-Antag Escalation Oportunities: -As an example an assitant could get fined by security for Loitering, the assistant, not able to get the Scrip to pay the fine, gets charged with Failure to Pay a Fine. This builds up resentment, and once they are out of the brig, the look for other people wronged by sec and start a strike. -As the strike was not approved, Security tries to split up the strike. First peacefully, then by using Tear Gas. Then the thing turns violent and now there is a partial riot on the station. - -Example of Antag Shielded Contra: -A wizard appears on the station, a security officer stops them for a random search. They see some clothing and an orb, think nothing of it, and let them go. Half an hour later the wizard has killed 3 people and is captured, this time command gets involved and recognizes that the orb and clothes are used for casting the dangerous spells the wizard has been using per the CTMs info. They decide to confiscate the items saying that their combined use is like that of a major weapon - - -## Administrative & Server Rule Impact (if applicable) - -As mentioned on the main doc, with so many changes we think players will AHelp more to ask for clarification on said changes. - -## Techincal Considerations - -For infraction enfocement, two new things will need to be implemented: -- Sec will need to get a new device capable of printing fines, and; -- An ATM-like device near the courtroom that allows players to pay the fine, or give the option to page the judge for it to be disputed. diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-3_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-3_design_doc.md deleted file mode 100644 index 21787b86..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-3_design_doc.md +++ /dev/null @@ -1,104 +0,0 @@ -# Nanotrasen Colonial Law and Procedures: Standard Operating Procedure - -| Designers | Implemented | GitHub Links | -|---|---|---| -| SOP Workgroup, Document written by Gamercodeleo1 |:x: No | TBD | - -## Overview - -This doc will cover the Standard Operating Procedures Section of the new Nanotrasen Colonial Law and Procedures. The reasoning for the changes and the guidelines for the new SOP that has been written. - -## Background -This section of the Nanotrasen Colonial Law and Procedures (I'll refer to it at NCLP from now on) is designed to rework SOP to fit better with the new vision of the game post-forky. Current SOP tends towards being very oddly written, very inconsistent, and is not aligned with the new vision for the game. SOP also has a bad habit of simply being server rules, which is very counteractive to the point of SOP, which is to cause conflict. SOP that is also a rule, and thus cannot be broken, should be avoided at all costs. There has also been a focus on making command further from the regular crew, to play further into our theme of class conflict. - -## Features to be added -There are many things planned to be changed in SOP so I will give each their own section. A large part of the SOP has already been drafted. This section will cover the proposed changes and use examples from that draft. If you would like to see the draft, check the related drafts of the document under `station_protocol_rework`. - -### SOP Requirements -These are guidelines for drafting the SOP that cover how we expect SOP to be written, and things to be included. -*This section is based off of a version created by Catty.* -#### Minimum Job Requirements -This type of SOP is more about results rather than process, and is what would be expected should a player being performing their job properly. This type of SOP should cover what you do to do your job properly, and failing to do it would be a failure to perform said job, normally resulting in punishment. This is, of course, just SOP, which is ***explicitly allowed*** to be broken (OOC and server rules-wise, of course). These SOP shouldn't be made as the primary incentive for a playstyle, any changes to that should be encouraged mechanically (with a seperate design document), and then have SOP changed to match. -##### Examples (from the draft): -**Chef 3:** *[The Chef is] to ensure that food for all species on board is available to be produced should it be ordered.* -**Janitor 1:** *[Janitors are to] ensure all public parts of the stations are properly maintained according to Nanotrasen Cleanliness Regulations.* -**Engineer 1:** *[Engineers are to] ensure that the distribution air is a steady mix breathable for a majority of species on the station.* -##### Examples (from current SOP): -**Security Officer [Green] 2:** *Security Officers are required to state the reasons behind an arrest before any further action is taken. Exception is made if the suspect refuses to stop;* - -#### Roleplay and Conflict Creation -This type of SOP is more about creating opportunities for conflict or other roleplay. Ideally each job should have one or more of these. This SOP is meant to align very well with our themes of class conflict and corporate dystopia, and as such can be over the top or unreasonable (but doesn't have to be). -##### Examples (from the draft): -**Clown 3:** *[The Clown is] to attempt to be legitimately funny or entertaining at least once every fifteen (15) minutes.* -**Scientist 4:** *[Scientists are] to document anomalies and artifacts and submit the documentation to the Research Director.* -**Engineer 6:** *[Engineers are to] urgently respond to any request for work from command.* -##### Examples (from current SOP): -**Engineer 10:** *Engineers must ensure there is at least one (1) engineering hardsuit available on station at all times, unless there is an emergency that requires the use of all suits.* - -#### Basically Server Rules -Sometimes the minimum job requirements SOP veers into effectively being server rules, which isn't ideal for SOP (which is meant to be broken), while this type of SOP *can* exist, you should first consider two things: One, can this be communicated in another way (actual rule, space law, mechanics, ect), Two, How can this be made clear it has to be followed. This type of SOP should be avoided if possible, and made clear how important it is, especially with the soon to come removal of Command and CCvip OOC rules (Source: [Catty, SOP Workgroup Head/Community Manager](https://ptb.discord.com/channels/1276640157511979008/1484259495130566656/1501258020435267618)). -##### Examples (from the draft): -**Captain 6:** *[The Captain is to] ensure the safety of the station's nuclear authentication disk at all costs.** -**This is technically a rule break, counting as a play your character rule break.* -##### Examples (from current SOP): -**Captain 5:** *The captain must keep the Nuclear Authentication Disk on their person at all times or failing that, in the possession of the Head of Security;* - -#### MetaSOP -This is SOP that covers how SOP is to be enforced or instructing the following of other SOP. This type of SOP is redundant and arduous. Any SOP that acts as MetaSOP should be moved to either a general SOP chapter or to another article such as Regulations or Corporate Law. - -There are no proper examples from the draft, but there is an example of a solution, there is a General Command SOP that covers what is normally expected of command from Nanotrasen. -##### Examples (from the draft): -**Command 2:** *[All Command Personnel are to] ensure the wellbeing and dignity of Nanotrasen and its related assets.* -**Command 4:** *[All Command Personnel are to] never use any language towards Nanotrasen that may be considered defamatory or overtly negative.* -##### Examples (from current SOP): -**Detective [Green] 6:** *When not undercover, the Detective must follow the same guidelines as Security Officers for attire, with the exception that their own assigned attire is also acceptable for any of the attire mentioned for Security Officers.* - -#### Space Law -Space Law should not be in SOP, if it is a space law issue, it should be put in the space law article. This includes things that give crew special protections or regulations (like arrest procedures). A good example of this is how most command SOP (currently) covers how they are permitted to carry a flash. This is space law, and so should go into space law and it's rules about contraband. Any SOP that is space law should be removed and not added in at all. -##### Examples (from current SOP): -**Chief Medical Officer 2:** *The Chief Medical Officer is permitted to carry a flash and their hypospray;* - -#### Escalation -Escalation is SOP that changes or is altered based on the alert level. This type of SOP is counteractive to how SOP is meant to operate and the very definition of SOP. SOP is **Standard** Operating Procedure, if you are on red alert, you should not expect to be following SOP anymore, this isn't a standard shift. SOP should also be a driver of conflict, let us say a doctor is getting punished for an SOP violation they committed on blue alert due to the chaos in the medical bay, this is good RP, the kind SOP is meant to encourage. Is it wrong to punish a doctor for doing the right thing while under pressure and in an emergency, probably, but it causes that conflict. SOP that relies on alert level should be removed and not added in at all. -##### Examples (from current SOP): -**Scientist [Blue] 2:** *Scientists are permitted to produce weapons and grenades from the protolathe provided they get delivered to security.* - -## Game Design Rationale - -### Seriously Silly -SOP will now be changed to play into more of the serious aspects of our theming, class conflict and corporate dystopia, but there will still be room for the more silly aspects one would expect from Space Station 14. The serious aspects will be more about the punishments and cost of violating SOP and incurring the higher-ups wrath, while the sillier aspects would be finding strange and funny loopholes to SOP, to stick it to those same higher-ups. While SOP will likely play more into a serious tone, there will still be opportunities for the silly aspects we all love. - -### There is no Winning or Losing -SOP as a feature is intended to be broken, nobody is expected to be perfect at following SOP, it's a natural thing. So whether you are good or bad at SOP, there isn't a win condition or a loss condition, merely a system that is always there to drive conflict. - -### Maintaining Authenticity -This is what SOP has been focused on in the draft. Trying to play more into our themes we had to reconsider everything about SOP and what it is. While I have already covered what we use to write SOP above, here I will go into more detail about keeping it authentic. - -We have made a lot of changes to try and fit SOP better into the roles and into the other changes we are planning to make in the NCLP. A perfect example is the changes adding in considerations for Scrip and Unions (features we have been told to take into consideration): Scrip has had some major changes to the service department's SOP, with roles like the bartender not only expected to take payment but also now allowed to open a tab for customer. This is both authentic and a good vector for roleplay, allowing for new interactions that wouldn't have occurred before. Imagine a bartender having to report someone to sec for not paying their tab, that's new, interesting roleplay created by a mix of scrip, SOP, and authenticity. Roles like engineering have also had changes made, with them having a more urgent response required for work from command compared to regular crew. Of course Nanotrasen would want it's command to be prioritized, they are the most trusted and likely have a better reason for calling engineering compared to a bartender. That's authentic too, and that's the type of SOP that can really help drive home that class conflict as well. By using existing systems and considering how to make it not real, but authentic, we can drive home our themes in major and minor ways. - -### Take Things Slow -Most SOP has been altered to match more of a slower round flow, although SOP rarely covers time, it does cover another part of this Design Principal, which is making more of an engaging story. *"When designing other features, consider the story you want to tell, and ask yourself if it is a worthwhile story a player wants to engage with for more than 15 minutes."* SOP is a tool to create conflict, and making SOP that can cause an interesting conflict that could last or even change the whole round is something heavily considered when the SOP is written. Ideally SOP should be there as a way to truly cause an interesting story that can play properly into the themes of Funky Station. - -### Maximizing Roleplay Potential (Avoid QOL slop) -When the IAA walks into the department, you aren't worried you'll get in trouble because you aren't doing your job, you're worried you'll get in trouble because you forgot to keep an extra hardsuit around as per the SOP (Engi SOP 10). Is that a mechanical issue with your gameplay? No. But it can create that conflict between players, and further that tension between the crew and the higher ups. You may feel it's stupid, and your character may agree, but that is the POINT! You are meant to hate the stupid pedantry of the corporate environment, the rules that you know don't matter, because you're the one who actually does the work, puts in the effort to get things done, and some pencil pusher comes in and decides to tell you that you are the one who's wrong? That, that right there is the point of SOP. The creation of conflict between players, and that is why it aligns so well with this principal. - -## Roundflow & Player interaction -SOP isn't guaranteed to come into effect every round, but it should be expected that it will occur often, with the most major conflicts being less common, of course. SOP can come in at almost any point, all it takes is someone to notice an opportunity (like a SOP Violation) and run with it. Most SOP interactions won't effect the whole round, but there can be some times where it boils over and changes the whole round. I would expect us to see more of this as Unions are added and used, as they would be an amplifier to the conflict created by SOP (worker vs. boss). In cases where this happens, SOP can genuinely change the course of the round, causing chaos and protests, and maybe even riots should the conflict grow large enough. Of course, some SOP conflicts might go nowhere, but that is fine as well, as long as some roleplay value was had. - -As for the second part of this, the player interaction, we would hope that players are able to play into the conflict creation potential of SOP, either intentionally or unintentional. Players who don't know SOP will be more likely to break it, and thus get punished by the relevant authorities. This will lead to conflict. Players who do know SOP will likely break the "stupider" parts of it, and get in trouble anyways, just less often and less frequently. Of course we don't expect every player to break SOP, but it should happen unless someone is *perfect* at their job. SOP should remain a constant chance to get in trouble, even if you are working hard. - -## Administrative & Server Rule Impact (if applicable) -**1.** Does this feature introduce any new rule enforcement challenges or additional workload for admins? -Yes, this is a feature built on conflict so rules based around conflict (like escalation) will need more attention to them. This is a concern for all of the related changes as well. The one benefit is that SOP is player enforced, and thus, only the actions that violate rules need to be enforced, not anything relating to SOP as well. - -**2.** Could this feature increase the likelihood of griefing, rule-breaking, or player disputes -Griefing? Not likely. Rule-Breaking? Possibly (see above). Player Disputes? Absolutely. - -**3.** How are the rules enforced mechanically by way the feature will be implemented? -They will be enforced by certain positions on the station being encouraged to pressure the positions beneath them to follow the SOP, less they themselves become even more pressured from those above them. Cargo Technicians pressured by IAAs and the QM, who are pressured by their bosses, and at the highest level, Central Command pressuring roles like the captain (Minimum Admin intervention, however). -# Technical Considerations -**1.** Are there any anticipated performance impacts? -No. - -**2.** Does the feature require new systems, UI elements, or refactors of existing ones? -Yes, however there are other design documents being made for those changes, and is out of the scope of this document. However, it will require changes to the guidebook and the addition and change of books that exist as items. diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-4_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-4_design_doc.md deleted file mode 100644 index d87c2314..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-4_design_doc.md +++ /dev/null @@ -1,42 +0,0 @@ -# Nanotrasen Colonial Law and Procedure: Unions - -| Designers | Implemented | GitHub Links | -|---|---|---| -| SOP Workgroup | :x: No | TBD | - -## Overview - -A very short, maybe three sentence summary of what this proposal is about. A high level "overview" or "what this adds". - -## Background - -Summarize any information that is needed to contextualize the proposed changes, e.g. the current state of the game. - -Also link any relevant discussions on Discord, GitHub, or HackMD that are relevant to the proposal. - -## Features to be added - -Give a description of what game mechanics you would like to add or change. This should be a general overview, with enough details on critical design points that someone can directly implement the feature from this design document. Exact numbers for game balance however are not necessary, as these can be adjusted later either during development or after it has been implemented, but mention *what* will have to be balanced and what needs to be considered when doing so. - -## Game Design Rationale - -Consider addressing: -- How does the feature align with our [Core Design Principles](../design/design-principles.md) and game philosphy? - -## Roundflow & Player interaction - -Consider addressing: -- At what point in the round does the feature come into play? Does it happen every round? How does it affect the round pace? -- How do you wish for players to interact with your feature and how should they not interact with it? How is this mechanically enforced? - -## Administrative & Server Rule Impact (if applicable) - -- Does this feature introduce any new rule enforcement challenges or additional workload for admins? -- Could this feature increase the likelihood of griefing, rule-breaking, or player disputes? -- How are the rules enforced mechanically by way the feature will be implemented? - -# Technical Considerations - -- Are there any anticipated performance impacts? -- Does the feature require new systems, UI elements, or refactors of existing ones? -- For required UI elements, give a short description or a mockup of how they should look like (for example a radial menu, actions & alerts, navmaps, or other window types) \ No newline at end of file diff --git a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-5_design_doc.md b/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-5_design_doc.md deleted file mode 100644 index f2edad8e..00000000 --- a/src/design-proposals/nanotrasen-colonial-law-and-procedure/article-5_design_doc.md +++ /dev/null @@ -1,224 +0,0 @@ -# Station Protocol Rework: Sentencing, Trials, and Hearings - -| Designers | Implemented | GitHub Links | -|---|---|---| -| SOP Workgroup, Document written by Alicios| :x: No | TBD | - -## Overview - -This proposal provides a major overhaul of the current legal system, including Sentencing, Trial, and Hearing procedures. It majorly restructures the current legal job's power dynamics and role, creating a clear distinction between the "Enforcement" of Security, and the "Sentencing" of Legal jobs. - -The main intent of this overhaul is to make the procedures surrounding committing crimes open to many more roleplay opportunities. Crimes are less cut and dry, and have much more room to argue, create drama, and foster better roleplaying scenarios. - -## Background - -There are many issues with Funky's current legal system. - -The Warden is currently primarily responsible for sentencing, despite also having to keep an eye on the brig, handle armory access, watch monitors, and relay information from Emergency channels. Current SOP tries to emulate real-life legal systems, such as giving prisoners a right to a lawyer, giving them a chance to plead not guilty, and potentially escalating to trial. All of this is fundamentally impossible while the Warden is the only one in charge of sentencing. - -The Magistrate is the ultimate authority on Space Law verdicts, but is never present for any sentencing procedures. The only time the Magistrate is allowed to get invovled is when a case gets escalated to a full-on trial, which is an extreme rarity, and totally optional. Additionally, the Magistrate sits outside the normal Command power structure, and supersedes even the Captain and Head of Security. This does not align with Funky's future vision of the Captain being the ultimate authority on the station, and instead makes existing Non-CCVIP Command members feel impotent. - -Lawyers feel like they have no purpose. Security SOP and current Space Law barely supports Lawyers actually escalating charges to a court case. Brig times are far too short, and any amount of argument or legal battle would take far longer than the unmodified sentence. Lawyers do not even have security comms, so they cannot know if there is a client unless they physically sit in Security and ask every incoming detainee. - -Trials are rare, and when they do happen, they are incredibly long, unfocused, and have no clear points to fight for. There are no clear procedures to determine what is necessary to come to a verdict, and what consequences can even come from it. Often times, the main participants of a Trial are characters with Jobs that are much more important to the operation of the station, like a Command Member or Security Officer, which almost certainly results in the Trial having to get cut short without a satisfying conclusion. - -Punishments for breaking the law are intentionally short and inconsequential, because they were designed for a much shorter round length than what Funky has. There is no room for alternative punishments, and the Warden is encouraged to keep brig times low, because there is little to no interaction while in the brig, and players have a fear of "ruining someone else's round" - -Essentially, any and all interaction with legal battles in the game's current state is unwieldy, and completely voluntary. This proposal aims to push the legal system to the forefront of any criminal charges, in a way that is still efficient for gameplay's sake, but also allows for much more depth and nuance with every interaction. - -## Features to be added - -### Job Restructuring & Legal Department: - -Many of these changes are part of the larger design proposals from the SOP Workgroup, but it is important to highlight the ones that are vital for the Legal System. - -Head of Personnel (Head of Service) -> Executive Officer (Head of Legal)\ -Magistrate (CCVIP) -> Judicial Officer (Legal Deputy)\ -Internal Affairs Agent (CCVIP) -> Internal Affairs Agent (Legal)\ -Lawyer (Civilian) -> Lawyer (Legal) - -There is a new clear division between Security, and Legal staff. This will come with a comms channel specifically for Legal staff, to help the Legal team facilitate court cases, and hearings. - -#### Legal Department -Legal becomes its own department, with its own comms channel to facilitate smooth court operations, but it does not need major mapping changes. -Existing maps can just reuse the current Lawyer, Magistrate, HOP, and IAA offices, as well as the Court. - -A key design decision here is that the Legal Department is not solely focused on Legal/Security concerns. As SOP and Law are largely unified with our workgroup's proposal, the Legal department would be focused not just on court proceedings and law interpretations, but on also on administrative, bureaucratic, and regulatory duties. - -The Executive Officer would still be the primary authority on access changes, job hirings, and permit drafting. -The Judicial Officer gaining the power of legal regulation expands the Legal department's regulatory authority. -The Internal Affairs Agents are still concerned with performing departmental audits and SOP enforcement. - -The Legal Department stands to separate administrative duties away from CCVIPs, which should be an outside, third party entity, and solidify regulatory power under normal command structures, and especially under the Captain and XO. - -### Job Responsibilities & Authority: - -Power shifts as follows: -The Magistrate's ultimate authority on legal matters goes to the Captain, with the Executive Officer second in line. -The Warden's authority and responsibility in sentencing goes to the Judicial Officer, who is not Command/CCVIP, but instead a Deputy of the Executive Officer. -Internal Affairs Agents are now able to audit Space Law misinterpretations, much like how the Magistrate was previously. -(As part of a wider change from the SOP workgroup, audits are less powerful in general, but the authority to audit still falls upon IAAs) -The Executive Officer is now the Command member primarily responsible for the Legal team, and the one that all Legal members directly answer to. - - -### Expanded Sentencing -Since Sentencing is fully the responsibility of a single job, with a level of trust and authority, this brings the opportunity to expand punishments and sentencing as a whole. - -#### Crime Tiers -This is also part of the SOP Workgroup's Corporate Law proposal, but it is worth going over here. - -There are now only 4 tiers of crimes, each with FIXED punishment lengths in each tier. - -Infractions: Warning/Tickets\ -Misdemeanor: 10 minutes.\ -Felony: 20 minutes.\ -Capital Offense: Permanent. - -Permanent Brig time threshold is 40 minutes, instead of 20. - -Base brig time is generally higher, specifically to create opportunities for legal battles, and to create incentives to argue for Extenuating Circumstances, Alternative Punishments, and Parole. - -Long and Permanent sentences will become more common, but this does NOT mean actual time served will be higher. There will be opportunity to fight your way out of a long sentence, or prove your worth and get out early. - -#### Extenuating and Aggravating Circumstances -Circumstances make differences in sentence length a point to argue about, and create roleplaying opportunities, rather than being entirely up to Warden fiat. - -The Prosecution can argue for Aggravating circumstances, which increase the severity of the punishment. -Examples include: Brutality, Evasion of Enforcement, Privileged Victim, Repeat Offenses - -The Defense can argue for Extenuating circumstance, which reduce the severity of the punishment. -Examples include: Cooperation with Enforcement, First Offense, Self-Defense, Self-Report - -#### Alternative Punishments -Alternative Punishments are NT-approved alternatives to brig time, which create a clear target for either side to argue for. This makes sentences potentially much more interesting than "time out" in the brig. - -Examples include: Community Service/Forced Labor, Demotion, Whistleblowing, Financial Compensation, Reversing Damages - -#### Parole -Parole is the opportunity for a criminal to be freed from their brig sentence early, giving prisoners incentives to have good behavior, as well as providing opportunities for interesting roleplay scenarios. - -Examples include: Community Service/Station Labor, Appointments with the Chaplain/Psychologist, Parole with Tracking implants, bodycams, electropacks, etc. - -(This also gives Chaplains and Psychologists perfect opportunities to roleplay with criminals, with mechanical incentives as well) - - -### Court Procedures - -All arrests above a minor infraction must take the detained to court, to formally receive a sentence before the Judicial Officer. -Here, the defendant is given the opportunity to plead "not guilty", which initiates a formal legal procedure to determine their guilt, as well as what punishments they should receive. - -It is to be made VERY clear, that the intent is NOT to make every simple crime and sentence a full-blown trial that takes dozens of minutes. Your typical criminal charge with clear-cut evidence and/or low severity in punishments are supposed to be swift, and take only a few minutes at most. The intent is to allow criminals to negotiate alternative punishments, or smooth-talk their way out of punishments, and create meaningful legal roleplaying scenarios, NOT to add unnecessary bureaucracy and moving parts to every criminal interaction. - -It is also worth noting, that any Court Procedure above a Summary Hearing exclusively involves jobs that are fully committed to Legal scenarios. This means that those roles can put 100% of their attention to a legal procedure, without risk of interruption. They are also able to gather a level of expertise and knowledge of legal procedures, making the system much more efficient and interesting than otherwise. - -There are 3 levels of court procedures, which scale according to the potential punishment and crime severity. - -#### Summary Hearings -Quick, efficient legal procedure. 1-2 minutes. These are held for simple misdemeanor crimes, and anything of low severity. - -There is not supposed to be a ton of back and forth, just the opportunity for the defendant to state their case, or bring to attention details that may have been missed. The Prosecution is simply the officer who performed the arrest, to make it as quick and efficient as possible. The Judicial Officer opens with a proposed sentence, and gives the defense the opportunity to accept their charges with no pushback. - -Summary Hearings are largely reminiscent of the way the Warden used to determine brig times. - -#### Formal Hearings -Lengthier, proper hearing for crimes with a big enough punishment to warrant it. Could take up to 15 minutes, but they are only held for crimes that could potentially result in a punishment more severe than the time it takes to hold the hearing. Felonies and Capital Offenses receive Formal Hearings. - -Formal Hearings are the when legal representation comes into the picture. Security consults with an IAA, who will act as prosecution. The Defendant consults with a Lawyer, who acts as the defense. - -Each side presents their case, and potentially questions up to one witness, if necessary. After the Judicial Officer makes their verdict, the both sides are given the opportunities to argue for Extenuating and Aggravating circumstances, or make deals for alternative punishments. - -Formal Hearings are supposed to still be quick, but they just give both sides a bit more opportunity to explore all options, and utilize or exploit the legal system to their advantage. - -#### Trials -Extremely in-depth, highly formal procedure only for the most severe of crimes. Trials can take as long as necessary, and stop only when the Judicial Officer can confidently come to a verdict. Trials can only be held for Capital Offense charges, and only if the Judicial Officer approves it is worthy of a Trial. - -Trials consist of a formalized procedure, multiple witness and evidence examinations, and plenty of opportunity for roleplay and drama. - -Trials are capable of, and intended to, consume a Legal role's entire round. This is why they are entirely opt-in, and case-by-case. A Trial will NEVER be standard procedure for any crime, and only happen if all players involved wish to engage in formalized legal scenarios. - - -## Addressing Common/Anticipated Concerns -### Sentencing criminals will take too long. -Summary hearings are designed in such a way to directly replace the old "Warden-style" quick sentencing. For minor, inconsequential crimes, the criminal will be processed in hardly any time at all. The process is simply formalized and opens the floor for the defense to escalate into a more lengthy legal battle if they so desire. - -Even for Capital Offenses, the escalating to a full-on trial is a fully voluntary affair, and also up to the discretion of the Judicial Officer. Lengthy trials are an opportunity for players who WANT long trials to have them, without hurting the necessary efficiency of your everyday sentences. - -### There is no way a court hearing can happen in such a short amount of time. -The procedure for each type of Hearing is a formalized step-by-step process, and is intentionally designed to keep hearings brief and efficient. It reduces as much back-and-forth as possible, and focuses only on key facts and agreed upon talking points. - -Having jobs/roles that are knowledgeable and primarily responsible for Legal procedures will also dramatically cut down on rambling/unfocused court cases that we have now. Since Trials are so rare in current Funky, there is no common consensus on how they should be run, which leads them to be unfocused and inefficient. - -### Role bloat with a new department and/or new department will have nothing to do. -Every "new" Job in this proposal is a job that already existed. The things that a "Legal team" would do are already happening, it is just not formalized as a separate entity. It is simply reinforcing their responsibilities and reframing them as a team that works together, instead of disparate individuals from separate departments and power scales dysfunctionally trying to work together. -Each job other than the Judicial Officer is also intentionally designed to have alternative, lesser tasks when hearings/trials are not happening. Legal Jobs to not only exist within the court, they have their own tasks and assemble when necessary. - -XO -> Help the Captain enforce corporate policy, manage ID access, handle paperwork/permits\ -JO -> Participate in civil suits, or more casual Legal RP scenarios.\ -IAA -> Perform SOP audits, provide legal counsel, measure productivity quotas.\ -Lawyer -> Help draft civil suits, consult with brigged criminals, propose parole\ - -Once Unions are implemented, the Legal team will play a big part as correspondants between the general Crew, Unions, and Command. - -### Not everyone wants to participate in Legal RP. -Every Hearing/Trial procedure has a path of least resistance, so that if the arrested criminal does not wish to engage with Legal RP whatsoever, they have that choice. They can refuse consultation or legal representation. They can accept any charges without any pushback. The pipeline of arrest -> sentence -> brig -> continue still exists, it is just an option, rather than the only choice. Trials are completely optional, and no one will be forced into it if they do not wish to. - -### Brig times will be too long. -Brig times should be longer in general, to accompany Funky Station's inherently longer round time. Going through the whole process of an arrest only for someone to get a 5 minute sentence is a complete waste of time. There is no incentive to fight back or engage in any meaningful RP when there is no gameplay incentive to do so. - -Brig times are longer, but with the additions of Alternative Punishments and Parole, those who actually engage with the Legal System will be given opportunities to circumvent their "time out" time with RP scenarios. Talking with Lawyers, the Judicial Officer, the Warden, getting a new Job, consultations with Chaplains and Psychologists are all avenues to reduce your brig time, and result in much more interesting scenarios post-arrest. - - -## Game Design Rationale - -### Seriously Silly: -All levels of authority and importance with Legal jobs creates many opportunities for interesting and fun characters. -JOs and IAAs will be uptight, formal, and NT-loyalists. Lawyers may be "aligned with the people", and sympathetic. - -A proper framework for legal procedures opens the door for frivolous, humorous cases and lawsuits. - -### There is no Winning or Losing: -Currently, getting brigged is just about the most glaring instance of "clearly losing" in the game. There's barely any opportunity to fight it, there's nothing to do inside the brig, and the rules are structured in a way to just put you in "time out", and move on. - -This Legal overhaul creates opportunities for gray areas and ways to fight back against getting arrested at every opportunity. Even a permanent brig sentence is just an opportunity to consult a Lawyer and ask for parole. Getting arrested shouldn't feel like you "lost", it should just be the next chapter in your story. - -### Maintaining Authenticity: -Real-life Legal procedures are incredibly pedantic, formal, and take ages. We are not trying to emulate legal procedures for realism's sake. We are taking inspiration from real courts of law, and seeing which parts meaningfully create opportunity for conflict and roleplay, and condensing it into a manageable amount of rules for use in game. - -Many people are familiar with legal stories and dramas, with court cases in TV shows, and video games. The goal is to take that larger-than-life, dramaticized version of court, and inject that into the game. - -### Take Things Slow: -The old brig system is built for rapid-fire, in-and-out sentences. Brig times are incredibly short, and there is no room for argument or formal procedures. This is because the servers these rules originated from are also short. - -This system takes advantage of the extra time we have in Funky rounds to meaningfully expand upon what happens after you get arrested. Short, inconsequential crimes remain fast and efficient, but more severe, round-defining crimes are given the proper amount of attention and time to play out a scenario. - -### Maximizing Roleplay Potential (Avoid QOL Slop): -Adding in a human element to sentencing and legal procedures greatly encourages roleplay. Every player is given the opportunity to argue their case in their own way, and Legal jobs are given the opportunity to completely explore their role. - -### Dynamic Enviroment: -Every major crime becomes it's own story and fight in court. More moving parts creates more opportunities for breakouts, elaborate plans, and individual judgement. No two murder cases will ever feel the same. - - -## Roundflow & Player interaction - -This is a major change to sentencing and criminal interactions. It will affect every single arrest, impact almost any antagonist role that commits a crime. -This is why we have intentionally designed Summary Hearings to be quick and efficient, and emulate the old Warden quick sentencing. Not every crime needs a full on procedure; we should be putting time and effort into places where it matters, like major crimes. - -There will be a large variation in how Legal players interpret their role. Some JOs will be extremely strict and overly harsh, and create tons of conflict. Some will be incredibly lenient and get in trouble with the XO. This is intentional, and welcomed. - -It is mentioned in the relevant section, but Trials are entirely opt-in. No one will be forced into an hour-long legal battle unless they want to. All players who are charged with a crime will have to interact with the legal system in some capacity, but it should never completely consume their round unless they want it to. - -## Administrative & Server Rule Impact (if applicable) - -Admins may have to monitor problematic players being too harsh or abusive with their power over punishment. However, this is no different than the way Security and Command are held to a higher standard for the exact same reasons. - -Players will still have all the normal avenues for expresing themselves through in-character conflict, whether that is reporting to their Head of Staff, the Captain, or getting a Lawyer to represent them. - -That being said, much like the Magistrate already is, the JO will likely have to have a sizeable playtime requirement, and a decent amount of monitoring for abusive behavior. - -# Technical Considerations - -Legal Comms key for relevant parties. -Existing Legal offices will need access changes. -Job icons will need changes to accomodate the departmental shifts and hierarchy adjustments. - -The rest is purely guidebook entries. From 0295ce41775196dba087e42b1c948c2c6f643e0d Mon Sep 17 00:00:00 2001 From: Alicios Date: Fri, 5 Jun 2026 12:34:31 -0700 Subject: [PATCH 53/53] Added Article 5 descriptor --- src/design-proposals/nanotrasen_colonial_law_and_procedure.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md index aa6fb8e2..91b66f6f 100644 --- a/src/design-proposals/nanotrasen_colonial_law_and_procedure.md +++ b/src/design-proposals/nanotrasen_colonial_law_and_procedure.md @@ -55,6 +55,7 @@ SOP has to be overhauled to better fit the themes and expectations of Funky Stat *[Article 4 - Unions](./station_protocol_rework/Article%204%20-%20Unions.md)* ### Article 5 - Trials and Hearings +Restructuring existing Legal roles to operate under the normal Command hierarchy, instead of CC, in order to reinforce the Captain's power. Moving the job of sentencing to the Magistrate to alleviate the Warden's duties, while expanding court protocol to provide a better platform for Legal RP scenarios. *[Design Document: Article 5 - Trials and Hearings](./station_protocol_rework/article-5_design_doc.md)*