Project Charter

FckTrump Project Charter

Version 1.4.0 | Generated: 2025-11-03

Article I: Foundation

Section 1.1 - Name and Purpose

This organization shall be known as the FckTrump Project (“FckT”). The Project unites MetalStorm squadrons under a shared mission, code of conduct, and common organizational framework while respecting their individual goals, character, and operational styles.

Section 1.2 - Mission

We are a Metalstorm community that exists to challenge MAGA’s sense of dominance. In this corner of the Universe, fascists don’t get to own the narrative unchallenged. We are, in our own small way, contributing to the greater resistance to fascism. We are a constant reminder that they do not own the skies. FckT aims to provide a structured home for MetalStorm squadrons united in opposition to Trump, bound by agreed values and systems.

Section 1.3 - Organizational Model

The FckT Project operates as a federation of squadrons governed by a central command. Each squadron maintains its own identity, leadership, culture, and standards within the framework of Project-wide agreements.

Section 1.4 - Definitions

For purposes of this Charter:

Pilot: Any individual member of the Project
Squadron: A unit within the Project with its own leadership and standards
CiC (Commander in Chief): The chief executive and head of the FckT Project who chairs the Leadership Council
Leadership Council: The governing body comprising at least five members, including all Squadron COs and additional members nominated and approved by the Council
Command Staff: Staff positions appointed by the CiC to execute Project operations
Secretary: Leadership Council member responsible for record keeping and meeting administration
CO (Commanding Officer): The primary leader and in-game owner of a squadron
XO (Executive Officer): The second-in-command of a squadron
Administrator (Admin): Additional leadership roles within a squadron beyond CO and XO
Transfer: Movement of a pilot from one squadron to another
Project: The FckTrump Project, the collective organization of all squadrons
Charter: This governing document
SOP (Standard Operating Procedure): Detailed operational procedures adopted under Article IX

Article II: Structure and Governance

Section 2.1 - Leadership Council

The Leadership Council is the primary governing body of the FckTrump Project, comprising at least five members with a minimum quorum of three for all business. The Council includes:

All Commanding Officers (COs) from all squadrons (automatic membership)
Additional members nominated by any Council member and approved by majority vote
Members serve until resignation, removal, or inability to perform duties

Section 2.1.0 - Leadership Council Membership and Structure

Minimum Size and Quorum:

The Leadership Council must maintain a minimum of five members
Quorum for all Council business requires at least three members present
If membership falls below five due to resignation, removal, or inability to perform duties, the remaining Council members must nominate and approve replacement members by majority vote within 14 days

Membership Requirements:

All Squadron COs are automatically members of the Leadership Council
Non-CO members may be nominated by any Council member
Nominees must be active Project members in good standing
Approval requires simple majority vote of Council members present
Members may be removed by three-fifths supermajority vote for misconduct, inactivity, or inability to perform duties

Powers of the Leadership Council:

The Leadership Council has the following binding authorities:

Elect the Commander in Chief by simple majority vote
Remove the Commander in Chief with a three-fifths supermajority vote for the following reasons:
- Gross misconduct or violation of this Charter
- Abuse of authority
- Failure to fulfill duties of office
- Loss of confidence by the Leadership Council
Final authority over disciplinary actions involving Commanding Officers
Final authority to approve commendations for Commanding Officers

The Leadership Council provides advisory functions:

Deliberate on Project-wide matters and provide recommendations to the CiC
Help shape policies and Standard Operating Procedures through recommendations
Review violations of Project standards and recommend actions to the CiC
Approve new squadrons joining the Project by simple majority vote
Nominate and approve new Leadership Council members by majority vote
When the CiC is unavailable or on leave, provide recommendations to the acting CiC

The CiC makes final decisions on all matters except where the Leadership Council has binding authority as specified above.

Section 2.1.1 - Meetings and Procedures

Leadership Council meetings shall be conducted according to the following procedures:

Meeting Scheduling and Notice:

The CiC may call meetings at any time
Any two Council members may call a meeting by providing notice to all Council members
Notice of meetings must be provided to all Council members at least 48 hours in advance
Emergency meetings may be called with 24 hours notice for urgent matters
Secretary prepares and distributes agenda 24 hours before regular meetings

Meeting Conduct:

Quorum requires at least three Council members to be present
If the CiC is unavailable or is the subject of the meeting, the most senior Council member (by tenure in position) shall preside
Secretary records minutes of all meetings and decisions
If Secretary is absent, the presiding officer designates a temporary minute-taker
Temporary minute-taker must be a Council member present at the meeting
Formal motions required for all votes
Second required for all motions before discussion
Discussion period before voting on all motions
Roll call voting for important decisions (CiC removal, charter amendments)
Results announced and recorded by Secretary

Voting Requirements:

Election of CiC requires simple majority vote of Council members present
Removal of CiC requires three-fifths supermajority of all Council members (not just those present)
Advisory recommendations require simple majority of Council members present
Charter amendments require three-fifths supermajority of all Council members (not just those present)

Record Keeping:

Secretary maintains official minutes of all meetings
If Secretary is absent, temporary minute-taker provides notes to Secretary within 24 hours
Secretary reviews and finalizes all minutes before distribution
Minutes distributed to all Council members within 48 hours of meeting
All votes recorded with member names and outcomes
Secretary maintains archive of all Council decisions and votes

Section 2.1.2 - CO Commendations

Procedures for commending Commanding Officers:

Any pilot, CO, or Project member may nominate a CO for commendation
The CiC reviews nominations and recommends commendations to the Leadership Council
The Leadership Council approves commendations by simple majority vote
COs who are the subject of a commendation must recuse themselves from voting
Approved commendations become part of the Project record

Section 2.1.3 - CO Disciplinary Actions

Procedures for disciplining Commanding Officers:

The CiC may recommend disciplinary action against a CO to the Leadership Council
The Leadership Council approves disciplinary actions by simple majority vote
COs who are the subject of disciplinary action must recuse themselves from voting
The CO facing discipline has the right to be heard before the vote
Disciplinary actions may include warnings, suspensions, removal from CO position, or removal from the Project
Approved disciplinary actions become part of the Project record

Section 2.2 - Commander in Chief

The Commander in Chief (CiC) serves as the chief executive and head of the FckT Project. The CiC is elected by the Leadership Council and holds final decision-making authority on Project-wide matters. The CiC:

Chairs the Leadership Council
Makes final decisions on Project policies, standards, and operations with input from the Leadership Council
Appoints Command Staff to support Project operations
Deputizes pilots, including COs, to carry out specific Project-wide initiatives and delegate authority as necessary
Ensures adherence to this Charter
Facilitates inter-squadron cooperation
May create and recruit new squadrons for Project membership
Reviews and decides on violations of Project standards

Section 2.2.1 - Term of Service

The CiC serves a one-year term. At the end of each term, the Leadership Council shall vote by simple majority to extend the CiC’s term for an additional one-year term or elect a new CiC. There is no limit to the number of terms a CiC may serve if the term is extended.

Section 2.2.2 - Delegation Authority

The CiC may delegate authority and responsibilities to execute Project-wide initiatives:

Appoint pilots to temporary or permanent roles supporting Project operations
Deputize COs or other pilots to lead specific initiatives, task forces, or working groups
Grant specific authorities necessary to accomplish delegated tasks
Revoke delegations at any time
Delegated authority does not transfer the CiC’s final decision-making power
CiC remains accountable for actions taken under delegated authority

Section 2.2.3 - Succession

If the CiC becomes unavailable due to leave, illness, or other temporary circumstances, the Leadership Council shall nominate and elect an acting CiC by simple majority vote.

Acting CiC has full authority to make decisions and call meetings
Acting CiC status continues until the CiC returns or the LC elects a permanent replacement
The CiC may notify the LC of planned absence and nominate an acting CiC for LC consideration
If the CiC is removed or permanently steps down, the Leadership Council must elect a new CiC within 14 days

Section 2.3 - Command Staff

The Command Staff consists of positions appointed by the CiC to execute Project operations and provide administrative support. Command Staff handles day-to-day functions including but not limited to website maintenance, logistics, scheduling, and administrative coordination. Command Staff members serve at the pleasure of the CiC. Specific roles and responsibilities are defined in Project SOPs.

Section 2.3.1 - Secretary

The Secretary is a Leadership Council member appointed by the CiC to handle official record keeping and meeting administration:

Records and maintains minutes of all Leadership Council meetings
Tracks all Council decisions, votes, and official actions
Maintains official Project records and archives
Distributes meeting notices, agendas, and minutes to all Council members
Serves as voting member of Leadership Council (if also a CO) or non-voting member
May be removed by three-fifths supermajority vote of Council members
Secretary position may be held by any Council member, including COs
If Secretary is unavailable for extended period, CiC may appoint acting Secretary
Acting Secretary has full authority of Secretary role until Secretary returns or replacement appointed
Secretary absence does not prevent Council meetings from proceeding

Section 2.4 - Squadron Leadership

Each squadron shall have:

One Commanding Officer (CO) who leads the squadron
One Executive Officer (XO) who supports the CO
Up to two additional admins as determined by squadron leadership
CO serves as voting member of Leadership Council
XO attends Leadership Council without voting power
Additional admins beyond two require Leadership Council approval

Section 2.5 - Honorary Titles

Titles such as “Founder” may be retained for historical recognition but carry no operational authority within the Project structure.

Article III: Squadron Formation and Membership

Section 3.1 - Squadron Creation and Recruitment

The Commander in Chief may create and recruit new squadrons for Project membership. Additionally, existing squadrons may apply for Project membership.

Section 3.2 - Squadron Application Process

Squadrons seeking Project membership must:

Submit a formal application to the Leadership Council
Meet minimum membership requirements (to be defined in Project SOPs)
Demonstrate alignment with Project mission and values
Provide squadron leadership structure including CO and XO
Agree to abide by Project Charter and standards

Section 3.3 - Squadron Approval

All new squadrons must be approved by the Leadership Council by simple majority vote
The CiC facilitates the application process but does not have veto power
The Leadership Council must vote on applications within 30 days of submission
Approved squadrons immediately gain full Project membership and their CO becomes a Leadership Council member

Section 3.4 - Squadron Dissolution

Inactive or non-compliant squadrons may be dissolved by Leadership Council vote
Dissolution requires three-fifths supermajority vote of Council members
Squadron members retain individual Project membership unless removed for cause
Squadron assets and resources are handled according to Project SOPs

Article IV: Squadron Operations

Section 4.1 - Internal Management

Within the framework of this Charter and Project-wide standards, each squadron manages:

Recruitment standards and requirements
Internal culture and leadership style
Activity requirements and participation expectations
Internal discipline and management
Squadron-specific events and initiatives

Section 4.2 - Supremacy Clause

Project-wide Standard Operating Procedures, policies, and this Charter take precedence over squadron-level rules in all cases. Where squadron rules conflict with Project standards, Project standards govern. Squadron leadership must ensure their internal procedures align with and do not contradict Project-wide requirements.

Section 4.3 - Non-Interference

Squadrons shall not interfere in the internal operations of other squadrons. Inter-squadron disputes shall be resolved through the Leadership Council.

Article V: Pilot’s Bill of Rights

Section 5.1 - Right to Information

Pilots have the right to know both Project-wide and squadron-specific standards, policies, and expectations. This includes but is not limited to activity requirements, performance standards, code of conduct, and operational procedures.

Section 5.2 - Right to Notice

Pilots must be informed when standards, policies, or expectations change. Changes to squadron or Project requirements shall be communicated clearly and in advance when possible.

Section 5.3 - Right to Clear Expectations

Pilots have the right to understand performance requirements, activity standards, and communication expectations before joining a squadron. Squadron standards must be documented and made available to prospective and current pilots.

Section 5.4 - Right to Communication

Pilots have the right to be directly informed of any issues regarding their standing, performance, or conduct. Squadron leadership must communicate concerns clearly and in a timely manner.

Section 5.5 - Right to Due Process

Pilots facing removal have the right to understand the reasons why and to respond. Removal procedures must follow established Standard Operating Procedures except in cases of serious misconduct.

Section 5.6 - Right to Appeal

Pilots may contest removal decisions through established procedures. The Leadership Council serves as the final arbiter in contested cases.

Section 5.7 - Protection from Retaliation

Pilots shall not face retaliation for exercising their rights, requesting transfers, raising concerns, or appealing decisions.

Article VI: Amendments

Section 6.1 - Amendment Process

This Charter may be amended by three-fifths supermajority vote of all Leadership Council members. Proposed amendments must be:

Presented in writing to all Leadership Council members
Discussed in Leadership Council meeting
Approved by three-fifths supermajority of all Leadership Council members (not just those present)

Adopted: [Date]

Signatures of Leadership Council:

This Charter is hereby adopted by the Founding members of Leadership Council of the FckTrump Project.

Name	Role	Date
Novacaine	Commander in Chief, CO FckT1
Clutch	Secretary, FckT4
DmanYoFoo!	Founder, CO - FckT2
Beekeeper	CO - FckT3
Ibic	Member of the Council

Document Information:

Charter Version: 1.4.0
Effective Date: 2025-10-29
Last Amended: 2025-10-29
Next Review: 2026-10-29

Document History

Version Information

Current Version: 1.4.0
Generated Date: 2025-11-03
Document Status: Official

This document is maintained at: https://github.com/fckt-clutch/fckt-charter For the source markdown, see: charter/FckTrump Project Charter.md