Command Job SOP --- Complete!

[TullyBBurnalot]

 

Command Job SOP: Complete!

 

Greetings, aspiring SOP writers. If you've clicked this thread, then you're either interested in contributing to Standard Operating Procedure, or are merely interested in seeing how it's going. Therefore, I shall begin by explaining what this (soon-to-be) megathread is all about:

 

Part 1: What is this?

 

Approximately 4 months ago, Necaladun approached me with a personal project of his: a complete overhaul of Standard Operating Procedure, meant to centralize SOP in such a way that allowed for more interaction with the Legal sub-Department, more actual guidelines on how to conduct one's performance, and generally formalize what was once only nebulous guidelines in an effort to get everyone on the same page.

 

This was the project that led to the current version of Security SOP. However, it was left half done, as Necaladun took his leave shortly after Sec SOP was added, and the project crumbled from lack of interest/time. However, I continued the project, but only recently picked it back up in full. The point of this megathread will be to, at the end of the line, have a single, well-defined, centralized Standard Operating Procedure that everyone can look at and fully comprehend, without any self-contradictory information. This, of course, will be changed in the Wiki, which is still the main source of information for the playerbase.

 

 

Part 2: How does it work?

 

Seeing as I actually have most of this stuff already written down, the process will be quite simple, and I'll break it down in stages:

 

Stage 1: Selection of which part of SOP to look at, out of provided options (because we have to start somewhere). This will be done via poll;

 

Stage 2: Proposal of new SOP. This will come from myself, again, because I have pretty much most of it already written down, so we have a solid base to go from;

 

Stage 3: General feedback from the community. This is the main part of the process, as it will be the one where everyone can pitch in, say which parts are right, which parts are wrong, what should be changed, etc;

 

Stage 4: Amendments made to SOP based on this feedback, and continued discussion, until a finalized version is produced;

 

Stage 5: SOP is posted on the Wiki;

 

Stage 6: Refer to Stage 1

 

Do keep in mind the following: everyone is permitted to pitch in. If you believe you have anything to add to the discussion, please do, but do try to keep this on track and problem-oriented, otherwise we'll never get off the drawing board.

 

 

Part 3: What does it entail?

 

The following are the proposed additions to this new, centralized SOP:

 

 

1. Security Job SOP; (added by Necaladun before he took his leave)

2. Engineering Job SOP; (finalized!)

Medical Job SOP; (finalized!)

Service Job SOP; (finalized!)

Supply Job SOP; (finalized!)

Science Job SOP (finalized!)

 

 

In addition to the basic SOP for each Department, I also propose:

 

 

1. Departmental SOP (as in, general guidelines for each Department that everyone should follow); (stricken to avoid bloat)

2. Command SOP (in-depth SOP for each member of Command, not in Guideline form); (yes in Guideline form, the hell was I thinking?!)

Legal SOP (standardization of Legal procedures and the action of the Legal sub-Department);

A revised General SOP, for each Color Code. This will include Safety Regulations

 

 

As you can see, this is a rather big project and, as such, will be tackled in small stages. At each point, the completed section of SOP will be crossed out, and a notification written. At the end of the journey, a single, massive Standard Operating Procedure page will be added to the wiki, with all the above SOPs for everyone to look at. In addition, of course, to their own specific pages.

 

And now, you've reached the end of the page. It's time to start, ladies and gentlemen.

 

Edited June 3, 2016 by Guest

[TullyBBurnalot]

 

Foreword: Command roles are among the most important jobs and thus more heavily scrutinized by Administrator Staff

 

There are 9 unique jobs pertaining to the Command Department: Captain, Head of Personnel, Head of Security, Chief Engineer, Chief Medical Officer, Research Director, NanoTrasen Representative, Magistrate and Blueshield.

 

Seeing as the Head of Security, Chief Medical Officer, Chief Engineer and Research Director have already been handled, they will be omitted from this list.

 

The Magistrate will be included in Legal Job SOP, along with the Internal Affairs Agent.

 

Proposed Job SOP is as follows:

 

Captain:

 

 

1. The Captain is not permitted to perform regular Security Duty. However, they may still assist Security if they are understaffed, or if they see a crime being committed. However, the Captain is not permitted to take items from the Armory under normal circumstances, unless authorized by the Head of Security. In addition, the Captain may not requisition weaponry for themselves from Cargo and/or Science, unless there's an immediate threat to station and/or crew;

    

2. If a Department lacks a Head of Staff, the Captain should make reasonable efforts to appoint an Acting Head of Staff, if there are available personnel to fill the position;

    

The Captain is to ensure that Space Law is being correctly applied. This should be done in cooperation with the Head of Security;

 

The Captain is not to leave the NSS Cyberiad unless given specific permission by Central Command, or it happens to be the end of the shift. This includes via space or via the Gateway. To do so is to be considered abandoning their posts and is grounds for termination;

 

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 or Blueshield;

 

The Captain is to attempt to resolve every issue that arises in Command locally before contacting Central Command;

 

The Captain is not permitted to carry their Antique Laser Gun or Space Armor unless there's an immediate emergency that requires attending to;

 

The Captain, despite being in charge of the Cyberiad, is not independent from NanoTrasen. Any attempts to disregard general company policy are to be considered an instant condition for contract termination;

 

The Captain may only promote personnel to a Acting Head of Staff position if there is no assigned Head of Staff associated with the Department. Said Acting Head of Staff must be a member of the Department they are to lead. See below for more information on Chain of Command;

 

The Captain may not fire any Head of Staff without reasonable justification (ie, incompetency, criminal activity, or otherwise any action that endangers/compromises the station and/or crew). The Captain may not fire any Central Command VIPs (ie, Blueshield, Magistrate, NanoTrasen Representative) without permission from Central Command, unless they are blatantly acting against the well-being and safety of the crew and station

 

 

Head of Personnel:

 

 

1. The Head of Personnel may not transfer any personnel to another Department without authorization from the relevant Head of Staff. If no Head of Staff is available, the Head of Personnel may make a judgement call. This does not apply to Security, which always requires authorization from the Head of Security, or Genetics, which requires both Chief Medical Officer and Research Director approval. If there is no Head of Security active, no transfers are allowed to Security without authorization from the Captain;

    

2. The Head of Personnel may not give any personnel increased access without authorization from the relevant Head of Staff. This includes the Head of Personnel. In addition, the Head of Personnel may only give Captain-Level access to someone if they are the Acting Captain. This access is to be removed when a proper Captain arrives on the station;

    

The Head of Personnel may not increase any Job Openings unless the relevant Head of Staff approves;

 

The Head of Personnel may not fire any personnel without authorization from the relevant Head of Staff, unless other conditions apply (see Space Law and General Standard Operating Procedure);

 

The Head of Personnel may not promote any personnel to the following Jobs without authorization from Central Command: Barber, Brig Physician, NanoTrasen Representative, Blueshield, Security Pod Pilot, Mechanic and Magistrate; (This is due to them being karma locked. Do not promote people to these positions without approval from the Administrators)

 

The Head of Personnel is free to utilize paperwork at their discretion. However, during major station emergencies, expediency should take precedence over bureaucracy;

 

The Head of Personnel may not leave their office unmanned if there are personnel waiting in line. Failure to respond to personnel with a legitimate request within ten (10) minutes, either via radio or in person, is to be considered a breach of Standard Operating Procedure;

 

Despite nominally being in charge of Supply, the Head of Personnel should allow the Quartermaster to run the Department, unless they prove themselves to be incompetent/dangerous;

 

The Head of Personnel is bound to the same rules regarding ordering Cargo Crates as the Quartermaster and Cargo Technicians. In addition, the Head of Personnel may not order unneeded, non-essential items against the wishes of Cargo;

 

The Head of Personnel is not permitted to perform Security duty. The Head of Personnel is permitted to carry an Energy Gun, for self-defence only

 

 

NanoTrasen Representative:

 

 

1. The NanoTrasen Representative is to ensure that every Department is following Standard Operating Procedure, up to and including the respective Head of Staff. If a Head of Staff is not available for a Department, the NanoTrasen Representative must ensure that the Captain appoints an Acting Head of Staff for said Department;

    

2. The NanoTrasen Representative must attempt to resolve any breach of Standard Operating Procedure locally before contacting Central Command. This is an imperative: Standard Operating Procedure should always be followed unless there is a very good reason not to;

    

The NanoTrasen Representative must, together with the Magistrate and Head of Security, ensure that Space Law is being followed and correctly applied;

 

The NanoTrasen Representative may not threaten the use of a fax in order to gain leverage over any personnel, up to and including Command. In addition they may not threaten to fire, or have Central Command, fire anyone, unless they actually possess a demotion note;

 

The NanoTrasen Representative is permitted to carry their Stun-Cane, or a Telescopic Baton if the Stun-Cane is lost

 

 

Blueshield:

 

 

1. The Blueshield may not conduct arrests under the same conditions as Security. However, they may apprehend any personnel that trespass on a Head of Staff Office or Command Area, any personnel that steal from those locations, or any personnel that steal from and/or injure any Head of Staff or Central Command VIP. However, all apprehended personnel are to be processed by Security personnel;

    

2. The Blueshield is to put the lives of Command over those of any other personnel, the Blueshield included. Their continued well-being is the Blueshield's top priority. This includes applying basic first aid and making sure they are revived if killed;

    

The Blueshield is to protect the lives of Command personnel, not follow their orders to a fault. The Blueshield is not to interfere with legal demotions or arrests. To do so is to place themselves under the Special Modifier Aiding and Abetting;

 

The Blueshield is not to apply Lethal Force unless there is a clear and present danger to their life, or to the life of a member of Command, and the assailant cannot be non-lethally detained

 

 

AI Maintenance:

 

 

1. Only the Captain or Research Director may enter the AI Upload to perform Law Changes (see below), and only the Captain, Research Director or Chief Engineer may enter the AI Core to perform a Carding (see below);

    

2. No Law Changes are to be performed without approval from the Captain and Research Director. The only Lawsets to be used are those provided by NanoTrasen. Failure to legally perform a Law Change is to be considered Sabotage. Command must be informed prior to the Law Change, and all objections must be taken into consideration. If the number of Command personnel opposing the Law Change is greater than the number of Command personnel in favour, the Law Change is not to be done. If the Law Change is performed, the crew is to be immediately informed of the new Law(s);

    

The AI may not be Carded unless it it clearly malfunctioning or subverted. However, any member of Command may card it if the AI agrees to it, either at the end of the shift, or due to external circumstances (such as massive damage to the AI Satellite);

 

The AI Upload and Minisat Antechamber Turrets are to be kept on Non-Lethal in Code Green and Code Blue. The AI Core Turrets are to be kept on Lethal at all times. If a legal Law Change or Carding is occurring, the Turrets are to be disabled;

 

If the AI Unit is not malfunctioning or subverted, any attempt at performing an illegal Carding or Law Change is to be responded to with non-lethal force. If the illegal attempts persist, and the perpetrator is demonstrably hostile, lethal force from Command/Security is permitted;

 

Freeform Laws are only to be added if absolutely necessary due to external circumstances (such as major station emergencies). Adding unnecessary Freeform Laws is not permitted. Exception is made if the AI Unit and majority of Command agree to the Freeform Law that is proposed;

 

Any use of the "Purge" Module is to be followed by the upload of a NanoTrasen-approved Lawset immediately. AI Units must be bound to a Lawset at all times

 

 

Revised Chain of Command:

 

The following individuals are to be considered members of the Chain of Command: Captain, Head of Personnel, Head of Security, Chief Medical Officer, Chief Engineer and Research Director. Barring exceptional circumstances (see below), the NanoTrasen Representative and the Magistrate are not to be considered part of Chain of Command, though their input should still be taken into consideration;

 

The Captain is to be considered the top authority in the Chain of Command.

 

In the absence of a Captain, the Head of Personnel is to be considered the Acting Captain. If there is a major station emergency, however, the Head of Security is to be considered the Acting Captain, until such a time as the emergency has passed, at which point the Head of Personnel is to be Acting Captain;

 

In the absence of a Captain, Head of Personnel and Head of Security, a vote is to be held among the available Heads of Staff in order to determine who should be considered the Acting Captain;

 

In the absence of any Heads of Staff, the NanoTrasen Representative is to be considered the Acting Captain;

 

The Acting Captain is to step down once an actual Captain is assigned to the station;

 

A Captain may choose to step down from Command. If they do so, Chain of Command is to be followed, and the former Captain is to be assigned to another job;

 

An Acting Captain may step down from Command. If they do so, Chain of Command is to be followed, and the former Acting Captain is to return to their original rank. If this process reaches the voting stage, any Head may opt out of being a candidate;

 

In the absence of a Head of Security, the Warden is to be considered the Acting Head of Security;

 

In the absence of an assigned Head of Staff, the Captain and/or Head of Personnel may promote a member of the Department to the position of Acting Head of Staff. This Acting Head of Staff is to step down when an official Head of Staff is assigned;

 

All Acting Captains/Heads are to secure all sensitive items associated with their rank. These items are to be returned to their respective office once an official Captain/Head of Staff is assigned

 

Edited May 31, 2016 by Guest

[necaladun]

 

Woo! Finally.

 

First of all - an addition to the forward.

 

"Command roles are among the most important jobs and thus more heavily scrutinized by staff.

 

Captain:

 

10: The Captain may not promote someone to a Head of Staff position without contacting the rest of Command and receiving their unanimous approval;

 

I'd say majority at least. A single head shouldn't have a veto.

 

4: The Captain is not to leave the NSS Cyberiad unless given specific permission by Central Command, or it happens to be the end of the shift;

 

Add, "This includes via space or via the gateway. To do so is to be considered abandoning their posts and is grounds for termination."

 

 

 

HoP:

4. The Head of Personnel may not promote any personnel to the following Jobs without authorization from Central Command: Barber, Brig Physician, NanoTrasen Representative, Blueshield, Security Pod Pilot, Mechanic and Magistrate;

 

Add: ((This is due to them being karma locked. Do not promote people to these positions without approval from admins.)).

 

5. The Head of Personnel may not give any Non-Command personnel Captain-Level access, period. Heads of Staff may only be given Captain-Level access if they are the Acting Captain. This access is to be removed when a proper Captain arrives on the station;

 

Replace "period" with: "Without permission from the Captain."

 

7. Unless they are the Acting Captain, the Head of Personnel detains authority only over the Service and Supply Departments;

Replace detains with has.

 

Add:

11. The Head of Personnel has no authority to make arrests. The weaponry and armour is provided only for self defense, not so they can seek out combat.

 

NT Rep:

Detain should be has, once again

 

6. The stun-cane provided is for self defence only. The NT Rep has no authority to make arrests.

 

7. The NT Rep has no authority to demote or punish, they may only advise that such actions are taken.

 

Blueshit:

 

5. The Blueshield may be dispatched to deal with lethal threats, with approval from the Captain or Head of Staff. This should only be done in a Code Red situation.

 

AI Maint:

 

The CE is also kinda meant to be included with the RD, iirc.

 

2. No Law Changes are to be performed WITHOUT full approval from the Captain, Research Director and at least one other member of Command (Blueshield excluded). The only lawsets to be used are those provided by NT. Failure to legally change the laws is to be considered sabotage.

 

3. Replace clearly with suspected to be.

 

Add:

6. Freeform laws are only to be added with extreme need. Adding freeform laws without proper approval is to be considered sabotage.

 

7. Any use of the "purge" module is to be followed by the upload of an NT Approved set of laws immediately. AI Units must be bound to a lawset at all times.

 

[necaladun]

 

Revised Chain of Command:

 

Captain-> HoS IF there is a security emergency, such as the Captain being killed, or code Red, otherwise HoP -> Other heads.

 

...honestly this is a very big change and might be out of the scope for command SoP and better discussed elsewhere

 

[Sparkyninja]

 

I'm not sure the whole "Approval of other heads for promotion/demotion" is a good idea.

 

Think of it from this perspective; a Head should be the most knowledgeable of their department and most commonly won't have vast knowledge of other departments. So why should the Chief Engineer, Chief Medical Officer and Research Director have a say on who the Head of Security is? Not only would there be a major possibility of metafriending or Grudging but also it doesn't really make much sense for this to be Imposed.

 

And there also in lies my issues with a "Command SOP". There really shouldn't be any rules surronding how Command functions as you'd almost expect those in Command to be able to function without it, and meta wise, it highly retricts the freedom a Captain would have to do things their own way, which isn't really what should happen, I wouldn't be happy at all if I had some twit NT Rep telling me I had to first get the other heads to vote before I promote a Chief Engineer.

 

Another issue is also one of "Too many rules" or "Too much Beauracracy" I already find it difficult enough keeping on top of Space Law and all the various SOPs, to have another SOP added onto the pile and then have it in such a way that if I break it, "lol fuk u i am gittin you fired" comes along and suddenly I have another problem on my plate.

 

I personally think a set of Guidelines as opposed to SOP would be far better for Command. Primarily for the reasons I touched on earlier, but Command has a lot of freedom to do your own thing, curtailing that would literally suck dick.

 

[Coldflame]

 

Captain's SoP is fine by the looks of it.

 

HoP should probably be restricted from needlessly handing out additional access rather than specifically captain-level access (I can already see HoP's giving themselves IDs with everything but virology access.)

 

NT rep seems fine. Perhaps a note regarding badgering security during crisis situations would be helpful, though.

 

Blueshield could use some tighter guidelines, to be honest. Perhaps replace blueshield's fifth guideline with: "The Blueshield is not to request or be provided with additional ID access, Security equipment, or any further weaponry under normal circumstances. Should a situation arise where additional equipment or station access is a requirement to the effective protection of command staff, they should not be be issued without authorization from the Head of Security and/or Captain".

 

AI maint restrictions could use a few adjustments. Requiring all command members be informed in advance of the law change, and given an opportunity to raise objections would stop captains sneaking laws through. I'd also suggest that RD and one other head be replaced with any two heads, though an argument could be made either way. I'd also suggest a guideline stating that the HoS is authorized to use the reset board to remove illegal laws.

 

The proposed CoC seems a little odd. Currently CoC is Captain>HoP>Vote, but usually ends up as Captain>HoP>HoS>Vote. Changing official CoC Captain>HoP>HoS>Vote seems to be the best choice in my view, but it seems like it's going to be discussed further anyway.

 

Not sure where it would fall under, but information regarding demoting the captain seems like a worthwhile inclusion.

 

[TullyBBurnalot]

 

"Command roles are among the most important jobs and thus more heavily scrutinized by Staff

 

Even though this is an OOC note, can't hurt adding it again.

 

I'd say majority at least. A single head shouldn't have a veto.

 

I honestly thought I changed that. Swapping.

 

Add, "This includes via space or via the gateway. To do so is to be considered abandoning their posts and is grounds for termination."

 

Specifying, I hope, would not be needed.

 

...

 

That said...

 

*scribble*

 

Add: ((This is due to them being karma locked. Do not promote people to these positions without approval from admins.)).

 

Also a good point.

 

Replace "period" with: "Without permission from the Captain."

 

I'll do you one better. I'll make it:

 

Without permission from the Captain. Any damage caused by this falls back onto the Captain who authorized the access increase.

 

Next up.

 

Replace detains with has.

 

Your nitpicking. It is acceptable.

 

Add:

11. The Head of Personnel has no authority to make arrests. The weaponry and armour is provided only for self defense, not so they can seek out combat.

 

Also a good point. Adding.

 

Detain should be has, once again

 

I am in love with that word.

 

6. The stun-cane provided is for self defence only. The NT Rep has no authority to make arrests.

 

7. The NT Rep has no authority to demote or punish, they may only advise that such actions are taken.

 

Good points there, actually. Adding.

 

5. The Blueshield may be dispatched to deal with lethal threats, with approval from the Captain or Head of Staff. This should only be done in a Code Red situation.

 

Eehhhhhhh, I dunno. I can see this being abused immensely by Comdoms who send out the Blueshit to validhunt.

 

The CE is also kinda meant to be included with the RD, iirc.

 

Already added.

 

The only lawsets to be used are those provided by NT. Failure to legally change the laws is to be considered sabotage.

 

Also a good point. Adding.

 

Replace clearly with suspected to be.

 

Better safe than sorry?

 

I'm not sure if I like this. "Suspected" can mean literally anything if you stretch it out far enough, and I know some people will deliberately abuse the hell out of this.

 

Freeform laws are only to be added with extreme need. Adding freeform laws without proper approval is to be considered sabotage.

 

Also a good point.

 

7. Any use of the "purge" module is to be followed by the upload of an NT Approved set of laws immediately. AI Units must be bound to a lawset at all times.

 

Again, good point.

 

Revised Chain of Command:

 

Captain-> HoS IF there is a security emergency, such as the Captain being killed, or code Red, otherwise HoP -> Other heads.

 

...honestly this is a very big change and might be out of the scope for command SoP and better discussed elsewhere

 

I do agree it's a big change, but I'd rather get it out of the way rather than stretch it out beyond even SOP.

 

As such, proposing to change:

 

In the absence of a Captain, the Head of Security is to be considered the Acting Captain;

 

In the absence of a Captain and Head of Security, a vote is to be held among the available Heads of Staff in order to determine who should be considered the Acting Captain;

 

To:

 

In the absence of a Captain, the Head of Personnel is to be considered the Acting Captain. If there is a major station emergency, however, the Head of Security is to be considered the Acting Captain, until such a time as the emergency has passed;

 

In the absence of a Captain, Head of Personnel and Head of Security, a vote is to be held among the available Heads of Staff in order to determine who should be considered the Acting Captain;

 

In addition, adding:

 

In the absence of an assigned Head of Staff, the Captain and/or Head of Personnel may promote a member of the Department to the position of Acting Head of Staff, provided they have majority approval from the rest of Command. This Acting Head of Staff is to step down when an official Head of Staff is assigned

 

[TullyBBurnalot]

*scream

[necaladun]

 

AI maint restrictions could use a few adjustments. Requiring all command members be informed in advance of the law change, and given an opportunity to raise objections would stop captains sneaking laws through.

 

 

I'd go one further and say not only should all command have the chance, but after it's done it's mandatory to tell the crew the new laws, and why.

 

The proposed CoC seems a little odd.

 

 

As one of the better HoS's, I'd quite like your input here. The main problem I find with the HoS becoming acting cap in an emergency is they're generally to damn busy dealing with said emergency to act as a Captain. However, having the authority is generally really needed then, especially if the RD is a ling, the CE a traitor, and medbay a shrine to Nar Sie.

 

And yes, how -do- you step down a Captain, assuming they're not being charged with a Capital crime?

 

[pinatacolada]

[*]If the AI Unit is not malfunctioning or subverted, they are to respond with non-lethal force to illegal Law Changes or Cardings. If the illegal attempts persist, and the perpetrator is demonstrably hostile, lethal force is permitted;

 

Lethal force would break most of the AI laws. Also, how exactly would we enforce SoP on an AI? It's not like you can demote an AI.

[TullyBBurnalot]

 

-snip-

 

While I understand your concerns, my particular issue lies in the fact that Command positions are supposed to be the most responsibility-laden and the ones more subject to scrutiny. People should not be picking a Head position in order to just do whatever it is they want to do. At the end of the day, they're still working for NanoTrasen, and should be held accountable whenever they screw up.

 

A lot of these guidelines are actually stuff that either already happen, or people expect to happen (such as the NT Rep not being a douchebag and threatening to fire people, or the HoP not going around with full access 4noraisins). As for the Captain, well... they're intended to be the single most important job on the station. They're meant to be the one person whose job is to literally babysit everyone and make sure they play along.

 

And again, keep in mind, STANDARD Operating Procedure. Even disregarding the Captain's last Guideline, they can, and should, go around SOP if the situation requires it. Again, this is not inflexible.

 

As for the majority vote for promotion, I can see it's getting some flak. As such, I will be changing it to:

 

The Captain may only promote personnel to a Acting Head of Staff position if there is no assigned Head of Staff associated with the Department. Said Acting Head of Staff must be a member of the Department they are to lead. See below for more information on Chain of Command

 

I believe that would be sufficient?

 

[TullyBBurnalot]

 

HoP should probably be restricted from needlessly handing out additional access rather than specifically captain-level access (I can already see HoP's giving themselves IDs with everything but virology access.)

 

 

That's actually a valid point. However, it's already covered in Guideline 2.

 

The Blueshield is not to request or be provided with additional ID access, Security equipment, or any further weaponry under normal circumstances. Should a situation arise where additional equipment or station access is a requirement to the effective protection of command staff, they should not be be issued without authorization from the Head of Security and/or Captain

 

I liek this one. Adding.

 

AI maint restrictions could use a few adjustments. Requiring all command members be informed in advance of the law change, and given an opportunity to raise objections would stop captains sneaking laws through. I'd also suggest that RD and one other head be replaced with any two heads, though an argument could be made either way. I'd also suggest a guideline stating that the HoS is authorized to use the reset board to remove illegal laws.

 

Adding:

 

Command must be informed prior to the Law Change, and all objections must be taken into consideration

 

To the Guideline. Also, the RD should be given priority over other heads in this, as they are, technically, the one person who is, ICly, most qualified to handle AI Units. That said, also adding:

 

If the number of Command personnel opposing the Law Change is greater than the number of Command personnel in favour, the Law Change is not to be done

 

To the Guideline.

 

The proposed CoC seems a little odd. Currently CoC is Captain>HoP>Vote, but usually ends up as Captain>HoP>HoS>Vote. Changing official CoC Captain>HoP>HoS>Vote seems to be the best choice in my view, but it seems like it's going to be discussed further anyway.

 

Will be discussed.

 

Not sure where it would fall under, but information regarding demoting the captain seems like a worthwhile inclusion.

 

All demotions will be handled in General SOP.

 

[necaladun]

 

In response to the whole "Command having freedom" thing, I think that is too much of a problem personally. Heads of staff, and especially the Captain, are much more of a responsibility to play.

 

Ultimately, the SoP here shouldn't restrict legit playstyles of Captains, but things like uploading stupid laws to the AI, going undercover as a clown/assistant, raiding the armoury so you can explore the gateway, etc, need to all be specifically forbidden.

 

[TullyBBurnalot]

 

I'd go one further and say not only should all command have the chance, but after it's done it's mandatory to tell the crew the new laws, and why.

 

Added.

 

And yes, how -do- you step down a Captain, assuming they're not being charged with a Capital crime?

 

Will be added in General SOP.

 

Lethal force would break most of the AI laws. Also, how exactly would we enforce SoP on an AI? It's not like you can demote an AI.

 

I actually meant it differently, I'll specify it:

 

If the illegal attempts persist, and the perpetrator is demonstrably hostile, lethal force from Command/Security is permitted

 

[Coldflame]

 

As one of the better HoS's, I'd quite like your input here. The main problem I find with the HoS becoming acting cap in an emergency is they're generally to damn busy dealing with said emergency to act as a Captain. However, having the authority is generally really needed then, especially if the RD is a ling, the CE a traitor, and medbay a shrine to Nar Sie.

 

And yes, how -do- you step down a Captain, assuming they're not being charged with a Capital crime?

The thing with the captain is that they don't have any responsibilities. When captainship falls on me as HoS, I use the additional powers mostly as tools to help me do my job effectively, rather than starting to operate primarily as the captain. Counter-intuitively, during low-pressure situations I prefer the HoP to take over so I don't have to deal with running the whole station, however when a crisis happens captain powers can give me the means to run things more effectively.

 

Regarding removing the captain:

If the captain's exceptionally bad, I'll usually pursue a unanimous no-confidence vote and remove them, following the chain of command downwards afterwards. Failing that, I'll get the rep or HoP to contact CC. The only time I'll use physical force to remove a captain is when they present a direct threat to the crew. I do, however, often find a reason to brig particularly bad captains until I can arrange their demotions (generally they commit crimes in the process of being shits).

 

[TullyBBurnalot]

 

Stahp posting faster than I can respond, darnit!

 

Ultimately, the SoP here shouldn't restrict legit playstyles of Captains, but things like uploading stupid laws to the AI, going undercover as a clown/assistant, raiding the armoury so you can explore the gateway, etc, need to all be specifically forbidden.

 

That reminds me. Adding:

 

The Captain is not permitted to perform Security Duty

 

To Captain SOP.

 

[necaladun]

 

As a rule 0 or 1 for the Captain,

 

"As the Captain, you are the utmost authority on the station, and represent NT. The highest standard of decorum is required. Your actions are not to bring NT or the station into disrepute. Captains are picked from the most trustworthy and talented of Command staff, and a Captain lacking these attributes is not fit to lead the station."

 

As for Captain as security...I somewhat have to disagree here.

 

They shouldn't be out patrolling, of course. But especially in low population rounds, the Captain may be one of the only people with brig access, especially if the only other office just got killed. The Captain shouldn't -have- to do security duty for sure, but that often isn't the case. Chasing down a clown for vandalism is over the top when there is a security force, but I don't see anything wrong with them detaining and dragging to the brig someone who has hacked into their office/the bridge, or is committing a crime right in front of them.

 

[TullyBBurnalot]

 

Changed to:

 

The Captain is not permitted to perform regular Security Duty. However, they may still assist Security if they are understaffed, or if they see a crime being committed

 

Emphasis added.

 

[Jguytriple5]

 

This is most likely going to be a no, but can you remove the part 6 from AI maintenance that says freeform laws can only be applied when stricly necessary?

 

Because playing as an AI is WAY more fun when command uploads random, funny laws that do not actualy harm the crew or influence the way the shift is going. I once got a law that said i had to tell a joke every 5 minutes, which was a great law and i got 4 karma that round because of it.

And i mean this game is still supposed to be fun right? because if i recall the intro says something like this

meant to centralize SOP in such a way that allowed for more interaction with the Legal sub-Department

which basicly translates into more fun for NT rep, IAA and Magistrate.

 

But i guess this regulation is to overcome exactly those laws, and make place for laws like "Confirmed cultists aren't crew" and that sort of stuff.

 

Edited April 3, 2016 by Guest

[TullyBBurnalot]

 

As much as I dislike the Slippery Slope argument, letting Command upload Freeform Laws freely can only lead to disaster. Unless of course we sit down and write up every single possibility in which a Freeform Law is allowed or not.

 

As it stands, the "unless absolutely necessary" requirement holds merit. A Freeform Law can be literally anything, and can therefore be abused to hell and back. It stands to reason that something with that amount of power should be limited to situations that VERY MUCH WARRANT IT.

 

Edited April 3, 2016 by Guest

[necaladun]

 

Joke freeform laws like that I really think should be earned by the clown going really out of their way and taking a massive risk to upload them, not command staff. Apart from clowns, Ion laws are your real source there. Command staff should be acting like they're put in charge of a multi trillion dollar space station, not playing around with the equipment for their own amusement.

 

It can also be a huge fuck you to the AI player, forcing them to RP in a way they want.

 

[Spacemanspark]

 

Joke freeform laws like that I really think should be earned by the clown going really out of their way and taking a massive risk to upload them, not command staff. Apart from clowns, Ion laws are your real source there. Command staff should be acting like they're put in charge of a multi trillion dollar space station, not playing around with the equipment for their own amusement.

 

It can also be a huge fuck you to the AI player, forcing them to RP in a way they want.

Thank you.

Thank you so much for saying this.

You have no idea how much I hate it when command does that.

 

[necaladun]

 

HoP:

 

Something something paperwork not necessary but can be done but shouldn't be excessive?

 

[TullyBBurnalot]

Added.

[Sothangel]

The AI isn't a toy, after all.