Infrastructure Sovereignty Regulation Act

SUMMARY OF PROBLEM:

Control over critical space infrastructure (launch systems, orbital platforms, communications networks, navigation systems, and energy systems) increasingly functions as a form of de facto sovereignty, yet no legal framework defines or limits this power.¹
Existing frameworks, including the Outer Space Treaty, prohibit national sovereignty claims but do not address functional sovereignty exercised by private or state-backed operators through infrastructure control.²
Entities controlling infrastructure can dictate access, pricing, operational conditions, and participation, effectively governing economic and operational behavior within their systems.
This creates a gap where power exists without corresponding legal accountability or constraint.
The absence of regulation allows infrastructure operators to operate as quasi-sovereign actors without democratic, legal, or regulatory checks.

EXAMPLES

A dominant orbital platform operator sets rules governing access, pricing, and behavior for all participants using the platform.
A communications network provider controls data access and prioritization across multiple missions.
A navigation system operator can influence mission viability by restricting access or altering service conditions.
A vertically integrated entity controls multiple infrastructure layers, effectively governing participation across the value chain.

ANALYSIS / IMPACT ON SOCIETY

Sovereignty traditionally refers to ultimate authority within a system, but infrastructure control can replicate this authority in functional terms.³
Economic impact includes concentration of power and distortion of market dynamics.
Operational impact includes dependency on infrastructure providers for mission success.
Market impact includes reduced competition and increased barriers to entry.
Individual and enterprise impact includes subjection to rules set by non-governmental actors.
Analog systems (railroads, telecommunications, digital platforms) demonstrate that infrastructure control can create governance-like power.⁴
In space, where alternatives are limited, infrastructure sovereignty becomes particularly dominant.

SOLUTIONS

Define and regulate “infrastructure sovereignty” as a legally recognized concept.
Impose obligations on dominant infrastructure operators equivalent to public-interest duties.
Establish limits on unilateral rule-making by infrastructure controllers.
Require oversight of infrastructure governance functions.

RELATED COURT CASES (IRAC + CITATIONS)

Case 1: Munn v. Illinois, 94 U.S. 113 (1877)

Summary: Businesses affecting public interest may be regulated.
Issue: Whether private control can be subject to public regulation.
Rule: Public interest justifies regulation of private entities.
Analysis: Space infrastructure meets this threshold.
Conclusion: Regulation is appropriate.⁵

Case 2: Marsh v. Alabama, 326 U.S. 501 (1946)

Summary: Private entity performing public functions subject to constitutional constraints.
Issue: Whether private actors can be treated as public authorities.
Rule: Functional equivalence triggers obligations.
Analysis: Infrastructure operators exercise similar functions.
Conclusion: Accountability is required.⁶

Case 3: United States v. Terminal Railroad Ass’n, 224 U.S. 383 (1912)

Summary: Infrastructure control required shared access obligations.
Issue: Whether control can be limited.
Rule: Essential facilities doctrine applies.
Analysis: Space infrastructure qualifies as essential.
Conclusion: Limits are necessary.⁷

POSSIBLE SUPPORT

Governments would support this legislation because it preserves regulatory authority.
Market participants would support this legislation because it limits arbitrary control.
Consumer protection organizations would support this legislation because it promotes fairness.
Smaller firms would support this legislation because it reduces dependency risk.

POSSIBLE OPPOSITION

Infrastructure operators may oppose this legislation due to constraints on control.
Commercial firms may argue that governance flexibility is necessary for efficiency.
Investors may oppose due to reduced returns from control advantages.
Some stakeholders may argue that sovereignty concepts do not apply to private systems.

ARGUMENTS IN SUPPORT

This legislation ensures that infrastructure control does not become unchecked authority.
This legislation aligns power with accountability.
This legislation preserves competitive and open systems.
This legislation reflects realities of system-based governance.

ARGUMENTS IN OPPOSITION

This legislation may increase regulatory complexity.
This legislation may reduce incentives for infrastructure investment.
This legislation may limit operational flexibility.
This legislation may create jurisdictional conflicts.

BUDGET IMPACT

Implementation costs are moderate and include oversight and regulatory frameworks.
Governments bear administrative costs; operators bear compliance costs.
Long-term benefits include reduced systemic risk and improved governance.

TARGET LEGISLATIVE BODIES AND JURISDICTIONS

UNITED STATES CONGRESS: This entity is relevant because it can regulate infrastructure control under federal law (51 U.S.C.).
FEDERAL AVIATION ADMINISTRATION (FAA): This entity is relevant because it regulates operational systems.
FEDERAL COMMUNICATIONS COMMISSION (FCC): This entity is relevant for communications infrastructure oversight.
EUROPEAN UNION: This entity is relevant because it enforces competition and infrastructure regulation.
UNITED NATIONS COPUOS: This entity is relevant because it can define international governance norms.
EMERGING SPACEFARING NATIONS: These entities are relevant because they can define infrastructure governance early.

SECTIONS OF LAW IMPACTED

51 U.S.C. § 509 would require amendment to include infrastructure governance obligations.
Antitrust laws (Sherman Act, Clayton Act) would intersect with enforcement.
Administrative law principles would apply to governance oversight.
International frameworks would be influenced through sovereignty interpretations.

ENFORCEMENT REALITY + GAP ANALYSIS

Current frameworks do not recognize infrastructure sovereignty.
Operators exercise governance-like control without oversight.
Enforcement is fragmented across multiple agencies.
No unified framework exists to regulate infrastructure power.

RISK EXPOSURE ANALYSIS

Legal risk is high due to undefined authority structures.
Operational risk is severe due to dependency on dominant systems.
Financial risk is high due to concentration of control.
Systemic risk is critical due to governance gaps.

LANGUAGE (MANDATORY — LEGISLATIVE CORE)

TITLE

Infrastructure Sovereignty Regulation Act

DETAILED LEGISLATIVE LANGUAGE (FULLY DEVELOPED)

Section 1 — Definitions

(a) “Infrastructure Sovereignty” means the effective control over access, rules, and operations within a space system.
(b) “Dominant Infrastructure Operator” means any entity exercising such control.
(c) “Public Interest Obligation” means duties imposed to ensure fairness, access, and accountability.

Section 2 — Scope and Applicability

This Act applies to all Dominant Infrastructure Operators under 51 U.S.C. § 509.

Section 3 — Recognition of Infrastructure Sovereignty

(a) Infrastructure Sovereignty is recognized as a form of functional authority subject to regulation.
(b) Entities exercising such authority shall be subject to Public Interest Obligations.

Section 4 — Limitations on Authority

(a) Operators shall not impose rules that restrict access or participation without justification.
(b) Governance functions shall be subject to oversight.

Section 5 — Transparency Requirements

(a) Operators shall disclose rules governing system use.
(b) Decisions affecting participants shall be documented and reviewable.

Section 6 — Oversight Mechanisms

(a) Regulatory authorities shall supervise infrastructure governance practices.
(b) Independent review bodies may be established.

Section 7 — Prohibited Conduct

(a) Operators shall not exercise arbitrary or discriminatory control.
(b) Operators shall not exceed defined authority limits.

Section 8 — Enforcement

(a) Violations shall be subject to regulatory and judicial action.
(b) Non-compliant operators may face operational restrictions.

Section 9 — Liability

(a) Operators shall be liable for harm resulting from misuse of Infrastructure Sovereignty.
(b) Liability shall not be waived.

Section 10 — Measurable Triggers

A violation occurs when:
(a) Authority is exercised without oversight.
(b) Rules are not disclosed.
(c) Access is restricted arbitrarily.

Section 11 — Implementation

(a) Regulations shall be issued within 12 months.
(b) Compliance required within 24 months.

Section 12 — Penalties

(a) Violations shall result in fines and corrective measures.
(b) Repeat violations may result in structural remedies or license revocation.

Section 13 — Supremacy and Non-Waiver

(a) This Act supersedes conflicting provisions.
(b) Rights under this Act may not be waived.

FOOTNOTES (CHICAGO STYLE)

Space infrastructure control studies.
Outer Space Treaty.
Sovereignty theory and governance doctrine.
Infrastructure regulation research.
Munn v. Illinois, 94 U.S. 113 (1877).
Marsh v. Alabama, 326 U.S. 501 (1946).
Terminal Railroad, 224 U.S. 383 (1912).