Project Goliath
A classified UESC Security Council programme — codenamed GOLIATH (internal shorthand PRO:GO) — to dispatch a mission to re-establish communications with New Cascadia and the UESC Marathon at Tau Ceti IV; accompanied by a companion project, PROTUS (POR), covering evidence files and runner threat assessment; the entire programme was subsequently the target of a multi-party intelligence breach led by MIDA, with secondary involvement from Traxus OffWorld Industries and Sekiguchi Genetics.
What the source establishes — canon
Origins and stated purpose
The earliest intercepted UESC document on Project Goliath is Draft A, dated 2 November 2795, a TOP SECRET memorandum from the United Earth Space Security Council Center, Reconciliation Court, Building 1A, Strauss Archology, New York, addressed to the Secretary-General1. Its stated subject is: “Required Actions to Re-Establish Communications and Investigate Disruption of Same with the UESC Marathon and the Terran Colony, New Cascadia, at Tau Ceti.”
Draft A defines two primary objectives: (1) re-establish reliable communications with New Cascadia; (2) establish dialogue with colony leadership or, alternatively, re-establish contact with shipboard AI or colony AI1. A secondary objective frames the mission as a demonstration of UESC reach and resolve to Mars, Luna, and Main Belt allies1.
The document explicitly acknowledges a non-zero likelihood that the communications disruption originated in a rampancy event, citing reference document V-17(m)07427 / Traxus IV, 22061. This rampancy-risk citation appears verbatim in every draft of the Goliath memo123.
The draft sequence and internal disputes (Drafts A, B, E, and the email thread)
The pack contains four documents in the 2795 drafting cycle: Draft A (2 Nov), an email chain between LM_102009 and AS_101186 (23 Oct, all same day), Draft B (20 Oct), and Draft E (22 Oct). The email chain predates both Draft B and Draft A in calendar terms, and its content reveals the internal politics driving the draft sequence4567.
LM_102009’s email (23 Oct 2795) describes the project as “backsliding,” noting at least two parallel drafts from “hardline conservative constituencies,” active lobbying to include ships scheduled for mothballing (including the MDF Electris CSGN-28, explicitly flagged as not demilitarized and equipped for orbital bombardment), and proposals reaching fourteen ships with combat troops outnumbering engineers and support personnel four-to-one4.
AS_101186’s reply proposes stripping the proposal to a bare minimum: one ship (acknowledged to require military class for speed), minimum personnel, with a security complement accepted as unavoidable. The strategy is explicitly to get budget-board sign-off before “war hawks have a chance to react”5. A follow-on email from LM_102009 proposes drawing from the UIL Rapid Reaction Group framework, made “less enforcement and more assistance-centric,” and suggests replacing cyborgs with clones wherever feasible — citing lower cost, lighter weight, and adaptability — with particular emphasis that “when the Marathon left for Tau Ceti, cyborgs were WEAPONS OF WAR,” and that the colony would perceive them as such6. AS_101186 agrees and recommends tying up the militarist proposals in subcommittees indefinitely7.
Draft B (20 Oct 2795) is the most militarised surviving draft2. Its primary objectives explicitly name MIDA as a suspected anti-government element that may have fabricated or exacerbated the communications disruption to seize control of the colony2. Section 3 details direct actions against MIDA: actions designed to “provoke local MIDA and pro-MIDA factions, thereby gaining increased political acceptability and justifying increased retaliatory actions against MIDA and pro-MIDA factions”2. The force package in Draft B is substantially larger: one company-strength unit (three platoons of 2nd-gen clones + one platoon of 3rd-gen cyborgs, Mjölnir Mk VII–IX / Sharur Mk 2–6 class), plus two squad-strength SIGINT units with 200 2nd-gen clones for rampancy response, plus three platoon-strength HUMINT infiltration units with 400 2nd-gen clones for local and Tau Ceti counter-intelligence2. Internal annotations (ADNM notes) record: concern about Tau Ceti IV’s 2-atmosphere sea-level environment and whether the 97-year travel time suffices for acclimatisation without aging degradation; acknowledgment that UIL standards killed development of ecosystem-specific clones; and an annotator (ASG MP) flagging that the colony AI roster includes a chevalerie-class AI, identified via reference documents Y-05(m)12247 and Y-65(m)035452.
Draft E (22 Oct 2795) moderates the Draft B militarism3. MIDA is no longer named in the primary objectives; the framing returns to “anti-government elements” with a dialogue-first posture3. The force package is scaled back: one platoon-strength Engineering Unit (50 2nd-gen clones), two squad-strength SIGINT security units (48 3rd-gen cyborgs, Mjölnir Mk VII–IX / Sharur Mk 2–6), and one rampancy-centric SIGINT unit (40 2nd-gen clones, Mimir Mk I–II / Odin Mk III–V / Athena α–δ class)3. A SRSG annotator (LR) explicitly objects to sending Mjölnir-class assets: “there is no way the colony will see that as anything but overtly aggressive”3. The chevalerie-class AI citation appears again in the rampancy section, with the same ref docs, alongside a counter-note that no regularly-maintained chevalerie-class AI has ever displayed rampancy3. All three memos carry an identical worst-case provision: “destroy all surface assets and reassess potential sites for a new colony on Argolis” (ref. doc. W-95(t)01143 / Project: Marathon)123. Draft B labels this section “NUKE AND PAVE”; Draft E uses plain language. Annotations in Draft B explicitly discuss the viability of nuclear weapons, antimatter demolition charges, and in-system asteroid weaponisation2.
All three memos share identical security markings: TOP SECRET, DOWNGRADED AT 12 YEAR, SEALED UNTIL INTENDED ARRIVAL DATE 20/4/2894, INTERVALS: NOT AUTOMATICALLY DECLASSIFIED, UESC DIR 6123. The issuing address is Reconciliation Court, Building 1A, Strauss Archology, New York123.
The vessel: UESC Equanimity
Draft A names the mission vessel as the UESC Equanimity T-SR 151, Kingfisher-class Salvage and Rescue craft, to be refueled and overhauled with mission-specific modifications1. Drafts B and E do not name the vessel explicitly, but all three memos acknowledge this is effectively a one-way trip: a round trip would take approximately 200 years, meaning personnel who arrive at Tau Ceti would return to a Sol system as alien to them as the colony3.
The AI roster and rampancy-risk citations
Every draft records eleven AI in total — three shipboard, eight planetside — each requiring its own solution for decommissioning123. Every draft cites the same rampancy precedent: reference document V-17(m)07427 / Traxus IV, 2206123. Draft B’s annotations identify a chevalerie-class AI in the colony roster from manifest documents; a second annotator counters that the chevalerie class has no meaningful instability history, citing an eighth-generation chevalerie running Hy-Brasil since 2752 with no issues2. Draft E repeats this exchange3.
Traxus surveillance of Project Goliath (2888)
Four intercepted Traxus board chat logs, dated 24–26 May 2888, document Traxus OffWorld Industries (TOI Board) conducting independent surveillance of Project Goliath nearly a century after the UESC drafts891011.
24 May, 02:15 PST: NinoDC_0312 informs the board that their intel on Interorbital United Shipping’s interest in reopening old routes is “high confidence” and “matches long-run surveil interests related to Project: GOLIATH.” UrosBS_0111 reports the pertinent data sets are passphrase-protected and scattered across the net; netcrawlers are searching for the passphrase fragments8.
24 May, 04:45 PST: UrosBS_0111 reports that crawlers have hit on two United Shipping passphrases — CTEQNQIA and VKVCP — with more expected by morning. Simultaneously, HedvT_6221 and NinoDC_0312 confirm they have engaged SekGen (Sekiguchi Genetics) with a purchase order for biomata supplies “required for agents in the field.” KrisBD_4505 advocates for “plausible deniability” via freelancers rather than Traxus security forces; UrosBS_0111 expresses reservations. The purchase order is described as obfuscated to avoid United Shipping scrutiny, issued through non-standard channels but slipped into approved order flows afterwards9.
25 May, 04:08 PST: UrosBS_0111 states that “MIDA disruption escalating. Project risk increasing.” and “we are not the only ones shadowing Goliath.” Contracts are finalised and triggered; Nino confirms logistics are “on track for TCIV.” An incident at OxPa B 01 (a shaft collapse with 53 casualties, 300+ injured, and 304 biomata lost) is discussed; the board notes that “clone-wear workers” all survived and were ejected10.
26 May, 08:45 PST: UrosBS_0111 announces: “United Shipping breached. Goliath files cracked. The first floodgate.” The board discusses openly that UESC infodef will respond. KrisBD_4505 states: “Goliath = TCIV is a conversation starter. Confirmation of Equanimity > TCIV changes everything.” The board concludes that Traxus can leverage the breach to bring the UESC to the table; the channel is to be wiped by VLCN on the turn11.
The Traxus chat sequence establishes: (a) the name “Goliath” was in active UESC use as late as 2888; (b) the UESC Equanimity’s destination (TCIV) was the core secret being protected; (c) MIDA is confirmed as the primary party penetrating the Goliath files; (d) Traxus and Sekiguchi Genetics are secondary parties with defined roles (intel/biomata procurement); (e) freelancers contracted for an unnamed field operation tied to TCIV891011.
The intelligence breach: OPERATION STARTING LINE
The UE-Intelligence Division classified report STARTING LINE (case type: Multi-target Threat Assessment, status and classification redacted) provides the UESC’s own account of the Goliath breach12. Its summary: “External infosec breach compromised vital intelligence related to system-wide security. Highly-classified details specific to PRO:GO and its target were discovered by non-UESC operatives with intent to disseminate.”
Parties listed: MIDA (primary); Traxus OffWorld Industries (secondary); Sekiguchi Genetics (secondary). Additional parties redacted12. The document notes: “Initial disruption points to MIDA instigation. Involvement of entities with direct connect and/or operational relations with UESC and UESC sub-branches requires thorough consideration and varied clearance approvals.”12
The incident report index (page 9 of 33) lists 15 case files, of which six are visible: board chat 001 (trxus); OxPa B 01 incident report; SekGen comm IR; biomata PO discrepancy; Yoshito T. investigation; and runner activity trackers (E.init, EO.init, M.init). The remainder are security-classified12. The document confirms PRO:GO and a related project abbreviated POR were both compromised12.
Project Protus (POR)
A separate intercept header, Project:Protus_UNUS, reference B-24(i)013437, contains five evidence file links13:
_evidence file_1841....Director Deposition_evidence file_1842....Unknown Presence_evidence file_1843....Site Survey_evidence file_1844....Colony_evidence file_1845....Runner Threat Assess
The document provides no further text — only the reference number, the project name Protus, and the five evidence file titles. The linked URLs resolve to video content (YouTube) not captured in the Mirror. The STARTING LINE report confirms POR (Project Protus) was compromised alongside PRO:GO12.
The intercept header for Project:Goliath_PROGO (reference T-15(i)134349) and the header for Project:Goliath_DIGICORR (reference B-74(i)924017, a FROM/TO communication between LM_102009 and AS_101186 dated 23 October 2795) both appear in the pack but contain no body text beyond their reference numbers and metadata1415.
Cross-corpus appearances
| Volume | Section | What it adds |
|---|---|---|
| Project:Goliath_DRAFT_A | UESC memoranda | Draft A (2 Nov 2795): primary/secondary objectives, UESC Equanimity, 11 AI, rampancy ref Traxus IV 2206, worst-case Argolis |
| Project:Goliath_DRAFT_B | UESC memoranda | Draft B (20 Oct 2795): MIDA named as target; provocation strategy; NUKE AND PAVE; chevalerie-class AI noted; full military force package |
| Project:Goliath_DRAFT_E | UESC memoranda | Draft E (22 Oct 2795): moderated draft; cyborg-sensitivity debate; same rampancy ref; Argolis fallback retained |
| CONFIDENTIAL_PROJECT: GOLIATH (LM→AS) | UESC emails | 23 Oct 2795: 14-ship war-hawk draft described; LM alarmed at MDF Electris inclusion |
| CONFIDENTIAL_PROJECT: GOLIATH (AS→LM) | UESC emails | 23 Oct 2795: strip-to-one-ship counter-strategy; get budget sign-off before hawks react |
| CONFIDENTIAL_PROJECT: GOLIATH (LM→AS, 06:08) | UESC emails | 23 Oct 2795: UIL Rapid Reaction Group framework to be adapted; clone-over-cyborg argument |
| CONFIDENTIAL_PROJECT: GOLIATH (AS→LM, 06:22) | UESC emails | 23 Oct 2795: clones preferred; cyborgs were “WEAPONS OF WAR”; tie hawks in subcommittees |
| Project:Protus_UNUS | UESC emails | Project Protus header; 5 evidence file titles; no body text |
| Project:Goliath_PROGO | UESC letters | Header + reference number only; no body text |
| Project:Goliath_DIGICORR | UESC emails | Header + reference number + sender/recipient only; no body text |
| TRAXUSCONNECT 24 May 02:15 | Traxus intercepts/chats | Intel on United Shipping tied to Goliath; passphrase hunt begun |
| TRAXUSCONNECT 24 May 04:45 | Traxus intercepts/chats | Two passphrases found (CTEQNQIA, VKVCP); SekGen PO for biomata; freelancer debate |
| TRAXUSCONNECT 25 May 04:08 | Traxus intercepts/chats | MIDA disruption escalating; contracts triggered; OxPa B 01 shaft collapse |
| TRAXUSCONNECT 26 May 08:45 | Traxus intercepts/chats | Goliath files cracked; “Equanimity > TCIV changes everything”; UESC brought to table |
| STARTING_LINE.log | UESC terminal | UE-ID breach report; PRO:GO and POR compromised; MIDA primary; Traxus + SekGen secondary |
Source-silent / open questions
- The final approved version of Project Goliath is not in the pack. The draft sequence ends at Draft E; whether a later draft was adopted, what its force package was, and whether the UESC Equanimity actually departed Sol are source-silent in this pack.
- The identity of LM_102009 and AS_101186 is not stated. Their email domain (UESSC.egn) confirms UESC Security Council affiliation; their full names and roles are source-silent.
- The identity of “Mx Moreau”, referenced in Draft E’s annotations as an annotator whose speculation was cautioned against, is not confirmed. Whether this is the same individual as any named M2026 character is source-silent.
- The rampancy citation ref V-17(m)07427 / Traxus IV, 2206 is named but its content is not reproduced. What the Traxus IV rampancy event was, how it ended, and why it is the operative precedent are source-silent in this pack.
- The chevalerie-class AI in the colony roster is identified by two reference documents (Y-05(m)12247, Y-65(m)03545) not reproduced in the pack. Which of the eleven AI is the chevalerie class — and whether it is Leela, Durandal, or Tycho — is not stated in this pack.
- Project Protus (POR): beyond the five evidence file titles and the reference number, the pack contains no substantive text. The relationship between Protus and Goliath (companion project, sub-operation, or parallel programme) is source-silent.
- The PROGO letter (ref T-15(i)134349) and the DIGICORR email header (ref B-74(i)924017) contain no body text in the pack. Their content is source-silent.
- The OxPa B 01 shaft collapse (53 casualties, 304 biomata lost, all clone-wear workers survived) is discussed as “timely” by the Traxus board. Whether this was a staged event, sabotage, or genuine accident is not stated; annotations flag it only as “no signs of hostilities / site error.”
- The individual identified as “Yoshito T.” in the STARTING LINE incident file list (ueid.casefile5cf-0_yoshito_t_invst.rpt) is not described elsewhere in the pack. Source-silent.
- VLCN, the Traxus entity tasked with wiping the channel, is referenced only by handle. Its nature (AI, human operative, automated system) is source-silent.
- Whether the breach of the Goliath files by Traxus in 2888 and MIDA’s parallel breach resulted in the UESC actually being “brought to the table,” and what that negotiation produced, is source-silent.
Cross-references
Cerberus · MIDA · UESC Marathon · Traxus IV · New Cascadia · Bernhard Strauss · Traxus OffWorld Industries · Sekiguchi Genetics · UESC Equanimity · New Cascadia · Leela · Durandal · Tycho
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.