Subject01
An unidentified entity located inside Vault 7 / Archive 07 of the UESC Marathon’s Cryo Archive (TCIV_M.CA); designated “Subject01” by UESC Security Forces; classified as connected to a “contact event”; described as an advanced, non-human species that repelled a fully-armed UESC assault team in under three minutes.
What the source establishes — canon
Designation and classification. UESC Security Forces refer to the entity exclusively as Subject01 (abbreviated S01 in tactical records); it is never given a name, species label, or other identifier in any captured volume.12 Cerberus’s threat-classification logic — which triggers the designation NUNAMNIR for any detected hostile that is not a Runner, not known fauna, and not a malfunctioning UESC unit — is the closest the source comes to formally categorizing entities like Subject01, though that volume does not name Subject01 directly.3
Location: Vault 7 / Archive 07. Subject01 is located inside the secure Cryo Archive region of the UESC Marathon, in the area UESC forces designate TCIV_M.CA. Specifically, the PRIMETIME operation targeted Vault 7 (also called Archive 07).2 The “First Contact” field alert places an unknown entity — designated only “remnant of contact event” at that point — in proximity to Lab 06 and Archive 07 before the S01 designation is formally adopted.4
Connection to the “contact event.” UESC records consistently link Subject01 to what they call a “contact event” — an event that preceded UESC operations in the Cryo Archive and that UESC Security Command (SecDefComm) had theorized as a possible outcome of the mission.12 Subject01 is explicitly described as a “confirmation of subjects believed connected with the contact event,” and the mission shift to prioritize its capture was driven by that confirmation.1 The nature of the contact event itself is not elaborated in these volumes.
Active control of local systems. Subject01 had locked down main access to Archive 07 and rendered subsystem cross-hacking attempts unsuccessful.2 A WINTER WALK field note (Operation 0121 / Cryo Deck Exploration) separately records an unknown signal in the ship’s systems — “something is active in the deeper regions of this zone” — which the reporting operative could not confirm as corrupt data versus deliberate action.5 The PRIMETIME after-action report states directly: “S01 had us locked out and local systems were unhelpful.”2
Mutual observation. Captain Orion’s after-action report for PRIMETIME states that UESC operatives had conducted observational runs to study Subject01 before the assault — and that Subject01 had done the same: “Watched us while we watched it.”2 This is the only detail in any captured volume that speaks to Subject01’s behavior or awareness prior to direct confrontation.
Defeat of the PRIMETIME assault team. Operation PRIMETIME (UESC tactical record secdef.tacrec_tciv009994011) was a full breach-and-capture assault on Vault 7, commanded by Orion with Strategic Intelligence Cerberus providing operational planning and probability assessment.2 The force included Orion (O.0407c), field operatives 0042, 0109, and 0121 as the primary strike element, and ARS squads S008/17/33/34 as secondary.2 Two ARS squads were pushed as a frontal diversion; Orion led the remainder to the breach point identified by Cerberus.2
The assault failed immediately: “Breach turned negative almost immediately.” Subject01 ignored the ARS diversion and focused exclusively on the four named operatives — Orion, 0042, 0109, and 0121.2 The engagement lasted approximately three minutes before Orion called the withdrawal; two operatives were forced to eject before the order.2 Orion’s summary: “S01 is impressive. Terrifying, but impressive.” and “We knew it was an advanced species. We knew it was beyond us. But we have experience and the expanse of human history on our side. We know war. Our weapons and tactics are field-tested. None of it mattered.”2
Pursuit and ARS flooding. Subject01 pursued the withdrawing operatives: “It followed. We didn’t make it.” Operative 0109 retrieved an unspecified object from inside Archive 07, but it was lost in Subject01’s final push; the team was forced to eject and left it behind.2 In response, Orion flooded Archive 07 with ARS units — at significant cost in resources.2 The operatives survived (Orion notes “will keep pushing”), but the mission was a full operational loss.
UESC strategic classification: “advanced species.” Orion’s own report describes Subject01 as “an advanced species” and frames the failure as a consequence of underestimating something considered “other.”2 No additional taxonomic, biological, or technological characterization appears in any captured volume.
Capture priority above trespass. The IGLOO command directive (Operation 0042, secdef.tacrec_tciv009993922) elevated Subject01’s capture to Priority 1 for all TCIV_M.CA operations, superseding anti-trespass deployments: “Confirmation of subjects believed connected with the ‘contact event’ take strategic precedence.”1 SecDefComm had theorized this encounter as a hypothetical outcome from mission outset.1
Cross-corpus appearances
| Volume | Map / Section | What it adds |
|---|---|---|
| Securing Cryo Deck | Cryo Archive · Collectibles | Subject01 designated capture target (Priority 1); IGLOO operation; ARS deployed under Cerberus guidance; Orion’s command note on the “contact event” |
| Engagement [Subject01] | Cryo Archive · Collectibles | PRIMETIME after-action; full operational loss; 3-minute engagement; mutual observation; ARS useless; S01 pursued the team |
| First Contact | Cryo Archive · Collectibles | ”Not trespass. Remnant of contact event”; first-person near-encounter near Archive 07; biomat failure / neural eject |
| Cryo Deck Exploration | Cryo Archive · Collectibles | Unknown signal in deeper systems; “something is active” in zone core; precedes formal S01 designation |
Source-silent / open questions
- What Subject01 is — species, origin, biology, AI or organic or hybrid — is entirely source-silent across all captured volumes. It is named, never described.
- The “contact event” that preceded UESC operations in the Cryo Archive is referenced but never explained. What happened, when, and who was involved are source-silent.
- Subject01’s relationship to the Anomaly is not addressed in these volumes. Cerberus’s NUNAMNIR classification logic (for entities that are not Runners, not known fauna, and not malfunctioning UESC units) may apply, but the source never makes that connection explicit for Subject01.
- The unspecified object retrieved by operative 0109 from inside Archive 07 — and lost in Subject01’s pursuit — is not identified. Its significance is source-silent.
- Why Subject01 is located in Vault 7 / Archive 07 specifically, and whether it arrived, was stored, or originated there, is source-silent.
- Whether Subject01 is singular (one entity) or a designation for a class of entities is source-silent. The tactical records consistently treat it as a single target.
- Subject01’s capabilities beyond defeating the PRIMETIME team are not described. The “digital fingerprints” sensation reported in the First Contact field alert (biomat compromise, systems interference) may relate to its methods, but that volume does not use the S01 designation and the connection is implicit, not stated.
- What happened to Subject01 after PRIMETIME — whether it remained in Archive 07, whether subsequent UESC operations were mounted, or whether Runners later encountered it — is not addressed in the captured volumes.
Cross-references
Cerberus · Orion (Captain) · UESC Marathon · The Anomaly · Cryo Archive
Where it appears in the vault
No inbound links yet.
Mirror pages
The local 1:1 pages this hub’s citations resolve to — the twin’s own ground truth.
Sources
Every factual claim above is cited to primary Marathon source material — see Sources below. Cross-corpus connections and interpretation are the vault’s own; where the games are silent, this page says so.