PD-BOD-0001 Governing Documents - Revision history

CLloyd: Change division to branch

2026-03-13T10:39:12Z

Change division to branch

← Older revision		Revision as of 06:39, 13 March 2026
Line 25:		Line 25:
	:7. Directives are short single-topic documents that are created to provide guidance on how activities, within the purview/authority of the issuer, shall be undertaken.		:7. Directives are short single-topic documents that are created to provide guidance on how activities, within the purview/authority of the issuer, shall be undertaken.
	:::a. These documents further elaborate on those defined in Governing Policies.		:::a. These documents further elaborate on those defined in Governing Policies.
	:::b. All ~~Divisional Vice Presidents~~, Corporate Executives, as well as regional leadership may issue Directives or designate senior subordinates to do so on their behalf.		:::b. All Branch Heads, Corporate Executives, as well as regional leadership may issue Directives or designate senior subordinates to do so on their behalf.
	:::c. Shall be titled to clearly describe the topic and labeled with “DIR” followed by 3-letter code of authorizer (see Table 1 below) and sequentially numbered (example: DIR-RMN-0001).		:::c. Shall be titled to clearly describe the topic and labeled with “DIR” followed by 3-letter code of authorizer (see Table 1 below) and sequentially numbered (example: DIR-RMN-0001).
	:::d. Shall be maintained by its issuing authority and recorded with the Board Secretary.		:::d. Shall be maintained by its issuing authority and recorded with the Board Secretary.
Line 117:		Line 117:
	\| data-sort-value=01-12-24 \| 01 December 2024 \|\| Initial Approval \|\| Board of Directors		\| data-sort-value=01-12-24 \| 01 December 2024 \|\| Initial Approval \|\| Board of Directors
	\|-		\|-
			\| data-sort-value=13-03-26 \| 13 March 2026 \|\| Change division language to branch \|\| Steering committee, Bylaws and Governance Committee
			\|-
	\|}		\|}

	==PDF Version of the Document==		==PDF Version of the Document==
	:[https://drive.google.com/file/d/1jPYbr0VWBHHhlvKNe1zULLuAUyB-tVVl/view?usp=sharing PD-BOD-0001 PDF]		:[https://drive.google.com/file/d/1jPYbr0VWBHHhlvKNe1zULLuAUyB-tVVl/view?usp=sharing PD-BOD-0001 PDF]

CLloyd: add link to pdf

2025-09-19T10:13:53Z

add link to pdf

← Older revision		Revision as of 06:13, 19 September 2025
Line 119:		Line 119:

	\|}		\|}

			==PDF Version of the Document==
			:[https://drive.google.com/file/d/1jPYbr0VWBHHhlvKNe1zULLuAUyB-tVVl/view?usp=sharing PD-BOD-0001 PDF]

David Westover at 13:22, 8 August 2025

2025-08-08T13:22:30Z

← Older revision		Revision as of 09:22, 8 August 2025
Line 49:		Line 49:
	:12. No governing document shall be deleted. If the document is no longer in use, it shall be noted as such, on what date, by which authority, and placed in an archive for reference.		:12. No governing document shall be deleted. If the document is no longer in use, it shall be noted as such, on what date, by which authority, and placed in an archive for reference.

	:13. Orders shall be used for providing basic information to the members and can be issued by any unit leader on a topic within the scope of their authority. They are not considered an organizational governing document and therefore are limited in scope. Promotions, appointments, awards, and other honors are all examples of orders. Each order shall be titled, to clearly describe the topic, and labeled with a 3-letter code of the authorizer followed by the last two digits of the year and two digit month then sequentially numbered (example: CIV-2401-01 or ~~2FC~~-2402-05).		:13. Orders shall be used for providing basic information to the members and can be issued by any unit leader on a topic within the scope of their authority. They are not considered an organizational governing document and therefore are limited in scope. Promotions, appointments, awards, and other honors are all examples of orders. Each order shall be titled, to clearly describe the topic, and labeled with a 3-letter code of the authorizer followed by the last two digits of the year and two digit month then sequentially numbered (example: CIV-2401-01 or 02F-2402-05).

	:14. This policy in no way requires any organizational entity to ‘go back’ and re-align their document numbering or abbreviation system, but will only apply going forward from its approval date of 1 Dec 2024.		:14. This policy in no way requires any organizational entity to ‘go back’ and re-align their document numbering or abbreviation system, but will only apply going forward from its approval date of 1 Dec 2024.

David Westover at 17:49, 24 July 2025

2025-07-24T17:49:11Z

← Older revision		Revision as of 13:49, 24 July 2025
Line 88:		Line 88:
	\|BPL \|\| Bureau of Planning		\|BPL \|\| Bureau of Planning
	\|-		\|-
	\|BSH \|\| Bureau of ~~Ship~~		\|BSH \|\| Bureau of Ships
	\|-		\|-
	\|BCM \|\| Bureau of Communication		\|BCM \|\| Bureau of Communication

David Westover at 17:09, 24 July 2025

2025-07-24T17:09:52Z

← Older revision		Revision as of 13:09, 24 July 2025
Line 88:		Line 88:
	\|BPL \|\| Bureau of Planning		\|BPL \|\| Bureau of Planning
	\|-		\|-
	\|BSH \|\| Bureau of ~~Ships~~		\|BSH \|\| Bureau of Ship
	\|-		\|-
	\|BCM \|\| Bureau of Communication		\|BCM \|\| Bureau of Communication

David Westover: /* Record of Changes */

2025-06-26T16:28:12Z

Record of Changes

← Older revision		Revision as of 12:28, 26 June 2025
Line 113:		Line 113:
	{\| class="wikitable sortable"		{\| class="wikitable sortable"
	\|-		\|-
	! Effective Date !! Subject !! Proposed By ~~!! Vote~~		! Effective Date !! Subject !! Proposed By
	\|-		\|-
	\| data-sort-value=01-12-24 \| 01 December 2024 \|\| Initial Approval \|\| Board of Directors ~~\|\| \|\|~~		\| data-sort-value=01-12-24 \| 01 December 2024 \|\| Initial Approval \|\| Board of Directors
	\|-		\|-

	\|}		\|}

David Westover at 14:53, 26 June 2025

2025-06-26T14:53:22Z

← Older revision		Revision as of 10:53, 26 June 2025
Line 109:		Line 109:

	==Record of Changes==		==Record of Changes==
	Amendments may, from time to time, be proposed to, or by, the ~~Grand Alliance Joint Chiefs~~ of ~~Staff~~. Any amendments will be considered and voted on as necessary. All amendments that have been passed will be noted below.		Amendments may, from time to time, be proposed to, or by, the Board of Directors. Any amendments will be considered and voted on as necessary. All amendments that have been passed will be noted below.

	{\| class="wikitable sortable"		{\| class="wikitable sortable"

David Westover: Created page with "==PD-BOD-0001== :1. As a 501(c)(7) corporate entity under the IRS Code and State of Delaware Law, TRMN is required to have Articles of Incorporation and Bylaws and these shall be regularly updated and filed with the appropriate bodies. :2. To maintain an orderly organizational structure, the TRMN shall use the following hierarchy of documentation:
::: a. Articles of Incorporation ::: b. Bylaws ::: c. Governing Policies ::: d. Directives ::: e. Standard Operating P..."

2025-06-26T14:43:55Z

Created page with "==PD-BOD-0001== :1. As a 501(c)(7) corporate entity under the IRS Code and State of Delaware Law, TRMN is required to have Articles of Incorporation and Bylaws and these shall be regularly updated and filed with the appropriate bodies. :2. To maintain an orderly organizational structure, the TRMN shall use the following hierarchy of documentation:<br> ::: a. Articles of Incorporation ::: b. Bylaws ::: c. Governing Policies ::: d. Directives ::: e. Standard Operating P..."

New page

==PD-BOD-0001==

:1. As a 501(c)(7) corporate entity under the IRS Code and State of Delaware Law, TRMN is required to have Articles of Incorporation and Bylaws and these shall be regularly updated and filed with the appropriate bodies.

:2. To maintain an orderly organizational structure, the TRMN shall use the following hierarchy of documentation:<br>
::: a. Articles of Incorporation
::: b. Bylaws
::: c. Governing Policies
::: d. Directives
::: e. Standard Operating Procedures

:3. No document may contradict any document above it in the hierarchy. Any rule from lower in the hierarchy that conflicts is automatically considered void and every effort should be made to correct the conflicting document.

:4. Articles of Incorporation were initially filed with the State of Delaware for the creation of TRMN as a legal entity. This document shall be maintained and updated by the Board of Directors.

:5. Bylaws are required by the State of Delaware and the IRS and must operate within the boundaries set in the Articles of Incorporation.
::: a. This document lays out the legal governing structure of the organization
::: b. Shall be maintained and updated by the Board of Directors as needed.

:6. Governing Policies are used to elaborate and codify the necessary details and procedures for the regular governance of TRMN as prescribed by the Bylaws.
::: a. These policies may be created by the Board of Directors or one of its standing committees as directed by the Board.
::: b. Shall be titled to clearly describe the topic and labeled with “PD” followed by 3-letter code of authorizer (see Table 1 below) and sequentially numbered (example: PD-BOD-0001).
::: c. Shall be maintained by its issuing authority and recorded with the Board Secretary.

:7. Directives are short single-topic documents that are created to provide guidance on how activities, within the purview/authority of the issuer, shall be undertaken.
:::a. These documents further elaborate on those defined in Governing Policies.
:::b. All Divisional Vice Presidents, Corporate Executives, as well as regional leadership may issue Directives or designate senior subordinates to do so on their behalf.
:::c. Shall be titled to clearly describe the topic and labeled with “DIR” followed by 3-letter code of authorizer (see Table 1 below) and sequentially numbered (example: DIR-RMN-0001).
:::d. Shall be maintained by its issuing authority and recorded with the Board Secretary.

:8. Standard Operating Procedures (SOP) are a set of detailed step-by-step procedures that outline how unit operations approach and/or support one or more governing documents within the TRMN.
:::a. The following topics must be addressed within each SOP:
:::::i. Introduction/Purpose
:::::ii. Scope
:::::iii. Responsible Parties
:::::iv. Procedure
:::::v. Resources
:::::vi. Definitions
:::b. All creators shall follow the above format for the creation of SOPs.
:::c. Shall be titled to clearly describe the topic and labeled with “SOP” followed by 3-letter code of authorizer (see Table 1 below) and sequentially numbered (example: SOP-BOD-0001).
:::d. Shall be maintained by its issuing authority and recorded with the Board Secretary.

:9. All of the above documents shall be maintained as living documents on a typical TRMN location (e.g., wiki) so that all organizational members have easy access.

:10. Whenever a document is updated the date and approving body shall be noted at the bottom of the document. All documents shall keep a running record of all updates.

:11. All documents shall be reviewed annually and updated by the approving body as necessary to make sure that the documents reflect the most accurate account of current practices. The approving body may also rescind and archive a document that no longer has any relevance to the organization.

:12. No governing document shall be deleted. If the document is no longer in use, it shall be noted as such, on what date, by which authority, and placed in an archive for reference.

:13. Orders shall be used for providing basic information to the members and can be issued by any unit leader on a topic within the scope of their authority. They are not considered an organizational governing document and therefore are limited in scope. Promotions, appointments, awards, and other honors are all examples of orders. Each order shall be titled, to clearly describe the topic, and labeled with a 3-letter code of the authorizer followed by the last two digits of the year and two digit month then sequentially numbered (example: CIV-2401-01 or 2FC-2402-05).

:14. This policy in no way requires any organizational entity to ‘go back’ and re-align their document numbering or abbreviation system, but will only apply going forward from its approval date of 1 Dec 2024.

:15. This document will supersede/replace the following Orders and Directives: AO1202-03, AO1909-03, and AO2103-02

:'''Table 1. Three Digit Command Abbreviations'''
{| class = "wikitable sortable"
! Code !! Body
|-
|BOD || Board of Directors
|-
|EXC || Executive Committee
|-
|DIS || Discipline Committee
|-
|STC || Steering Committee
|-
|BGC || Bylaw and Governance Committee
|-
|LLC || Legal and Licensing Committee
|-
|RMN || Royal Manticoran Navy
|-
|RMA || Royal Manticoran Army
|-
|RMC || Royal Manticoran Marine Corps
|-
|GSN || Grayson Space Navy
|-
|RHN || Republic of Haven Navy
|-
|IAN || Imperial Andermani Navy
|-
|CIV || Civilian Corps (all sub-branches)
|-
|BPL || Bureau of Planning
|-
|BSH || Bureau of Ships
|-
|BCM || Bureau of Communication
|-
|BPR || Bureau of Personnel
|-
|BTR || Bureau of Training
|-
|BSP || Bureau of Supply
|-
|##F || Fleet Commands designated by two digit number (i.e. 01, 02, 10, etc)
|-
|##A || Army Commands designated with two digit number
|-
|##E || Marine Expeditionary Force designated with two digit number
|-
|XXQ || Civilian Quadrant Command with two letter abbreviation for name (i.e. DR = Draco)
|-
|}

==Record of Changes==
Amendments may, from time to time, be proposed to, or by, the Grand Alliance Joint Chiefs of Staff. Any amendments will be considered and voted on as necessary. All amendments that have been passed will be noted below.

{| class="wikitable sortable"
|-
! Effective Date !! Subject !! Proposed By !! Vote
|-
| data-sort-value=01-12-24 | 01 December 2024 || Initial Approval || Board of Directors || ||
|-

|}