Federation Space Constitution

From Federation Space - Official Wiki
Jump to: navigation, search

The Federation Space Constitution serves as the rulebook for the site. By being a member, you agree to abide by terms outlined below.

NOTE: Any rules or guidelines posted in RED ALERT on the Federation Space forum supercede whatever is posted here. If you have a question as to a rules interpretation, please contact your FO, CO, FC, or the CinC, VP or President.

Contents

1. SECTION 1 - Federation Space RPG

1.1. Federation Space RPG is a play-by-forum Star Trek roleplaying game set 40+ years after the events of Star Trek: The Next Generation, Star Trek: Deep Space Nine, and Star Trek: Voyager.

1.2. Site members assume the role of Star Fleet officers through the use of expository fiction.

1.3. Goal: To bring together a diverse community of writers and roleplayers with a common interest in Star Trek, friendship, mutual respect, and writing.

1.4. All applicants to the site must demonstrate knowledge of basic writing techniques. Every attempt will be made to accommodate writers whose first language is not English.

1.5. The provisions of this document cover all mediums of communication between members including, but not limited to: forum posts, email, instant messaging, verbal communications, and chat.

1.6. By being a member of Federation Space, you agree to abide by all items in this document.

2. SECTION 2 – Roles and Responsibilities

2.1. All Members

2.1.1. Must be 13 years of age or older to join the site.

2.1.2. Treats all members of the site with respect and courtesy.

2.1.3. Respects the chain of command.

2.1.4. Posts at least two times a week. Posts must be story-oriented and move along the ship's mission or an approved subplot. Out-of-character (OOC) posts do not count towards this total.

2.1.5. Notifies Commanding Officer (CO) for planned absences of more than one week.

2.1.6. Does not post from another member's account.

2.1.7. Plays only one rated character (Primary Rated Character) unless approved for a Second Rated Character (SRC).

2.2. Cadets

2.2.1. Considered to be a member-in-training.

2.2.2. Reports to: Bio Evaluator and Academy Instructor (AI).

2.2.3. Posts in their assigned training holodecks minimum two times per week.

2.2.3.1. Posts will be relevant to the lesson being conducted or in response to a post by a member of the administrative staff.

2.2.3.2. Out-of-character (OOC) posts or social posts do not count towards this minimum.

2.2.4. Posts only in the Academy Auditorium, assigned holodeck, and the Lounge/Cafeteria/Gardens threads.

2.2.4.1. Posts to another Cadet’s holodeck are prohibited.

2.2.4.2. May post in the Lounge/Cafeteria/Gardens thread only if they are up to date on their training. There should not be a Bio Evaluator or AI post in their assigned holodeck waiting for reply.

2.2.5. Works with Bio Evaluator to bring character bio up to site standards.

2.2.6. Trains under an AI to learn the formatting, roleplaying, and rules of Federation Space.

2.3. Probationary Members

2.3.1. Prerequisite: Graduation from the Academy.

2.3.2. Reports to: Department Head (DH).

2.3.3. Players are considered probationary members while they hold the rank of Midshipman.

2.3.4. Returning Players (section 3.16) who return at a rank other than Midshipman are considered probationary members for three full points cycles.

2.3.5. Can be ordered back to the Academy for demonstrating a lack of understanding of the game and mechanics, or for gross rules violations.

2.3.6. Actively learns and demonstrates how to be a contributing member of a ship.

2.3.7. Demonstrates understanding of site policies and procedures.

2.4. Junior officers

2.4.1. Prerequisites:

2.4.1.1. Rank of Ensign or higher.

2.4.1.2. Complete of Probationary Member period.

2.4.2. Reports to: Department Head (DH).

2.4.3. Actively contributes to mission plot or posts in a subplot during shore leave.

2.5. Mission Authors

2.5.1. Prerequisites:

2.5.1.1. Rank of Lieutenant Junior Grade or higher.

2.5.1.2. Minimum six months as a Game Moderator (GM) an asset.

2.5.1.3. Approval of their Commanding Officer (CO).

2.5.2. Considered a Creative role.

2.5.3. Reports to: Creative Director (CD).

2.5.4. Works as mission writer.

2.5.4.1. Works with CD to develop story ideas.

2.5.4.2. Writes outline points for assigned missions.

2.5.5. Receives up to 100 points per mission assignment, when mission is launched by a ship.

2.6. Content Editors

2.6.1. Prerequisites:

2.6.1.1. Rank of Ensign or higher.

2.6.1.2. Considered a Content role.

2.6.1.3. Approval of their Commanding Officer (CO).

2.6.2. Reports to: Content Manager (CM).

2.6.3. Works as a wiki content writer for their assigned area.

2.6.3.1. Works with Division Commander and CM to develop and write new wiki content.

2.6.3.2. Edits and maintains assigned content pages.

2.6.4. Receives up to 300 points per month for executing the duties of this position.

2.7. Department Head (DH)

2.7.1. Prerequisite: Rank of Lieutenant Junior Grade or higher.

2.7.2. Reports to: First Officer (FO).

2.7.3. Considered the first link in a Junior Officer or Probationary Member’s chain of command.

2.7.4. Serves as a role model for all Junior Officers and Probationary Members.

2.7.5. Works as mentor to Junior Officers and Probationary Members in their department.

2.7.6. Ensures Junior Officers and Probationary Members in their department are posting.

2.7.6.1. Works with the FO to ensure all department members are involved in the mission, whether through the main plot or an approved subplot.

2.7.6.2. Follows up with department members not on approved leave of absence (LOA) that have not posted in two weeks. 2.7.6.3. Notifies FO regarding absent players in their department.

2.7.7. Advises First Officer on any issues concerning their department.

2.7.8. Provides participation points for department members to the FO by the 18th of the month.

2.7.9. Receives up to 100 points each month for executing the duties of this position.

2.8. Academy Instructor (AI)

2.8.1. Prerequisites:

2.8.1.1. Rank of Lieutenant Junior Grade or higher.

2.8.1.2. Approval of their Commanding Officer (CO).

2.8.2. Considered an Academy role.

2.8.3. Reports to: Dean of Admissions (DoA).

2.8.4. Considered the first link in a Cadet’s chain of command.

2.8.5. Serves as instructor for Cadets.

2.8.5.1. Teaches Cadets game mechanics, including post formatting, roleplaying, how to work with a Game Moderator (GM), chain of command, and other mechanics as outlined in the Graduation Checklist.

2.8.5.2. Acts as GM, taking Cadets through a short scenario so they can experience game mechanics.

2.8.5.3. Assesses Cadet skills and abilities, taking the time needed to ensure Cadet’s understanding of the required topics.

2.8.6. Serves as role model to Cadets:

2.8.6.1. Posts every three days while working with a Cadet.

2.8.7. Receives up to 300 points each month for executing the duties of this position.

2.9. Bio Evaluator

2.9.1. Prerequisites:

2.9.1.1. Minimum one year experience as an Academy Instructor (AI).

2.9.1.2. Approval of Dean of Evaluations (DoE).

2.9.2. Considered an Academy role.

2.9.3. Reports to: Dean of Evaluations.

2.9.4. Considered the first link in a Cadet’s chain of command.

2.9.5. Reviews Cadet’s character bio for:

2.9.5.1. Completion.

2.9.5.2. Technical requirements, including grammar, spelling, and formatting.

2.9.5.3. Suitability as a character.

2.9.5.4. Alignment with site history and canon.

2.9.6. Serves as role model to Cadets.

2.9.6.1. Posts every three days while working with a Cadet.

2.9.7. Receives up to 300 points each month for executing the duties of this position (to a maximum total of 300 points earned for all Academy responsibilities).

2.10. First Officer (FO)

2.10.1. Prerequisites:

2.10.1.1. Minimum rank of Lieutenant or higher.

2.10.1.1.1. Rank of Lieutenant Commander required for CA, CS, or GSC class ships.

2.10.1.1.2. Rank of Commander required for BB or CV class ships.

2.10.1.2. Minimum six months experience as a Department Head (DH).

2.10.1.3. Successful completion of Command Certification.

2.10.2. Reports to: Commanding Officer (CO).

2.10.3. Considered the second link in a member’s chain of command.

2.10.4. Serves as a role model for DHs, Junior Officers, and Probationary Members.

2.10.5. Works as mentor to DHs on assigned starship, laying the groundwork for DHs to become the next generation of FOs.

2.10.6. Ensures DHs, Junior Officers, and Probationary Members are posting.

2.10.6.1. Greets new players and works diligently to get them involved in the mission as soon as possible, at the CO’s discretion.

2.10.6.2. Works with DHs and CO to ensure all ship’s crew are involved in the mission, whether through the main plot or an approved subplot.

2.10.6.3. Follows up with ship crew not on approved leave of absence (LOA) that have not posted in four weeks.

2.10.6.4. Advises CO on any issues concerning ship’s crew.

2.10.7. Ensures DHs are performing their duties per section 2.7.

2.10.8. Acts as advisor to CO.

2.10.9. Assumes command during CO’s absence.

2.10.9.1. In the event of an unplanned CO absence, on day five of waiting, the FO may push the mission along as necessary. This includes hijacking the CO as needed.

2.10.10. Provides participation points for ship’s crew to the CO by the 21st of the month.

2.10.11. Receives up to 200 points each month for executing the duties of this position.

2.11. Game Moderator (GM)

2.11.1. Prerequisites:

2.11.1.1. Rank of Lieutenant Junior Grade or higher.

2.11.1.2. A history of running well-defined subplots.

2.11.1.3. Approval of their Commanding Officer (CO).

2.11.2. Considered a Creative role.

2.11.3. Reports to: Creative Director (CD).

2.11.4. Works with assigned CO to coordinate the mission.

2.11.4.1. Reviews mission outline at start of mission and submits any changes to CO and CD.

2.11.4.2. Ensures main mission plot moves forward in a timely manner.

2.11.4.3. Responds to GM input requests within three days.

2.11.4.4. If ship’s rated characters are not involved in main mission plot, works with CO to develop mission plot hooks and subplots.

2.11.5. Is not permitted to GM a ship on which they have a rated character.

2.11.6. Receives up to 300 points each month for executing the duties of this position.

2.12. Division Commanders

2.12.1. Prerequisites:

2.12.1.1. Rank of Lieutenant Junior Grade or higher.

2.12.1.2. Minimum six months experience as Content Editor.

2.12.1.3. Approval of their Commanding Officer (CO).

2.12.2. Reports to: Content Manager (CM).

2.12.3. Serves as content expert for their assigned division.

2.12.3.1. Works with CM, Creative Director (CD), and President (Pres) to determine advancements in their division.

2.12.3.2. Answers any questions related to their division.

2.12.3.3. Works with Content Editors to develop new content for their division.

2.12.3.4. Monitors and approves all updates to content in their division.

2.12.4. Receives up to 300 points each month for executing the duties of this position.

2.13. Blog Editor

2.13.1. Prerequisites:

2.13.1.1. Rank of Lieutenant Junior Grade or higher.

2.13.1.2. Considered an Academy role.

2.13.1.3. Approval of their Commanding Officer (CO).

2.13.2. Reports to: Academy Superintendent (Supt).

2.13.3. Acts as administrative head of the blog.

2.13.3.1. Recruits members to write content for the blog.

2.13.3.2. Mentors any blog writers.

2.13.3.3. Posts monthly points chart to the Commanding Officer section by the 18th of the month.

2.13.3.4. Creates and manages blog user accounts.

2.13.3.5. Works with Systems Administrator on maintaining the blog tool.

2.13.4. Acts as content developer for the blog.

2.13.4.1. Works with Supt and President (Pres) to develop and write new blog content.

2.13.4.2. Edits and maintains assigned content.

2.13.4.3. Assigns content tasks to blog editors.

2.13.5. Receives up to 300 points each month for executing the duties of this position.

2.14. Junior Leadership

2.14.1. Includes Commanding Officers, Dean of Evaluations, and Dean of Admissions.

2.15. Commanding Officer (CO)

2.15.1. Prerequisites:

2.15.1.1. Minimum out-of-game rank of Lieutenant Commander or higher.

2.15.1.1.1. Rank of Lieutenant Commander for ES, FF, FSC class ships.

2.15.1.1.2. Rank of Commander for DD, CL class ships.

2.15.1.1.3. Rank of Captain for CA, CS, GSC, BB, CV class ships.

2.15.1.2. Minimum six months experience as a First Officer (FO).

2.15.1.3. Minimum six months experience as Game Moderator (GM).

2.15.2. Reports to: Fleet Commander (FC).

2.15.3. Considered a Junior Leadership position.

2.15.4. Acts as administrative head of their assigned starship.

2.15.4.1. Considered the third link in a member’s chain of command.

2.15.4.2. Acts as disciplinary head for their starship.

2.15.4.3. Ensures FO is performing their duties per section 2.10.

2.15.4.4. Appoints Department Heads (DHs) and selects FO candidates.

2.15.4.5. Ensures all ship’s crew are posting.

2.15.4.5.1. Works with FO and GM to ensure all ship’s crew are involved in the mission, whether through the main plot or an approved subplot.

2.15.4.5.2. Follows up with ship crew not on approved leave of absence (LOA) that have not posted in six weeks.

2.15.4.5.3. Advises FC on any issues concerning ship’s crew.

2.15.4.6. Responsible for ensuring their ship’s roster on the Active Personnel (AP) sheet is up to date, including personnel and mission status. Notifies FC of any required changes within seven days.

2.15.4.7. Responsible for keeping assigned starship’s wiki homepage up to date, including crew roster, character bios, and mission logs. This may be delegated, but the CO is the responsible party.

2.15.4.7.1. All Crew and Captain’s Logs must be uploaded to the wiki before a new mission is assigned.

2.15.4.7.2. Must send a copy of final mission log to Content Manager (CM), so that mission can be integrated into other aspects of the wiki.

2.15.5. Acts as creative head of assigned starship.

2.15.5.1. Works with FC and Creative Director (CD) on mission development. CD serves as final mission approval authority.

2.15.5.2. Coordinates plot development with assigned GMs.

2.15.5.3. Ensures main plot moves forward.

2.15.5.4. Acts as GM as needed.

2.15.5.5. Regularly posts Captain's Logs as mission progresses.

2.15.6. Serves as a role model for ship’s crew.

2.15.7. Works as mentor to their FO, laying the groundwork for FOs to become the next generation of CO.

2.15.8. Provides monthly points chart including participation, Roleplayer of the Month, and medal recommendations for ship’s crew to the FC by the 24th of the month.

2.15.9. Receives up to 300 points each month for executing the duties of this position.

2.16. Dean of Evaluations (DoE)

2.16.1. Prerequisites:

2.16.1.1. Minimum one year experience as an Academy Instructor (AI).

2.16.1.2. Experience as a Bio Evaluator.

2.16.2. Considered an Academy role.

2.16.3. Reports to: Academy Superintendent (Supt).

2.16.4. Considered the second link in a Cadet’s chain of command.

2.16.5. Considered first link in a Bio Evaluator’s chain of command.

2.16.6. Manages Bio Evaluators.

2.16.6.1. Coordinates training of Bio Evaluators.

2.16.6.2. Assigns Bio Evaluators to available holodecks.

2.16.6.3. Ensures Bio Evaluators are performing their duties per section 2.9.

2.16.6.4. Works as mentor to Bio Evaluators.

2.16.6.5. Follows up with Bio Evaluators not on approved leave of absence (LOA) who have not taken part in Academy duties in four weeks.

2.16.7. Serves as Academy expert regarding bios.

2.16.7.1. Reviews all Cadet bios to confirm suitability as a character.

2.16.7.2. Stays up to date on site history and canon.

2.16.8. Acts as advisor to Supt.

2.16.9. Serves as backup for Dean of Admissions (DoA) and Supt in their absence.

2.16.10. Receives up to 300 points each month for executing the duties of this position (to a maximum total of 300 points earned for Academy responsibilities).

2.17. Dean of Admissions

2.17.1. Prerequisites:

2.17.1.1. Minimum one year experience as an Academy Instructor (AI).

2.17.2. Considered an Academy role.

2.17.3. Reports to: Academy Superintendent (Supt).

2.17.4. Considered the second link in a Cadet’s chain of command.

2.17.5. Considered first link in an AI’s chain of command.

2.17.6. Serves as the first point of contact for new members joining the site.

2.17.6.1. Responds to membership applications.

2.17.6.2. Determines department assignments.

2.17.6.3. Submits account creation request for new players.

2.17.6.4. Gets new players set up with a holodeck.

2.17.7. Manages AI.

2.17.7.1. Coordinates training of new instructors.

2.17.7.2. Assigns AIs to available holodecks.

2.17.7.3. Ensures AIs are performing their duties per section 2.8.

2.17.7.4. Works as mentor to AIs.

2.17.7.5. Follows up with AIs not on approved leave of absence (LOA) who have not taken part in Academy duties in four weeks.

2.17.8. Acts as advisor to Supt.

2.17.9. Serves as backup for Dean of Evaluations (DoE) and Supt in their absence.

2.17.10. Receives up to 300 points each month for executing the duties of this position (to a maximum total of 300 points earned for Academy responsibilities).

2.18. Senior Leadership

2.18.1. Includes Fleet Commanders, Personnel Director, Creative Director, and Systems Administrator.

2.19. Fleet Commander (FC)

2.19.1. Prerequisites:

2.19.1.1. Minimum out-of-game rank of Lieutenant or higher, Lieutenant Commander preferred.

2.19.1.2. Minimum one year experience as a Commanding Officer (CO).

2.19.1.2.1. Members may not hold Site Administration position while serving as FC.

2.19.1.3. Members may not serve as FC for the Fleet in which they have a rated character (PRC or SRC).

2.19.2. Reports to: Commander in Chief (CinC).

2.19.3. Considered a Personnel role and a Senior Leadership position.

2.19.4. Acts as administrative and creative head of their assigned Fleet.

2.19.4.1. Considered the fourth link in a member’s chain of command.

2.19.4.2. Welcomes new Academy graduates to their Fleet.

2.19.4.3. Adjudicates disciplinary issues within their assigned Fleet per section 3.19.

2.19.4.4. Ensures Fleet COs are performing their duties per section 2.15.

2.19.4.5. Approves and coordinates transfer requests within their Fleet, and approves inter-Fleet transfer requests.

2.19.4.6. Ensures their Fleet roster on the Active Personnel (AP) sheet is up to date. This includes adding new players, updating player promotions and transfers, and following up with COs regarding leaves of absence (LOAs) that are past the return date and AWOLs that are more than a month past the AWOL date. Updates are made within three days of required change.

2.19.5. Manages forum accounts and ship threads in their Fleet:

2.19.5.1. Updates forum account settings for Academy Graduates.

2.19.5.2. Deletes and creates ship threads at the end of each ship mission.

2.19.6. Works with CinC, Vice President (VP), Creative Director (CD), and Fleet COs regarding creative direction of their Fleet.

2.19.7. Works as mentor to COs within their Fleet.

2.19.8. Audits their Fleet’s monthly points charts for completeness and accuracy. Submits charts to CinC by the 27th of the month.

2.19.8.1. Approves and awards medals within their assigned Fleet as necessary.

2.19.9. Receives up to 300 points each month for executing the duties of this position.

2.20. Personnel Director (PD)

2.20.1. Prerequisite: 2.20.1.1. Minimum out-of-game rank of Lieutenant or higher, Lieutenant Commander preferred. 2.20.2. Reports to: Commander in Chief (CinC). 2.20.3. Considered a Personnel role and a Senior Leadership position. 2.20.4. Manages Personnel forum accounts: 2.20.4.1. Creates forum accounts for Secondary Rated Characters (SRCs), registered Non-Rated Characters (NRCs), and new Primary Rated Characters (PRCs). 2.20.4.2. Updates forum account settings for Academy graduates. 2.20.4.3. Deletes PRC, SRC, and NRC accounts that are no longer in use. 2.20.5. Monitors character updates: 2.20.5.1. Ensures Active Personnel (AP) sheet stays up to date by following up with FCs if sheet is past due for updating. 2.20.5.2. Ensures starship wiki rosters are updated and match the AP sheet. Contacts FCs if rosters are out of date. 2.20.6. Receives up to 300 points each month for executing the duties of this position.

2.21. Creative Director (CD)

2.21.1. Prerequisites: 2.21.1.1. Minimum out-of-game rank of Lieutenant or higher, Lieutenant Commander preferred. 2.21.1.2. Minimum one year experience as a Game Moderator (GM). 2.21.2. Considered a Creative role and a Senior Leadership position. 2.21.3. Reports to: Vice President (VP). 2.21.4. Manages the Creative team. 2.21.4.1. Considered the first link in the Creative chain of command. 2.21.4.2. Ensures Creative team are performing their duties. 2.21.4.3. Mentors GMs and Mission Authors. 2.21.4.4. Appoints/relieves all Creative personnel. 2.21.4.5. Assigns GMs to starships. Removes or reassigns GMs as needed. 2.21.4.6. Works with Commanding Officers (COs), Fleet Commanders (FCs), and the CinC regarding GM personnel issues. 2.21.5. Coordinates creative direction of the site. 2.21.5.1. Develops and manages major site story arcs. 2.21.5.2. Works with COs on mission development. 2.21.5.3. Acts as approval authority on all missions. 2.21.6. Serves as a content expert regarding site history and canon. 2.21.6.1. Works with Academy team and Division Heads on any bio exceptions regarding race, technology, etc. 2.21.7. Posts monthly points chart to the Commanding Officer section by the 18th of the month. 2.21.8. Receives up to 300 points each month for executing the duties of this position.

2.22. Systems Administrator

2.22.1. Prerequisites: 2.22.1.1. Real world experience as a systems administrator with compatible or comparable technologies to those in use by Federation Space RPG. 2.22.1.2. Must be a member in good standing for at least three years. 2.22.2. Reports to the President (Pres). 2.22.3. Manages the site servers. 2.22.4. Responsible for: 2.22.4.1. Security. 2.22.4.2. Updates. 2.22.4.3. Message board software. 2.22.4.4. Main site (news) software. 2.22.5. Works with Content Manager (CM) to maintain wiki software. 2.22.6. Earns up to 300 points per month for executing the duties of this position.

2.23. Site Administration

2.23.1. Includes President, Commander in Chief, 2.23.2. Establishes policies and procedures for Federation Space. 2.23.3. Acts as the de-facto Board of Directors of the Fed-Space Association, LLC entity. 2.23.4. In the event of a 14-day or more absence (planned or otherwise) of any Site Administration members, the remaining Site Administration may, if mutually agreed, take necessary actions to ensure site continuity and operation.

2.24. Commander in Chief (CinC)

2.24.1. Prerequisites: 2.24.1.1. Minimum out-of-game rank of Commander or higher. 2.24.1.2. Minimum one year experience as a Fleet Commander (FC). 2.24.1.3. Must be a member in good standing for at least 3 (three) years. 2.24.2. Serves as a member of the Site Administration team. 2.24.3. Acts as administrative head of Personnel. 2.24.3.1. Considered the fifth link in a member’s chain of command. 2.24.3.2. Adjudicates personnel disciplinary issues per section 3.19. 2.24.3.3. Ensures FCs are performing their duties per section 2.19. 2.24.3.4. Acts as final approval authority on transfer requests. 2.24.4. Works with President, Vice President (VP), Creative Director (CD), FCs, and Commanding Officers (COs) regarding creative direction of site. 2.24.5. Works as mentor to FCs. 2.24.6. Audits monthly points charts for completeness and accuracy. 2.24.6.1. Posts charts to Red Alert thread by 1st of the month. 2.24.6.2. Approves and awards medals as necessary.

2.25. Vice President (VP)

2.25.1. Prerequisites: 2.25.1.1. Minimum out-of-game rank of Commander or higher. 2.25.1.2. Minimum one year experience as Creative Director (CD). 2.25.1.3. Must be a member in good standing for at least three years. 2.25.2. Serves as member of the Site Administration team. 2.25.3. Acts as administrative head of the Creative team. 2.25.3.1. Considered second link in the Creative chain of command. 2.25.3.2. Ensures Creative personnel are performing their duties. 2.25.3.3. Mentors CD. 2.25.3.4. Appoints/relieves CD. 2.25.4. Responsible for creative direction of the site. 2.25.4.1. Works with President (Pres) and CD on overall creative direction. 2.25.4.2. Works with CD on all major plot decisions. 2.25.4.3. Acts as approval authority on all sitewide plot plans. 2.25.5. Serves as site expert regarding site history and canon.

2.26. Content Manager (CM)

2.26.1. Prerequisites: 2.26.1.1. Minimum out-of-game rank of Commander or higher. 2.26.1.2. Minimum one year experience as Division Commander. 2.26.1.3. Must have proven knowledge of wiki, webpage creation, and website management. 2.26.1.4. Must be a member in good standing for at least three years. 2.26.2. Serves as a member of the Site Administration team. 2.26.3. Acts as administrative head of the Content team. 2.26.3.1. Considered the first link in the Content chain of command. 2.26.3.2. Ensures Content personnel are performing their duties. 2.26.3.3. Mentors Content personnel. 2.26.3.4. Appoints/relieves all Content personnel. 2.26.4. Serves as site expert regarding wiki and content. 2.26.4.1. Works with Creative Director (CD) and Vice President (VP) to develop new content and canon. 2.26.5. Manages wiki: 2.26.5.1. Creates and manages wiki user accounts. 2.26.5.2. Responsible for organization of wiki content. 2.26.5.3. Responsible for wiki software and regular software updates. 2.26.5.4. Responsible for all wiki functionality and templates. 2.26.6. Posts monthly points chart to the Commanding Officer section by the 18th of each month.

2.27. Superintendent (Supt)

2.27.1. Prerequisites: 2.27.1.1. Minimum out-of-game rank of Commander or higher. 2.27.1.2. Minimum one year experience as Dean of Admissions (DoA) or Dean of Evaluations (DoE). Experience as both an asset. 2.27.1.3. Must be a member in good standing for at least three years. 2.27.2. Serves as a member of the Site Administration team. 2.27.3. Acts as administrative head of the Academy. 2.27.3.1. Considered the third link in the Academy chain of command. 2.27.3.2. Ensures Academy personnel are performing their duties. 2.27.3.3. Mentors DoA and DoE. 2.27.3.4. Follows up with Academy Instructors (AIs) and Bio Evaluators not on approved leave of absence (LOA) who have not taken part in Academy duties in eight weeks. 2.27.3.5. Adjudicates personnel disciplinary issues per section 3.19. 2.27.3.6. Appoints/relieves all Academy personnel. 2.27.3.7. Follows up with Cadets not on approved LOA who have not posted in two weeks. 2.27.3.8. Evaluates Cadet’s suitability to join the site. 2.27.3.9. Assigns graduates to starships. 2.27.4. Serves as site expert regarding training and bio development. 2.27.4.1. Develops a curriculum for cadets that includes: site policies and procedures, game mechanics, bio development, and creative development. 2.27.4.2. Stays up to date on Federation Space history and canon. 2.27.4.3. Works with Creative team and Division Heads on any bio exceptions regarding race, technology, etc. 2.27.5. Manages Academy forum accounts and threads: 2.27.5.1. Creates forum accounts for cadets and instructors. 2.27.5.2. Updates forum account settings for Academy graduates. 2.27.5.3. Deletes Academy and Cadet accounts that are no longer in use. 2.27.5.4. Creates and deletes Academy Campus and Academy Instructor area threads. 2.27.6. Posts monthly points chart to the Commanding Officer section by the 18th of the month.

2.28. President (Pres)

2.28.1. Serves as a member of the Site Administration team. 2.28.2. Acts as overall administrative head of Federation Space. 2.28.2.1. Acts as final approval/appeal authority on all site-wide decisions. 2.28.2.2. Ensures Site Administration are performing their duties. 2.28.2.3. Mentors Site Administration. 2.28.2.4. Appoints Commanding Officers (COs) at the advice of the Site Administration team. 2.28.3. Directs overall operations of Federation Space 2.28.3.1. Acts as domain, forum, and website administrator. 2.28.3.2. Retains legal and financial responsibility for the Fed-Space Association LLC, which owns the site and contents. 2.28.3.3. Serves as legal President and Treasurer of Fed-Space Association LLC. 2.28.4. Acts as overall creative head of Federation Space. 2.28.4.1. Works with the Vice President (VP) on the site’s creative direction.

3. SECTION 3 - Policies and Procedures

3.1. Appointment of Site Administration

3.1.1. Policies: 3.1.1.1. New Site Administration will be appointed when: 3.1.1.1.1. A current Site Administration position is vacated. 3.1.1.1.2. A new Site Administration position is created. 3.1.2. Procedures: 3.1.2.1. Site Administration and Senior Leadership may nominate potential candidates that meet the requirements as outlined in the Roles and Responsibilities section for that position. 3.1.2.2. The current Site Administration will review the potential candidate for: 3.1.2.2.1. Prerequisites for the position. 3.1.2.2.2. Contributions to the site. 3.1.2.2.3. Suitability for the position. 3.1.2.2.4. Ability to work productively with the existing Site Administration. 3.1.2.3. Once a candidate is determined, the member will be notified through email by the President (Pres). 3.1.2.4. Once the member accepts, they become the new Site Administration member.

3.2. Appointment of Senior Leadership

3.2.1. Policies: 3.2.1.1. New Senior Leadership will be appointed when: 3.2.1.1.1. A current Senior Leadership position is vacated. 3.2.1.1.2. A new Senior Leadership position is created. 3.2.2. Procedures: 3.2.2.1. Site Administration and Senior Leadership may nominate potential candidates that meet the requirements as outlined in the Roles and Responsibilities section for that position. 3.2.2.2. The Site Administrators will review the potential candidate for: 3.2.2.2.1. Prerequisites for the position. 3.2.2.2.2. Contributions to the site. 3.2.2.2.3. Suitability for the position. 3.2.2.3. Once a candidate is determined, the member will be notified through email by the Site Administrator responsible for this position. 3.2.2.4. Once the member accepts, they become the new Senior Leadership member.

3.3. Appointment of Junior Leadership

3.3.1. Policies: 3.3.1.1. New Junior Leadership will be appointed when: 3.3.1.1.1. A current Junior Leadership position is vacated. 3.3.1.1.2. A new Junior Leadership position is created. 3.3.2. Procedures: 3.3.2.1. Site Administration, Senior Leadership, and Commanding Officers (COs) may nominate potential candidates that meet the requirements as outlined in the Roles and Responsibilities section for that position. 3.3.2.2. The Senior Leadership personnel responsible for hiring this position will review the potential candidate for: 3.3.2.2.1. Prerequisites for the position. 3.3.2.2.2. Contributions to the site. 3.3.2.2.3. Suitability for the position. 3.3.2.3. Once a candidate is determined, the member will be notified through email by the Senior Leadership member responsible for this position. 3.3.2.4. Once the member accepts, they become the new Junior Leadership member.

3.4. Appointment of Commanding Officers

3.4.1. Policies: 3.4.1.1. New Commanding Officers (COs) will be appointed when: 3.4.1.1.1. A current CO position is vacated. 3.4.1.1.2. A new CO position is created, based on the Fleet Expansion policies in section 3.18. 3.4.2. Procedures: 3.4.2.1. Site Administration, Fleet Commanders (FCs), and CO may nominate potential candidates that meet the requirements as outlined in section 2.15. 3.4.2.2. Site Administration and FCs will review the potential candidate for: 3.4.2.2.1. Prerequisites for the position. 3.4.2.2.2. Contributions to the site. 3.4.2.2.3. Suitability for the position. 3.4.2.3. Once a candidate is determined, the member will be notified through email by the President (Pres). 3.4.2.4. Once the member accepts, they become a CO-in-waiting. 3.4.2.5. The CO-in-waiting will officially become a Commanding Officer when they take command of their ship.

3.5. Appointment of First Officers

3.5.1. Policies: 3.5.1.1. New First Officers (FOs) will be appointed when: 3.5.1.1.1. A current FO position is vacated. 3.5.1.1.2. A new FO position is created, based on the Fleet Expansion policies in section 3.18. 3.5.2. Procedures: 3.5.2.1. Site Administration, Fleet Commanders (FCs), and Commanding Officers (COs) may nominate potential candidates that meet the requirements as outlined in section 2.10. 3.5.2.2. The FC and the CO will review the potential candidate for: 3.5.2.2.1. Prerequisites for the position. 3.5.2.2.2. Contributions to the site. 3.5.2.2.3. Suitability for the position. 3.5.2.2.4. Potential as a future CO. 3.5.2.3. The FC will submit the FO candidate to the Site Administration for review. 3.5.2.4. Once a candidate is approved, the CO will offer the position to the member. 3.5.2.5. Once the member accepts, they become FO. 3.5.2.6. The receiving CO will notify the losing CO of the player’s promotion and transfer, copying their respective FCs.

3.6. Appointment of Department Heads

3.6.1. Policies: 3.6.1.1. New Department Heads (DHs) will be appointed when: 3.6.1.1.1. A current DH position is vacated. 3.6.1.1.2. New DH positions are created, based on the Fleet Expansion policies in section 3.18. 3.6.2. Procedures: 3.6.2.1. Commanding Officers (COs) and First Officers (FOs) may nominate potential candidates that meet the requirements as outlined in section 2.7. 3.6.2.2. The CO and FO will review the potential candidate for: 3.6.2.2.1. Prerequisites for the position. 3.6.2.2.2. Contributions to the site. 3.6.2.2.3. Suitability for the position. 3.6.2.2.4. Potential as a future FO. 3.6.2.3. Once a candidate is determined, the CO will offer the position to the member. 3.6.2.4. Once the member accepts, they become DH. 3.6.2.5. If the member is on a different starship than the position, the receiving CO will notify the losing CO of the player’s promotion and transfer.

3.7. Points

3.7.1. Policies:

3.7.1.1. Points are awarded to Primary Rated Characters (PRCs) and Secondary Rated Characters (SRCs) based on their player’s site participation each month.

3.7.1.1.1. A month is defined as the 16th of the month to the 15th of the next.

3.7.1.2. Points can be earned through:

3.7.1.2.1. Participation. Up to 500 points are assigned based on active participation and post quality. This is at the discretion of the character’s Commanding Officer (CO).

3.7.1.2.2. Medals. Characters and players can earn points based on actions that are above and beyond the minimum participation requirements, both in-game and out-of-game. Any medals earned by a player will be awarded to the PRC (with the exception that medals earned by an SRC will go to the SRC). See Medals page for amount of points earned.

3.7.1.2.3. Additional roles. Members can earn points for active participation in additional site responsibilities. Any points earned through additional roles will be awarded to PRCs only, with the exception of an SRC Department Head. See Roles section above for amount of points earned.

3.7.1.3. Additional points will be prorated based on a player’s participation.

3.7.1.4. Character rank promotions may not be taken until a rank is achieved and posted to the Monthly Points section.

3.7.1.5. All characters must occupy each rank for one posting cycle before moving up to the next rank. No skipping ranks is permitted.

3.7.2. Procedures:

3.7.2.1. Starting the 16th of the month, a character’s senior officers will calculate the points earned by the character.

3.7.2.2. All points will be entered into a ship points chart by the character’s CO.

3.7.2.3. The completed ship points chart will be submitted up the chain of command to the Commander in Chief (CinC).

3.7.2.4. The CinC will post the ship points charts to the Monthly Points section by the 1st of the following month.

3.7.2.5. The character’s CO is responsible for working out any promotions due to the character.

3.7.2.6. The character’s CO is responsible for ensuring all bios and rosters are updated to reflect any rank changes and medals awarded.

3.8. Medals

3.8.1. Policies:

3.8.1.1. Medals are awarded to players and characters who go above and beyond the standard site expectations.

3.8.1.1.1. Character contribution: Medals may be awarded to characters who went above the call of duty or who made significant contributions to a ship’s mission. These medals are awarded to the Primary Rated Character (PRC) or Secodary Rated Character (SRC).

3.8.1.1.2. Player contribution: Medals may be awarded to players for extra effort during a mission or contributions to the site. These medals are awarded to the PRC.

3.8.1.1.3. Any medals awarded to a Secondary Rated Character (SRC) will be awarded to the SRC. Any other medal awarded to a member or character will go to the Primary Rated Character (PRC).

3.8.1.2. Certain medals are awarded by Commanding Officers (COs), while higher level medals are awarded by Fleet Commanders (FCs) and Site Administration on the recommendation of COs. A full list of medals can be seen here.

3.8.2. Procedures:

3.8.2.1. COs continually review the performance of their crew.

3.8.2.2. When a CO finds a member eligible for a medal, they will include the medal on the points chart for that month.

3.8.2.2.1. For higher medals, the CO will include a medal recommendation to the FCs with the points chart for that month.

3.8.2.3. The FC will review all awarded medals and medal recommendations.

3.8.2.4. The Commander in Chief (CinC) will post the medals to the Monthly Points section by the 1st of the following month.

3.8.2.5. The character’s CO is responsible for ensuring all bios are updated to reflect any medals awarded.

3.9. Rank Caps

3.9.1. Policies:

3.9.1.1. Rank caps are in place to ensure even distribution of ranks across the site membership.

3.9.1.2. Rank caps may be lifted with the approval of Site Administration.

3.9.2. Procedures:

3.9.2.1. Ensign

3.9.2.1.1. All characters are capped at Ensign until a character bio is completed and approved by the Academy.

3.9.2.2. Lieutenant

3.9.2.2.1. All Primary Rated Characters (PRCs) and Secondary Rated Characters (SRCs) are capped at Lieutenant until:

3.9.2.2.1.1. They are offered and accept a Department Head (DH) position.

3.9.2.2.1.2. They complete a Command Certification training scenario (see Section 3.10).

3.9.2.2.2. PRCs with the rank of Lieutenant may be First Officers (FOs) of an ES, FSC, FF, or DD class ship with approval of their Fleet Commander (FC).

3.9.2.3. Lieutenant Commander

3.9.2.3.1. All PRCs are capped at Lieutenant Commander (LCdr) until:

3.9.2.3.1.1. They are offered and accept an FO position.

3.9.2.3.1.2. They serve as a DH or an FO aboard a BB or CV class ship, with FC approval.

3.9.2.3.2. All SRCs are capped at Lieutenant Commander.

3.9.2.3.3. PRCs of this rank may serve as FO on ES, PFF, FF, FSC, DD, CL class starships.

3.9.2.3.4. PRCs of this rank may serve as Commanding Officer (CO) of an ES, FSC, FF, or PFF class ship with approval of their FC.

3.9.2.4. Commander

3.9.2.4.1. All PRCs are capped at Commander until:

3.9.2.4.1.1. They are offered and accept a CO position.

3.9.2.4.2. May serve as FO of any class ship.

3.9.2.4.3. May serve as CO of an ES, FSC, FF, PFF, or DD class ship.

3.9.2.5. Captain

3.9.2.5.1. All PRCs are capped at Captain until:

3.9.2.5.1.1. They have permission of Site Administration.

3.9.2.5.1.2. They are the CO of a BB or CV class ship.

3.9.2.5.2. May serve as CO of any class of ship.

3.9.2.5.3. May serve as FO of a BB or CV ship with a CO of rank Commodore or higher and with approval of Site Administration.

3.9.2.6. Commodore

3.9.2.6.1. All PRCs are capped at Commodore until:

3.9.2.6.1.1. They become a Site Administration member.

3.9.2.6.1.2. They command a flagship or heavy cruiser and they command a group of NPC starships as a battle group.

3.9.2.6.2. May command any ship larger than a CL.

3.10. Command Certification

3.10.1. Policies 3.10.1.1. Command Certification is a subplot run by a member with the approval of their Commanding Officer (CO). 3.10.1.2. The goals of the subplot are to: 3.10.1.2.1. Demonstrate that the member can lead a group of two to three other players through a story. 3.10.1.2.2. Demonstrate that the character can lead others. 3.10.1.2.3. Present command-level challenges (such as challenging their character's values or ethics, or how they deal with challenging situations) and demonstrate the character’s ability to work through them. 3.10.1.3. Players may run command certification at any time. The recommended time is once they reach the rank of Lieutenant. 3.10.1.4. Characters are capped at the rank of Lieutenant until Command Certification is complete. 3.10.2. Procedures 3.10.2.1. Player contacts their CO regarding running Commander Certification. 3.10.2.1.1. Players should include an outline of what the plot will be and who will be participating. 3.10.2.2. The CO creates a subplot thread for the player. 3.10.2.3. Once the plot is complete, the CO determines if the player was successful in meeting the goals of the Command Certification. 3.10.2.4. If successful, the character is now eligible for promotion to Lieutenant Commander. 3.10.2.5. If unsuccessful, the player may attempt Command Certification again. 3.11. Non-Rated Characters and Non-Player Characters 3.11.1. Definitions: 3.11.1.1. Non-Rated Characters (NRCs) are characters played by members that do not earn points. 3.11.1.1.1. Temporary NRCs are short-term characters, usually “redshirts”. They are noted by the use of out-of-character (OOC) marks at the top of a post (i.e. == Ens Boone - NRC == ). 3.11.1.1.2. Registered NRCs are long-term characters that have their own user accounts and character biographies. 3.11.1.2. Non-Player Characters (NPCs) are characters played by Game Moderators (GMs). 3.11.2. Policies: 3.11.2.1. All NRCs must be approved by the player’s Commanding Officer (CO). 3.11.2.2. An NRC may only be up to one rank higher than its player’s Primary Rated Character (PRC). This includes enlisted ranks as shown on the rank explanation page. (i.e.: A Lieutenant could control an NRC no higher than Lieutenant Commander). 3.11.2.2.1. Exceptions to this provision must be approved by the President (Pres), Vice President (VP), or Commander in Chief (CinC). 3.11.2.2.2. An NRC with the rank of Captain or higher must be approved by the Pres, VP, or CinC. 3.11.2.3. Only members with the rank of Lieutenant Junior Grade or higher may create registered NRCs. 3.11.2.4. Registered NRCs must have their bios approved by the Academy. 3.11.2.5. A registered NRC account that has not been used for over 90 days is subject to deletion without notice. 3.11.3. Procedures 3.11.3.1. Players submit NRC character idea to the ship’s CO for approval. For registered NRCs, a full character biography must be submitted. 3.11.3.2. If they are applying to play an NRC on a different ship than their PRC, they must also seek permission of their PRC’s CO. 3.11.3.3. The CO reviews the character and determines if it’s a good fit for their ship. 3.11.3.4. The CO notifies the player (and the PRC’s CO, if applicable) of the character’s approval or denial. 3.11.3.5. Once approved, the player may request an NRC forum account using the Account Request Form. 3.11.3.6. For registered NRCs, character bios must be added to the ship’s wiki page.

3.12. Secondary Rated Characters (SRC)

3.12.1. Policy: 3.12.1.1. Secondary Rated Characters (SRCs) allow players to play a second character that earns points (and is thus “rated”). 3.12.1.2. SRCs may not serve on the same starship as the player’s Primary Rated Character (PRC). 3.12.1.3. Players with PRCs at the rank of Lieutenant Junior Grade or above may create an SRC with the approval of their Commanding Officer (CO) and the approval of the CO on the ship where the SRC will serve. 3.12.1.4. Newly created SRCs begin with 1,500 points and the rank of Ensign. 3.12.1.4.1. No new SRC may start with more than 1,500 points without the approval from the President (Pres), Vice President (VP), or Commander in Chief (CinC). 3.12.1.4.2. An SRC may begin with the rank of Lieutenant Junior Grade in order to fulfill the requirements to be a Department Head (DH), with approval of the Pres, VP, or CinC. However, these SRCs will still begin with 1,500 points and must earn their way to the next rank through normal methods. 3.12.1.5. SRC bios must be approved by the Academy. 3.12.1.6. SRCs may not hold any position above DH. 3.12.2. Procedure: 3.12.2.1. Members email their interest and a character concept to the CO of the ship on which they wish to have an SRC. 3.12.2.2. The CO will respond with approval or denial of the character. 3.12.2.3. If approved, the member then must receive permission to play an SRC from their PRC’s CO. This permission must be forwarded to the SRC’s intended CO and Fleet Commander (FC). 3.12.2.4. The player creates a biography for the SRC and submit this to the SRC’s intended CO and FC. 3.12.2.5. The CO and FC review the bio and provide feedback. 3.12.2.6. Once approved, the player requests an SRC forum account using the Account Request Form. 3.12.2.7. Character bios must be added to the ship’s wiki page.

3.13. Leaves of Absence (LOA)

3.13.1. Policy: 3.13.1.1. In recognition of the fact that sometimes real life takes precedence over our sci-fi existence, we have an established leave of absence policies. 3.13.1.2. Leave of Absence (LOA): 3.13.1.2.1. An approved absence of two weeks to two months. 3.13.1.2.2. Requires approval of Commanding Officer (CO). 3.13.1.3. Extended Leave of Absence (ELOA): 3.13.1.3.1. An approved absence of two months to four months. 3.13.1.3.2. Requires approval of Fleet Commander (FC). 3.13.1.4. Special Leave of Absence (SLOA): 3.13.1.4.1. An approved absence greater than four months. 3.13.1.4.2. Requires approval of Commander in Chief (CinC) or President (Pres). 3.13.1.5. A date of return must be provided to approval authority prior to an absence. 3.13.1.6. Players may ask for an extension of their current leave. 3.13.1.7. In the event that the player does not return at the end of the points cycle following the return date, the character will be considered abandoned. 3.13.2. Procedure: 3.13.2.1. Prior to their leave, players must email the leave approval authority with a leave request. Request should include leave starting date and the expected date of return. 3.13.2.2. The approval authority will acknowledge the leave, and note it down on the Active Personnel (AP) sheet. 3.13.2.3. Players must notify their CO upon their return.

3.14. AWOL and Abandoned Characters

3.14.1. Policy: 3.14.1.1. Players who don’t post for 30 consecutive days, without any notification to their Commanding Officer (CO), will have their characters declared “AWOL”. 3.14.1.2. Players who have been considered AWOL for 30 days will have their characters declared Abandoned. 3.14.1.2.1. Abandoned characters are deleted, and all rank, position, and points associated with that character are forfeit. 3.14.2. Procedure: 3.14.2.1. A CO who does not hear from a member for 30 consecutive days will notify their Fleet Commander (FC). 3.14.2.2. The FC will mark the character AWOL on the AP sheet. 3.14.2.3. After 30 additional days, if the member has not returned, the FC will remove the character from the AP sheet. 3.14.2.4. The CO will remove the character from points charts. The CO will also update the wiki roster and mark the character's wiki bio as retired. 3.14.2.5. The FC will notify the CinC of the character abandonment. The character account will be deleted from the forum by the FC or CinC. 3.14.2.6. If applicable, the FC will notify the Content Manager (CM) to delete player's wiki account.

3.15. Character Death

3.15.1. Policy: 3.15.1.1. A member whose character dies as part of an approved plot, with no intention of leaving the site, will suffer no penalties in either rank or points. The player may create a new character with the same position, rank, and points. Such plots require the written approval of the Creative Director (CD). 3.15.1.2. Members who arbitrarily kill their character with the intention of leaving the site only to return at a later date will forfeit their rank and points. 3.15.1.2.1. A member that returns after such an event must obtain permission of the Commander in Chief (CinC) and create a new character. 3.15.1.3. Members who put their characters intentionally in a situation where the character would be killed, with no intention of leaving the site: 3.15.1.3.1. The ship Game Moderator (GM) will discuss the scenario with the Creative Director (CD) and Site Administration regarding possible outcomes for the character. 3.15.1.3.2. If it’s determined that there’s no plausible way for the character to be saved, the character will face the story outcomes. 3.15.1.3.3. The player will be required to write up a new character, though they may retain the same rank and position of the killed character.

3.16. Returning Players

3.16.1. Policy: 3.16.1.1. Members that leave the site via character abandonment who wish to return to former characters/rank/points/position will suffer the following penalty: 3.16.1.1.1. One reduction in rank per month away from site. 3.16.1.1.2. The returning member’s points will be reduced to the minimum amount of points necessary to hold their new rank. 3.16.1.1.3. There is no guarantee the player will return to the same ship or position. 3.16.1.1.4. If more than 12 months have elapsed since the players' departure, they must start over as a new player via standard means unless two Site Administrators approve the return in another form. 3.16.1.2. Players that leave the site via character abandonment who do not wish to return to former characters/rank/points/position may reapply as new members. 3.16.2. Procedure: 3.16.2.1. Returning players must email the Commander in Chief (CinC) with their character name and reason for abandonment. 3.16.2.2. The CinC will review the player’s site history and their reason for abandonment and determine the rank reductions. 3.16.2.3. The CinC will determine if the player may return to their previous ship assignment, or forward the player to the Academy for ship assignment. 3.16.2.4. Character bios of returning players, whether for a new character or continuing their existing character, are subject to review by the Academy.

3.17. Transfer Requests

3.17.1. Policy: 3.17.1.1. From time to time, players wish to transfer their character to another starship. 3.17.2. Procedures: 3.17.2.1. The player must first email a transfer request to the Commanding Officer (CO) of the ship they wish to transfer to. 3.17.2.2. The receiving CO, if they plan to accept, will email their Fleet Commander (FC) requesting approval for the transfer. 3.17.2.3. The receiving FC will contact the losing FC to request transfer approval. 3.17.2.4. The losing FC will contact the losing CO for their approval. 3.17.2.5. If the losing CO and FC approve the transfer, the losing FC then notifies the receiving FC. 3.17.2.6. The receiving FC then notifies the player and the receiving CO of the approval. 3.17.2.7. The receiving CO ensures all rosters, character bios, account profiles, and the Active Personnel (AP) sheet are updated in a timely manner to reflect the transfer. 3.17.2.8. If a transfer is rejected for any reason by a losing CO or FC, the player may appeal to the Commander in Chief (CinC). The CinC acts as the final approval authority on all transfer requests. 3.17.2.9. If a transfer is rejected for any reason by a receiving CO or FC, there is no appeal process.

3.18. Fleet Expansion

3.18.1. Policies 3.18.1.1. Fleet Expansion refers to the addition of a new rated character starship to the Fleet. 3.18.1.1.1. This refers to the addition of a ship to the site, not the replacement of an existing ship with another. 3.18.1.2. The Site Administration continually reviews membership levels to determine if a new vessel should be added. Guidelines for this include: 3.18.1.2.1. When all current ships have met their requested personnel levels in each department (usually two). 3.18.1.2.2. The site has enough qualified personnel of appropriate ranks to fill Commanding Officer (CO), First Officer (FO), and Department Head (DH) roles of the new ship. 3.18.2. Procedures 3.18.2.1. The President (Pres), under advisement of the other Site Administration, will approve the type and name of the new ship to be launched. This may include giving the new ship’s CO naming privileges. 3.18.2.2. The Site Administration, with advisement from Fleet Commanders (FCs), will select a CO as per section 3.4. 3.18.2.3. Working with the CO, the Site Administration will set a ship launch date. Once determined, the Pres will make an official announcement. 3.18.2.4. The CO will select an FO as per section 3.5. 3.18.2.5. The CO and FO will recruit DHs as per section 3.6. 3.18.2.6. New forum space will be created by the Site Administration.

3.19. Disciplinary Measures

3.19.1. Policy: 3.19.1.1. Disciplinary measures are established to enforce the site’s rules and regulations. 3.19.1.2. Reprimand 3.19.1.2.1. Issued by a Commanding Officer (CO) or above upon the approval of the Fleet Commander (FC). 3.19.1.2.2. Issued for a rules infraction. 3.19.1.2.3. Recipients of a reprimand will lose 500 points per reprimand. These points will be deducted on the next points cycle. 3.19.1.2.4. Reprimand will be added to career section of the character bio on the wiki. 3.19.1.2.5. May be appealed to the Commander in Chief (CinC). 3.19.1.3. Court Martial 3.19.1.3.1. Issued by the FC. 3.19.1.3.2. Issued for major rules infractions or to members who accumulate three Reprimands within a one year period. 3.19.1.3.3. Recipients of a Court Martial will drop one full rank, and their points total will drop to the minimum points necessary to hold this rank. 3.19.1.3.4. The career section of the character bio on the wiki will be updated to reflect this event. 3.19.1.3.5. May be appealed to the CinC. 3.19.1.4. Membership Revocation 3.19.1.4.1. Issued by the CinC in consultation with the Site Administration. 3.19.1.4.2. Issued for gross rules violations or for multiple rules infractions. 3.19.1.4.3. Players that have their membership revoked will no longer be allowed to participate on the site. 3.19.1.4.4. The CinC may issue a term-length of the membership revocation. 3.19.1.4.5. May be appealed to the President (Pres). 3.19.2. Procedures: 3.19.2.1. Complaints will be submitted via email up the chain of command. 3.19.2.2. The complaint will be investigated by the next link in the chain of command above the complainant and offender. 3.19.2.3. Evidence gathered is reviewed. This includes relevant posts, emails, chat text, etc. 3.19.2.4. If required, the complaint may be referred to the next higher link in the chain of command. 3.19.2.5. Once a decision is reached, the members involved will be notified via email of the decision and, if required, of any action needed. 3.19.2.6. A player may request an appeal within seven days of a decision. The appeal must be submitted via email up one level higher in the chain of command, or directly to the Pres. 3.19.2.7. The appeal will be reviewed by no less than three people. 3.19.2.8. Once a decision is reached, the members involved will be notified via email and, if required, of any action needed. 3.19.2.9. Decision of an appeal is final.

3.20. Recruiting/Advertising

3.20.1. In an effort to spread the word about the site and increase our membership, current members are encouraged to recruit new members. 3.20.1.1. New members may be recruited from family, friends, chat rooms, newsgroups, or any other viable source. 3.20.1.2. New members may be recruited from other Star Trek roleplaying games. Members should seek permission of other games before posting advertisements for players. 3.20.1.3. Current members that recruit a new member is eligible for a 300 point recruitment bonus when the new member reaches the rank of Ensign. 3.20.1.3.1. It is up to the recruiting member to notify their Commanding Officer (CO) when the recruited member reaches Ensign. 3.20.2. Advertising on other RPG and Star Trek related sites is encouraged. 3.20.2.1. Before doing so, please contact the Academy Superintendent (Supt). Inform them where you plan to submit an ad, what the ad will say, and if the site has any other requirements. 3.20.2.2. If the site requires a reciprocating link, please notify the Supt. 3.20.2.3. No Federation Space banner or links will be placed on politically affiliated sites or those that condone violence, adult-only content, hatred, racism, or discrimination of any form.

4. SECTION 4 – Association

4.1. Amendments

4.1.1. Amendments and updates to the Constitution may be made by majority agreement of the Site Administration.

4.1.2. Members will be notified of major changes through a post made in the Red Alert area of the forum.

4.1.3. By being a member of Federation Space, all players automatically agree to any changes made to the Constitution and, by extension, any future Constitutions issued by Site Administration.

4.2. Copyrights

4.2.1. Federation Space is considered a roleplaying game/fanfiction site. Star Trek and all its derivatives are copyright to Paramount/CBS/Viacom. No copyright infringement is intended.

4.2.2. All works on this website are fictional. Names, characters, technologies, incidents are fictional, and any resemblance to other persons, businesses, technologies, real or fictional, are entirely coincidental.

4.2.3. By being a member, players grant the Federation Space RPG joint ownership over characters and any writing done by players that is posted to the forum.

4.2.4. No content from another roleplaying game or fanfiction site will be posted to the forum or wiki without the permission of the President (Pres).

4.2.5. Members wishing to use copyrighted material from the Federation Space RPG must obtain the permission of the Pres and/or the member who created the content. This includes characters, writing, graphics, layouts, and any other intellectual property.