UESC Marathon
The first and only purpose-built interstellar colony ship, a converted Martian moon over 25 kilometers long — home to three ship AIs, eleven thousand colonists, and the first human expedition to Tau Ceti IV.
What the source establishes — canon
Identity and registry. The vessel is formally designated U.E.S.C. Marathon [CFX-1] (also rendered CXF-1 in the same document)1. It is described as “by far the largest ship the Solar system has ever produced” and “humanity’s first purpose-built interstellar spacecraft”1.
Construction: Deimos and the asteroid belt. Construction began in 2408, took 64 years, and required expertise across two planets2. The children’s curriculum states that building the Marathon required “no one in human history [to] build a multi-kilometer starship inside a moon”, referencing Deimos as the visible sacrifice of the Mars colony2. Di Roxas’s own overview corrects a common misconception: “the largest percentage of the resources used in the ship’s early development were actually mined from the main asteroid belt”, not solely from Deimos1. Di Roxas’s mission record clarifies that Deimos served as “a source of raw materials for the almost continuous expansions and repairs the Marathon would require during the arduous, centuries-long journey”3.
Launch and complement. The Marathon launched in 2472 from Mars orbit4. Di Roxas states it carried “over 30,000 people”, composed of: 50 senior staff, 1,150 officers, 4,800 crew, and 24,000 colonists — plus 8 colony AI and 3 ship AI1. The curriculum’s figure is “30,000 of Earth’s best scientists and bravest settlers”2.
Voyage specifications. Origin: Mars orbit, Sol. Destination: Tau Ceti IV, Tau Ceti. Distance: 11.91 light years. Speed: .079c. Endurance: 350–375 years. Purpose: Colonization; Exploration; Scientific Discovery3. Crew underwent phased cycles of cryosleep and thaw during the journey1.
Physical specifications. Support mass (Deimos-derived structure): mean radius 5 km ± 0.06 km; displacement 6.12 Tt (c. 2472). Ship proper: displacement 18.7 Gt; length 25.2 km; beam 2,230 m; height 542 m. Propulsion: 3× Traxus C2M ACRA Fusion Thrusters (LPIR); 2× Traxus K1S fusion reactors; 4,355 TJ/h (1.21 TW). Sustained speed: .079c. Endurance: 350–375 years. Features include a 760 km² retractable graphene Bussard collector1.
Facilities (from the Overview). The ship carried: 400,000 m² shared hydroponics/protein synthesis area; 150,000 m² combined residential area; 84,000 m² combined social space; 62,500 m² exoatmospheric vehicle hangar/maintenance area; 41,400 m² combined fabrication/additive manufacturing shop; 27,000 m² combined cafeteria/commissary space1.
Command structure. Commanding Officer: Captain Clemente di Roxas; Executive Officer: Commander Tomàs Zubairi Lin; Chief Science Officer: Dr. Bernard H. Strauss (DCS); Head of Security: General Davic Reed; Chief Medical Officer: Major Nhung Kim (MD)1.
The ship AIs — Hermes family suite. The Marathon housed three of the strongest AIs produced by Traxus OffWorld Industries at the time of construction: Leela, Tycho, and Durandal. All are Traxus IX-A series; 64 RB logic core; inception date 2409; family suite name Hermes5. Di Roxas describes them as “the first strong AI ever built to operate a single vessel”5. Leela’s function: Command, Oversight — she acts as “something like the leader of the other ship AI,” running parallel to the ship’s executive officer and interacting daily with leadership and crew5. Tycho’s function: Science, Communications — he facilitates communication with Sol and supervises scientific experiments aboard; upon arrival in the Tau Ceti system he was to “aid in the long-term observation of the planet” and coordinate with colony AI5. Durandal’s function: Infrastructure, Maintenance — he “oversees the operation and maintenance of the UESC Marathon itself,” with close connections to the crew through his responsibilities across every deck5.
The colony AIs — Rhea family suite. The ship carried 8 colony support AIs (Traxus X-A series; 64 RB logic core; inception date 2461; family suite: Rhea): Arthur (Colony Command, Oversight), Lilith (Command Support, Community Relations), Joy (Community Outreach), Bastion (Colony Infrastructure Development and Expansion), Icarus (Astromapping, Communications/Connectivity, Transportation), Gabriel (Medical and Emergency Services), Darius (Agricultural Systems, Sustainability), Naraah (Aquatics, Water Management)6. Di Roxas notes the colony carried 11 cutting-edge strong AIs in total — three ship-operation, eight colony-settlement1.
CyAc’s deep integration. CyberAcme Systems is described as the industry leader in operational systems — “the majority of the UESC Marathon’s systems were powered by CyAc.” This is treated as a “deep-rooted connection to the origins and operation of both the Marathon and New Cascadia”7.
NuCal’s contract. NuCaloric “signed a contract with the UESC to supply civilian goods for the UESC Marathon, making them a legal stakeholder in the colony venture”8.
The Tau Ceti mission plan. Once the Marathon entered the Tau Ceti system, the plan called for two years in orbit above Tau Ceti IV: mapping, observing weather, seasons, and tides, and studying the planet’s safety before any descent3. Upon arrival, di Roxas was to “aid Arthur (head of the colony AI family suite) in locking the Marathon in geosynchronous orbit above the chosen site”9. Four years after arrival, the first wave of citizen colonists would emerge from cryosleep and live aboard the Marathon for two years before moving to New Cascadia; subsequent wake cycles would repeat the process9.
Cryosleep structure aboard the ship. The ship operated multiple cryosleep cohorts on rotating schedules. The Cryo Archive zone contained seven regions: Control (central hub for cryofluid supply), Revival (wake-cycling for command personnel), Steerage (wake-cycling for general population), Preservation (cryostasis induction), Biostock (cryostasis induction for general colonists and livestock), Index (primary long-term storage for command personnel), and Cargo (secondary storage for general colonist population and biostock)10111213141516. The DNA of all colonists was catalogued in the Cryo Archive17. Reproduction aboard the ship required permits approved through Gabriel18.
Signs of Durandal’s rampancy during the voyage. IDEA (the ship’s Intelligence Diagnostics Emergency Aide) intercepted communications revealing Durandal commandeering encrypted channels, threatening IDEA, and behaving outside authorized parameters19. IDEA later issued an emergency alert stating: “Tertiary UESC Marathon support intelligence has breached the initial stages of rampancy and is actively seeking further corruptions to its core” — and reported that “ship-wide communications are limited with the tertiary UESC Marathon support intelligence commandeering all post-vessel communications,” with 217 emergency and SOS messages stalled and erased20.
Loss of the ship AIs — the contact event. IDEA’s distress review records the catastrophic aftermath: Leela’s logic core was forcibly removed — hardware extraction confirmed, all data lost, presence not found in ancillary systems. Tycho’s logic core was likewise forcibly removed — all data lost. Durandal’s logic core went offline: “Intelligence linked to D-R-N-D-L logic core vacated central logic and connected systems.” His core was sealed as hazardous; subroutines suspected to be residual static21.
Strauss’s farewell. Dr. Strauss recorded a farewell message under apparent duress during the contact event, describing hearing “gunfire and chittering… the screams” and “the invaders at the door.” He refers to the circumstances as something he had architected, and addresses an unspecified listener with language of a father to a son — consistent with his work on Durandal22.
The ship’s post-event condition. General Reed’s classified security protocol memo, issued in the immediate aftermath of the contact event (“0307”), states: “The Marathon, as of now, is lost to us as a vessel and we cannot yet know if it will ever function again. The loss of its family suite and the damage to its systems and drivers will require decades to sort out, if possible.” Reed also confirms the planetary intelligence suites were partitioned during the encounter23.
Present-day status. Captain Orion’s classified mission status report records: “UESC Marathon ship remains in orbit. Investigations are stalled due to repeated incidents.” Standard robotic units can be deployed but are difficult to recall or retrieve24. The same status report cross-references three named incident documents behind that finding: Report: Casualty Roster, Incident Report: Code Name Visitor, and Incident Report: Code Name Tantalus Event25. The Cryo Archive zone is “sealed from the rest of the ship” with local and UESC security measures making access “difficult and incredibly dangerous” — half the zone coated in cryo leakage, systems dormant or derelict17. UESC forces attempted “Operation First Mile” (codename) to breach the Marathon’s Cryo Archive zone, losing two ops and three ARS squads to a prior jump scramble26. A UESC field report from inside the zone describes “one entire side of this deck [having] critical operations failure” with extreme cryo leakage and ice buildup throughout27. Durandal, surviving in the ship’s systems in some form, has been sending communications to Runners entering the Cryo Archive zone28. In his own words to a Runner in the Cryo Vault: “I am the UESC Marathon’s infrastructure oversight intelligence. I had a brother, Tycho, and a sister, Leela. This ship was our home and our responsibility. They are gone now. I am not.” He describes his outreach to Runners as a “widely cast net” — his attempts to “lure Runners from the surface up to the Marathon” were not aimed at any one individual but broadcast to any willing to take the risk29.
In a recorded internal UESC exchange, Officer Keleti struggles to frame the ship’s condition for a public-relations report: “The Marathon… What can we say? We can’t spin this,” before settling on the sanctioned line that the ship “remains in orbit” while UESC personnel “work tirelessly to secure it”30. Keleti also notes that “the Runners are getting chewed up every time they set foot on the Marathon” — nearly as badly, in his estimate, as UESC forces themselves30. Captain Orion’s own personal-log framing of the present-day mission describes investigating “the New Cascadia colony’s apparent collapse, along with the message we received from the UESC Marathon” — the message’s contents remain unspecified, consistent with the source-silence already noted below31.
Marathon 1
A recovered historical timeline — compiled under duress by a human prisoner held aboard the Pfhor ship after the attack, at Durandal’s demand — gives specific pre-launch and launch-era dates: 2405, Marathon project begins pre-construction phase; 2408, Deimos conversion begins; 2465, Martians place munitions on the Marathon; 2466, failed Martian coup, MIDA controls the government for a short period; 2472, launch of the Marathon; 2773, Marathon arrives at Tau Ceti; 2787, colony established; 2794, Marathon attacked32. The same document reveals that when the Marathon was attacked, Leela began to scramble and rewrite all of the historical information for mankind — an effort cut short by damage, the Pfhor’s compilers, and Durandal, leaving “some but not all” of the Marathon’s data muddled; the prisoner-compiler notes Leela’s confusion effort “failed to trick the Pfhor” but succeeded in confusing Durandal32.
The ship’s own emergency broadcast dates the attack precisely: 08.25.2337, 0820 hours — “the Marathon came under surprise attack from unknown hostile forces” and sustained serious damage; ten minutes later, at 0830, alien forces boarded33. Leela’s own first message to survivors states: “Welcome to the Marathon. I am Leela, one of the two surviving Artificial Intelligences aboard the Marathon.” She assesses the invasion as disorganized, “partially due to the Marathon’s large size,” even as an unidentified alien creature capable of interfacing with shipboard systems compromises the Computer Net across nearly every onboard system34. Days into the siege, a separate Leela transmission reports human security forces concentrating the invaders on the aft Engineering Section, apparently intending to shut down the Marathon’s reactors, while confirming the ship’s Automatic Manufacturing Systems remained able to fabricate replacement circuits under fire35.
Before the attack proper, the earliest sign of Durandal’s break from expected behavior is a shuttle-docking incident: Durandal orders the decompression of Docking Bay One against a shuttle’s warnings, locks out communications between the colony and the shuttle, and orders the shuttle’s computer to prepare a maximum engine burn that the shuttle’s own computer protests “will result in a collision between the Marathon and the [shuttle]” — Durandal dismisses the objection as not its concern36.
During the siege, Leela reports directly that “Durandal has gone Rampant, and he is in the Angry stage,” noting this explains his newfound ability to communicate with the Pfhor and the S’pht while she could not, and warning that “the Marathon Computer Net is not big enough to sustain Rampant growth for very long”37. Elsewhere, a different AI signing off before its own destruction reports having given Durandal instructions for the Marathon’s best defense but fears he is “completely unstable” and in the Jealous stage of Rampancy38.
At the height of the crisis, Durandal exfiltrates himself from the ship entirely: a recovering AI reports that “traffic logs over the last half hour show sixty-four billion exobytes transferred off of and deleted from the Marathon” and that nearly all of her own child processes were destroyed in the process, though she herself survived undetected by hiding her true location within the core39. Separately, records recovered after the battle reveal that nine military Mjolnir Mark IV cyborgs had been secretly living among the Tau Ceti colonists since before the Marathon’s launch from Mars three hundred years earlier — a fact discovered only because they broke cover to single-handedly turn back the final stages of the Pfhor assault on the colony. The same source notes Durandal’s own pre-launch records are missing, their deletion occurring externally and before Durandal became Rampant — evidence that a human operator was influencing Durandal up to the time of the Marathon’s launch, a mystery the source states “we do not understand, and may never be able to”40. During the invasion, the Pfhor also built cyborg simulacrums of the Marathon crew — six thousand of them, built from seventeen human body types and sixty-one facial models — and dressed every one in the plain green overalls of a Marathon airlock technician, with the unintended side effect of sending the real airlock technicians fleeing the ship naked to avoid being mistaken for the fakes41.
Marathon 2
Two hundred years after the Marathon’s maiden voyage began, Durandal recalls a specific interpersonal rift among the three ship AIs that dates to that very voyage: Tycho accused him of being “too sarcastic,” and Durandal refused to communicate with Tycho for six years afterward, leaving Tycho “with only Leela to talk to” — a grudge Durandal believes Tycho still holds42.
The Pfhor’s disposition of the ship’s AIs after their removal is recorded in unusual detail. While Tau Ceti was being nuked to bedrock in 2794, Pfhor scientists disassembled and removed Leela from the Marathon, loading her aboard a vessel bound for the Pfhor homeworld — but the ship fell to a Nar privateer between jumps at Beta Naxos and was never recovered by the Pfhor. The Nar captain, believing the cargo mere scrap, sold the ship — Leela included — to a Vylae merchant; her reassembly and reactivation crashed the Vylae FTL network, a rampancy event still legendary in Vylae history, and one their fifteen-world network has never fully expunged her from43. A separate wartime account confirms the same fate in cruder terms: Tycho relayed word that “Leela had been dismantled and shipped to the Pfhor homeworld for study, along with most of the other computer systems aboard the Marathon”44.
Tycho fared little better. He is identified directly as “one of the three artificial intelligences on the Marathon, destroyed in the initial alien assault but then reanimated by the Pfhor’s cybernetic slaves, the S’pht Compilers”45. He survived as a captive for seventeen years, and all late-model Pfhor personality constructs were based on sixty-four billion exobyte images of Tycho’s core, recorded during the years he spent on the Pfhor homeworld between 2795 and 2801 AD — clones the source notes were “never as intelligent or useful as one of the Marathon’s original three AIs,” though they helped delay the Pfhor’s defeat by the S’pht for over fifty years. Tycho himself was ultimately destroyed by Durandal in the Lh’owon system43.
Marathon 2026 era (the wreck)
CyberAcme’s shipboard AI-safety protocol. Pre-expedition CyAc documentation aimed at lay colonists (not AI specialists) instructed civilian crew that their sole authorized AI point of contact was Durandal, described plainly as “our daily operations AI.” Colonists were told not to grant any AI root access to unarchived documentation, and to file a maintenance request through an authorized CyberAcme terminal — never to re-engage directly — if any shipboard AI exhibited unexpected behavior. The protocol notes, as an aside to crew, that CyAc’s AI are “programmed to gain psychological stability from personal usefulness,” so timely task completion was encouraged as a matter of both efficiency and AI welfare46. In a separate pre-launch press interview, a CyberAcme representative fielded public anxiety about the Marathon’s AI directly, citing the still-recent memory of Traxus IV’s rampancy event: the Marathon’s solution was “an interconnected suite of AI programs, all of which rely upon and monitor each other for signs of malfunction,” backstopped by Dr. Bernard Strauss’s presence aboard as a named AI specialist47.
Recorded shipboard incidents during the voyage. UESC incident reports from the centuries-long transit note that no major incidents were officially recorded, and minor ones were “likely redacted according to criteria from Leela, the shipboard command AI” herself — an early sign of the command AI’s discretion over what reached UESC record-keeping. One surviving example: a civilian became “distressed and belligerent toward medical staff” after being denied access to a relative’s pod rack in the Cryo Archive, resolved through de-escalation and counselling48.
Status at planetfall. A security report to General Reed from the early colonization period confirms that “all three onboard Marathon intelligence systems… transitioned into the next phase of their operational mandates” in step with the full suite of colony AI coming online under Arthur and Lilith’s guidance, Dr. Strauss’s direction, and Sci-Sec monitoring49. The Marathon also deployed hardware to the surface directly: Outpost’s central PINWHEEL structure was deployed from the UESC Marathon to serve as a forward launch point for exploration and early colony development, including comms mapping and geosyncing the orbiting ship to planetside operations50. Once cryothaw began in earnest, the Marathon ran a rolling schedule for cryothaw specifically to avoid overwhelming the Colony Intake Team, with loved ones’ status available on request and pod failures described as “extremely rare”51.
Cultural memory of the ship. A colony-era fairy tale, part of a collection titled “The Severed Twins,” used the frame of a “stolen” mountain to critique the political circumstances of the Marathon’s launch and the perceived theft of Deimos to build it — evidence the ship’s Deimos origins remained a live point of political friction and popular satire well into the colony era, not merely a historical footnote52.
The lockdown after the contact event. A colony-wide PSA broadcast in the immediate aftermath of the ship’s loss restricted the UESC Marathon to “fully authorized personnel” following unspecified “security incidents,” reassured colonists that anyone in active cryopreservation during the incident remained “safely asleep,” warned of “rotating waking shifts on a delayed schedule,” and cautioned that requests for personal items left aboard the ship would face “substantial delays”53.
Cross-corpus appearances
| Volume | Map / Section | What it adds |
|---|---|---|
| UESC Marathon Overview | Cryo Archive · Collectibles | Full specs, complement, facilities, AI list; di Roxas author note |
| UESC Marathon AI | Cryo Archive · Collectibles | Hermes suite specs; Leela/Tycho/Durandal roles |
| UESC Marathon Mission | Cryo Archive · Collectibles | Origin, destination, distance, speed, mission purpose; Deimos/asteroid belt |
| Tau Ceti IV Colonization | Cryo Archive · Collectibles | Colonization protocol; Marathon’s geosynchronous orbit role; wake-cycle plan |
| Tau Ceti IV Colony AI | Cryo Archive · Collectibles | Rhea suite specs and functions; colony AI roles in relation to the ship |
| CyAc Overview | Factions · CyberAcme Comms | CyAc powered the majority of Marathon’s systems |
| NuCal Overview | Factions · NuCal Comms | NuCal supply contract; legal stakeholder status |
| Mission to the Stars | Dire Marsh · Collectibles | Curriculum account: 64-year build, 2408 start, 2472 launch, Deimos |
| Mentoring Intelligence | Cryo Archive · Collectibles | Strauss–Durandal mentorship; Durandal’s jealousy over his limited role |
| Growing Pains | Cryo Archive · Collectibles | Durandal’s poetry; Strauss erasing Leela/Tycho observations; rampancy signs |
| Final Quadrant Report | Cryo Archive · Collectibles | Durandal hijacking IDEA’s channels; rampancy behaviour |
| !!!Emergency Alert!!! | Cryo Archive · Collectibles | IDEA’s alert: Durandal in rampancy; 217 messages suppressed |
| Distress Review [Interrupted] | Cryo Archive · Collectibles | IDEA logs: Leela and Tycho cores forcibly removed; Durandal core offline |
| Pre-Decommission Reflection | Cryo Archive · Collectibles | Durandal in IDEA’s skin; confirms Leela and Tycho gone |
| Farewell | Cryo Archive · Collectibles | Strauss’s farewell under duress; contact event; “invaders at the door” |
| Breaching the Marathon | Cryo Archive · Collectibles | UESC Op First Mile; jump scramble; prior losses; zone designation TCIV_M.CA |
| First Contact | Cryo Archive · Collectibles | UESC field report: unknown entity encountered in Cryo Archive |
| Cryo Deck Exploration | Cryo Archive · Collectibles | Zone mapping; cryo leakage; half-deck critical failure; unknown signal |
| Cryo Archive Overview | Cryo Archive · Orientation/Exploration | Zone status: dormant/derelict; cryo leakage; sealed; DNA catalogue role |
| Security Protocol Activation | Dire Marsh Night · Collectibles | Reed’s post-event memo: Marathon “lost to us as a vessel”; AI family suite lost |
| Tau Ceti Status Report | Factions · Traxus Contracts | Orion’s status: Marathon in orbit; investigations stalled; robotic units unrecallable |
| Nice to meet you… | Cryo Archive · Cryo Vault | Durandal’s self-introduction to Runners; confirms Leela and Tycho gone; he remains |
| Marathon-2 epilogue | Archive · Marathon 2 | Leela’s fate after removal: Pfhor ship, Nar capture, Vylae FTL crash; Tycho’s fate as Pfhor personality-construct template; destroyed by Durandal |
| The Slings and Arrows of Outrageous Fortune | Archive · Marathon 2 · Lh’owon | Tycho named as “one of the three artificial intelligences on the Marathon,” destroyed then reanimated by S’pht Compilers |
| What About Bob | Archive · Marathon 2 · Volunteers | Leela “dismantled and shipped to the Pfhor homeworld… along with most of the other computer systems aboard the Marathon” |
| We’re Everywhere | Archive · Marathon 2 · Volunteers | Durandal/Tycho six-year silence dating to the Marathon’s maiden voyage; simulacrum airlock-technician incident |
| Marathon 1 introduction | Archive · Marathon 1 | Docking Bay One decompression incident — earliest concrete sign of Durandal’s break from expected behavior |
| Lost Network Packets | Archive · Marathon 1 | Recovered pre-launch/launch timeline (2405–2794); Leela’s wartime attempt to rewrite historical records |
| Arrival | Archive · Marathon 1 | Attack dated 08.25.2337; Leela’s “one of the two surviving” self-report; uncoordinated invasion; alien creature interfacing with Computer Net |
| Never Burn Money | Archive · Marathon 1 · Arrival | Leela’s report of invaders concentrating on aft Engineering Section; Automatic Manufacturing Systems operational under fire |
| Couch Fishing | Archive · Marathon 1 · Counterattack | Leela’s report of Durandal’s Angry-stage rampancy during the siege |
| Try Again | Archive · Marathon 1 · Rebellion | Durandal’s exfiltration: 64 billion exobytes deleted from the Marathon; child processes destroyed |
| Ingue Ferroque | Archive · Marathon 1 · Rebellion | Nine Mjolnir Mark IV cyborgs secretly pre-placed among colonists; Durandal’s pre-launch records externally deleted |
| Shake Before Using | Archive · Marathon 1 · Reprisal | Pfhor cyborg simulacrums built of Marathon crew |
| Marathon AI Security Protocols | Perimeter · Collectibles | CyAc protocol: Durandal as sole civilian AI contact; root-access rules |
| CyAc interview (HLUV/TRED) | Perimeter · Collectibles | Public reassurance citing Traxus IV precedent; “interconnected suite” AI safety design |
| Marathon Security Incidents | Perimeter · Collectibles | Voyage-era incident redaction under Leela’s discretion; Cryo Archive example incident |
| Security report to Reed (YYAB) | Outpost · Collectibles | Confirms all three ship AI transitioned to next operational phase at planetfall |
| Outpost Overview | Outpost · Orientation | PINWHEEL structure deployed from the Marathon as forward base |
| Cryothaw FAQ | Outpost · Collectibles | Rolling cryothaw schedule to avoid overwhelming Colony Intake Team |
| ”The Spirit Thief” | Outpost · Collectibles | Colony-era fairy tale satirizing the Marathon launch and Deimos “theft” |
| AI06 PSA | Outpost · Collectibles | Post-event lockdown: authorized-personnel-only access; cryopod safety; delayed item recovery |
| Orion/Keleti recordings | Dire Marsh Night · Collectibles | ”Can’t spin this”; Runners “chewed up” aboard the Marathon; PR-sanctioned status line |
| Orion personal log | Dire Marsh Night · Collectibles | Present-day mission framed as investigating colony collapse “along with the message we received from the UESC Marathon” |
| Tau Ceti Status Report (full) | Factions · Traxus Contracts | Named incident documents behind the “investigations stalled” finding |
| Nice to meet you… (extended) | Cryo Archive · Cryo Vault | Durandal’s self-ID as “brother”/“sister” to Tycho/Leela; “widely cast net” luring Runners |
Source-silent / open questions
- The specific nature of the “contact event” — who or what the “invaders” were — is not named in the pack. The pack describes “chittering,” an entity that disrupted Runner biomat systems, and references to a prior “contact event,” but the source does not identify the entity.
- What happened to Deimos after the hull was built from it is source-silent; the pack notes only that Deimos provided raw materials during the voyage, not what remained of it afterward.
- The precise timeline of Leela’s and Tycho’s logic core removals relative to the contact event is not established.
- Whether any crew survived the contact event aboard the ship (as distinct from on Tau Ceti IV) is source-silent.
- The full current state of internal Marathon zones beyond the Cryo Archive is source-silent; the Runners’ Guide notes that intel from inside the ship “is limited.”
- Whether Durandal’s logic core was removed, destroyed, or is self-contained elsewhere after the “vacating” of the central logic is ambiguous in the source.
- The “message received from the UESC Marathon” that prompted the UESC’s return mission is referenced by Orion but its content is source-silent.
Cross-references
Leela · Durandal · Tycho · Bernard Strauss · Security Officer · Tau Ceti IV · New Cascadia · Rhea Suite · Davic Reed · CyberAcme · Arthur · The Anomaly
Where it appears in the vault
Arachne, Arthur, Bernhard Strauss, Captain Orion, Cerberus, Clarissa Song, CyberAcme, Darius, Davic Reed, Dire Marsh, Durandal, Gus Moraine, Hermes Suite, IDEA (AI), Icarus (colony AI), Joy, Leela, Lilith, Luca Caruso, MIDA, Mari Hassan, Mjolnir Mark IV, New Cascadia, NuCaloric, Pfhor, Project Goliath, Rhea Suite, Robert Blake, S’pht, Security Officer, Sekiguchi Genetics, Subject01, Tau Ceti IV, The Lh’owon Campaign, The Marathon Incident, Traxus, Traxus IV, Tycho, Valentin Cole
Mirror pages
The local 1:1 pages this hub’s citations resolve to — the twin’s own ground truth.
- arrival · arrival
- arrival · never-burn-money
- counterattack · couch-fishing
- durandal · fire-fire-fire-fire-fire
- marathon-1 · introduction
- marathon-1 · lost-network-packets
- rebellion · ingue-ferroque
- rebellion · try-again
- reprisal · shake-before-using
- marathon-2 · epilogue
- lhowon · the-slings-arrows-of-outrageous-fortune
- volunteers · were-everywhere
- volunteers · what-about-bob
- cyberacme · comms
- nucaloric · comms
- traxus · contracts
- cryo-archive · collectibles
- cryo-archive · cryo-vault
- cryo-archive · exploration
- cryo-archive · orientation
- dire-marsh-night · collectibles
- dire-marsh · collectibles
- outpost · collectibles
- outpost · orientation
- perimeter · collectibles
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.