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

Safe, instantaneous, operator-controlled travel between mapped destinations

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

To provide safe, instantaneous, operator-controlled spacetime folding portals for travel between pre-mapped destinations while maintaining full human/post-biological/ASI command authority, multi-century reliability, and zero vendor lock-in.

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).
  • Power substrate: PGEDS-v1 (Section 3.1.6.1) with minimum 10 PW burst capability and triple-redundant failover.
  • 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 & Redundancy: Triple-redundant nacelle control, independent fail-operational shutdown. Interior-flat condition enforced to <10⁻⁶ g tidal gradient. Pinhole probe verification mandatory.
  • 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)

All portal hardware shall comply with the binding open-standard Universal Portal Interface Specification (PIS-v1) detailed in Section 4.4.1.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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