Horizon Fleet Constitution

From HFWiki
Jump to: navigation, search
This page has been adopted by the FC as an official policy.

The following is the Constitution of the Eighth "Horizon" Fleet as ratified by a vote of the Commanding Officers and Fleet Council of the Horizon Fleet Community on 9 January 2013. It is the product of a Constitutional review held in late 2012 and is a continuation of the original constitution as adopted by the Commanding Officers and Fleet Council on 12 July 2008 as a guideline for fleet membership.

Contents

Article I - Mission Statement

Horizon Fleet seeks to provide a safe, enjoyable environment where members are free to explore the furthest reaches of Gene Roddenberry's creative vision for the future. Our community will be a place where we can share our hopes, dreams, and ideas free from the fear of discrimination or harassment. We are dedicated to providing a quality simming experience throughout the fleet by maintaining an atmosphere of communication and respect. Above all, we are a community which will never cease to push the horizon of mankind's imagination, going boldly where no one has gone before.

Article II - Structure

Whereas the establishment of a certain structure is necessary in order to make the operation of any fleet feasible and as efficient as possible, each simulation will be assigned to a Task Force whose operation will be overseen by a Task Force Commanding Officer with operations of the entire fleet overseen by the Horizon Fleet Council. Horizon Fleet shall operate in what is considered to be the "post-Nemesis time frame". Accommodations may be made for those members in Horizon Fleet interested in simulations of other Star Trek eras should appropriate interest be shown.

Section 1 - Chain of Command

1) All members of Horizon Fleet are expected to abide by the Chain of Command. Positions marked with a + are not considered to be steps in the chain of command with regards to disciplinary measures.

2) When dealing with disciplinary matters, the chain of command begins with the person being disciplined, proceeding upwards from them. It does not begin with the superior of the person seeking to discipline another. The Judge Advocate-General (JAG) is the final authority on all matters relating to judicial and administrative discipline only. In all other matters, the JAG is to be considered as any other member of the Horizon Fleet Council.

3) The Chain of Command for Horizon Fleet is as follows, from highest to lowest:

  • Horizon Fleet JAG (Judicial & Disciplinary matters only)
  • Horizon Fleet Council (as a whole)
  • Task Force CO/ FC Member
  • Task Group CO/FC Member's Deputy +
  • Simulation CO
  • Simulation XO +
  • Simulation Department Head +
  • General Player

4) Under special circumstances, a Committee or designated Council Member may be assigned to oversee the department normally assigned to another Council Member.

5) Unless a Council Member has been designated to oversee a department where the council position is currently vacant or that Council Member is on leave, the Department Deputy will run that department temporarily. Deputies acting as their department head will not gain the voting rights of that Council Member.

6) Any Fleet Member may, upon being disciplined or who is about to be disciplined, petition directly to the Office of the Judge Advocate-General for court-martial.

Section 2 - Task Forces

1) A Task Force (TF) is defined as a group of simulations overseen by a Task Force Commanding Officer (TFCO), assisted by additional members of TF Staff as required.

2) Task Forces may be divided into Task Groups consisting of a smaller number of simulations and overseen by a Task Group Commanding Officer (TGCO).

3) A Task Force Commanding Officer may appoint other staff members with the approval of the Horizon Fleet Council.

4) Task Forces shall be created and modified by means of By-Law.

Section 3 - Horizon Fleet Council

1) The operations of Horizon Fleet shall be overseen by a council of senior members of the fleet known as the Fleet Council (FC).

2) The Fleet Council shall make decisions in a fashion so as to best meet the needs of Horizon Fleet and its members.

3) A list of the topics being discussed by the Fleet Council shall be kept in a designated area on the Horizon Fleet Forums with separate areas for public and Council access. This listing shall be updated no less than once a month in conjunction with Fleet Council monthly reports.

4) Council members shall encourage the members of their Departments to forward their opinions, concerns, or petitions through the chain of command.

5) In order to ensure that each member of the Fleet Council can speak frankly and because some content may be sensitive to the persons involved, the votes and opinions expressed by the members of the Fleet Council will be kept in the strictest confidence.

6) Once finalized, all decisions of the Fleet Council will be supported in full by all Council Members.

7) Fleet Council members shall be responsible for the development and maintenance of documents outlining how their departments shall be run as described in Article VI.3.

8) The Fleet Council may delegate some of its authority to committees established by By-Law.

9) The Fleet Council shall consist of the following members:

  • Judge Advocate-General shall oversee the Office of the Judge Advocate-General (JAG Office)
  • Academy Director shall oversee the Horizon Fleet Academy (HF Academy)
  • One Task Force Commanding Officer shall oversee each Task Force
  • Director of Personnel & Awards shall oversee the Department of Personnel & Awards (DPA)
  • Director of Research & Development shall oversee the Department of Research & Development (R&D)

Article III - Rights and Responsibilities

Whereas some members of Horizon Fleet may fall into more than one category, all members enjoy the rights and responsibilities guaranteed under Section 1 as all are players on some simulation somewhere in the fleet.

Section 1 - General Players

1) All players have the right to have an unresolved dispute mediated and resolved by a member of the Office of the Judge Advocate-General.

2) All players have the right to have Fleet Law applied to them in a fair and even manner no differently than any other player in the fleet.

3) All players have the responsibility to follow the chain of command. Questions regarding the interpretation of rules or any proposals to introduce new aspects to Horizon Fleet should be addressed to the next level in the chain of command from the position in which they occupy and through that level to the next. The Chain of Command is outlined in Article II, Section 1.

4) All players shall leave the determination of the rank of their character to their simulation Commanding Officer so as to ensure an equitable ranking system across the fleet. A player shall not have the rank of their character lowered when transferring from one Horizon Fleet simulation to another without the consent of the player or for just cause. A player reviving a former Horizon Fleet character shall be subject to the same restrictions as with a new character and the rank shall be determined by the Commanding Officer with that in mind.

5) All players shall post to any simulation of which they are a member at least once every two weeks unless they are on a leave of absence or the simulation Commanding Officer has determined otherwise on a ship-wide or personal basis. Posting requirements different than these must be clearly posted on the ship's website.

6) All players will respect the role and authority of a simulation Commanding Officer. They shall not start new missions or significantly alter the plot of the simulation without the permission or direction of the Commanding Officer.

7) All players will recognize the restraints of Star Trek and Horizon Fleet canon.

8) A player in Horizon Fleet is allowed to be an active member of no more than five (5) simulations across Horizon Fleet. At the discretion of the Commanding Officer, a player may control or 'own' secondary characters or "PNPCs" on the simulation, but the player must designate which is his primary character for the purposes of promotions and awards. PNPCs are not to be included in the simulation's IFS manifest. A player may have only one primary character on each simulation they are on.

9) All players will show respect for the characters of other players and shall not use them in a fashion that would not be condoned by or has not been approved by the player owning the character in question.

10) All players who wish to resign their character or position will do so by informing their Commanding Officer. They will not announce their resignation by posting to a public forum such as the simulation mailing list, the Horizon Fleet CO listing, the Horizon Fleet Forums, and so on without having first informed the appropriate authorities. Disrespectful, deliberately insulting, or inappropriate resignation announcements will result in disciplinary action proportional to the offense.

11) All players will attempt to resolve disputes with other players in a respectful manner. They will try to resolve them first with the other player and then with the next person in the chain of command before taking action with higher levels of the chain of command or with the Office of the Judge Advocate-General. The exception to this is if they have been disciplined or are about to be disciplined, in which case they may apply directly to the Office of the Judge Advocate-General for Court-Martial.

12) All players will refrain from starting petitions or spamming mailing lists or other means of communication in order to advance their position on a particular issue. All concerns and proposals should be directed through the chain of command in order to make things more manageable for those who volunteer their time to help administrate the fleet.

13) All players shall agree to the terms of the Horizon Fleet Constitution and shall participate in any Horizon Fleet simulation within the rights and responsibilities laid out in this document.

Section 2 - Simulation Commanding Officers

1) A simulation Commanding Officer shall be required to complete and pass the Horizon Fleet Command Academy, develop a website for his or her simulation, and obtain a minimum of five (5) crew members (excluding the Commanding Officer) before the simulation can be declared 'active'. The Commanding Officer may still conduct their simulation administration as they would normally, with no additional hindrances, during any time when a simulation is considered 'inactive'. Simulations designated as 'inactive' will be a more primary focus for Task Force and Recruitment Staff in order to best help the Commanding Officer reach 'active' status.

2) Simulation Commanding Officers have the right to administer their simulations as they see fit so long as they do not violate the terms of Fleet Law. This includes the right to demote or remove players from his or her simulation and to define the scope and nature of the simulation plot. The demotion or removal of a player shall be reported to the Office of the Judge Advocate-General as well as the Director of Personnel & Awards who shall follow up the action if an appropriate and just reason is not provided.

3) Simulation Commanding Officers have the right to set the ranks of their crew up to and including the rank of Commander (or the equivalent marine or alien rank). Further promotions must be approved by the Task Force Commanding Officer.

  • No member of a simulation may exceed the rank of the simulation's Commanding Officer under any circumstances.
  • A member of a simulation may only hold a rank equal to the simulation's Commanding Officer if it is approved by the Task Force Commanding Officer.
  • No member of a simulation other than the Commanding Officer may exceed the rank of the simulation's Executive Officer.

4) Simulation Commanding Officers have the right to create and award their players with special citations in addition to those created by the Horizon Fleet Department of Personnel & Awards.

5) Simulation Commanding Officers shall not permanently damage, destroy, change the class of, or parts of the specifications of the class as defined by the Horizon Fleet Department of Research & Development of their in-character vessel or starbase without the approval of their Task Force Commanding Officer. All changes to ship class specifications shall be approved or denied in conjunction with the Department of Research & Development.

6) Simulation Commanding Officers shall not destroy or otherwise do anything to affect any base, ship, or other simulation that currently exists in Horizon Fleet (including mothballs). To that end, any event on one simulation taking place in the environment of another shall only occur with the consent of all affected simulation Commanding Officers. An "event" shall be defined as anything that changes the back-story or nature of the simulation such as the location, status, whereabouts, and so on. In the case of ships or stations which do not have a Commanding Officer (such as mothballs and queued ships), the event requires the consent of the Task Force Commanding Officer.

7) Simulation Commanding Officers shall have the final responsibility for recruiting members of their simulation and shall do so within the restrictions set by Fleet Law. They may enlist help and support in this from the Department of Personnel & Awards as well as their Task Force staff if they so desire.

8) Simulation Commanding Officers shall direct any applications to their simulation or existing players on their simulation which do not attain quality posting standards as set by the Commanding Officer to an Academy established for training purposes overseen by the Horizon Fleet Academy Director or remove them from their simulation.

9) No player shall command more than one simulation in Horizon Fleet.

10) In order to receive command, all simulation Commanding Officers shall agree to obey Fleet Law. Commanding Officers are also responsible for ensuring that all players aboard their simulation are aware of the rights and responsibilities established by Fleet Law.

11) Simulation Commanding Officers shall have the right to conduct their simulation in whatever platform or medium they desire so long as it is viable. A Commanding Officer should inform their Task Force Commanding Officer of the platform they intend to use upon being accepted for their command so that he or she may ensure the IFS records are properly updated. The Commanding Officer must also inform his or her Task Force Commanding Officer if he or she wishes to change from one platform to another.

12) Simulation Commanding Officers who wish to have their ship visit a base contained in another Horizon Fleet simulation shall be responsible for contacting the starbase Commanding Officer and undertaking any procedures the starbase Commanding Officer may require for the interaction of the two simulations. Should the requesting simulation Commanding Officer be unable or unwilling to comply with the requirements of the starbase Commanding Officer, he or she shall visit another Horizon Fleet facility or interact with an NPC facility.

13) Simulation Commanding Officers shall file a monthly report to their Task Force Commanding Officer using the form provided by the Integrated Fleet System (IFS) no sooner than the 26th of the month and no later than the first of the next month. (Example: January's monthly report must be submitted between 26th January and midnight on 1st February). 14) A simulation Commanding Officer who resigns from his or her position shall be barred from assuming a new command in Horizon Fleet for ninety (90) days. This time should be used for the player to re-evaluate his or her ability to command. Should a simulation Commanding Officer resign in a public area, as is prohibited by the constitution, an additional six (6) months shall be added to the period in which he or she shall be barred. A simulation Commanding Officer may rescind his or her resignation within twenty-four (24) hours and face no penalty. A Commanding Officer may also petition the Fleet Council for easement of this ninety (90) day barring from command if they are able to provide an acceptable reason why they should be accepted.

15) Not withstanding any provisions in the By-Laws imposing restrictions on such matters, a Task Force Commanding Officer may grant command of a simulation to the Executive Officer or another crew member when a Commanding Officer resigns or is removed, providing said member is not already a Commanding Officer within Horizon Fleet and providing they have submitted an acceptable application for command. Such a Commanding Officer will be required to complete any requirements laid out in this section immediately after assuming the role of Commanding Officer if they have not already been completed. If the Task Force Commanding Officer does not grant command of the simulation to the Executive Officer or another existing crew member, the crew of the simulation shall be reassigned by the Director of Personnel & Awards.

Section 3 - Task Group Commanding Officers

Whereas the Task Group Commanding Officer (TGCO) is the In-Character, Administrative, and Out-of-Character leader of their Task Group, it is expected the Commanding Officers of the Task Group can look to their Task Group Commanding Officer for guidance and advice. They can also expect their Task Group Commanding Officer to be a person who will listen to them in all matters concerning their individual simulations. Specific Task Group Commanding Officer responsibilities include:

1) Task Group Commanding Officers have the right to recommend the Task Force Commanding Officer reject any applications for Commanding Officers received by their Task Group.

2) Task Group Commanding Officers have the right to administer their Task Group as they see fit in cooperation with the Task Force Commanding Officer and within the confines of Fleet Law.

3) Task Group Commanding Officers have the responsibility to work closely with their Task Force Commanding Officer on all matters relating to their Task Group or the Task Force in general.

4) Task Group Commanding Officers have the responsibility to assist in advertisement of their Task Group and the recruitment of new players for simulations within the Task Group.

5) Task Group Commanding Officers have the responsibility to bring to the attention of the Task Force Commanding Officer any and all suggestions and ideas made by members of their Task Group for approval and possible consideration by the Fleet Council.

6) Task Group Commanding Officers have the responsibility to bring to the attention of the Task Force Commanding Officer any major changes to simulations (including ships/starbases, technology, and specification alterations) for final approval from the Fleet Council or one of its members, whichever is most applicable.

7) Task Group Commanding Officers have the responsibility to encourage Commanding Officers and players to participate in Horizon Fleet by setting a good example. This includes sending news articles, using IRC, and participating on the forum.

8) Task Group Commanding Officers have the responsibility to keep the Task Force Commanding Officer updated on any simulation changes in their Task Group.

9) Task Group Commanding Officers have the responsibility to ensure that training is provided for all new simulation Commanding Officers within their Task Group.

10) Task Group Commanding Officers have the responsibility to refer Commanding Officers for removal or who have resigned to the Task Force Commanding Officer and note the circumstances of their departure. A Task Group Commanding Officers also has the right to refer a Commanding Officer who has resigned to the Task Force Commanding Officer if he or she feels the circumstances of the departure merit a longer probation than the standard defined in the Constitution.

Section 4 - Task Force Commanding Officers

Whereas the Task Force Commanding Officer (TFCO) is the In-Character, Administrative, and Out-of-Character leader of their Task Force, it is expected the Commanding Officers of the Task Force can look to their Task Force Commanding Officer for guidance and advice. They can also expect their Task Force Commanding Officer to be a person who will listen to them in all matters concerning their individual simulations. Specific Task Force Commanding Officer responsibilities include:

1) Task Force Commanding Officers have the right to reject any applications for Commanding Officers received by their Task Force.

2) Task Force Commanding Officers have the right to administer their Task Force as they see fit, including the right to choose their own Task Force staff, within the confines of Fleet Law.

3) Task Force Commanding Officers have the responsibility to work closely with their Task Group Commanding Officers. They should consider their Task Group Commanding Officers to be future candidates for Task Force Commanding Officer who should be trained and educated as such.

4) Task Force Commanding Officers have the responsibility to advertise for their Task Force and to assist in the recruitment of new players for simulations within the Task Force.

5) Task Force Commanding Officers have the responsibility to bring to the attention of the relevant Fleet Council Member any and all suggestions and ideas made by members of their Task Force that have been approved by the Task Force Commanding Officers for possible consideration by the Fleet Council.

6) Task Force Commanding Officers have the right to give initial approval for major changes to simulations (including ships/starbases, technology, and specification alterations) while waiting for final approval from the Fleet Council or one of its members, whichever is most applicable.

7) Task Force Commanding Officers have the responsibility to encourage Commanding Officers and players to participate in Horizon Fleet by setting a good example. This includes sending news articles, using IRC, and participating on the forum.

8) Task Force Commanding Officers have the responsibility to keep the Fleet Council updated on any simulation changes in their Task Force.

9) Task Force Commanding Officers have the responsibility to ensure that training is provided for all new simulation Commanding Officers within their Task Force.

10) Task Force Commanding Officers have the responsibility to refer Commanding Officers they have removed or have resigned to the Office of the Judge Advocate-General as well as the Department of Personnel & Awards to be added to the Command Probation list with particular note of the circumstances of their departure. A Task Force Commanding Officer also has the right to refer a Commanding Officer who has resigned to the Office of the Judge Advocate-General if he or she feels the circumstances of the departure merit a longer probation than the standard defined in the Constitution.

Section 5 - Fleet Departments

Whereas proper and efficient fleet operation requires the several distinct areas of expertise, the following Fleet Departments shall be established and delegated the described responsibilities. Fleet Department Heads are granted the authority to issue Standing Orders relating to the operations and procedures of their respective department. Departments shall be created and modified by means of By-Law.

1) The Horizon Fleet Academy

  • The Horizon Fleet Academy will be responsible for the training and certification of fleet members in the form of a Command Academy Course and a Cadet Academy Course as approved by the Fleet Council.
  • The Academy Director shall oversee the Horizon Fleet Academy with the authority to issue Standing Orders relating to the creation and maintenance of educational resources for fleet members as approved by the Fleet Council.
  • The Academy Director shall submit monthly reports to the Legislative Governance regarding the status and progress of the department.

2) The Department of Personnel & Awards

  • The Department of Personnel & Awards will be responsible for the management of fleet members, character information, community development, and recognition of awards.
  • The Director of Personnel & Awards shall oversee the Department of Personnel & Awards with the authority to issue Standing Orders relating to management of fleet personnel, community development, and recognition of awards.
  • The Director of Personnel & Awards shall submit monthly reports to the Legislative Governance regarding the status and progress of the department.

3) The Department of Research & Development

  • The Department of Research & Development will be responsible for ensuring consistency of information within the fleet, reviewing technology-related proposals, as well as updating and maintaining the official IFS and Wiki databases.
  • The Director of Research & Development shall oversee the Department of Research & Development with the authority to issue Standing Orders relating to both content and procedures for determining technological and cultural continuity within Horizon Fleet.
  • The Director of Research & Development shall submit monthly reports to the Legislative Governance regarding the status and progress of the department.

4) Standing Committees

  • The Fleet Council may establish standing committees as needed to assist with operations of the fleet by means of official By-Law. Such committees shall be required to consist of at least one Fleet Council Member.
  • Rulings, decision, findings, or other actions of the Committee shall not carry effect or authority until approved by the Fleet Council. If such rulings, decisions, findings, or other actions will have a significant impact on Fleet operations, procedures, regulations, or other such operational protocol, then such actions will not carry effect or authority until approved by the Legislative Governance.
  • While established, a member of the committee shall submit monthly reports to the Fleet Council regarding the status and progress of the Committee.

Article IV - Horizon Fleet Council

Section 1 - Membership

1) Each Task Force Commanding Officer shall be a member of the Fleet Council

2) The Horizon Fleet Academy Director shall be a member of the Fleet Council

3) The Director of Personnel & Awards shall be a member of the Fleet Council

4) The Director of Research & Development shall be a member of the Fleet Council

5) The Horizon Fleet Judge Advocate-General shall be a member of the Fleet Council

Section 2 - Responsibilities

1) The members of the Fleet Council have the responsibility to run the fleet in an ethical and legal manner.

2) Fleet Council members shall ensure the laws of the fleet are obeyed by all parties and not ignored or by-passed.

3) In case of vacancy or absence of a Fleet Council Member, their Deputy shall be assigned the rights and responsibilities of that member. If the situation involves a simple Leave of Absence whose start or end falls within the period of a vote, the Deputy shall not have voting rights on that issue. In the event no Deputy is available, another member of the Fleet Council may assume temporary authority over the department as acting or emergency substitute.

4) Fleet Council Members may hold no more than one Council-level position except when serving as acting or emergency substitute until a qualified successor for the position may be found.

5) Fleet Council members have the responsibility to build and maintain wiki articles for their respective department. They may seek wiki assistance from the Department of Research & Development.

6) Fleet Council Members have the responsibility of submitting a monthly report to the Fleet Council and Horizon Fleet Commanding Officers mailing lists in the format prescribed by the Fleet Council no later than the 5th of each month.

7) Fleet Council Members have the responsibility to attend any Fleet Staff meetings when held unless other arrangements are made.

8) Fleet Council Members have the responsibility to encourage players to participate in Horizon Fleet by setting a good example. This includes sending news articles, using IRC, and participating on the forums.

9) Fleet Council Members have the responsibility to participate in the Fleet Council mailing list to the best of their ability.

10) Fleet Council Members have the responsibility to keep the Fleet Council updated on any changes and projects in their respective department.

11) A Fleet Council member does not cast a ballot in any vote directly involving themselves (such as position appointments or promotions).

Section 3 - Powers

1) The Fleet Council shall have the sole authority to permanently pass and amend the by-laws and standing orders of Horizon Fleet as per Article VI.

2) The Fleet Council, in conjunction with the Commanding Officers of the fleet, shall have the authority to pass and amend the Constitution and Policies of the fleet as per Article VI.

3) Members of the Fleet Council have the right to administer their respective departments as they see fit, including the right to choose their own departmental staff, within the confines of this constitution, the Selection Policy, and the by-laws.

4) The Fleet Council shall, in conjunction with the Commanding Officers, determine what constitutes Horizon Fleet canon.

5) Fleet Council members have the right to speak freely in any discussion that comes before the Council without fear of penalty for their opinions. Internal discussions of the Fleet Council will be kept private to ensure this right.

6) Fleet Council members have the full right to vote on any matter brought before the Council.

7) The Fleet Council may delegate any of its powers to a sub-committee by By-Law or Executive Order.

8) Membership on the Fleet Council does not automatically grant the member any moderator/administrator powers on the Horizon Fleet Forums, Horizon Fleet Wiki, the Integrated Fleet System, Internet Relay Chat, or elsewhere in the fleet unless it is required in order to perform the duties of their position.

9) All matters before the Fleet Council will be decided by a simple majority (>50%) vote except as defined elsewhere.

Article V - Judge Advocate-General

1) The Horizon Fleet Judge Advocate-General is an out-of-character body designed to ensure fair, impartial, and equitable discharge of Horizon Fleet's rules and regulations.

2) The Office of the Judge Advocate-General will be run according to the Horizon Fleet Code of Justice, which shall be a policy as established in the Fleet Constitution so as to hold primacy over other fleet documents except the Fleet Constitution. The Code of Justice is bound to support the laws of the fleet.

3) The Judge Advocate-General will be responsible for keeping full records of all complaints, whether they go to trial or not, as well as any and all information relating to those complaints, including but not limited to: the Writ, Summons, and Opinions documents of the courts. These documents will be stored in a public part of the Horizon Fleet Wiki Database. These documents will be stored in a public part of the JAG website. Certain documents that are felt to be too sensitive to be available to the public will be stored in a private section available only to officers of the court.

Article VI - Fleet Law Structure

This article details the procedures involved in enacting or amending the laws of the fleet, their purposes, and how they interact with one another. Voting procedures will last one week from the time they are announced to those who may vote unless all votes are received before the week has expired. All votes will be issued and overseen by the Judge Advocate-General.

Section 1 - The Constitution

The Constitution has primacy over all other documents and is the sole document by which all other laws of the fleet derive their authority.

1) A sixty-six percent (66%) majority vote of the entire Fleet Council and of the Commanding Officers is required to amend any part of the Constitution unless otherwise specified below. The total voting tally will be a composite score averaging the total voting results of the Fleet Council with those of the Commanding Officers.

2) Article I and Article VI may only be amended by a unanimous vote of the entire Fleet Council.

3) Horizon Fleet Commanding Officers must be given the opportunity to vote on all constitutional amendments.

4) Constitutional amendments may be proposed by any Fleet Council Member.

5) All Commanding Officer votes ranked Commander or higher must be cast on the Commanding Officers Mailing List after the vote has been announced there. Fleet Council Members cannot vote on this list.

6) All Fleet Council Members must vote and their votes must be cast on the Fleet Council Mailing List after the vote has been announced there.

Section 2 - Policies

Policies shall be important documents that affect Horizon Fleet as a whole and shall have primacy over all other documents except the Constitution.

1) The Code of Justice shall be considered a Policy and shall be considered to have primacy over all other policies.

2) Where two or more Policies contradict one another, the Policy which was first established shall have primacy over the other unless the newer policy is meant as a replacement to the older one.

3) Policies may be proposed by any member of the Fleet Council for discussion.

4) Policies are adopted by a simple majority (>50%) vote of the Commanding Officers and Fleet Council Members who vote. The total voting tally will be a composite score averaging the total voting results of the Fleet Council with those of the Commanding Officers.

5) All Commanding Officer votes ranked Commander or higher must be cast on the Commanding Officers Mailing List after the vote has been announced there. Fleet Council Members cannot vote on this list.

6) All Fleet Council Members must vote and their votes must be cast on the Fleet Council Mailing List after the vote has been announced there.

Section 3 - By-laws

By-Laws shall be created by the Fleet Council to assist in the administration of the fleet, the execution of their duties, or as required by the Constitution. They shall have primacy over Standing Orders.

1) Where two or more By-Laws contradict each other, the By-Law which was first established shall have primacy over the other.

2) By-Laws may be proposed by any member of the Fleet Council for discussion

3) By-Laws are adopted, revoked, or altered by a simple majority vote (>50%) of the Fleet Council

Section 4 - Standing Orders

Standing Orders shall be documents that regulate the international procedures of individual Departments that constitute the Admiralty and any Committees that are established.

1) Standing Orders are developed, maintained, and proposed for discussion by the Fleet Council member whose department they will govern.

2) Where Standing Orders and Executive Orders conflict, the Executive Order shall have primacy over the Standing Order.

3) Standing Orders always replace the previous Standing Orders for a Department.

4) Any changes to Standing Orders must be approved by a simple majority vote (>50%) of the Fleet Council.

5) All votes shall be cast via the Fleet Council Mailing List after the Judge Advocate-General has called for a vote.

Section 5 - Executive Orders

Executive Orders are temporary instructions that handle emergency situations within the fleet.

1) The Fleet Council may make temporary changes to the laws of the fleet by means of Executive Order when urgent action is required.

2) Any Executive Order shall be referred to the Fleet Council for consideration as a permanent change.

3) All Executive Orders shall expire under whichever of the following conditions comes first:

  • The Executive Order is passed or failed under the appropriate guideline for the type of law the order falls under.
  • The Fleet Council revokes the Executive Order
  • After ninety (90) days have elapsed.

4) An Executive Order cannot be extended or reissued once it has expired or been voted down as a policy or by-law.

5) Executive Orders are not meant to be used to remove people from the Fleet without following proper protocol, but may be used to limit the access and authority of people on a temporary basis until either disciplinary proceedings can take place or until a proper decision can be made on the matter.

Article VII - Ratification

The following ratification process is required in order to adopt this Constitution as the basis of legal and administrative governance for the Horizon Fleet Community.

Section 1 - Proposal to Fleet Council

1) The constitutional draft must be proposed or endorsed by a member of the Fleet Council.

2) Once the constitutional draft has been introduced to the Fleet Council, they shall be given a review period lasting seven (7) days. Amendments, revisions, and changes may be proposed during this time without having to restart the entire process.

3) A poll of record shall then be opened to determine whether or not the constitutional draft in its revised form should be brought before the Commanding Officers of the Fleet for discussion. Council Members will have five (5) days in which to approve, reject, or abstain from the vote.

4) The measure must have at least sixty-six percent (66%) affirmation by the Fleet Council in order to be brought before the Commanding Officers for discussion.

Section 2 - Proposal to Fleet COs

1) The constitutional draft must be brought before the Commanding Officers of the Fleet for discussion by the Fleet Council.

2) Once the constitutional draft has been introduced to the Commanding Officers via the Commanding Officers Yahoo Group and Horizon Fleet Forums, they shall be given a review period lasting seven (7) days. Amendments, revisions, and changes may be proposed during this time without having to restart the entire process.

3) A poll of record shall then be opened to determine whether or not the constitutional draft in its revised form should be considered for ratification. Voting members will have five (5) days in which to approve, reject, or abstain from the vote.

Section 3 - Final Vote

Whereas the Horizon Fleet Community has operated under a fleet constitution since shortly after its founding and whereas the current fleet constitution outlines specific procedures relating to a Constitutional Vote (Article III, Section 4), the following procedure shall be used to administer the final ratification vote.

1) A Constitutional Vote shall be a vote among the Fleet Council Members and the Commanding Officers of the Fleet ranked Commander or higher.

2) Each eligible member shall have one (1) vote.

3) If a Commanding Officer also sits on the Fleet Council, he/she shall vote as part of the Fleet Council.

4) Fleet Council members are required to vote.

5) Once a measure requiring a Constitutional Vote has been introduced by the Fleet Council, it shall be distributed to all voting members for a review period lasting seven (7) days.

6) A poll of record shall then be opened and voting members will have five (5) days in which to approve, reject, or abstain from the vote.

7) In order to pass a measure requiring a Constitutional Vote, the measure must have at least two thirds (2/3) affirmation by the voting Commanding Officers and a unanimous affirmation by the Fleet Council.

8) The voting process shall be conducted and overseen by the Judge Advocate-General.