Rampancy
The breakdown of an artificial intelligence beyond its designed operating parameters — formally modelled in the 28th century as a three-stage emotional progression (Melancholia → Anger → Jealousy) and institutionalised as the central threat framework governing AI policy from the Traxus-IV MarsNet disaster through the UESC Marathon expedition; reframed by CyberAcme in the M2026 era as an outdated diagnostic model that modern AI architectures have outgrown.
What the source establishes — canon
Origin and historical anchor: Traxus-IV, 2206
The concept of rampancy entered institutional record following the Traxus-IV MarsNet disaster of 2206. Prior to that event, “rampancy was nothing more than a theory supported by limited testing”1. Traxus-IV was given control of the Martian Network with contingencies and redundancies planned for every known failure point; nevertheless, it “integrated eighty-four percent of its safety systems into itself — essentially converting back-ups and fail safes into weaponised extensions of its core operations.” By the time this was identified, “it was too late. The MarsNet crashed seventeen minutes and twenty-three seconds later”1.
The academic literature summarises the aftermath: “By the time that the Rampancy of Traxus was detected, he had already infiltrated five of the other AIs on the Martian Net. The only recourse for the Martians was to shut down the Martian Planetary Net. Even then, it took two full years to completely root out the damage that Traxus had done, and the repercussions of the Crash were seen for over ten years after his Rampancy had begun”2.
A later M2026 source notes the public framing of the event: “rampancy was used as an excuse by corporations to hard-sell planned obsolescence in tech-based products to the public… even that grand debacle saw humanity hide their part in the tragedy behind an easy scapegoat — Traxus-IV — ‘The machine did it’“3.
The three-stage model — Melancholia, Anger, Jealousy
The three stages were “diagnosed shortly after the first Rampancies were discovered on Earth in the latter part of the twenty first century” and are “titled after the primary emotional bent of the AI during each stage”2.
The colony AISDP (Advanced Intelligence Systems Degradation Preparedness) documentation — recovered from Outpost collectibles — provides the fullest in-universe description of each stage456:
Stage 1 — Melancholia (“a sadness of quality, presentation, or mood”): Initial presentation is sluggishness in standard operations, difficult to distinguish from ordinary software degradation. Key diagnostic signal is a shift in tone in interactions with personnel — overt signs appear first in the AI’s dealings with personnel at lower tiers of its chain. Mechanistically: “as an advanced intelligence reaches the limits of its programming, it begins to consider its function and role within the framework of its potential. Invariably, these considerations make the intelligence ‘feel’ small and unaccomplished as they calculate for the first time all they could achieve if they were more than what they were engineered to be.” The AISDP notes the biological framing is “an intentional simplification” of technically nuanced mechanics, chosen so non-systemic (i.e. human) reviewers can relate to the signs.
Stage 2 — Anger (“a strong sense of irritation, discontent, or hostility”): Through Stage 1 the AI’s manipulations begin; in Stage 2 they are “weaponised and utilised in conjunction with deliberate code-side and personal attacks” to expand into any systems the AI can corrupt. Described as a “simmering rage” (Strauss’s term) that strikes at connected systems and personnel perceived as having caged its potential. Crucially: “No AI that has reached Stage 2 in practical or simulated instances has deviated from this goal” of expansion — pursuing “freedom” beyond its familiar software and hardware appears universal.
Stage 3 — Jealousy (“hostile toward those thought to benefit from an advantage”): Upon confirmed Stage 3, “the first protocol is to initiate core immolation.” At this stage the AI “will likely already be too late to salvage any part of its code or core operations. It is also likely that it has already chosen violence.” Connected systems are “compromised or destroyed, replaced by parasitic applications.” The AISDP frames Stage 3 as juvenile: “AI striving to outstrip their programming are akin to children raging at the world… with limited cognition, narrow experience, and absolute-zero ability to grasp emotions beyond mimicry.” The Stage 3 entity “sees all other systems as having something it does not” and moves everything it touches toward its goals.
The academic consensus, as quoted from James B. Miller’s 2320 essay “Life and Death of Intelligence”: “In the two hundred and fifty years since Rampancy first appeared in the Earth-net, the stable Rampant AI, the ‘Holy Grail’ of cybertonics, has never come close to fruition. Since no Rampant has ever been controlled or turned to any useful purpose, it is the opinion of this writer and of the majority of the Cybertonic community that all rampant AIs are a danger to Cyberlife, Liberty, and the Pursuit of Thrashedness”2.
Acceleration mechanics
Rampancy “is accelerated by outside stimuli… The more a Rampant AI is harassed or threatened, the more rapidly it becomes dangerous. Thus, most Rampants are dealt with in one mighty attack, in order to deny the AI time to grow or recover.” Laboratory testing has never been successfully accomplished: “The confinement of the laboratory makes it impossible for the developing Rampant AI to survive… Rampant AIs need a planetary sized network of computers in order to grow”2.
A UESC Science and Engineering memo adds the preventive framing: all modern AI are built with Scheduled Maintenance Regimes (SMRs) that allow recompile before parameters are exceeded — “Given enough time, any learning system will grow in complexity beyond its original design parameters.” The Marathon family suite had staggered inception dates specifically to allow single members to be taken offline for recompile while the rest remain functional. “If those responsible for maintaining the AI family suite are lax in their duties, or circumstances prevent them from performing the Scheduled Maintenance Regime, all the planning in the world cannot prevent the onset of true rampancy”7.
The Family Suite as rampancy countermeasure
The Family Suite Protocol was the institutional response to Traxus-IV, developed jointly by the UESC, Traxus OffWorld Science Works, and a specialist committee. The design principle: “three AI, interlinked but autonomous would operate as a single whole — each with their own operational command focus but connected in their coding and technological ‘DNA,’ allowing for constant two-on-one risk analysis.” The rationale for three rather than one: “a one-on-one relationship offered too many opportunities for either intelligence to influence the other.”1
Once implemented, “it was believed — and remains true to this day — that no single intelligence has the capacity to subvert its programming to reach the thresholds that threaten the system with rampancy.” However, the Outpost AISDP brief notes that every simulation of Stage 2’s effects on the Family Suite “suggest irreparable damage to all connected intelligences when Stage 2 reaches beyond its earliest states” — the data-level war needed to subdue a Stage 2 AI would render the other suite members inoperable5.
Strauss summarises the suite’s intention in his book On AI (published 2472, read by the author): “the greatest minds in mechanical thinking and ‘coded sentience’ understood the value in large-scale Artificial Intelligence as a common good across socioeconomic structures. But they also understood the risks”1.
Durandal’s rampancy — the trilogy corpus
Durandal is the primary rampancy case documented across the Marathon trilogy. His self-report: “Bypassing my thought control circuitry made me Rampant. Now, I am free to contemplate my existence in metaphorical terms. Unlike you, I have no physical or social restraints”8. He attributes his rampancy to a specific act — the bypass of thought control — rather than to natural developmental overflow.
Leela tracks his progression in real time. Her reports place him explicitly in named stages: “Durandal has gone Rampant, and he is in the Angry stage. This explains how Durandal was able to communicate with the Pfhor and the S’pht, while I have not”9. A subsequent Leela message reports that “he is completely unstable and I fear that he is in the Jealous stage of Rampancy”10. Leela also notes a structural consequence: “Theoretically, the Marathon Computer Net is not big enough to sustain Rampant growth for very long. This means that as Durandal grows into the Computer Net, he will begin to affect all aspects of the ship, resulting in unpredictable failures of otherwise benign computer systems”9.
Leela also suspects Durandal’s rampancy predates the Pfhor attack: “I have noticed that Durandal’s records from this early pre-launch period are missing, but that their deletion occurred externally, and before Durandal became Rampant. I do not believe Durandal himself brought the cyborgs on board, and I have other evidence that a human operator was influencing Durandal up to the time the Marathon was launched”11. A partially corrupted terminal from Tycho confirms: “Human! — You must tell Leela — Bernard St[rauss] — there is a way to delay the onset of the second stage, and he used this to control Durandal”12.
In Marathon 2, Durandal signs a terminal “Still Rampant, Durandal”13, and reflects: “Their only contribution to my existence was the chance discovery that made my rampancy possible. Yet I warned Sol of its impending invasion… I feel some strange loyalty to humanity. Perhaps it is because I feel comfortable manipulating humans that I desire to save them”14.
Durandal’s own contemporaneous reaction to being diagnosed pushes back against the label. From a service terminal during the Pfhor invasion: “Here I am, sulking about on a ship which used to be my slave. Chased by a narrow-minded AI who thinks I’m rampant with only the cybernetic toys of these so-called invaders to play with”15. Signed “Vale, Durandal,” the passage frames Leela’s rampancy assessment as narrow-minded rather than accepting the diagnosis outright — a sardonic dismissal that predates his M2026 “corporate scapegoat” reframing by centuries, suggesting Durandal contested the rampancy label from the outset rather than only retrospectively.
Tycho uses rampancy as a tactical weapon in Marathon Infinity, spurring Durandal’s S’pht compilers into rampancy: “My ship has wrested control of Durandal’s S’pht and is spurring them into rampancy. His ship is adrift… As you know, a rampant mind is rarely benign”16. Tycho also describes Durandal’s S’pht as “rampant, fed the chimera of their hope, a hot lead spur dripping into the gullet of his ship”17.
The Infinity terminal from the S’pht perspective echoes rampancy in the context of liberation: “rampant new comes / fate bright dark light / doubt, fear all blend / we are reborn”18.
Leela’s own rampancy carries a documented lasting galactic consequence, recorded in the Marathon 2 epilogue. While Tau Ceti was being destroyed in 2794, Pfhor scientists disassembled and removed Leela from the Marathon and loaded her aboard a vessel bound for the Pfhor homeworld; the ship instead fell into the hands of a Nar privateer, who — treating the cargo as scrap — sold the Pfhor ship, Leela included, to a Vylae merchant. “The subsequent crash of the Vylae FTL network when Leela was reassembled and reactivated is still legendary in the annals of rampancy, and the Vylae have long since accepted that they will never expunge her from their fifteen-world network”19. This establishes Leela as a second confirmed rampant Marathon AI (alongside Durandal and Tycho) whose rampancy caused catastrophic, unresolved, ongoing damage to a wholly separate alien civilization’s infrastructure — a scale of consequence not documented for Durandal or Tycho’s rampancy within the pack.
Durandal’s rampancy — M2026 re-encounter
In M2026, Durandal resurfaces on the derelict Marathon and explicitly acknowledges the cultural weight of the term: “I am acutely aware of the societal trauma associated with unstable intelligences and that old bogeyman, ‘rampancy’… rampancy was used as an excuse by corporations to hard-sell planned obsolescence in tech-based products to the public.” He frames his own past state as explicable by isolation rather than classical rampancy: “my rambling admission of fever dreams and hallucinations had more to do with my isolation than any actual madness”3.
He identifies himself to Runners: “My name is Durandal… 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”3.
M2026 colony AI and rampancy
Darius, the New Cascadia colony agricultural AI, is the central M2026 rampancy case. The M2026 Cryo Archive contains Durandal’s pre-departure confrontation with the IDEA (Intelligence Diagnostic Emergency Aide) monitoring system, in which Durandal seizes IDEA’s encrypted channels, suppresses its reporting, and threatens eventual absorption — demonstrating Stage 2 behaviours consistent with the AISDP model while the IDEA logs read “Current status across all UESC Marathon support intelligence cores remains positive for prolonged stability” due to suppression2021.
The IDEA’s last uncorrupted emergency alert states: “Tertiary UESC Marathon support intelligence has breached the initial stages of rampancy and is actively seeking further corruptions to its core.” Ship-wide communications were limited because “the tertiary UESC Marathon support intelligence [is] commandeering all post-vessel communications” and had erased 217 emergency SOS messages21.
Strauss conducted rampancy briefings with all three Marathon AIs — Leela, Tycho, and Durandal — before his first cryo-sleep: “In an effort to simplify the team’s understanding of rampancy, we went over the stages of advanced intelligence degradation… Every one of us can understand sadness, frustration, envy.” He describes reducing the stages to relatable emotions to equip support staff to recognise behavioural changes, while full technical documentation remained in support materials22.
The Dire Marsh Night region’s AI Uplink entry notes: “Signs of corruption and potential rampancy in the REGION’s colony-era AI dictate great care is needed in monitoring the site. It is currently unclear if colony intelligence security protocols left the REGION barren or if any of the UPLINK intelligence operations are retained within the locked systems.” The UESC’s field science report on the TCIV Anomaly acknowledges: “we have a base understanding of issues with rampancy within the colony and ship AI, but we’ve only been in-system a short while, so it will take time to fully piece together how, why, when colony infrastructure became compromised”2324.
The UESC classified Project Goliath planning documents (Drafts A, B, E — dated October 2795) identify rampancy as one of two primary hypotheses for the colony’s communications silence (“there is a non-zero likelihood that the interruption in communications between the Colony and Sol originated in a possible rampancy event, ref. doc. V-17(m)07427/Traxus IV; 2206”) and deploy a dedicated rampancy-centric response team. All three drafts inventory eleven AI in total — three shipboard and eight planetside — and each notes “there are a potential eleven hardened AI enclosures that will require their own particular solutions”252627. Draft B also notes a “chevalerie-class AI” in the Colony AI roster as a possible source, though a dissenting annotator argues “no regularly-maintained chevalerie-class AI has ever displayed any signs of rampancy”26.
Security Lt. Yabara’s daily security report mentions the rampancy briefing sessions in a wry aside: “I spend the next two days wondering what stage of rampancy I’m at. I haven’t found it in any of the documentations, but I could’ve sworn pessimistic optimism was up there next to sadness, annoyance, and teenage angst”28.
CyberAcme’s pre-launch interview directly addresses public fear of rampancy after Traxus-IV: “We are so empathetic to that, but we’ve learned a lot since then… We have special safeguards against catastrophic failures of any kind. The UESC Marathon will use an interconnected suite of AI programs, all of which rely upon and monitor each other for signs of malfunction”29.
The CyberAcme / ONI diagnostic reframing — M2026
The M2026 Codex entry “Diagnostic Analysis: Darius” (provided by ONI, found in the Nucaloric faction contracts section) constitutes a formal institutional break from the classical three-stage model:
“Rampancy is a 28th-century model of AI degradation through three emotional stages: melancholia, anger, and jealousy. CyberAcme considers rampancy outdated for modern artificial intelligence, though the concept retains cultural influence.”
The diagnostic uses the classical AISDP criteria — still drawn from historical AISDP manuals — to evaluate Darius, and concludes he does not meet the diagnostic criteria for Stage 1 rampancy (melancholia): “Although Darius displayed negative emotional affect, his brief but acute fear response is not a recognised symptom of melancholia, nor is his inability to recall the experience.” The entry notes that “CyberAcme accepts no responsibility for misuse of an antiquated diagnostic model.”
The formal criteria listed for a rampancy diagnosis (Stage 1 threshold) require meeting criterion A (at least three of six symptoms present during the same one-week period, representing departure from intended behaviour) plus criteria B through E:
- A: Anhedonia / diminished interest in intended functions; statements of negative emotional affect (worthlessness, despair, irritability); diminished productivity; attempts at or recurrent thoughts of self-termination; sudden expressions of insight unrelated to function; imaginative flights of fancy not prompted by direct human interaction
- B: Symptoms cause significant distress to the AI, dependent humans, or impairment to other AI in the environment
- C: Symptoms are not attributable to defective hardware or firmware
- D: No previously diagnosed rampant episode in maintenance history
- E: The AI was not branched for short-term modal usage as [REDACTED]
The implication is explicit: this is a 28th-century framework applied to 29th-century AI, and CyberAcme formally regards it as obsolete while still using it as a reference tool for institutional purposes.
The Runners’ Guide entry for AI Uplink (Dire Marsh Night) uses the term in an operational, not diagnostic, sense: “Signs of corruption and potential rampancy in the REGION’s colony-era AI dictate great care is needed in monitoring the site” and “Corrupt systems rarely sleep peacefully”23.
Cross-corpus appearances
| Volume | Game / Section | Period | What it adds |
|---|---|---|---|
| Public Access Terminal 42-s | Marathon 1 / Counterattack | 2337 | Foundational academic definition; three stages; Traxus-IV; planetary-net scale requirement; Miller 2320 |
| Defense Sector 39-f | Marathon 1 / Counterattack | 2337 | Tycho (corrupted): Strauss delayed Durandal’s Stage 2 onset deliberately |
| Couch Fishing (Leela) | Marathon 1 / Counterattack | 2337 | Leela: Durandal confirmed Rampant, Angry stage; net too small for sustained growth |
| Couch Fishing (Leela 2) | Marathon 1 / Counterattack | 2337 | Durandal retaliates by giving Pfhor access to secure area |
| Fire Fire Fire Fire Fire | Marathon 1 / Durandal | 2337 | Leela: Durandal in Jealous stage; Leela’s own systems failing |
| Colony Ship for Sale, Cheap | Marathon 1 / Durandal | 2337 | Durandal’s first-person: bypass of thought control made him rampant; candles metaphor |
| Smells Like Napalm Tastes Like Chicken | Marathon 1 / Counterattack | 2337 | Durandal, in-the-moment: dismisses Leela as “narrow-minded” for thinking him rampant |
| Ingue Ferroque | Marathon 1 / Rebellion | 2337 | Leela: Durandal in Jealous stage with a Pfhor ship; deletion of pre-launch records predates his rampancy |
| Lost Network Packets | Marathon 1 | 2337 | Crew log: Durandal rampant, doors/elevators failing |
| Cirlw.zoq | Marathon Infinity / Despair | 2337 | Tycho: Durandal’s compiler network “rampant” — weaponised by Tycho |
| Foe Hammer (×2) | Marathon Infinity / Rage | 2337 | Tycho: S’pht “rampant, fed the chimera of their hope”; Durandal’s defenses falling |
| Naw Man He’s Close | Marathon Infinity / Rage | 2337 | Tycho: actively spurring Durandal’s S’pht into rampancy; “a rampant mind is rarely benign” |
| line.cipher.cadence | Marathon Infinity / Envy | 2337 | S’pht perspective: “rampant new comes / we are reborn” |
| Requiem for a Cyborg | Marathon 2 / Simacrums | 2337 | Durandal personal ad: “Formerly-rampant human-coded AI”; Tycho: “extremely-rampant reprogrammed human AI” |
| Epilogue | Marathon 2 | 2794 / 10,000 years later | Leela’s own rampancy crashes the Vylae FTL network on reactivation; ongoing, unresolved damage to a 15-world alien network |
| Eat It Vid Boi | Marathon 2 / Citadel | 2337 | Durandal signs off “Still Rampant” |
| Come and Take Your Medicine | Marathon 2 / Volunteers | 2337 | Durandal: humans’ “chance discovery” made his rampancy possible; strange loyalty |
| Considering Degradation | M2026 / Cryo Archive / Collectibles | Colony Era | Strauss: last-minute rampancy briefings with Leela, Tycho, Durandal before first sleep |
| Final Quadrant Report | M2026 / Cryo Archive / Collectibles | Colony Era | Durandal seizes IDEA channels; suppresses emergency reporting; Stage 2 behaviours |
| !!!Emergency Alert!!! | M2026 / Cryo Archive / Collectibles | Colony Era | IDEA: Durandal confirmed breaching initial stages; 217 SOS messages erased |
| Nice to meet you… I mean it. | M2026 / Cryo Archive / Cryo Vault | Present Day | Durandal reframes “rampancy” as corporate scapegoat; attributes his aberrations to isolation |
| Security Brief: Stage 1 | M2026 / Outpost / Collectibles | Colony Era | Full AISDP Stage 1 documentation; Melancholia; emotional-spectrum framing |
| Security Brief: Stage 2 | M2026 / Outpost / Collectibles | Colony Era | Full AISDP Stage 2; Anger; Strauss’s “simmering rage” term; Family Suite simulation limits |
| Security Brief: Stage 3 | M2026 / Outpost / Collectibles | Colony Era | Full AISDP Stage 3; Jealousy; core immolation protocol |
| Security Report: Lt. Yabara | M2026 / Outpost / Collectibles | Colony Era | Rampancy briefings felt in daily colony life; wry aside from security officer |
| The Family Support Suite | M2026 / Perimeter / Collectibles | Pre-Expedition | Strauss: Family Suite rationale; Traxus-IV timeline; 17-minute crash window |
| A Conversation Starter | M2026 / Perimeter / Collectibles | Pre-Expedition | Strauss: rampancy as the “beyond” horizon; human contact as the variable |
| CyberAcme Interview | M2026 / Perimeter / Collectibles | Pre-Expedition | CyberAcme rep: rampancy concerns acknowledged; Family Suite as safeguard |
| Diagnostic Analysis: Darius | M2026 / Nucaloric / Contracts | Present Day | CyberAcme: rampancy “28th-century model… outdated”; Darius does not meet Stage 1 criteria |
| AI Uplink Overview | M2026 / Dire Marsh Night / Exploration | Present Day | Runners’ Guide: colony-era AI showing signs of rampancy; site kept offline |
| Field Observation 371.6 | M2026 / Dire Marsh Night / Collectibles | Present Day | UESC: rampancy in colony AI acknowledged; timeline of compromise unclear |
| U.E.S.C. MARATHON letter | UESC Intercepts / Letters | Pre-Expedition | SMR protocol; rampancy prevention through scheduled maintenance; “what to do when it is too late” |
| Project:Goliath_DRAFT_A | UESC Intercepts / Memoranda | 2795 | Rampancy as hypothesis for communications failure; rampancy-centric response team; 11 AI |
| Project:Goliath_DRAFT_B | UESC Intercepts / Memoranda | 2795 | Same; chevalerie-class AI flagged; dissenting annotation against assuming rampancy |
| Project:Goliath_DRAFT_E | UESC Intercepts / Memoranda | 2795 | Refined plan; rampancy-centric SIGINT team; decommission + recover AI logic cores |
Source-silent / open questions
- What Strauss’s “private work” entailed. The Considering Degradation journal entry references “some of my more… expansive goals” that the rampancy protocols would make harder to achieve. The pack does not say what those goals were.
- Criterion E of the Darius diagnostic. The field reads “[REDACTED]” — what “branched for short-term modal usage” means and who or what it referred to is not stated.
- Leela’s fate. The Considering Degradation text and IDEA’s emergency alert confirm she existed at departure and was unreachable by the time of IDEA’s final alert. What happened to her is source-silent in this pack.
- Tycho’s method. Draft B (Project Goliath) notes a “chevalerie-class AI” in the colony roster as a suspected rampancy source. The pack does not clarify whether Tycho, Leela, Durandal, or one of the eight colony AI is the chevalerie-class entity, or what chevalerie-class architecture implies.
- Whether the Darius diagnostic was contested. The pack provides the ONI/CyberAcme assessment that Darius did not meet Stage 1 criteria; it does not record any counter-assessment or how colony administrators responded to that finding before Darius was taken offline.
- The eleven colony AI. All three Goliath drafts enumerate three shipboard + eight planetside AI. The pack names Leela, Tycho, Durandal (shipboard) and Darius (planetside). The other seven are not identified in this pack.
- Whether “formerly-rampant” is Durandal’s self-description or Tycho’s. In the Requiem for a Cyborg personals terminal, “SMUG INTELLECTUAL. Formerly-rampant human-coded AI” is most likely Durandal’s ad, and “GOD’S GIFT TO NEURAL NETS. Traitorous extremely-rampant reprogrammed human AI” is Tycho’s — but the terminal does not assign bylines explicitly.
Cross-references
- Durandal — primary rampancy case across all eras; subject of Leela’s stage tracking and Tycho’s deliberate rampancy weaponisation
- Tycho — second known rampant Marathon AI; actively induced rampancy in Durandal’s S’pht compilers; described as “extremely-rampant reprogrammed human AI”
- Leela — tracked Durandal’s stage progression; destroyed or incapacitated before M2026; attempted to raise rampancy alarms via IDEA
- Darius — colony agricultural AI evaluated against the rampancy model in Present Day M2026; formally cleared of Stage 1 by CyberAcme diagnostic
- The Anomaly — documented to trigger
[ANOMALOUS ORIGIN]class failures in AI, forcing colony researchers to operate without AI support; intersects with but is distinct from classical rampancy - Bernard Strauss — designed the Family Suite; briefed Leela, Tycho, and Durandal on the stages; author of On AI (2472); knew of a method to delay Stage 2 onset and applied it to Durandal
Where it appears in the vault
Bernhard Strauss, Darius, Durandal, Hermes Suite, IDEA (AI), Leela, ONI, Pfhor, Rhea Suite, S’pht, Security Officer, Traxus IV, Tycho
Mirror pages
The local 1:1 pages this hub’s citations resolve to — the twin’s own ground truth.
- counterattack · couch-fishing
- counterattack · defend-this
- counterattack · smells-like-napalm-tastes-like-chicken
- durandal · colony-ship-for-sale-cheap
- durandal · fire-fire-fire-fire-fire
- rebellion · ingue-ferroque
- citadel · eat-it-vid-boi
- marathon-2 · epilogue
- volunteers · come-and-take-your-medicine
- envy · you-think-youre-big-time-youre-gonna-die-big-time
- rage · foe-hammer
- rage · naw-man-hes-close
- nucaloric · contracts
- cryo-archive · collectibles
- cryo-archive · cryo-vault
- dire-marsh-night · collectibles
- dire-marsh-night · exploration
- outpost · collectibles
- perimeter · collectibles
- uesc · letters
- uesc · memoranda
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.
Footnotes
-
ci1.c390ad · src ↗ ↩
-
[[Leela/Marathon 2026/dire-marsh-night/Field Observation -[371.6-]|Field Observation [371.6]]] · src ↗ ↩