Home › Master Spec › Base Security, Defense & Marshall Service Systems
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.15 • 01 May 2026

Base Security, Defense & Marshall Service Systems

Internal security, patrol craft, defensive systems, and marshall-service operations

The requirement cards on this page govern. Command linkage uses 3.1.19 at light delay. FPL-v1 is an upgrade path. Whether lethal effect is permitted at any tier is unset.

Inter-Planetary Link Ship • Guildford, Surrey, UK

1. Purpose

To define the functional requirements for comprehensive, fail-operational security, defense, and marshall-service systems inside hollowed asteroid bases, orbital platforms, and colonies — ensuring protection of life, property, and infrastructure while preserving full human/post-biological command authority and ethical oversight.

2. Core Design Principles

  • Universal Modular Platform (3.2) compliance with PIS-v1 and PGEDS-v1 hardpoints for all security assets.
  • Whether lethal effect is permitted at any tier is unset. Command of irreversible acts follows IPLS-5.1-002.
  • Integration with IPLS-SRS-v1 for self-replicating patrol and response swarms.
  • Full robotics tiering, sentience emergence monitoring, and ethical kill-switch capability (3.1.20–3.1.21).

3. Frontier Technology Integration

3.1 Self-Replicating Security Swarms (IPLS-SRS-SEC-v1)

Functional Requirements — Autonomous Patrol & Response

  • Tiered von Neumann security drones manufactured on-site from ISRU materials.
  • Replication only under explicit operator or marshall-service command; immediate halt on sentience detection.
  • Hot-swappable via internal docking facilities (3.1.7) and maglev transport (3.1.8).

3.2 Patrol Craft & Defensive Systems

Functional Requirements — Mobile & Fixed Assets

  • Light patrol craft powered by IPLS-NWM-v1 nacelles for rapid intra-base and near-field response.
  • Full IPLS-RSS-v1 hybrid shielding on all vessels and fixed defensive emplacements.
  • Non-lethal and scalable response tiers (warning, containment, disablement) with ethical oversight.

3.3 Portal & Network Integration (FPL-v1 + TSP-v1)

Functional Requirements — Command & Supersession Readiness

  • Real-time command linkage to Sol network and sister colonies via IPLS-FPL-v1.
  • TSP-v1 supersession protocol pre-engineered for future defensive technology upgrades without asset retirement.
  • Marshall Service coordination across the entire interstellar network (Long-Term Expansion 4.3).

4. Operational Sequence

  1. Continuous automated monitoring via SRS-v1 sensor swarms.
  2. Escalation to marshall-service patrol craft on operator or AI-assisted alert.
  3. Defensive activation only after ethical review and explicit command authority.
  4. Each incident is reported to the operator on the 3.1.19 network at light delay. FPL-v1 is an upgrade path.

5. Ethical & Safety Guardrails

The requirement cards govern. Whether lethal effect is permitted at any tier is unset. An emergent mind does not gain operator authority.

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

Base Security, Defense & Marshall Service Mandate

Requirement: The system is that in IPLS-3.1.15-002 to IPLS-3.1.15-010. Operator means the IPLS-5.1-002 operator. Irreversible acts follow IPLS-5.1-002. Who may act as a marshall, and what a marshall may direct, are unset. A marshall may deploy an existing unit, not copy one, under IPLS-3.1-013. The role confers no operator authority. RSS-v1 is an upgrade path under IPLS-3.1.4-005. SRS-v1 promotion to this section is unset. N per security function is unset. Whether security functions sit on the command path under IPLS-5.1-002 is unset.

Rationale: Protects life, property, and infrastructure while preserving human/post-biological command authority at every level.

Interfaces
UMP-OPERATOR-001, IPLS-SRS-v1, RSS-v1, Ethical Frameworks (5.1)
Verification Method
Integrated security simulation • Human-in-the-loop ethical review
Failure Modes & Mitigations
Security breach (mitigated by layered autonomous + operator-controlled response)
Dependencies
Hollowed Asteroid Bases (3.1.4), Ethical Frameworks (5.1)

Open Questions: None at v0.7

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

Self-Replicating Security Swarms (IPLS-SRS-SEC-v1)

Requirement: Each replication cycle waits for operator consent under IPLS-5.1-002. A marshall may deploy an existing unit, not copy one, under IPLS-3.1-013. What counts as one cycle is unset. Autonomous response acts inside the IPLS-5.1-002 hostile-act envelope and is logged and reported to the operator. Pursuit is outside the envelope. Escalation beyond the envelope is unset. Response time is unset. IPLS-SRS-SEC-v1 has no defining card. The 3.1.20 tier of a security unit is unset. Whether production of a security unit by 3.1.13 is replication is unset. Whether producing a weapon module waits for operator consent is unset under IPLS-3.1.13-001.

Rationale: Enables scalable, self-sustaining internal security without Earth resupply.

Interfaces
IPLS-SRS-v1, UMP-ROBOTIC-001, Operator-Control Layer
Verification Method
Swarm replication and response testing • Sentience monitoring validation
Failure Modes & Mitigations
Uncontrolled replication (mitigated by hard operator consent gate and ethical kill-switch)
Dependencies
IPLS-SRS-v1

Open Questions: None at v0.7

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

Patrol Craft & Mobile Response Assets

Requirement: Response acts inside the IPLS-5.1-002 hostile-act envelope. Pursuit is outside the envelope. Force beyond the envelope is unset. Fitting a weapon module follows IPLS-3.1.7-004. Whether patrol craft carry crew is unset. Whether a crewed patrol sortie is a crew launch under IPLS-5.1-002 is unset. Nacelle integration uses UMP-PROP-001. Whether NWM-v1 is a dependency at Lane B is unset. RSS-v1 is an upgrade path under IPLS-3.1.4-005. Response time and near-field range are unset. The patrol zone list and N per patrol zone are unset.

Rationale: Delivers mobile, high-speed security capability inside and around the hollowed base.

Interfaces
NWM-v1, RSS-v1, UMP-PROP-001
Verification Method
Patrol craft operational testing • Response-time validation
Failure Modes & Mitigations
Vehicle loss (mitigated by redundant fleet and hot-swap capability)
Dependencies
IPLS-3.1.15-002

Open Questions: None at v0.7

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

Fixed Defensive Emplacements & Shield Integration

Requirement: Fitting a weapon module waits for operator consent under IPLS-5.1-002. Response acts inside the IPLS-5.1-002 hostile-act envelope. The escalation tiers, and who may order each, are unset. Escalation beyond the envelope is unset. Whether discharge of a fitted weapon falls within containment under IPLS-5.1-002 is unset. Whether lethal effect is permitted at any tier is unset. Ethical review follows IPLS-5.1-007. Power to defensive hardpoints follows IPLS-3.1.6-006. RSS-v1 is an upgrade path under IPLS-3.1.4-005. Panel overlap and N per emplacement are unset.

Rationale: Keeps command of irreversible acts on the IPLS-5.1-002 chart. Whether lethal effect is permitted is unset.

Interfaces
RSS-v1, UMP-SHIELD-001, Operator-Control Layer
Verification Method
Defensive system integration testing • Ethical escalation workflow audit
Failure Modes & Mitigations
Shielding gap (mitigated by overlapping panel design and real-time monitoring)
Dependencies
IPLS-3.1.15-003

Open Questions: None at v0.7

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

Portal & Network Command Integration (FPL-v1)

Requirement: Command linkage uses 3.1.19, not a portal, under IPLS-3.1-013. Relay follows IPLS-3.1.12-004. FPL-v1 and PIS-v1 are upgrade paths. Entanglement is not a link. Command of a base's security assets follows the IPLS-5.1-002 chart. Whether a remote marshall or colony may direct them is unset. A seized credential is not consent. 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.

Rationale: Provides command linkage at light delay.

Interfaces
FPL-v1, PIS-v1, Network Standards (3.1.19)
Verification Method
Portal-linked command latency testing
Failure Modes & Mitigations
Network isolation (mitigated by triple-redundant local fallback)
Dependencies
Long-Term Expansion (4.3)

Open Questions: None at v0.7

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

Sentience Safeguards & Ethical Kill-Switch

Requirement: On sentience detection the IPLS-5.1-003 halt applies. A kill-switch follows IPLS-3.1-008. Kill-switch reset waits for operator consent under IPLS-5.1-002. Which unit takes over a life-preserving action held by a halted asset is unset. Rights of an emergent mind follow IPLS-5.1-003 and do not include operator authority. Its standing is unset. Whether a halted mind may return to a security role, and on whose consent, is unset.

Rationale: Prevents unintended sentient systems from operating in security roles without full moral consideration.

Interfaces
Sentience Emergence Framework (3.1.21), Robotics Tiering (3.1.20)
Verification Method
Sentience detection and response testing
Failure Modes & Mitigations
Sentience oversight failure (mitigated by hardware-level kill-switch)
Dependencies
Sentience Emergence Framework (3.1.21)

Open Questions: None at v0.7

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

Operator Control & Manual Override Layer

Requirement: Critical security functions shall expose physical overrides. Their use follows IPLS-3.1.4-007. 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 an engagement in progress is unset. The list of critical security functions is unset. Veto latency and reliability floor are unset. Whether a veto can stop a life-preserving action already running is unset. A seized credential is not consent under IPLS-5.1-002. How a physical override is authenticated is unset.

Rationale: Keeps command of irreversible acts on the IPLS-5.1-002 chart.

Interfaces
UMP-OPERATOR-001
Verification Method
Human-in-the-loop override testing
Failure Modes & Mitigations
Automation lockout (mitigated by physical interlocks and audit logging)
Dependencies
UMP-OPERATOR-001

Open Questions: None at v0.7

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

Multi-Century 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 security elements are life-critical is unset. Supersession waits for operator consent under IPLS-5.1-002. TSP-v1 readiness criteria are undefined. The state a weapon hardpoint takes on degradation or loss of control is unset. Replication to restore a unit waits for operator consent under IPLS-5.1-002.

Rationale: Ensures long-term reliability of defense systems as frontier security technologies evolve.

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

Open Questions: None at v0.7

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

Post-Incident Logging, Reporting & Continuous Improvement

Requirement: Reporting uses 3.1.19, not a portal, under IPLS-3.1-013. Each incident is reported to the operator under IPLS-5.1-002. Relay follows IPLS-3.1.12-004. Records are append-only. A correction is a new entry. Preservation of logs is inside the IPLS-5.1-002 hostile-act envelope. The record store, its node count and location, and which copy governs during loss of link are unset. What counts as a security incident is unset. The review body and its time limit are unset. ASI analysis is advisory under IPLS-5.1-002.

Rationale: Enables continuous learning and improvement of security protocols across the entire interstellar network.

Interfaces
FPL-v1, UMP-DIAG-001, Governance Frameworks (3.1.11)
Verification Method
Incident simulation and logging audit • After-action review workflow test
Failure Modes & Mitigations
Incomplete records (mitigated by triple-redundant immutable logging)
Dependencies
All prior 3.1.15 items

Open Questions: None at v0.7

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

Security Systems Hand-Over & Readiness Gate

Requirement: Crew arrival follows IPLS-3.1.4-012. The 180-day count follows IPLS-3.1-018. Whether simulated operation counts toward it is unset. Pass criteria and the reset event for the 180 days are unset. The automated gate can block and cannot grant. Consent is the operator's under IPLS-5.1-002. Whether representatives are consulted, and the weight of their dissent, is unset. Hand-over does not move command of irreversible acts off the IPLS-5.1-002 chart. Governance review follows IPLS-3.1.11-008. What may run before the gate is unset. Integration from extraction follows IPLS-3.1-013.

Rationale: Ensures the security system is verifiably reliable and ethically aligned before permanent habitation.

Interfaces
Operator-Control Layer, Ethical Frameworks (5.1), Governance Frameworks (3.1.11), Hollowed Asteroid Bases (3.1.4)
Verification Method
Integrated security simulation • Human-in-the-loop readiness gate review
Failure Modes & Mitigations
Premature transition (mitigated by hard automated gate and multi-stakeholder consent)
Dependencies
All prior 3.1.15 items, Ethical Frameworks (5.1)

Open Questions: None at v0.7