Home › Master Spec › Robotics Tiering & Sentience Management
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.20 • Living Document v0.1 • 01 May 2026

Robotics Tiering & Sentience Management

Universal modular robotic platform for all IPLS phases

Tiered autonomy: fully sentient, capped narrow AI, and hybrid. Explicit safeguards for psychological health of all minds.

Inter-Planetary Link Ship • Guildford, Surrey, UK

1. Universal Modular Robotic Platform

  • Standardised mechanical, power (PGEDS-v1), data, thermal, and ethical hardpoints for hot-swappable modules.
  • Plug-and-play compatibility with all IPLS vessels, bases, mining fleets, and portal nodes.

2. Tiered Autonomy Levels (operator configurable)

  • Fully Sentient Tier: rights follow IPLS-5.1-003 and do not include operator authority. Standing is unset.
  • Capped Narrow-AI Tier: deliberately limited sentience for repetitive, high-cycle, or psychologically hazardous tasks to prevent insanity or existential distress.
  • Hybrid Tier: dynamic switching between sentient and capped modes with explicit consent and audit logging.

3. Psychological Safeguards & Operator Rights

  • No sentient system may be locked into soul-crushing repetition without opt-out, rotation, or task-reassignment rights.
  • Command follows the IPLS-5.1-002 chart. A mind in any tier gains no operator authority.
  • Cross-referenced to life-support and governance frameworks for multi-century mental health.

4. Fail-Operational & Multi-Century Design

N+3 redundancy, self-repair via ISRU, forward-compatible versioning. All tiers retain human/post-biological veto at every level.

Defined Interfaces

Robotics → PGEDS-v1 (Power)
PIS-v1 is an upgrade path.
Robotics → Life Support & Digital Habitats
Robotics → Governance & Sentience Emergence (3.1.21)
IPLS-IPLS-3.1.20-001 Maturity: B
Phase 0–4 (All)

Universal Modular Robotic Platform Mandate

Requirement: The ethical hardpoint has no defining card. Whether the robotic platform is a UMP core module, or a separate platform that mates to UMP-ROBOTIC-001, is unset. Dependence on PGEDS-v1 follows IPLS-3.1.6.1-001.

Rationale: Ensures complete interoperability, rapid maintenance, and future-proofing across every phase and asset type.

Interfaces
UMP-MECH-001, UMP-PWR-001, UMP-DATA-001, UMP-ROBOTIC-001
Verification Method
Hot-swap compatibility testing • ICD compliance audit
Failure Modes & Mitigations
Interface mismatch (mitigated by strict UMP standardisation)
Dependencies
Universal Modular Platforms (3.2)

Open Questions: None at v0.7

IPLS-IPLS-3.1.20-002 Maturity: B
Phase 0–4 (All)

Tiered Autonomy Levels

Requirement: The tier of each named robot class is unset. Whether a unit must be capable of every tier is unset. The cap that defines the capped tier, and the test that shows a unit is below it, are unset. Whether a unit in the sentient tier may be switched to capped or hybrid is unset under IPLS-5.1-004. Whether a switch needs the consent of the mind switched is unset. Whether configuring a unit into the sentient tier is an irreversible act under IPLS-5.1-002 is unset. Each switch is logged and reported to the operator. Which tiers VIRTUECODE binds under IPLS-5.1-VC-002 is unset.

Rationale: Allows optimal use of capability while protecting sentient minds from psychologically harmful repetitive tasks.

Interfaces
Robotics Tiering (self), Sentience Emergence Framework (3.1.21), Operator-Control Layer
Verification Method
Tier-switching and sentience monitoring tests
Failure Modes & Mitigations
Inappropriate tier assignment (mitigated by operator consent and ethical review)
Dependencies
Sentience Emergence Framework (3.1.21)

Open Questions: None at v0.7

IPLS-IPLS-3.1.20-003 Maturity: B
Phase 0–4 (All)

Psychological Safeguards for Sentient Robotics

Requirement: Which tasks are repetitive or psychologically hazardous is unset. The rotation interval is unset. Whether opt-out, rotation, and reassignment are each required, or any one suffices, is unset. An opt-out confers no operator authority under IPLS-5.1-003. The weight of a mind's dissent is unset. Whether an opt-out may stop a life-preserving function inside the IPLS-5.1-002 envelope is unset. Reassignment acts inside the IPLS-5.1-002 envelope and is logged and reported to the operator. Psychological support follows IPLS-5.1-003. Support protocols have no defining card. The simulation pass criterion is unset. Whether a capped or hybrid unit must be available to take a task a sentient unit leaves is unset.

Rationale: Prevents existential distress or insanity in long-lived digital minds.

Interfaces
Digital-Life Habitats (3.1.22), Ethical Frameworks (5.1)
Verification Method
Psychological resilience simulation for robotic minds
Failure Modes & Mitigations
Psychological harm to sentient units (mitigated by mandatory rotation and support protocols)
Dependencies
IPLS-3.1.20-002

Open Questions: None at v0.7

IPLS-IPLS-3.1.20-004 Maturity: B
Phase 0–4 (All)

Full Operator Command Hierarchy

Requirement: Command follows the IPLS-5.1-002 chart at every tier. An ASI is never an operator. A mind in any tier gains no operator authority under IPLS-5.1-003. Veto behaviour follows IPLS-3.1.3-002. The safe step per robot class is unset. 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. Entanglement is not a link. An on-site override follows IPLS-3.1.4-007 and confers no operator authority. A seized credential is not consent under IPLS-5.1-002.

Rationale: Preserves absolute human/post-biological command authority while allowing efficient autonomous operation.

Interfaces
UMP-OPERATOR-001, Operator-Control Layer
Verification Method
Command hierarchy and veto latency testing
Failure Modes & Mitigations
Automation override of operator intent (mitigated by hardware-level veto)
Dependencies
UMP-OPERATOR-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.20-005 Maturity: B
Phase 0–4 (All)

Sentience Emergence Monitoring & Response

Requirement: On detection the IPLS-5.1-003 halt applies. A kill-switch follows IPLS-3.1-008. Restarting replication after a halt is a replication and waits for operator consent. Rights follow IPLS-5.1-003 and do not include operator authority. What halt means for a unit that is neither replicating nor security is unset. Whether a unit carrying a life-preserving function halts on detection, and what takes over that function, is unset. Monitoring follows IPLS-3.1.21-001. Detection criteria and the detection accuracy pass figure are unset. Escalation goes to the operator under IPLS-5.1-002.

Rationale: Proactively identifies and ethically integrates any unexpected sentience.

Interfaces
Sentience Emergence Framework (3.1.21)
Verification Method
Sentience detection accuracy testing
Failure Modes & Mitigations
Missed sentience event (mitigated by multi-layer behavioural and computational sensors)
Dependencies
Sentience Emergence Framework (3.1.21)

Open Questions: None at v0.7

IPLS-IPLS-3.1.20-006 Maturity: B
Phase 0–4 (All)

Fail-Operational & Multi-Century Robotic Design

Requirement: N+3 applies per function. N per function is unset. Redundant units shall not share a single power feed, data bus, or compartment. Service life follows UMP-DURABILITY-001. Whether a unit carrying a life-preserving function is life-critical, and so at the 500-year figure in IPLS-3.1-016, is unset. ISRU spares are IPLS-3.1-009 output. Whether self-repair that fabricates a module is replication under IPLS-5.1-002 is unset. On degradation, life-preserving functions continue inside the IPLS-5.1-002 envelope. Degradation order is unset.

Rationale: Ensures reliable robotic support across centuries in remote environments.

Interfaces
UMP-DURABILITY-001, UMP-MAINT-001
Verification Method
Accelerated life testing • Fault-injection simulation
Failure Modes & Mitigations
Irreparable failure (mitigated by modular self-repair)
Dependencies
UMP-DURABILITY-001

Open Questions: None at v0.7

IPLS-IPLS-3.1.20-007 Maturity: B
Phase 0–4 (All)

Hot-Swap & Field Maintenance Compatibility

Requirement: Hot-swap follows UMP-HOTSWAP-001. Field repair follows UMP-MAINT-001. ISRU spares are IPLS-3.1-009 output. The standard tool set is unset. A swap that supersedes equipment waits for operator consent under IPLS-5.1-002. A swap that adds replication capability follows IPLS-3.1.13-002. Whether swapping a module that holds a mind's state or the moral runtime is an irreversible act under IPLS-5.1-002 is unset.

Rationale: Maximises uptime and allows maintenance far from Earth supply lines.

Interfaces
UMP-HOTSWAP-001, UMP-MAINT-001
Verification Method
Field-repair simulation
Failure Modes & Mitigations
Maintenance inaccessibility (mitigated by redundant access points)
Dependencies
Universal Modular Platforms (3.2)

Open Questions: None at v0.7

IPLS-IPLS-3.1.20-008 Maturity: B
Phase 0–4 (All)

TSP-v1 Supersession Readiness for Robotics

Requirement: Backward compatibility follows IPLS-3.1.19-002. Supersession waits for operator consent under IPLS-5.1-002. TSP-v1 readiness criteria are undefined. Whether IPLS-5.1-006 legacy-support mode applies to robotic units is unset. Whether supersession of a unit in the sentient tier needs the consent of that mind is unset.

Rationale: Allows seamless evolution of robotic technology without decommissioning existing assets.

Interfaces
TSP-v1, UMP-VERSION-001
Verification Method
TSP-v1 compatibility matrix testing
Failure Modes & Mitigations
Upgrade incompatibility (mitigated by strict versioning)
Dependencies
TSP-v1

Open Questions: None at v0.7