Home › Master Spec › Power Architecture for Permanent Bases
IPLS Foundation Release v0.5.4 • 11 May 2026 • 100 % Lighthouse Scores (Mobile + Desktop) • Disciplined Requirements Engineering • External Validation Integrated • Foundation Phase 100 % Complete
NOW OPEN Serious contributors wanted — Section 7.1 Contributor Value Proposition is live Read what you receive →
Lane B Engineering extrapolation (known physics, plausible scaling)

Power Architecture for Permanent Bases

Reliable, multi-century power systems for hollowed-asteroid habitats — designed to support life support, manufacturing, docking, and all other operations with zero dependence on Earth resupply.

Purpose

Provide continuous, safe, and highly redundant power for a permanent base that may operate for hundreds or thousands of years. The system must be restartable after long dormancy periods and gracefully degrade over centuries.

Key Functional Requirements

The requirement cards on this page govern. Where this text differs, the card applies.

  • The ASI recommends the primary power source. The operator selects it under IPLS-5.1-002.
  • Service life per IPLS-3.1.6-008.
  • Multiple independent power buses and energy storage systems (redundancy at every level)
  • Safe, restartable architecture after multi-decade or multi-century dormancy
  • Universal power interfaces compatible with the Universal Modular Platform hardpoints
  • Integration with ISRU-derived materials for shielding and structural components
  • Thermal management and waste-heat utilisation for base heating and industrial processes
  • Autonomous monitoring, fault isolation, and repair protocols
  • Scalable output to support growing base population and industrial activity

Integration with Hollowed Asteroid

Installation order relative to hollowing and sealing is unset. Heat not used shall be rejected to space. Life-support heat shall not depend on generator waste heat alone.

IPLS-IPLS-3.1.6-001 Maturity: B
Phase 4

Permanent Base Power Architecture Mandate

Requirement: Every hollowed asteroid base shall operate a fail-operational power architecture (PGEDS-v1). Life support is a separate fail-operational path under IPLS-5.1-002. Redundant life-support units shall not share a single power feed (IPLS-3.1.5-008). Which PGEDS-v1 sources a Lane B base may depend on is unset.

Rationale: Installation order relative to hollowing, sealing, and life-support commissioning is unset. Construction-phase power is unset.

Interfaces
PGEDS-v1, UMP-PWR-001, UMP-THERMAL-001, Operator-Control Layer
Verification Method
Full-system power-flow simulation • Load-balance testing • Digital-twin long-duration validation
Failure Modes & Mitigations
Total power loss (mitigated by N+3 redundancy and automatic failover)
Dependencies
Hollowed Asteroid Bases (3.1.4), Life Support (3.1.5), UMP-PWR-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-002 Maturity: B
Phase 4

Multi-Tier Scalable Power Generation

Requirement: Tier boundaries are provisional. The demand basis is unset. UMP-PWR-001 hot-swap applies up to its port rating. The interface for generation above that rating, and the per-port ceiling, are unset.

Rationale: Allows graceful scaling as the base grows from initial crewed operations to full industrial colony.

Interfaces
UMP-PWR-001, PGEDS-v1, UMP-MECH-001
Verification Method
Tiered load testing • Hot-swap validation • Digital-twin scalability simulation
Failure Modes & Mitigations
Generation mismatch during growth (mitigated by modular bus design)
Dependencies
IPLS-3.1.6-001, Universal Modular Platforms (3.2)

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-003 Maturity: B
Phase 4

N+3 Redundancy & Graceful Degradation

Requirement: N per node and the list of critical nodes are unset. The output floor after failures is unset. Load-shedding acts inside the IPLS-5.1-002 envelope and is logged and reported to the operator. Life-support loads are on the separate fail-operational path and are not shed. The shed order for other loads is unset. Whether a hot-swap that lowers redundancy on a node feeding life support needs operator consent is unset.

Rationale: Ensures continuous habitability and operations across centuries, even during major faults or maintenance.

Interfaces
PGEDS-v1, UMP-DIAG-001, Operator-Control Layer
Verification Method
Fault-injection testing • Accelerated life testing • Digital-twin failure-mode simulation
Failure Modes & Mitigations
Cascading failure (mitigated by isolated redundant buses)
Dependencies
IPLS-3.1.6-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-004 Maturity: B
Phase 4

Long-Dormancy Restart Capability

Requirement: Restart after dormancy is logged and reported to the operator. Whether restart waits for operator consent is unset. On loss of link the IPLS-3.1-014 hold applies. The black-start energy source, its capacity, and its storage life are unset.

Rationale: Supports future expansion, daughter-colony seeding, or contingency reactivation of legacy bases.

Interfaces
PGEDS-v1, UMP-MAINT-001, Operator-Control Layer
Verification Method
Cold-start simulation • Long-term storage validation • Digital-twin dormancy testing
Failure Modes & Mitigations
Restart failure (mitigated by multiple independent starter systems)
Dependencies
IPLS-3.1.6-003, UMP-DURABILITY-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-005 Maturity: B
Phase 4

Waste-Heat Utilisation & Thermal Integration

Requirement: Waste heat may be routed to habitat heating, water distillation, and industrial processes. Heat not used shall be rejected to space. Life-support heating and water distillation shall not depend on power-generation waste heat as their only heat source. Heat-rejection capacity is unset.

Rationale: Maximises overall system efficiency and reduces auxiliary power demand in the closed-loop ecosystem.

Interfaces
UMP-THERMAL-001, Life Support (3.1.5), On-Site Manufacturing (3.1.13)
Verification Method
Thermal-balance audit • Digital-twin heat-flow simulation
Failure Modes & Mitigations
Thermal runaway (mitigated by redundant cooling loops)
Dependencies
IPLS-3.1.6-001, UMP-THERMAL-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-006 Maturity: B
Phase 4

Universal Power Hardpoint Distribution

Requirement: Hardpoints on one face shall be fed from independent buses. Hardpoints feeding life support follow IPLS-3.1.5-008. Automatic isolation acts inside the IPLS-5.1-002 envelope and is logged and reported. Whether isolation may de-energise an occupied zone is unset.

Rationale: Enables rapid reconfiguration and expansion without rewiring.

Interfaces
UMP-PWR-001, UMP-MECH-001, Operator-Control Layer
Verification Method
Power integrity testing • Hot-swap validation
Failure Modes & Mitigations
Single-point power loss (mitigated by dual-bus design)
Dependencies
Universal Modular Platforms (3.2)

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-007 Maturity: B
Phase 4

Operator Control & Manual Override Layer

Requirement: Critical power functions shall expose physical overrides. A person on site may use an override to preserve life inside the IPLS-5.1-002 envelope. Each use is logged and reported to the operator and confers no operator authority. Telemetry goes to the command node on the 3.1.19 network. On loss of link, life-preserving functions continue inside the envelope. The IPLS-3.1-014 hold applies to other actions. T is unset. Whether a veto can stop a life-preserving action already running is unset.

Rationale: Preserves operator authority under IPLS-5.1-002.

Interfaces
UMP-OPERATOR-001, PGEDS-v1
Verification Method
Human-in-the-loop testing • Override latency audit
Failure Modes & Mitigations
Automation lockout (mitigated by physical interlocks)
Dependencies
UMP-OPERATOR-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-008 Maturity: B
Phase 4

Multi-Century Durability & TSP-v1 Readiness

Requirement: Life-critical systems remain at the 500-year figure in IPLS-3.1-016. Whether power elements feeding life support are life-critical is unset. Supersession waits for operator consent under IPLS-5.1-002. TSP-v1 readiness criteria are undefined.

Rationale: Ensures the base remains powered as frontier energy technologies evolve without decommissioning existing assets.

Interfaces
PGEDS-v1, TSP-v1, UMP-DURABILITY-001
Verification Method
Accelerated life testing • TSP-v1 retrofit simulation
Failure Modes & Mitigations
Irreparable failure (mitigated by modular replacement and on-site replication)
Dependencies
All prior 3.1.6 items, UMP-DURABILITY-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-009 Maturity: B
Phase 4

ISRU Feedstock Integration for Power Systems

Requirement: Feedstock specification follows the selected source. Fuel, coolant, and shielding specifications are unset until the source is selected. The dose limit and its source standard are unset.

Rationale: Closes the power loop completely and supports true multi-century self-sufficiency far from Earth supply lines.

Interfaces
UMP-FLUID-001, On-Site Manufacturing (3.1.13), Storage & Logistics (3.1.14), PGEDS-v1
Verification Method
ISRU-to-power feedstock testing • Digital-twin closed-loop simulation
Failure Modes & Mitigations
Feedstock incompatibility (mitigated by material-agnostic modular design)
Dependencies
All prior 3.1.6 items, On-Site Manufacturing (3.1.13)

Open Questions: None at v0.7

IPLS-IPLS-3.1.6-010 Maturity: B
Phase 4

Power Architecture Hand-Over & Readiness Gate

Requirement: Crew arrival follows IPLS-3.1-018 and IPLS-3.1.4-012. The 180-day power audit is evidence for that gate, not a second gate.

Rationale: Protects biological and post-biological crews by ensuring the foundational utility is verifiably stable before human presence.

Interfaces
Operator-Control Layer, Ethical Frameworks (5.1), Governance Frameworks (3.1.11), Hollowed Asteroid Bases (3.1.4)
Verification Method
180-day autonomous power operations audit • Human-in-the-loop readiness gate simulation
Failure Modes & Mitigations
Premature transition (mitigated by hard automated gate and operator veto)
Dependencies
All prior 3.1.6 items, Ethical Frameworks (5.1)

Open Questions: None at v0.7