SYSTEM SEVEN 2956 CHAMPIONSHIP

OFFICIAL REGULATIONS

1 — GENERAL PROVISIONS

1.1 Purpose & Spirit of Competition

1.1.1 — The System 7 is a competitive racing league conducted within Star Citizen and organized by ATMO Esports.

1.1.2 — These Sporting Regulations establish the rules, procedures, and standards governing all official System Seven events, including the qualifier and all championship races.

1.1.3 — The Racing League is inspired by professional motorsport formats such as Formula 1 while maintaining a community-focused environment designed to encourage participation, accessibility, and enjoyable competition.

1.1.4 — All participants are expected to compete in accordance with both the written rules and the spirit of fair competition.

1.1.5 — Any situation not explicitly covered within these regulations will be resolved by race officials in a manner that preserves competitive fairness and the integrity of the championship.

1.2 Regulatory Authority

1.2.1 — The System 7 is governed and administered by ATMO Esports and its appointed race officials.

1.2.2 — Race officials are responsible for:

• Administering race procedures
• Enforcing sporting regulations
• Reviewing incidents and protests
• Issuing penalties when necessary

1.2.3 — Race officials retain full authority to interpret these regulations and apply them in order to ensure fair and orderly competition.

1.2.4 — All participants must comply with instructions issued by race officials during any official System Seven event.

1.3 Applicability of Regulations

1.3.1 — These regulations apply to all participants involved in the System 7, including:

• Drivers
• Team members
• Event staff
• Race officials
• Participants in official communication channels

1.3.2 — By registering for or participating in any System 7 event, drivers and teams agree to comply with these regulations.

1.3.3 — Failure to comply with these regulations may result in penalties as defined in 8 — Protests & Penalties.

1.4 Official Event Scope

1.4.1 — The System 7 includes the following official events:

• Qualifier Event
• Seven Championship Races
• Any additional official sessions conducted by race officials

1.4.2 — These regulations apply to all official sessions conducted as part of the championship, including:

• Qualifying events
• Race sessions
• Administrative procedures related to the championship

1.5 Regulation Updates & Amendments

1.5.1 — ATMO Esports reserves the right to update or amend these regulations when necessary to address technical issues, competitive fairness, or operational requirements.

1.5.2 — Any amendments to these regulations will be communicated to participants prior to taking effect whenever reasonably possible.

1.5.3 — Updated regulations become effective immediately upon official announcement unless otherwise specified.

1.6 Interpretation of Rules

1.6.1 — In the event of ambiguity or disputes regarding the interpretation of these regulations, the decision of race officials will be considered final.

1.6.2 — Race officials may interpret these rules in a manner that best preserves the intent of the regulations and the fairness of competition.

1.6.3 — Participants are expected to respect and accept the rulings of race officials during official events.

2 — CHAMPIONSHIP STRUCTURE

2.1 Championship Format

2.1.1 — System 7 is conducted as a competitive racing series consisting of a qualifying event followed by seven official races.

2.1.2 — The competition field is limited to sixteen (16) teams, determined through the official qualifier event and any applicable automatic qualifications.

2.1.3 — The System 7 season includes the following official events:

Component Format

Qualifier Event Best Lap Time

League Races 7

Total Competitors 16

Heat Races 4 heats of 4 racers

The qualifier determines entry into the championship grid.

2.1.4 — Each race awards points that contribute toward the System 7 Team Standings.

2.1.5 — Certain races may use specialized formats, including heat races or ladder advancement formats, as defined in 5 — Competition Format.

2.2 Returning Champions Advantage

2.2.1 — The top three finishing teams from the previous System 7 season may automatically qualify for the following season.

2.2.2 — Automatic qualification is granted only if the following conditions are met:

• The team roster remains unchanged
• The team registers within the official registration period
• The team maintains the same team name

2.2.3 — If a returning team modifies its roster or fails to meet registration requirements, the team must qualify through the standard qualification process.

2.3 Championship

2.3.1 — The System 7 Champion is the team that accumulates the highest total number of points at the conclusion of the season.

2.3.2 — If two or more teams finish the season with equal points, the following tie-breaker criteria will be applied in order:

1. Highest number of race victories

2. Highest number of second-place finishes

3. Highest number of third-place finishes

4. Highest number of subsequent finishing positions

5. Best qualifying result during the season

2.6.3 — If a tie remains unresolved after applying these criteria, race officials will determine the final classification based on overall competitive performance throughout the season.

2.4 Official Season Results

2.4.1 — Final System 7 results will be declared official once all races have concluded and any outstanding protests or penalties have been resolved. Within a 48 hour timeframe?

2.4.2 — ATMO race officials reserve the right to adjust race results or standings if rule violations are discovered during post-race reviews.

3 — TEAMS & DRIVERS

3.1 Team Composition

3.1.1 — A System 7 team must consist of a minimum of one (1) and a maximum of four (4) registered Star Citizen players, hereafter referred to as citizens.

3.1.2 — Teams must register under a unique team name during the official registration period.

3.1.3 — Each registered team is permitted to have up to four members in order to provide scheduling flexibility and backup racers during the season.

3.1.4 — All members listed on the official team roster are considered eligible participants for System 7 events.

3.2 Driver Roles

3.2.1 — Only one team member may compete in a race at any given time.

3.2.2 — Teams may choose which registered member will represent the team for each race.

3.2.3 — The selected driver for a race is considered the Primary Racer for that event.

3.2.4 — Remaining team members serve as Backup Racers and may participate in future races if designated by the team.

3.2.5 — Points earned by the Primary Racer during a race are awarded to the team.

3.3 Qualifier Participation

3.3.1 — The System 7 qualifier determines which teams advance to the official race roster.

3.3.2 — Each team is allowed up to two drivers to attempt qualifying runs if the team has a full roster of four members.

3.3.3 — Each driver participating in the qualifier will complete the designated qualifying laps as defined in 5 — Competition Format.

3.3.4 — The fastest recorded lap time from a team will determine that team’s qualifying result.

3.4 Roster Lock

3.4.1 — Once the official registration period closes, team rosters become locked for the duration of the season.

3.4.2 — Teams may not add, remove, or replace members after the roster lock unless approved by race officials.

3.4.3 — Roster changes may only be approved in exceptional circumstances such as:

• Verified emergencies
• Long-term player unavailability
• Technical or account-related issues

3.4.4 — Requests for roster modifications must be submitted to race officials no later than 48 hours before the next scheduled race.

3.4.5 — Race officials reserve the right to approve or deny roster modification requests at their discretion.

3.5 Driver Responsibilities

3.5.1 — Drivers representing a team in a System 7 race are responsible for:

• Being present and ready at the designated race time
• Following all pre-race staging and race procedures
• Maintaining control of their vehicle and racing safely
• Communicating with race officials when required
• Reporting incidents or technical issues when necessary

3.5.2 — Drivers must comply with all instructions issued by race officials during official System 7 events.

3.6 Team Responsibilities

3.6.1 — Each team is responsible for ensuring that at least one eligible driver is available to compete in each scheduled race.

3.6.2 — Teams are responsible for coordinating internally to determine which team member will compete in each race.

3.6.3 — Teams are accountable for the conduct of their registered members during official System 7 events.

3.6.4 — Any rule violations committed by a team member may result in penalties applied to the team.

3.7 Team Identity

3.7.1 — Teams must compete under the registered team name submitted during registration.

3.7.2 — Team names may not contain offensive, discriminatory, or inappropriate language.

3.7.3 — Race officials reserve the right to require a team to modify its name if it violates community standards or event guidelines.

4 — SYSTEM 7 2956 POINTS SYSTEM

4.1 Standard Race Points

Points are awarded when the race leader completes 75% or more of race distance.

Position   Points

1st 25

2nd 18

3rd 15

4th 12

5th 10

6th 8

7th 6

8th 4

9th 2

10-16th 1

4.2 Fastest Lap Bonus

4.2.1 — Drivers receive +1 championship point for setting the fastest lap, provided they finish within the Top 16.

4.3 Heat Race Points

4.3.1 — For races using the HEATS format:

• Each heat awards full championship points
• Racers compete only within their assigned heat
• Points contribute directly to overall standings

4.3.2 — HEATS races:

• Race 2 – Covalex Distribution Center
• Race 4 – Winners Circle

4.4 Reduced Points for Partial Races

4.4.1 — If a race ends early:

Completion Points

≥75% Full points

50–74% Reduced points

25–49% Further reduced

<25% Minimal points

4.4.2 — If fewer than two laps are completed, no points are awarded.

Position    75%+ (Full Points)    50–74%   25–49% Under 25% 

1st                   25                   19           13         6

2nd                   18                   14           10         4

3rd                   15                   12     8         3

4th                   12                   10 6         2

5th                   10                     8             5         1

6th                     8                     6             4         0

7th                     6                     4             3         0

8th                     4                     3             2         0

9th                     2                   2             1         0

10-16th         1                     1              0         0

4.5 DNF (Did Not Finish)

4.5.1 — Drivers who do not finish a race may still be classified and eligible to receive championship points based on the percentage of race distance completed.

4.5.2 — A driver is considered classified if they have completed at least 25% of the scheduled race distance before retiring from the race.

4.5.3 — Classified drivers will be ranked according to the distance completed at the time of retirement, relative to other competitors.

4.5.4 — Points will be awarded according to the Race Completion Points Structure (4.4) based on the total race completion percentage achieved by the race leader.

4.5.5 — Drivers who retire before completing 25% of the race distance will be recorded as DNF – Not Classified and will not receive championship points.

4.5.6 — If a race is stopped early and cannot be restarted, drivers will receive points based on their classification order at the time of stoppage, provided they have completed at least 25% of the scheduled race distance.

5 — COMPETITION FORMAT

5.1 Qualification Event

5.1.1 — Location
Crossroad of Crime (AC), Nexus System – Track Name: Abandoned Speedway

5.1.2 — Vehicle
RSI Lynx

5.1.3 — Format

• 3 laps per attempt
• Best lap time recorded
• Top 16 teams advance

5.2 Standard Race Format

5.2.1 — Most races feature:

• 16 racers competing simultaneously
• Grid start formation will be determined per race.
• Starting positions determined by qualifying or previous race results

5.3 HEATS Format

5.3.1 — Certain System 7 races use a HEATS format due to track size limitations or race design that prevents all teams from competing simultaneously.

In the HEATS format, the sixteen (16) participating teams are divided into four heats of four teams each.

Heat Seeding

Teams will be seeded into heats based on the current System 7 Team Standings prior to the race.

The sixteen teams will be grouped into the following seeding brackets:

• Heat A — Teams ranked 1st through 4th
• Heat B — Teams ranked 5th through 8th
• Heat C — Teams ranked 9th through 12th
• Heat D — Teams ranked 13th through 16th

If the HEATS race occurs before official standings exist, seeding will be determined by qualifier results.

5.3.2 — Heat Race Procedure

• Each heat will run the same course, race format, and race distance.

• Drivers compete only within their assigned heat.

• Each heat produces a final race completion time for all participating teams.

• Heat finishing position alone does not determine advancement to the final races.

5.3.3 — Overall Time Classification

• After all heats are completed, teams will be ranked based on their overall race completion times across all heats.

• Overall classification will be determined from fastest to slowest race time, regardless of which heat the team competed in.

• This overall time ranking will determine advancement to the Final and Runner-Up Final races.

5.3.4 — Final Race Qualification

• The four teams with the fastest overall race times will advance to the Final Race.

• The Final Race will determine 1st through 4th place for the event.

5.3.5 — Runner-Up Final Qualification

• The teams with the 5th through 8th fastest overall race times will advance to the Runner-Up Final Race.

• The Runner-Up Final will determine finishing positions 5th through 8th.

5.3.6 — Remaining Positions

• The team with the 9th fastest overall heat time will be awarded 9th place and corresponding championship points.

• Teams ranked 10th through 16th will be classified based on their overall heat race times.

5.3.7 Tie Situations

If two teams record identical race times in the heat classification, the tie will be resolved based on:

• Fastest individual lap during the heat race

• Higher position in the current System 7 standings

If a tie still cannot be resolved, race officials will determine the final classification.

5.4 Race Starts

5.4.1 Grid Start

Drivers line up in the formation specified per race.

Overtaking is prohibited before crossing the start line.

The race begins when the official issues the “GO” command.

5.4.2 — Specific format for each race is noted in the race calendar (7)

6 — RACE PROCEDURES

6.1 Pre-Race Preparation

6.1.1 — Drivers must:

• Report to staging area 15 minutes before race start
• Spawn vehicles 10 minutes before race start
• ATMO officials will verify all participants are ready and in position
• Grid positions will be assigned based on qualifying or previous race results

6.2 Start Procedure

6.2.1 — Once all racers are staged and race officials confirm readiness, the race will begin using a 30-second countdown start procedure.

6.2.2 — An ATMO race official will initiate the countdown verbally in the following format:
"30 seconds…"
The countdown will continue until the start signal is given.

6.2.3 — When the countdown reaches zero, the race official will announce “GO!” which serves as the official start of the race.
•Drivers may begin accelerating only after the GO command is issued.

6.2.4 — Any driver who begins moving before the GO signal may be considered to have committed a false start and may receive a time penalty or other sanction determined by race officials.

6.2.5 — If a technical issue occurs before the start signal is given, race officials may pause or restart the countdown to ensure all competitors begin under fair conditions

6.3 During Race

6.3.1 Track Navigation

Drivers must:

• Pass all checkpoints in order
• Return if a checkpoint is missed
• Remain on the designated course

Track cutting or bypassing sections is prohibited.

6.4 Vehicle Usage

6.4.1 — Vehicle replacement is generally not permitted during System Seven races unless explicitly allowed within the specific race rules.

6.4.2 — Drivers are expected to complete the race using the same vehicle they started with.

6.4.3 — Vehicle replacement is only allowed under the following circumstances:

• The race rules for that specific event explicitly allow replacement.

• The replacement vehicle is the exact same model as the original race vehicle.

• The replacement occurs only at the designated spawn or start/finish location specified for that race.

6.4.4 — Drivers may not intentionally destroy or abandon their vehicle in order to gain an advantage through replacement.

6.4.5 — Drivers can not intentionally fire weapons or deliberately ram other racers.

6.4.6 — Intentional vehicle destruction, abuse of replacement mechanics, or spawning replacement vehicles outside of permitted areas may result in penalties including:

• Time penalties
• Position penalties
• Disqualification

6.4.7 — Technical Failure Exception

If a vehicle becomes inoperable due to a confirmed game bug, server issue, or physics glitch, race officials may allow a replacement at their discretion.

6.5 Race Completion

6.5.1 — The race winner is determined when the leading racer crosses the finish line after completing the full scheduled race distance.

6.5.2 — Once the race leader has crossed the finish line, all remaining racers will continue racing until they reach the finish line or are unable to continue.

6.5.3 — Drivers who are still on track when the winner finishes will be classified based on the distance completed and their position on the course at the time they cross the finish line.

6.5.4 — Drivers who are unable to reach the finish line will be classified according to the percentage of race distance completed, as outlined in the DNF classification rules (4.5).

6.5.5 — Final race classification will be determined by the following criteria:

• Drivers who completed the full race distance, ranked by finishing order

• Drivers who did not complete the full distance, ranked by the greatest distance completed

• Drivers who retired before completing the minimum classification distance

6.5.6 — The race is considered officially concluded once race officials confirm the final classification and declare the race complete.

6.5.7 — Race officials may delay the final declaration of results if incidents, protests, or technical issues require review.

Because of Star Citizen bugs and crashes, you may want to add this:

6.5.8 — Race Stoppage

If a race must be stopped due to server failure, technical issues, or track obstruction, race officials may suspend or restart the race. Points will be awarded according to the race completion percentage defined in 4.4.

6.6 Incident Reporting

6.6.1 — Drivers and teams must report any significant on-track incidents that occur during a race. Incidents include, but are not limited to:

• Collisions involving multiple racers
• Suspected rule violations
• Missed checkpoints that required correction
• Vehicle failures caused by contact with another driver
• Track obstructions or blocked course sections

• Technical issues that may affect race fairness

6.6.2 — Incidents should be reported to ATMO race officials as soon as reasonably possible through the designated event communication channel.

If the incident occurs during the race and does not prevent the driver from continuing, the driver should report the incident after completing the race.

6.6.3 — When submitting an incident report, the driver or team should include the following information when available:

• Name of the driver submitting the report
• Name(s) of any driver(s) involved
• The race and approximate location on the course where the incident occurred
• A brief description of what happened
• Any supporting video or screenshot evidence

6.6.4 — Drivers are encouraged to record their races when possible, as video footage may assist officials in reviewing incidents. However, video evidence is not required to submit a report.

6.6.5 — ATMO race officials may review reported incidents during or after the race. Officials may request additional information from involved drivers before issuing a ruling.

6.6.6 — Race officials may investigate incidents even if no formal report has been submitted if they observe potential rule violations during the race.

6.6.7 — Penalties resulting from incident reviews will be applied according to the penalty guidelines outlined in 8 — Protests & Penalties.

Officials may review incidents post-race and apply penalties.

7 — SYSTEM 7 2956 RACE CALENDAR

Event Location Vehicle Format

Qualifier COC - Abandoned Speedway (AC) RSI Lynx 3 Lap Time Trial

Race 1 Orison, Crusader - Leisure Loop (PU) Greycat STV 8 Laps

Race 2 Lorville, Hurston - Dust Hustle (PU) Drake Mule 12 Laps

Race 3 Levski, Nyx - Levski Helix (PU) Mirai Pulse LX 10 Laps

Race 4 Winner’s Circle - Deadman’s Hook (AC) Origin X1 Velocity HEATS - 3 Laps

Race 5 Monox, Pyro - Jackson’s Gauntlet (PU) Drake Mule HEATS - 3 Laps

Race 6 Bloom, Pyro - Marshfire Ridge (PU) Aopoa NOX 2 Laps

Race 7 Fairo, Pyro - Volcano Lake RSI Lynx → Tumbril Cyclone RC Final - 1 Lap

Some races require teams to supply vehicles and transport ships.
Legend: Arena Commander (AC), Persistent Universe (PU), Crossroads of Chaos (COC)

8 — PROTESTS & PENALTIES

8.1 Filing a Protest

8.1.1 — Any driver or team participating in a System 7 event may file a protest regarding actions that may have affected the outcome or fairness of a race.

8.1.2 — Valid protest subjects include, but are not limited to:

• Alleged rule violations by another competitor
• Unsafe driving or intentional contact
• Missing checkpoints or course violations
• False starts or race start violations
• Incorrect race classifications or results
• Procedural errors during race administration

8.1.3 — Protests must be submitted within 2 hrs of the official race completion announcement unless otherwise approved by race officials.

8.1.4 — All protests must be submitted in writing through the designated race communication channel.

8.1.5 — A valid protest should include the following information:

• Name of the driver submitting the protest
• Name(s) of the driver(s) involved
• The race and approximate location where the incident occurred
• A description of the incident or rule violation
• Any supporting evidence available (video, screenshots, timestamps)

8.1.6 — Video evidence is strongly encouraged but is not mandatory for a protest to be reviewed.

8.1.7 — Frivolous or abusive protest submissions may be dismissed and may result in disciplinary action if determined to be intentionally disruptive.

8.2 Protest Review

8.2.1 — Once a protest is submitted, ATMO race officials will review the incident and determine whether an investigation is required.

8.2.2 — Race officials may review:

• Recorded video footage
• Screenshots or telemetry
• Statements from drivers involved
• Statements from witnesses or other racers
• Observations made by race officials during the event

8.2.3 — Officials may request additional clarification or evidence from involved drivers if necessary to determine an accurate ruling.

8.2.4 — If an incident cannot be clearly verified due to insufficient evidence, race officials may dismiss the protest.

8.2.5 — Race officials aim to resolve protests within 48 hours of race completion so that championship standings can be updated in a timely manner.

8.2.6 — Race officials may initiate investigations independently if they observe potential rule violations during an event, even if no formal protest has been submitted.

8.3 Penalty Types

8.3.1 — Race officials may apply the following penalties depending on the severity of the violation.

Warning

8.3.2 — Issued for minor infractions or first-time offenses.

Warnings are recorded but do not affect race results. Multiple warnings may result in escalated penalties.

8.3.3 — Time Penalty

A specified amount of time (typically 5–30 seconds) added to a driver's final race time.

Common uses include:

• Minor false starts
• Minor track cutting
• Unsafe rejoining of the course

8.3.4 — Position Penalty

The driver is moved down a specified number of positions in the final race classification.

Common uses include:

• Gaining unfair advantage through contact
• Repeated track violations
• Ignoring race director instructions

8.3.5 — Points Deduction

A deduction of championship points from the driver or team.

Typically used for:

• Repeat rule violations
• Unsporting conduct
• Major procedural violations

8.3.6 — Disqualification (DQ)

The driver is removed from the race classification and receives zero points for the event.

Disqualification may be issued for:

• Intentional ramming or dangerous driving
• Cheating or exploiting game mechanics
• Severe rule violations

8.3.7 — Race Ban

Suspension from one or more future races.

Race bans may be applied for:

• Extreme unsporting behavior
• Harassment or abuse toward competitors or officials
• Repeated serious rule violations

8.4 Standard Infractions & Guideline Penalties

8.4.1 — The following penalties represent standard guidance. Final decisions remain at the discretion of race officials.

False Start (minor movement before GO)

→ 5 second time penalty

Missing Checkpoint (unintentional)

→ Driver must return to checkpoint or receive time penalty

Track Cutting (minor advantage)

→ Warning or 5 second time penalty

Track Cutting (significant advantage)

→ 10 second time penalty or position penalty

Intentional Contact or Ramming

→ Position penalty or disqualification

Ignoring Race Director Instructions

→ Position penalty or points deduction

Unsporting Behavior

→ Warning up to race ban depending on severity

Late Arrival or No-Show Without Notice

→ 0 points for race and possible future penalties

9 — CODE OF CONDUCT

9.1 General Sporting Conduct

9.1.1 — All participants in System Seven are expected to demonstrate professionalism, respect, and good sportsmanship at all times while participating in league events.

9.1.2 — This Code of Conduct applies to all individuals involved in the championship, including:

• Drivers

• Team members

• Event staff

• Race officials

• Spectators participating in official event communication channels

9.1.3 — Participants must compete within both the written rules and the spirit of fair competition.

9.1.4 — Actions that intentionally disrupt races, undermine competitive fairness, or negatively impact the experience of other participants may result in disciplinary action.

9.2 On-Track Conduct

9.2.1 — Drivers must make reasonable efforts to race cleanly and safely.

9.2.2 — Drivers are expected to:

• Avoid intentional collisions with other racers

• Maintain control of their vehicle at all times

• Respect racing space when competing for position

• Avoid reckless or dangerous driving

9.2.3 — Minor contact may occur during racing; however, intentional use of another vehicle to gain advantage (ramming, blocking, or forcing another racer off track) is prohibited.

9.2.4 — Drivers must rejoin the race safely after leaving the course or recovering from an incident. Unsafe rejoins that interfere with other racers may result in penalties.

9.2.5 — Drivers must comply with all instructions issued by race officials during an event.

9.3 Off-Track Conduct

9.3.1 — Participants must maintain respectful communication with all members of the System Seven community.

9.3.2 — Acceptable conduct includes:

• Respectful communication in voice and text channels

• Constructive feedback regarding races or league operations

• Cooperation with race officials during event procedures

9.3.3 — The following behaviors are prohibited:

• Harassment or personal attacks toward other participants

• Discriminatory language or behavior

• Threats or intimidation

• Repeated disruptive or inflammatory behavior in official channels

9.3.4 — Participants must not intentionally spread false information about race results, competitors, or league officials.

9.4 Fair Play & Competitive Integrity

9.4.1 — All competitors must compete fairly and may not intentionally exploit game mechanics, bugs, or unintended gameplay behavior to gain an unfair advantage.

9.4.2 — Examples of prohibited competitive behavior include:

• Intentional exploitation of game bugs

• Manipulating race results or standings

• Collusion between drivers to influence race outcomes

• Using external tools or exploits that provide an unfair advantage

9.4.3 — Any suspected cheating or exploit abuse will be investigated by race officials and may result in severe penalties.

9.5 Communication Standards

9.5.1 — Communication during official System Seven events must remain professional and respectful.

9.5.2 — Drivers must not engage in abusive language directed toward competitors, officials, or event staff.

9.5.3 — Heated discussions may occur in competitive environments; however, participants are expected to remain respectful and avoid escalating conflicts.

9.5.4 — Race officials may issue warnings or disciplinary actions for inappropriate communication during official events.

9.6 Zero Tolerance Violations

9.6.1 — The following behaviors are considered severe violations of the Code of Conduct and may result in immediate disciplinary action:

• Harassment, discrimination, or hate speech

• Threats or intimidation directed at participants or officials

• Intentional sabotage of races or league operations

• Cheating or exploiting game mechanics for unfair advantage

• Sharing private league communications or administrative decisions without authorization

9.6.2 — Violations of this nature may result in penalties, including:

• Disqualification from the event

• Championship point deductions

• Suspension from future races

• Removal from the System Seven Championship

9.7 Enforcement & Disciplinary Authority

9.7.1 — ATMO race officials and league organizers are responsible for enforcing the System Seven Code of Conduct.

9.7.2 — Officials may investigate potential violations through:

• Direct observation during events

• Incident reports submitted by participants

• Review of recorded footage or communications

9.7.3 — Disciplinary actions will be determined based on the severity of the violation and may include penalties outlined in 8 — Protests & Penalties.

9.7.4 — Repeated misconduct may result in escalated disciplinary action.

9.8 Spirit of Competition

9.8.1 — System Seven is designed to create exciting and competitive racing experiences within the Star Citizen community.

9.8.2 — All participants are encouraged to:

• Race competitively while respecting fellow racers

• Contribute positively to the league environment

• Represent the System Seven community with professionalism

9.8.3 — While competition is taken seriously, maintaining a welcoming and enjoyable environment for all participants remains a core principle of the championship.

END OF RULES