The single core architecture that powers every IPLS vessel, mining rig, orbital factory, station, and infrastructure module — designed for maximum flexibility, full operator control, and zero vendor lock-in.
Provide one highly versatile, standardised core platform that can be rapidly reconfigured for any mission — from small prospector drones to massive asteroid miners, orbital shipyards, lunar bases, or security vessels — without redesigning the entire vehicle each time.
Every probe, mining rig, orbital manufacturing platform, support vessel, and habitat module is built around this same universal core. This creates true fleet-wide interoperability, simplifies maintenance, and allows third-party companies to develop specialised bolt-on modules while IPLS retains control of the core architecture.
Requirement: Every UMP core module shall expose standardised mechanical hardpoints on all six faces with ISO 668-compatible load ratings, self-aligning connectors, and operator-controlled locking mechanisms.
Rationale: Enables rapid hot-swapping of any module without vendor lock-in or custom engineering.
Open Questions: None at v0.6
Requirement: Every UMP core module shall expose redundant bidirectional power hardpoints (minimum 2 per face) capable of 48–400 VDC with automatic load-sharing and hot-swap capability.
Rationale: Ensures fail-operational power distribution across all modules for multi-century operation.
Requirement: Every UMP core module shall expose dual redundant optical + copper data hardpoints supporting 100 Gbps+ with quantum-entanglement-ready fibre ports and operator-controlled authentication.
Rationale: Provides deterministic, low-latency command and telemetry while preserving operator sovereignty.
Requirement: Every UMP core module shall expose standardised quick-connect fluid/gas ports for propellant, coolant, air, water, and waste transfer with automatic leak detection and operator-controlled isolation valves.
Rationale: Enables closed-loop resource sharing across modules and future ISRU integration.
Requirement: Every UMP core module shall support hot-swapping of any attached module while the platform remains operational.
Rationale: Maximises uptime and allows in-flight reconfiguration without EVA or downtime.
Requirement: UMP core modules shall be available in standardised size classes from small tug-scale to large industrial-scale.
Rationale: Allows the same architecture to serve every mission class without redesign.
Requirement: Every UMP core module shall be designed for a minimum 200-year service life with graceful degradation and field-repairable components.
Rationale: Meets the multi-century fail-operational requirement of the IPLS philosophy.
Requirement: UMP core modules shall be fully manufacturable by ASI using in-situ resources once orbital factories are online.
Rationale: Eliminates Earth-to-orbit launch mass dependency for all future expansion.
Requirement: Every UMP core module shall incorporate active and passive thermal management interfaces compatible with all attached modules and the central PGEDS-v1.
Rationale: Maintains thermal stability across the full range of operational environments and power loads.
Requirement: Every UMP core module shall provide standardised mounting points and power/data interfaces for modular radiation shielding and micrometeoroid protection panels.
Rationale: Allows mission-specific shielding without redesigning the core platform.
Requirement: Every UMP core module shall expose a complete operator control layer with physical manual overrides for all critical functions, independent of ASI or automated systems.
Rationale: Preserves human (and post-biological) command authority at all times.
Requirement: Every UMP core module shall be designed for field repair using only standard tools and ISRU-derived spares, with clear access panels and hot-swappable internal components.
Rationale: Supports multi-century operation far from Earth supply lines.
Requirement: Every UMP core module shall provide dedicated mechanical, power, data, thermal, and fluid interfaces for hot-swappable propulsion modules including IPLS-NWM-v1 nacelles.
Rationale: Enables seamless integration and future upgrade of all propulsion systems under TSP-v1.
Requirement: Every UMP core module shall expose standardised sealing and pressurization hardpoints compatible with all attached modules and the base life-support system.
Rationale: Ensures pressure integrity across modular assemblies in vacuum or partial-atmosphere environments.
Requirement: Every UMP core module shall provide standardised avionics and navigation bus interfaces for attitude control, positioning, and traffic management.
Rationale: Enables fleet-wide coordination and precise navigation without vendor-specific hardware.
Requirement: Every UMP core module shall expose standardised life-support and ECLSS resource coupling ports for air, water, nutrients, and waste exchange.
Rationale: Guarantees closed-loop resource sharing across all modules and future expansion.
Requirement: Every UMP core module shall provide standardised mechanical, power, data, and thermal mounting interfaces for sensor suites and instrumentation arrays.
Rationale: Enables mission-specific sensing without redesigning the core platform while maintaining full operator control and interoperability.
Requirement: Every UMP core module shall expose standardised emergency egress ports, EVA hardpoints, and rescue coupling interfaces compatible with all IPLS vessels and bases.
Rationale: Guarantees rapid crew evacuation, EVA operations, and external rescue capability in all failure scenarios.
Requirement: Every UMP core module shall provide standardised cargo, payload, and docking attachment hardpoints with automatic load sensing and operator-controlled locking.
Rationale: Enables safe, rapid transfer of cargo, modules, and entire vessels across the entire IPLS fleet and infrastructure.
Requirement: Every UMP core module shall incorporate a dedicated self-diagnostic, health-monitoring, and telemetry bus with real-time reporting to the central command layer.
Rationale: Provides continuous system health visibility and predictive maintenance for multi-century reliability.
Requirement: Every UMP core module shall implement versioned interface definitions with full backward compatibility and automated upgrade pathways under TSP-v1.
Rationale: Ensures seamless evolution of the platform across centuries without decommissioning legacy assets.
Requirement: Every UMP core module shall provide standardised robotic manipulation hardpoints and maintenance access ports compatible with all robotics tiers (3.1.20).
Rationale: Enables autonomous and teleoperated maintenance, repair, and reconfiguration by robotic systems.