Home › Master Spec › On-Site Manufacturing & Shipyard Facilities
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)
Section 3.1.13 • 01 May 2026

On-Site Manufacturing & Shipyard Facilities

Internal factories and shipyards using local ISRU materials

Fully integrated with IPLS-SRS-v1 self-replicating systems, Universal Modular Platforms (3.2), PGEDS-v1 power, and all frontier technologies for autonomous, operator-controlled local production and expansion.

Inter-Planetary Link Ship • Guildford, Surrey, UK

1. Purpose

To define the functional requirements for fully autonomous, on-site manufacturing and shipyard facilities inside hollowed asteroid bases and orbital platforms, enabling rapid production of vessels, habitats, and infrastructure using only local ISRU resources while maintaining full operator control and multi-century reliability.

2. Core Design Principles

  • PIS-v1 is an upgrade path. PGEDS-v1 dependence follows IPLS-3.1.6.1-001.
  • 100 % ISRU feedstock utilisation — no Earth-sourced materials required after initial seed delivery.
  • Integration with IPLS-SRS-v1 self-replicating systems for exponential scaling of production capacity.
  • Full robotics tiering, sentience monitoring, and operator command authority (3.1.20–3.1.22).

3. Frontier Technology Integration

3.1 Self-Replicating Manufacturing (IPLS-SRS-v1)

Functional Requirements — On-Site Replication & Production (IPLS-SRS-MFG-v1)

  • Tiered von Neumann manufacturing cells that replicate themselves and expand factory floor space using local regolith/asteroid material.
  • Operator consent required before each replication cycle; immediate halt on any sentience detection (3.1.21).
  • Hot-swappable production modules via internal docking and transport systems (3.1.7 & 3.1.8).

3.2 Shipyard & Vessel Construction

Functional Requirements — Internal Shipyard Bays

  • Large internal bays sized for generation-ship and colony-seeding-ship construction (Section 4.1 & 3.1.17).
  • Nacelle integration uses UMP-PROP-001. PIS-v1 is an upgrade path. Whether NWM-v1 is a dependency at Lane B is unset.
  • Automated assembly lines powered by dedicated PGEDS-v1 micro-grids with triple-redundant failover.

3.3 Shielding, Power & Portal Readiness

Functional Requirements — Manufacturing Resilience

  • RSS-v1 is an upgrade path.
  • FPL-v1 is an upgrade path. Design updates use the 3.1.19 network at light delay.
  • TSP-v1 supersession readiness — all manufactured assets designed for future upgrades without decommissioning.

4. Operational Sequence

  1. Initial seed factory delivered via colony-seeding ships or mining fleet.
  2. ISRU feedstock processing begins; SRS-v1 replication expands production capacity exponentially under operator oversight.
  3. Parallel construction of vessels, habitats, and infrastructure components.
  4. Quality assurance, testing, and handover to fleet operations or colony expansion teams.

5. Ethical & Safety Guardrails

All manufacturing and replication operations remain under explicit operator consent (Section 5.1). Sentience safeguards, ethical kill-switches, and cultural continuity protocols are embedded at the hardware level.

Living Document v0.7 • 01 May 2026 • Ready for immediate ASI implementation
IPLS-IPLS-3.1.13-001 Maturity: B
Phase 4

On-Site Manufacturing & Shipyard Mandate

Requirement: Autonomous operation acts inside the IPLS-5.1-002 envelope and is logged and reported to the operator. Irreversible acts follow IPLS-5.1-002. Feedstock is IPLS-3.1-009 output. Allocation follows IPLS-3.1-019. The product list and the largest vessel class produced are unset. Power to manufacturing hardpoints follows IPLS-3.1.6-006. Load shedding follows IPLS-3.1.6-003. Whether producing a weapon module waits for operator consent is unset. N per production function is unset.

Rationale: Eliminates Earth dependency and enables exponential local growth once the base is operational.

Interfaces
Universal Modular Platforms (3.2), UMP-MECH-001, PGEDS-v1, IPLS-SRS-v1
Verification Method
Digital-twin manufacturing simulation • Physical prototype production run
Failure Modes & Mitigations
Production halt (mitigated by N+3 redundancy and hot-swappable cells)
Dependencies
Hollowed Asteroid Bases (3.1.4), On-Site ISRU (3.1)

Open Questions: None at v0.7

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

Self-Replicating Manufacturing Cells (IPLS-SRS-MFG-v1)

Requirement: SRS-v1 promotion to this section is unset. IPLS-SRS-MFG-v1 has no defining card. Each replication cycle waits for operator consent under IPLS-5.1-002. What counts as one cycle is unset. On sentience detection the IPLS-5.1-003 halt applies. The 3.1.20 tier of replicating cells is unset. Feedstock is IPLS-3.1-009 output. Allocation follows IPLS-3.1-019. The capacity ceiling and the simulation pass criterion are unset.

Rationale: Enables exponential scaling of manufacturing output without Earth resupply.

Interfaces
IPLS-SRS-v1, UMP-ROBOTIC-001, Operator-Control Layer
Verification Method
Replication cycle testing • Digital-twin exponential growth simulation
Failure Modes & Mitigations
Uncontrolled replication (mitigated by hard operator consent gate and sentience halt)
Dependencies
IPLS-SRS-v1, IPLS-3.1.13-001

Open Questions: None at v0.7

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

Internal Shipyard Bays

Requirement: Bay excavation and enlargement follow IPLS-3.1.4-001 and IPLS-3.1.4-006. The vessel classes built and the bay dimensions are unset. Nacelle integration uses UMP-PROP-001. PIS-v1 is an upgrade path. Whether NWM-v1 is a dependency at Lane B is unset. Colony-seeding-ship construction follows IPLS-3.1-015. Whether generation-ship construction waits for operator consent is unset. Fitting a weapon module follows IPLS-3.1.7-004.

Rationale: Turns the base into a true shipyard capable of building the next wave of interstellar assets on-site.

Interfaces
UMP-PROP-001, PIS-v1, UMP-MECH-001
Verification Method
Shipyard bay scale simulation • Vessel assembly validation
Failure Modes & Mitigations
Bay capacity shortfall (mitigated by modular expansion corridors)
Dependencies
IPLS-3.1.13-001

Open Questions: None at v0.7

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

Automated Additive & Subtractive Manufacturing

Requirement: The materials list, tolerances, and production-rate targets are unset. Gravity follows IPLS-3.1.4-002. The gravity condition in manufacturing zones is unset. Whether manufacturing volumes share atmosphere with occupied volumes is unset. Automatic isolation follows IPLS-3.1.5-006. Quality control follows IPLS-3.1.13-007.

Rationale: Provides rapid, on-demand production of spare parts, tools, and structural components.

Interfaces
UMP-ROBOTIC-001, UMP-THERMAL-001
Verification Method
Material property testing • Production speed and accuracy validation
Failure Modes & Mitigations
Material defects (mitigated by in-process quality control)
Dependencies
IPLS-3.1.13-001

Open Questions: None at v0.7

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

Hot-Swap Production Module Compatibility

Requirement: Hot-swap follows UMP-HOTSWAP-001. A swap that supersedes equipment waits for operator consent under IPLS-5.1-002. Whether like-for-like replacement is supersession is unset. A swap that adds replication capability follows IPLS-3.1.13-002. N per production function is unset.

Rationale: Maximises uptime and allows continuous reconfiguration as technology advances.

Interfaces
UMP-HOTSWAP-001
Verification Method
Live hot-swap production testing
Failure Modes & Mitigations
Production interruption (mitigated by redundant parallel lines)
Dependencies
Universal Modular Platforms (3.2)

Open Questions: None at v0.7

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

Operator Control & Manual Override in Manufacturing

Requirement: Critical manufacturing functions shall expose physical overrides. Their use follows IPLS-3.1.4-007. Telemetry goes to the command node on the 3.1.19 network. On loss of link, life-preserving functions continue inside the IPLS-5.1-002 envelope and other actions follow the IPLS-3.1-014 hold. T is unset. The safe step for a replication cycle or vessel assembly in progress is unset. Restarting replication after a halt is a replication and waits for operator consent. Kill-switch reset follows IPLS-3.1-008. The list of critical manufacturing functions beyond the three named is unset. Veto latency and reliability floor are unset.

Rationale: Preserves absolute human/post-biological command authority over self-replicating systems.

Interfaces
UMP-OPERATOR-001, IPLS-SRS-v1
Verification Method
Human-in-the-loop override testing
Failure Modes & Mitigations
Automation lockout (mitigated by physical interlocks)
Dependencies
UMP-OPERATOR-001

Open Questions: None at v0.7

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

Quality Assurance & Certification Layer

Requirement: Which component classes need operator sign-off, and who may sign the rest, are unset. An ASI does not give operator verification. On loss of link, integrating a part needed to preserve life proceeds inside the IPLS-5.1-002 envelope and is logged and reported. Whether operator verification follows when the link returns is unset. Acceptance criteria per component class and the certification stages are unset. Records are append-only. A correction is a new entry. The record store, its node count and location, and which copy governs during loss of link are unset.

Rationale: Ensures safety and reliability of all locally manufactured assets.

Interfaces
UMP-DIAG-001, Operator-Control Layer
Verification Method
End-to-end QA workflow testing
Failure Modes & Mitigations
Defective parts entering service (mitigated by multi-stage certification)
Dependencies
IPLS-3.1.13-004

Open Questions: None at v0.7

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

Multi-Century Manufacturing Durability & TSP-v1 Readiness

Requirement: Service life follows IPLS-3.1-016. Life-critical systems remain at the 500-year figure in IPLS-3.1-016. Whether manufacturing elements that produce life-critical spares are life-critical is unset. Supersession waits for operator consent under IPLS-5.1-002. TSP-v1 readiness criteria are undefined. Degradation order, the parts repairable from ISRU spares, and the life-test acceleration basis are unset.

Rationale: Supports continuous local production as frontier manufacturing technologies evolve.

Interfaces
TSP-v1, UMP-DURABILITY-001
Verification Method
Accelerated life testing • TSP-v1 retrofit simulation
Failure Modes & Mitigations
Irreparable obsolescence (mitigated by modular design)
Dependencies
All prior 3.1.13 items

Open Questions: None at v0.7

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

Seamless Integration with Internal Logistics and Docking

Requirement: Tube routing follows IPLS-3.1.8-002. Receipt and airlocks follow IPLS-3.1.7-005. Allocation follows IPLS-3.1-019. The minimum route count from manufacturing to each zone is unset. Crew launch of a produced vessel waits for operator consent under IPLS-5.1-002. Whether release of an uncrewed vessel waits for operator consent is unset.

Rationale: Creates an efficient closed-loop production ecosystem inside the base.

Interfaces
Internal Transportation (3.1.8), Docking Facilities (3.1.7), UMP-CARGO-001
Verification Method
Integrated logistics flow simulation
Failure Modes & Mitigations
Material flow bottleneck (mitigated by redundant pathways)
Dependencies
IPLS-3.1.8, IPLS-3.1.7

Open Questions: None at v0.7

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

Manufacturing Readiness & Hand-Over Gate

Requirement: Pass criteria and the reset event for the 180 days are unset. Whether the count runs with the IPLS-3.1-018 count is unset. What may run during the 180 days is unset. Replication during it follows IPLS-3.1.13-002. The automated gate can block and cannot grant. Hand-over does not move command of irreversible acts off the IPLS-5.1-002 chart. Governance integration follows IPLS-3.1.11-008.

Rationale: Ensures the facility is verifiably reliable before being used for critical production.

Interfaces
Operator-Control Layer, Governance Frameworks (3.1.11)
Verification Method
180-day autonomous operations audit
Failure Modes & Mitigations
Premature activation (mitigated by hard readiness gate)
Dependencies
All prior 3.1.13 items

Open Questions: None at v0.7