---
# System prepended metadata

title: Acheron Sovereign Code

---

# Acheron Sovereign Code
## Preamble
Enacted under the authority of the **Acheron Sovereign Code**, this Codex serves as the supreme legal framework of **IMR–Acheron**. It governs civil order, criminal conduct, institutional protocol, and sovereign operations within the bounds of its District Domes.

It defines the scope of authority, establishes the structure of governance, and safeguards justice through Compact-aligned doctrine and procedural law.
## Table of Titles
| Title No. | Title Name                             | Scope |
|-----------|----------------------------------------|-------|
| 1         | General Provisions                     | Definitions, formatting, jurisdiction, statutory logic |
| 2         | The Red Council                        | Legislative authority, procedures, and credentialing |
| 3         | The SiInstallationte Director                      | Executive power, directives, succession |
| 4         | Executive Ministries & Personnel Administration | Departments, appointments, compensation, structure |
| 5         | Internal Security & Breach Oversight   | ISB, counterintelligence, procedural audits |
| 6         | Criminal Offenses & Systemic Breach  | Classifications, penalties, justice triggers |
| 7         | The Tribunal & Adjudication Protocols  | Judiciary structure, hearings, appeals |
| 8         | Electoral Protocols and Referenda | Council elections, voting eligibility, candidacy, referenda procedures |
# Title 1 — General Provisions
## Chapter 1 — Rules of Construction
### §1. Number and Identity
Unless context dictates otherwise, singular references shall be interpreted to include the plural, and vice versa. All references to individuals include authorized personnel, recognized artificial entities, and identity modifications formally registered under Compact authority.
### §2. Language of Obligation and Discretion
- The term *“shall”* indicates a mandatory legal requirement.
- *“May”* denotes discretionary authority within administrative scope.
- *“Must”* applies exclusively to non-negotiable requirements involving public safety, legal compliance, or operational containment.
### §3. Timekeeping and Record Format
All official dates and durations adhere to the **Darian Calendar Standard**, consisting of 24 named months per Martian year (668.6 sols). A "sol" refers to a full Martian rotation. Records follow the format: `[Month] [Sol], [Year] A.M.E.` (Acheron Martian Era).
### §3a. Era Anchor and Temporal Jurisdiction
The **Acheron Martian Era (A.M.E.)** begins at the ratification of the Sovereign Code and activation of Dome Primus, designated as **Sol 0, Sagittarius 1, Year 0 A.M.E.** All legal timelines, procedural mandates, and jurisdictional records are computed from this epoch unless otherwise specified.

Time-based provisions, including breach eligibility windows, sentence durations, and archival minimums, are calculated in **sols**, as defined by the Darian Standard.
### §4. Interpretive Presumptions
In the absence of explicit direction, any ambiguity shall be resolved in favor of maintaining administrative continuity and Compact governance. Where needed, precedent issued by the Red Council or adjudication by the Tribunal shall control.
### §5. Valid Record Forms
Where this Code requires a signature, filing, or notice, it may be satisfied through:
- Biometric validation
- Encrypted digital certification
- Internal system log entry
- Tribunal-verified procedural documentation
### §6. Standard Definitions
Unless otherwise defined in this or another Title:
- “Agent” refers to any officially registered personnel acting under Compact authority.
- “Directive” means any lawful order—verbal, written, or electronic—issued and authenticated by a recognized official.
- “Facility” refers to any recognized Compact-controlled location, including planetary installations, sector hubs, or digitally administered operational systems.
- “Law” includes all codified Titles, applicable directives, and binding judicial opinions currently in force under Compact administration.
### §7. Codified Supremacy
This Code supersedes all prior regulations, provisional rules, or internal policies inconsistent with its content, unless expressly retained by Tribunal ruling or through approved interagency agreement.
## Chapter 2 — Legislative Instruments: Enactment, Repeal, and Validation
### §8. Law Enactment Requirements
A statute is binding within Compact jurisdiction only if:
1. Ratified by a Red Council quorum
2. Authenticated by the Site Director or Tribunal Ethics Council
3. Assigned a formal Title–Chapter–Section designation and registered in the Acheron Sovereign Code
### §9. Emergency Executive Directives
During extraordinary circumstances, the Site Director may issue provisional directives valid for up to 40 sols. Each directive must be logged in the Sovereign Ledger and reviewed by either the Tribunal or Red Council prior to expiration.
### §10. Legal Instrument Requirements
All binding instruments must contain:
- A Codex Classification Identifier (CCI)
- Timestamp compliant with UMTP calendar format
- Authorizing signature or digital credential
- Entry in the Sovereign Ledger
### §11. Repeal Guidelines
No statute is considered repealed unless explicitly revoked. Repealed materials are retained under *Nullified Classification* for legal audit and reference.
### §12. Amendment Protocols
All amendments must:
- Reference the applicable CCI
- Log the revision date in the Sovereign Ledger
- Identify modifications using standardized section labeling (e.g., §302(a), §302-1)

Editorial corrections require official logging but do not require Council re-ratification.
### §13. Finalization of Statutes
No statute becomes enforceable until it receives verification from:
- The Site Director,
- A Red Council quorum, or
- The Tribunal Ethics Council

Attested statutes take immediate effect upon registration unless specified otherwise.

> **Notice:** Once enacted, all provisions remain binding until repealed or superseded through formal procedure.
### §14. Citation Format
References to this Code shall use: *ACC Title–Chapter–Section* (e.g., ACC 1–2–105). Subsections use lowercase letters and numerals.

All orders or rulings shall be cited by CCI and issue date (e.g., CCI–TRB–Sag-17–43). All official submissions—including legal filings, disciplinary actions, and rulings—must use citation formats consistent with the Sovereign Ledger Index.
# Title 2 — The Red Council
## Chapter 1 — Election and Credentialing of Councilors
### §1. Structure of the Red Council
The **Red Council** is the supreme bicameral legislative body of the Acheron Compact, composed of:
- The **Vox Chamber**, representing operational personnel assigned to Compact divisions; delegate ratios are based on verified clearance-level population
- The **Obsidian Circle**, representing recognized chartered jurisdictions, with equal representation per authorized entity

Each chamber governs its internal rules under Codex authority.
### §2. Councilor Eligibility
To serve in either chamber, an individual must:
- Hold a valid **Red Council Credential (RCC)** issued by the Codex Archive
- Possess Clearance Level III or higher
- Be endorsed by a recognized division (Vox) or jurisdiction (Obsidian) at least 30 sols prior to credential validation

Disqualification by Tribunal ruling supersedes any credential issuance.
### §3. Credential Issuance and Verification
Confirmed appointments require:
- Issuance of a personalized RCC
- Entry into the **Council Ledger of Credentialed Delegates (CLCD)**
- Timestamped validation using official Codex attestation

Expired RCCs automatically revoke access to legislative systems and chamber proceedings unless renewed.
### §4. Vox Chamber Elections
Each operational division conducts elections every 720 sols, ensuring:
- Open access and procedural fairness for personnel
- Delegate allocation based on verified division size
- Results formally recorded in the **Election Log Archive (ELA)**
### §5. Obsidian Circle Appointments
Each recognized jurisdiction must ensure:
- Endorsement by at least three authorized administrators or committee members
- Appointment registered in the **Faction Appointment Record (FAR)**
- All contested appointments are subject to Tribunal review
### §6. Interim Appointments
If a vacancy occurs:
- The affected entity may issue an **Interim Credential** (valid for up to 180 sols)
- Details are recorded in the Codex Archive
- Interim Councilors may not introduce amendments or preside over chamber sessions
### §7. Disqualification Conditions
Councilors may be disqualified due to:
- Breach conviction (Class III or higher under Codex Title 6)
- Formal sanction by the Office of Planetary Integrity (OPI)
- Tampering with credential verification data

All disqualifications are listed in the **Disqualification Index (DI)**.
### §8. Credential Dispute Resolution
The Judicial Panel may resolve credential disputes if:
- Three Councilors file a joint petition
- A recognized division, jurisdiction, or registered clerk submits a formal challenge
- Credential anomalies are flagged by the Codex Archive

Tribunal rulings are final in such cases.
### §9. Codex Compliance
Credentialing records must be:
- Indexed in the **Codex Civic Ledger**
- Cross-referenced with vote history and delegate status
- Retained for ≥1440 sols in the **Directive Vault**
## Chapter 2 — Codex Structure and Procedural Authority
### §10. Codex Structure
The Codex is divided into numbered **Titles**, each subdivided into **Chapters** and **Sections (§)**, based on:
- Thematic domain (e.g., governance, enforcement, civil systems)
- Legislative continuity and jurisdictional application
- Legal hierarchy of Executive, Legislative, and Judicial issuances

All pending proposals remain in the **Codex Deliberation Log** until ratified.
### §11. Chamber Autonomy
Each chamber maintains internal authority over:
- Rules of debate, committee structure, and voting thresholds
- Formation of issue-specific review panels
- Document formatting and procedural naming conventions

Cross-chamber override requires joint resolution or Tribunal directive.
### §12. Codex Enactment Requirements
To enact updates, the following are required:
1. Passage by both chambers (unless granted expedited exemption)
2. Formatting and document attestation by the **Codifier General**
3. Formal registration with the Codex Archive

Comprehensive revisions may be filed as a **Title Enactment Package (TEP)**.
### §13. Joint Committee Operations
Joint Committees may be convened to:
- Reconcile discrepancies between chamber versions
- Conduct multi-sector inquiries
- Propose updates to Codex formatting standards

All committees must be recorded in the **Convergence Register**.
### §14. Role of the Codifier General
The **Codifier General** is responsible for:
- Maintaining Codex structural formatting
- Identifying procedural inconsistencies or technical errors
- Coordinating with the Archive Systems team on Codex integration

The Codifier may issue **Procedural Advisory Statements (PAS)** but holds no legislative vote.
### §15. Presiding Officer Duties
Each chamber selects a presiding officer responsible for:
- Maintaining order and attendance records
- Routing proposals to relevant committees
- Ruling on **Procedural Order Requests (PORs)** (subject to appeal)
### §16. Codex Amendment Process
Codex updates may be enacted by:
- Passage of an Amendment Act with specific section reference
- Verification of formatting by the Codifier General
- Logging in the **Codex Amendment Ledger (CAL)**

All historical versions are maintained in the **Living Archive (LCA)**.
### §17. Archival Continuity
The Codex Archive ensures:
- Accurate integration of approved content
- Version control and documented rollback capability
- Access visibility is maintained through the **Codex Archive Portal (CAP)**
## Chapter 3 — Councilor Entitlements and System Access
### §18. Entitlements and Privileges
Councilor compensation and procedural privileges shall be:
- Determined through recorded Council resolution
- Consistent across terms, with standardized assignments for procedural roles
- Subject to periodic review by the Codex Secretariat
### §19. System Access
Councilors may request:
- Access to Codex systems, committee dockets, and communication logs
- Internal routing tools for proposal tracking
- Use of the **Sovereign Delegate Portal (SDP)** for administrative coordination

Misuse or breach of usage terms may result in privilege suspension under §22.
### §20. Leave and Representation
Councilors may:
- Submit formal leave notices (maximum 60 sols per service cycle)
- Assign proxy delegates for non-voting procedural duties
- File post-breach rehabilitation requests with Tribunal assistance

All actions are recorded in the **Councilor Continuity Record (CCR2)**.
### §21. Suspension of Access or Privileges
Entitlements may be suspended due to:
- Tribunal-issued sanction or ethics violation
- Unauthorized use of secure systems
- Unexcused absence exceeding 120 sols

Status is reviewed every 60 sols via the **Entitlement Audit Register (EAR)**.
### §22. Transparency and Public Recordkeeping
The Codex Archive shall maintain:
- A public-facing **Councilor Access Log**
- Participation records linked to proposal sponsorship and committee service
- Verification hashes for all system revisions and documentation changes
## Chapter 4 — Codex Offices and Support Personnel
### §24. Administrative Offices
The Red Council shall authorize and maintain the following support offices:
- **Codifier General**
- **Codex Archive and Records Division**
- **Clerk of the Red Council**
- **Office of Procedural Integrity (OPI)**
- **Councilor Services Directorate (CSD)**

Additional offices may be established via Council resolution and registered in the **Codex Institutional Register (CIR)**.
### §25. Codex Archive and Records Division
The Archive is responsible for:
- Preserving all enacted Codex laws, amendments, and judicial rulings
- Maintaining version tracking and audit metadata
- Providing public access to authorized records
- Securing original records in the **Directive Vault**

The Archive operates with autonomy and may issue nonbinding procedural assessments.
### §26. Clerk of the Red Council
The Clerk functions as registrar for both chambers and is responsible for:
- Logging activity in the **Procedural Transcript Ledger (PTL)**
- Issuing legislative notices and credential records
- Verifying attendance and quorum
- Certifying Red Council Credentials (RCC) and corresponding entries

Up to three deputy registrars may be appointed under Council authorization.
### §27. Personnel and Staff Functions
Each chamber may appoint support personnel including:
- Legislative and procedural analysts
- Records management officers
- Documentation specialists
- Liaison staff to internal and external organizations

All appointments must be cleared through the CSD and are subject to Codex ethics policy.
### §28. Orientation and Training
Newly credentialed personnel must complete a **Codex Orientation Program** within 30 sols, covering:
- Systems access and compliance protocols
- Records management and procedural standards
- Ethics and operational conduct training

Completion is recorded in the **Personnel Integration Register (PIR)**.
### §29. Access and Clearance Levels
Codex access is assigned as follows:
- **Level I** — Public and view-only access
- **Level II** — Authorized formatting and archival access
- **Level III** — Full procedural rights for credentialed Councilors
- **Level IV** — Restricted access to judicial and sealed documentation

Clearance modifications require Tribunal approval or formal disciplinary resolution.
### §30. Disciplinary Enforcement
Codex personnel are subject to disciplinary action for:
- Data falsification or unauthorized credential alteration
- Interference with procedural enforcement or concealment of records
- Abuse of access privileges

Penalties may include dismissal, credential revocation, and entry into the **Personnel Conduct Index (PCI)**.
### §31. Continuity of Records
All Codex-related activity must be:
- Logged in the **Institutional Continuity Ledger (ICL)**
- Indexed by role and organizational function
- Retained for ≥1440 sols from last verified action
## Chapter 5 — Archive Management and Record Doctrine
### §32. Archive Function
The Codex Archive functions as the authenticated repository for:
- Codified law and active amendments
- Procedural version history
- Council deliberation records
### §33. Directive Vault
The **Directive Vault** maintains:
- Immutable, secured legislation files
- Signature metadata and official certification
- Reinstatement versions for post-crisis restoration

Access is limited to Level III personnel and above.
### §34. Version Control
Each amendment generates:
- A unique **Codex Version Identifier (CVI)**
- Timestamped entry by the Codifier General
- Change log in the **Codex Amendment Register (CAR)**

All modification cycles must follow version control protocols.
### §35. Public Access and Transparency
The Archive provides:
- Open access to verified records for Level I users
- Indexed search functions and chronological filters
- Enactment histories viewable by section and revision

Public commentary is permitted but nonbinding.
### §36. Judicial Synchronization
All Tribunal rulings and legal opinions must be:
- Logged using the **Judicial Integration Protocol (JIP)**
- Indexed by jurisdiction and ruling scope
- Made accessible to qualified personnel under Codex audit

Rulings remain in force unless overturned by appeal.
### §37. Integrity Monitoring
The Archive must implement:
- Validation systems to detect record tampering
- Scheduled checksum verification every 10 sols
- Alert and lockout triggers for data integrity disruptions

All incidents must be reported to OPI and Tribunal within 12 sols.
### §38. Legislative Indexing
The Archive shall maintain:
- A continuously updated **Codex Directive Index**
- Impact summaries by Title, Section, and domain
- Playback records for internal review and traceability

Retention minimum: 2880 sols unless otherwise ordered.
## Chapter 6 — Council Procedures and Investigatory Powers
### §39. Internal Rules
Each chamber shall adopt official **Rules of Order** covering:
- Legislative calendar and voting criteria
- Conduct guidelines and recognition standards
- Amendment proposal and routing procedures

All Rules of Order must be filed in the **Codex Procedural Annex (CPA)**.
### §40. Committees and Panels
The Red Council may establish standing or ad hoc Committees to:
- Review legislative proposals or compliance concerns
- Monitor operational offices
- Investigate procedural failures

Committee records are maintained in the **Procedural Transcript Ledger (PTL)**.
### §41. Hearings and Testimony
Committees may convene formal Hearings to:
- Evaluate system-level failures or security incidents
- Question Councilors, personnel, or support staff
- Recommend enforcement actions or protocol changes

Public access is enabled unless restricted by formal chamber vote.
### §42. Investigative Authority
Committees may issue:
- **Procedural Orders** with enforceable status
- Subpoenas or witness appearance notices
- Requests for official records and administrative reports

Noncompliance is referred for violation review under Title 6.
### §43. Procedural Contempt
Individuals may be held in contempt for:
- Willfully obstructing Council process
- Altering, deleting, or withholding records
- Refusing a valid appearance order

All sanctions must be reviewed by the Tribunal.
### §44. Final Investigative Records
At the conclusion of proceedings:
- A **Codex Investigation Record (CIR)** shall be completed
- Summary and findings archived with proposal ID
- Legislative response requires formal enactment
### §45. Procedural Transparency
The Archive and Codifier General shall ensure:
- Full indexing of committee and chamber actions
- Access to procedural history and enacted resolutions
- Restricted access may only be imposed by two-thirds vote citing verifiable security risk
## Chapter 7 — Investigations and Inquiries
### §46. Investigative Authority
Committees or chambers may initiate inquiries into:
- Breach events impacting personnel systems or procedural infrastructure
- Factional misconduct related to Codex operations
- Credential fraud, document tampering, or systems anomalies

All inquiries must be logged in the **Inquiry Docket (IDK)**.
### §47. Preliminary Inquiry Process
An investigation begins upon:
- Filing a **Notice of Intent to Investigate (NII)**
- Assignment of a lead investigator or panel
- Notification to relevant offices, affiliates, or administrative zones

Informal reviews may occur, but formal investigatory powers under §48 require chamber authorization.
### §48. Investigative Powers
Authorized investigations may:
- Collect systems logs, protocol records, and breach indicators
- Secure testimony under procedural oath (per §42)
- Temporarily seize implicated records or assets under custodial control

Tribunal warrants may expand investigatory jurisdiction where appropriate.
### §49. Recommendations and Referrals
Where violations are substantiated, a Committee may:
- Refer findings to the Judicial Panel
- Recommend legislative amendments or enforcement actions
- Issue censure notices or suspend access credentials for involved personnel

All decisions are filed in the **Procedural Response Register (PRR)**.
### §50. Conclusion and Archival
Upon completion of an inquiry:
- A vote to formally close the investigation is conducted
- A **Final Procedural Report (FPR)** is issued
- Records are archived in the **Codex Oversight Archive** for a minimum of 720 sols
## Chapter 8 — Codex Counsel Bureau
### §51. Function and Authority
The **Codex Counsel Bureau (CCB)** serves as a nonpartisan technical office. It is responsible for:
- Interpreting Codex language and precedent
- Supporting legislative drafting and procedural review
- Maintaining structural consistency in coordination with the Codifier General

The CCB holds no voting authority.
### §52. Available Services
Upon Councilor request, the CCB may provide:
- Drafting templates and procedural formatting guidance
- Amendment review for Codex conformity
- Legal memos clarifying ambiguous Codex language

All guidance is archived as **Doctrinal Counsel Notes (DCNs)**.
### §53. Confidentiality
CCB consultations are:
- Protected under Clearance Level III
- Summarized within the **Counsel Integrity Ledger (CIL)**
- Not disclosed without consent or Tribunal order
### §54. Coordination Protocols
The CCB shall work with the Codifier General to:
- Maintain consistent formatting and terminology
- Resolve drafting disputes or conflicts
- Prevent duplicated or contradictory procedural language
### §55. Public Reference and Education
The CCB shall periodically publish:
- **Redacted Precedent Bundles (RPBs)** for instructional use
- Digest summaries of recent Codex activity
- Training materials for new Councilors and analysts

These resources are available to Tier I access.
## Chapter 9 — Recognition and Award Programs
### §62. Program Purpose
The **Recognition and Achievement Program (RAP)** honors individuals for contributions to Compact service, procedural excellence, and cross-sector innovation.
### §63. Recognition Board Composition
The **Recognition Board (RB)** shall include:
- Two Vox Chamber Councilors
- Two Obsidian Circle Councilors
- One appointed Tribunal officer

The Board reviews nominations and confirms honors.
### §64. Award Categories
Eligible distinctions include:
- **Iron Distinction** — outstanding procedural execution
- **Obsidian Citation** — contributions to Codex or doctrinal advancement
- **Crimson Response Mark** — exceptional response to crisis or breach
- **Astral Service Emblem** — advancement of systems architecture or public service

Award post-nominals may be conferred upon confirmation.
### §65. Nomination Protocols
Nominations may be submitted by:
- Credentialed Councilors (Tier III+)
- Codex offices by internal memorandum
- Authorized faction leadership with clearance

Submissions must document institutional or procedural merit.
### §66. Evaluation Criteria
Nominations are reviewed every 360 sols based on:
- Measurable institutional benefit
- Duration and scope of contribution
- Relevance to public or organizational integrity

A minimum of four affirmative votes is required to confer an award.
### §67. Documentation and Recognition
Confirmed honors shall trigger:
- Entry in the **Recognition Register (RR)**
- Optional chamber commendation
- Public archive listing with Tier I visibility
### §68. Award Revocation
Awards may be rescinded if:
- A unanimous vote of the RB is recorded
- The Tribunal affirms breach or fraudulent credential

All revocations are logged in the **Recognition Integrity Log (RIL)**.
### §69. Public Records
The Archive maintains searchable records for:
- Award recipients and historical context
- Supporting documentation
- Nomination and eligibility guidance
## Chapter 10 — Integrity and Grievance Framework
### §78. Institutional Purpose
The Compact maintains a grievance system to ensure fair process, personnel safeguards, and integrity standards across Codex operations.
### §79. Office of Procedural Integrity (OPI)
The **OPI** operates independently to:
- Investigate misconduct filings
- Resolve procedural disputes
- Enforce outcomes through administrative sanctions
### §80. Access to Grievance Procedures
All personnel may file **Grievance Submissions (GS)** through secure channels. Anonymity is permitted when requested.
### §81. Workplace Safety and Access
All facilities governed by Codex must:
- Comply with operational safety protocols
- Meet accessibility and accommodation requirements
- Uphold nondiscrimination policies
### §82. Whistleblower Protections
Individuals reporting verified violations are entitled to:
- Shielded identity and procedural anonymity
- Protection from retaliation
- Award consideration under §64
### §83. Tribunal Oversight
The Tribunal may:
- Hear OPI-related appeals
- Confirm or overturn findings
- Enforce additional measures under ACC Title 6
### §84. Recordkeeping
All procedural findings and decisions must be:
- Indexed in the **Procedural Annex (PA)**
- Retained in public or restricted view for ≥1440 sols
# Title 3 — The I Director
## Chapter 1 — Elections, Succession, and Emergency Transition
### §1. Election Cycle
The **Site Director** shall be selected through a Compact-wide election every **720 sols**, unless deferred by Tribunal ruling during planetary emergency.
If no certified candidates are available, the election is delayed **60 sols**, and an Interim Director may be appointed under §9.
### §2. Eligibility Criteria
Candidates must:
- Possess Tier IV clearance or receive formal Tribunal exemption
- Be endorsed by at least three recognized factions or sovereign jurisdictions
- Demonstrate operational conduct stability for ≥360 sols prior to nomination
- Have no active breach judgments at the time of filing
### §3. Nomination Procedure
To qualify for candidacy, individuals must submit a **Declaration of Executive Intent (DEI)**:
- Filed ≥60 sols prior to official voting cycle
- Verified by the **Compact Electoral Office (CEO)**
- Indexed in the **Directorate Candidacy Ledger (DCL)**
### §4. Voting System
Votes are cast through the **Red Council-certified Electoral Relay System**, ensuring:
- One verified ballot per eligible participant
- Secure transmission overseen by the ISB
- Vote tabulation certified by the **CEO**
### §5. Vote Weighting and Grid Allocation
Factions and jurisdictions receive adjusted voting weights according to:
- Active engagement and turnout rates
- Sector operational reliability
- Tribunal audit compliance scores

If integrity of any registered sovereign dome or jurisdictional division is compromised, the Red Council may implement a **raw-vote override protocol**.
### §6. Transition of Office
Upon certification:
- The outgoing Director must transfer authority within **5 sols**
- A formal command handover is conducted with Codex observers present
- Active policies must be reauthorized or retired by the incoming Director
### §7. Vacancy Triggers
The role is declared vacant upon:
- Voluntary resignation (see §8)
- Removal by Tribunal under Compact law
- Confirmation of death, incapacity, or breach disqualification
### §8. Resignation Protocol
To resign, the Director must:
- Submit a formal notice to the Red Council
- Register resignation with the Codex Archive and Tribunal
- Complete a secure access termination process
### §9. Interim Appointment
If vacancy occurs:
- The **Deputy Director of Record** named in the **Tier Succession Chain (TSC)** serves for up to **60 sols**
- The Tribunal may convene a **Compact Emergency Forum** to confirm or replace interim leadership
- In the absence of a deputy, the Red Council appoints a **Provisional Director** via majority vote
### §10. Emergency Succession
If conditions prevent standard process:
- The **Sovereign Succession Protocol (SSP)** is activated
- A Tribunal-appointed caretaker assumes authority using emergency credentials
- All appointments logged in the **Continuity Vault**
- A new election must be called within **180 sols**
### §11. Election Disputes
Certification disputes may be filed as a **Codex Electoral Challenge (CEC)**:
- Must be submitted ≤7 sols after certification
- Tribunal must rule within 30 sols
- Contested policies are held in suspension during arbitration
### §12. Codex Compliance
All Director elections, transfers, and succession events must be:
- Logged in the **Executive Succession Ledger (ESL)**
- Cross-referenced with factional endorsements and personnel records
- Archived for ≥2880 sols in the **Directive Vault**
## Chapter 2 — Office and Compensation of the Site Director
### §13. Office Location and Security
The Director’s office is housed in the **Executive Command Office** in **Dome Primus**, accessible via Tier IV credentials.  
All official communications must bear the authenticated **Directorate Seal** and be logged in the **Directive Vault**.
### §14. Compensation Structure
The Director shall receive a designated **Codex Compensation Package (CCP)**:
- Based on standardized service classification
- Reviewed every 360 sols by authorized Codex administrators
- Includes procedural privileges and executive accommodations
### §15. Travel and Communication Access
The Director is granted:
- Priority access to all secure intra-facility corridors
- Direct connection to facility-wide communication systems
- Secure transmission via the **Executive Communication Channel (ECC)**
### §16. Continuity Office
A dedicated **Emergency Command Locus (ECL)** shall be:
- Maintained for leadership continuity during crisis
- Synced to Codex procedural systems
- Staffed by a standby executive operations team on rotation
### §17. Leave and Suspension
To take leave:
- The Director must file a **Continuity Notification** with the Tribunal
- Delegate duties to the Deputy Director (for ≤30 sols)
- Log absence in the **Executive Continuity Index (ECI)**

Suspension may occur only by:
- Tribunal decision
- Voluntary withdrawal ratified by Red Council vote
### §18. Conclusion of Term
Upon conclusion:
- Credentials and command access are formally retired
- All records are archived in accordance with Directive retention policy
- Optional honorary recognition may be conferred by Red Council resolution
## Chapter 3 — Delegation of Executive Authority
### §19. Delegated Powers
The Director may assign operational duties to:
- Deputy Directors
- Departmental Overseers (see Title 4)
- Appointed Agents with a clearly defined scope

All delegations must be:
- Logged in the **Executive Delegation Index (EDI)**
- Subject to regular review and revocation terms
- Credentialed using a verified digital authorization
### §20. Authority Limits
Delegated agents may not:
- Issue system-wide directives without explicit authority
- Override Tribunal rulings or enact emergency protocols
- Assume control over sovereign facilities without interagency coordination

Violations result in immediate revocation and disciplinary review.
### §21. Revocation Process
Delegated authority may be revoked at any time.  
All revocations must be:
- Recorded in the **Directive Annulment Record (DAR)**
- Reflected in the EDI within 24 sols
- Communicated to affected parties with updated clearance profiles
### §22. Succession Plan Record
A standing **Executive Succession Directive (ESD)** shall:
- List official successors in order of assumption
- Define authorized zones and transitional limits
- Activate automatically under pre-defined criteria

The ESD is reviewed biannually and digitally re-certified by Codex officials.
## Chapter 4 — Rights and Protections for Directorate Personnel
### §23. Scope
Applies to all personnel employed within the Directorate, including:
- Deputy Directors and senior advisors
- Executive office staff and support teams
- Embedded specialists under Codex operational designation

Rights remain in force unless formally suspended by Tribunal ruling.
### §24. Personnel Protections
Directorate personnel are entitled to:
- A safe and harassment-free workplace
- Equal protection regardless of factional background
- Access to post-incident recovery programs following exposure to high-clearance operations

Violations are reported to the **Office of Procedural Integrity (OPI)**.
### §25. Whistleblower Protections
Personnel who report:
- Codex violations, fraud, or systemic coercion

are entitled to protection from retaliation.
Anonymous disclosures may be submitted via the **Sovereign Integrity Channel (SIC)**.
### §26. Grievance Procedures
Personnel may file complaints through:
- The **Executive Accountability Channel (EAC)**
- Initial review by OPI
- Right to further appeal through the Codex Tribunal

Response required within 7 sols; formal resolution issued within 60.
### §27. Codex Compliance
All grievances, protections, and rulings under this Chapter must be:
- Indexed in the **Directorate Rights Ledger (DRL)**
- Cross-linked with associated personnel logs
- Archived for ≥1440 sols or until cleared by ruling
# Title 4 — Executive Ministries and Personnel Administration
## Chapter 1 — Ministry Formation and Structure
### §1. Establishment of Ministries
The Site Director may authorize Ministries to execute duties under Compact law. Each Ministry must define its operational jurisdiction and register in the **Ministry Ledger (ML)**. Ministries operate under Codex authority.
### §2. Charter Requirements
A Ministry charter shall include:
- Clearly defined functional domain (e.g., logistics, biosphere, education)
- Assigned Minister of Record
- Designated access permissions for relevant administrative systems

All charters are archived in the **Directive Vault**.
### §3. Ministerial Powers
Ministers are empowered to:
- Issue administrative orders within their assigned jurisdiction
- Direct personnel within their organizational structure
- Propose amendments to Codex policy within their scope

Orders may not override Codex law or Tribunal directive.
### §4. Oversight Procedures
All Ministries are subject to:
- Procedural audits per Title 5
- Compliance evaluations conducted by the Judicial Panel
- Review upon formal request by the Site Director or Tribunal
### §5. Continuity and Termination
A Ministry remains active unless:
- Dissolved through a Sovereign Directive
- Terminated by Tribunal ruling
- Reorganized via Codex amendment
### §6. Subunits and Special Divisions
Ministries may establish subordinate units, working groups, or task forces. All units must be recorded in the **Ministry Annex Register (MAR)**.
### §7. Personnel Access
Ministry personnel are granted:
- Tier II clearance or Tier III with authorization
- Credentialed system access relevant to their assigned duties
- Institutional tools and platforms appropriate to role
### §8. Coordination and Inter-Ministry Operations
All Ministries must:
- Adhere to standardized communication protocols
- Use the **Ministerial Concord Forum (MCF)** to resolve conflicts
- Submit cooperative operation reports quarterly to the Site Director
### §9. Emergency Operations
During a certified emergency:
- Ministries may activate the **Compact Emergency Protocol (CEP)**
- Request temporary clearance extensions or access scope changes
- Submit post-event justification within 10 sols of activation
### §10. Activity Logging
Ministerial actions must be:
- Logged in the **Operational Continuity Register (OCR)**
- Cross-indexed with procedural performance assessments
- Archived for ≥1440 sols or until formally retired
## Chapter 2 — Personnel Appointments and Tier Structure
### §11. Personnel Classification
All Compact personnel are classified according to role and access tier:
- **Tier I** — General Staff
- **Tier II** — Technical and Analytical Staff
- **Tier III** — Command and Supervisory Staff
- **Tier IV** — Senior Executive Authority

Access level determines procedural authority and systems access.
### §12. Appointment Authority
Ministers may appoint individuals up to Tier III. Tier IV appointments require:
- Site Director authorization
- Entry in the **Sovereign Personnel Index (SPI)**
- Confirmation with authorized digital signature
### §13. Hiring Requirements
Prospective personnel must:
- Pass Internal Security Bureau (ISB) background verification
- Submit a **Personnel Induction Record (PIR)**
- Complete system access orientation and compatibility review

Faction affiliation is not grounds for exclusion unless in conflict with Codex primacy.
### §14. Orientation and Training
All new personnel are provided:
- Standard role-based orientation documentation
- Onboarding training not exceeding 15 sols
- Access to the **Codex Operations Primer (COP)**

Higher tiers may require supplemental technical certification.
### §15. Advancement Criteria
Tier advancement requires:
- Direct supervisor endorsement
- Merit and procedural compliance review
- Verification by Personnel Oversight Council

Tier III and above require formal credential confirmation.
### §16. Inter-Ministry Transfers
Transfers must be:
- Jointly approved by originating and receiving Ministries
- Recorded in the **Personnel Transfer Register (PTR)**
- Reviewed over a 360-sol performance evaluation period

Performance anomalies alone do not justify inter-Ministry reassignment.
### §17. Disciplinary Actions
Personnel may be subject to suspension or termination for:
- Violation of Codex statutes
- Professional misconduct or repeated procedural noncompliance
- Compromise of systems access or institutional data

Termination requires submission of a **Directive Termination Form (DTF)** and SPI update within 24 sols.
### §18. Appeals Process
Tier I–III personnel may appeal administrative actions through:
- The **Personnel Grievance Panel (PGP)**
- Final review by the **Office of Procedural Integrity (OPI)** under Title 7

Appeals must be filed within 10 sols of notice issuance.
### §19. Recordkeeping Requirements
All personnel actions must be:
- Logged in the **Unified Personnel Codex (UPC)**
- Cross-synced with relevant Ministry systems
- Archived ≥1440 sols
## Chapter 3 — Compensation and Benefits
### §20. Compensation Tiers
Base compensation is structured as:
- Tier I — Foundational Level
- Tier II — Technical or Performance-Based Stipend
- Tier III — Operational Leadership Allocation
- Tier IV — Executive Designation Rate

All compensation follows the established **Codex Compensation Rate (CCR)** schedule and is reviewed at least once every 360 sols.
### §21. Personnel Support Allocations
Personnel may receive:
- Housing allowances
- Equipment or role-based resource support
- Uniform issue and sector mobility allocations

Tracked via the **Personnel Allocation Ledger (PAL)**.
### §22. Incentive Eligibility
Performance-based incentives may be awarded for:
- Completion of high-priority assignments
- Notable service recognized under the Codex Recognition Program (see Title 2, §64)
- Assignment to remote or high-risk domains

Incentives must be authorized by the relevant Ministry and reported to Codex personnel systems.
### §23. Assignment-Based Provisions
Personnel stationed in remote or restricted-access areas may be eligible for:
- Nutritional and logistical support packages
- Stabilization assistance for prolonged deployments
- Emergency contingency equipment

Provision is coordinated by the designated personnel support branch.
### §24. Leave Accrual
Personnel accrue leave as follows:
- 1 sol of leave per 30 sols of active duty
- Additional leave for verified occupational recovery
- Maximum rollover capped at 90 sols

Leave status is tracked through the **Personnel Recalibration Record (PRR)**.
### §25. Hazard-Based Compensation
Increased compensation applies for:
- High-risk assignments (×1.5 multiplier)
- Continuous operations in breach-adjacent zones or secure facility protection roles (×2.0)
- Other hazard zones classified under Title 5 jurisdiction

Risk designations are verified by the Tribunal where applicable.
### §26. Retirement Benefits
Personnel with ≥1440 sols of certified service are eligible for:
- Pension in alignment with final Tier status
- Administrative continuation benefits as authorized
- Registration in the **Personnel Retirement Index (PRI)**
### §27. Compensation Records
All compensation and entitlements must be:
- Logged in the **Unified Personnel Codex (UPC)**
- Subject to audit by OPI and Tribunal upon request
- Archived ≥2880 sols
# Title 5 — Internal Security and Breach Oversight
## Chapter 1 — Internal Security Bureau (ISB)
### §1. Establishment
The **Internal Security Bureau (ISB)** functions as a sovereign enforcement agency under Codex authority. It is responsible for safeguarding Compact systems, enforcing breach containment, and maintaining procedural integrity.
### §2. Jurisdiction
ISB is authorized to:
- Conduct security stress testing and system surveillance
- Perform compliance audits on Compact divisions and Ministries
- Enforce data seizure and personnel suspensions upon authorization
### §3. Bureau Director
The ISB is overseen by a Director who:
- Is appointed by the Site Director and confirmed by the Red Council
- Serves a 360-sol term, renewable once
- Maintains Tier IV clearance and operational accreditation
- May issue enforceable Bureau Orders
### §4. Bureau Structure
ISB divisions include:
- **Counterintelligence Division (CID)**
- **Containment Response Unit (CRU)**
- **Procedural Audit Division (PAD)**

All actions must be logged in the **Bureau Oversight Index (BOI)**.
### §5. Operational Monitoring
ISB may implement:
- Monitoring protocols in high-risk operational sectors
- Real-time anomaly detection and alert systems
- Auto-lockdown triggers using secured override codes

All activity must be recorded in the **System Risk Log (SRL)**.
### §6. Emergency Authority
During declared emergency events, ISB may:
- Activate the **Codex Containment Clause (CCC)**
- Restrict or suspend access privileges
- Detain individuals or isolate systems pending investigation

Actions must be archived in the **Crisis Invocation Ledger (CIL)**.
### §7. Oversight and Review
ISB operations are subject to:
- Committee oversight every 180 sols
- Tribunal review under Title 7 provisions
### §8. Personnel Standards
All ISB personnel must:
- Hold Tier III or IV clearance
- Complete annual loyalty and cognitive resilience review
- Disclose all external affiliations

Violations result in immediate review by a disciplinary board.
### §9. Operational Logging
All ISB enforcement and administrative activity must be:
- Indexed in the BOI and CIL
- Submitted to the Codex Archive within 48 sols
- Retained ≥1440 sols unless directed otherwise
## Chapter 2 — Breach Management and Containment
### §10. Breach Severity Classification
All breach events are classified according to operational scope, containment risk, and jurisdictional reach:

| Class | Description | Representative Scenarios |
|-------|-------------|---------------------------|
| I     | Isolated procedural anomaly with no containment impact | Missed credential log, low-level access irregularity |
| II    | Node-scale breach affecting a secured chamber, corridor, or restricted system | Unauthorized entry into sealed facility node or intrusion into a Tier-locked digital environment |
| III   | Disruption spanning an entire dome or its critical infrastructure | Dome-wide systems loss, multi-sector containment breach, tram lockdown triggering |
| IV    | Breach escalation across multiple domes, transit lines, or governance zones | Simultaneous structural or systems failure in two or more Compact installations |
| V     | Threat to Compact-wide operational stability or continuity | Cross-domain collapse, sovereign override, Tribunal evasion, or activation of crisis-level subroutines |

All breach classifications must be assigned within **4 sols** of incident logging and entered into the **Containment Incident Ledger (CIL)**. Class III and above require ISB notification and preliminary containment readiness within **1 sol** of designation.
### §11. Containment Activation
Containment measures may be triggered upon:
- Detection of unauthorized activity in high-security zones
- Surveillance identification of Class II+ behavior
- Tribunal confirmation of systemic instability

Authorization must be issued by an ISB supervisor or Ministry official.
### §12. Lockdown Measures
Upon breach verification:
- Access permissions are suspended
- Facility segments are sealed
- Emergency credentials and restriction codes are deployed

Release requires joint ISB–Director approval or Tribunal override.
### §13. Response Deployment
**Containment Response Units (CRUs)** are dispatched based on:
- Severity classification
- Affected dome or sector infrastructure
- Diagnostics and containment pathways

Deployment data must be logged in the **Containment Deployment Record (CDR)**.
### §14. Purge and Reset Protocols
For Class IV–V breaches:
- ISB may initiate the **Directive Nullification Protocol (DNP)**
- Impacted zones are returned to verified operational baseline
- Involved personnel undergo access review or behavioral evaluation

Tribunal confirmation required within 3 sols of initiation.
### §15. Ministry Notification
Affected Ministries must:
- Be notified within 1 sol of breach designation
- Verify operational status and halt nonessential directives
- Cooperate fully with ISB inquiries

Failure to comply triggers Codex audit under Title 7.
### §16. Civilian Protective Measures
In breach zones, civilians shall:
- Be relocated to secure containment areas
- Undergo exposure screening
- Receive cognitive shielding where applicable

Protections are guaranteed by Compact indemnity statutes.
### §17. Breach Review
All Class II+ events require:
- Joint ISB–OPI procedural review
- Formal causal analysis within 10 sols
- Policy recommendations for Codex adjudication

Final report filed in the **Post-Breach Review Codex (PBRC)**.
### §18. Codex Compliance
All breach-related records must be:
- Indexed in the **Codex Containment Annex (CCA)**
- Categorized by class, dome, and procedural vector
- Archived for ≥2880 sols unless Tribunal exception applies
## Chapter 3 — Surveillance, Audits, and Investigations
### §19. Surveillance Authority
ISB is authorized to monitor:
- Operational data streams for breach indicators
- Communications flagged via threat analysis
- Behavioral patterns within high-risk facility domes or designated sectors

All monitoring must be:
- Authorized by a Tier III+ supervisor
- Justified and filed in the **Surveillance Justification Record (SJR)**
### §20. Covert Operations
Covert actions must be:
- Filed under an authorized operational charter
- Approved at Tier IV or above
- Subject to oversight by Tribunal or Red Council committee

Records are sealed in the **Restricted Operations Archive (ROA)**.
### §21. Procedural Audits
All Compact entities are subject to:
- Scheduled audits every 180 sols
- Spot inspections during emergencies
- Verification of systems access and role compliance

Outcomes are logged in the **Procedural Audit Ledger (PAL)**.
### §22. Personnel Scrutiny
Investigation is warranted upon:
- Unusual credential usage
- Behavioral anomalies exceeding procedural limits
- Suppressed or falsified access records

All findings entered into the **Personnel Audit Archive (PAA)**.
### §23. Inquiry Initiation
Formal investigations begin when:
- A **Notice of Procedural Concern (NPC)** is submitted
- An Investigatory Cell is established
- OPI is notified with record number

Review launches within 3 sols of NPC approval.
### §24. Investigative Authority
Investigators may:
- Access audit logs and internal reports
- Isolate suspect systems under temporary Codex custody
- Suspend personnel for up to 30 sols pending Tribunal action

All actions logged in the **Investigatory Docket Register (IDR)**.
### §25. Conclusion and Reporting
Outcomes must include:
- A **Breach Report Summary (BRS)** to the Tribunal
- Recommendations for action or redress
- Optional Council briefing if cross-chamber policy is affected

Reports remain sealed for 720 sols unless released by order.
### §26. Abuse and Sanctions
ISB agents found to have:
- Exceeded authority
- Suppressed procedural evidence
- Engaged in retaliatory practices

are referred to the Tribunal and OPI, and recorded in the **Internal Abuse Ledger (IAL)**.
### §27. Logging and Oversight
All records must be:
- Stored in the SJR, PAL, IDR, and other codified ledgers
- Auditable by the Red Council and Tribunal committees
- Archived ≥2880 sols or under sealed status
## Chapter 4 — Enforcement and Jurisdiction
### §28. Sovereign Security Division (SSD)
The **Sovereign Security Division (SSD)** is the Compact’s primary enforcement unit for dome-level perimeter security and personnel compliance operations. SSD is authorized to:
- Conduct Tier verification and clearance checks at access points
- Detain unauthorized individuals or procedural violators
- Secure breach locations and seal compromised zones

All SSD actions are conducted under the authority of the Site Director and remain subject to Tribunal audit.
### §29. Mobile Tactical Field Command (MTFC)
The **Mobile Tactical Field Command (MTFC)** serves as the Compact’s rapid-response enforcement unit, deployed in high-risk or destabilizing scenarios. MTFC may be activated to respond to:
- Class III–V containment incidents
- Multi-jurisdictional breach escalation
- Hostile interference affecting Compact stability

Activation requires:
- Tier IV or equivalent authorization
- Directive issued by the Site Director or Tribunal
### §30. Deployment Logging
All SSD and MTFC operations must be:
- Logged in the **Enforcement Deployment Registry (EDR)**
- Indexed by event type, location, breach class, and personnel involved
- Reviewed post-action for Codex compliance by ISB enforcement auditors

Log entries must be certified within 10 sols of mission closure.
### §31. Jurisdictional Boundaries
SSD and MTFC enforcement authority is limited to:
- Compact-affiliated domes and sovereign sites
- Registered corridors, hubs, and transit zones
- Zones officially governed by Compact jurisdictional mandates

Operations beyond jurisdiction require:
- Tribunal-issued cross-border authorization
- Coordination with external factional or jurisdictional forces

Unauthorized activity in foreign-controlled or unregistered zones constitutes a **Class IV breach** unless pre-cleared under compact emergency authority.
### §32. Use of Force and Tactical Escalation
SSD and MTFC personnel may apply force proportional to the breach class and situational threat. Permitted enforcement tools include:
- Detainment restraints
- Environmental lockdown systems
- Non-lethal disruption utilities

Use of lethal force is prohibited unless:
- There is verified threat of fatal harm
- Lethal authorization is granted through a Tribunal-confirmed Active Response Directive (ARD)

All tactical escalation must be reviewed within 5 sols of incident and certified in the **Compact Use of Force Log (CUFL)**.
### §33. Codex Compliance
All actions under this Chapter must be:
- Indexed in the **Jurisdictional Enforcement Record (JER)**
- Cross-referenced with EDR and ISB audit reports
- Archived for ≥2880 sols or until closed by Tribunal oversight
# Title 6 — Criminal Offenses & Systemic Breach
## Part I — Crimes
### Chapter 1 — General Provisions
#### §1. Jurisdiction and Applicability
This Title applies to criminal acts that:
- Occur within **operational domains** under Compact control
- Target Codex personnel, authority structures, or sovereign assets
- Are committed by any Tiered individual, denizen, or autonomous procedural entity

Codex law supersedes local dome or faction statutes in all breach-related adjudications.
#### §2. Definitions
**(a) Breach** — An act or omission that violates Codex law, destabilizes authorized environments, or compromises procedural integrity
**(b) Access State** — A verified condition wherein an actor is linked to a sovereign system environment and capable of command interaction
**(c) Operational Domain** — A Compact-governed system space wherein personnel, directives, and authority functions are maintained
**(d) Offender** — Any sapient, procedural, synthetic, or factional construct that initiates a breach under Codex jurisdiction
#### §3. Criminal Liability
An offense requires:
- Deliberate conduct or procedural negligence
- Awareness of role and authority context
- Alignment with a Tier classification carrying Codex obligations

Cognitive coercion or compromised access state may qualify as mitigating factors, pending Tribunal evaluation.
#### §4. Equivalence of Environments
Crimes occurring within **authorized sovereign domains**—regardless of physical or non-physical form—are treated with equal legal weight. Breach committed through linked access shall not be differentiated from direct enactment.
#### §5. Attempt and Conspiracy
Attempted violations are classified at the same level as completed breaches. Coordinated action constitutes conspiracy and shall be logged in the **Compact Recidivism Ledger (CRL)**. Proxy agents are considered liable unless proven unsynchronized or uncommanded.
#### §6. Codex Primacy
All personnel, institutions, and agencies are subject to this Title. Questions of scope, contradiction, or authority are resolved by Tribunal ruling and recorded in the **Codex Juris Canon (CJC)**. Sovereign overrides must bear a Tribunal-sealed credential to defer prosecution.
### Chapter 2 — Classification and Sentencing
#### §7. Breach Tiers
| Class | Severity Level      | Examples: Systems & Access        | Examples: Behavioral & Legal        | Examples: Structural & Sovereign     |
|-------|---------------------|-----------------------------------|--------------------------------------|---------------------------------------|
| I     | Procedural Infraction | Unlogged command, failure to document credentials | Minor misconduct, failure to report | Unauthorized entry into non-sensitive zones |
| II    | Improper Access Conduct | Unauthorized system link, Tier overreach | Harassment, falsified work records | Tampering with non-critical equipment |
| III   | Operational Harm     | Credential tampering, breach of secure corridors | Assault, breach of conduct code | Damage to active infrastructure or transport systems |
| IV    | Sovereign Disruption | Unauthorized directive override, multi-tier access fraud | Electoral manipulation, coercion | Sabotage of critical Compact systems |
| V     | Compact Destabilization | Systemic corruption, classified intrusion | Treason, high-level conspiracy | Structural collapse, widespread security failure |

> **NOTICE**
All offenses must be classified by breach class and domain, and filed in the **Codex Breach Matrix (CBM)**.
#### §8. Sentencing Ranges

| Class | Minimum Sentence     | Maximum Sentence                                   |
|-------|----------------------|----------------------------------------------------|
| I     | Citation             | 30-sol suspension                                  |
| II    | Clearance restriction| 180-sol detainment + Tier downgrade                |
| III   | Operational removal  | 360-sol stasis + registry flag                     |
| IV    | Sovereign exile      | System expulsion + Tribunal restriction            |
| V     | Directive extinction | Codex-sealed termination (sealed adjudication)     |

> **NOTICE**
Modifiers as outlined in §10 apply.
#### §9. Tier Responsibility
Penalties scale based on clearance:
- **Tier I–II** — Standard enforcement
- **Tier III** — Heightened accountability; role-based review
- **Tier IV** — Tribunal-exclusive proceedings; privileges suspended upon charge
#### §10. Aggravating Conditions
Offenses are elevated if:
- Coordinated or repeat in nature
- Occur under operational emergency or corridor lockdown
- Target protected systems, personnel, or secured Compact facilities

All escalations logged in the **Sentencing Modifier Index (SMI)**.
#### §11. Codex Integration
Each ruling must be:
- Logged in the **Sovereign Justice Grid (SJG)**
- Cross-referenced with access credentials and operational metadata
- Archived ≥2880 sols unless formally expunged under Part IV
### Chapter 3 — Personal Harm and Sovereign Endangerment
#### §12. Assault and Unlawful Force
The intentional application of physical force, procedural interference, or harmful conduct toward another individual constitutes a **Class III offense**, elevated to **Class IV** if:
- The victim holds Tier III or IV status
- The event occurs in a restricted-access area
- Medical or operational incapacitation is documented

All cases must be recorded in the **Sovereign Harm Ledger (SHL)**.

#### §13. Unlawful Killing
Causing the death of any Compact-aligned individual or system-embedded person is a **Class IV offense**, escalated to **Class V** if:
- The victim holds Tier III–IV status
- The act results in broader operational disruption
- Prohibited instruments or classified tools were used

Offenses are logged in the **Termination Record Archive (TRA)**.
#### §14. Unauthorized Detention
Holding, isolating, or detaining another person without legal warrant is a **Class III offense**, elevated to **Class IV** if:
- The individual is under Compact protection
- Movement or communication systems are manipulated
- Detention includes psychological or neurological interference

Filed within the **Containment Breach Register (CBR)**.
#### §15. Coercion and Psychological Manipulation
Any intentional use of technology, behavioral triggers, or conditioning techniques to manipulate, intimidate, or disorient another person constitutes a **Class III–IV offense**, determined by severity and duration.

Cases reviewed by the **Office of Procedural Integrity** in accordance with Title 7 guidelines.
#### §16. Human Exploitation and Transport Offenses
Transporting, modifying, or transferring individuals without lawful authority is a **Class IV offense**, escalated to **Class V** if:
- The conduct spans multiple sectors or affects protected persons
- Involves coercive labor, credential fraud, or system tampering
- Victims undergo identity alteration or procedural restraint

Reported in the **Human Exploitation Registry (HER)**.
#### §17. Codex Logging
All offenses in this Chapter must be:
- Indexed in the **Personal Harm Register (PHR)**
- Reviewed by the ISB and Compact Ethics Division
- Archived ≥2880 sols or until formally cleared by Tribunal order
### Chapter 4 — Theft, Vandalism, and Structural Crimes
#### §18. Theft of Compact Property
Unauthorized possession, concealment, or removal of Compact-issued equipment, sealed assets, or operational-grade tools constitutes a **Class III offense**, elevated to **Class IV** if:
- The item is clearance-restricted or essential to facility operations
- Theft disrupts authorized activity within a designated dome or sector
- The item exhibits tampering, modification, or obstruction of tracking protocols

All violations must be recorded in the **Asset Integrity Register (AIR)**.
#### §19. Unauthorized Entry and Data Intrusion
Accessing restricted terminals, archives, or sealed facility areas without proper clearance is a **Class III offense**, elevated to **Class IV** if:
- A classified storage unit or procedural archive is compromised
- Intrusion triggers automated defense protocols or alert thresholds
- The target location is under judicial seal or restricted Tribunal control

All incidents are audited by the **Facility Access Oversight Unit (FAOU)**.
#### §20. Vandalism and Infrastructure Damage
Defacing, disabling, or intentionally damaging Compact infrastructure—including stations, terminals, or transport corridors—is a **Class II offense**, elevated to **Class III** if:
- Disruption impedes personnel movement or signal systems
- Damage requires intervention from external engineering support
- The act targets official markings, insignia, or jurisdictional emblems

Each incident must be entered into the **Infrastructure Violation Log (IVL)**.
#### §21. Arson and Energy Hazard Events
Initiating fire, thermal discharge, or unsafe energy activity within any Compact-regulated zone is a **Class III offense**, escalated to **Class IV** if:
- Occupied areas are endangered or compromised
- Emergency suppression systems are bypassed
- Structural safeguards exceed containment tolerance

All responses and event trails must be filed in the **Hazard Response Register (HRR)**.
#### §22. Unauthorized Resource Diversion
Diverting energy, bandwidth, water, or ration allocations without formal authorization constitutes a **Class III offense**, elevated to **Class IV** if:
- The diversion is distributed or sold outside Compact channels
- The disruption causes failure or destabilization of dome-wide systems or support infrastructure

All cases are reviewed by the **Resource Oversight Tribunal (ROT)**.
#### §23. Codex Integration
All violations in this Chapter must be:
- Logged in the **Compact Disruption Register (CDR)**
- Cross-referenced with zone activity audit logs
- Archived for ≥2880 sols or until formally annulled by Tribunal ruling
### Chapter 5 — Procedural Forgery and Codex Misuse
#### §24. Forgery of Credentials and System Access Tokens
Creating, altering, or duplicating registered authority symbols, command signatures, or identification credentials without lawful authorization is a **Class IV offense**, escalated to **Class V** if:
- The item grants access to restricted systems or high-clearance areas
- The forgery mimics Tribunal-certified markers
- It functions across multiple departments or protected sectors

All seized materials are to be cataloged in the **Credential Forgery Index (CFI)**.
#### §25. Falsified Identity and Role Misrepresentation
Claiming unauthorized Tier status, impersonating official personnel, or using falsified role indicators—including visual mimicry or data injection—is a **Class III offense**, raised to **Class IV** if:
- The impersonation affects judicial or electoral processes
- It spans multiple sectors or clearance domains
- It's used to bypass procedural safeguards

Cases are logged in the **Identity Violation Register (IVR)**.
#### §26. Unauthorized Access and System Misuse
Operating secured systems, automated platforms, or access-controlled environments using counterfeit credentials, revoked clearances, or tampered tokens is a **Class III offense**, escalated to **Class IV** if:
- Performed during declared security incidents
- Involves override of active commands or lockdown states

Incidents must be reported to the **Access Breach Registry (ABR)**.
#### §27. Tampering with Official Records
Altering, destroying, or replacing any official Compact documentation—such as Tribunal rulings, Council directives, or facility records—is a **Class III offense**, escalated to **Class IV** if:
- It affects legal outcomes, administrative enforcement, or public record accuracy
- It simulates lawful documentation or distributes false legal materials

All interference must be escalated to the **Office of Procedural Integrity (OPI)** for review.
#### §28. Distribution of Forged Materials
Creating or transmitting counterfeit system credentials, falsified control access tools, or forged legal documentation for the purpose of disruption or fraud is a **Class IV offense**, elevated to **Class V** if:
- Materials are widely disseminated across protected Compact institutions  
- The act compromises institutional stability or internal security protocols

Offenders are indexed in the **Forgery Oversight Log (FOL)**.
#### §29. Codex Compliance
All violations under this Chapter must be:
- Investigated by the **ISB Credential Integrity Division**
- Audited by the **Red Council Integrity Review Committee**
- Archived ≥2880 sols unless formally voided by Tribunal order
### Chapter 6 — Factional Corruption and Obstruction of Oversight
#### §30. Bribery and Improper Influence
Offering, requesting, or accepting unauthorized compensation—whether monetary, resource-based, or preferential—in exchange for:
- Tiered access privileges, role appointment, or artifact possession
- Intervention in breach proceedings or directive enforcement
- Favorable rulings in judicial or administrative actions

constitutes a **Class IV offense**, escalated to **Class V** if the bribe results in alteration of official procedure or interference with containment.

All incidents must be recorded in the **Corruption Integrity Ledger (CIL)**.
#### §31. Sovereign Interference by Factional Entities
Any attempt by a faction, Ministry, or affiliated agent to influence:
- The independence of Tribunal operations
- The lawful authority of the Site Director
- Scheduled audits or investigations under Red Seal directive

is considered a **Class IV offense** under sovereign interference statutes. May result in issuance of **Codex Suspension Orders** and immediate review.

Violations filed in the **Sovereign Oversight Breach Index (SOBI)**.
#### §32. Obstruction of Oversight Procedures
Actions that disrupt or falsify authorized reviews by enforcement or ethics bodies—including deletion of records, creation of false audit trails, or technological interference—constitute a **Class III offense**, escalated to **Class IV** if:
- Conduct is perpetrated by Tier III or IV personnel
- Audit integrity is compromised or delayed

Entries must be logged in the **Compact Audit Archive (CAA)**.
#### §33. Misinformation and Public Deception
Disseminating false or misleading information regarding Codex law, institutional protocol, or procedural directives—through official platforms, public broadcasts, or embedded content—is a **Class IV offense**, elevated to **Class V** if:
- The misinformation causes public panic or institutional breakdown
- The act undermines faith in sovereign governance

Tribunal-authorized suppression orders may be initiated.
#### §34. Breach Concealment and Coordinated Evasion
Coordinated action by two or more individuals to:
- Obscure or withhold verified breach data
- Protect involved individuals from enforcement
- Circumvent Tribunal or authorized investigation procedures

constitutes a **Class IV offense per actor**, escalated further if Tier IV personnel are involved or operational stability is compromised.

All incidents are to be indexed in the **Factional Conspiracy Register (FCR)**.
#### §35. Codex Compliance
All cases covered in this Chapter must be:
- Logged in the **Factional Interference Record (FIR)**
- Reviewed by impartial auditors affiliated with the Tribunal
- Archived ≥2880 sols unless overturned by Tribunal ruling
### Chapter 7 — Dangerous Artifacts and Unauthorized Systems Threats
 §36. Possession of Prohibited Devices
Possessing, modifying, or distributing devices banned under Compact authority—including unauthorized weapons, experimental instruments, or tampered operational tools—is a **Class III offense**, elevated to **Class IV** if:
- Carried into secure domes, high-clearance corridors, or protected operational sectors
- Enhanced through unauthorized system modification or instability triggers
- Located with falsified authentication or clearance credentials

All recovered items must be recorded in the **Restricted Equipment Index (REI)**.
#### §37. Illicit Manufacturing and Trafficking
Constructing, copying, or transporting prohibited tools or components—including banned access tokens, destabilizing modules, or unlicensed controls—is a **Class III offense**, elevated to **Class V** if:
- The material disrupts operations across multiple domes or systems  
- Activity demonstrates intent of sabotage or coordinated subversion  
- Distribution spans multiple Compact jurisdictions

Confiscated materials are entered in the **Contraband Control Ledger (CCL)**.
#### §38. Unauthorized Weapon Activation
Activating Compact-issued defensive tools or hazard-class instruments without valid clearance constitutes:
- A **Class II offense** if no harm or system disruption occurs  
- A **Class III–IV offense** if damage results or safeguards are bypassed in active operational space

All incidents must be filed in the **System Deployment Record (SDR)**.
#### §39. Structural Damage to Critical Systems
Damaging Compact infrastructure—such as structural supports, reinforced gates, or stabilization anchors—using explosives or disruptive tools constitutes a **Class IV offense**, escalated to **Class V** if:
- System failure leads to irreversible disruption or cascading damage
- Facility-wide coordination is lost
- The incident occurs during transport, security lockdown, or active containment protocols

All events are subject to Tribunal-level review and permanent record entry.
#### §40. Misuse of High-Energy Equipment
Activating unstable, unverified, or high-load energy devices—such as signal enhancers, disruption emitters, or command amplifiers—without authorization is a **Class III offense**, escalated if:
- Injury or damage is caused through malfunction or overload
- The device is untested or omitted from known systems registries
- Activation occurs during a recorded emergency or breach event

All violations are reviewed by the **Ordnance and Safety Division (OSD)**.
#### §41. Codex Compliance
All offenses under this Chapter must be:
- Logged in the **Compact Weapons and Devices Register (CWDR)**
- Investigated by authorized security and enforcement entities
- Archived for ≥2880 sols unless cleared by Tribunal ruling
## Part II — Criminal Procedure

### Chapter 1 — Breach Reporting and Detainment

#### §42. Breach Reporting
All suspected breach incidents must be reported within 4 sols by the observing officer, system monitor, or certified automation agent. Required documentation includes:
- Timestamp and location
- Tier classification of involved parties
- Suspected breach class and subtype

Reports are filed in the **Initial Breach Declaration Network (IBDN)**.

#### §43. Investigation Authority
Jurisdiction is granted to:
- **Internal Security Bureau (ISB):** Class I–IV offenses
- **Tribunal Investigative Panel:** Class V or multi-jurisdictional breaches
- **OPI Review Teams:** Cases involving procedural misconduct or Codex deviation

All investigative actions must preserve verified chain-of-custody for evidence and system credentials.

#### §44. Detainment Procedure
Valid detainment requires:
- Judicial warrant or verified enforcement citation
- Notification to superior officer or assigned supervisory Tier (if applicable)
- Secure placement in a designated holding location

In exigent circumstances, provisional detainment may occur without formal warrant if:
- The breach is actively in progress
- There is immediate risk to personnel or sovereign systems
- ISB validation is secured within 8 sols

#### §45. Rights of the Detained
All detained individuals retain the right to:
- Full disclosure of charges under the Codex
- Access to Tier-matched representation
- Basic health and cognitive stability safeguards
- Tribunal appearance within 10 sols

Due process violations are grounds for procedural challenge or relief.

#### §46. Evidence Collection
ISB agents may:
- Secure breach-linked materials, credentials, or records
- Extract system logs and communications data
- Request forensic analysis by certified review teams

All materials must be recorded in the **Compact Evidentiary Vault (CEV)**.

#### §47. Codex Compliance
All enforcement actions must be:
- Logged in the **Breach Apprehension Registry (BAR)**
- Cross-referenced with case files and investigative ledgers
- Archived for ≥2880 sols or until judicial resolution

---

### Chapter 2 — Adjudication and Rulings

#### §48. Tribunal Authority
All breach hearings are conducted before a **Triad Tribunal**, composed of:
- One Red Council magistrate
- One Tier IV representative
- One independent Codex arbiter

Class V breaches require oversight by a **Red Seal Adjudicator**. All judgments are binding unless overturned under §52.

#### §49. Hearing Procedures
The Tribunal must:
- Convene within 10 sols of detainment
- Present charges and validated evidence
- Permit qualified representation for Tier I–III respondents
- Log all proceedings in the **Trial and Verdict Record (TVR)**

Substantive disruption or procedural failure may result in retrial authorization.

#### §50. Evidence Standards
Permissible evidence includes:
- System command logs and credential records
- Validated testimony or recorded observations
- Seized devices or falsified instruments
- Trace records of unauthorized actions

All accepted evidence must be indexed in the **CEV**. Tampering or withholding constitutes a **Class III offense** (see §13, §46).

#### §51. Plea Options
An accused party may submit:
- **Admission** — Full or partial breach acknowledgment
- **Denial** — Rejection of all charges
- **System Override Claim** — Assertion of operational or cognitive impairment
- **Non-Declaration** — Triggers escalation review by Tribunal

All plea entries follow Codex procedural routing.

#### §52. Appeals Process
An appeal may be granted if:
- New material evidence is presented
- Procedural irregularities are confirmed
- Adjudicative bias or conflict is substantiated

Appeals are evaluated within 20 sols by the **Adjudicative Override Council (AOC)**.

#### §53. Codex Compliance
All rulings must be:
- Filed in the **Judicial Archive Codex (JAC)**
- Cross-linked to the subject's personnel or registry record
- Retained ≥2880 sols unless expunged by authorized mechanism

---

### Chapter 3 — Sentencing and Enforcement

#### §54. Sentencing Guidelines
Sentencing is determined by:
- Assigned breach severity (§7)
- Personnel role and Tier designation (§9)
- Circumstantial factors or historical conduct
- Post-incident behavioral assessment

Modifiers are applied by Tribunal discretion.

#### §55. Enforcement Measures
Tribunal-approved enforcement actions include:
- **Access Revocation** — Temporary system credential suspension
- **Secure Detention** — Physical placement up to 360 sols
- **Clearance Demotion** — Tier status or role reduction
- **Account Lockout** — Revocation of digital privileges
- **Codex Flagging** — Breach status link to personnel record

Each action is logged in the **Sentencing Execution Log (SEL)**.

#### §56. Corrective Mandates
Corrective orders may include:
- Legal re-education or orientation remediation
- System restoration or procedural restitution
- Monitored community assignments
- Formal acknowledgments to affected parties

Failure to comply constitutes a **Class II offense**.

#### §57. Review and Reevaluation
Reevaluation is permitted when:
- Sentence duration exceeds ≥1440 sols
- Mandated actions are verifiably completed
- Behavioral profile demonstrates restored eligibility

Tier III+ personnel may request early review with Red Council authorization.

#### §58. Codex Compliance
All post-sentencing actions must be:
- Logged in the **Tribunal Enforcement Register (TER)**
- Synchronized with the **Breach Apprehension Registry (BAR)**
- Archived ≥2880 sols unless modified by legal override
## Part III — Expungement, Reintegration, and Pardons
### Chapter 1 — Record Sealing and Behavioral Review
#### §59. Eligibility for Record Sealing
A breach record may be sealed if:
- At least 2880 sols have elapsed since the final sentencing date
- The individual has committed no new Class II or higher offenses
- Behavioral evaluations confirm consistent procedural stability
- All corrective mandates have been fully completed

Class V offenses are not eligible for sealing unless a formal pardon is issued by the Red Council under §62.
#### §60. Petition and Review
Qualified individuals may submit a petition through the **Restorative Petition Channel (RPC)**. Review must occur within 20 sols and include:
- A Tribunal-led behavior and conduct assessment
- Confirmation of procedural reliability and operational capability
- Full verification of Codex compliance and mandate fulfillment

Outcomes must be entered in the **Expungement Determination Ledger (EDL)**.
#### §61. Reinstatement of Clearance and Status
Clearance levels and prior roles may be reinstated following expungement if:
- The Tribunal confirms functional eligibility
- The individual secures factional authorization or sponsorship
- The Site Director affirms readiness for reintegration

Reinstated status remains inactive for 144 sols prior to formal activation.
#### §62. Red Council Pardons
The Red Council may grant formal pardons that:
- Seal all prior offenses, regardless of breach classification
- Restore Tier status or operational assignments
- Nullify current sanctions, restrictions, or containment designations

All pardons must include Red Seal verification and be archived in the **Clemency Grant Archive (CGA)**.
#### §63. Codex Compliance
All expungement and reintegration activity must be:
- Filed in the **Compact Reintegration Register (CRR)**
- Linked to the subject’s personnel and system identity record
- Auditable by ISB, Site Administration, or Red Council for ≥2880 sols
# Title 7 — Tribunal and Adjudication Protocols
## Chapter 1 — Structure and Appointment
### §1. Tribunal Composition
Each adjudicative Tribunal shall consist of:
- One Red Council Magistrate (legislative authority)
- One Tier IV Delegate (executive oversight)
- One Compact Arbiter (judicial neutrality)

Class V breach hearings require oversight by a Red Seal Adjudicator.
### §2. Term and Convening
Tribunal members serve terms of 1440 sols, renewable by Red Council vote. A Tribunal is convened upon:
- Escalation of a breach to Class III or higher
- Referral by ISB or formal procedural review request
- Activation of Judicial Protocol IX

Emergency panels may form under restricted conditions during confirmed systemic disruption.
### §3. Appointment Procedures
Appointments are made through:
- Red Council nomination or decree
- Predefined delegation rosters
- Random selection from Tier IV-certified judicial pool

All appointments logged in the **Tribunal Appointment Register (TAR)**.
### §4. Disqualification and Recusal
A Tribunal member must recuse if:
- Affiliated with the case subject's institution or faction
- Documented correlation with breach activity exceeds approved threshold
- Impartiality concern is verified and entered in the **Conflict Record Log (CRL)**

Failure to recuse invalidates subsequent verdicts.
### §5. Jurisdiction and Powers
Tribunals are empowered to:
- Hear and resolve Class II–V charges
- Issue binding sentences and containment orders
- Rule on expungement and privilege reinstatement
- Suspend Compact rights under approved authority clauses

Minor administrative disputes fall outside scope unless referred by oversight bodies.
### §6. Codex Compliance
Tribunal composition and rulings must be:
- Indexed in the **Judicial Composition Ledger (JCL)**
- Audited on a 720-sol cycle by the Council Integrity Division
- Assessed for verdict consistency and procedural precedent
## Chapter 2 — Procedure and Deliberation
### §7. Case Initialization
Upon referral, the Tribunal shall:
- Review submitted evidence and investigative logs
- Validate the procedural integrity of the case file
- Assign a unique Judicial Case Identifier (JCI)
- Schedule a hearing within 10 sols of registration

The involved party must be notified via an official communication channel.
### §8. Disclosure Requirements
All parties are entitled to receive:
- The full evidentiary record
- Names and roles of all assigned Tribunal members
- A formal briefing of charges and legal rights
- Access to certified legal representation or support

Failure to provide disclosures within 3 sols results in a mandatory hearing delay.
### §9. Hearing Procedure
Hearings proceed as follows:
1. Verification of Tribunal authority
2. Presentation of formal charges
3. Submission of evidence
4. Plea entry by the respondent
5. Witness statements, if applicable
6. Private Tribunal deliberation
7. Pronouncement of verdict
8. Issuance of sentencing or procedural directive

Class V hearings may be redacted under sealed status (see §17).
### §10. Representation
Respondents may be represented by:
- Authorized legal advocates
- Compact-assigned counsel
- Themselves (if Tier III or higher)

All witnesses or testimonial participants must undergo procedural briefing prior to appearance.
### §11. Deliberation Protocol
Tribunal deliberation shall:
- Occur in a secure and access-restricted chamber
- Be concluded within 72 adjudication units
- Involve only official Tribunal members and required notetakers
- Record all decision inputs in the **Judicial Insight Index (JII)**

Dissenting members may register formal objections using designated notation.
### §12. Verdict Finalization
A ruling is formalized upon:
- Majority or unanimous Tribunal concurrence
- Authorization override for Class V by Red Council Review
- Entry of verdict record into the **Final Judgment Archive (FJA)**

All confirmed verdicts are binding and immediately enforceable.
### §13. Codex Compliance
All proceedings under this Chapter must be:
- Logged in the **Sovereign Tribunal Record (STR)**
- Cross-indexed with relevant legal and procedural case entries
- Archived ≥2880 sols or permanently if issued under sealed status
## Chapter 3 — Appeals and Emergency Authority
### §14. Grounds for Appeal
An appeal may be filed if:
- New verified evidence emerges
- Procedural misconduct or systemic fault is documented
- Adjudicator conflict is confirmed via record
- Testimony was compromised by system interference

Appeals must be initiated within 20 sols of final judgment.
### §15. Adjudicative Override Council (AOC)
The AOC consists of:
- Two Red Council Magistrates
- One Tier IV Governance Advisor
- One Codex Continuity Officer

The AOC may:
- Affirm, amend, or overturn decisions
- Mandate Tribunal reconstitution
- Seal or nullify verdicts under emergency provisions

Actions must be recorded in the **Appeal Verdict Register (AVR)**.
### §16. Emergency Panels
If adjudicative functions are disrupted:
- A **Rapid Response Tribunal** may be invoked by ISB order
- Verdict must be reached within 12 units using authorized override mechanisms
- Red Council reviews outcome within 40 sols

Proceedings indexed in the **Emergency Adjudication Register (EAR)**.
### §17. Sealed Proceedings
Certain high-risk trials may proceed under restricted conditions:
- Records are omitted from public documentation
- Participant identity records are secured
- Final ruling stored in the **Confidential Seal Vault (CSV)**

Access restricted to relevant judicial and executive authorities.
### §18. Post-Review Procedure
All modified or emergency rulings shall undergo review by:
- The OPI audit division
- Qualified legal historians
- Designated systemic analysts

Findings entered into the **Tribunal Integrity Archive (TIA)**.
### §19. Codex Compliance
All records under this Chapter must be:
- Integrated into breach lineage system logs
- Attached to relevant verdict records
- Archived ≥2880 sols or indefinitely if sealed
# Title 8 — Electoral Protocols and Referenda
## Chapter 1 — Legislative Chamber Structure and Appointment
### §1. Council Composition
Legislative authority under the Martian Initiative is vested in the **Red Council**, a bicameral body composed of:
- The **Vox Chamber**, representing Compact divisions and operational personnel
- The **Obsidian Circle**, representing sovereign installations and planetary jurisdictions

Each chamber governs its own appointment procedures under this Title.
### §2. Vox Chamber Appointments
Appointments are assigned per operational division of IMR–Acheron (e.g., Containment, Research, Engineering), based on:
- **One representative per 50 active personnel**, with at least one per division
- Personnel audits conducted quarterly by the **Office of Personnel Enumeration (OPE)**
- Certification by the **Credentials Subcommittee**, with registration in the **Congressional Roster Ledger (CRL)**

Terms are 100 sols and renewable unless restricted by disciplinary sanction.
### §3. Obsidian Circle Appointments
Obsidian Circle membership includes:
- **One Councilor per sovereign installation or planetary division** under IMR designation
- Eligibility certified by the **Office of Planetary Governance (OPG)** under **Directive A-13**
- Councilors serve 200-sol terms, renewable unless barred by active investigation or concurrent officeholding

Selection may occur via appointment, site-level election, or sovereign delegation. Records are filed in the **Sovereign Councilor Archive (SCA)**.
### §4. Elector Eligibility
To vote in Vox Chamber elections, electors must:
- Hold Tier II clearance or above
- Maintain verified operational engagement ≥92%
- Have no Class III or higher violations in the previous 720 sols

Verification is conducted by the **Sovereign Citizenship Archive (SCA)** and certified via the **Initiative Relay Grid (IRG)**.
### §5. Dispute Resolution
If chamber seat disputes or vacancies arise:
- A **Judicial Verification Review** may be initiated
- A **Credential Arbitration Panel (CAP)** rules within 12 system units
- Final decisions are recorded in the **Electoral Codex Register (ECR)**
## Chapter 2 — Legislative Referenda and Public Measures
### §6. Council-Initiated Referenda
The Red Council may submit measures to public vote for:
- Amendments to Compact provisions
- Reforms to structural protocol or Tier systems
- Recognition of new planetary jurisdictions
- Ratification or repeal of existing laws

Passage requires:
- ≥60% affirmative vote from verified electors
- Participation from electors across ≥3 sovereign installations

Results are archived in the **Sovereign Decision Vault (SDV)**.
### §7. Citizen-Initiated Measures
Any Tier II+ denizen may petition for referendum by:
- Submitting ≥1440 validated endorsements to the **IRG**
- Confirming structural compatibility and procedural scope
- Ensuring no identical measure failed in the last 2880 sols

Qualified petitions are reviewed within 20 sols by the Council.
### §8. Factional Measures
Recognized factions may propose regionally scoped directives to:
- Establish internal policy or ceremony
- Alter factional norms or engagement practices
- Define Tier interaction terms within factional governance

These measures are locally binding unless escalated through Council referendum.
### §9. Emergency Override Procedures
If:
- Four or more Obsidian Circle seats remain vacant, or
- Verified system cohesion drops below 80%

Then:
- An **Emergency Override Referendum** may be initiated by the Council
- All verified electors may vote on reconstituting Council membership or authority
- Results are entered in the **Continuity Safeguard Register (CSR)** and subject to expedited Tribunal review
### §10. Codex Compliance
All referenda, appointments, and override measures must be:
- Filed in the **Electoral Codex Register (ECR)**
- Certified by Red Council staff and Tribunal oversight
- Considered binding unless overturned through lawful public vote or sovereign directive