Pegasus Fleet Constitution


Revision as of 15:35, 2 July 2010 by Williams (talk | contribs)

The following is the 11th Fleet Constitution; it and by-laws passed under its authority serve as a guide to Pegasus Fleet's membership.

Article I - Mission Statement

Pegasus Fleet seeks to provide a positive, creative and challenging environment for members to write about the Star Trek universe, whilst being both safe and enjoyable for all. We shall strive to provide an environment in keeping with gene Roddenberry's vision - free of any form of discrimination or harassment, where members are encouraged to express originality, inventiveness, and to pursue and harness their full potential, exploring the farthest reaches of the Star Trek realm. We shall aim to provide a fleet whose simulations speak of excellence in quality, whose members are held, and hold others, in the highest respect. Through an ever evolving system of governance, we shall provide support and resources to all members, and shall strive to be ambassadors to all others in the Star Trek community. Above all else, we shall aim to let our imaginations take flight, and soar boldly where no one has gone before.

Article II - Structure of the Fleet

In order to make the operation of any fleet feasible and as efficient as possible, it is necessary to establish a certain structure to the fleet. Each simm will be assigned to a Task Force, whose operation will be vested in a Task Force Commanding Officer. The operation of the fleet as a whole is vested in the Pegasus Fleet Admiralty. The main operations of Pegasus Fleet are in what will be referred to as the "post-Nemesis time frame". As the film Star Trek: Nemesis was released in the year 2002, and set in 2379, the post-Nemesis timeline is defined as 377 years after the real-world date. In time, and if appropriate interest is shown, accommodations may be made for those members in Pegasus Fleet interested in simming in other eras of Star Trek.

Section 1 - Chain of Command

1. All members of Pegasus Fleet have the responsibility to follow the chain of command, as outlined in Article III. The Chain of Command is as follows, from lowest to highest:

  • General Player
  • Simm Executive Officer
  • Simm Commanding Officer
  • Task Group Commanding Officer
  • Task Force Commanding Officer/Chief of Fleet Operations
  • Pegasus Fleet Admiralty
  • Pegasus Fleet Executive Officer
  • Pegasus Fleet Commanding Officer
  • Pegasus Fleet Judge Advocate General (Judicial & Disciplinary matters only)

2. The Judge Advocate General (JAG) is the final link in the chain of command for judicial and disciplinary matters only. For all other matters, the JAG is to be treated as any other member of the Pegasus Fleet Admiralty.

  1. A player may at any time take an issue direct to the Judge Advocate General if they feel the need for it is warranted

Section 2 - Task Forces

  1. A Task Force is defined as a group of simms supervised by a Task Force Commanding Officer (TFCO), who may be assisted by additional members of Task Force Staff, as required.
  2. Task Forces may be divided into Task Groups consisting of a smaller number of simms, supervised by a Task Group Commanding Officer (TGCO).
  3. A TFCO may appoint other staff members with the approval of the Pegasus Fleet Commanding Officer (PFCO) or Executive Officer (PFXO).
  4. The size and specific structures allowed in Task Forces may be defined by by-law.
  5. Task Forces shall be created and modified by means of by-law.
  6. When no active Task Force has been established by by-law, all simulations will be supervised by the Chief of Fleet Operations.
    1. The Chief of Fleet Operations is a temporary position, which shall be created while no active Task Force exists within the Fleet, and shall be disbanded upon the creation of an active Task Force.

Section 3 - Pegasus Fleet Admiralty

  1. The operations of Pegasus Fleet shall be overseen by a council of senior members of the fleet known as the Pegasus Fleet Admiralty (PFA).
  2. The PFA shall make decisions in a fashion so as to best meet the needs of Pegasus Fleet and its members. In order to facilitate this, it shall proceed as follows:
    1. A list of the topics being discussed by the PFA shall be kept in a publicly accessible area on the Pegasus Fleet Wiki Database, and shall be updated on the 1st day of every month.
    2. TFCOs shall encourage the members of their Task Forces to forward their views on matters being discussed through the chain of command.
  3. In order to ensure that each member of the PFA can speak frankly, and because some content may be sensitive to the persons involved, the votes made by and the opinions expressed by the members of the PFA will be kept in the strictest confidence.
  4. Once finalised, all decisions of the PFA will be supported in full by all members of the PFA.
  5. The PFA may delegate some of its powers to committees established by this constitution or by by-law.

Section 4 - Sister Fleets

  1. Sister Fleets are defined as other simming fleets or organisations which wish to ally with, and have an official close working relationship with Pegasus Fleet, yet still remain an independent organisation from Pegasus Fleet.
  2. Members of Sister Fleets do not fall under the scope of the 11th Fleet Constitution.
    1. A Sister Fleet is free to set their own rules and regulations for their members. The PFA shall have no authority over the operations of a Sister Fleet.
    2. The commanding officer of a Sister Fleet does not have any standing within the body known as the Pegasus Fleet Admiralty, nor any part of the Pegasus Fleet governance.
    3. Not withstanding the above, members of Sister Fleets will be expected to abide by all relevant Pegasus Fleet guidelines when making use of Pegasus Fleet resources (such as forums, the wiki, etc).
  3. Sister Fleets shall be managed by means of one by-law for each sister fleet which is officially recognised as such. Said by-law shall list the name of their fleet and the URL of their website. The Sister Fleet can also define the nature of their relationship with Pegasus Fleet, including, but not limited to, exchanging links, joint missions, character exchanges, and use of fleet resources.
  4. The status of a Sister Fleet is a non-binding agreement and may be dissolved by either party at any time.
    1. The Sister Fleet's Commander may do so by informing the Pegasus Fleet CO, who will then instruct the PFA to update the aforementioned by-law.
    2. Pegasus Fleet may dissolve a Sister Fleet arrangement through a vote to update said by-law as directed by Article IV, Section 2.

Article III - Rights and Responsibilities

Some members of Pegasus Fleet may fall into more than one category. All members enjoy the rights and responsibilities of Section 1, as all are players on some simm 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 Judge Advocate General's office.
    1. No Pegasus Fleet member will use the threat of a JAG investigation to intimidate other players. JAG shall have the right to determine penalties for players, COs and PFA members in cases where they have unnecessarily used the threat of JAG investigation to intimidate other players.
  2. All players have the right to have the constitution and by-laws applied to him or her in a fair and even manner, no different than any other player in the fleet.
  3. All players have the responsibility to follow the chain of command; questions surrounding the interpretation of rules or any proposals to introduce new aspects to PF canon 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 level and so forth. The chain of Command is outlined in Article II, Section 1.
  4. All players have the responsibility of creating original characters which are not established Star Trek, Star Wars, or any other commercial show, movie or game's characters or relatives thereof, nor already created Pegasus Fleet characters or relatives thereof without the permission of the creator of the Pegasus Fleet character.
  5. 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 PF simm to another without the consent of the player or for just cause. A player reviving a former PF character shall be subject to the same restrictions as a new character and the rank shall be determined by the CO with that in mind.
  6. All players shall post to any simm in which they are a member at least once every two weeks unless they are on a leave of absence or the simm CO has determined otherwise on a ship-wide or personal basis.
  7. All players will refrain from the unsolicited recruitment of other Pegasus Fleet members to play on any simm inside or outside of PF.
  8. All players will comply with the age rating of simms and refrain from using profanity or sexuality in excess to that which has been used in Star Trek television shows and movies in their posts.
  9. All players will respect the role of a simm CO and shall not start new missions or significantly alter the plot of the simm without the permission or direction of the CO.
  10. All players will recognise the restraints of Star Trek and PF canon and will not create unusual and abnormal classes of ships, types of weapons and alien creatures without the approval of the PFA.
  11. A player in PF is allowed to be an active member of no more than 5 simms across PF. At the discretion of the CO, a player may control or 'own' secondary characters or "PNPCs" on the simm, but the player must designate which is his primary character for the purposes of promotions, awards, and simm reports. PNPCs are not to be included in the simm's IFS manifest, and are not to be included in the CO's monthly report. A player may only have one primary character on each simm they are on.
  12. 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.
  13. 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 simm mailing list, the PF COs list, the PF Forums, and so on.
  14. All players will try to resolve any disputes with other players in a respectful manner and 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.
  15. 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. In order to make things manageable for those players who volunteer their time to help run the fleet, all concerns and proposals should be directed through the chain of command.
  16. All players have the right to take a leave of absence from their simm(s) and/or position(s), without fear of loss of rank, when they have real life commitments to which they must attend.
  17. All players will participate in Pegasus Fleet with the primary aim of having fun.
  18. All players shall agree to the terms of the Pegasus Fleet Constitution and as such shall play in any Pegasus Fleet simms within the restrictions laid out in this document and shall also enjoy the rights laid out in this document.
  19. All Pegasus Fleet players are entitled to a harassment-free environment, where they are not discriminated against in any out of character environment due to religion, skin colour, nation, gender, sexual orientation, disability, veteran status, marital status or any other characteristic.
  20. All players have the responsibility of keeping the PF forums a safe, fun, and non-stressful environment for all of its users.

Section 2 - Simm Commanding Officers

  1. A Simm CO shall be required to complete and pass the command academy, develop a website for his or her simm, and obtain a minimum crew of 5, excluding the CO, before the simm can be declared 'active'. During the time where a simm is considered ‘inactive’, the CO may still conduct their simm administration as they would normally, with no additional hindrances. However, the simm will be a more primary focus for the Task Force and Recruitment Staff, to attempt to help the CO attain ‘active’ status.
  2. Simm COs have the right to administer their games as they see fit so long as they do not violate the terms of this constitution and its by-laws. This includes the right to demote or remove players from his or her simm and to set the scope and nature of the plot of their simm.
    1. The demotion or removal of a player shall be reported to the Office of the Judge Advocate General, who shall follow up the action if an appropriate and just reason is not provided.
  3. Simm COs have the right to set the ranks of their crew up to and including the rank of Commander (or its equivalent in marine or alien rank). Further promotions shall be approved by the TFCO.
    1. No member of a simm may exceed the rank of the simm's Commanding Officer, under any circumstances.
    2. A member of a simm may only hold a rank equal to the simm's Commanding Officer if approved by the TFCO.
    3. No member of a simm other than the Commanding Officer may exceed the rank of the simm's Executive Officer.
  4. Simm COs have the right to create and award their players with special citations created by the CO, in addition to those created by the Pegasus Fleet Department of Personnel Management.
  5. Simm COs shall not permanently damage, destroy, change the class of or parts of the specifications of the class, as defined by Pegasus Fleet Research & Development, of their in-character ship or starbase without the approval of their TFCO.
    1. All changes to ship class specifications shall be approved or denied in conjunction with the Office of Research & Development.
  6. Simm COs shall not destroy or otherwise do anything to affect any base, ship or other simm that currently exists in Pegasus Fleet, including mothballs. To that end, any event on one simm taking place in the gaming environment of another shall only occur with the consent of all affected Simm COs. "Event" shall be taken to mean anything that changes the back story or nature of the simm such as the location, status, whereabouts, and so on. In the case of ships or stations which do not have a CO (such as mothballs and queued ships), the event requires the consent of the PFCO.
  7. Simm COs shall have the final responsibility for recruiting members of their simm and shall do so within the restrictions set by this constitution. They may enlist help and support in this from the Department of Fleet Recruitment and their Task Force staff, if they desire it.
  8. Simm COs shall direct any applications to their simm or existing players on their simm which do not attain quality posting standards as set by the CO to an Academy established for training purposes under the Pegasus Fleet Academy Commandant, or remove them from their simm.
  9. No player shall command more than one simm in Pegasus Fleet.
  10. In order to receive command, all Simm COs shall agree to obey the Pegasus Fleet Constitution. COs are also responsible for ensuring that all players on their simm are aware of the Constitution, the rights they enjoy therein and the responsibilities of the Simm CO.
  11. Simm COs shall have the right to conduct their game in whatever platform they wish, so long as it is viable. A CO should inform their TFCO upon being accepted for their command of the platform they intend to use, so that he or she may ensure that the IFS records are properly updated. If a CO wishes to change from one platform to another, the CO must inform his or her TFCO.
  12. Simm COs who wish to have their ship visit a base contained in another PF simm shall have the responsibility of contacting the Base CO and undertaking any procedures that the Base CO may require for interaction of the two simms. Should the requesting simm CO be unable or unwilling to comply with the requirements of the Base CO he or she shall visit another PF base or, alternatively, interact with an NPC base.
  13. Simm COs shall file a monthly report to their TFCO, in the form prescribed by the Integrated Fleet System (IFS), no sooner than the 26th of the month the report is dues for, and no later than the 1st of the next month. (January’s monthly report must be submitted between 26th Jan and midnight on 1st Feb)
  14. A simm CO that resigns from his or her position shall be barred from taking a new command in PF for 90 days in order to allow for a "cooling off" period. During this time, the player can re-evaluate his or her ability to command. Should a simm CO resign in a public area, as is prohibited by the constitution, an additional 6 months shall be added to the cooling off period.
    1. Notwithstanding the above, a simm CO may rescind his or her resignation within 24 hours and face no penalty.
  15. Notwithstanding any provisions in the by-laws imposing restrictions on such matters, a TFCO may award command of a simm to the XO or another crew member when a CO resigns or is removed providing said member is not already a CO within Pegasus Fleet. Such a CO will be required to complete any requirements laid out in this section, if they are not already completed, immediately after his or her assuming the role of CO.
    1. If the TFCO does not award command of the simm to the XO or another existing crew member, then the crew of the simm shall be reassigned by the Office of Personnel Management.

Section 3 - Task Force Commanding Officers

Summary of TFCO responsibilities

In general, the Task Force Commanding Officer (TFCO) is the In-Character, Administrative and Out-of-Character leader of their Task Force. The COs of the Task Force can look to their TFCO for guidance and advice, and expect from their TFCO a person who will listen to them with all matters concerning their individual simms.

Specific TFCO responsibilities

  1. TFCOs shall be a member of the PFA and shall not occupy any other PFA-level position except on an acting or emergency basis until a qualified person for the position can be found.
  2. TFCOs have the right to reject any applications for players or COs coming to his or her TF.
  3. TFCOs have the right to administer their Task Force as they see fit, including the right to choose their own TF staff, within the confines of this constitution and its by-laws.
  4. TFCOs have the right to vote on all matters that come before the Pegasus Fleet Admiralty. In casting these votes a TFCO shall take into account not only his or her opinion on the matter but also the interests of his or her Task Force which he or she represents on the PFA.
  5. TFCOs have the responsibility to work closely with their TGCOs, if applicable, who should be treated as TFCOs-in-waiting and trained and educated as such.
  6. TFCOs have the responsibility to submit a monthly report to the PFA and PF COs mailing list, in the form prescribed by the PFCO, no later than the 6th of each month.
  7. TFCOs have the responsibility to build and maintain a website for their Task Force.
  8. TFCOs have the responsibility to advertise for their Task Force, and to assist in the recruiting of new players for simms within the Task Force.
  9. TFCOs have the responsibility to bring to the attention of the relevant PFA member any and all suggestions and ideas made by members of their Task Force that have been approved by the TFCO, for possibility of becoming PF canon.
  10. TFCOs have the right to give initial approval for major changes to simms (including ships/starbases, technology, and specification alterations) while waiting for final approval from the Pegasus Fleet Admiralty or one of its members, whichever is most applicable.
  11. TFCOs have the responsibility to attend any Fleet Staff meetings when held, unless other arrangements are made.
  12. TFCOs have the responsibility to encourage COs and players to participate in Pegasus Fleet by setting a good example. This includes sending news articles, using IRC and the forum, and voting for PF.
  13. TFCOs have the responsibility to participate in the PFA mailing list to the best of their ability.
  14. TFCOs have the responsibility to vote for PF as often as possible, daily is preferred.
  15. TFCOs have the responsibility to keep the PFCO and PFXO updated on any simm changes in their Task Force.
  16. TFCOs have the responsibility to ensure that training is provided for all new Simm COs within their Task Force.
  17. TFCOs have the responsibility to refer COs they have removed or have resigned to the JAG Office to be added to the Command Probation list, and note the circumstances of their departure. A TFCO also has the right to refer a CO who has resigned to JAG if he/she feels the circumstances of the departure merits a longer probation than the standard defined in the constitution.

Section 4 – Members of the PFA

  1. The members of the Pegasus Fleet Admiralty have the responsibility to run the fleet in an ethical and legal manner.
  2. PFA members shall ensure that the rules outlined in this constitution and its by-laws are obeyed by all parties, and not ignored or by-passed when it suits.
  3. PFA members may only hold no more than one PFA-level position except on an acting or emergency basis until a qualified person for the position can be found.
  4. Members of the PFA 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 and its by-laws.
  5. PFA members have the right to speak freely in any discussion that comes before it without fear of penalty for their opinions.
  6. PFA members have the right to vote on any matter that is brought before it.
  7. PFA members have the responsibility to build and maintain a website for their respective department.
  8. PFA members have the responsibility of submitting a monthly report to the PFA and PF COs mailing lists in the format prescribed by the PFCO no later than the 6th of each month.
  9. PFA members have the responsibility to attend any Fleet Staff meetings when held, unless other arrangements are made.
  10. PFA members have the responsibility to encourage players to participate in Pegasus Fleet by setting a good example. This includes sending news articles, using IRC and the forum, and voting for PF.
  11. PFA members have the responsibility to participate in the PFA mailing list to the best of their ability.
  12. PFA members have the responsibility to vote for PF as often as possible, daily is preferred.
  13. PFA members have the responsibility to keep the PFCO and PFXO updated on any changes and projects in their respective department.

Section 5 - Pegasus Fleet XO

  1. The Pegasus Fleet Executive Officer (PFXO) shall be a member of the PFA and serve as its vice-chair and shall not occupy any other PFA-level position except on an acting or emergency basis until a qualified person for the position can be found.
  2. The PFXO will coordinate with the respective TFCOs and the DPM on keeping the Integrated Fleet Management System and fleet mothballs lists up to date, in order to make sure requests and transfers are smooth and coordinated. This will also maintain an accurate list of simm locations.
  3. In the event of an LOA or unexplained absence of the PFCO during which the PFCO cannot be reached, the PFXO shall act as PFCO until such time as the PFCO returns, resigns or is removed from office. In the event of the absence of the PFXO, the person(s) eligible to act for the PFCO in these circumstances shall be determined by by-law. Anyone acting in the capacity of PFCO shall have the full powers of the PFCO, except for the power of executive order.
  4. The PFXO shall perform other such duties as delegated to him or her by the PFCO or by the PFA by by-law.

Section 6 - Pegasus Fleet CO

  1. The Pegasus Fleet Commanding Officer (PFCO) shall be the chief executive of Pegasus Fleet and shall serve as chair of the PFA. He or she shall not occupy any other PFA-level position except on an acting or emergency basis until a qualified person for the position can be found.
  2. The PFCO shall have a deciding vote in the case of a tie for matters before the PFA even if he or she has already cast a vote.
  3. The PFCO has the final say in all matters brought up the chain of command that do not require a decision of the PFA.
  4. The PFCO shall nominate persons to occupy all PFA-level positions, subject to approval of the PFA. The PFCO, when nominating someone in a TF chain of command, is advised to consult with the TFCO to determine the suitability of a person prior to nominating him or her for the PFA.
  5. The PFCO may delegate any of his or her powers, save those surrounding executive orders, to other members of the PFA.
  6. In the event of an LOA or unexplained absence of the PFCO during which the PFCO cannot be reached, the PFXO shall act as PFCO until such time as the PFCO returns, resigns, or is removed from office. In the even of the absence of the PFXO, the person(s) eligible to act for the PFCO in these circumstances shall be determined by by-law. Anyone acting in the capacity of the PFCO shall have the full powers of the PFCO, except for the power of executive order.
    1. The same procedure shall be used to determine the person who shall become PFCO in the event of the resignation or removal of the PFCO. Persons in line to become PFCO may opt to decline the position, in which case the next available and willing person shall become PFCO.
  7. The PFCO shall have the responsibility of calling a vote on a matter within the PFA, once he or she has determined that sufficient discussion has taken place on the subject in question.

Article IV - Pegasus Fleet Admiralty

Section 1 - Membership

  1. The Pegasus Fleet Commanding Officer (PFCO) shall be the chair of the Pegasus Fleet Admiralty and will have full voting rights.
  2. The Pegasus Fleet Executive Officer (PFXO) shall be the vice-chair of the Pegasus Fleet Admiralty and will have full voting rights.
  3. Each commanding officer of a Task Force established by by-law shall be a member of the Pegasus Fleet Admiralty and will have full voting rights.
  4. When the position of Director of Fleet Operations is in effect, he or she shall be a member of the Pegasus Fleet Admiralty and will have full voting rights.
  5. The Pegasus Fleet Academy Commandant shall be a member of the Pegasus Fleet Admiralty and will have full voting rights.
  6. The Director of Personnel Management shall be a member of the Pegasus Fleet Admiralty and will have full voting rights.
  7. The Director of Fleet Recruitment shall be a member of the Pegasus Fleet Admiralty and will have full voting rights.
  8. The Director of Research & Development shall be a member of the Pegasus Fleet Admiralty and will have full voting rights.
  9. The Pegasus Fleet Judge Advocate General shall be a member of the Pegasus Fleet Admiralty and will have full voting rights.
  10. Membership on the PFA does not automatically grant the member any moderator/administrator powers on the PF Forums, PF wiki or elsewhere in the fleet unless it is required or were it is applicable.

Section 2 - Powers

  1. The PFA shall have the sole authority to permanently pass and amend the by-laws and amend the constitution of Pegasus Fleet.
  2. All matters before the PFA will be decided by a simple majority (>50%) vote, except as defined elsewhere in this constitution or by by-law.
    1. When calling a vote, the PFCO may state that the vote is mandatory for all PFA members not on a Leave of Absence.
  3. The PFA shall determine what constitutes PF canon.
  4. The PFA shall have the power to remove any of its members from office.
    1. The removal of the PFCO shall be determined by an 80% majority vote of the rest of the PFA.
    2. The removal of any other member of the PFA shall be determined by a 66% majority vote of the rest of the PFA.
    3. Any vote to remove a member of the PFA shall be deemed to be null and void if the PFA member affected is on an authorised LOA.
  5. The PFA may delegate any of its powers to a sub-committee by by-law.
  6. A PFA member does not cast a ballot in any vote directly involving themselves (such as position appointments).

Article V – Judge Advocate General

  1. The Pegasus Fleet Judge Advocate General (JAG) is an out-of-character body designed to ensure fair, impartial, and equitable discharge of Pegasus Fleet's rules and regulations.
  2. The chair of the JAG (JAG CO) is appointed by the Pegasus Fleet Admiralty (PFA) and removed by the PFA in the same manner as PFA members, except as set out in sub-section 27. He or she will not hold any other office that entitles them to a seat on the Pegasus Fleet Admiralty.
  3. JAG staff may be supplemented by appointing assistants. These positions are appointed by the JAG CO with the approval of the Pegasus Fleet Admiralty.
  4. The JAG will be checked by a permanent Appeals Panel of three Pegasus Fleet members with more than three months of consecutive service, appointed by the Pegasus fleet Admiralty.
    1. The members of the appeal panel will meet the following requirements: one will be a member of the Pegasus Fleet Admiralty, one will be a commanding officer that is not a member of the Pegasus Fleet Admiralty, and one will be neither a member of the Pegasus Fleet Admiralty, nor a commanding officer.
      1. The appeals panel members are appointed on a voluntary basis. Members of the fleet from each of the three different categories will be asked to place their name on a list of candidates for the appeal panel. When a new Appeals Panel member is required, the JAG CO will select a name at random from the list.
      2. Every member of the Pegasus Fleet Admiralty, excluding the JAG CO, are automatically volunteered for the Appeals Panel.
    2. The members of the Appeals Panel will serve terms of up to six months, with the length of their terms being specified upon their appointment. Their terms will be renewable.
      1. The length of the terms of Appeals Panel members will be set in such a way that there will be at least one month between the expiry of each member's term.
  5. Juries will be appointed as required by the constitution. Three jurors and two alternates will be drawn from a list of any and all members of Pegasus Fleet who have been members for three consecutive months who ask to be on the list in the following manner:
    1. The JAG CO will randomly select three names from the list. Should any of these individuals fail to respond within 24 hours, be unwilling to serve, or are in a conflict of interest, the JAG CO will select one additional name at random and continue doing so until three jurors have been selected.
    2. After three jurors have been selected, the JAG CO will select an additional two names from the list to serve as alternate jurors, using the same procedure as outlined above.
    3. The terms of the jurors and alternate jurors will end upon the close of the tribunal for which they have been selected.
    4. Should a juror become inactive or resign from his or her position before the natural end of his or her term, the first available alternate juror will succeed him or her as a juror.
  6. The JAG CO and Task Force Commanding Officers will undertake all reasonable efforts to ensure that members know that the list set out in sub-section 5 exists and of their right, if applicable, to place their names on said list.
  7. The procedures for the Judicial process of Pegasus Fleet shall be defined in a Uniform Code of Military Justice.
  8. The JAG CO will keep a full record of all complaints, and any applicable information relating to the complaints, including but not limited to: when and by whom they were made, whether charges were recommended as a result, whether charges were filed, whether a tribunal proceeded, the specifics of the tribunal, the ruling of the tribunal, the sentence, and any appeal process.
  9. The database will not be on a personal computer, but will be on a network that can be accessed at the end of the JAG CO's term and during his or her absence.
  10. Information from the database relating to tribunals that have concluded with a guilty result will be posted on a public website. The full database (containing information from all cases) will be accessible by the JAG standing officers and the Pegasus fleet Commanding Officer only.

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. All voting procedures will be set to take one week from when they are announced to those who may vote, unless all votes are received before the week has expired. All votes are put up and officiated by the JAG.

Section 1- the Constitution

The Constitution has primacy over all other documents, and is the document through which all other laws of the fleet are empowered.

  1. Any part of the constitution, unless otherwise specified below, may be amended by a 66% majority of each vote of the entire PFA and those COs who vote.
  2. Articles I and VI can only be amended if the PFA votes are all in favor.
  3. Pegasus Fleet CO's must be given the opportunity to vote.
  4. Constitutional Amendments may be put up for discussion by any PFA member.
  5. All CO votes must be cast on the CO Mailing List after the vote has been announced there. PFA Members should not vote on this list.
  6. All PFA votes must be cast on the PFA Mailing List after the vote has been announced there.

Section 2- Policies

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

  1. The Judicial Code of Practice shall be considered a Policy, and shall be considered to have Primacy over all other policies.
  2. Where two or more Policies contradict each other, the Policy which was first established shall have primacy over the other, unless the newer policy is meant as a replacement to the earlier one.
  3. Policies may be put up for discussion by any member of the PFA.
  4. Policies are adopted by a simple majority (>50%) vote of the COs and PFA who vote.
  5. All votes must be cast on the CO Mailing List after the vote has been announced there.

Section 3- By-Laws

By-Laws shall be created by the PFA 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 put up for discussion by any member of the PFA
  3. By-laws are adopted, revoked, or altered by a simple majority vote of the PFA.
  4. All votes must be cast over the PFA List after the vote has been called for there.

Section 4- Standing Orders

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

  1. Standing Orders are developed, maintained, and put up for discussion by the PFA 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 of the PFA.
  5. All votes must be cast over the PFA List after the JAG has called for a vote.

Section 5 – Executive Orders

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

  1. The PFCO 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 immediately to the PFA for consideration as a permanent change.
  3. All executive orders shall expire under whichever of the following conditions comes first:
    1. The Executive Order is passed or failed under the appropriate guideline for the type of law that the order falls under.
    2. The PFCO revokes the Executive Order
    3. After 90 days have elapsed.
  4. Should a matter be dealt with by Executive Order and later be rejected by a vote, such a matter cannot be dealt with again by Executive Order.
  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.