Astral Dynamics: Manifesto

We dig it, haul it, and keep the people moving it alive.

Astral Dynamics began by feeding Project Archangel with construction materials. Today we supply, escort, refuel and recover wherever the work and the danger are. A fleet is only as good as its last tank of fuel and its last magazine, and we exist so that nobody runs dry.

What we stand for

• Reliability. A contract is a promise, and we deliver.
• Nobody left behind. We answer distress calls, recover stranded crews and stand with the Civilian Defense Force when it calls.
• Honest trade. We deal fairly with human, Xi’an and Banu partners, and we bring in rare materials from beyond UEE space.
• Industry, not piracy. We earn our credits. We don’t prey on haulers, and we don’t grief. If a fight finds us, we finish it.

What we do

• Prospecting & Procurement. Mining, refining and sourcing.
• Hauling & Logistics. Cargo, contracts and fleet supply.
• RRR Division. Resupply, escort and recovery, backed by our Starfarer, Reclaimer, Kraken and Idris-M.

How we operate

We are friendly and relaxed, and we run organised operations when the work needs it. Our crews keep Greenwich time (GMT/BST) and communicate in English. Comms are part of the job. You need to be in voice chat with us, but a microphone is optional.

Who we want

Miners, haulers, escorts and salvagers who like steady, useful work in good company. Everyone starts as a Junior Employee and rises on merit, through Employee and Senior Employee. Group Leads, Division Leads and the Board are by invitation, so if you want to lead, show us how you work.

How to join

Join our Discord and ask a member of Staff!

Astral Dynamics Charter

Version 1.0 – adopted 14 October 2026

Article I – Name and purpose

Astral Dynamics is an industrial corporation. It exists to prospect, haul and supply, and through its RRR Division to escort and recover, honestly and reliably.

Article II – Membership

1. Any citizen may apply who accepts this Charter and can join voice chat. A microphone is optional.

2. New members serve a probation of three months before confirmation as full members. Probation affects membership status only and does not affect rank.

3. Members may hold affiliations with other organisations. Astral Dynamics’ interests come first during org operations, and no member may act against the org through an affiliate.

4. Inactivity is dealt with under Article VII.1.

Article III – Conduct

1. Members treat one another and outsiders with respect.

2. Piracy is forbidden and is a breach of this Article. Members do not prey on haulers or other non-hostile players.

3. Griefing, harassment, cheating, exploiting and hate speech are forbidden.

4. PvP is permitted in defence of the org, its members, its contracts and its cargo, and in sanctioned operations.

5. A non-member who commits piracy against a member, an org operation or org cargo is removed from the org’s Discord and from org operations after one incident. The Board records the removal.

Article IV – Ranks and divisions

1. Ranks, from lowest to highest, are Junior Employee, Employee, Senior Employee, Group Lead, Division Lead and Board Member.

2. Every new member starts as a Junior Employee and stays at that rank until promoted. Promotion from Junior Employee to Employee to Senior Employee is by merit, proposed by the Division Lead and confirmed by Human Resources. Promotion to Group Lead, Division Lead or Board Member is by offer.

3. The org has three divisions: Prospecting & Procurement, Hauling & Logistics, and the RRR Division. Each is led by a Division Lead. Where a post is unfilled, a Board Member acts in it.

Article V – The Board

1. The Board holds the org’s authority. Board roles are CEO, Executive, Human Resources and Marketing.

2. The CEO chairs the Board. Executive oversees operations, the fleet and the org fund. Human Resources handles recruitment, probation and discipline. Marketing handles recruitment outreach and the org’s public presence.

3. A Board decision passes with 60% of votes cast. A vote is valid only if at least three Board members take part.

4. Any willing member may join the Board, subject to approval by the CEO and the Board. A Board member is removed by a vote under paragraph 3.

5. Under-strength Board. While the Board has fewer than three members, the CEO and the remaining Board member decide jointly, in order to bring the Board back to three. Where only the CEO remains, the CEO may appoint new Board members only with the approval of the Division Leads. During this time the Board may not amend the Charter or spend from the fund, except to pay claims already due.

6. Conflicts of interest.

6.1 A Board member who is party to a matter, or who gains from it, declares this to the Board before the vote. They do not vote and do not count towards quorum.

6.2 No one votes on their own appointment to a Board seat.

6.3 A Board member does not vote in a dispute that concerns them.

6.4 Any Board member may propose spending from the org fund. The rest of the Board votes on it. Executive approves it and the CEO ratifies it. Where Executive made the proposal, the CEO approves it and another Board member ratifies it.

6.5 A Board member who breaches Article III or this Charter is dealt with by the rest of the Board and the CEO. If the CEO is the one in breach, the other Board members decide by 60% of the votes cast.

6.6 Where fewer than three eligible voters remain, paragraph 5 of this Article applies.

7. Donations. Board members, Division Leads and Group Leads are expected to donate to the org fund.

8. Fund check. Each month a Board member other than Executive checks the fund balance against Executive’s record and reports the result to the Board.

Article VI – Fleet and fund

1. Any member whose ship is outfitted to the standard a mission requires may use it on org operations.

2. Ships remain the property of their owners. Losses on org operations are handled under Schedule B.

3. The org fund is held and recorded by Executive. It is funded by the levy in Schedule A and by voluntary donations. Spending from it is decided under Article V.6.4.

4. Org mining, salvage and hauling events are paid under Schedule A. Payouts from normal contracts are split equally. Non-org mining is paid at the owner’s discretion, and a 5% share to the owner followed by an equal split of the rest is advised.

Article VII – Discipline and appeals

1. Warnings, suspension and removal.

1.1 Human Resources issues a written warning for a first breach of Article III. It is recorded and lapses after 90 days.

1.2 A second breach within 90 days leads to a suspension of 14 days. A suspended member keeps their membership but cannot join org operations, claim under Schedule B or vote.

1.3 A further breach within 90 days of the end of a suspension leads to removal, decided under Article V.

1.4 The member may reply in writing before any suspension or removal.

1.5 Serious breaches (real-money trading, exploiting, harassment) skip steps and may lead directly to removal.

1.6 Six months of inactivity leads to one notice. If the member doesn’t respond within 14 days, they are removed.

1.7 A member on notified leave is not treated as inactive.

2. Appeals. A removed or suspended member may appeal to a panel of the Board and the Division Leads. The panel also hears appeals against refused claims under Schedule B.8. The appeal must be made within 14 days of the decision, and the panel decides within 14 days of the appeal. The panel is quorate when at least 60% of its members are present, and it decides by simple majority of votes cast.

3. The member who ordered the removal or refusal attends to make their case. They do not vote and do not count towards quorum.

4. A member who fails to repay a recovery claim under Schedule B faces this Article.

Article VIII – Amendment

1. This Charter may be amended by a Board decision under Article V.

2. If a Board vote fails to reach 60% on two votes held at least 7 days apart, the matter goes to a vote of the members.

3. A members’ vote passes by simple majority of the votes cast. It is valid only if at least 50% of members active in the last 30 days vote.

4. Disciplinary decisions and claims involving a named member are not referred to a members’ vote.

Article IX – Definitions

• Org operation: an operation announced in the org’s Discord in advance by Executive or a Division Lead, with a crew list.
• Sanctioned operation: an org operation, or any action ordered during one.
• Mission standard: the minimum ship and loadout set by Executive in the announcement.
• Hostile: an NPC or player who attacks org members, ships or cargo without provocation from the org.
• Friendly: any other player, member or not, whose actions cause a loss.
• Wipe: a reset announced by CIG that clears aUEC balances and ships.
• Payout: the gross aUEC received from selling an operation’s yield, before any deduction.
• Crew: members aboard ships taking part in the operation. A scout is not crew.
• Notified leave: leave announced to the Board with an end date. It may be extended by notice to the Board. Human Resources queries any member who passes the end date without an extension.
• Presence: as defined in Schedule B.8.2.

Article X – Adoption, version and review

1. This Charter is version 1.0. The Board adopted it by a 60% vote on 14 October 2026, and it took effect that day.

2. It is published in the org’s Discord and on the org’s RSI page. Joining the org is acceptance of the Charter.

3. It is reviewed six months after adoption, and then at least once a year.

4. Changes take effect on publication. Changes to fund rules or discipline take effect seven days after members are notified.

Article XI – Succession, dissolution and ownership

1. If the CEO resigns, is removed, or is inactive for six months without notified leave, the other Board members appoint a new CEO by 60% of the votes cast. Until then, Executive acts as CEO.

2. The org may be dissolved by a Board vote with the approval of the Division Leads. Claims already due are paid first. The rest of the fund is split equally between active members. An active member is one who has had presence in the org community, as defined in Schedule B.8.2, in the 30 days before the dissolution vote.

3. The CEO owns the org’s RSI organisation and Discord. All Board members hold admin rights on both. If the CEO changes, ownership passes to the new CEO within 7 days.

4. Ships and accounts belonging to members stay theirs.

Article XII – Conduct and trading

1. Members must follow the terms of service and code of conduct published by Cloud Imperium Games.

2. Members must not buy, sell or trade, for real money or anything of real-world value, any of the following: aUEC, RSI hangar ships, in-game items, or RSI accounts. This applies to trades with any other player.

3. Members must not advertise any such trade, in the org’s Discord, on its RSI page, or in any org operation.

4. Buying from Cloud Imperium Games’ own store is not affected.

5. A breach of this Article is a serious breach under Article VII.1.5 and may lead directly to removal.

Schedule A – Org mining, salvage and hauling events

1. 10% of the payout goes to the org fund, fixed.

2. 5% of the remaining payout goes to the owner of the ship used, for operating costs.

3. The rest is split equally between the crew and the owner.

4. Scouts (mining operations).

4.1 A scout is a member who is not on the mining ship and who is explicitly scouting, declared to the crew at the start of the operation.

4.2 Scouting means finding a rock of suitable quality, quantity and mineral type for the mission objectives.

4.3 A scout is paid 15,000 aUEC for each rock that the mining crew mine, plus the bonus in Schedule C. The org fund pays the scout on the day of the operation, not from the payout.

4.4 Before the operation, Executive announces whether it is a quality operation or a quantity operation. Only the matching bonus applies.

4.5 The scout posts the scan result (mineral, quality, rock) in the org’s Discord. The crew confirm the rock was mined before it is paid.

4.6 Total scout pay for one operation may not exceed 50% of the fund’s 10% share of that operation’s payout. If it would, every scout’s pay is reduced proportionally.

Example for a 1,000,000 payout: 100,000 to the fund, 45,000 to the owner, and 855,000 split equally.

Schedule B – Ship losses on org operations

1. What is covered. The org covers the insurance claim fee for a lost ship and the fee for a loadout claim. It does not insure loadouts or pay for their replacement. Where Executive decides a ship is urgently needed for an org operation, the Board also covers the expedite fee, as far as the fund allows. The expedite fee is paid in addition to the insurance payout, is not capped, and does not count towards the tier cap.

2. Cover tiers. The cover tier is the lower of the tier the fund balance supports and the tier the last 30 days of donations support. Every figure is a maximum per claim.

Tier	Maximum cover	Donations in the last 30 days	Fund balance
Base	10k	none	none
Low	30k	50k	150k
Medium	100k	250k	500k
High	500k	1M	2.5M
Very High	1.5M	3M	7.5M

3. How the tier is decided.

3.1 A tier applies only if both its donation and balance thresholds are met on the day of the loss. If only one is met, the tier below applies.

3.2 Only voluntary donations count. The 10% levy in Schedule A does not.

3.3 The 30 days run back from the day of the loss, but never earlier than the most recent wipe.

3.4 Executive records the balance and the last 30 days of donations on the day of the loss. That record fixes the tier for the claim.

3.5 Thresholds do not change after a wipe. After a wipe, donations count from zero and the balance is the new in-game balance, so cover starts at Base and rises as the fund rebuilds.

3.6 The Board may pause all cover while the fund balance is below the Base cap.

3.7 A loss on the day of a wipe is assessed at the tier that applied before the wipe, and is paid only if the fund still holds the money.

4. Hostile NPCs and players. The org covers losses to hostile NPCs and players in full, up to the cap in paragraph 2.

5. Gameplay issues. Losses caused by bugs, server crashes and desync are covered at 50%, up to the cap. No evidence is needed unless the Board decides a claimant is abusing the system. As a guide, one org operation a week is about 13 in 90 days. The Board decides what counts as abuse.

6. Friendlies.

6.1 A loss caused by a member is paid for by that member. The member has 3 days to pay the owner. After that the fund covers the owner, and the member has 14 days to reimburse the fund.

6.2 A loss caused by a non-member is first claimed from the non-member. If the owner has not been reimbursed within 3 days, the fund pays 50% of the cover the loss would have received under paragraph 4, within the tier cap. The owner bears the rest.

6.3 Claims must be made within 14 days of the loss. The Board decides within 14 days of the claim.

7. Not covered. Losses from the owner’s own error, ships that did not meet the mission standard, losses outside org operations, and losses in breach of Article III or the mission brief.

8. Who may claim.

8.1 All members are eligible to claim, including members on probation.

8.2 The Board may refuse a claim if the claimant has had no presence in the org community in the last 30 days. Presence means any of the following: activity in the org’s Discord in a Star Citizen context; playing in the game with Astral Dynamics members; paying into the org fund.

8.3 A member on notified leave is exempt from the presence test until the end date of the leave.

8.4 A refusal is decided under Article V. It is given in writing with a reason, and Executive records it with the claim record.

8.5 The refused member may appeal under Article VII.2.

8.6 A claim by a Board member, Division Lead or Group Lead is paid only if they have donated at least 50,000 aUEC to the org fund in the 30 days before the loss, and never earlier than the most recent wipe. Their donations also count towards the tier. A claim by a Board member is decided by the other Board members. A claim by a Division Lead or Group Lead is decided by the Board.

8.7 A lead on notified leave is exempt from the donation condition in paragraph 8.6 until the end date of the leave. The 30-day period starts again on the first day after the leave ends.

9. Records. Executive keeps the record in paragraph 3.4 for each claim, and the refusals under paragraph 8.4. Only the Board may see these records.

10. Executive applies this Schedule. Disputes go to the Board.

Schedule C – Scout bonus

Quality operation. The bonus is based on the best quality of the target mineral in the rock. It is the same for every mineral.

Quality	Tier	Bonus
under 600	F–E	0
600–749	D / low C	3,000
750–899	C / B	7,500
900–969	A	15,000
970–999	S	30,000
1000	Perfect	75,000

Quantity operation. The bonus is based on the target mineral’s refined value per SCU. Executive may reset the value bands after a wipe and announces them before the next operation.

Refined value	Examples	Bonus
under 20k	common ores	0
20k–50k	Taranite, Bexalite, Gold, Laranite	5,000
50k–100k	Riccite, Diamond	10,000
100k and over	Quantanium, Savrilium, Stileron	25,000

Where a rock holds several minerals, the bonus is for the target mineral in the mission objectives.

Examples: a perfect-1000 rock in a quality operation pays 15,000 + 75,000 = 90,000. A Quantanium rock in a quantity operation pays 15,000 + 25,000 = 40,000.