Icarus (colony AI)
Disambiguation: This hub covers Icarus the colony AI — the Astromapping / Communications / Transportation intelligence of New Cascadia’s Rhea suite, working under Tycho aboard the UESC Marathon. Not the Icarus asteroid government or any other entity sharing the name.
Icarus is one of eight Strong colony support intelligences (family suite Rhea, Traxus X-A series, 64 RB logic core, inception 2461) built by Traxus OffWorld Industries for the New Cascadia colony on Tau Ceti IV.1 His attributed motto: “Connection makes us whole.”2
What the source establishes — canon
Role and functions. Icarus’s primary function is colony communications and transportation — zone-to-zone travel, resource shipping, and planet-to-Marathon transport. His secondary function is star-mapping and navigational support; his tertiary function is maintaining the colony’s Impact Risk Table.2 Captain Clemente di Roxas’s colony AI overview describes him as responsible for “Astromapping, Communications/Connectivity, Transportation.”1
Working under Tycho. Icarus works “undere Tycho aboard the Marathon” — a direct supervisory relationship with one of the Marathon’s three ship AIs.1 Of all the colony-focused support intelligences, Icarus spent the most time active (in a limited capacity) during the voyage from Sol to Tau Ceti, aiding Leela, Tycho, and UESC Marathon operational command in navigation as part of his star-mapping duties.2
Unique architecture: orbital core. Icarus is the only colony AI whose core is not based on Tau Ceti IV. His central intelligence is designed as an interconnected array of orbital satellites with sub-routines located locally on the surface. This linked system creates an intricate communications network protected from planetary interference.2
Deployment sequence. Icarus is first deployed to the Tau Ceti IV surface as sub-routines within the initial wave of outpost stations. His full deployment and core migration takes place once the colony’s central habitats and main support zones are established.2
Collaboration with Bastion. Di Roxas notes that Icarus “will collaborate with Bastion to make sure those [communications and transportation] systems are able to expand seamlessly along with the colony.”1 Bastion’s own cerebral record confirms this: his Sub-Suite is listed as “Icarus; Naraah,” placing Icarus as a key partner in infrastructure work.3 Bastion’s initial planetary survey was performed “in coordination with Arthur, Leela, and Tycho” — the same command chain Icarus operates within.3
Family suite structure. Arthur’s cerebral record lists Icarus in both the Main Family Suite (all eight colony AIs) and the Sub-Suite: Icarus; Darius — meaning Icarus and Darius are specifically grouped as Arthur’s supporting sub-suite.4 Bastion’s record mirrors this, placing Icarus in his own Sub-Suite alongside Naraah.3 Icarus’s Focused Family Suite is Icarus, Arthur, Bastion — his three closest operational relationships.2
Colony presence noted in curriculum. A school-age edutainment lesson (“Our Cosmic Home”) produced for young New Cascadia colonists directs students to “interview a friendly support AI (Bastion or Icarus) about other colony planets” — presenting Icarus as accessible and colony-facing at the time the curriculum was produced.5
Listed in the Marathon’s complement. Captain di Roxas’s Marathon ship overview lists Icarus among the eight colony AIs (“Arthur, Lilith, Bastion, Icarus, Gabriel, Naraah, Darius, Joy”) who will oversee settlement of Tau Ceti IV.6
Secondary Colonization Target list — never delivered to Sol. A UESC letter dated 19 July 2797, sent from the Unified Earth Space Council Center (Strauss Archology, Earth) to the crew of the investigatory mission dispatched toward Tau Ceti, raises the possibility that New Cascadia was forced to abandon its Primary Colonization Target and relocate to “one of the candidates from the list Icarus surely compiled during the known duration of their time in the Tau Ceti system.” The letter states plainly that neither Icarus nor colony leadership ever supplied Sol with such a list, and expresses hope that the data might be recovered on-site at New Cascadia.7 This is the pack’s only reference to a Secondary Colonization Target list, and the only source establishing that Icarus’s star-mapping/navigational role was expected to extend to identifying fallback colonization sites beyond Tau Ceti IV.
Cross-corpus appearances
| Volume | Location | What it adds |
|---|---|---|
| Tau Ceti IV Colony AI1 | Cryo Archive · Collectibles | Roster, Rhea suite, Traxus build; Icarus function (Astromapping/Comms/Transport); works under Tycho; collaborates with Bastion |
| UESC Marathon Overview6 | Cryo Archive · Collectibles | Icarus in colony AI complement of 8 |
| Our Cosmic Home5 | Dire Marsh · Collectibles | Icarus named as approachable colony AI for student interviews; colony-facing role |
| Cerebral Record: Arthur4 | Dire Marsh · Collectibles | Icarus in Main Family Suite and Sub-Suite: Icarus; Darius under Arthur |
| Cerebral Record: Lilith8 | Dire Marsh · Collectibles | Icarus in Main Family Suite |
| Cerebral Record: Bastion3 | Dire Marsh · Collectibles | Icarus in Bastion’s Sub-Suite (Icarus; Naraah); Bastion surveyed with Arthur, Leela, Tycho |
| Cerebral Record: Gabriel9 | Dire Marsh · Collectibles | Icarus in Main Family Suite |
| Cerebral Record: Icarus2 | Dire Marsh · Collectibles | Full role breakdown; orbital satellite core; voyage-active; Impact Risk Table; Focused Suite |
| Project:Goliath letter7 | UESC Intercepts · Letters | Icarus expected to compile a Secondary Colonization Target list during the voyage; list never delivered to Sol |
Source-silent / open questions
- Icarus’s current status in the M2026 present day is not addressed in any pack volume — whether he is online, compromised, or destroyed is unknown.
- The Impact Risk Table (his tertiary function) is named but its content, operational history, and whether any entries were triggered are not elaborated.
- The nature of the “sub-routines” deployed locally on Tau Ceti IV versus his orbital core — how they communicate, whether surface sub-routines survived colony-era events — is not described.
- The pack contains no volumes showing Icarus speaking in first person or exhibiting behavioral traits (unlike Arthur, Lilith, Bastion, Gabriel, each of which has an attribution quote). His attribution “Connection makes us whole” appears in his Cerebral Record but is the only window into his expressed perspective.
- No volume in the pack addresses any failure, degradation, or anomaly affecting Icarus — unlike Darius, whose pack includes maintenance logs and a diagnostic. Whether Icarus has a parallel record is not shown here.
- The
Our Cosmic Homecurriculum states “three AI stayed behind to keep the ship running and support New Cascadia” — but does not name them.5 Whether Icarus (whose core is orbital) is among those three is not stated. - Whether Icarus’s Secondary Colonization Target list was ever compiled, lost, or simply never transmitted is not stated — the UESC letter only confirms it was never received at Sol.7 Whether it survives anywhere in New Cascadia’s records for the investigatory mission (or the player) to recover is source-silent.
- A separate, unrelated “War between Icarus and Thermopylae” (2194) appears elsewhere in the pack’s Sol-system chronology — this refers to a place/conflict predating the colony AI’s 2461 inception and is not this Icarus. Flagged and rejected as a naming collision, not a hub gap.
Cross-references
Rhea Suite · Tycho · Bastion · Darius · Arthur · Lilith · Gabriel · Joy (AI) · Naraah · New Cascadia · The Anomaly · Leela · UESC Marathon
Where it appears in the vault
Arthur, Bastion, Darius, Gabriel, Joy, Lilith, Marathon 2026, New Cascadia, New Cascadia and the Anomaly, Rhea Suite
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.