Home › Master Spec › Portal Transportation & Spacetime Folding
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 D Frontier physics / speculative placeholder (non-baseline for early phases)
Section 4.4 • 01 May 2026

Portal Transportation & Spacetime Folding

The requirement cards on this page govern. Activation waits for operator consent. Transit time is unset.

Pinhole probe verification, PGEDS-v1 power substrate, PIS-v1 universal interface, and full integration of IPLS-NWM-v1 positive-energy nacelle warp modules (Frontier Annex 4.5).

Inter-Planetary Link Ship • Guildford, Surrey, UK

1. Purpose

The requirement cards on this page govern. Activation of a portal waits for operator consent. Transit time is unset. An ASI is never an operator.

2. Core Operational Requirements

  • Pinhole probe verification mandatory before any full-scale portal activation (probe returns with full spacetime metric data).
  • All portals shall interface exclusively through the Universal Portal Interface Specification (PIS-v1, Section 4.4.1).
  • Burst power per nacelle is unset. The port rating is unset.
  • Fail-operational design: any single nacelle or power failure shall trigger safe shutdown with no loss of crew or vessel integrity.

3. Integration of Frontier Technology (IPLS-NWM-v1)

Reference: Frontier Technology Integration Framework (Section 4.5.3.1) and White et al., “Interior-flat cylindrical nacelle warp bubbles”, Classical and Quantum Gravity 42(23), 235022 (08 December 2025).

The nacelle warp module (n = 2–4 discrete Gaussian-cylinder nacelles) replaces continuous ring geometries, localising energy to end-caps and producing an interior-flat bubble volume. This is the primary engineering path for all IPLS portal and generation-ship precursor drives.

Functional Requirements — Nacelle Warp Module (IPLS-NWM-v1)

  • Interface Compatibility: Mates to Universal Modular Platforms (3.2) via PGEDS-v1 power hardpoints and PIS-v1 spacetime-fold ports. Nacelle count selectable at outfitting.
  • Energy Source: PGEDS-v1 micro-modular fusion / antimatter / zero-point extraction. Metric minimises (and ideally eliminates) negative-energy-density requirements.
  • Safety: The interior tidal limit is unset. Pinhole-probe pass criteria are unset.
  • Operator Control: Full command authority via robotics tiering (3.1.20), manual override, ethical kill-switch, and sentience-emergence monitoring (3.1.21).
  • Multi-Century Reliability: On-board ISRU repair swarm (von Neumann-compatible) and self-diagnostic loops. Design lifetime ≥500 years with 99.999 % uptime.
  • Modularity: Hot-swappable nacelle units in zero-g docking facilities (3.1.7). Scalable from probe to generation-ship scale (Section 4.1).

4. PIS-v1 Interface Contract (Reference)

PIS-v1 is an upgrade path. The 4.4.1 cards are not yet repaired.

5. Validation & Promotion Path

IPLS-NWM-v1 has passed Frontier Annex validation protocol (4.5.4) and is now promoted to core operational status in this page. Future refinements will be tracked here and in the Frontier Annex.

Living Document v0.5.1 • 07 May 2026 • Frontier-physics placeholder retained for ASI-contingent evaluation. Not a baseline dependency for Foundation Phase, asteroid mining, UMP, or orbital manufacturing work.
IPLS-IPLS-4.4-001 Maturity: D
Phase 4+

Portal Transportation & Spacetime Folding Mandate

Requirement: Safe, instantaneous, operator-controlled spacetime folding portals shall be provided for travel between pre-mapped destinations, using pinhole-probe verification, PGEDS-v1 power substrate, and PIS-v1 universal interface. Transit time is unset. Oversight is at light delay. Entanglement is not a link. What counts as safe transit is unset. The safety margin is unset. What counts as a pre-mapped destination, and which survey maps it, are unset. Pinhole-probe verification follows IPLS-4.2-002. Its pass criteria are unset. The pinhole probe has no defining card. Command follows the IPLS-5.1-002 chart. An ASI is never an operator. Activation of a portal waits for operator consent under IPLS-5.1-002. Verification can block activation and cannot grant it. Whether transfer of a person through a portal is crew launch under IPLS-5.1-002 is unset. Dependence on PGEDS-v1 follows IPLS-3.1.6.1-001. PIS-v1 is an upgrade path. NWM-v1 has no defining card under IPLS-4.1-004. The Operator-Control Layer has no defining card. The 4.5 cards are not yet repaired. On loss of link, life-preserving functions continue inside the IPLS-5.1-002 envelope. The IPLS-3.1-014 hold applies to other actions. T is unset. What the current safe step is for a portal with a transfer in progress is unset. Paths per link are unset. The pass criteria for the end-to-end portal transit simulation and human-in-the-loop safety validation are unset.

Rationale: Enables practical interstellar civilisation while maintaining full human/post-biological command authority and multi-century safety margins.

Interfaces
PIS-v1, PGEDS-v1, NWM-v1, Operator-Control Layer
Verification Method
End-to-end portal transit simulation • Human-in-the-loop safety validation
Failure Modes & Mitigations
Unsafe folding event (mitigated by mandatory pinhole-probe gate and ethical kill-switch)
Dependencies
Portal Universal Interface (4.4.1), Frontier Technology Integration Framework (4.5)

Open Questions: None at v0.7

IPLS-IPLS-4.4-002 Maturity: D
Phase 4+

Mandatory Pinhole Probe Verification Protocol

Requirement: No full-scale portal activation or warp bubble formation shall occur without prior deployment and successful return of a pinhole probe swarm confirming safe spacetime metric conditions. Pinhole-probe verification follows IPLS-4.2-002. Its pass criteria are unset. What counts as probe return is unset. The pinhole probe has no defining card. The probe data interface is unset. Verification can block portal activation and warp bubble formation and cannot grant either. Activation of a portal waits for operator consent under IPLS-5.1-002. Whether warp activation is an irreversible act under IPLS-5.1-002 is unset under IPLS-4.1-009. N for the probe swarm is unset. The fallback protocols are unset. The interval within which verification must precede activation is unset. Whether one verification covers one activation or a destination is unset. The pass criterion for probe swarm deployment and metric validation testing is unset.

Rationale: Provides the critical safety data required before any spacetime manipulation event.

Interfaces
NWM-v1, PIS-v1, Operator-Control Layer
Verification Method
Probe swarm deployment and metric validation testing
Failure Modes & Mitigations
Incomplete metric data (mitigated by redundant probe swarm and fallback protocols)
Dependencies
IPLS-4.4-001

Open Questions: None at v0.7

IPLS-IPLS-4.4-003 Maturity: D
Phase 4+

IPLS-NWM-v1 Nacelle Warp Integration

Requirement: Portals shall utilise discrete cylindrical IPLS-NWM-v1 nacelles (n = 2–4) in equatorial ring layout, hot-swappable via PIS-v1, producing interior-flat bubbles with tidal forces < 10⁻⁶ g. NWM-v1 has no defining card under IPLS-4.1-004. NWM-v1 promotion to this section is unset. The 4.5 cards are not yet repaired. Nacelle integration uses UMP-PROP-001. Hot-swap follows UMP-HOTSWAP-001. PIS-v1 is an upgrade path. Dependence on PGEDS-v1 follows IPLS-3.1.6.1-001. The interior tidal limit is unset under IPLS-4.1-004. What counts as interior-flat is unset. The number of nacelles that may fail with the fold held or safely collapsed is unset. Whether a nacelle may be swapped with a bubble formed is unset. Whether automatic nacelle shutdown is inside the IPLS-5.1-002 envelope is unset. A kill-switch follows IPLS-3.1-008. The pass criterion for nacelle warp bubble formation and stability testing is unset.

Rationale: Provides the primary engineering implementation for all spacetime-folding operations.

Interfaces
NWM-v1, PIS-v1, PGEDS-v1
Verification Method
Nacelle warp bubble formation and stability testing
Failure Modes & Mitigations
Tidal force exceedance (mitigated by independent nacelle control and automatic shutdown)
Dependencies
Frontier Technology Integration Framework (4.5)

Open Questions: None at v0.7

IPLS-IPLS-4.4-004 Maturity: D
Phase 4+

PGEDS-v1 Portal-Scale Power Substrate

Requirement: All portal operations shall draw from dedicated PGEDS-v1 micro-modular arrays delivering minimum 10 PW burst per nacelle with triple-redundant failover. Burst power per nacelle is unset under IPLS-4.1-004. Burst duration and energy per activation are unset. N for portal power failover is unset. Power follows UMP-PWR-001 up to its port rating, which is unset. The interface for generation above that rating is unset under IPLS-3.1.6-002. Which PGEDS-v1 sources a portal may depend on is unset. Dependence on PGEDS-v1 follows IPLS-3.1.6.1-001. Life support is a separate fail-operational path under IPLS-5.1-002. Which loads automatic load shedding may shed is unset. What a power loss does to an active bubble is unset. The pass criterion for portal power burst and failover testing is unset.

Rationale: Ensures sufficient energy for stable spacetime folding while maintaining fail-operational power distribution.

Interfaces
PGEDS-v1, UMP-PWR-001
Verification Method
Portal power burst and failover testing
Failure Modes & Mitigations
Power shortfall (mitigated by N+3 redundancy and automatic load shedding)
Dependencies
Power Generation & Energy Distribution (3.1.6.1)

Open Questions: None at v0.7

IPLS-IPLS-4.4-005 Maturity: D
Phase 4+

Operator-Controlled Activation & Ethical Kill-Switch

Requirement: All portal and warp activation sequences shall require explicit operator consent, with independent ethical kill-switches and sentience monitoring active at every stage. What counts as activation of a portal is unset. The stages of an activation sequence are unset. Whether one consent covers one activation, several, or a link held open is unset. Activation of a portal waits for operator consent under IPLS-5.1-002. Command follows the IPLS-5.1-002 chart. An ASI is never an operator. The holder follows the IPLS-5.1-002 succession. A seized credential is not consent. Oversight is at light delay. Whether warp activation is an irreversible act under IPLS-5.1-002 is unset under IPLS-4.1-009. A kill-switch follows IPLS-3.1-008. Kill-switch reset waits for operator consent under IPLS-5.1-002. What a kill-switch stop does to an active bubble is unset under IPLS-4.1-009. What a kill-switch stop does to a transfer in progress is unset. Who may trigger a kill-switch is unset. The interface follows UMP-OPERATOR-001, which does not define it. The Operator-Control Layer has no defining card. The kill-switch latency figure is unset. Whether the kill-switch path is independent of the function it stops is unset. N for the kill-switch path is unset. Whether activation may proceed with sentience monitoring degraded or failed is unset. Monitoring follows IPLS-3.1.21-001. Escalation on detection follows IPLS-3.1.21-003. What halt means for a portal is unset. The pass criterion for operator consent and kill-switch latency testing is unset.

Rationale: Prevents any non-consensual or unsafe use of frontier spacetime technology.

Interfaces
UMP-OPERATOR-001, Ethical Frameworks (5.1), Sentience Emergence Framework (3.1.21)
Verification Method
Operator consent and kill-switch latency testing
Failure Modes & Mitigations
Unauthorised activation (mitigated by hardware-level consent gate)
Dependencies
UMP-OPERATOR-001

Open Questions: None at v0.7

IPLS-IPLS-4.4-006 Maturity: D
Phase 4+

Fail-Operational Portal Safety Architecture

Requirement: Portals shall incorporate triple-redundant nacelle control, independent fail-operational shutdown per nacelle, and automatic reversion to safe metric state on any anomaly. What counts as an anomaly is unset. The safe metric state is unset. Whether automatic reversion is inside the IPLS-5.1-002 envelope is unset. Activation after reversion waits for operator consent under IPLS-5.1-002. Whether triple redundancy is per nacelle or per portal is unset. What reversion does to a transfer in progress is unset. Whether nacelle control is separate from the command path under IPLS-5.1-002 is unset. What counts as isolation between redundant paths is unset. The pass criterion for fail-operational shutdown and recovery testing is unset.

Rationale: Guarantees crew and asset safety even during partial system failures.

Interfaces
NWM-v1, PGEDS-v1
Verification Method
Fail-operational shutdown and recovery testing
Failure Modes & Mitigations
Cascading failure (mitigated by fully isolated redundant paths)
Dependencies
IPLS-4.4-003

Open Questions: None at v0.7

IPLS-IPLS-4.4-007 Maturity: D
Phase 4+

PIS-v1 Universal Interface Compliance

Requirement: All portal hardware shall comply with the binding open-standard Universal Portal Interface Specification (PIS-v1), including mechanical, power, data, fluid, and command hardpoints. PIS-v1 is an upgrade path. The 4.4.1 cards are not yet repaired. Where PIS-v1 does not apply, interfaces follow IPLS-3.1.19-001. The command hardpoint follows UMP-OPERATOR-001, which does not define it. The pass criterion for PIS-v1 compliance matrix testing is unset.

Rationale: Guarantees zero vendor lock-in and seamless integration with every IPLS asset.

Interfaces
PIS-v1 (4.4.1)
Verification Method
Full PIS-v1 compliance matrix testing
Failure Modes & Mitigations
Interface mismatch (mitigated by strict PIS-v1 certification)
Dependencies
Portal Universal Interface (4.4.1)

Open Questions: None at v0.7

IPLS-IPLS-4.4-008 Maturity: D
Phase 4+

Multi-Century Portal Durability & TSP-v1 Readiness

Requirement: Portal systems shall be designed for ≥200-year service life with graceful degradation, field-repairable via ISRU spares, and pre-engineered TSP-v1 supersession pathways. Service life follows UMP-DURABILITY-001. Whether a portal element is life-critical is unset. Life-critical systems remain at the 500-year figure in IPLS-3.1-016. Whether the figure in this card applies to the portal or to each element is unset. ISRU spares are IPLS-3.1-009 output. The spares a portal carries before Phase 3 at that body are unset. Degradation order and the output floor are unset. Whether a degraded portal may be activated is unset. Each replication cycle waits for operator consent under IPLS-5.1-002. Whether a repair that fabricates a module is replication is unset. Supersession waits for operator consent under IPLS-5.1-002. TSP-v1 readiness criteria are undefined under IPLS-3.1-016. Whether IPLS-5.1-006 legacy-support mode applies is unset. Version changes follow IPLS-3.1.19-002. The pass criteria for accelerated life testing and TSP-v1 retrofit simulation are unset.

Rationale: Ensures portals remain operational and upgradable across centuries as spacetime-folding technology evolves.

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

Open Questions: None at v0.7

IPLS-IPLS-4.4-009 Maturity: D
Phase 4+

PIS-v1 Universal Interface Compliance for All Portal Operations

Requirement: All portal hardware and nacelle warp modules shall fully comply with the binding open-standard Universal Portal Interface Specification (PIS-v1), including mechanical, power, data, fluid, and command hardpoints for seamless integration with every IPLS asset. Portal hardware, including nacelle warp modules, follows IPLS-4.4-007. The interoperability test set and pass criterion are unset under IPLS-3.1.19-001. The node list is unset.

Rationale: Guarantees zero vendor lock-in, full interoperability, and operator-controlled modularity across the entire interstellar network.

Interfaces
PIS-v1 (4.4.1), Universal Modular Platforms (3.2)
Verification Method
Full PIS-v1 compliance matrix testing • Cross-asset interoperability validation
Failure Modes & Mitigations
Interface mismatch (mitigated by mandatory PIS-v1 certification before deployment)
Dependencies
Portal Universal Interface (4.4.1)

Open Questions: None at v0.7

IPLS-IPLS-4.4-010 Maturity: D
Phase 4+

Portal Readiness & Operator Hand-Over Gate

Requirement: Full operational use of portals shall only commence after successful pinhole-probe verification, 180 days of continuous fail-operational testing, explicit operator consent, and integrated governance review. Activation of a portal waits for operator consent under IPLS-5.1-002. The automated gate can block portal use and cannot grant it. Command follows the IPLS-5.1-002 chart. An ASI is never an operator. Review follows IPLS-5.1-007. Whether review can block portal use is unset. Whether representatives' consent is also required is unset. The standing of a mind and the weight of its dissent are unset. What counts as full operational use is unset. The systems covered and the reset event for the 180 days are unset. Pinhole-probe verification follows IPLS-4.2-002. Its pass criteria are unset. Hand-over does not move command of irreversible acts off the IPLS-5.1-002 chart. What hand-over transfers is unset. Whether these criteria are the hand-over gate under IPLS-4.2-010 is unset. Whether transfer of a person through a portal is crew launch under IPLS-5.1-002 is unset. The Operator-Control Layer has no defining card. The pass criteria for the portal readiness gate simulation and governance review audit are unset.

Rationale: Ensures portals are verifiably safe and ethically aligned before being used for crewed or high-value transport.

Interfaces
Operator-Control Layer, Ethical Frameworks (5.1), Governance Frameworks (3.1.11)
Verification Method
Portal readiness gate simulation • Human-in-the-loop operational audit
Failure Modes & Mitigations
Premature activation (mitigated by hard automated gate and multi-stakeholder consent)
Dependencies
All prior 4.4 items, Ethical Frameworks (5.1)

Open Questions: None at v0.7