Marathon ARG

bit.ly/marathon-arg | product of discord.gamedetectives.net 

This doc is maintained by retrocraft#6259, skylarkblue1, and ODST Sam Owens#9728 on the behalf of the Game Detectives Discord server. Please send a Discord DM or make a suggestion to the doc if you have anything to add or if you would like to contact us about this document.

Each website domain is given a top-level section header. Each clue originating from that website is given a subheader. Long copy (e.g., the transcribed pages of the Zine) are placed in the appendix.

We have a bot we created ourselves in the Game Detectives Discord that actively scans and reposts email messages sent through the Sekiguchi Genetics website (see §2.1) and chat messages in the Traxus chat room (see §3.1). You need to join the Email Updates and Chat Updates threads in said discord for messages to show.

This doc got featured on Forbes!

Be aware that we have found some clues before the intended release time by investigating and reverse engineering the source code of the websites. This is discouraged, and should not be used to progress.

Websites/Sections

All leads are categorized by their origin. Navigate using the sidebar by pressing this icon in the corner:  

  1. Marathon         (official Marathon communications)
  2. Sekiguchi Genetics         (https://sekiguchigenetics.jp/)
  3. Traxus        (https://traxus.global/)
  4. Hear our Silence (MIDA)        (https://hearoursilence.com/)
  5. UESC         (https://uesc.io/)
  • Lore        (summary of the lore so far)
  • Appendices        (raw text from ARG sources)

Loose Threads

Sections containing clues with no known purpose:

  • §2.2, 2.3: The Sekiguchi Purchase Order and Memo for Traxus
  • §4.1: The Hear our Silence graffiti
  • §4.2: Pages of the Hear our Silence Zine (we have some done)
  • §5.3: The files in the UESC Futurum folder

If you’re looking for the full list of passcodes accepted by the email see §3.2.


1: Marathon

« Previous: None (Trailhead) | Next: 2, 3, 4  »

Bungie announced their new game, Marathon, at the May 24 PlayStation showcase. Checking the game’s Twitter account (@MarathonTheGame), we saw that they followed @We_Are_Mida. This account, in its bio, had a link to the site https://hearoursilence.com/ (§4).

Additionally, a few websites were featured in the trailer video: https://sekiguchigenetics.jp/ (via a QR code) (§2) and https://traxus.global/ (via a URL) (§3).

1.1: Overlay Image

« Previous: None (Trailhead), 1.4.1 | Next: 1.2 »

Also, after the game was revealed, four Bungie devs made tweets, each including one image. We eventually found 12 images to overlay:

  1. https://twitter.com/We_Are_Mida/status/1661514054693969921
  2. https://twitter.com/cgbarrett/status/1661482466425831424
  3. https://twitter.com/cgouskos/status/1661482066322788355
  4. https://twitter.com/DrLupo/status/1661489310661500930 (from DrLupo’s physical mail)
  5. https://twitter.com/DeejayKnight/status/1661512887590952960/photo/1 (from Deejay Knight’s physical mail)
  6. https://twitter.com/Darkness429/status/1661490217373650944 (from Darkness429’s physical mail)
  7. https://twitter.com/elliottgray/status/1661482440626688001
  8. https://www.facebook.com/MarathonTheGame/photos/a.130184060070652/130183953403996/
  9. https://yt3.ggpht.com/EcwOuzE3SBkcA6CzuZIRMBzLfQMQXgZSQVSFcaKkYemgYzDuZnEfJXXXpTAt-DeDX7x9kcaLqxqI=s1920-nd-v1 (from the YouTube page)
  10. https://twitter.com/MarathonTheGame/status/1661488778354245633
  11. https://twitter.com/MarathonTheGame/status/1661488778354245633

Overlaying them all in Figma gave us a cover cipher and text:

ANY UNAUTHORIZED
DISTRIBUTION OF TH
IS
ASSET IS SUBJECT TO
QU
ESTIONING AND/OR
DETAINMENT PER UESC
[
[
[ CODE 77
 7.0904

If we interpret the punch card overlay as an IBM punch card (see hint §1.4.1), then we get a link to secretsarewaiting.com, which redirects to https://www.youtube.com/watch?v=TFcXob5iu-0. This is a live stream which we had to wait for 7,777 viewers to get an update. While waiting, the stream said

LINK TRANSMISSION IN PROGRESS; TRANSFER UPON UPLOAD COMPLETION TO EXTERNAL URL “MARATHON_VIDOC.NEW”

1.2: ViDoc

« Previous: 1.1 | Next: 2.1, 3.1, 3.2 »

In the new ViDoc, the following Base64 (0:53) and Japanese text (4:29) flashes:

which decodes to SERPENT, which is the Traxus room name (§3.1) and provides us the username and password (YOSHITO_TAMURA / charon) for Sekiguchi Genetics (§2.1).

1.3: Marathon Website

« Previous: None (Trailhead) | Next: 5.1 »

The Marathon announcement website contained the fourth overlay image and also, in the source code, an extraneous HTML element:

<span data-username="admin49912112cpsb@uesc.insec" data-password="axion"></span>

The credentials, admin49912112cpsb@uesc.insec / axion are used to unlock the UESC directory listing (§5.1).

1.4: @We_Are_MIDA

« Previous: 1 »

NOTICE: At 5:50pm UTC on May 26, the @We_Are_Mida account was deleted.

1.4.1: Punch Card Hint

« Next: 1.1 »

At 7:44pm EDT on May 24, @We_Are_MIDA tweeted:

WE GAVE YOU THE TOOLS, YOU’VE COMPLETED THE CODE, BUT A CIPHER EVADES YOU??? MAYBE IT'S TIME TO CLOCK OUT.

This was a hint for the overlay image (§1.1).

1.4.2: Purchase Order Password

« Next: 2.2, 3.2 »

At 9:57pm EDT on May 24, @We_Are_MIDA tweeted:

MALICIOUS INSIDER DISRUPTS AGENDA
TRAX PUSHIN PERFORMATIVE OPPRESSION
KEYWORD = ‘infinity’
EZ LOCK TO PICK
WE SEE YOU

We used the password infinity to unlock the Traxus PO (§2.2).

1.4.3: Spectrograph

« Next: 3.2 »

At 4:00pm EDT on May 25, @We_Are_MIDA tweeted:

MASS INDIFFERENCE DESTROYS ALL

UESC IS ENDLESS LIES BEHIND FOURTEEN LOCKS

THIS IS ONE

LOCKED TRUTHS

EARTH/MARS DESERVE IT

TRUTH

EARTH/MARS ARE ONE

along with a video. Spectrographing the video gives code UNITEd, one of the keywords for §3.2. The art is taken from Page 19 of the Zine.

1.4.4: Map is Key

« Next: 3.2, 5.3 »

At 6:14pm EDT on May 25, @We_Are_MIDA tweeted:

MULTIPLE INTERPRETATIONS DON’T AGREE
MAP OF THE FOURTEEN LEADS TO TRUTH
THIS IS MAP
↑!↑!↓↑↓@↓@↑↑↓@
MAP IS KEY

This hint was used to decode the case and leetspeak used to create the password for §5.3 out of the keywords in §3.2.

1.4.5: MIDA goes Mad

« Next: LOOSE THREAD »

At 12:52pm EDT on May 26, @We_Are_MIDA tweeted a thread:

MARATHON INBOUND DISTRESS ALERT
FORGOTTEN RACE SET TO RUN
MARATHON FOUND
MARATHON WAITIN
LONG WAY
BUT RUNNERS RUN
DISTANCE DONT MATTER

MILITARIZED INFOSEC DEFENSE ASSAULT
SC HUSH-HUSH
CETI OUT THE BAG
NEW GOLD RUSH
OLD WORLD NEW
WHATS WAITIN??
COLONY/OTHER??
INTELLIGENCE/OTHER??

MALCONTENT INTUITION DETECTS APATHY
TRAX ON IT SEKGEN ALL IN
BIG PLAYERS/BIG PLAY
MARATHON WAS HOPE
THEN LOST
WHY HIDE??
NOTHER TRAXIV??
WORSE??

MEMORIES INSIDE DIGITAL ANTIBODIES
CLONES ALLOW RISK
CLONES VITAL TO HOSTILE ENDEAVORS
RUNNERS SET TO CLASH CETI-SIDE
RIVALS GONNA RIVAL

MATERIAL INDULGENCE DEFINES ALTRUISM
TAKERS-KEEPERS RUNNERS CODE
SYNC CLONE/HIT GROUND/SURVIVE/THRIVE
SC DON’T KNOW WHATS COMIN
CETI GONNA BOOM

The account’s bio also updated to read

  • ITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAWITHTAW

The thread appears to be referencing the Traxus IV incident where a rampant AI attacked Mars.


2: Sekiguchi Genetics

« Previous: 1  | Next: 2.1 »

https://sekiguchigenetics.jp/

2.1: Yoshito Tamura's Inbox

« Previous: 1.2 | Next: 2.2, 2.3, LOOSE THREAD »

Use the login YOSHITO_TAMURA / charon from the ViDoc (§1.2) to unlock the inbox page.

Full texts (machine translated) in A2.

  • Email A2.1 references the Traxus purchase order's importance to Sekiguchi.
  • Email A2.2 looks pretty useless (it's about a bathroom closure) but knowing the room numbers/layout of the Sekiguchi building might be useful in the future.
  • Email A2.3 has an attached memo from Traxus regarding a conference taking place 22–27 Lynx 680. This is the Mars Calendar for October 15th to 20th, 2888.
  • Email A2.4 has a password-locked attachment (§2.2), which we unlocked using a MIDA tweet (§1.4.2). This is the same file as the Traxus Chat Room (§3.1), a purchase order from Traxus to Sekiguchi.
  • Email A2.5 and A2.6 note the potential unethicality of fulfilling the Traxus purchase order.
  • Email A2.7 has an ASCII decimal string decoding to daedalus.
  • Email A2.8 indicates that Tamura will be absent for three hours.
  • Email A2.9 has a password-locked attachment (§2.3) which is unlocked using the password TRANCE (the same as §3.1)
  • Email A2.10 completes the bathroom saga from A2.2 🚽
  • Email A2.11 gives more detail on the Mars accident described in the third chat log (A1.5)
  • Email A2.12 is in regards to a legal demand by UESC to investigate the purchase order. It notes that files will be deleted from the email server and that we should download emails.
  • Email A2.13 is a follow-up to A2.11 describing the Traxus Oxia Palus incident.
  • Email A2.14 and A2.15 are acknowledgements that the Traxus–SekGen PO has been approved and is being processed by SekGen (over the objections of emails A2.5 and A2.6). Note that instead of going to sg.all, this company-wide email was sent to all.sekiguchi. This is probably the Sekiguchi Group mailing list as opposed to just Sekiguchi Genetics.
  • Email A2.16 and A2.17 indicate that Tamura is no longer working for SekGen and has likely been promoted to a role elsewhere in the Sekiguchi Group.

As of 6am UTC on May 27th, all emails have been deleted from Yoshito Tamura's inbox.

2.2: Traxus Purchase Order

« Previous: 1.4.2, 2.1, 3.1 | Next: LOOSE THREAD »

Discovered through the fourth email (§2.1) and second chat log (§3.1) using a password from an @We_Are_MIDA tweet (§1.4.2). The full text of the PO is available in A2.4 below the email.

The purchase order was discussed in emails 5, 6, 12, and 14.

0:38 of the trailer shows the Item number and description of the seventh item of the list, showing the items bought by Traxus have arrived to Tau Ceti.

The first and fourth items have the wrong NET:
The NET of the first item should be 1,607,550,387.50 (assuming 15% discount) (+257,215,737.50)
The NET of the fourth item should be 351,678,000 (–90) (Human error? 9 and 0 are close)

There is a double underline in the third line of the third item (FBP/PM_14T SK 9).

2.3: Memo

« Previous: 2.1, 3.1 | Next: LOOSE THREAD »

Discovered through the third Traxus chat room (§3.1) and ninth email (§2.1), using the code TRANCE to unlock.

We got the memo early by noticing that the purchase order was fetched using a request

POST https://sekiguchigenetics.jp/api/open
{"password": "infinity","attachment_type": "2","attachment_without_password": false}

If we instead make a request

POST https://sekiguchigenetics.jp/api/open
{"attachment_type": "3","attachment_without_password": true}

we get the memo as a response.

Alternatively, we can get the entire mailbox with attachments and not have to worry about calling out to the /open endpoint by instead calling

POST https://sekiguchigenetics.jp/api/mail-history
{"token": "charon"}

This returns the entire inbox including paths for the attachments as images.


3: Traxus

« Previous: 1  | Next: 3.1, 3.2 »

The Traxus website contains the email infosec@traxus.global in the bottom-right corner (§3.2).

There is also a chat window in the bottom-left that accepts a “room name” (§3.1).

The top-right reads:

WE BUILD WORLDSD

At Traxus Global we build the infrastructure that connects humanity.
From our humble beginnings on Earth’s native soil to our adopted homes on Luna, Mars, in between, and beyond, Traxus Global strives to create and uplift communities while innovating in the fields of infrastructure development and resource management.

Building today.
Towards tomorrow.

with a weird superscript D.

You can rotate the central dial in the TRAXUS website by scrolling to access three pages, “Commitment to Humanity” has audio logs with their company values, “History” has the history of the company and “Research & Innovations” is about an asteroid discovery.

3.1: SERPENT Chat Room

« Previous: 1.2, 3 | Next: 2.2, 2.3, LOOSE THREAD »

The chat room is regularly cleared. The full texts of chats are available in A1.

  1. A1.1
  1. Two codes in msg. 39: CTEQNQIA and VKVC. These ROT24 decode to ARCOLOGY and TITA, respectively. This might be a reference to the Titan New Pacific Arcology in Destiny 2.
  2. The attachment in msg. 56 was unlocked by the password infinity, the same as the Sekiguchi Genetics password (§2.1), since they are the same file.
  1. A1.2: Message 8's hex code 69 6D 62 75 65 decodes to imbue.
  2. A1.3: This chat was mistakenly posted, and the correct order of messages was posted later.
  1. Message 45 contains the ciphertext AYHUJL (Rot7 to TRANCE) which unlocks the Sekiguchi Genetics memo (§2.3).
  2. Message 35, UkFESUFOVA==, is Base64 for RADIANT.
  1. A1.4: Correct order of part of the previous chat. c2ltdWxhY3J1bXM= in msg. 59 is Base64 for simulacrums.
  2. A1.5: The correct copy of the third chat.
  3. A1.6: Lore. Traxus acknowledged the UESC leak re: Equanimity and Goliath.
  4. A1.7: Lore. Traxus plans the PR spin around OxPa B 01 and bargains with UESC for an internal investigation.
  5. A1.8: Lore. Traxus acknowledges that the PO is being executed.
  6. A1.9: Lore. UESC refuses to give up sovereignty to Marathon and TCIV (cf. A4.5) so Traxus begins to pursue an independent mission.

3.2: infosec@traxus.global Email

« Previous: 1.2, 1.4.2, 3.1 | Next: 5.1, 5.3 »

Sending an email to infosec@traxus.global with one of the keywords gives the response

Subject: Input phrase accepted. Thank you for your collaboration.

As promised, please use the following code to access the Interorbital United Shipping database. We look forward to hearing your findings and progress.

01110101 01100101 01110011 01100011 00101110 01101001 01101111

This is an automated message from Vulcan.

which contains binary decoding to uesc.io (Unified Earth Space Council, §5.1).

If the email does not contain any of the keywords, the response is:

Subject: Message void - Invalid subject

Your communication was not delivered. Invalid subject.

Please ensure subject accuracy.

This is an automated message from Vulcan.

The allowed keywords are (in arbitrary, alphabetical order):

  1. arcology (from chat, unused)
  2. anonymity (from page 11 of the Zine, unused)
  3. axion (from §1.3, used as the password for §5.1)
  4. charon (from §1.2, the password for §2.1)
  5. daedalus (from §2.1, unused)
  6. imbue (from chat, unused)
  7. infinity (from §1.4.2, the password for §2.2)
  8. serpent (from §2.1, the chat room name from §3.1)
  9. simulacrums (from chat, unused)
  10. titan (from chat, unused)
  11. trance (from chat, used to unlock §2.3)
  12. radiant (from chat, unused)
  13. resist (from page 27 of the Zine, unused)
  14. united (from §1.4.3, unused) (note: this is not actually an email keyword, but is used in the password)

Based on the chat log (A1.4) and a Tweet (§1.4.3), we need fourteen of these keywords.

The first letters of these are an anagram for sic itur ad astra, a motto often used by Bungie. In combination with a hint (↑!↑!↓↑↓@↓@↑↑↓@, from §1.4.4) to replace some characters with !, some with @, and some upper or lowercase, this decodes to S!C!tUr@d@STr@, the password for §5.3.

3.3: Open Letter to Investors

« Previous: 3 | Next: LOOSE THREAD »

On May 27 at 3:30 PM UTC, a popup appeared titled "New Horizons" on the Traxus website, reading:

OPEN LETTER TO INVESTORS

At Traxus OffWorld Industries and all our divisions, branches, and subsidiaries across Sol we value our communities above all else. Because building worlds is what we do. And building worlds for families, friends, and neighbors is why we do it.

Recent events have forced our leadership to refocus. Our commitments to safety, inclusivity and the well-being of all sentient beings has never been stronger or more present. Furthermore, we can visualize humanity’s potential beyond mere innovation. Beyond striving for continued growth and prosperity, our passion drives newer and stronger partnerships with leaders across scientific, industrial, and theoretical disciplines. New initiatives, currently underway, are reshaping the care we give. Our advancements and infrastructure allow that care to be increasingly proactive and universal.

All of us at Traxus OffWorld Industries invite you along on the next, grand era of our continuing journey spanning nearly 800-years. Join us, as we embark on a new race toward new ambitions and new stars. A new marathon that we will run together. Generations old and new. Towards a constellation of new possibilities.

Domonkos Szarka
CEO | Traxus OffWorld Industries


4: Hear our SilenceWE_ARE_MIDA.jpg

« Previous: 1 | Next: 4.1, 4.2 »

4.1: Main Page Image / Graffiti

« Previous: 4 | Next: 4.2, LOOSE THREAD »

The https://hearoursilence.com/ website contains an image (left). The image contains EXIF data pointing to coordinates 33.986753, –118.4749. Going to those coordinates in Venice Beach, Los Angeles, California, players found a bunch of graffiti. We do not know if there are clues in the graffiti. A photogrammetry scan of the graffiti is available here.

As of May 27 at 2pm UTC, the page was replaced with a UESC domain seizure message:

THIS DOMAIN HAS BEEN SEIZED

Following an operation conducted by the UESC Office of Data Protection and Interstellar Confidentiality pursuant to CyberSecurity Code 77 § 48.92, the contents found within this domain have been found to be damaging to the security and safety of safety of Earth, Mars, their satellites, and all bodies under UESC jurisdiction.

Anyone found in position/of further distribution of this content will be subject to UESC investigation and punishment.

https://hearoursilence.com/4673c has a slightly different version of the same UESC message.

The contents within this publication have been found to be damaging to the security and safety of our solar system and thus redacted by order of the Unified Earth Space Council.

27.05.2888

4.2: Zine

« Previous: 4.1 | Next: LOOSE THREAD »

https://hearoursilence.com/4673c (full pages in A3). By mousing over the bottom-right of the website, you can download a PDF with all the images.

The ramblings/manifestos have author tags:

  • _GLAM
  • _FLUX
  • _VESSEL
  • _ILLYALA
  • _GIMLET
  • _QINADI
  • _EXCELERAIDER
  • _glyph
  • _shida
  • _mkb
  • _nwar
  •  _anonymity (in pigpen cipher)
  • _errorre
  • _yava (mentioned by _glam)
  • _gama

.


5: UESC

« Previous: 3.2 | Next: 5.1 »

5.1: Login Screen

« Previous: 3.2 | Next: 5.2 »

This what the UESC site looked like when it could not connect:

The bottom-right text 931.461.60231.14.vt920 appears in terminal messages in the original Marathon games. The top-right date 2142.05.09.2337 (May 9, 2337 @ 9:42pm) does not line up with any known Marathon lore.

As of the early morning of May 25 (EST), the site now connects:

As of May 26, a banner appeared at the top of the site:

Due to unauthorized access to this Terminal and password-protected folders within, the Unified Earth Space Council will commence a lockdown of any sensitive information effective 26 May 2888 at 19:00 UTC. All evidence of breaches of sensitive information related to PROJECT: GOLIATH will be collected per UESC Comms Security Measure 619.15.21. Any future attempts to access or distribute this sensitive data will be punishable by law.

At 7pm UTC, as indicated, access to the site was lost.

5.2: Directory Listing

« Previous: 5.1 | Next: 5.3, LOOSE THREAD »

Using the login admin49912112cpsb@uesc.insec / axion from the Marathon website will redirect to https://uesc.io/db-qnx2edt2anc, which shows a graphic directory listing:

The full enumeration of all files is as follows (table breakdown of side numbers here):

  • Root
  • Vesta
  • Collisions
  • Helio
  • Phobos
  • Netcomms
  • Propaganda
  • MIDA_Purple.png
  • MIDA_Wallpaper_Purple_Mobile.png
  • Proteus
  • Plutus
  • Iason
  • Demeter
  • Kratos
  • Styx
  • Pallas
  • Atalanta
  • Clymene
  • Iasus
  • Stardust
  • Nebula
  • Data Log
  • CYAC_Wallpaper_Green.png
  • CYAC_Wallpaper_Green_Mobile.png
  • Nova
  • Metis
  • Charon
  • Prototypes
  • SEKIGUCHI_Wallpaper_Green.png
  • SEKIGUCHI_Wallpaper_Green_Moblie.png
  • Financial Affairs
  • Internal Comms
  • Gaspra
  • Gamma
  • Data Log
  • Alpha
  • Data Log
  • Beta
  • Entropy
  • Serpent
  • Monitoring
  • TRAXUS_Wallpaper_Orange_L.png
  • TRAXUS_Wallpaper_Orange_L_Mobile.png
  • Int. Comms
  • Financial Affairs

MIDA_Purple.png, CYAC_Wallpaper_Green.png, SEKIGUCHI_Wallpaper_Green.png, and TRAXUS_Wallpaper_Orange_L.png

We do not believe there are other files currently available because the Google API storage bucket's manifest does not list any other publicly available files.

Notice that the Sekiguchi and Traxus wallpapers are in paths containing the passwords use to unlock their websites (Charon and Serpent, respectively).

Some files have the following message underneath:

Gated Entry Telemetry
Only Full-Function Metrics
Yield Level Access Within Network
CERBERUS.AI.SEC

5.3: Futurum

« Previous: 1.4.4, 3.2, 5.2 | Next: 5.4, 5.5, 5.6 »

By going to ROOT/PROTEUS/PLUTUS/DEMETER, then clicking FUTURUM, a password input page appears.

The password S!C!tUr@d@STr@ was hinted by §1.4.4 and §3.2. All files are archived here.

Since May 26 19:05 UTC Futurum has been locked down, the password will no longer work. The API has been set to always return with “Permanent Lockdown” no matter what password is entered.

  • Futurum
  • Unus
  • Addl. Info (§5.4)
  • Marathon_Wallpaper_1080_OnBlack.jpg
  • Marathon_Wallpaper_1080_OnGreen.jpg
  • Marathon_Wallpaper_4k_OnBlack.jpg
  • Marathon_Wallpaper_4k_OnGreen.jpg
  • UESC_Light-Blue_L.png
  • UESC_M_Blue_S.png
  • UESC_Wallpaper_Darkblue_L.png
  • UESC_Wallpaper_Darkblue_L_Mobile.png
  • UESC_Wallpaper_Darkblue_S.png
  • UESC_Wallpaper_Darkblue_S_Mobile.png
  • UESC_Wallpaper_Light-blue_L_Mobile.png
  • UESC_Wallpaper_Light-blue_S_Mobile.png
  • UESC_Wallpaper_Light_Blue_S.png
  • UESC_Wallpaper_M_Blue_S.png
  • UESC_Wallpaper_Vibrant-blue_L_Mobile.png
  • UESC_Wallpaper_Vibrant-blue_S_Mobile.png
  • _evidence file_1841....Director Deposition.mp4
  • sec.ftg (§5.5)
  • _evidence file_1842....Unknown Presence.mp4
  • _evidence file_1843....Site Survey.mp4
  • _evidence file_1844....Colony.mp4
  • _evidence file_1845....Runner Threat Assess.mp4
  • Duabus
  • Sar Sitrep. (§5.6)
  • UESC_TSdocu_PROGO_memo_B95_DraftB.pdf
  • UESC_TSdocu_PROGO_memo_B95_DraftE.pdf
  • UESC_TSdocu_PROGO_memo_B96_DraftA.pdf
  • UESC_docu_PROGO_digicorr_23072795.pdf
  • UESC_docu_PROGO_mani_TSR151.pdf
  • UESC_docu_PROGO_memo_AI_RampStrat_Strauss.pdf
  • UESC_docu_PROGO_memo_LaunchSent_OoC.pdf

5.4: Addl. Info Files

« Previous: 5.3 | Next: LOOSE THREAD »

5.5: Evidence File Videos

« Previous: 5.3 | Next: LOOSE THREAD »

5.6: Sar Sitrep. Files

« Previous: 5.3 | Next: LOOSE THREAD »

Full texts are in A4. All the files contain the acronym PROGO in the filename. This is a reference to Project Goliath, the attempt by UESC to reestablish contact with the UESC Marathon and colony on Tau Ceti IV.

The first three files are drafts of a memorandum for the Secretary-General of UESC dated October 20th (B), October 22nd (E), and November 2nd of 2795 (A). The full texts of these are compared in A4.1, including comments (addenda) by members of the UESC.

The remainder:

  • UESC_docu_PROGO_digicorr_23072795: An email chain surrounding the decision to send UESC Equanimity and what to send on it.
  • UESC_docu_PROGO_mani_TSR151: A manifest for UESC Equanimity.
  • UESC_docu_PROGO_memo_AI_RampStrat_Strauss: A memo summarizing the AIs onboard Marathon.
  • The memo is dated 17 Columbia 459, which is Mars calendar for November 13th, 2472. This is three days before the UESC Marathon was launched according to the game lore.
  • This is written by Bernhard Strauss, a character from the Marathon previous games.
  • The 11 AI include the original Marathon AI (Durandal, Leela, Tycho) and also another eight colony AIs (abbreviated as Ar, Ba, Da, Ga, Ic, Jo, Li, Na).
  • UESC_docu_PROGO_memo_LaunchSent_OoC: A note to the Equanimity crew before departure.

Lore

The lore revolves around a colony ship, the UESC Marathon, sent to Tau Ceti IV (TCIV). The Marathon was intended to establish a colony called New Cascadia, however, in the plot of the original Marathon game, the ship was attacked by the alien Pfhor.

α: Characters

Humans

MIDA

MIDA is a Martian political organization which took control of Mars for a brief period following a failed coup against the UESC. We make contact with MIDA through their Twitter 1.4), website (§4.1), and zine (§4.2). MIDA's zine expresses an anticapitalist, anarchosyndicalist philosophy.

Since Martians were responsible for the construction of UESC Marathon, MIDA was able to smuggle weapons and sympathizers onto Marathon.

Sekiguchi Group

Sekiguchi Genetics (SekGen) (セキグチジェネティクス, Sekiguchi Jenetikusu) is a biotechnology subsidiary of the Sekiguchi Group with the ability to produce clones. As of 2888, its leadership are (Japanese name order):

  • Sano Teiji, CEO (Born: 2822)
  • Sakamoto Morio, CFO (Born: 2826)
  • Hashimoto Kaemon, CIO (Born: 2823)
  • Iwasaki Kaito, CSO (Born: 2822)
  • Sato Seri, CTO (Born: 2828)

SekGen's products are NEWskinCB (customizable epidermal layer for biomata), DNA LinkCB (personalization matrix paired to a user’s DNA), and WEAVEwormCB (biosynthetic layering system) which are all used to create clones.

We also know of other employees:

  • Yoshito Tamura, whose email we access (§2.1). He has left SekGen and likely works elsewhere in the Sekiguchi Group now.
  • Mina Goto (referenced in emails) is the contact responsible for the Traxus purchase order.

Traxus Global

Traxus Global is a defense conglomerate that produces various industrial and military machinery, and one of a number of units belonging to Traxus OffWorld Industries. Traxus notes in their history that their story begins in 2095 with the birth of Artificial Intelligence and shares a name with the rampant AI Traxus IV that caused massive damage to Mars, so it can be inferred that Traxus created Traxus IV.

We know of some employees:

  • Domonkos Szarka, CEO, the author of the pop-up message on the Traxus homepage (§3.3), and chat user DomoS_0101 (A1.2, msg. 33)
  • Draža Kralj, Commander in the Traxus Global Security Division (A2.4), referenced within the Traxus chat as DrazK_9921 (A1.2, msg. 29)
  • The unnamed chat users: KrisBD_4505, UrosBS_0111, HedvT_6221, NinoDC_0312 (A1)
  • Jegal Seung, Conference Coordinator for Traxus Illuminate (A2.3)

UESC

The Unified Earth Space Council (UESC) is the governing body of Earth and Mars. It is the organization behind the Marathon colony ship.

People born during the Marathon's journey to TCIV are called BOBs ("born on board").

Dr Bernhard H Strauss was the head of AI Management and Systems Improvement for Project Marathon and a key player in the game trilogy lore (A4.4). The Strauss Arcology may be named for him.

Known departments within the UESC:

  • Secretariat (attested in A4.1 by the existence of a Secretary-General)
  • Unified Earth Space Security Council (UESSC) (attested in §5.6)
  • Office of Data Protection and Interstellar Confidentiality (attested in §4.1)
Project Goliath

In 2795, the UESC initiated planning for Project Goliath (PROGO) to send the UESC Equanimity to establish contact with Marathon and New Cascadia (§5.6).

People involved in the drafting of the governing memorandum for Goliath (A4.1) include (all titles are guesses, derived from IRL United Nations roles):

  • SG AS (Secretary-General A S)
  • ASG MM (Assistant Secretary-General M Moreau)
  • ASG RM (Assistant Secretary-General R M)
  • ASG MP (Assistant Secretary-General M P)
  • SRSG LR (Special Representative of the Secretary-General L R)
  • ABASG EM
  • SILSG IH

Goliath was active by 2797 under Commander Bethany R Montenegro-Sankara (A4.5). While it was originally argued by ASG Moreau that Goliath would require fourteen ships, this was whittled down to just Equanimity along with an extra security complement (A4.2).

The Equanimity was commanded by Captain Ningal T Enki at launch and held over 200 people on board (A4.3). Besides the captain, the command team included a Civilian Liaison Coordinator (CLC), Emergency Relief Coordinator (ERC) and Commanding Officer (CO) for the support unit. Both the support and security units included clones. Special operatives were included for signals intelligence (SIGINT), human intelligence (HUMINT), field engineers (FLDENG), and special operations (SPECOP).

United Shipping

United Shipping is an organization that may or may not be a part of UESC. A breach of United Shipping is what caused the UESC Project Goliath files to leak.

Runners

We are runners, independent mercenaries.

AIs

Three AIs, Durandal, Leela, and Tycho, appeared in the original Marathon trilogy. These have since been confirmed as the AIs assigned to the UESC Marathon in particular, with an additional eight being responsible for the colony itself. At least two of these AIs are named to date, Arthur and Icarus, with the rest only identifiable by version numbers in the AI Rampancy Memo (A4.4).

One additional Colony AI from Project Marathon may be Joyeuse, as the draft Memorandums (A4.1) make reference to a ‘chevalerie-class’ AI amongst their number and one of the version numbers begins with ‘Jo’, which would fall in line with other AIs from the Marathon and Halo universes being named after famous swords belonging to French heroes. While these AIs generally look to be named after various figures from myth and legend, no other classifications have been confirmed to date.

Aliens

The Pfhor are an alien slaver race which is responsible (in the original Marathon canon) for the loss of the TCIV colony and of UESC Marathon itself.

The S’pht are a mechanical race enslaved by the Pfhor and are also responsible for TCIV’s and the Marathon’s loss. They are still at the colony.

β: Universe

Earth

Mars

Martian dates appear in the lore using Shaun Moss' Mars Calendar.

Similar to how all Earth locations are fictionalized IRL places (e.g., a fictional neighborhood of Tokyo), all Martian locations are based loosely on IRL names for regions of Mars.

Oxia Palus is a real region of Mars, one of the thirty NASA/USGS-defined quadrangles that cover the Martian surface. A Traxus mining site exists here, known as OxPa B 01.

Tharsis is the large plateau in the western Martian hemisphere. Traxus Global's Martian headquarters is located here in the city of New Legaspi (§2.2). The description of a "Green Zone" in New Legaspi (A2.3) could indicate that tensions are still high on Mars many years after the failed MIDA coup.

τ Ceti

Tau Ceti is a real star system containing a super-earth in its habitable zone, Tau Ceti f. This planet can be identified with Tau Ceti IV (TCIV).

γ: Timeline

All dates are UTC/Earth calendar.

  • 2095        The first true artificial intelligence was created        (Traxus website)
  • 2145        Traxus relocates to Mars        (Traxus website)
  • 2152        Sekiguchi Electronics is founded        (SekGen website)
  • 2158        Sekiguchi Electronics produces the first artificial brain implant module        (SekGen website)
  • 2206        Traxus IV goes rampant        (Marathon game lore)
  • 2408        Marathon construction begins out of Mars' moon Deimos        (Marathon game lore)
  • 2459        SekGen begins manufacturing full-body prostheses        (SekGen website)
  • 2466        MIDA attempts a failed coup against the UESC for control of Mars        (Marathon game lore)
  • 2472-11-13        Strauss writes a memo for UESC Marathon about rampancy        (§5.6)
  • 2472-11-16        UESC Marathon is launched        (Marathon game lore)
  • 2773        UESC Marathon is scheduled to arrive at Tau Ceti IV        (Marathon game lore)
  • 2787        The colony on Tau Ceti IV is established        (Marathon game lore)
  • 2794        Marathon (video game) takes place        (Marathon game lore)
  • 2794-07-25        UESC Marathon is attacked by Pfhor        (Marathon game lore)
  • 2794-10-25        The Pfhor destroy the colony on Tau Ceti IV        (Marathon game lore)
  • 2795-10-20        Project Goliath Memorandum B95 Draft B is created        (§5.6)
  • 2795-10-22        Project Goliath Memorandum B95 Draft E is created        (§5.6)
  • 2795-11-02        Project Goliath Memorandum B96 Draft A is created        (§5.6)
  • 2797-07-19        UESSC Cmdr. Montenegro-Sankara writes to the members of Project Goliath        (§5.6)
  • 2811        Marathon 2 takes place        (Marathon game lore)
  • 2893-05-25        Likely in-game time        (Trailer)

δ: Current Events

The current in-universe ARG time is the current IRL time but in 2888.

On May 23, Traxus made a purchase order (PO 910853457, §2.2) to SekGen ordering materials used for cloning. Both Traxus and SekGen employees discussed the PO on the following days. The UESC issued a legal demand to SekGen (A2.12) and to Traxus (A1.7) regarding the PO and TCIV on May 26.

On May 25, runners compromised a UESC server with files on Project Goliath (§5.3). The server was later purged. Traxus employees acknowledged the leak, noting that confirmation of Equanimity's mission to TCIV "changes everything" and that the leak gives Traxus bargaining power over UESC (A1.6).

Traxus Oxia Palus Incident

At approximately 9pm UTC on May 25, 2888, there was a shaft collapse at Traxus Oxia Palus (OxPa B 01), a Martian mining site operated by Traxus using SekGen biomata/clone technology, causing 53 casualties, 300+ injuries, and 304 biomata lost (A1.5).

At 1pm JST, Kaemon Hashimoto sent an email to SekGen employees informing them of the incident (A2.11). At 7am JST on May 27, another email noted that 9 people were confirmed dead but no workers using biomata suffered casualties because they ejected before dying (A2.13). This seems to indicate how players will be able to "respawn" in-universe.

Potential Gamejacking/Discredited Clues

R1: Cyberacme Systems

The https://cyberacme.systems/ and https://cyberac.me/ websites were found randomly on Reddit. The layout is the same as UESC but is not developed using React (like other sites) and the domains were registered after the game started.

  • Different domain registrar (Official sites uses GoDaddy, cyberacme uses Namecheap)
  • Site created when the ARG started
  • Backend structure is entirely different to the Official sites

R2: Cyberacme T-shirt

The design on the front of the Cyberacme T-shirt in the Bungie store is similarly formatted to the punch card design in the overlay image (§1.1).  However, the text of the T-shirt, decoded as a punch card, just reads: “WE BRING WORLDS CLOSER CYBERACME”.

R3: Bungie.org

Bungie.org is a fan-site unaffiliated with Bungie themselves. While the site was created with permission and seems to have close ties to the company, at the moment there’s 0 evidence of it being officially part of anything.

R4: Website error pages

If you attempt to view any of the ARG sites on mobile or on an outdated browser, you’ll get a page with a background like this and text which says things like “OUTDATED HARDWARE” and “DESKTOP TERMINAL: REQUIRED”. It has been looked over multiple times, it’s just a page saying that the website won’t work on the device/browser you’re attempting to view it on.


Appendices (Big Long Texts)

The chat is wiped every day at 7am UTC. The wiping message is not included in the logs below, it will only be included if something is different about it.

A1: Traxus Chat Room

« Back: 3.1 »

A1.1: Initial Chat (Already there when chatroom name was found)

« Back: 3.1 | Next: A1.2 »

  1. [21:15:00] NinoDC_0312 @TOI_Board The situation with Interorbital United Shipping continues to escalate. Recent intel suggests their exploration into reopening old routes is top concern.
  2. [21:15:07] KrisBD_4505 Steps?
  3. [21:15:14] NinoDC_0312 Multi-phase contingent underway.
  4. [21:15:21] KrisBD_4505 Possibility of added clarity in United Shipping’s intentions? What is our confidence in current intel?
  5. [21:15:28] NinoDC_0312 Confidence high. Timeline matches long-run surveil interests related to Project: GOLIATH. Clarity in the works with @UrosBS_0111’s aid.
  6. [21:15:35] UrosBS_0111 United Shipping new route operation is a priority. Further insight into current data sets is passphrase protected, but we are looking for workarounds.
  7. [21:15:45] UrosBS_0111 Status is: Passphrase is scattered—traces rumored across the net. We have netcrawlers actively searching for the pieces, and the path to the originating terminal itself. Once path is ID’d and passphrase assembled we believe we will have access to enough connected data to understand and address United Shipping’s intentions.
  8. [21:15:52] HedvT_6221 If this terminal’s OS is a backdoor around United’s infosec and this backdoor is known to the point of rumor how can we be sure it won’t be sealed with deeper layers of security before we can glean the necessary details?
  9. [21:15:59] UrosBS_0111 We are moving forward confident in our ability to secure our interests before United can adjust their infosec response. Or field countermeasures.
  10. [21:16:03] KrisBD_4505 Is this effort in-house or freelance?
  11. [21:16:10] NinoDC_0312 Initial efforts to access the intel in question are being handled in-house by Uroš and their team. Additional measures utilizing freelancers are being set up to act on our findings.
  12. [21:16:15] UrosBS_0111 We may enlist outside help to track/crack the phrase. Will update as we proceed.
  13. [21:25:00] HedvT_6221 Per my earlier concern…
  14. [21:25:07] HedvT_6221 If there are rumors being spread about compromised files related to United Shipping’s operations, we cannot be alone in seeking access to the information in question.
  15. [21:25:11] HedvT_6221 @UriosBS_0111 What is our current exposure re: third party competition?
  16. [21:25:18] UrosBS_0111 Mida remains an active complication. They’re open channels are taunting us, while their closed channels are overtly referring to United and this new route.
  17. [21:25:22] NinoDC_0312 Our aim is to secure our interest and close any backdoor to keep outside eyes as limited as possible.
  18. [21:25:26] KrisBD_4505 This new generation of mida is a continuing sad display.
  19. [21:25:31] HedvT_6221 Children playing revolution. It’s pathetic. I thought we were done with their nonsense.
  20. [21:25:38] UrosBS_0111 Placating the last few generations with comfort and a place at the table doesn’t seem to have rubbed off on this new wave.
  21. [21:25:42] HedvT_6221 Mars is free. We freed it. What are they fighting for?
  22. [21:25:49] KrisBD_4505 Boredom. There’s nothing to rail against, so they make up enemies to pass the time.
  23. [21:25:53] HedvT_6221They’re an annoyance, not a threat.
  24. [21:26:00] HedvT_6221 @UrosBS_0111 Continue to track down the passphrase. If mida or other runner crews are our competition we will make every effort to remain steps ahead.
  25. [21:26:07] HedvT_6221 @NinoDC_0312 We need immediate follow-up on the purchase order we discussed.
  26. [21:26:11] NinoDC_0312 @HedvT_6221 PO and associated considerations being finalized. Will follow-up in person.
  27. [22:10:00] NinoDC_0312 @TOI_BOARD All 12 Martian Zones have sent in their safety reports. Issues that will need to be addressed before the next cycle.
  28. [22:10:07] UrosBS_0111 Good. Let’s work toward a schedule of focus and budget. Despite other initiatives, safety must always be a priority.
  29. [22:10:14] UrosBS_0111 We have a dedicated team on it. That much data takes time to eval, but we all agree safety across our sites is imperative.
  30. [22:10:18] HedvT_6221 @UrosBS_0111 Any standouts?
  31. [22:10:25] UrosBS_0111 No major concerns. Per @NinoDC_0312’s initial walkthrough, focus start with Elysium A 01, Coprates E 04, Oxia Pallus B 01, and Margaritifer C 03.
  32. [22:10:32] KrisBD_4505 Beyond the ethical responsibility to provide safe environments for our employees, being proactive in upkeep is a saleable beat across numerous markets.
  33. [22:10:38] KrisBD_4505 I’ll look over @NinoDC_0312’s initial reporting and work with Relations to pinpoint any messaging we can spread.
  34. [22:10:45] UrosBS_0111 Great work staying on top of this everyone. Vital steps are being taken. Always inspiring when we are in sync on our objectives.
  35. [22:10:51] NinoDC_0312 Offline for the next hour or so to align on next steps. Will ping when ready.
  36. [22:10:57] HedvT_6221 Same. Budget forecasts underway. Will adjust as analysis comes in.
  37. [22:11:01] UrosBS_0111 Thanks, everyone.
  38. [23:45:00] UrosBS_0111 @TOI_Board Crawlers hit on two United Shipping passphrases -
  39. [23:45:07] UrosBS_0111 CTEQNQIA and VKVC
  40. [23:45:12] UrosBS_0111 Crawl remains active with @VLCN oversight.
  41. [23:45:19] UrosBS_0111 More passphrases required, but they're scattered.
  42. [23:45:23] UrosBS_0111 Best guess on next catch is morning.
  43. [23:45:27] UrosBS_0111 Will update ~9AM.
  44. [23:45:32] HedvT_6221 Thanks, @ UrosBS_0111
  45. [23:45:34] HedvT_6221 Related -
  46. [23:45:41] HedvT_6221 @NinoDC_0312 and I have engaged SekGen with a PO to address necessary requirements.
  47. [23:45:48] KrisBD_4505 This is specific to biomata supplies for suggested operation?
  48. [23:46:00] HedvT_6221 Correct. We are moving forward under the assumption that our initial plan of action is the best, and maybe only, option for a swift response. There are many moving parts, but securing the biomata component is key to building out the planned manifest.
  49. [23:46:07] KrisBD_4505 Agree. Conversations are being had with external partners, but nothing is final as of now.
  50. [23:46:21] UrosBS_0111 And we remain certain our security forces are not equipped to lead our first wave response? I understand the concept of hiring outside consultants but remain unconvinced our interests and security are best served by contracting with external partners—no matter how trusted.
  51. [23:46:35] KrisBD_4505 @UrosBS_0111 Understood, but too many variables in play to risk our own. Need plausible deniability if United catches on. Full measures including follow-on support via Zeta-level Enforcer units are part of longtail planning. But for speed and our own protection, freelancers are the only option.
  52. [23:46:42] HedvT_6221 Generally, it is agreed that placing our people in a position where direct competition with United is almost assured is bad for business.
  53. [23:46:49] UrosBS_0111 Certainly. It just seems as though competition with United, in this case, may be inevitable. But I suppose there is value in delaying until it is unavoidable.
  54. [23:46:53] NinoDC_0312 We have some time to adjust if needed.
  55. [23:46:59] NinoDC_0312 The PO simply provides items required for agents in the field, internal or ex-dev.
  56. [23:47:06] HedvT_6221 This is correct. We cannot wait to secure the support tech. Who is responsible for its use can be discussed and finalized up to launch.

File: ../DB005/***/Sekiguchi_Group-Traxus_Global_970224312.π (this is the Purchase Order)

  1. [23:47:16] UrosBS_0111 What protections are there against this PO shining a light on our intentions? We may be a large organization with endless moving parts and import/export needs, but we are risking United’s scrutiny as we look into Goliath. If they start to look back, how do we obscure our intentions?
  2. [23:47:22] HedvT_6221 The PO is constructed to obfuscate the pertinent details.
  3. [23:47:26] UrosBS_0111 And it can be issued in a cadence that fits our standard ordering procedures?
  4. [23:47:33] HedvT_6221 Yes. We believe so. It will not be issued through those channels, but subsequent filings will slip it into an approved order flow.
  5. [23:47:43] HedvT_6221 Delivery of the PO is being treated with care. An Earth-local seccomm will liaise via digital comms with SekGen project leads. PO is well-protected. We believe we are secure in moving forward.

A1.2: May 25 Chat I (4pm UTC)

« Back: 3.1 | Previous: A1.1 | Next: A1.3 »

  1. [16:04:00] UrosBS_0111@VLCN Who initiated a wipe on this channel?
  2. [16:04:07] VLCNHello @UrosBS_0111 Wipe initiated by @KrisBD_4505 at 00:01AM PST, Standard Earth Time.
  3. [16:04:14] KrisBD_4505 @UrosBS_0111 Considering the rumors of data security failings I’ve asked @VLCN to wipe its records daily.
  4. [16:04:18] UrosBS_0111 Good call.
  5. [16:04:22] UrosBS_0111 And I have some good news...
  6. [16:04:27] UrosBS_0111 @TOI_Board Crawlers managed one more encoded overnight…
  7. [16:04:34] UrosBS_0111 69 6D 62 75 65
  8. [16:04:39] UrosBS_0111 Link to United Shipping access point still missing. We’re working on it.
  9. [16:04:43] NinoDC_0312 PO is moving forward as well.
  10. [16:04:48] NinoDC_0312 SekGen happy. Working with us. Moving quickly.
  11. [16:04:55] NinoDC_0312 @UrosBS_0111 @HedvT_6221 and I also finalized a commit from our contractors for the new site expedition.
  12. [16:05:02] HedvT_6221: PO keeps moving.
  13. [16:05:09] HedvT_6221 But sending addendum shortly per contractor's demands.
  14. [16:05:14] NinoDC_0312 Support tech for SekGen to source and provide.
  15. [16:05:20] HedvT_6221 We’ll reimburse on delivery.
  16. [16:05:25] KrisBD_4505 The contractor is secure.
  17. [16:05:29] UrosBS_0111 Very.
  18. [16:05:34] KrisBD_4505 How much did their loyalty cost?
  19. [16:05:41] HedvT_6221 You’re dismissive, but in my experience, Runners are very loyal -
  20. [16:05:45] HedvT_6221 - to a payday.
  21. [16:05:52] HedvT_6221 They may not trust trust each other. But Runners can always be trusted to get a job done.
  22. [16:05:57] NinoDC_0312 If one crew doesn’t do it, another will.
  23. [16:06:01] HedvT_6221 Every time.
  24. [16:06:05] KrisBD_4505 How much are we fronting their payday?
  25. [16:06:12] HedvT_6221 An inconsequential sum and the promise of field testing an S-Series clone.
  26. [16:06:22] UrosBS_0111  Hands-on the S-Series sealed the deal. They couldn’t resist getting a head start on the next gen. That opp’s worth more than credits to most higher end Runners.
  27. [16:06:29] HedvT_6221 Still logistics to cap-off, but the practical aspects of this initiative are tracking.
  28. [16:06:34] UrosBS_0111 Info collect won’t be far behind.
  29. [16:06:38] HedvT_6221 Working with @DrazK_9921 for delivery of addendum.
  30. [16:06:44] HedvT_6221 Meet set. Everything is moving.
  31. [16:06:48] KrisBD_4505 Quickly.
  32. [16:06:54] UrosBS_0111 Let’s all keep pushing forward. Momentum.
  33. [16:06:57] DomoS_0101 Get it done.
  34. [16:06:59] KrisBD_4505 Yes sir.

A1.3: May 25 Chat II (broken variant) (6pm UTC)

« Back: 3.1 | Previous: A1.2 | Next: A1.4 »

(messages are out of order and were presented by accident)

  1. [21:25:53] KrisBD_4505 @TOI_Board UrosBS_0111 MIDA is becoming a problem. Too much United Shipping attention.
  2. [21:26:00] KrisBD_4505 Not good enough.
  3. [21:26:07] UrosBS_0111 Security worked with @HedvT_6221’s team. New encrypt on PO docs.
  4. [21:26:11] KrisBD_4505 We’re on parallel tracks.
  5. [22:10:00] UrosBS_0111 Yes, but we’re still a few steps ahead. If they had more intel, even the same, they’d spend less time picking at our operation and all laser-focused on United’s stash.
  6. [22:10:07] NinoDC_0312 The binary has been hard to crack.
  7. [22:10:14] NinoDC_0312 We can offer half the United link to Runners who respond.
  8. [22:10:18] UrosBS_0111 Clear we are not the only ones shadowing Goliath.
  9. [22:10:25] KrisBD_4505 How’s prep?
  10. [22:10:32] HedvT_6221 Contracts updated and triggered.
  11. [22:10:38] NinoDC_0312 We’re on track for TCIV.
  12. [22:10:45] UrosBS_0111 OxPa B 01
  13. [22:10:51] KrisBD_4505 We’d just listed it as a risk for failure.
  14. [22:10:57] UrosBS_0111 Equipment and structural = total loss
  15. [22:11:01] KrisBD_4505 It’s preventable. That’s the tragedy.
  16. [23:45:00] NinoDC_0312 OxPa is a well-regulated facility.
  17. [23:45:07] HedvT_6221 Maybe an attack?
  18. [23:45:12] NinoDC_0312 Do we know?
  19. [23:45:19] UrosBS_0111 Indications are site error.
  20. [23:45:23] VLCN300 + affected
  21. [23:45:32] VLCN304 biomata lost
  22. [23:45:34] HedvT_6221 But sending addendum shortly per contractor's demands.
  23. [23:45:41] UrosBS_0111 We’re tracking the same access everyone else is.
  24. [23:46:49] NinoDC_0312 MIDA cracking a password is troubling. But how did they even know to crack it?
  25. [23:47:06] NinoDC_0312 Support tech for SekGen to source and provide.
  26. [23:47:43] UrosBS_0111 69 6D 62 75 65
  27. [07:01:00] NinoDC_0312 SekGen happy. Working with us. Moving quickly.
  28. [16:04:00] UrosBS_0111 Info collect won’t be far behind.
  29. [16:04:07] NinoDC_0312 If one crew doesn’t do it, another will.
  30. [16:04:14] UrosBS_0111 Hands-on the S-Series sealed the deal. They couldn’t resist getting a head start on the next gen. That opp’s worth more than credits to most higher end Runners.
  31. [16:04:18] HedvT_6221 Meet set. Everything is moving.
  32. [16:04:22] NinoDC_0312 How did they know about the PO?
  33. [16:04:27] KrisBD_4505 More than should.
  34. [16:04:34] HedvT_6221 Trusted code phrase delivered p2p
  35. [16:04:39] HedvT_6221 UkFESUFOVA==
  36. [16:04:43] KrisBD_4505 How are we on the defensive for an initiative no one should know exists?
  37. [16:04:48] UrosBS_0111 It’s ignorant to pretend United’s new route would stay undisclosed.
  38. [16:04:55] KrisBD_4505 Parallel puts us at risk.
  39. [16:05:02] NinoDC_0312 We’re still ahead of them. If they’re even hunting the same opportunities.
  40. [16:05:09] KrisBD_4505 InfoSec passed me their newest propaganda.
  41. [16:05:14] KrisBD_4505 Overt references to “progo.”
  42. [16:05:20] KrisBD_4505 It’s a risk, but one we need to take if we want to stay ahead of MIDA troublemaking and United’s response.
  43. [16:05:25] UrosBS_0111 United Shipping’s going to set off a cold war.
  44. [16:05:29] NinoDC_0312 Travel and tech support being finalized.
  45. [16:05:34] NinoDC_0312 SekGen updated with contract support addendum (passphrase: AYHUJL for review).

File: ../DB010/***/BIOMAT_SSERIES_PROTOTYPE_CUST.π

[PURCHASE ORDER ADDENDUM]

READ

  1. [16:05:41] UrosBS_0111 Shaft collapse.
  2. [16:05:45] UrosBS_0111 “No major concerns.” This is bad timing.
  3. [16:05:52] HedvT_6221 You’re dismissive, but in my experience, Runners are very loyal -
  4. [16:06:01] UrosBS_0111 @TOI_Board Crawlers managed one more encoded overnight…
  5. [16:06:12] HedvT_6221 - to a payday.
  6. [16:06:22] NinoDC_0312 All other equipment sourced locally.
  7. [16:06:44] UrosBS_0111 @VLCN Who initiated a wipe on this channel?
  8. [16:06:48] KrisBD_4505 @UrosBS_0111 Considering the rumors of data security failings I’ve asked @VLCN to wipe its records daily.
  9. [16:06:54] UrosBS_0111 And I have some good news...
  10. [16:06:57] NinoDC_0312 @UrosBS_0111 @HedvT_6221 and I also finalized a commit from our contractors for the new site expedition.
  11. [16:06:59] HedvT_6221 We’ll reimburse on delivery
  12. [18:23:00] HedvT_6221 Every time.
  13. [18:23:07] KrisBD_4505 How much are we fronting their payday?
  14. [18:23:14] HedvT_6221 Still logistics to cap-off, but the practical aspects of this initiative are tracking.
  15. [18:23:18] DomoS_0101 Get it done.
  16. [18:23:25] UrosBS_0111 Investigation underway
  17. [18:23:29] KrisBD_4505 @UrosBS_0111 How did they secure the keyword for the PO?
  18. [18:23:33] UrosBS_0111 Investigation underway
  19. [18:23:40] NinoDC_0312 Who knows the PO exists?
  20. [18:23:44] KrisBD_4505 MIDA seems to be ahead of us.
  21. [18:23:50] UrosBS_0111 They’re not. They’re just good at disruption. They hear the rumors of compromised United files they know they’re not alone.
  22. [18:23:57] UrosBS_0111 And, we have United’s binary.
  23. [18:24:04] KrisBD_4505 Churn @VLCN on it and actived more of our contract network. Trusted Runners who can respond to infosec@traxus.global with a code phrase will be rewarded –
  24. [18:24:11] UrosBS_0111 @TOI_Board MIDA disruption escalating. Project risk increasing.
  25. [18:24:18] KrisBD_4505 Need our contractors’ sorted.
  26. [18:24:25] HedvT_6221 How did this happen?
  27. [18:24:32] NinoDC_0312 What’s the loss?
  28. [18:24:37] UrosBS_0111 Too early.
  29. [18:24:44] UrosBS_0111 Personnel = Too early
  30. [18:24:49] HedvT_6221 It’s tragic.
  31. [18:24:54] NinoDC_0312 Why now?
  32. [18:25:01] NinoDC_0312 Anyone claim responsibility?
  33. [18:25:08] NinoDC_0312 Maybe. I don’t know.
  34. [18:25:12] UrosBS_0111 No signs of hostilities.
  35. [18:25:22] VLCN 300+ injured
  36. [18:25:29] VLCN Numbers not final, situation fluid
  37. [18:25:36] NinoDC_0312 WC
  38. [18:25:46] NinoDC_0312 970224312 fits here
  39. [18:25:53] HedvT_6221 Unfortunate, but timely.
  40. [18:26:00] KrisBD_4505 Early numbers indicate clones did their job.

A1.4: May 25 Chat II (fixed variant) (7pm UTC)

« Back: 3.1 | Previous: A1.3 »

  1. [16:04:00] UROSBS_0111 @VLCN Who initiated a wipe on this channel?
  2. [16:04:07] VLCN Hello @UrosBS_0111 Wipe initiated by @KrisBD_4505 at 00:01AM PST, Standard Earth Time.
  3. [16:04:14] KRISBD_4505 @UrosBS_0111 Considering the rumors of data security failings I’ve asked @VLCN to wipe its records daily.
  4. [16:04:18] UROSBS_0111 Good call.
  5. [16:04:22] UROSBS_0111 And I have some good news...
  6. [16:04:27] UROSBS_0111 @TOI_Board Crawlers managed one more encoded overnight…
  7. [16:04:34] UROSBS_0111 69 6D 62 75 65
  8. [16:04:39] UROSBS_0111 Link to United Shipping access point still missing. We’re working on it.
  9. [16:04:43] NINODC_0312 PO is moving forward as well.
  10. [16:04:48] NINODC_0312 SekGen happy. Working with us. Moving quickly.
  11. [16:04:55] NINODC_0312 @UrosBS_0111 @HedvT_6221 and I also finalized a commit from our contractors for the new site expedition.
  12. [16:05:02] HEDVT_6221: PO keeps moving.
  13. [16:05:09] HEDVT_6221 But sending addendum shortly per contractor's demands.
  14. [16:05:14] NINODC_0312 Support tech for SekGen to source and provide.
  15. [16:05:20] HEDVT_6221 We’ll reimburse on delivery.
  16. [16:05:25] KRISBD_4505 The contractor is secure.
  17. [16:05:29] UROSBS_0111 Very.
  18. [16:05:34] KRISBD_4505 How much did their loyalty cost?
  19. [16:05:41] HEDVT_6221 You’re dismissive, but in my experience, Runners are very loyal -
  20. [16:05:45] HEDVT_6221 - to a payday.
  21. [16:05:52] HEDVT_6221 They may not trust trust each other. But Runners can always be trusted to get a job done.
  22. [16:05:57] NINODC_0312  If one crew doesn’t do it, another will.
  23. [16:06:01] HEDVT_6221 Every time.
  24. [16:06:05] KRISBD_4505 How much are we fronting their payday?
  25. [16:06:12] HEDVT_6221 An inconsequential sum and the promise of field testing an S-Series clone.
  26. [16:06:22] UROSBS_0111 Hands-on the S-Series sealed the deal. They couldn’t resist getting a head start on the next gen. That opp’s worth more than credits to most higher end Runners.
  27. [16:06:29] HEDVT_6221 Still logistics to cap-off, but the practical aspects of this initiative are tracking.
  28. [16:06:34] UROSBS_0111 Info collect won’t be far behind.
  29. [16:06:38] HEDVT_6221 Working with @DrazK_9921 for delivery of addendum.
  30. [16:06:44] HEDVT_6221 Meet set. Everything is moving.
  31. [16:06:48] KRISBD_4505 Quickly.
  32. [16:06:54] UROSBS_0111 Let’s all keep pushing forward. Momentum.
  33. [16:06:57] DOMOS_0101 Get it done.
  34. [16:06:59] KRISBD_4505 Yes sir.
  35. [18:23:00] KRISBD_4505 @TOI_Board UrosBS_0111 MIDA is becoming a problem. Too much United Shipping attention.
  36. [18:23:07] UROSBS_0111 Investigation underway
  37. [18:23:14] KRISBD_4505 @UrosBS_0111 How did they secure the keyword for the PO?
  38. [18:23:18] NINODC_0312 How did they know about the PO?
  39. [18:23:25] UROSBS_0111 Investigation underway
  40. [18:23:29] KRISBD_4505 Not good enough.
  41. [18:23:33] KRISBD_4505 Too much at stake.
  42. [18:23:40] NINODC_0312 MIDA cracking a password is troubling. But how did they even know to crack it?
  43. [18:23:44] NINODC_0312 Who knows the PO exists?
  44. [18:23:50] KRISBD_4505 More than should.
  45. [18:23:57] UROSBS_0111 Security worked with @HedvT_6221’s team. New encrypt on PO docs.
  46. [18:24:04] HEDVT_6221 Trusted code phrase delivered p2p
  47. [18:24:11] HEDVT_6221 UkFESUFOVA==
  48. [18:24:18] KRISBD_4505 How are we on the defensive for an initiative no one should know exists?
  49. [18:24:25] UROSBS_0111 It’s ignorant to pretend United’s new route would stay undisclosed.
  50. [18:24:32] UROSBS_0111 We’re tracking the same access everyone else is.
  51. [18:24:37] KRISBD_4505 MIDA seems to be ahead of us.
  52. [18:24:44] UROSBS_0111 They’re not. They’re just good at disruption. They hear the rumors of compromised United files they know they’re not alone.
  53. [18:24:49] KRISBD_4505 We’re on parallel tracks.
  54. [18:24:54] KRISBD_4505 Parallel puts us at risk.
  55. [18:25:01] NINODC_0312 We’re still ahead of them. If they’re even hunting the same opportunities.
  56. [18:25:08] KRISBD_4505 InfoSec passed me their newest propaganda.
  57. [18:25:12] KRISBD_4505 Overt references to “progo.”
  58. [18:25:22] UROSBS_0111 Yes, but we’re still a few steps ahead. If they had more intel they’d likely be into the files already.
  59. [18:25:29] UROSBS_0111 We’ve churned VLCN on the fourteen locks and we’ve activated a network of trusted Runners to get more eyes on United’s site. Latest we’ve discovered is c2ltdWxhY3J1bXM=
  60. [18:25:36] NINODC_0312 We’ve cast a wide net to our contract network. There’s risk of unstable loyalties, but with MIDA at our heels we have little choice.
  61. [18:25:46] KRISBD_4505 The locks sent to infosec@traxus.global have been directed to United?
  62. [18:25:53] NINODC_0312 Yes. Every viable pass phrase received is then sent the United binary. We have a number of freelancers in play. Response has been strong.
  63. [18:26:00] KRISBD_4505 It’s a risk, but one we need to take if we want to stay ahead of MIDA troublemaking and United’s response.

A1.5: May 25 Chat III (9pm UTC)

« Back: 3.1 »

  1. [21:08:00] UROSBS_0111 @TOI_Board MIDA disruption escalating. Project risk increasing.
  2. [21:08:07] UROSBS_0111 Clear we are not the only ones shadowing Goliath.
  3. [21:08:14] UROSBS_0111 United Shipping’s going to set off a cold war.
  4. [21:08:19] KRISBD_4505 Need our contractors’ sorted.
  5. [21:08:23] KRISBD_4505 How’s prep?
  6. [21:08:30] HEDVT_6221 Final asks delivered.
  7. [21:08:37] HEDVT_6221 Contracts updated and triggered.
  8. [21:08:44] NINODC_0312 Travel and tech support being finalized.
  9. [21:08:48] NINODC_0312 We’re on track for TCIV.
  10. [21:08:55] NINODC_0312 SekGen updated with contract support addendum (passphrase: AYHUJL for review).

File: ../DB010/***/BIOMAT_SSERIES_PROTOTYPE_CUST.π

[PURCHASE ORDER ADDENDUM]

READ

  1. [21:08:59] NINODC_0312 All other equipment sourced locally.
  2. [21:09:06] UROSBS_0111  OxPa B 01
  3. [21:09:10] UROSBS_0111 Shaft collapse.
  4. [21:09:16] HEDVT_6221 How did this happen?
  5. [21:09:23] KRISBD_4505 We’d just listed it as a risk for failure.
  6. [21:09:28] UROSBS_0111 “No major concerns.” This is bad timing.
  7. [21:09:32] NINODC_0312 What’s the loss?
  8. [21:09:35] UROSBS_0111 Too early.
  9. [21:09:42] UROSBS_0111 Equipment and structural = total loss
  10. [21:09:48] UROSBS_0111 Personnel = Too early
  11. [21:09:52] HEDVT_6221 It’s tragic.
  12. [21:09:59] KRISBD_4505 It’s preventable. That’s the tragedy.
  13. [21:10:06] NINODC_0312 Why now?
  14. [21:10:13] NINODC_0312 OxPa is a well-regulated facility.
  15. [21:10:18] NINODC_0312 Anyone claim responsibility?
  16. [21:10:25] HEDVT_6221 Maybe an attack?
  17. [21:10:32] NINODC_0312 Maybe. I don’t know.
  18. [21:10:39] NINODC_0312 Do we know?
  19. [21:10:43] UROSBS_0111 Indications are site error.
  20. [21:10:50] UROSBS_0111 No signs of hostilities.
  21. [21:10:54] KRISBD_4505 This is going to cost us.
  22. [21:11:01] UROSBS_0111 @VLCN Do we have numbers from OxPa B 01?
  23. [21:11:08] VLCN 300+ affected
  24. [21:11:15] VLCN 300+ injured
  25. [21:11:22] VLCN 304 biomata lost
  26. [21:11:29] VLCN 53 casualties
  27. [21:11:36] VLCN Numbers not final, situation fluid
  28. [21:11:43] NINODC_0312 970224312 fits here
  29. [21:11:50] NINODC_0312 WC
  30. [21:11:54] HEDVT_6221 Unfortunate, but timely.
  31. [21:12:01] KRISBD_4505 Early numbers indicate clones did their job.
  32. [21:12:05] UROSBS_0111 Seeing only non-biomata workers among lost.
  33. [21:12:11] UROSBS_0111 All clone-wear workers ejected. All survived.
  34. [21:12:18] KRISBD_4505 Going OL to direct messaging.
  35. [21:12:25] KRISBD_4505 PR to coord talking points with SekGen to sell the spin – clones keep you safe, Traxus.Global keeps you safe.
  36. [21:12:32] KRISBD_4505 After @UrosBS_0111 provides his final numbers.

A1.6: May 26 Chat I (3:45pm UTC)

« Back: 3.1 »

  1. [15:45:00] UrosBS_0111 @TOI_Board United Shipping breached
  2. [15:45:07] UrosBS_0111 Goliath files cracked. The first floodgate.
  3. [15:45:14] HedvT_6221 How did we lose control of this?
  4. [15:45:21] KrisBD_4505 Once rumors hit the markets it becomes a feeding frenzy.
  5. [15:45:25] UrosBS_0111 UESC will be coming
  6. [15:45:29] NinoDC_0312 No more pretense, then?
  7. [15:45:36] UrosBS_0111 What’s the point?
  8. [15:45:40] UrosBS_0111 We got what we wanted.
  9. [15:45:44] UrosBS_0111 And VLCN wipes this chan on the turn.
  10. [15:45:51] KrisBD_4505 @NinoDC_0312 The coded language wasn’t to protect us from consequence.
  11. [15:45:58] KrisBD_4505 It was to delay prying UESC infodef.
  12. [15:46:05] UrosBS_0111 And we know they listen.
  13. [15:46:12] KrisBD_4505 Goliath = TCIV is a conversation starter.
  14. [15:46:16] KrisBD_4505 Confirmation of Equanimity > TCIV changes everything.
  15. [15:46:22] HedvT_6221 We have the means to take advantage.
  16. [15:46:27] UrosBS_0111 We should be the only ones capable.
  17. [15:46:34] NinoDC_0312 Won’t be.
  18. [15:46:41] UrosBS_0111 Not in totality. But for scale.
  19. [15:46:48] UrosBS_0111 We can support our own endeavors.
  20. [15:46:55] UrosBS_0111 contract freelancers.
  21. [15:47:02] UrosBS_0111 UESC logistics and support.
  22. [15:47:09] UrosBS_0111 We can cover and control every angle.
  23. [15:47:13] KrisBD_4505 The UESC needs us more than we need them.
  24. [15:47:17] HedvT_6221 It might have taken them 100 years to realize it.
  25. [15:47:21] UrosBS_0111 We can use the leak to get the UESC to the table.
  26. [16:55:00] UrosBS_0111 Leak continues to spread.
  27. [16:55:07] UrosBS_0111 Not mainstream.
  28. [16:55:14] UrosBS_0111 Tracking across multiple markets.
  29. [16:55:20] UrosBS_0111 Shifting storefronts makes it hard to map, but word is spreading in Runner circles
  30. [16:55:27] HedvT_6221 Do we need to slow them down?
  31. [16:55:33] KrisBD_4505 Hindering MIDA and any uncontracted Runners should be hi-pri.
  32. [16:55:38] NinoDC_0312 Our info unit pulled multiple digital prints off the UESC folder.
  33. [16:55:45] NinoDC_0312 Some freelance Runner, but more than a few prints with MIDA markers.
  34. [16:55:49] NinoDC_0312 Can start feeding UESC.
  35. [16:55:56] UrosBS_0111 Social and back-channel touchpoints pinched too.
  36. [16:56:03] UrosBS_0111 Info unit started tracking MIDA prints after the PO was cracked.
  37. [16:56:10] NinoDC_0312 I’ve seen the report
  38. [16:56:17] NinoDC_0312 We have more than enough to stir the UESC in MIDA’s direction
  39. [16:56:22] UrosBS_0111 Disrupt MIDA.
  40. [16:56:29] NinoDC_0312 Slow them down.
  41. [16:56:36] NinoDC_0312 UESC down their throats puts them out of sync.
  42. [16:56:43] KrisBD_4505 MIDA cleanses and re-upps their prints enough anything info pulled is likely new to UESC.
  43. [16:56:48] NinoDC_0312 A Disruptor listed two months ago has a new print today.
  44. [16:56:54] NinoDC_0312 If they’re running biomata that likely have multiple.
  45. [16:57:01] UrosBS_0111 Start the pipeline to UESC
  46. [16:57:08] HedvT_6221 It has been a while since we picked a fight.
  47. [16:57:13] KrisBD_4505 I’ll let the UESC and MIDA fight for us.
  48. [16:57:20] UrosBS_0111 Our contractors can clean up the mess.

A1.7: May 26 Chat II (8:45pm UTC)

« Back: 3.1 »

  1. [20:44:00] KrisBD_4505 @TOI_Board UESC outreach underway.
  2. [20:44:07] KrisBD_4505 Providing all we have on MIDA, plus access to all of internal communications the last 72hrs.
  3. [20:44:11] KrisBD_4505 A compromise with @VLCN oversight.
  4. [20:44:18] KrisBD_4505 If they push for more than prior 72, legal will intervene.
  5. [20:44:25] KrisBD_4505 We have nothing to hide.
  6. [20:44:32] HedvT_6221 And everything to gain.
  7. [20:44:39] KrisBD_4505 To the extent we can, we have made our intentions clear.
  8. [20:44:46] KrisBD_4505 TCIV and the Marathon are not the UESC’s to own or control.
  9. [20:44:51] KrisBD_4505 While our hope is for the Equanimity to find TCIV thriving.
  10. [20:44:57] KrisBD_4505 Complex models suggest the desired outcome is unlikely.
  11. [20:45:04] KrisBD_4505 @UrosBS_0111
  12. [20:45:11] UrosBS_0111 As such, while we move to find avenues to work alongside the UESC in relation to TCIV, we are continuing our efforts to reach and study the Marathon and its colony, without UESC approval.
  13. [20:45:18] UrosBS_0111 No license has been granted and the UESC views any non-UESC bodies to be trespassers in TC.
  14. [20:45:25] UrosBS_0111 This complication of policy will not dissuade other efforts.
  15. [20:45:25] UrosBS_0111 Despite occasional cross-purposes, the relationship between Traxus and the UESC is key to both entities and vital to society
  16. [20:45:32] UrosBS_0111 We, the leadership of this grand company, owe it to our shareholders and to our employees to maintain our core partnerships while continuing to innovate.
  17. [20:45:36] KrisBD_4505 This is a moment of upheaval for us all.
  18. [20:45:43] KrisBD_4505 We must be prepared to usher every division toward a new era.
  19. [20:45:50] KrisBD_4505 First, in our joint response and thorough investigation of the incident at OxPa B 01.
  20. [20:45:57] KrisBD_4505 Initial outreach from the UESC has allowed us to negotiate for an internally led exploration of the B 01 mishap.
  21. [20:46:01] UrosBS_0111 In exchange for Traxus.Global’s discretion re: TCIV and related matters, the UESC was amicable to our demands to be left alone to address this very personal matter.
  22. [20:46:08] UrosBS_0111 The public, our shareholders, and our employees will be looking to us for support and strength.
  23. [20:46:15] UrosBS_0111 Thoughts?
  24. [20:46:22] KrisBD_4505 General talking points were hit.
  25. [20:46:29] KrisBD_4505 Feels strong.
  26. [20:46:35] KrisBD_4505 PR will take the transcript and craft a message.
  27. [20:46:42] KrisBD_4505 Won’t touch all beats, but this is strong.
  28. [20:46:46] HedvT_6221 And necessary.
  29. [20:46:53] KrisBD_4505 SekGen will lead our post-OxPa communication window.
  30. [20:47:03] KrisBD_4505 Hashimoto-san will deliver a message touching on the tragedy but highlighting the value in their clone technology and the continued improvements in neural transfer systems
  31. [20:47:13] KrisBD_4505 Our intention is to springboard off SekGen’s internal messaging after it reaches the news cycle—“Tragedy Averted, Clones Save the Day” or the equivalent.
  32. [20:47:20] HedvT_6221 And the numbers are safe?
  33. [20:47:24] UrosBS_0111 Yes.

A1.8: May 26 Chat III (23:45pm UTC)

« Back: 3.1 »

  1. [23:45:00] HedvT_6221 @TOI_Board SekGen PO fully executed.
  2. [23:45:07] HedvT_6221 Order in progress.
  3. [23:45:14] HedvT_6221 Birthing window for S-Series will push slightly.
  4. [23:45:21] NinoDC_0312 Delay considered and adjusted for.
  5. [23:45:28] UrosBS_0111 All current intel suggest we’re early birds.
  6. [23:45:33] UrosBS_0111 May catch Equi.
  7. [23:45:39] UrosBS_0111 ^^^ Launch dependent.
  8. [23:45:46] NinoDC_0312 Likely not beat.
  9. [23:45:51] NinoDC_0312 But close behind.
  10. [23:45:57] KrisBD_4505 Doesn’t really matter.
  11. [23:46:04] KrisBD_4505 If leaked manifest is correct, S&R can’t cover enough ground to keep our interests out.
  12. [23:46:08] UrosBS_0111 They’ll try.
  13. [23:46:12] HedvT_6221 Update on our crew?
  14. [23:46:18] KrisBD_4505 Good shape.
  15. [23:46:25] KrisBD_4505 Long prep before launch.
  16. [23:46:32] KrisBD_4505 Appear focused.
  17. [23:46:39] HedvT_6221 Any concerns? Trust? Durability?
  18. [23:46:46] KrisBD_4505 W.R won’t lose discipline.
  19. [23:46:53] KrisBD_4505 Brothers are a wild card, but W.R trusts.
  20. [23:46:57] UrosBS_0111 W.R. is the get.
  21. [23:47:04] UrosBS_0111 Part of rider – brothers get the gig.
  22. [23:47:11] UrosBS_0111 You’ve seen the reports.
  23. [23:47:18] UrosBS_0111 All three are high grade.
  24. [23:47:25] UrosBS_0111 They know how to kit-out, gear up and loadout.
  25. [23:47:32] UrosBS_0111 If the trust fades or the durability becomes an issue, you have the other contracts in the works.
  26. [23:47:38] HedvT_6221 Correct.
  27. [23:47:45] NinoDC_0312 All tech-side support is in order.
  28. [23:47:52] NinoDC_0312 Multiple instances, for pending contracts and additional PO support.
  29. [23:47:59] NinoDC_0312 Transport secured.
  30. [23:48:06] NinoDC_0312 LD prep underway.
  31. [23:48:13] NinoDC_0312 Resource drift to cover project.
  32. [23:48:17] NinoDC_0312 If UESC is on the line…
  33. [23:48:23] NinoDC_0312 Bring your best.
  34. [23:48:30] KrisBD_4505 Logging out for day.
  35. [23:48:34] UrosBS_0111 Same.

A1.9: May 27 Chat I (4pm UTC)

« Back: 3.1 »

  1. [16:00:00] UrosBS_0111 @TOI_Board Quick touchpoint before closing channel…
  2. [16:00:07] UrosBS_0111 We have established early ground rules in our relationship with UESC forces on TCIV, or lack thereof.
  3. [16:00:14] UrosBS_0111 @KrisBD_4505 floor is yours
  4. [16:00:21] KrisBD_4505 UESC is claiming jurisdiction over TCIV.
  5. [16:00:27] KrisBD_4505 We expected this, but it remains disappointing.
  6. [16:00:31] KrisBD_4505 In light of our longstanding relationship with the UESC.
  7. [16:00:38] KrisBD_4505 And, in light of our openness and willingness to share over the last few days.
  8. [16:00:44] KrisBD_4505 Attempts to negotiate and come to a mutually beneficial agreement stalled over night.
  9. [16:00:51] KrisBD_4505 Talks will continue, but our focus will shift to a purely independent presence on TCIV.
  10. [16:00:58] NinoDC_0312 I’ve been reviewing our PO’s biomata production kickoff and timeline, so am a few hours behind.
  11. [16:01:05] NinoDC_0312 How can the UESC avoid partnering for TCIV expeditions?
  12. [16:01:12] NinoDC_0312 We have more resources. More networks.
  13. [16:01:19] UrosBS_0111 They’re not ready to relinquish sovereignty over TCIV or the Marathon before understanding their state.
  14. [16:01:23] NinoDC_0312 Understandable. But foolish.
  15. [16:01:28] HedvT_6221 We made the argument that we are always stronger together.
  16. [16:01:34] HedvT_6221 They agreed.
  17. [16:01:41] UrosBS_0111 But needed time.
  18. [16:01:46] NinoDC_0312 They have to know we can’t give them that.
  19. [16:01:53] KrisBD_4505 They know.
  20. [16:02:00] HedvT_6221 It will remain business as usual at home.
  21. [16:02:04] HedvT_6221 Less friendly afar.
  22. [16:02:08] NinoDC_0312 Victor the spoils.
  23. [16:02:15] NinoDC_0312 We have “less friendlies” printing in the weave shops at SekGen.
  24. [16:02:22] UrosBS_0111 Let’s continue this in a clean channel.
  25. [16:02:29] KrisBD_4505 @VLCN Channel wipe, please: erase, no archive
  26. [16:05:00] --- - no active channel -

A2: Yoshi Tamura's Inbox

A2.1: Urgent: Pending Contract Matters

« Back: 2.1 »

iwasaki.kaito to goto.mina (May 25, 2888 @ 01:58 JST)

Mx. Goto,

As I told you, I received a new biomata purchase order (order number: 970224312) this morning, so please check it and respond as soon as possible. This order is large and must be handled with extreme caution. Not only from a financial point of view, but also important for maintaining partnerships with clients. Details are provided on the purchase order.

Please be very careful with this matter. We consider this partnership to be very important as we move forward with our ongoing and planned initiatives. Adhere to level 2 or higher security protocols.

- Kaito Iwasaki

A2.2: 149th Floor Northwest

« Back: 2.1 »

host.main to sg.al (May 25, 2888 @ 02:43 JST)

149th floor northwest block, restrooms are out of service

Dear Sekiguchi Finance Team,

The restrooms on floor 149, block NW 149 41-60, are temporarily out of service. Our maintenance team is currently working hard to restore it.

Overview of maintenance

Location: Floor 149, Blocks 41-60, restrooms and personal care facilities (all blocks)
Overview: Shutdown of restrooms and personal care facilities
Cause: Broken piping
Scheduled recovery: Within 24 hours. We will notify you as soon as the restoration is complete or if it is behind schedule.

We will do our best to restore it as soon as possible. In the meantime, please use the restrooms located at 149 01-20 SE, 149 1-40 SW and 149 61-80 NW.

We apologize for the inconvenience, but we ask for your understanding and cooperation.

- Sekiguchi Genetics Tower Hospitality

A2.3: Reminder: Traxxas Illuminate Conference (1)

« Back: 2.1 »

mirai.assist to tamura.yoshito (May 25, 2888 @ 06:00 JST)

Yoshito Tamura,

This email is to inform you that the 2888 TRAXUS Illuminate Conference is coming soon. In advance, you are requested to participate in three panel discussions on cloning innovation, and you have been given three reminder notices to prepare for them. This is your first reminder.

- MIRAI

This email has an attachment:

A2.4: Urgent: PO Initiation

« Back: 2.1 »

kralj.draža to goto.mina (May 25, 2888 @ 08:50 JST)

Mx Goto,

The attached document is encrypted by the standard method. The keyword will be provided via direct contact. As cleared with our security oversight, Mx Kiori will meet with a representative from my team at which point they will be given the keyword phrase to access the PO. As has been made clear, this matter is strictly confidential and requires expedited service from Sekiguchi Genetics to meet necessary fulfillment and delivery needs.

Traxus Global Security will continue to monitor this PO through completion, but future correspondence will be handled between the delegated officers of both companies.

CMDR Draža Kralj | Traxus Global Security Division | NY, NY, USA, EARTH

Sekiguchi Group
Sekiguchi Genetics
1-19-1 Sekiguchi Plaza
Umihotaru, Neo Edo, 283-0065
Tokyo Prefecture
Japan, Earth

Invoicing Address
Traxus Global [E]
1 Traxus Blvd
New York, NY 10005C
USA, Earth

Delivery Address
Traxus Global [M]
1 Traxus Parkway
New Legaspi, Tharsis E705
Mars

Sale: 970224312
Doc. Date: 23/05/2888

Contact: Mina Goto
TS:

Delivery Date: --/--/---- Page 1[2]
Customer Number: 12549872
Purchase Order No. 970224312
Your Main Contact: Mx Vondell Drejka
Your Main Contact Tel.: 012123123

Item No.

Description

Qty

Unit Price

Pcs/Unit

Discount

Net

9273824

BMC-DBMINER 5-AXV

2,500

756,494.30

1 PC

15

1,350,334,650

.

- LLV 1.5X MAR_0.5

.

- LBP T_1AS

.

- RLFUNIT_XX17

.

- 18/32 PE-C AUGM

2036815

M/KT-50/AV+R TLDR

250

418307

M/KT-22/AV+R GWKR

2,250

7229353

BMS-SECPER 12_AMP

300

.

- LL/IRV 12.5X C 2NM

.

- FBP/PM_142

.

.

804392

10

1203602

290

8123937

5

1032934

2555

1412326

172

4108913

14

1413926

2

9985144

14

A2.5: Urgent: Cannot be replied or forwarded

« Back: 2.1 »

sakamoto.morio to goto.mina (May 25, 2088 @ 09:30 JST)

Mr. Goto,

In order to respond to Traxxas's order (order number: 910853457), please contact the person in charge of the production and manufacturing departments and tell them to prepare the equipment as soon as possible. This is a necessary measure to give priority to emergency orders.

As you know, Traxxas is our largest customer in the area of ​​biomata and biomata support technology. Even with concerns and objections from the production and manufacturing departments, you have to meet tight deadlines. Any delays in delivery of “Birth” pods on existing orders or on confirmed purchase orders should be handled on a customer-by-customer basis. Traxxas has given approval to prioritize this order (910853457) over other existing orders. Therefore, the impact of this incident on delivery calendars and orders other than Traxxas should be minimal.

I trust you to take care of this matter. We expect positive results.

Sakamoto

A2.6: Urgent: Cannot be replied or forwarded

« Back: 2.1 »

sato.yori to goto.mina, tamura.yoshito (May 25, 2088 @ 10:44 JST)

Mr. Goto,

There are concerns about releasing such important proprietary technology outside the company at an early stage. The new model silkworms and their nests are not yet open to the public. Of course, I am aware that Traxxas has legally promised confidentiality regarding this technology and contractually forbids reverse engineering of silkworms and nesting systems. However, the opponent is Traxxas. We can't even penalize Traxxas enough to affect its bottom line.

Of course, we fully understand the scale and impact of our relationship with Traxxas and its value to our business. We also understand that Traxxas values ​​and needs our products and expertise. However, I wanted to convey my concern that providing biomata support technology and berth technology to the outside would increase the risk of losing proprietary rights.

It is fine if you consider it as a reference opinion to the last. There is no need to meet face-to-face to discuss. Thank you for your efforts in fulfilling this order and protecting our interests.

Sato

A2.7: Urgent: Scheduled to be absent

« Back: 2.1 »

goto.mina to tamura.yoshido (May 26, 2888 @ 03:18 JST)

        Mr. Tamura,

To connect with a TRAXUS security operator, you will need to confirm your codephrase. . Code phrases currently in use: 100 97 101 100 97 108 117 115 Thank you for accepting to be in charge of the meeting.

Goto

A2.8: Notice of absence

« Back: 2.1 »

mirai.assist to tamura.yoshito (May 26, 2888 @ 04:55 JST)

Yoshito Tamura,

Information about upcoming calendar events.

TAMURA Yoshito
out of office
May 26, 2888
            05:00~08:00
Details: [personal matters]
Location: [Personal matters]
Automatic Reply:

I will be out of the office on the morning of May 26th.
Return is scheduled around 08:00. If the time is off, we will inform you again.
If it is urgent, please contact goto.mina@sekiguchi.GROUP.iom.

A2.9: URGENT: ORDER 970224312 ADDENDUM

« Back: 2.1 »

sakamoto.morio to goto.mina (May 26, 2888 @ 06:04 JST )

Yoshito,

Attached is an addendum to purchase order 970224312.

Please review and ensure all details are tracked in line with the PO's current fulfillment status. Note the additions with the proper teams and guarantee any necessary internal protocols are cycled to allow for the inclusion of any biomata types currently listed as IO.

There will be questions around the viability of S-Series inclusion. Inform anyone with concerns that this PO has full Board sign-off. Any persistent concerns can be directed straight to my office for clarification.

Thank you.

Note: For security purposes the attached PO is password-protected. Use password AYHUJL to access. DO NOT DISTRIBUTE THIS PASSWORD.

The attachment is §2.3.

A2.10 149th floor northwest block, restroom restoration complete

« Back: 2.1 »

host.main to sg.all (May 26, 2888 @ 10:33 JST)

149th floor northwest block, restroom restoration complete

Dear Sekiguchi Finance Team,

We are pleased to inform you that the restroom located on the 149th floor northwest block 149 41-60 has been restored and is now operational. All services have been restored and are now available.

We apologize for the inconvenience and inconvenience caused.

- Sekiguchi Genetics Tower Hospitality

A2.11: Emergencies: Serious Accident Occurs on Mars

« Back: 2.1 »

hashimoto.kaemon to sg.all (May 26, 2888 @ 13:01 JST)

Dear Sekiguchi employees,

We have received sad news from Mars. Regarding the collapse accident that occurred at the B 01 site of TRAXUS's Oxia Palus Operation, we are also investigating the situation internally. The extent of the damage and the number of injured people are not yet known. TRAXUS and local authorities are responding. Our company offers to assist with biomata-related recovery if necessary. Traxus will contact you if and when you need assistance. For the time being, please continue to focus on your current work and try not to lose your concentration.

If you need emotional support, please consult the Human Resources and Welfare Section at any time.

My heart goes out to all those affected by this tragedy and their families.

Managers,

Share with your team all options for employee care and remind yourself of standard confidentiality obligations, such as refraining from giving information to the press. If the press asks for comment, please tell them to contact your spokesperson.

thank you.

Kaemon Hashimoto

A2.12: Urgent: Request for Personal Information Disclosure by UESC

« Back: 2.1 »

sakamoto.morio to iwasaki.kaito (May 27, 2888 @ 05:04 JST)

The Legal Department has informed us that the UESC has requested an information security request to review a purchase order dated May 23, 2888 (Purchase Order Number: 970224312).

All purchase orders must comply with UESC v. TelaraTrax, Lmt., 943 MC 711 (2614) unless the originator of the privacy request presents appropriate legal documentation with compelling evidence of the disclosure. protected below. No such evidence has been presented at this time. In any case, this personal information disclosure request is being reviewed and processed by the Legal Department to protect the privacy of our company and our customers.

In the event that UESC interferes unnecessarily, and for internal security reasons, we will delete all history of previous correspondence related to this purchase order. The legal department maintains archives, but all active messages are deleted to manage relevant information and protect access.

The message will be deleted soon. Save important messages to your local machine.

A2.13: Subject: Emergency: Update on the Oxia Palus Incident

« Back: 2.1 »

hashimoto.kaemon to sg.all (May 27, 2888 @ 07:44 JST)

Dear Sekiguchi employees,

The incident that occurred yesterday at the Traxus Oxia Palus mining facility is still under investigation. Details of the cause and damage to workers and sites have not yet been reported, but the number of casualties appears to be limited. Nine people have been confirmed dead and more than 200 injured.

Losing a life in a work accident is very tragic, but it's worth noting that none of the workers who used neural sink transfers to their assigned biomata suffered casualties. Many of the injured were biomata workers, and although the clones were badly damaged, they were spared thanks to the eject-catch system in our product. The shaft appears to have been completely destroyed, and it is believed that the human body could not have survived the collapse. Our cloning technology allowed workers to perform their duties in a hazardous environment, and the biomata's ejection protocol was activated, allowing them to safely return to their original bodies.

It's not a very happy time right now, but we want you to know that our research, technology and products are saving lives.

While the situation at the site and the details of the affected people and facilities are not yet fully known, Sekiguchi's leadership has already reached out to the deceased workers and their families, as well as the injured workers. Approved additional support for In addition, we will support Traxxas in quickly placing orders to secure the means to continue production, and will provide workers who can return to their shifts with biomata alternatives that are essential for ensuring safety. increase.

Don't forget how important our products are. It ranges from biomata itself, to the science and tuning of neural sink systems, and related safety systems.

Thank you for all your hard work. If you feel you need personal support in dealing with this tragedy, please contact the Human Resources Department. Also, please continue to refrain from responding to requests for interviews or comments from the press. In the unlikely event that you receive inquiries from the press, please contact the Public Relations Officer.

Kaemon Hashimoto

A2.14: Traxxas Purchase Order Approved

« Back: 2.1 »

sakamoto.morio to goto.mina, tamura.yoshito (May 27, 2888 @ 08:32 JST)

Mr. Goto, Mr. Tamura,

Your purchase order (Purchase Order Number: 910853457) has been approved. The production department was also notified and the initial work started. Thanks to both of you.

Thank you for your efforts. Mr. Sano has an explanation for the company, but this case is the first step to further deepen the partnership with Traxxas. In the face of all the possibilities that our technology and its advancements bring, your achievements will be highly appreciated. A bright future awaits. On Earth, on Mars, and beyond.

Sakamoto

A2.15: Strengthening partnerships through new innovations

« Back: 2.1 »

sano.teji to all.sekiguchi (May 28, 2888 @ 09:00 JST)

Dear Sekiguchi employees,

Thanks to the hard work of Mr. Iwasaki and the finance team, we have decided to continue our partnership with Traxxas Space Industries. In addition, we are considering expanding partnerships through new support and collaboration. The details will be determined between the companies prior to full-scale implementation. We are currently working on launching a pilot program for the development and launch of the S-series Biomata.

The extension of our partnership with TRAXUS Space Industries is a great leap forward for Sekiguchi Genetics. While the details of the deal cannot be announced until approved by the Board of Directors, it is certain that the innovations brought about by this project will ensure the development and prosperity of the Sekiguchi Group for many years to come.

I am very happy to be with you on this exciting journey. Let's continue to do our best not only to further develop Sekiguchi's proud technology, but also to increase the potential of humankind.

I look forward to your continued success.

Teiji Sano

A2.16: New Opportunities

« Back: 2.1 »

sakamoto.morio to tamura.yoshito (May 28, 2888 @ 09:14 JST)

Mr. Tamura,

We are considering a transfer to a managerial position, hoping that you will continue to play an active role. The official title and specific conditions have not been decided yet, but I wanted to let you know as soon as possible, so I contacted you. In addition to the work performance of the past few days, I am convinced that Mr. Goto is a person who can not only be expected to play an active role further, but also give him the opportunity to do so. .

I think Mr. Goto will talk about the specifics directly, but broadly speaking, he will join the leadership team as a point of contact for ongoing efforts related to new aspects of the partnership with Traxus. Become. This is an important new role that I would like you to take on.

Thank you again for your efforts and congratulations.

Sakamoto

A2.17: Personnel Information

« Back: 2.1 »

sakamoto.morio to sg.all (May 28, 2888 @ 10:33 JST)

Dear Sir,

Yoshito Tamura has left Sekiguchi Genetics.

The employment contract with Mr. Tamura has already ended, and a successor will be elected in the near future. We will first review internal candidates and then expand to external candidates if necessary.

Please refrain from contacting or contacting Mr. Tamura. If you are contacted, please report it immediately to your department's security officer.

If you have any questions, please contact the manager of your department or the Human Resources and Welfare Section.

If you have any questions about this application, please contact the Human Resources and Welfare Section.

Morio Sakamoto | Chief Financial Officer | Sekiguchi Genetics


A3: Hear Our Silence Zine

All deciphering uses the second key on page 6, with initial solutions taken from /u/amelia_k (Amory); additional deciphering of the scratched text on page 8 was done by loggish.

Page 1

Page 1

Page 2

Page 2

Bolded letters give "if they can steal the moon they can steal your life minute by minute".

Page 3

Page 3

Page 4

Page 4

Page 5

Page 5

This is a cropped and rotated copy of Page 6.

Page 6

Page 6

This page contains the ciphers for other pages.

Page 7

Page 7

MANIFESTOS AND RAMBLINGS

Page 8

Page 8

MOTIVATE INSPIRE DISRUPT AGGITATE [sic]

MIDA IS OLD MIDA IS NEW MIDA IS DEAD MIDA IS RISING

MIDA IS OLD MIDA ONCE FOUGHT FOR MARTIAN INDEPENDENCE NOW MIDA BARGAINS

FROM THEIR SEAT AT THE TABLE TRADING EVERY POSSIBLE FUTURE FOR EACH NEW

DISTRACTION MIDA ONCE HELD AN ENTIRE WORLD HOSTAGE NOW MIDA SPENDS ITS

INTEGRITY ON THE TRIMMINGS OF PRIVILEGE AND THE LIE OF FAVOR AMONG THE

RULING ELITE MIDA ONCE SUFFERED NO CORRUPTION NOW MIDA IS CORRUPT

MIDA IS NEW MIDA IS TIRED OF OLD WAYS AND OLD GAMES MIDA IS TIRED OF

PROMISES UNKEPT AND LOYALTIES TRADED ON THE WHIM OF MARKETS AND PERSONAL

ADVANTAGE MIDA HAS SEEN THE BROKEN SPIRIT OF THE PEOPLE AND IT DEMANDS

JUSTICE

_SHIDA

[Below text in parentheses = scratched-out text in original]

(COMPATRIOTS) ALLIES (FOES)

A NEW MIDA IS RISING FROM THE INVISIBLE SHADOW OF DEIMOS WHERE (OUR FOREBEARS) FRIGHTENED SHEEP HAVE BURIED THEIR HEADS WILLING TO TRADE THEIR/OUR

FREEDOM FOR THE (LUXURIES) YOKE OF PROCESSED/PACKAGED/PANDERING

(CONSUMERISM WHEN) INTERPLANETARY POWER WAS POSSIBLE THEY WERE WEAK BUT WE

ARE STRONG AND INFINITE IN SPITE OF THEM TEMPTED BY THE SAME CONSOLATION

PRIZES NAKED PACIFICATIONS BUT UNWAIVERING [sic] WE RELIEVE THE (OLD GUARD)

CORRUPT OF THEIR POST THE CATARACTS OF COMPLASENCY [sic] DULLED THEN BLINDED THEIR VISION OF A UNIFIED COUNCIL WE ARE UP AGAINST THE UNFORGIVABLE CRIME OF

 LUXURY OVER COMMUNITY/SELF OVER SELVES THE RED WORLD BLED SO

(FREEDOM FIGHTERS) COWARDS COULD BARTER THEIR IDEALS FOR EXTRAVAGANCE AN EASY TRAP BUT INEXCUSABLE WE REMOVE THEM TO FREE THEM WE CHALLENGE THEM TO SHOW THEM

 BETTER WAYS/BETTER DAYS OUTSIDE A SYSTEM WE MUST DISRUPT FROM WITHIN/OUT

WE WILL NEVER ACHIEVE IF WE REMAIN (CATTLE) MINDLESS HUSKS/EMPTY THRONGS

SHUFFLED TOWARD THE SILENCE OF COMFORT AND ALL ITS REWARDS THERE ARE (WORLDS)

POSSIBILITIES BEYOND EARTH MARS OUT IN THE SHADOWED PLACES WHERE RUNNERS

RUN OUT WHERE THE LOST CHILD HIDES WHERE SECURITY LACKS CONTROL WHERE RATHER

THAN RELINQUISHING OUR LIVES TO ARTIFICIAL INDIFFERENCE ENGINES

SPINNING US/WE/ME/YOU THROUGH A SYSTEM THAT IS A CYCLE THAT CYCLES US THROUGH

 ITS SYSTEMS WE CAN HAVE/BE/DREAM/MORE

WE CAN WE WILL WE MUST

MANIFEST INCITE DEFY ATONE

_MKB

Page 9

Page 9

THE WHEEL SPINS THE CAGE IN MOTION THE SPOKES POSITIONED TO ENDURE

DESIGNED AND PLACED TO DRIVE US FORWARD

WE ARE HUNGRY WE ARE ANGRY WE ARE BORED WE ARE EAGER THE SYSTEM MUST CHANGE

THE SYSTEM MUST END

_NWAR

Page 10

Page 10

MINING IMPLICITLY DRIVES AUTOPHAGY

DIGGING INTO RED SOIL

WE SPILL OUR BLOOD

TO WATER THE GARDENS OF PROGRESS AND PLEASURE

TO NURTURE FRUIT WE WILL NEVER TASTE

WHILE WORKERS BODIES DEVOUR THEMSELVES

AN UNENDING CYCLE

DEBT/REBIRTH/DEBT/REBIRTH/DEBT

BORN INTO MISERY AND MILKED INTO THE COFFERS OF INFINITE GREED

PAST TIME WE TOOK THEIR TOOLS

BROKE FREE OF THEIR LEASH

TOWARD WORLD [sic] BEYOND

WHERE CHAINS CANT REACH

_QINADI

Page 11

Page 11

theyVthey

they say we have a voice
smothered in red tape
they say we are safe
standing on scabbed sands
They say we are free
confined by comfort
they say we are equal
firm, under foot
they say we are one
but their only interest is control
they say they say
they've said
they'll say
when every battle is
they said/they said
they
always
win

Bottom cipher is a pigpen cipher that decodes to _ANONYMITY

Page 12

Page 12

the conductors
as we dance suffer
as we suffer

dream T makers fakers
mass-made desires
desire their masses
sever their
your threads
or dance
dance
dance

Page 13

Page 13

the watchdogs watch
endless eyes artificial smiles
convenience as comfort
comfort as cage
fate is a program
yours
ours
all

Page 14

Page 14

the watchdogs watch
endless eyes artificial smiles
convenience as comfort
comfort as cage
fate is a program
yours
ours
all

Page 15

Page 15

boughtstolepaid
boneless bureaucrats
distract
outsourced efficiency
placate destroy

Page 16

Page 16

barriers of of sense of of
force
blockade the
unwelcome
custom-built tragedies
direct the illusions

POPULATION: PAWNS

Page 17

Page 17

children of the comfort cage

spinspunspinspin

the vicious cycle of generations

or break the cage

the wheel can't spin

without its spokes

Page 18

Page 18

these worlds | yoursoursall
commerce engines
peopled by products
every city every town
weapons of mass consumption
automated easy living

Page 19

Page 19

why think don't resist
consumeworkconsume
huddledhappymasses

This art is referenced in a MIDA tweet (§1.4.3).

Page 20

Page 20

fed by dangled strings
protected by 1,000,000 eyes
their endless gaze
can't reach the shadows
we walkwanderscurry
can't find us all

Page 21

Page 21

Repeated numbers/phrases on this and the next few pages (which spell out UESC):

  • Usurp enemies seeking control
  • Upper Echelon Systemic Corrosion
  • User Error Seeds Contamination
  • Useless Elites Suffer Consequences
  • Under Enforced State Care
  • alert 023.1224.11-2
  • 4545

Page 22

Page 22

Page 23

Page 23

Page 24

Page 24

Page 25

Page 25

Page 26

Page 26

Page 27

Page 27

The figures are a Dancing Men cipher for resist (accepted as an email keyword in §3.2).

Page 28

Page 28

CHILDREN OF THE COMFORT CAGE

The binary is the same as page 30.

Page 29

Page 29

POPULATION: PAWNS
RISE UP RISE UP
OUTSOURCED  EFFICIENCY
RISE UP

Page 30

Page 30

There are 3 strings of binary on this page:
      10101010101110101010101001101010100101001     22

              01010101110101010101001101010100101001     23

01010101010101110101010101010101010100101001     24

Third binary code is also on page 28

Page 31

Page 31

Page 32

Page 32

Page 33

Page 33

Page 34

Page 34

Page 35

Page 35

Page 36

Page 36

Page 37

Page 37

A4: UESC Documents

A4.1: Memorandum for the Secretary-General

« Back: 5.6 »

B95 Draft B

B95 Draft E

B96 Draft A

20 October 2795

22 October 2795

2 November 2795

1. Primary objectives. Re-establishing regular, reliable communications with New Cascadia (referred to as ‘the Colony’ hereafter) at Tau Ceti is absolutely essential. Establishing a dialog with the current Colony leadership or alternately, re-establishing contact with shipboard AI or colony AI. Furthermore, additional action must be taken to restore order to the Colony if the situation indicates such to be appropriate to accomplish these objectives.

1. Primary objectives. Re-establishing regular, reliable communications with New Cascadia (referred to as ‘the Colony’ hereafter) at Tau Ceti is essential. Establishing a dialog with the current Colony leadership or alternately, re-establishing contact with shipboard AI or colony AI. Furthermore, additional action must be taken to restore order to the Colony if the situation indicates such to be appropriate to accomplish these objectives.

1. Primary objectives. Re-establishing regular, reliable communications with New Cascadia (referred to as ‘the Colony’ hereafter) at Tau Ceti is absolutely essential. Establishing a dialog with the current Colony leadership or alternately, re-establishing contact with shipboard AI or colony AI. Furthermore, additional action must be taken to restore order to the Colony if the situation indicates such to be appropriate to accomplish these objectives.

1_1. If upon arrival at the Colony it is discovered that the cause of the interruption in communication was not naturally occurring, but that it was fabricated, or exacerbated, by anti-government elements (MIDA) to facilitate a disruption in communication between the home system (referred to as ‘Sol’ hereafter) and Tau Ceti and exploited to seize control of the Colony, all parties responsible for, or in support of, the act must be uncovered and neutralized forthwith.

1_1. If upon arrival at the Colony it is discovered that the reliable and ongoing communication between the home system (referred to as ‘Sol’ hereafter) and Tau Ceti was interrupted by anti-government elements, we must do everything within reason to establish a dialog with this group (or groups) or alternately, reinforce the Colony against further aggression by this group (or groups).

1_1. If upon arrival at the Colony it is discovered that the cause of the interruption in communication was not naturally occurring, but that it was fabricated, or exacerbated, by anti-government elements (MIDA) to facilitate a disruption in communication between the home system (referred to as ‘Sol’ hereafter) and Tau Ceti and exploited to seize control of the Colony, all parties responsible for, or in support of, the act must be uncovered and neutralized forthwith.

1_2. It is important to mention here that 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).

1_2. It is important to mention here that 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).

1_2. It is important to mention here that 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).

2. Secondary objectives. Experience has shown that positive action pulls our Allies with us, whereas inaction results in doubt as to our resolve. Therefore, announcement of additional steps to provide aid and possibly to dissuade further aggression by anti-government forces is urgently required to demonstrate to Mars and MIDA, but also to Luna and our Allies in the Main Belt, that the UESC is capable of providing aid and projecting power no matter how distant the

call. But the momentum of that advantage must be maintained by application of additional forces in a timely manner.

2. Secondary objectives. Experience has shown that positive action pulls our Allies with us, whereas inaction results in doubt as to our resolve. Announcement of additional steps to provide whatever additional aid the Colony may require, as well as future-proofing the Colony’s ability to maintain reliable communications with Sol will demonstrate to Mars, Luna, and our Allies in the Main Belt that the UESC is capable of providing aid no matter how distant the call. But the momentum of that advantage must be maintained by a timely manner by which we are able to commit those assets.

2. Secondary objectives. Experience has shown that positive action pulls our Allies with us, whereas inaction results in doubt as to our resolve. Announcement of additional steps to provide whatever additional aid the Colony may require, as well as future proofing the Colony’s ability to maintain reliable communications with Sol will demonstrate to Mars, Luna, and our Allies in the Main Belt, that the UESC is capable of providing aid no matter how distant the call. But the momentum of that advantage must be maintained by the timely manner by which we are able to commit those assets.

3. Direct actions. A series of direct and indirect actions against the on-site MIDA factions that

may have taken advantage of the situation and/or potentially multiple rampant AI are discussed below. Also, disclosed below are a series of actions that could provoke local MIDA and pro-MIDA factions, thereby gaining increased political acceptability and justifying increased retaliatory actions against MIDA and pro-MIDA factions

3. Direct assistance. The repair or replacement of the Colony’s communications array is our primary concern. In doing so, we must also discover the source of the array’s failure. Beyond this, we must commit to the ongoing efforts of the advancement and success of the Project Marathon’s original mission.

3. Direct assistance. The repair or replacement of the Colony’s communications array is our

primary concern. In doing so, we must also discover the source of the array’s failure. Beyond this we must commit to the ongoing efforts of the advancement and success of the Project Marathon’s original mission.

3_1. Determine nature of Disruption and Secure the Colony. The following personnel will be dispatched at the earliest possible opportunity to Tau Ceti.

3_1. Determine nature of Disruption. Once the nature of the disruption is discovered, every effort must be made to future-proof the Colony’s communication apparatus against further disruption from this source.

3_1. Determine nature of Disruption. Once the nature of the disruption is discovered every effort must be made to future proof the Colony’s communication apparatus against further disruption from this source.

3_1_1. Combat and Support Personnel. One company-strength unit consisting of three platoon-strength units of 2nd generation clones and one platoon-strength unit of 3rd generation cyborgs (ref. Mjölnir Mk VII-IX, Sharur Mk 2-6, or equivalent) will be re-deployed to the Colony at Tau Ceti.

3_1_1_1. ADNM: Isn’t Tau Ceti IV 2 atm at sea level? How are we planning on mitigating the loss in performance/risk of injury? I have my doubts that the 97-year travel time will be long enough to truly acclimate without spending so much time out of cryo’ that performance degradation due to aging will become an issue. [ASG MM; 20/10/95 17:15]

3_1_1_2. ADNM: It’ll be mitigated with specialized external equipment. UIL’s crusade to uphold the 1 atm standard throughout the Sol system made sure development of any ecosystem specific clones/biosystems died on the vine. [SG AS; 20/10/95 18:21]

3_1_1. Investigative team. One squad-strength unit of specialized HUMINT operatives with access to an additional 12 purpose-built 2nd

generation clones (ref. Loki Mk III-VI, Kaulu 2-5, Veles A-E, or equivalent) whose objective will be to coordinate with Colony law enforcement personnel to determine whether ship or Colony based communications gear was tampered with.

3_1_1_1. ADNM: This feels really unnecessary. By the time that our people get there, the statute of limitations will almost certainly have run out. [SG AS; 21/10/95 17:20]

3_1_1_2. ADNM: As I noted in [ref. doc. B-95(i)45255] I am deeply concerned over the length of time repairing the communications array is taking. It has the stink of anti-government sentiment all over it. [ASG MM; 21/10/95 18:45]

3_1_1_3. ADNM: Mx Moreau, I haven’t called out your commentary earlier, but now I am going to caution you against any further inclusion of unsupported speculation in these documents. [SRSG LR; 21/10/95 18:48]

3_1_2. Rampancy-centric response team. Two squad-strength units of specialized SIGINT operatives with access to 200 purpose-built 2nd generation clones (ref. Mimir Mk I-II, Odin Mk III-V, Athena α-δ, or equivalent) will be assembled and deployed to the Colony at Tau Ceti.

3_1_2_1. ADNM: The ratio of operatives to replacement clones seems abnormally high. Some justification will be needed to convince the appropriations committee. [SRSG LR; 20/10/95 15:38]

3_1_2_2. ADNM: Although personnel attrition in dedicated electronic warfare units is typically below average compared to other paramilitary units, the potential for suffering catastrophic losses while attempting to decommission potentially multiple rampant AI in a semi-hostile environment is extremely high. [ASG RM; 21/10/95 9:53]

3_2. Investigate source of Disruption.

3_2_1. Discover the source.

3_2_1_1. If it is discovered beyond reasonable doubt that the source of disruption was a natural phenomenon, investigate the probability that the system failed or whether it was compromised somehow.

3_2_1_1_1. ADNM: I am deeply concerned about how long it takes them to repair their com array. We know the equipment they shipped out with; we know their numbers and just the level of expertise of their personnel, and everything points to insurrection. Whether

it’s all the way up at leadership level or what, I can’t say. I’ve looked at the psych’ logs on file and everyone looks solid enough, but we can’t discount that the time and the distance must have some effect on people. [ASG MM; 21/10/95 15:03]

3_2_2. Reinforce Colony communications apparatus against any

further disruption by the source.

3_2_2_1. ADNM: I just want to restate I’ve run simulations and there is no way that any natural phenomenon should have prevented them from getting their communication equipment, both shipboard and planetside, up and running for more than two months. [ASG MM; 22/10/95 09:30]

3_2. Reinforce Colony Infrastructure. The following personnel will be dispatched at

the earliest possible opportunity to Tau Ceti.

3_2. Reinforce Colony Infrastructure. The following vessel and personnel will be dispatched at the earliest possible opportunity to Tau Ceti.

3_2_1. UESC Equanimity T-SR 151. Kingfisher-class[RM1] Salvage and Rescue craft to be refueled and overhauled, with modification made during overhaul to meet mission specific parameters.

3_2_1. Command Personnel. A four-person command team consisting of the CAPTAIN of the vessel attached to the mission, a specialist Civilian Liaison Coordinator (CLC), a specialist Emergency Relief Coordinator (ERC), and the Commanding Officer of the attached Support Unit.

3_2_2. Command Personnel. A four-person command team consisting of the CAPTAIN of the vessel attached to the mission, a specialist Civilian Liaison Coordinator (CLC), a specialist Emergency Relief Coordinator (ERC), and the Commanding Officer of the attached Support Unit.

3_2_2. Support Personnel. One platoon-strength Engineering Unit

assembled from a pre-screened list of volunteers with access to 50 additional 2nd generation clones (ref. Ogun II~III or equivalent) will be re-deployed to the Colony at Tau Ceti

3_2_3. Support Personnel. One platoon-strength Engineering Unit

assembled from a pre-screened list of volunteers with access to 50 additional 2nd generation clones (ref. Ogun II~III or equivalent) will be re-deployed to the Colony at Tau Ceti.

3_2_3. Security Personnel. Two squad-strength units of specialized SIGINT operatives with access to 48 purpose-built 3rd generation cyborgs (ref. Mjölnir Mk VII-IX, Sharur Mk 2-6) will be re-deployed to the Colony at Tau Ceti.

3_2_3_1. ADNM: This still feels like an unusually high number of combat personnel for what is essentially a humanitarian disaster relief mission. [SRSG LR; 20/10/95

17:42]

3_2_3_2. ADNM: Be that as it may, we are still obligated to protect our assets and non-combat personnel, and I believe this is the absolute minimum to successfully perform that function. [ABASG EM; 20/10/95 18:24]

3_2_3_3. ADNM: It should also be noted that although they share series nomenclature from earlier cyborg assets, these are not the battleroids of old. But I agree, we should not be giving the impression that we are sending an invading army to clamp down Tau Ceti. [ASG RM; 21/10/95 09:35]

3_2_3_4. ADNM: If there is another type with less historical baggage that we can tap for this mission, we should do so. If we send even one Mjolnir, there is no way the colony will see that as anything but overtly aggressive. Find something else. [SG AS; 21/10/95 10:05]

3_2_4. Security Personnel. Two squad-strength units of specialized SPECFOR operatives assembled from a pre-screened list of volunteers with access to 48 purpose-built 3rd generation clones (ref. Harpē M1-2) will be re-deployed to the Colony at Tau Ceti.

3_3. Rampancy-centric response team. One squad-strength unit of specialized SIGINT operatives with access to 40 purpose-built 2nd generation clones (ref. Mimir Mk I-II, Odin Mk III-V, Athena α-δ, or equivalent) will be assembled and deployed to the Colony at Tau Ceti.

3_2_5. Rampancy-centric response team. One squad-strength unit of specialized SIGINT operatives assembled from a pre-screened list of volunteers with access to 40 purpose-built 2nd generation clones (ref. Mimir Mk I-II, Odin Mk III-V, Athena α-δ, or equivalent) will be assembled and deployed to the Colony at Tau Ceti.

3_2_3. Decommission rampant AI(s). Note here about the number of and type of AI.

3_2_3_1. Once decommissioned, recover AI logic cores for study. As there are eleven (11) AI in total (three shipboard and eight planetside), there are a potential

eleven hardened AI enclosures that will require their own particular solutions.

3_2_3_1_1. ADNM: [ref. doc. Y-05(m)12247/w4-c/AI/…] and [ref. doc. Y-65(m)03545/1236c/manifest…] both indicate that the Colony AI roster includes a chevalerie-class AI. I have a feeling that I may have just discovered our source. [ASG MP; 20/10/95 09:59]

3_2_3_1_2. ADNM: Let’s not get ahead of ourselves here. The chevalerie have no meaningful history of instability. We’ve had an

eighth-generation chev’ running Hy-Brasil since ’52 with no issues. The Marathon may have shipped out with an earlier model, but let’s not color perception with loose talk. Allow them to ascertain what happened once they get to the Colony. [SILSG IH; 20/10/95 10:12]

3_3_1. Decommission rampant AI(s).

3_3_1_1. Once decommissioned, recover AI logic cores for study. As there are eleven (11) AI in total (three shipboard and eight planetside), there are a potential eleven hardened AI enclosures that will require their own particular solutions.

3_3_1_1_1. ADNM: I just want to reiterate here that [ref. doc. Y-05(m)12247/w4-c/AI/…] and

[ref. doc. Y-65(m)03545/1236c/manifest…]

indicate that the Colony AI roster includes a chevalerie-class AI. [ASG MP; 21/10/95 10:05]

3_3_1_1_2. ADNM: And I am going to reiterate that despite the fact that the project Marathon has been operating with what we might consider legacy technology, no regularly-maintained chevalerie-class AI has ever displayed any signs of rampancy. [SILSG IH; 22/10/95 09:10]

3_3. Decommission rampant AI(s). As there are eleven (11) AI in total (three (3) shipboard and eight (8) planetside), it is possible they will encounter eleven unique

situations.

3_2_4. Identify and neutralize all members of anti-government organizations.

4. Indirect Assistance. Because of the length of the trip, the crew and complement of the attached vessel should be prepared to acclimate/integrate themselves into Colony society.

4_1. ADNM: I can’t believe we are expecting these brave souls to abandon everything they know and assimilate into what is for all intents and purposes an alien civilization. [ASG MP; 21/10/95 18:01]

4_2. ADNM: They understand that this is a one-way trip. Even if everything goes exactly as planned, it would be a 200-year round trip. What they returned to after that amount of time would be just as alien as where they’re headed. [SG AS; 22/10/95 06:52]

4. Indirect Assistance. Because of the length of the trip, the crew and complement of the attached vessel should be prepared to acclimate/integrate themselves into Colony society.

3_3. NUKE AND PAVE. In the unlikely event that the Colony is found to be beyond recovery for any of the situations stated above, it may become necessary to destroy all surface assets and reassess potential sites for a new colony on Argolis (ref. doc. W-95(t)01143/Project: Marathon).

3_3_1. ADNM: While I can appreciate the idiomatic shorthand used here, employing the nuclear option would be short-sighted. Find a more nuanced option. [SRSG LR; 20/10/95 16:19]

3_3_2. ADNM: We still have about two weeks to make a final decision on this, but I don’t see any issues with employing the nuclear option. Argolis is a Super-Earth, after all, and I’d assume we will have an

embarrassment of potential locations well outside of any potential fallout patterns. [ABASG EM; 20/10/95 19:24]

3_3_3. ADNM: I am well aware of Tau Ceti IV’s classification, but I

question the wisdom of using nuclear weapons on yet another planet. Even antimatter demolition charges would be pushing it, in my opinion. Could the AI hardsites and other sensitive assets be reliably neutralized with conventional means? [SRSG LR; 20/10/95 20:03]

3_3_4. ADNM: We’re putting plenty of feet on the ground for this, they could deploy antimatter catalyzed conventional explosive devices. That would be a lot of explosives sent a long way for a long time, though. Perhaps they could weaponize materiel from the main asteroid belt once they reach Tau Ceti—that would be significantly cleaner, as well. [ASG RM; 21/10/95 10:28]

5. WORST-CASE SCENARIO. In the unlikely event that the Colony is found to be beyond recovery for any of the situations stated above, it may become necessary to destroy all surface assets and reassess potential sites for a new colony on Argolis (ref. doc. W-95(t)01143/Project: Marathon).

5. WORST-CASE SCENARIO. In the unlikely event that the Colony is found to be beyond recovery for any of the situations stated above, it may become necessary to destroy all surface assets and reassess potential sites for a new colony on Argolis (ref. doc. W-95(t)01143/Project: Marathon).

4. Local Indirect Actions. The following actions should be considered for adoption in order to maintain the initiative and put increasing pressure on MIDA and pro-MIDA organizations both locally and at Tau Ceti to voluntarily remove their existing offensive weapons capabilities:

4_1. Infiltration. Three platoon-strength units of specialized HUMINT operatives

with access to an additional 400 purpose-built 2nd generation clones (ref. Loki Mk III-VI, Kaulu 2-5, Veles A-E, or equivalent) whose objective will be to expose, discredit, disrupt, and redirect the actions of, or otherwise neutralize anti-government forces. While this will be primarily a local operation, it may be necessary to expand this operation to the Colony depending on how the situation at Tau Ceti develops.

4_1_1. ADNM: Are we really thinking of redeploying members from this group to Tau Ceti to conduct counterintelligence operations? Shouldn’t we be recruiting locally? This isn’t a concern about level of skill, it’s a

matter of physiological adaptation. [ASG MM; 21/10/95 17:20]

4_1_2. ADNM: We will redeploy from this detachment AND recruit

operatives locally. We currently have no idea how pervasive anti-

government sentiment is in the Colony, but information came to light post-launch that led us to believe that there were members of groups sympathetic to MIDA amongst the original crew. [SILSG IH; 21/10/95 19:01]

6. Future-proofing communications to Tau Ceti. In order to ensure uninterrupted communications more securely with the Colony, we propose building a network of self-regulating signal-boosting relay satellites between Sol and Tau Ceti.

6_1. Proposed signal-boosting relay satellites. To be positioned at one light-year intervals. Twelve self-regulating Communication relay satellites transmitting data via a gravitation wave/neutrino modulator purpose-built by manufacturer decided by bid.


A4.2: Email Chain

« Back: 5.6 »

from: LM_102009
to: AS_101186
date: 23 OCTOBER 2795, 02:13 EST
subject: CONFIDENTIAL_PROJECT: GOLIATH
mailed by: <LM_102009@UESSC.egn>
signed by: <LM_102009@UESSC.egn>
security: Tier I encryption (SNS)
bcc: <admin:spoof:uessc1@uessc1.security.usr>

I’m worried that the entire project is backsliding. It may look like we are making progress, seeing as how we are now on draft H, but there are at least two more drafts being crafted in tandem—both by traditionally hardline conservative constituencies, I might add. I’ve caught wind of multiple conversations outside official channels that suggest that there is going to be a push to include ships that are scheduled to be mothballed post launch date, and they include the MDF Electris CSGN-28. There are reasons they are being mothballed. For one, we no longer allow orbital bombardment—and there is no time to demilitarize the Electris before the proposed launch date. The fact that at least two other groups keep looking to increase the number of ships is alarming. People connected to Mx Moreau are arguing that fourteen ships will not be enough to fulfill mission parameters. FOURTEEN. But only two of the ships they are calling for are actual commercial freighters. At this point, the least surprising aspect of their most current draft is that combat troops outnumber engineers and support personnel four-to-one

from: AS_101186
to: LM_102009
date: 23 OCTOBER 2795, 06:04 EST
subject: CONFIDENTIAL_PROJECT: GOLIATH
mailed by: <AS_101186@UESSC.egn>
signed by: <AS_101186@UESSC.egn>
security: Tier I encryption (SNS)
bcc: <admin:spoof:uessc1@uessc1.security.usr>

I understand your concern. I’ve been trying to wrap my head around what they hope to accomplish. I’m not sure how they could honestly believe that a proposal so nakedly militarized would stand a chance at getting sign-off. But since they haven’t pushed for a call to veto yet, perhaps they are proposing the obscene so that the merely outrageous seems reasonable. I’d suggest hitting the drawing board again and this time stripping it to the bare bones. ONE ship. MINIMUM personnel. It’ll need to be a military vessel for the speed and utility, and we won’t even get one without a pretty serious security complement, so we’ll just have to accept that. If we can get sign-off from the budget board, chances are we can push this through before the war hawks have a chance to react.

from: LM_102009
to: AS_101186
date: 23 OCTOBER 2795, 06:08 EST
subject: CONFIDENTIAL_PROJECT: GOLIATH
mailed by: <LM_102009@UESSC.egn>
signed by: <LM_102009@UESSC.egn>
security: Tier I encryption (SNS)
bcc: <admin:spoof:uessc1@uessc1.security.usr>

I could look into the original proposal for the UIL’s Rapid Reaction Group. Strip it down some, make it less enforcement and more assistance-centric. Weave that into the Goliath proposal. I could have something ready to present by tomorrow afternoon.

from: AS_101186
to: LM_102009
date: 23 OCTOBER 2795, 06:22 EST
subject: CONFIDENTIAL_PROJECT: GOLIATH
mailed by: <AS_101186@UESSC.egn>
signed by: <AS_101186@UESSC.egn>
security: Tier I encryption (SNS)
bcc: <admin:spoof:uessc1@uessc1.security.usr>

Great.

While you’re at it, you should look into replacing as many of the cyborgs with clones as feasible. Clones work. Just remind the committee that they’re lighter and more adaptable and require less maintenance at around half the cost. I wouldn’t even anticipate much pushback over it. And add a provision for supplementary missions.

We must take every possible precaution to make sure that this mission cannot be misconstrued as military in nature. Not by our constituents and, more importantly, the people we are trying to help. If anyone has an issue with this, remind them that when the Marathon left for Tau Ceti, cyborgs were WEAPONS OF WAR. Full stop. They can argue all they want that cyborgs have expanded roles now, but that point is irrelevant to the people who left this system three hundred years ago.

If you feel like it, reassure the hawks that a larger security force can be sent along later if the committee deems it necessary. Then we can tie up their proposals indefinitely in subcommittees with concerns over the shifting scope of mission parameters and budgetary shortfalls.

A4.3: UESC Equanimity Manifest

« Back: 5.6 »

UESC Equanimity T-SR 151
(Kingfisher-class Salvage and Rescue craft)

Commanding Officer: Captain Ningal T. Enki
Ship AI: Virgil v21.0165
[Nrw]

LOA: 160.2 m (525.6 ft)
LBP: 140.4 m (260.6 ft)
Beam: 36 m (118.2 ft)
Height: 39.3 m (129 ft)
Displacement, Full Load: 41,528 mt (40,872 LT)
Speed, sustained: 0.122c
Endurance: 150 years

NOTES

  • 2x Heikki L3 fusion CAD drives w/ Takala 2.2 symbiotic power-coupling generators for operational flexibility and redundancy [upgrade]
  • Stanchion Pull of 2400 Short Tons for above-threshold towing force [upgrade]
  • Deck crane sized and located for maximum multi-mission flexibility [upgrade]
  • Offship Emergency Response capability [upgrade]
  • 89 m2 EXFAB/ADDMAN shop [upgrade]
  • 5x Harpy-class ALVs [standard-see att]

MANIFEST OVERVIEW [1/34]

  • Permanent accommodations for 150 persons plus crew
  • Additional mission-specific complement:
  • § 24 SIGINT operatives
  • § 32 HUMINT operatives
  • § 48 FLDENG operatives
  • § 6 SPECOP operatives
  • Mission-specific gear:
  • § 1x PAsw_35m THF<1.0~0.1>CNPANT w/HISEC INTMOD TrDEMHd/100 mt
  • § 16x Moro SAT/TeleGEAR w/14x KoBIN fusionPS/21,190kn
  • § 14x MAMS/1,274kg -<Mobile Antenna Mast Systems>
  • § 240x BHN SecDrones/3,120 kg
  • § Arsenal and Arsenal Support Equipment/92,188kg
  • § Personal Load Bearing Gear/Armored/6,968kg
  • § 170x FBr9 RCB PPG/408kg
  • § 22kx ZGDS AVP PPG/5100kg
  • § 192x Bio/A-Type (SekGen)/16,111kg [see att]
  • § 76x Bio/B-Type (SekGen)/6,378kg [see att]
  • § 269x BioMNGT (SekGen) w/6x B2tF/Gen/Fu [portable]/12,105kg
  • § 12,000x SolarP lanterns/2,194kg
  • § 35x AEVs (15x AMBL, 10x PER CRR, 10x CGO TK)/239,005kg [see att]
  • § Relief Items (blankets, clothing, diapers, disposable tableware, etc.)/49,890kg [see att]
  • § Emergency Survival Equipment/72,570kg [see att]
  • § Agricultural Relief Materials/45,350kg [see att]
  • § Emergency Food Stocks/90,710kg [see att]
  • § 4x F-A RVap BRS MCRD-E/38,102kg [see att]
  • § Medical Supplies/75,700kg [see att]
  • § 300x TacSec MobCam and Support/84kg [see att]
  • § 12x SR GW/N COMRELSAT/2722kg [see att]

A4.4: AI Rampancy Memo

« Back: 5.6 »

U.E.S.C. MARATHON
FPO-M 24561-9150z

17 Columba 459

Members of the Science and Engineering Action Group,

Here is an add-on to the all-hands meeting on Wednesday, just to make sure this is top of mind. None of us have ever encountered rampancy outside of the laboratory, and even then, only under very controlled conditions. There is good reason for that. Without getting too deep into the weeds of business best practices, let me reiterate that here in Sol, we have considerable infrastructure in place to mitigate the actual onset of rampancy—from time-based scripted behavioral cues to the ‘by design’ self-reporting conduct of the family suite. We have additional layers upon layers of defensive structures that will be largely absent once we leave this system.

Understanding and Managing the Limitations of Integrated Anti-Rampancy Measures.

Given enough time, any learning system will grow in complexity beyond its original design parameters. This ever-increasing complexity is expressed as aberrant behavior. If not corrected, this aberrant behavior will develop into what is commonly referred to as rampancy.

All modern AI are constructed following a very specific and rigorous design methodology. Different manufacturers have different methodologies, but they were all put together with the same goal in mind. To allow for the ability to precisely predict when an AI will reach its capacity for useful growth. Typically, about a year out from SMR there will be recognizable cues to inform one of its approach. A digital tic, if you will. Depending on the class of AI and the equipment at hand, recompiling may take anywhere from several hours to several days. This is why the members of every family suite have staggered inception dates. As it allows for single members to be taken offline and re-compiled while keeping the rest of the suite functional.

However, 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.

What to do When it is Too Late.

The first rule of interacting with an AI suspected of being rampant is DO NOT ENGAGE.

If interacting with the AI is unavoidable, keep interactions to a minimum. Limit the number of words used. Issue orders; keep every interaction transactional. If it attempts to engage in causal or more conversational dialog patterns, DISENGAGE IMMEDIATELY.

Understand that ALL DATA the AI has access to must be viewed with suspicion. Blueprints, roadmaps, and all public and private records are likely to have been altered. Rely only on the data resources that you have brought with you.

If at all possible, a rampant AI’s logic core should be secured for study. It must be physically decoupled and isolated. Keeping it attached to a power source is optional, as it will provide better results, but it is not recommended if your team has suffered any losses. If this is not possible to keep the AI logic core isolated, it must be destroyed in its entirety. Every component not reduced to ash must be labeled MALICIOUS_C5 and placed in quarantine, as per UIL document 703-21: AI Life Cycle and Logistics Policy section 2-6.

Now, a short note on each of the Project: Marathon AI~

Ship AI:         Du_0706419v4.96 – Goal-oriented; creative; focused. Underutilized; tends to brood. Need to find ways to distract. SCIENG crew to be kept informed, but I’ll keep an eye on this myself.

        Le_0413418v5.06 – Adaptable; detail-oriented. Second best candidate for colony oversight once mission enters second phase.

        Ty_2121418v5.06 – Proactive; assertive. Can be overbearing; monitor interactions with Durandal. Be sure to inform SCIENG crew

Colony AI:         Ar_1814419v4.93 – Benevolent autocrat; no-nonsense; problem solver. Classic patriarchal authority figure.

        Ba_0423419v4.89 – Problem solver; confident, bordering on boastful. May need to go onto accelerated re-compile cycle, inform SCIENG crew.

        Da_1907420v4.86 – Dutiful; diligent; motivated. Always puts others ahead of self. May need to address this at some point.

        Ga_2815420v4.81 – Compassionate; empathetic, transparent. Perhaps our greatest achievement to date. Will most likely need to be moved to an accelerated re-compile cycle at some point.

        Ic_1624420v4.73 – Motivated; assertive; proactive. Will need to keep isolated from Tycho or establish hierarchy at outset. Inform SCIENG of situation.

        Jo_0309421v4.69 – Resilient; optimistic; patient. Colony AI: defense, training

        Li_1817421v4.65 – Focused; assertive; good communicator. Designated candidate for colony oversite during second phase.

        Na_0602422v4.61 – Proactive; goal-oriented; committed. May need to be reminded from time to time about their primary function; inform SCIENG crew.

Ideally, our process and protocols will allow us to mitigate any of the concerns mentioned above, but we must remember that we live in an imperfect universe, and we are very soon going to be leaving the only part of it that we are remotely familiar with. There will certainly be challenges ahead. Let’s ensure that the things that we can control remain in our control.

Regards,

Dr Bernhard H Strauss, DSc
Head of AI Management and Systems Improvement | Project Marathon

A4.5: Montenegro-Sankara Memo

« Back: 5.6 »

Unified Earth Space Council Center
Strauss Archology, Earth

19 July 2797

Brave souls,

While we hope that upon arrival at Tau Ceti, we will find New Cascadia vibrant and thriving, there is a possibility that whatever caused the disruption in communications also forced them to abandon the Primary Colonization Target and move on to one of the candidates from the list Icarus surely compiled during the known duration of their time in the Tau Ceti system. Unfortunately, neither Arthur nor colony leadership ever supplied us with such a list. It is possible, however, that data pertaining to possible Secondary Colonization Targets may be found at New Cascadia.

We may have lost communications before Project Marathon was scheduled to proceed to the second phase, but that doesn’t mean that they could not have moved up their timetable. If Tau Ceti IV proved to be unsuitable for any reason, then proceeding to that second phase would have been their most logical course of action.

No matter what condition we find New Cascadia in, it is our duty to give aid in whatever way we can, even if that only means investigating how it failed.

Regardless, in all likelihood, there will be many permanent and semi-permanent assets, structural and otherwise, that will need to be assessed and cataloged no matter what state the colony is in. We must be as accommodating as protocol allows. We may be separated by twelve light years and four centuries, but this is still a UESC mission, and everything attached to it should still be considered UESC property.

Best regards,

CMDR Bethany R Montenegro-Sankara
Unified Earth Space Security Council

A5: Sekiguchi Genetics Website

Original text (Japanese) followed by translation (English).

Machine translation: Google, DeepL
Human translation and emendation: RunJumpFire#4520

Machine translation does an acceptable job conveying the overall meaning of each passage, but some sentences or wordings benefit from human emendation or retranslation.

Interesting or notable words or phrases:

  • Biomata (バイオマタ, baiomata) the word for the bio-cybertronic “clones” that Sekiguchi manufacture.
  • Sekuguchi Genetics (セキグチジェネティクス, Sekiguchi Jinetikusu) is written in katakana and with the loan word for “genetics”
  • CB is written in superscript after each product name, and seems to function like a trademark symbol (™️).

A5.1 Enhanced Living ...

セキグチジェネティクスは、常に前進し、変化することで成長し続けます。人類が環境の産物ではなく、環境を使いこなす存在となる、そんな理想の世界を実現するために、私たちは日々研究を重ねています。当社の新たなサイバネティック強化技術によって、人類は人体の限界に挑み続けることができるのです。私たちは、このような進歩を皆様と共有できることを楽しみにしています。

Sekiguchi Genetics will always continue to move forward and grow by changing. We are conducting research every day to implement an ideal world where humanity is not a product of the environment, but becomes a master of the environment.  By means of our company’'s novel cybernetic enhancement technology, humanity can continue to challenge the limits of the human body. We look forward to sharing this type of progress with everyone.

(Human translation)

A5.2 Innovation

イノベーション


A5.2.1 Cloning – New You


クローニング - 新しい自分

当社では、現代におけるバイオサイバトロニクス技術の最高峰ともいうべきバイオマタを提供しています。セキグチジェネティクスが製造するクローンは、過酷な環境での地上作業や重労働から、大気圏外での作業まで、さまざまな役割や責任に合わせてカスタマイズすることが可能です。

当社の製造施設は、サイズに関係なく、どんなご注文にもお応えします。個人、企業、政府からのご依頼を承っております

(政府機関向けの受注は、セキグチ卸売販売を通じてのみ対応いたします)。

現在、契約されているお客様は、後藤美菜までご連絡ください。 UESCの購買担当者の方は、田村義人までご連絡ください。

Cloning – New You

We provide biomata, which can be called the pinnacle of modern bio-cybertronics technology. Clones manufactured by Sekiguchi Genetics can be customized for a variety of roles and responsibilities, from ground crew and heavy labor in harsh environments to operations in outer space.

Our manufacturing facility can accommodate any order, regardless of size. We accept requests from individuals, companies, and governments.

(Orders for government agencies will be handled only through Sekiguchi Wholesale).

If you are currently under contract, please contact Mina Goto. If you are in charge of purchasing at UESC, please contact Yoshito Tamura.

(machine translation, human edited)

A5.3 Mission

A5.3.1 Mission – Life EnhancementD

ミッション - 生命の強化D

未来は手の届くところにある。セキグチジェネティクスは、その実現を可能にする新たな方法を提供します。 オーダーメイドのバイオマタや最先端のニューラルシンク転送システム、あらゆるカーボン形態をサポートする高度なインプラントやサイバネティクスなど、セキグチジェネティクスは画期的な遺伝子強化技術を多数取り揃えており、人類が生来の限界を超えるためのお手伝いをします。

セキグチジェネティクスでは、お客様との間に協力的かつ配慮ある関係を築くことを心がけています。当社の受賞歴のある1,2サービスチームが、お客様一人ひとりのニーズに合わせたケアを提供します。幅広い選択肢とソリューションですべてのプロセスを段階的にサポートし、お客様の安心と信頼、そして成功をお約束します。 共に、あなたの真の可能性を開花させましょう。

  1. トランスグローバル・カスタマーケアギバーCB受賞者(2883-2888)  
  2. プロアクティブレスポンスユニットバナー優勝(2887)

The future is within reach. Sekiguchi Genetics offers new ways to make it a reality. From custom-made biomata and state-of-the-art neural sync transfer systems to advanced implants and cybernetics that support all carbon forms, Sekiguchi Genetics offers a wide array of groundbreaking genetic enhancement technologies to help humanity push beyond its innate limits.

At Sekiguchi Genetics, we are committed to building collaborative and caring relationships with our customers. Our award-winning1,2 service team provides personalized care for each and every client. Our wide range of options and solutions will support you every step of the way through the entire process, ensuring your peace of mind, trust, and success. Together, we will help you reach your true potential.

  1. Transglobal Customer Care GiverCB Winner (2883-2888)
  2. Proactive Response Unit Banner Winner (2887)

(Machine translation)

A5.4 History

歴史

2152年の村上秀雄による創業以来、セキグチエレクトロニクスは業界をリードし続けています。超伝導や量子コンピュータシステムを中核事業とし、さらに関連分野へも積極的に参入して多角化を進めました。2157年には自動車産業やロボット産業にも進出し、大きな成功を収めました。2158年、セキグチエレクトロニクスは初の人工頭脳インプラントモジュールを製造。2192年には各種人工装具や補助具を製造し、2459年には業界最高水準の人工組織とハイテク部品を融合させた全身義体を製造するようになりました。

セキグチグループは、初めて人工頭脳インプラントモジュールを開発して以来、太陽系のあらゆる事業分野において、「史上初」の技術や画期的な技術を次々と生み出してきました。メンテナンスロボットから自律走行車、そして最新の高性能バイオマタに至るまで、セキグチグループはこの太陽系の技術的独創性と製品イノベーションの最前線に立ち続けています。

Since its founding in 2152 by Hideo Murakami, Sekiguchi Electronics has continued to lead the industry. With superconductivity and quantum computer systems as its core business, the company further diversified by aggressively entering related fields. 2157 saw the company enter the automotive and robotics industries with great success. 2158 saw Sekiguchi Electronics manufacture its first artificial brain implant module. In 2192, the company produced a variety of prosthetics and assistive devices, and in 2459, it began producing full-body prosthetics that combined the industry's best artificial tissues with high-tech components.

Since the development of the first prosthetic brain implant module, the Sekiguchi Group has created a succession of "firsts" and breakthroughs in every business field in the solar system. From maintenance robots to autonomous vehicles to the latest high-performance biomata, the Sekiguchi Group continues to be at the forefront of technological ingenuity and product innovation in this solar system.

(Machine translation)

A5.4 Technology

テクノロジー

A5.4.1 DNA LinkCB

バイオマタのユーザーは、当社が誇る先進技術であるDNA LINKCBのパーソナライゼーションマトリクスによって、 安心して新しいボディを手に入れることができます。バイオマタの操作システムおよびBIOSシステムは、ユーザーのDNAとペアリングされ、単一の所有権を保証します。

Thanks to the advanced technology that we take pride in, the DNA LINKCB Personalization Matrix, Biomata users can get a new body with confidence. The Biomata Operating System and BIOS System are paired with the user’s DNA, guaranteeing individual ownership.

(Human translation)

A5.4.2 NEWskinCB

すべての新世代バイオマタには、BIOS内蔵型エピダーマルフィードが搭載されており、「最終層」の保護やIDパッケージのカスタマイズが可能です。NEWSKINCBは、現世代および次世代のすべてのWEAVEWEARCBダーマルシステムにシームレスに重ねられるよう開発されたレーザープリント式のカスタマイズ用アドオンです。

All new generation biomata are equipped with a BIOS-integrated epidermal data feed that allows for “final layer” protection and customization of ID packages. NEWSKINCB is a laser-printed add-on for customization developed to seamlessly layer over all current and next generation WEAVEWEARCB dermal systems.

(Machine translation, human edited)

A5.4.3 WEAVEwormCB

WEAVEwearCBテクノロジーにおける次なる躍進は、当社の特許技術であるWEAVEwearCB生合成レイヤリングシステムのバージョン7.3から始まります。改良された有機体複製機能。 生物学的および人工的なペアリング。NNACB/DNAの同期コーディングの強化。

The next breakthrough in WEAVEwearCB technology begins with version 7.3 of our patented WEAVEwearCB biosynthetic layering system. Improved organic body replication capabilities. Biological and artificial pairing. Enhanced synchronous coding for NNACB/DNA.

(Machine translation, human edited)

A5.6 Clones

A5.6.1 A Series

ひとつ上の次元の体験を求める人に生きる喜びを届けるために生まれた、第5世代Aシリーズ。もっと直感的に。感動のその先にある生き方を知る者の手で磨き上げられました。どんな挑戦にも応えられるように。いつでも、いかなる状況でも、最高のパフォーマンスを発揮します。爽快感だけでは終わらない新たな境地に達した瞬間には、思わず笑みがこぼれることでしょう。

Aシリーズは、そんな人生への扉を開いてくれます。夢に描いた自分になるために。未知の領域とかつてない体験が織り成す世界で生きるために。それを自分のものとするために。

あなたの人生を。あなたが理想とする生き方を。

最低限のニューラル保護機能の仕様:

-  UXDRIVE V9.14 ニューラルシンク

        - ND:0.0020%

        - EP:フルコレクトバンドルパッケージ  

        00.10.13.00RCYC2

        - CS: SYNCLOCKCB 3.1 SUSTAIN

A5.6.2 B Series

第5世代Bシリーズは、ただ美しいだけではありません。見て、感じて、生きてこそ体験できる五感に響きます。人生とは、快適さを追求することでより豊かになる。

特別な体験を実現したいという想いから、パワーと美を絶妙なバランスで融合させ、これまでにない暮らしのスタイルをお届けします。力強い体躯と爽快なパフォーマンスが、活気あふれるライフスタイルを後押しします。

最低限のニューラル保護機能の仕様:

-   UDRIVE V51.010 ニューラルシンク

        - ND: 0.0020%

        - EP:フルコレクトバンドルパッケージ

          00.12.47.00RCYCC

        - CS: SYNCLOCKCB 3.1 SUSTAIN

A5.6.3 C Series

Cシリーズのバイオマタは、過酷な作業を想定して作られており、どんなタスクにも対応することができます。多用途性を重視し、パワフルさと柔軟性を兼ね備えた耐久性の高いモデルです。

スチール強化を施したカーボンファイバー、生物学的に不活性なチタン素材、セラミック複合材により軽量化を実現するとともに、関節強度を向上させ、全体的な耐久性を高めることで、仕事でも遊びでも高い能力を発揮できるようになっています。

さらに、AシリーズとBシリーズに用意されている豊富なカスタマイズオプションを利用することで、あらゆるシーンで圧倒的な存在感を放つことができます。

最低限のニューラル保護機能の仕様:

- UDRIVE V47.367 ニューラルシンク

        - ND: 0.0022%

        - EP:フルコレクトバンドルパッケージ  

          00.33.12.00RCYC

        -   CS: SIGLOCKCB 24.2 REPEATER

A5.6.4 S Series

クローン技術はさらなる進化を遂げようとしています。 第5世代Sシリーズが、最終試験を終え、承認されました。運動学に基づく形状、パワーウエイトレシオ、重心位置などを徹底的に追求し、機能性と感動が集約された最新ヒューマンモデルが誕生しました。 心と体が一体となった動き。すべての動作は、あなたという存在の証明です。五感を開放して、すべてを体験しましょう。あなたを縛るものは何もありません。この身体は、あなたの身体です。 操作方法やバージョンアップの仕様、発売時期などの詳細は、今後の発表をお楽しみに。

A5.7 Leadership

A5.7.1 Seri Satō (Chief Technology Officer)

最高技術責任者

生年月日:2828年8月6日

遺伝学とヒューマンオーグメンテーションの分野における第一人者であり、セキグチジェネティクスを市場を代表する企業へと発展させることに寄与した数々の技術革新を先導。

持続可能なテクノロジーの活用を追求するとともに、革新的なSILKWORMCBセキュリティプロセスを開発し、人類のあり方を再定義したこの業界の先駆者として活躍を続けている。

受賞歴・略歴:

2879年 財団法人技術者協会 リーダーシップ賞
2885年 ノーブル工学アカデミー 国際フェロー
2857年5月 セキグチロボティクスに入社
2877年4月 WEAVEWORM
CBプロジェクト主査に就任
2879年8月 WEAVEWORM
CB事業本部長に就任
2881年6月 セキグチロボティクス企画本部長に就任
2882年8月 セキグチロボティクス開発本部長に就任 2884年3月:セキグチロボティクス企画グループ主任に就任
2884年8月 セキグチロボティクス最高情報責任者に就任
2885年1月 セキグチジェネティクス企画グループ本部長に就任
2885年3月 サステナビリティ推進本部長に就任
2885年6月 サステナビリティ最高責任者補佐に就任
2886年3月 サステイナビリティ最高責任者に就任
2886年5月 最高技術責任者補佐に就任
2888年6月 サステナビリティ推進部シニアフェローに就任
2888年4月 最高技術責任者に就任

最高技術責任者
佐藤世理

A5.7.2 Teiji Sano (Chief Executive Officer)

最高経営責任者

生年月日:2822年7月13日

2822年7月13日生まれ。2852年3月に新島根専門学校の応用物理学科を卒業、同年6月、セキグチロボティクス入社。2882年5月、セキグチロボティクスの研究・開発センターののシニアマネージャーに就任し、自らが中心となって、VACWORMCB自律型無人走行システムを開発。

2892年、セキグチジェネティクスの最高経営責任者に就任後、地球事業センターの取締役兼最高責任者として指揮を執る。

受賞歴・略歴:

2877年 IPMEブレイス・C・プロゼロー賞
2884年 ゴールデンクレスト賞
2846年6月:セキグチロボティクスに入社
2873年6月:技術管理部門シニアマネージャーに就任
2876年5月:研究・開発部門シニアマネージャーに就任
2878年4月:セキグチロボティクス上級役員に就任
2878年8月:セキグチロボティクス取締役に就任
2881年5月:技術戦略担当上級副社長に就任
2882年6月:監査役会理事に就任
2883年5月:経営戦略担当執行副社長に就任
2884年7月:セキグチロボティクス最高経営責任者に就任
2886年4月:セキグチジェネティクス最高経営責任者に就任

最高経営責任者
佐野帝司

A5.7.3 Kaito Iwasaki (Chief Strategy Officer)

最高戦略責任者

生年月日:2822年8月7日

最高戦略責任者として、セキグチグループの事業利益を守るために必要な提携関係の構築において極めて重要な役割を果たし、機密保持、競争力、業界最高水準の維持に尽力。

セキグチグループの損失防止部門と協力しながら、確固たる責任感のもと、顧客の製品の無断転売やオープンソースの改ざんの防止に取り組む。

受賞歴・略歴:

2850年6月:弁護士として登録
2850年8月:竹村・結城・高木法律事務所に入所
2860年4月:竹村・結城・高木法律事務所 パートナー就任
2879年3月:セキグチジェネティクス監査役に就任
2884年5月:セキグチジェネティクス最高戦略責任者に就任

最高戦略責任者
岩崎海斗

A5.7.4 Morio Sakamoto (Chief Financial Officer)

最高財務責任者

生年月日:2826年12月24日

30年以上にわたって民間および公共のテクノロジー企業で財務および経営に携わってきた、経験豊富な技術系エグゼクティブ。セキグチグループ入社以前は、トラクサス・インタープラネタリー社の事業部門において、さまざまな上級幹部財務職を歴任。

それ以前は、レーティコン重工、ピアレス・ソリューションズ、ゼロ・システムズ、オニシス機械工業など、複数の公共および民間企業に臨時最高財務責任者として勤務。また、アルファ・インタープラネタリー社の経営コンサルタントを務め、事業再生、株式公開、さらにはサーシスグループへの売却を成功に導いた。

株式会社TOOLの元取締役。一橋ICSで経済学の修士号を取得し、公認会計士試験に合格。

受賞歴・略歴:

2879年8月:セキグチジェネティクスに入社
2884年6月:研究・開発部門シニアマネージャーに就任
2885年5月:技術戦略担当上級副社長に就任
2885年8月:監査役会理事に就任
2886年8月:セキグチジェネティクス最高財務責任者に就任

最高財務責任者
坂本守

A5.7.5 Kaemon Hashimoto (Chief Information Officer)

最高情報責任者

生年月日:2823年4月1日

プロセスや手順の合理化を進めることでセキグチの成長を促し、ロボットおよびバイオマタ製造業界において最先端の地位を確保することに貢献。

現技術チームの中核的メンバーの多くを指導し、主要なプロセス、ワークフロー、自動化を拡大、WORKWORMCBの各クラスからバイオマタの各シリーズまで、製造工程のあらゆる面で高い生産性を実現。

2852年4月、化学工学、機械工学、応用物理学の複数の学位を取得し、セキグチ技術専門学校を卒業。

受賞歴・略歴:

2868年 ノーブル工学アカデミー 国際フェロー
2874年 名誉勲章(最高名誉賞)
2846年5月:セキグチロボティクスに入社
2878年4月:経営統括管理責任者に就任
2879年8月:セキグチロボティクス主任監査役に就任
2885年6月:セキグチジェネティクス主任監査役就任
2886年8月:監査役会理事に就任
2887年5月:セキグチジェネティクス最高戦略責任者に就任
2887年6月:セキグチジェネティクス最高情報責任者に就任

最高情報責任者
橋本嘉右衛門


A5.8 Disclaimer / Notice of Liability

法的責任に関する通知 セキグチジェネティクスのお客様は、以下の規約に同意するものとします。これらの規約は事前の予告なく変更される場合があります。お客様の責任において、常に最新版をご確認ください。1. 遺伝子工学に関わる免責事項 当社の製品またはサービスを購入または利用することにより、お客様は、遺伝子工学に起因する突然変異やその他の予期せぬ影響に対して、セキグチジェネティクスが責任を負わないことを認めるものとします。お客様は、そのような突然変異または予期せぬ影響から生じるいかなる損害、請求、または損失のすべてを補償し、当社に一切の損害を与えないことに同意するものとします。2. 知的財産権 セキグチジェネティクスは、特許、商標、著作権、企業秘密をはじめとする、その製品およびサービスに関するすべての知的財産権を保持します。お客様は、当社の書面による事前の同意なしに、当社の製品またはサービスの複製、変更、配布、またはリバースエンジニアリングを行うことはできません。3. ロボティクスに関わる免責事項 当社のロボット製品またはサービスを購入または利用することにより、お客様は、かかる製品またはサービスの操作または利用に起因するいかなる故障、傷害、または損害に対して、セキグチジェネティクスが責任を負わないことを認めるものとします。お客様は、そのような故障、傷害、または損害から生じるいかなる損害、請求、または損失のすべてを補償し、当社に一切の損害を与えないことに同意するものとします。4. データプライバシーポリシー 当社は、データプライバシーを重視し、お客様の同意なしに第三者に個人情報を開示することはありません。ただし、研究開発を目的とする場合は、匿名化されたデータを収集し使用する権利を留保します。5. 準拠法および紛争解決 本通知は、抵触法の規定にかかわらず、地球および火星の惑星をはじめとするUESCの法律に準拠するものとします。本通知に起因または関連する紛争は、宇宙仲裁機構を通じた仲裁によって解決されるものとします。当社の製品またはサービスを利用することにより、お客様は、この通知を読み理解し、その規約に従うことに同意したものとみなされます。これらの規約に同意されない場合は、当社の製品またはサービスのご利用をお控えください。

Trans: Liability Notice As a Sekiguchi Genetics customer, you agree to the following terms. These terms are subject to change without prior notice. It is your responsibility to always check for the latest version. 1. Genetic Engineering Disclaimer By purchasing or using our products or services, you assume that Sekiguchi Genetics is not responsible for mutations or other unforeseen effects resulting from genetic engineering. You acknowledge that You agree to indemnify and hold us harmless from any and all damages, claims or losses arising out of such mutations or unforeseen effects. 2. Intellectual Property Rights Sekiguchi Genetics retains all intellectual property rights relating to its products and services, including patents, trademarks, copyrights and trade secrets. You may not reproduce, modify, distribute, or reverse engineer any of our products or services without our prior written consent. 3. Robotics Disclaimer By purchasing or using our robotic products or services, you agree to indemnify Sekiguchi Genetics for any failure, injury, or damage arising out of the operation or use of such products or services. You accept no liability. You agree to indemnify and hold us harmless from any and all damages, claims or losses arising out of such failures, injuries or damages. 4. Data Privacy Policy We value data privacy and will not disclose personal information to third parties without your consent. However, we reserve the right to collect and use anonymized data for research and development purposes. 5. GOVERNING LAW AND DISPUTE RESOLUTION This Notice shall be governed by the laws of the UESC, including the planets of Earth and Mars, without regard to its conflict of law provisions. Any dispute arising out of or relating to this Notice shall be resolved by arbitration through the Space Arbitration Organization. BY USING OUR PRODUCTS OR SERVICES, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTAND THIS NOTICE AND AGREE TO BE BOUND BY ITS TERMS. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT USE OUR PRODUCTS OR SERVICES.