USP RESTRICTED — CARG OPERATIONAL USE ONLY ATH-EQ-005
equipment

Praetorian MK1 — SLIP Variant

Lightest configuration. Highest mobility. Built for speed and flanking. What it sacrifices in protection it earns back in unpredictability.

Document TypeTechnical Specification — Variant Configuration DesignationPraetorian MK1 — SLIP OperatorSLIP ConfigurationMinimum armour, maximum mobility Internal Schematics

Configuration Overview

The SLIP variant is the lightest configuration of the Praetorian MK1 — minimum armour plating, reduced mass across all non-essential structural elements, and mobility systems optimised for maximum speed and agility. It is the fastest suit in the deployment by a significant margin.

Configuration Trade-offs

Factor Assessment
Armour protection Reduced — surface plating at minimum viable thickness
Operational speed Maximum — highest velocity in the squad
Flanking capability Exceptional — can reach and hold positions unavailable to heavier variants
Sustained fire resistance Limited — not built to absorb; built to not be present when fire arrives

Full mobility and armour specification:

Operational Logic

The SLIP variant makes a specific calculation: that an operator who is difficult to anticipate and impossible to catch is more survivable than one built to absorb fire standing still. This is validated in the operator selection profile.

Whether it holds in the specific terrain and engagement conditions of Athena — dense jungle, limited sightlines, close-quarters contact — is an open question.

Operator Profile

Worn by SLIP — the squad's most mobile element. Lean, fast, and deceptive in profile. The suit was built for this operator. The operator was selected for this suit. The distinction between the two is not operationally significant.

// Viewer Access +

The SLIP variant's operational logic — that speed is the defence — was designed for open terrain. Athena is predominantly dense jungle with severely limited sightlines. The environment for which the suit calculates best survivability is not the environment it is being deployed into. This discrepancy was in the briefing documents. It did not change the deployment decision.