UNDER CONSTRUCTION

UNDER CONSTRUCTION

MEASURE 055: OBSIDIAN FLEET RULES AND POLICIES
Submitted by: Admiral Hawke
Measure Enacted by Fleet Council Vote: 11 August 2012

Banned races list modified by Joint Fleet Command: 11 December 2014
Task Force Setup modified by Measure 61: 9 January 2015
Office of Fleet Recruitment changed to Officer of Public Affairs by Measure 62: 31 May 2016
Secion 5.8 added by Joint Fleet Command to reflect Measure 056: 9 November 2016
In the interests of simplicity and clarity, the Obsidian Fleet Rules and Policies are consolidated as follows.
1. Measures 1, 2, 5, 7, 8, 10, 11, 12, 14, 15, 16, 17, 18, 19, 21, 23, 24, 28, 29, 30, 31, 32, 33, 35, 36, 37, 40, 42, 43, 47, 50, 51, 52, 53, and 54 are repealed.
2. Any General Order not repealed by the removal of the above Measures is hereby repealed.
3. The Fleet Constitution and Code of Justice are not affected by this Measure and continue as enacted and amended.
4. Obsidian Fleet Rules and Policies (See below) is hereby enacted, with the following provisions:

a) Parts I-IV may be amended through the Unanimous Consent Procedure.
b) Part V may be amended through the regular voting procedure.
c) Parts I-IV are to be understood are general Fleet policy and do not affect the ability of Joint Fleet Command to grant exceptions to the policies by virtue of General Executive Authority.
d) Where the relevant Article indicates such, Joint Fleet Command is able to amend the policy indicated.

OBSIDIAN FLEET RULES AND POLICIES

Part I – Player Rules and Policies

1.1 Characters & Biographies

1.1.1 A player character must be original and must have a complete biography.
1.1.2 A sim’s Commanding Officer will determine the acceptability of a player character and the character’s biography.
1.1.3 Characters are the property of the player creating them and may not be used without their consent except for moving the plot on in a minor and acceptable manner.
1.1.4 Canonical characters are not permitted.
1.1.5 A player character is not permitted to be one the races listed below. Additions or subtraction to this list may be made by Joint Fleet Command.

1.1.5.1 Non-Humanoid Races (big rock creatures, Tribbles, etc.)
1.1.5.2 Omnipotent beings (Q, Douwd, etc.)
1.1.5.3 Androids
1.1.5.4 Iconians
1.1.5.5 Shapeshifters
1.1.5.6 Jem-Hadar still in the Dominion
1.1.5.7 Vorta still in the Dominion
1.1.5.8 Suliban
1.1.5.9 Species 8472
1.1.5.10 Augments, Angosians and similar genetically engineered races can only be characters on non-Starfleet sims (civilian, alien, etc..)
1.1.5.11 Races from non-Star Trek continuities

1.1.6 Custom races are permitted, but a detailed description of the culture and abilities is required and accepting the player’s character is at the discretion of the sim’s Commanding Officer.
1.1.7 A player is permitted to play the same characters on a sim set within a different timeline or universe, according to the following guidelines:

1.1.7.1 The duplicate characters must be on two sims in different universes or timelines.
1.1.7.2 The character’s biography must make the situation plausible and must not include time travel.
1.1.7.3 The player must have approval from both COs
1.1.7.4 The player must have approval from both TFCOs (the Joint Fleet Command serves as TFCO for IFO sims)
1.1.7.5 Each manifestation of a character counts as one character toward the 5 character limit.

1.2 Ranks and Promotions

1.2.1 The sim’s Commanding Officer will determine the initial rank of a new player character.
1.2.2 Promotions are at the discretion of the sim’s Commanding Officer.
1.2.3 No player character may be promoted to a rank greater than that of the sim Commanding Officer.
1.2.4 No player character may be promoted to a rank equal to the sim’s Commanding Officer, except the sim’s Executive Officer, in the following circumstances:

1.2.4.1 A Commanding Officer with the rank of Lieutenant Commander may promote their Executive Officer to the rank of Lieutenant Commander with no restrictions.
1.2.4.2 A Commanding Officer with the rank of Commander may promote their Executive Officer to Commander after the Executive Officer has served on the sim for six months.
1.2.4.3 A Commanding Officer with the rank of Captain may promote their Executive Officer to Captain after the Executive Officer has served on the sim for one year and with the approval of the Task Force Commanding Officer.

1.2.5 A Department Head may not exceed the rank of one below that of the Commanding Officer.
1.2.6 A player who is not a Department Head may not exceed the rank of two below that of the Commanding Officer.
1.2.7 A Marine Department Commanding Officer may be promoted to Colonel with the authorization of the Task Force Commanding Officer. (Exception to 1.2.4)
1.2.8 A Commanding Officer who holds a position within the Fleet Operations chain of command shall apply rank and promotion rules as if they held the rank of Captain.
1.2.9 Alterations to these policies may be made by Joint Fleet Command.

1.3 Posting Requirements

1.3.1 Posting Requirements are at the discretion of the Commanding Officer.
1.3.2 They are to be clearly communicated to new players and posted on the sim’s website.
1.3.3 Players are required to post a minimum of once every two weeks.

1.4 Academy Attendance

1.4.1 A Commanding Officer may require a player to attend Cadet Academy.
1.4.2 While attending Cadet Academy a Commanding Officer may restrict the maximum rank a player may be promoted to.

1.5 Number of Player Characters

1.5.1 A player may have a maximum of 5 Player Characters in the Fleet.
1.5.2 Of these, one may be a Commanding Officer.
1.5.3 A player is only permitted to have one Player Character per sim.
1.5.4 A player may have 2 non-posting Characters beyond the 5 Player Characters.
1.5.5 No character may occupy more than one position except Fleet Operations personnel.
1.5.6 Fleet Operations personnel are required to command their sim with their Fleet Operations character.

1.6 Leave of Absence

1.6.1 A player who is unable to post for a period of time may ask for a Leave of Absence (LOA) from the sim’s CO.
1.6.2 The request should indicate when the player expects to return.
1.6.3 A Commanding Officer is not to reject a request for a LOA, except on reasonable grounds.

1.7 Sim Transfers

1.7.1 A player who wants to transfer from one unit to another must submit their character name, rank, position, current unit, proposed new unit and reason for transfer to their current Commanding Officer, their current Task Group Commanding Officer, their proposed Commanding Officer and the Director of the Office of Personnel Management.
1.7.2 Only the approval of the proposed Commanding Officer is required in order to effect a transfer.

Part II – Commanding Officer Rules and Policies

2.1 Applications

2.1.1 Once a Commanding Officer has received an application, they have seven days to contact the player.

2.2 Chain of Command

2.2.1 The chain of command applies to all players within Fleet Operations.
2.2.2 The chain of command is used for all material issues within the Fleet. Issues, concerns, appointments, removals, reports, information etc. should be passed up and down through the chain. The chain applies downwards as well as upwards – senior officers should not directly interfere with a matter which is not directly within their remit unless it is urgent or required by Fleet Law.
2.2.3 If a player has a question or concern, they bring it to the person above them in the chain of command. If that person is unable to assist them, the player is entitled to take their problem or concern to the next step in the chain of command.
2.2.4 A player who fails to adhere to the chain of command may be referred to the appropriate level to address their question or concern.
2.2.5 The chain of command of Fleet Operations is as follows:

2.2.5.1 Commanding Officer
2.2.5.2 Task Group Commanding Officer
2.2.5.3 Task Force Commanding Officer
2.2.5.4 Joint Fleet Command
2.2.5.5 Office of the Judge Advocate-General

2.2.6 Joint Fleet Command is the last step in the chain of command for non-disciplinary matters.
2.2.7 The Office of the Judge Advocate-General is the last step in the chain of command for disciplinary matters.
2.2.8 The chain of command may be varied by Joint Fleet Command.

2.3 Commanding Officer Academy

2.3.1 New Commanding Officers are required to attend and pass the Obsidian Fleet Commanding Officer Academy.
2.3.2 A Commanding Officer who previously passed the Obsidian Fleet Commanding Officer Academy, and who returns within one year of their resignation, are not required to attend the Commanding Officer Academy again.
2.3.3 A Commanding Officer who previously passed the Obsidian Fleet Commanding Officer Academy, and who returns one year or more after their resignation, are required to take the Commanding Officer Refresher Course. Joint Fleet Command my grant an exception to this requirement.

2.4 Operational Status

2.4.1 An Operational sim is defined as posting independently without supervision from the Task Group Commanding Officer. The requirements for achieving and maintaining Operational status are:

2.4.1.1 A minimum of six actively posting players (including the Commanding Officer)
2.4.1.2 Successful completion of the Obsidian Fleet Commanding Officer Academy Course
2.4.1.3 An actively functioning website

2.4.2 No sim will be allowed to post independently until they have met each of these requirements. Until the sim achieves Operational status, they will be on Restricted Independent Operations (RIO). RIO allows a sim to operate
with a degree of independence from the onset, including beginning a basic border patrol / shakedown mission, with no major plot devices, while the Command Academy course is being completed. The Task Group Commanding Officer is to be a part of the sim’s posting list.
2.4.3 Once the requirements to go Operational are completed, the sim will begin independent posting. However, a sim must maintain the requirements listed above to remain operational:

2.4.3.1 If a sim drops below six actively posting players, the Commanding Officer will have a four week grace period to recruit and recover to an operational level. (An additional two weeks can be granted by the Task Force CO to the four week period in extenuating circumstances (a CO must explicitly request the extension from their Task Force CO before the four week time period has lapsed.)
2.4.3.2 If a sim stays below six actively posting players for more than four weeks, the sim will be placed in Restricted Independent Operations (RIO) for a period of no less than one month to allow the Commanding Officer to recruit. During this time, the Task Group Commanding Officer will be subscribed to the mailing list of the sim and will actively monitor the sim and provide assistance as needed. Upon the end of the RIO period, the sim will return to Operational status.

2.5 Leave of Absence

2.5.1 When a Commanding Officer foresees that they will not have internet access or will be unable to fulfill their duties as a Commanding Officer, they are required to submit a Leave of Absence (LOA).
2.5.2 While on a Leave of Absence, a Commanding Officer is not responsible for the normal duties of a Commanding Officer. However, a Commanding Officer is responsible for making arrangements to ensure the continued operation of the sim during their absence.
2.5.3 To submit a Leave of Absence, the Commanding Officer:

2.5.3.1 Sends an e-mail to the Task Group Commanding Officer, Task Force Commanding Officer, and Director of Personnel Management as soon as they are aware they need a Leave of Absence.
2.5.3.2 A few days before the LOA, e-mail the TGCO, TFCO and OPM again to remind them of the LOA and the arrangements that have been made to ensure the continued operation of the sim.

2.5.4 In all communications, include the specific dates of the Leave of Absence and the extent of the absence (total, limited access, etc.)

2.6 Mailing Lists

2.6.1 Each Commanding Officer is required to be a member of the following Mailing Lists:

2.6.1.1 Obsidian Fleet Commanding Officer Mailing List
2.6.1.2 Relevant Task Force Mailing List
2.6.1.3 Relevant Task Group Mailing List

2.6.2 Task Force Commanding Officers are responsible for ensuring that Commanding Officers are a member of each Mailing List.

2.7 Mandatory Voting

2.7.1 Commanding Officers are required to vote in Mandatory Polls on the Obsidian Fleet Commanding Officers Mailing List.

2.8 Mandatory Reporting

2.8.1 Commanding Officers are required to submit a monthly report via IFS.
2.8.2 Reports are accepted beginning at 0000 UTC on the 25th of each month and must be completed by 2359 UTC on the last day of each month.

2.8.2.1 In February, the reporting window begins at 0000 UTC on the 23rd of the month and runs until 2359 UTC on the last day of the month.

2.9 Promotions

2.9.1 Commanding Officers who have never held a command in Obsidian Fleet begin with the rank of Lieutenant Commander.
2.9.2 Commanding Officers who have held a previous command in Obsidian Fleet begin with the rank of Commander.
2.9.3 Upon the successful completion of the Obsidian Fleet Commanding Officer Academy, a Commanding Officer is promoted to the rank of Commander.
2.9.4 A Commanding Officer is eligible for promotion to Captain by meeting the
following guidelines:

2.9.4.1 Six months at the rank of Commander.
2.9.4.2 Dedicated leadership, professional conduct and presentation, and participation in their respective sims, their Task Force, and the Fleet.

2.9.5 Promotion of a Commanding Officer is at the discretion of the appropriate Task Force Commanding Officer, providing the above policies are adhered to.
2.9.6 These policies may be altered by Joint Fleet Command.

2.10 Three Strikes

2.10.1 Where a Commanding Officer neglects to do their duty in relation to their
position, they may be issued a strike.
2.10.2 A strike may be issued for the following reasons:

2.10.2.1 Failure to complete a monthly report.
2.10.2.2 Failure to vote in a mandatory poll on the Command Officer
Mailing List.
2.10.2.3 Failure to handle an application within 7 days of submission.
2.10.2.4 Other major infraction as determined by the chain of command.

2.10.3 Strikes clear at the rate of one every six months.
2.10.4 An additional strike, awarded before a previous strike clears, resets the time applied against the initial strike.
2.10.5 Each strike carries an increased level of disciplinary action.
2.10.6 The disciplinary action of each strike is as follows:

2.10.6.1 First Strike – Formal warning. Notification via email. Entry in Out of Character Service Record.
2.10.6.2 Second Strike – Demotion by one rank for those holding the rank of Commander or above. Loss of automatic promotion for those holding the rank of Lieutenant Commander. Notification via email. Entry in Out of Character Service Record.
2.10.6.2 Third Strike – Removal from Command. Notification via email. Entry in Out of Character Service Record.

2.10.7 If a Commanding Officer is also a member of the Fleet Operations chain of command and they are removed from Command for receiving a Third Strike, they are also removed from their position in the Fleet Operations chain of command.
2.10.8 A player removed from Command for a third strike many not apply for a Command in Obsidian Fleet until the third strike has cleared.
2.10.9 Strikes apply to a character in a specific position.

2.11 Resignation & Removal from Command

2.11.1 A Commanding Officer who resigns their position as Commanding Officer of a sim, is ineligible to command a sim in Obsidian Fleet for a period of ninety (90) days, effective from the date of the resignation.
2.11.2 The Commanding Officer has a period of seven (7) days, effective from the date of resignation, to withdraw their resignation, and regain their command. After that date, if there is a substantial reason for shortening or suspending this rule, they may submit a written request to their Task Force Commanding Officer and the Joint Fleet Command asking for shortening or suspending this rule.
2.11.3 A player whose Commanding Officer Application has been declined is ineligible to apply for a sim as a Commanding Officer for a period of ninety days, effective the date the application was declined.
2.11.4 A Commanding Officer who has been administratively removed from Command is ineligible to apply for a sim as Commanding Officer for a period of ninety days, effective the date of the removal.

2.12 Marine Officers

2.12.1 A Marine Officer may not serve as a Commanding Officer or Executive Officer of a sim.
2.12.2 A Marine Officer may serve as the Commanding Officer or Executive Officer of a Marine Specialty Sim.
2.13 Covert Operations
2.13.1 Sims are not permitted to have covert operations units, hazard teams, black operation units, rapid reaction units, or variant there of.

Part III – Sim Rules and Policies

3.1 Sim Ratings

3.1.1 There shall be three distinct rating levels created for sims in Obsidian Fleet:

3.1.1.1 13+ The standard rating for all sims.
3.1.1.2 15+ May contain limited sexual and violent scenes or have content not suitable for younger fleet members.
3.1.1.3 18+ May contain sexual and violent scenes or have themes and content not suitable for younger fleet members.

3.1.2 All Obsidian Fleet sims shall, by default, have a rating of 13+.
3.1.3 Any Commanding Officer who wishes to request a higher rating for their sim may do so through the following process:

3.1.3.1 E-mail Fleet Operations Department requesting the change and give detailed reasons for the proposed ratings increase.
3.1.3.2 Fleet Operations will review the request and make a decision.
3.1.3.3 The relevant Task Force Commanding Officer will inform the Commanding Officer of the decision.

3.1.4 If a rating increase is approved, the sim rating must be clearly displayed in the mission notes of the sim’s IFS entry, the front page of the sim site and the sim’s application form.
3.1.5 If a rating increase is denied, the Commanding Officer may apply again for a rating increase 90 days after being informed of the decision.
3.1.6 A master list of rating increase requests (both approved and denied) shall be created and maintained by the Joint Fleet Command and be made available to the Task Force Commanding Officers, Office of Personnel Management and Office of the Judge Advocate-General.

3.2 Sim Transfers

3.2.1 Commanding Officers who have commanded in Obsidian Fleet for a period of twelve months or longer may request to transfer to a different class of sim with the approval of their Task Force Commanding Officer.
3.2.2 The request must conform to the following guidelines:

3.2.2.1 The new sim is to be selected from the current list of open/queue sims in Obsidian Fleet. No custom name/class/registry is permitted.
3.2.2.2 Sim names are non-transferrable.
3.2.2.3 Seniority does not carry over to any new CO who takes command of an active sim from another CO.
3.2.2.4 After a change is completed, the twelve month cycle begins again.
3.2.2.5 All transfers are final.

3.2.3 Requests for a transfer prior to the twelve month period of service are considered only in exceptional circumstances. A clear and convincing reason is required and the request must be approved by Joint Fleet Command upon consultation with the relevant TFCO.

3.3 Task Group / Task Force Transfers

3.3.1 Transfers to another Task Group or Task Force, for non-Operational reasons, are considered in exceptional circumstances.
3.3.2 In order to be considered for a Task Group / Task Force transfer all other
attempts to work out issues must be attempted before a transfer may be
requested.
3.3.3 Joint Fleet Command must approve the request upon consultation with the relevant TFCOs.

3.4 Three Strikes

3.4.1 Where a member of the Fleet Operations chain of command neglects to do their duty in relation to their position, they may be issued a strike.
3.4.2 A strike may be issued for the following reasons:

3.4.2.1 Failure to complete a monthly report.
3.4.2.2 Failure to vote in a mandatory poll on the Command Officer Mailing List.
3.4.2.3 Failure to handle an application within 7 days of submission.
3.4.2.4 Other major infraction as determined by the chain of command.

3.4.3 Strikes clear at the rate of one every six months.
3.4.4 An additional strike, awarded before a previous strike clears, resets the time applied against the initial strike.
3.4.5 Each strike carries an increased level of disciplinary action.
3.4.6 The disciplinary action of each strike is as follows:

3.4.6.1 First Strike – Formal warning. Notification via email. Entry in Out of Character Service Record.
3.4.6.2 Second Strike – Demotion by one rank. Notification via email. Entry in Out of Character Service Record.
3.4.6.3 Third Strike – Removal from Position. Notification via email. Entry in Out of Character Service Record.

3.4.7 If a member of the Fleet Operation chain of command is removed from their position for receiving a Third Strike, they are not automatically removed from command of their sim. The provisions in Section 2.10 apply for removal from command.
3.4.8 A player removed from their position for a third strike may not be appointed to a Fleet Operations position until the third strike has cleared.
3.4.9 Strikes apply to a character in a specific position.

3.5 Task Force Setup

3.5.1 Fleet Operations will be organized into the following Task Forces:

3.5.1.1 Task Force 1
3.5.1.2 Task Force 21
3.5.1.3 Task Force 47
3.5.1.4 Task Force 72

3.5.2 Task Force 1 is designated as a special Task Force and is exempt from regular Task Force requirements.
3.5.3 Each Task Force will be headed by a Task Force Commanding Officer, who will be appointed by Joint Fleet Command.
3.5.4 Each Task Force is composed of 19 sims.
3.5.5 Each Task Force will be organized into 4 Task Groups.

3.5.5.1 Independent – Composed of the TF Flagship
3.5.5.2 Task Group A – Composed of 6 sims.
3.5.5.3 Task Group B – Composed of 6 sims.
3.5.5.4 Task Group C – Composed of 6 sims.

3.5.6 Each Task Group will be headed by a Task Group Commanding Officer, who will be appointed by the Task Force Commanding Officer upon consultation with Joint Fleet Command.
3.5.7 Each TFCO will designate one of the TGCOs as Senior Task Group Commanding Officer. The Senior TGCO will assume the position of Acting TFCO if the TFCO is on a LOA.
3.5.8 Each Task Group Commanding Officer will appoint a Senior Ship Commanding Officer (SSCO) upon consultation with the Task Force Commanding Officer.

3.6 Ranks and Promotions

3.6.1 Task Force Commanding Officers are promoted to the rank of Rear Admiral upon their appointment.
3.6.2 A Task Force Commanding Officer is eligible for promotion to Vice Admiral for long and distinguished service.
3.6.3 A Commanding Officer must hold the rank of Captain to be eligible for appointment as a Task Group Commanding Officer.
3.6.4 A Commanding Officer must hold the rank of Captain to be eligible for appointment as a Senior Ship Commanding Officer.
3.6.5 A Task Group Commanding Officer is eligible for promotion to Commodore after six months and for dedicated leadership, professional conduct and presentation, and participation in their respective sims, their Task Force, and the Fleet.
3.6.6 Alterations to these policies may be made by Joint Fleet Command.

Part IV – Fleet Council Rules and Policies

4.1 Fleet Council Member Responsibilities

4.1.1 The role of the Joint Fleet Command will be in accordance with the Fleet
Constitution.
4.1.2 The role of the Judge Advocate-General will be in accordance with the Fleet Constitution, the Code of Justice, and the Standing Orders of the Office of the Judge Advocate-General
4.1.3 The role of the Task Force Commanding Officers will be:

4.1.3.1 Member of the Fleet Council.
4.1.3.2 Responsible for management of a Fleet Task Force.
4.1.3.3 Assures maintenance of Fleet CO mailing list.
4.1.3.4 Appoints, supervises, removes and reprimands Task Force personnel.
4.1.3.5 Maintains or delegates maintenance of the Task Force website.
4.1.3.6 Co-ordinates Task Force level awards in accordance with current policy.
4.1.3.7 Ensures continuous communication within the Task Force on all levels.
4.1.3.8 Point of contact for any matter regarding the respective Task Force.
4.1.3.9 Other duties as assigned by Joint Fleet Command.

4.1.4 The role of the Director of the Office of Personnel Management will be:

4.1.4.1 Member of the Fleet Council.

4.1.4.2 Responsible for the operation of the Office of Personnel Management.
4.1.4.3 Responsible for assigning all ‘any ship’ applications and deleting rejected CO applications.
4.1.4.4 Responsible for handling any transfer requests made by fleet players.
4.1.4.5 Responsible for contacting players of sims who have lost their CO and offer them transfers.
4.1.4.6 Other duties as may be assigned by the Joint Fleet Command.

4.1.5 The role of the Director of the Office of Research and Development will be:

4.1.5.1 Member of Fleet Council.
4.1.5.2 Responsible for all fleet technology.
4.1.5.3 Approves and modifies all technology with direction from Joint Fleet Command [et al.].
4.1.5.4 Ensures only approved technology is used within the fleet.
4.1.5.5 Responsible for consistency within the Fleet on matters regarding in-character technology.
4.1.5.6 Point of contact for any matter regarding technology.
4.1.5.7 Other duties as may be assigned by the Joint Fleet Command.

4.1.6 The role of the Director of the Office of Fleet Services will be:

4.1.6.1 Member of the Fleet Council.
4.1.6.2 Issuing of rules and regulations regarding the Office of Fleet ServicesMember of the Fleet Council.
4.1.6.3 Responsible for the management of the Office of Fleet Services, including the supervision of subordinate personnel;
4.1.6.4 Development and maintaining of the Obsidian Fleet Wiki Database;
4.1.6.5 Responsible for approving new account requests on the Obsidian Fleet Forums;
4.1.6.6 Responsible for monitoring the Obsidian Fleet Forums to ensure the rules are followed;
4.1.6.7 Responsible for all crew awards assigned in the fleet (Levels 1 and 2);
4.1.6.8 Conducts all applicable administration for Level 3 awards;
4.1.6.9 Oversees proper implementation of Unit Awards on a monthly basis (Bronze, Silver, Gold);
4.1.6.10 Development and maintaining of all Services websites;
4.1.6.11 Visualising new specific simulations and/or aiding in their development and implementation;
4.1.6.12 Issuing of rules and regulations regarding the Office of Fleet Services;
4.1.6.13 Other duties as may be assigned by the Joint Fleet Command.

4.1.7 The role of the Commandant of the Fleet Academy will be:

4.1.7.1 Member of the Fleet Council.
4.1.7.2 Responsible for the operations of the Fleet Academy (Cadet, Command and Departmental).
4.1.7.3 Responsible for ensuring that students are assigned an Instructor in a timely manner.
4.1.7.4 Oversees the maintenance of the Fleet Academy website.
4.1.7.5 Being capable of instructing within the Academy.
4.1.7.6 Responsible for investigate all claims referred to them of procedural violations of an Instructor.
4.1.7.7 Responsible for recruitment, training, organization and administration Staff and Instructors of the Academy.
4.1.7.8 Oversees the development of all Academy Courses.
4.1.7.9 Other duties as may be assigned by the Joint Fleet Command.

4.1.8 The role of the Director of the Office of Public Affairs will be:

4.1.8.1 Member of the Fleet Council.
4.1.8.2 Responsible for the operation of the Office of Public Affairs.
4.1.8.3 Responsible for Fleet-wide advertizing and advertizing campaigns.
4.1.8.4 Responsible for Fleet-wide social media updates (Twitter, Facebook, etc.).
4.1.8.5 Responsible for developing, promoting, and maintaining Obsidian Banner Exchange.
4.1.8.6 Responsible for maintaining Obsidian Fleet’s presence in outside banner exchanges and top site lists.
4.1.8.7 Oversees individual Task Force advertizing strategies.
4.1.8.8 Serving as a resource for Commanding Officer to develop and implement individual sim advertisements.
4.1.8.9 Other duties as may be assigned by the Joint Fleet Command.

4.2 Reports

4.2.1 Fleet Department Reports must be submitted to the Fleet Admiralty List by 0000 UTC on the 7th of the following month.
4.2.2 The Fleet Services Department Report must be submitted to the Fleet Admiralty List by 0000 UTC on the 14th of the following month.

4.3 Chain of Command

4.3.1 The chain of command applies to all Fleet Staff members.
4.3.2 The chain of command is to be used for all material issues within the Fleet. Issues, concerns, appointments, removals, reports, information etc. should be passed up and down through the chain. The chain applies downwards as well as upwards – senior officers should not directly interfere with a matter which is not directly within their remit unless it is urgent or required by Fleet Law.
4.3.3 If a player or staff member has a question or concern they bring it to the person above them in the chain of command. If that person is unable to assist them, the player is entitled to take their problem or concern to the next step in the chain of command.
4.3.4 A player or staff member who fails to adhere to the chain of command may be referred to the appropriate level to address their question or concern.
4.3.5 The chain of command of Fleet Departments is as follows:

4.3.5.1 Fleet Department Staff Member
4.3.5.2 Department Head
4.3.5.3 Joint Fleet Command
4.3.5.4 Office of the Judge Advocate-General

4.3.6 Joint Fleet Command is the last step in the chain of command for non-disciplinary matters.
4.3.7 The Office of the Judge Advocate-General is the last step in the chain of command for disciplinary matters.
4.3.8 The chain of command may be varied by Joint Fleet Command.

4.4 Three Strikes

4.4.1 Where a member of the Fleet Staff chain of command neglects to do their duty in relation to their position, they may be issued a strike.
4.4.2 A strike may be issued for the following reasons:

4.4.2.1 Failure to complete a monthly report.
4.4.2.2 Failure to vote in a mandatory poll.
4.4.2.3 Failure to address an application/submission/issue within one week of submission.
4.4.2.4 Other major infraction as determined by the chain of command.

4.4.3 Strikes clear at the rate of one every six months.
4.4.4 An additional strike, awarded before a previous strike clears, resets the time applied against the initial strike.
4.4.5 Each strike carries an increased level of disciplinary action.
4.4.6 The disciplinary action of each strike is as follows:

4.4.6.1 First Strike – Formal warning. Notification via email. Entry in Out of Character Service Record.
4.4.6.2 Second Strike – Demotion by one rank. Notification via email. Entry in Out of Character Service Record.
4.4.6.3 Third Strike – Removal from Position. Notification via email. Entry in Out of Character Service Record.

4.4.7 A player removed from their position for a third strike may not be appointed to a Fleet Staff position until the third strike has cleared.
4.4.8 Strikes apply to a character in a specific position.

4.5 Ranks and Promotions

4.5.1 Department Heads are promoted to the rank of Rear Admiral upon their appointment.
4.5.2 Department Heads are eligible for promotion to Vice Admiral after long and distinguished service.
4.5.3 The Judge Advocate-General is promoted to the rank of Vice Admiral upon their appointment.
4.5.4 Deputy Department Heads are promoted to the rank of Commodore upon their appointment.
4.5.5 The Deputy Judge Advocate-General is promoted to the rank of Rear Admiral upon their permanent appointment.
4.5.6 Assistant Judge Advocates-General are promoted to the rank of Commodore upon their permanent appointments.
4.5.7 Alterations to these policies may be made by Joint Fleet Command.

Part V – Fleet Rules and Policies

5.1 Data Access Policy

5.1.1 No Fleet Member may use the IFS to enter, alter, obtain or access data without authorization from the Joint Fleet Command and subject to such conditions as they may impose.
5.1.2 In the event the Joint Fleet Command cannot agree on a matter the wishes of the Data Controller shall prevail.
5.1.3 Theft (or the unauthorized removal) of email addresses, ages or any information held on the system relating to a Fleet Member in person (i.e. their real name, real age etc.) is an offence contrary to the Fleet Law and the mandatory punishment is removal from the Fleet, unless the Office of the Judge Advocate-General believes it is not in the interests of justice to do so.

5.2 Unexplained Leave of Absence Policy

5.2.1 Any Fleet Member deemed to be on unexplained leave of absence for a period of two weeks or more, dated from the last communication, the Joint Fleet Command or the relevant superior officer may petition the Office of the Judge Advocate General to have the Member removed from office. The Office of the Judge Advocate General may, at its discretion, permit a one week extension to the time limit.
5.2.2 Fleet Senior Staff Members who have been removed from office under this Policy may appeal their removal to the Office of the Judge Advocate General. If the appeal is successful, their rank shall be restored and they shall be appointed as a Staff Advisor until the next FSS position arises.
5.2.3 The same appeal procedure shall apply to any other Fleet Member, with the relative rank and next appropriate office available.

5.3 Equal Opportunities Policy

5.3.1 The Obsidian Fleet Council believes that people should not be subject to discrimination or harassment and that equal opportunities are fundamental to the work and nature of Obsidian Fleet.
5.3.2 Discrimination against any person or group of individuals on the basis of political or religious beliefs, race or colour, appearance or martial status, ethnicity or nationality, gender or sexual orientation, illness, age, responsibility toward dependants, disability or the adoption of favouritism or favourable practice will not be tolerated. However, in order to ensure compliance with laws of the various nations the Obsidian Fleet operates in, Obsidian Fleet requires that all members be over the age of 13. In the instances of sims with higher age ratings, minimum age requirements will be permitted if clearly posted and if authorized by the Fleet Command.
5.3.3 Harassment may be defined as offensive or hostile acts or expressions, which include verbal abuse, insults, jokes, threats and physical assault. In particular it is when interference with another person’s work or social life creates an intimidating or hostile environment. Any difficulty in defining harassment shall not prevent complaints being made.
5.3.4 Any person found guilty by the Office of the Judge Advocate-General of breaking this policy will face expulsion from Obsidian Fleet, unless the Office believes it is not in the interests of justice to do so.

5.4 Foreign Relations Policy

5.4.1 Obsidian Fleet is an independent RPG organisation governed by its own rules, policies, and strategies as laid forth by the appropriate governing 8/10/2012
bodies within the Fleet. Obsidian Fleet respects the rights of other fleets, groups and individual RPG simulations to pursue their own rules, policies and strategies without interference.
5.4.2 Obsidian Fleet is open and willing to discuss any matters of concern, requests for information or materials, or proposals for affiliations – alliances, sister fleets or other new relationships – made known to it by external simulations, fleets, or other RPG organisations. We do not bind ourselves with our current policies and are always open-minded to entertaining new ideas and suggestions. We welcome any involvement with other simulations toward a common view of promoting RPGing worldwide by engaging in relationships with those who share our interests and ideas.
5.4.3 Obsidian Fleet is open to contact at all levels of the chain of command. The main route for contact is through the Joint Fleet Command, but potential players or those interested in our operations are more than welcome to contact any member of the Fleet Council or players in order to find out more.
5.4.4 Obsidian Fleet takes any misconduct by its members very seriously and such misconduct cannot and will not be tolerated. Should any person feel that an Obsidian Fleet member has behaved in a discourteous manner, he or she is encouraged to contact the Joint Fleet Command, which may request the Office of the Judge Advocate General (whose remit is to supervise player conduct) to investigate the matter in complete confidence. Members of the Joint Fleet Command and the JAG will be more than happy to help and to hopefully achieve an amicable settlement. Obsidian Fleet JAG is also available through the JAG website: http://jag.obsidianfleet.net.
5.4.5 Any Obsidian Fleet member who is contacted in a hostile manner or who is aggrieved by a member of another fleet or simulation should contact their CO and JAG. The matter will be dealt with as quickly as possible. Obsidian Fleet takes the welfare of its players very seriously and is ready to defend our rights at any time, even through real life legal action. We view this, however, as a last resort and hope that all problems can be sorted out in their early stages.

5.5 IRC Rules of Conduct

5.5.1 Language must, at all times, be polite and respectful to other users. While swearing is permitted, users must exercise good judgement as to what is acceptable. The same applies for descriptions of violence. Overtly sexual material is not acceptable. As a courtesy to others, conversation is only permissible in English. Should other users wish to speak in another
language, they are advised to converse in a private message or in another room. If in doubt, a player should err on the side of caution/consult with the Operator(s) present in the channel.
5.5.2 All users shall be aware of the Obsidian Fleet Equal Opportunities Policy and adhere to it.
5.5.3 No user shall abuse any other Fleet Member or any other external organisation.
5.5.4 No recruitment is permitted.
5.5.5 The authority of channel Operators is unquestionable. Any and all users shall submit to their authority instantly should they be called to do so. The channel Operators are responsible for the maintenance of good conduct in the OF IRC channels.
5.5.6 Channel Operators may make other rules at their discretion to promote good conduct in the IRC channels.
5.5.7 Any user found contravening these rules are liable in the first instance to the full IRC disciplinary powers of Operators (i.e. kicks, bans etc.). Should a serious breach occur, proceedings may be instigated before JAG. Any user may also appeal the verdict of an Operator to JAG.
5.5.8 In all official Obsidian Fleet chat rooms, an operator (op) is defined as a member of the Obsidian Fleet Council holding the rank of Vice-Admiral or above (including Marine equivalents), or holding the position of Task Force Commanding Officer. Additional members of the Obsidian Fleet Council shall have their mode set +v to denote to the general public that they are Fleet Council members. Absent any channel operators, Fleet Council members shall take operator privileges when required for appropriate monitoring of the chat room.

5.6 Fleet Protection Order

5.6.1 Obsidian Fleet reserves the absolute right to request and require the removal of any player who is deemed to constitute a risk to the safe gaming environment.
5.6.2 A player will be deemed to constitute such a risk by the collective agreement of the Joint Fleet Command, the Judge Advocate General and the next senior member of the Office as determined by the Standing Orders of the Office.
5.6.3 The Judge Advocate-General shall also be understood to mean the Acting Judge-Advocate-General or the Commissioners for the Execution of the Office of the Judge Advocate-General.
5.6.4 The Judge Advocate-General has the authority to develop Standing Orders for the implementation of a Fleet Protection Order.

5.7 Appointment Policy

5.7.1 All appointments and promotions in the Fleet are to be made on the basis of merit only.
5.7.2 In the event of a conflict of interest, appointments must be made in co-operation with the appointer’s immediate superior.
5.7.3 “Conflict of interest” is defined as anything non-meritorious that could advantage one candidate over other potential candidates.
5.7.4 If, upon consultation with the appointer, the appointer’s immediate superior is of the opinion that no conflict of interest exists, the appointment process shall proceed as outlined in this measure’s other provisions and in other fleet legislation.
5.7.5 Any appointment made in contravention of this principle is void on application to the Office of the Judge Advocate-General.
5.7.6 Any Fleet Member who intentionally makes an appointment, or attempts to make an appointment, which they know not to be based on merit principle is guilty of a Standard Offence.
5.7.7 Any Fleet Member who attempts to assist, procure or secure the appointment of a Fleet Member in a like manner is also guilty of a Standard Offence.
5.7.8 Joint Fleet Command may issue guidelines regarding the appointment of Fleet Council members.

5.8 Fair Use of Copyrighted Material Policy

5.8 Fair Use of Copyrighted Material Policy
5.8.1 Star Trek and everything related is copyright of Paramount Pictures and CBS.
5.8.2 Copyrighted material is used here in a non-profit way.
5.8.3 Exchange of money or goods for services involving copyrighted material is not allowed by Fleet members.
5.8.4 Obsidian Fleet does not endorse or condone the transaction of financial affairs of any type between one member and another.
5.8.5 Fleet management and the Fleet Data Controller reserve the right to remove players should they be found to be conducting such transactions.