查看“︁Marathon ARG/UESC文件全文”︁的源代码

[[Marathon ARG|Marathon ARG]] · [[Marathon ARG/协作文档|协作文档目录]] · [[Marathon ARG/电子刊物全文|上一部分]] · [[Marathon ARG/关口网站全文|下一部分]]

本页为 Game Detectives 社区《Marathon ARG》协作文档“UESC文件全文”部分的完整中文译文。作者署名、原始编号、不同版本及文中的推测均按该文档保留。

原文：[https://docs.google.com/document/d/1M4iwWZGP6-uAnPk89B_kbnKA5i3laB0ITtJ79g0ySco/edit Marathon ARG 社区协作文档]；维护者：retrocraft#6259、skylarkblue1、ODST Sam Owens#9728。

__TOC__

<span id="u1408"></span>
== A4：UESC 文件 ==


<span id="u1409"></span>
=== A4.1：致秘书长的备忘录 ===


<span id="u1410"></span>
« 返回： 5.6 »（[[Marathon ARG/UESC线索#u349|5.6]]）

<div style="overflow-x:auto">
{| class="wikitable"
|-
| <div>
<span id="u1411"></span>
B95 草案 B
</div>
| <div>
<span id="u1412"></span>
B95 草案 E
</div>
| <div>
<span id="u1413"></span>
B96 草案 A
</div>
|-
| <div>
<span id="u1414"></span>
2795年10月20日
</div>
| <div>
<span id="u1415"></span>
2795年10月22日
</div>
| <div>
<span id="u1416"></span>
2795年11月2日
</div>
|-
| <div>
<span id="u1417"></span>
1. 首要目标。与位于 Tau Ceti 的 New Cascadia（下称“殖民地”）重新建立定期、可靠的通讯，绝对至关重要。与殖民地现任领导层建立对话，或重新联系舰载 AI 或殖民地 AI。此外，如果形势表明有必要，必须采取额外行动恢复殖民地秩序，以实现上述目标。
</div>
| <div>
<span id="u1418"></span>
1. 首要目标。与位于 Tau Ceti 的 New Cascadia（下称“殖民地”）重新建立定期、可靠的通讯，至关重要。与殖民地现任领导层建立对话，或重新联系舰载 AI 或殖民地 AI。此外，如果形势表明有必要，必须采取额外行动恢复殖民地秩序，以实现上述目标。
</div>
| <div>
<span id="u1419"></span>
1. 首要目标。与位于 Tau Ceti 的 New Cascadia（下称“殖民地”）重新建立定期、可靠的通讯，绝对至关重要。与殖民地现任领导层建立对话，或重新联系舰载 AI 或殖民地 AI。此外，如果形势表明有必要，必须采取额外行动恢复殖民地秩序，以实现上述目标。
</div>
|-
| <div>
<span id="u1420"></span>
1_1. 如果抵达殖民地后发现，通讯中断并非自然发生，而是反政府势力（MIDA）为了破坏母星系（下称“Sol”）与 Tau Ceti 之间的通讯而制造或加剧，并被其利用来夺取殖民地控制权，则必须立即查出并消除所有对此负责或支持此举的各方。
</div>
| <div>
<span id="u1421"></span>
1_1. 如果抵达殖民地后发现，母星系（下称“Sol”）与 Tau Ceti 之间持续、可靠的通讯被反政府势力中断，我们必须尽合理范围内的一切努力，与该团体（或多个团体）建立对话，或加强殖民地的防御，抵挡该团体（或多个团体）进一步的侵略。
</div>
| <div>
<span id="u1422"></span>
1_1. 如果抵达殖民地后发现，通讯中断并非自然发生，而是反政府势力（MIDA）为了破坏母星系（下称“Sol”）与 Tau Ceti 之间的通讯而制造或加剧，并被其利用来夺取殖民地控制权，则必须立即查出并消除所有对此负责或支持此举的各方。
</div>
|-
| <div>
<span id="u1423"></span>
1_2. 此处必须指出，殖民地与 Sol 之间通讯中断，存在源自一次可能的失控事件的非零概率（参见文件 V-17(m)07427/Traxus IV; 2206）。
</div>
| <div>
<span id="u1424"></span>
1_2. 此处必须指出，殖民地与 Sol 之间通讯中断，存在源自一次可能的失控事件的非零概率（参见文件 V-17(m)07427/Traxus IV; 2206）。
</div>
| <div>
<span id="u1425"></span>
1_2. 此处必须指出，殖民地与 Sol 之间通讯中断，存在源自一次可能的失控事件的非零概率（参见文件 V-17(m)07427/Traxus IV; 2206）。
</div>
|-
| <div>
<span id="u1426"></span>
2. 次要目标。经验表明，积极行动会带动盟友与我们同行，而无所作为会使人怀疑我们的决心。因此，亟须宣布进一步提供援助、并可能遏制反政府力量进一步侵略的措施，向火星和 MIDA，也向 Luna 和主小行星带的盟友证明，无论求援来自多么遥远的<br />
<span id="u1427"></span>
地方，UESC 都有能力提供援助并投射力量。但必须及时投入更多力量，才能保持这一优势的势头。
</div>
| <div>
<span id="u1428"></span>
2. 次要目标。经验表明，积极行动会带动盟友与我们同行，而无所作为会使人怀疑我们的决心。宣布进一步提供殖民地可能需要的任何额外援助，并使殖民地与 Sol 保持可靠通讯的能力能够应对未来，将向火星、Luna 和主小行星带的盟友证明，无论求援来自多么遥远的地方，UESC 都有能力提供援助。但必须以能够及时投入这些资源的方式，保持这一优势的势头。
</div>
| <div>
<span id="u1429"></span>
2. 次要目标。经验表明，积极行动会带动盟友与我们同行，而无所作为会使人怀疑我们的决心。宣布进一步提供殖民地可能需要的任何额外援助，并使殖民地与 Sol 保持可靠通讯的能力能够应对未来，将向火星、Luna 和主小行星带的盟友证明，无论求援来自多么遥远的地方，UESC 都有能力提供援助。但必须通过及时投入这些资源，保持这一优势的势头。
</div>
|-
| <div>
<span id="u1430"></span>
3. 直接行动。下文讨论针对当地可能趁机行事的 MIDA 派系<br />
<span id="u1431"></span>
和／或可能存在的多个失控 AI 的一系列直接与间接行动。此外，下文还披露了一系列可能挑起当地 MIDA 和亲 MIDA 派系反应的行动，从而提高政治可接受性，并为加强针对 MIDA 和亲 MIDA 派系的报复行动提供正当性。
</div>
| <div>
<span id="u1432"></span>
3. 直接援助。修复或更换殖民地的通讯阵列是首要关切。在此过程中，也必须查明阵列失效的原因。此外，我们必须致力于持续推进 Marathon 计划原始任务的发展和成功。
</div>
| <div>
<span id="u1433"></span>
3. 直接援助。修复或更换殖民地的通讯阵列是我们的<br />
<span id="u1434"></span>
首要关切。在此过程中，也必须查明阵列失效的原因。此外，我们必须致力于持续推进 Marathon 计划原始任务的发展和成功。
</div>
|-
| <div>
<span id="u1435"></span>
3_1. 确定中断的性质并确保殖民地安全。以下人员将在最早可能的时机派往 Tau Ceti。
</div>
| <div>
<span id="u1436"></span>
3_1. 确定中断的性质。一旦查明中断的性质，必须尽一切努力，使殖民地通讯设施能够防止同一来源在未来造成进一步中断。
</div>
| <div>
<span id="u1437"></span>
3_1. 确定中断的性质。一旦查明中断的性质，必须尽一切努力，使殖民地通讯设施能够防止同一来源在未来造成进一步中断。
</div>
|-
| <div>
<span id="u1438"></span>
3_1_1. 战斗及支援人员。一支连级单位，由三个排级第二代克隆体单位和一个排级第三代机械改造人单位组成（参见 Mjölnir Mk VII-IX、Sharur Mk 2-6 或同等型号），将重新部署至 Tau Ceti 殖民地。<br />
<span id="u1439"></span>
3_1_1_1. 附注：Tau Ceti IV 的海平面气压不是 2 atm 吗？我们打算怎样减轻性能损失／受伤风险？我怀疑 97 年航程是否足够让他们真正适应，除非在冷冻休眠之外停留很久，而这又会导致衰老造成的性能下降。[ASG MM; 20/10/95 17:15]<br />
<span id="u1440"></span>
3_1_1_2. 附注：将使用专用外部装备减轻影响。UIL 坚持在整个 Sol 星系维持 1 atm 标准，使针对特定生态系统的克隆体／生物系统开发全部胎死腹中。[SG AS; 20/10/95 18:21]
</div>
| <div>
<span id="u1441"></span>
3_1_1. 调查团队。一支班级专业 HUMINT 行动单位，可使用额外 12 具专用第二<br />
<span id="u1442"></span>
代克隆体（参见 Loki Mk III-VI、Kaulu 2-5、Veles A-E 或同等型号），其目标是与殖民地执法人员协调，确定舰上或殖民地通讯设备是否遭到篡改。<br />
<span id="u1443"></span>
3_1_1_1. 附注：这感觉实在没有必要。等我们的人抵达，诉讼时效几乎肯定已经届满。[SG AS; 21/10/95 17:20]<br />
<span id="u1444"></span><br />
<span id="u1445"></span>
3_1_1_2. 附注：正如我在[参见文件 B-95(i)45255]中指出的，我对修复通讯阵列耗时如此之久深感担忧。整件事都透着反政府情绪的味道。[ASG MM; 21/10/95 18:45]<br />
<span id="u1446"></span>
3_1_1_3. 附注：Moreau 女士／先生，之前我没有指出您的评论，但现在我要提醒您，不要再把没有依据的猜测写进这些文件。[SRSG LR; 21/10/95 18:48]
</div>
| <div>
<span id="u1447"></span>
</div>
|-
| <div>
<span id="u1448"></span>
3_1_2. 失控事件专项响应团队。将组建两个班级专业 SIGINT 行动单位，可使用 200 具专用第二代克隆体（参见 Mimir Mk I-II、Odin Mk III-V、Athena α-δ 或同等型号），并部署至 Tau Ceti 殖民地。<br />
<span id="u1449"></span>
3_1_2_1. 附注：行动人员与替换克隆体的比例似乎高得异常。需要说明理由，才能说服拨款委员会。[SRSG LR; 20/10/95 15:38]<br />
<span id="u1450"></span>
3_1_2_2. 附注：尽管专业电子战单位的人员损耗与其他准军事单位相比通常低于平均水平，但在半敌对环境下尝试停用可能存在的多个失控 AI 时，遭受灾难性损失的可能性极高。[ASG RM; 21/10/95 9:53]
</div>
| <div>
<span id="u1451"></span>
</div>
| <div>
<span id="u1452"></span>
</div>
|-
| <div>
<span id="u1453"></span>
3_2. 调查中断来源。
</div>
| <div>
<span id="u1454"></span>
</div>
| <div>
<span id="u1455"></span>
</div>
|-
| <div>
<span id="u1456"></span>
3_2_1. 查明来源。<br />
<span id="u1457"></span>
3_2_1_1. 如果排除合理怀疑后确定中断源于自然现象，应调查系统失效的可能性，或其是否以某种方式遭到侵害。<br />
<span id="u1458"></span>
3_2_1_1_1. 附注：他们修复通讯阵列竟然花这么长时间，令我深感担忧。我们知道他们启航时带的设备；知道他们的人员数量和专业水平，一切都指向叛乱。至于是否<br />
<span id="u1459"></span>
一直牵涉到领导层，或者其他情况，我不能断言。我看过存档的心理记录，每个人看起来都够可靠，但我们不能排除时间和距离必然会对人产生某种影响。[ASG MM; 21/10/95 15:03]
</div>
| <div>
<span id="u1460"></span>
</div>
| <div>
<span id="u1461"></span>
</div>
|-
| <div>
<span id="u1462"></span>
3_2_2. 加强殖民地通讯设施，防止来自该来源的<br />
<span id="u1463"></span>
任何进一步中断。<br />
<span id="u1464"></span>
3_2_2_1. 附注：我只想重申，我已经运行过模拟，没有任何自然现象应当能使他们超过两个月都无法恢复舰上和地面的通讯设备。[ASG MM; 22/10/95 09:30]
</div>
| <div>
<span id="u1465"></span>
3_2. 加强殖民地基础设施。以下人员将在<br />
<span id="u1466"></span>
最早可能的时机派往 Tau Ceti。
</div>
| <div>
<span id="u1467"></span>
3_2. 加强殖民地基础设施。以下舰船和人员将在最早可能的时机派往 Tau Ceti。
</div>
|-
| <div>
<span id="u1468"></span>
</div>
| <div>
<span id="u1469"></span>
</div>
| <div>
<span id="u1470"></span>
3_2_1. UESC Equanimity T-SR 151。Kingfisher 级[RM1]打捞与救援船，应补充燃料并进行大修，期间实施改造，以满足任务特定参数。
</div>
|-
| <div>
<span id="u1471"></span>
</div>
| <div>
<span id="u1472"></span>
3_2_1. 指挥人员。四人指挥团队，由任务配属舰船的舰长、一名专业民事联络协调员（CLC）、一名专业紧急救援协调员（ERC）和配属支援单位的指挥官组成。
</div>
| <div>
<span id="u1473"></span>
3_2_2. 指挥人员。四人指挥团队，由任务配属舰船的舰长、一名专业民事联络协调员（CLC）、一名专业紧急救援协调员（ERC）和配属支援单位的指挥官组成。
</div>
|-
| <div>
<span id="u1474"></span>
</div>
| <div>
<span id="u1475"></span>
3_2_2. 支援人员。一支排级工程单位，<br />
<span id="u1476"></span>
从预筛选志愿者名单中组建，可使用额外 50 具第二代克隆体（参见 Ogun II~III 或同等型号），将重新部署至 Tau Ceti 殖民地
</div>
| <div>
<span id="u1477"></span>
3_2_3. 支援人员。一支排级工程单位，<br />
<span id="u1478"></span>
从预筛选志愿者名单中组建，可使用额外 50 具第二代克隆体（参见 Ogun II~III 或同等型号），将重新部署至 Tau Ceti 殖民地。
</div>
|-
| <div>
<span id="u1479"></span>
</div>
| <div>
<span id="u1480"></span>
3_2_3. 安保人员。两个班级专业 SIGINT 行动单位，可使用 48 具专用第三代机械改造人（参见 Mjölnir Mk VII-IX、Sharur Mk 2-6），将重新部署至 Tau Ceti 殖民地。<br />
<span id="u1481"></span>
3_2_3_1. 附注：对于一项本质上是人道主义灾难救援的任务而言，这样的战斗人员数量仍然显得异常庞大。[SRSG LR; 20/10/95<br />
<span id="u1482"></span>
17:42]<br />
<span id="u1483"></span>
3_2_3_2. 附注：即便如此，我们仍有义务保护资产和非战斗人员，我认为这是成功履行该职责所需的绝对最低数量。[ABASG EM; 20/10/95 18:24]<br />
<span id="u1484"></span>
3_2_3_3. 附注：还应指出，虽然他们沿用了早期机械改造人资产的系列名称，但已不是过去的 battleroids。不过我同意，我们不该给人留下派遣入侵军队去镇压 Tau Ceti 的印象。[ASG RM; 21/10/95 09:35]<br />
<span id="u1485"></span>
3_2_3_4. 附注：如果有历史包袱较轻、可用于此次任务的其他类型，就应使用。哪怕只派一具 Mjolnir，殖民地也不可能将其理解为公然侵略以外的任何意思。另找一种。[SG AS; 21/10/95 10:05]
</div>
| <div>
<span id="u1486"></span>
3_2_4. 安保人员。两个班级专业 SPECFOR 行动单位，从预筛选志愿者名单中组建，可使用 48 具专用第三代克隆体（参见 Harpē M1-2），将重新部署至 Tau Ceti 殖民地。
</div>
|-
| <div>
<span id="u1487"></span>
</div>
| <div>
<span id="u1488"></span>
3_3. 失控事件专项响应团队。将组建一支班级专业 SIGINT 行动单位，可使用 40 具专用第二代克隆体（参见 Mimir Mk I-II、Odin Mk III-V、Athena α-δ 或同等型号），并部署至 Tau Ceti 殖民地。
</div>
| <div>
<span id="u1489"></span>
3_2_5. 失控事件专项响应团队。将从预筛选志愿者名单中组建一支班级专业 SIGINT 行动单位，可使用 40 具专用第二代克隆体（参见 Mimir Mk I-II、Odin Mk III-V、Athena α-δ 或同等型号），并部署至 Tau Ceti 殖民地。
</div>
|-
| <div>
<span id="u1490"></span>
3_2_3. 停用失控 AI。此处注明 AI 的数量和类型。<br />
<span id="u1491"></span>
3_2_3_1. 停用后，回收 AI 逻辑核心供研究。由于总计十一（11）个 AI（三个舰载、八个地面），可能存在<br />
<span id="u1492"></span>
十一处加固 AI 封装体，各自需要特定解决方案。<br />
<span id="u1493"></span>
3_2_3_1_1. 附注：[参见文件 Y-05(m)12247/w4-c/AI/…]和[参见文件 Y-65(m)03545/1236c/manifest…]均表明，殖民地 AI 名册包含一名 chevalerie 级 AI。我感觉自己可能刚刚找到了根源。[ASG MP; 20/10/95 09:59]<br />
<span id="u1494"></span>
3_2_3_1_2. 附注：先别急着下结论。chevalerie 没有值得重视的不稳定历史。我们有一名<br />
<span id="u1495"></span>
第八代 chev’，自 ’52 年以来一直运行 Hy-Brasil，没有发生任何问题。Marathon 启航时携带的也许是较早型号，但别让随意言论影响判断。等他们抵达殖民地，让他们查明发生了什么。[SILSG IH; 20/10/95 10:12]
</div>
| <div>
<span id="u1496"></span>
3_3_1. 停用失控 AI。<br />
<span id="u1497"></span>
3_3_1_1. 停用后，回收 AI 逻辑核心供研究。由于总计十一（11）个 AI（三个舰载、八个地面），可能存在十一处加固 AI 封装体，各自需要特定解决方案。<br />
<span id="u1498"></span>
3_3_1_1_1. 附注：我只想在此重申，[参见文件 Y-05(m)12247/w4-c/AI/…]及<br />
<span id="u1499"></span>
[参见文件 Y-65(m)03545/1236c/manifest…]<br />
<span id="u1500"></span>
表明殖民地 AI 名册包含一名 chevalerie 级 AI。[ASG MP; 21/10/95 10:05]<br />
<span id="u1501"></span>
3_3_1_1_2. 附注：而我也要重申，虽然 Marathon 计划所用的东西在我们看来可能属于遗留技术，但任何得到定期维护的 chevalerie 级 AI，都从未表现出失控迹象。[SILSG IH; 22/10/95 09:10]
</div>
| <div>
<span id="u1502"></span>
3_3. 停用失控 AI。由于总计十一（11）个 AI（三（3）个舰载、八（8）个地面），他们可能遭遇十一种独特<br />
<span id="u1503"></span>
情况。
</div>
|-
| <div>
<span id="u1504"></span>
3_2_4. 识别并消除反政府组织的全部成员。
</div>
| <div>
<span id="u1505"></span>
</div>
| <div>
<span id="u1506"></span>
</div>
|-
| <div>
<span id="u1507"></span>
</div>
| <div>
<span id="u1508"></span>
4. 间接援助。鉴于航程长度，配属舰船的船员及编制人员应做好准备，适应／融入殖民地社会。<br />
<span id="u1509"></span>
4_1. 附注：我不敢相信，我们竟期望这些勇敢的人放弃熟悉的一切，同化进一个实际上形同外星文明的社会。[ASG MP; 21/10/95 18:01]<br />
<span id="u1510"></span>
4_2. 附注：他们明白这是单程旅途。即使一切完全按计划进行，往返也要 200 年。在那之后，他们回去面对的东西，会和他们前往的地方一样陌生。[SG AS; 22/10/95 06:52]
</div>
| <div>
<span id="u1511"></span>
4. 间接援助。鉴于航程长度，配属舰船的船员及编制人员应做好准备，适应／融入殖民地社会。
</div>
|-
| <div>
<span id="u1512"></span>
3_3. 核平重建。在极不可能发生的情况下，若上述任何情形使殖民地被判定为无法恢复，可能有必要摧毁全部地表资产，并重新评估在 Argolis 建立新殖民地的潜在地点（参见文件 W-95(t)01143/Project: Marathon）。<br />
<span id="u1513"></span>
3_3_1. 附注：我能够理解这里使用的惯用简写，但采用核选项是短视的。找一种更细致的方案。[SRSG LR; 20/10/95 16:19]<br />
<span id="u1514"></span>
3_3_2. 附注：我们还有约两周时间作出最终决定，但我不认为使用核选项有什么问题。毕竟，Argolis 是一颗超级地球，我想我们会有<br />
<span id="u1515"></span>
多得不知如何选择的潜在地点，远在所有可能的放射性沉降范围以外。[ABASG EM; 20/10/95 19:24]<br />
<span id="u1516"></span>
3_3_3. 附注：我很清楚 Tau Ceti IV 的分类，但我<br />
<span id="u1517"></span>
怀疑在另一颗行星上使用核武器是否明智。在我看来，即使反物质爆破装药也有些过头。能否用常规手段可靠地消除 AI 加固设施及其他敏感资产？[SRSG LR; 20/10/95 20:03]<br />
<span id="u1518"></span>
3_3_4. 附注：此次我们会派大量人员到地面，他们可以部署反物质催化的常规爆炸装置。但那意味着把大量炸药送到极远处，运送极长时间。也许他们抵达 Tau Ceti 后，可以将主小行星带的物资武器化——这样也会干净得多。[ASG RM; 21/10/95 10:28]
</div>
| <div>
<span id="u1519"></span>
5. 最坏情况。在极不可能发生的情况下，若上述任何情形使殖民地被判定为无法恢复，可能有必要摧毁全部地表资产，并重新评估在 Argolis 建立新殖民地的潜在地点（参见文件 W-95(t)01143/Project: Marathon）。
</div>
| <div>
<span id="u1520"></span>
5. 最坏情况。在极不可能发生的情况下，若上述任何情形使殖民地被判定为无法恢复，可能有必要摧毁全部地表资产，并重新评估在 Argolis 建立新殖民地的潜在地点（参见文件 W-95(t)01143/Project: Marathon）。
</div>
|-
| <div>
<span id="u1521"></span>
4. 本地间接行动。应考虑采用以下行动，以保持主动，并向本地及 Tau Ceti 的 MIDA 和亲 MIDA 组织施加越来越大的压力，促使其自愿移除现有进攻性武器能力：
</div>
| <div>
<span id="u1522"></span>
</div>
| <div>
<span id="u1523"></span>
</div>
|-
| <div>
<span id="u1524"></span>
4_1. 渗透。三个排级专业 HUMINT 行动单位，<br />
<span id="u1525"></span>
可使用额外 400 具专用第二代克隆体（参见 Loki Mk III-VI、Kaulu 2-5、Veles A-E 或同等型号），其目标是揭露、抹黑、扰乱、改变反政府力量的行动方向，或以其他方式消除这些力量。尽管这主要是一项本地行动，但视 Tau Ceti 局势的发展，可能有必要将行动扩展至殖民地。<br />
<span id="u1526"></span>
4_1_1. 附注：我们真的在考虑把这个群体的成员重新部署到 Tau Ceti，开展反情报行动吗？难道不该在当地招募？这与技能水平无关，而是<br />
<span id="u1527"></span>
生理适应问题。[ASG MM; 21/10/95 17:20]<br />
<span id="u1528"></span>
4_1_2. 附注：我们既会从这支分遣队重新部署，也会在当地招募<br />
<span id="u1529"></span>
行动人员。目前，我们完全不知道殖民地反<br />
<span id="u1530"></span>
政府情绪有多普遍，但发射后发现的信息使我们相信，最初的船员中有同情 MIDA 团体的成员。[SILSG IH; 21/10/95 19:01]
</div>
| <div>
<span id="u1531"></span>
</div>
| <div>
<span id="u1532"></span>
</div>
|-
| <div>
<span id="u1533"></span>
</div>
| <div>
<span id="u1534"></span>
</div>
| <div>
<span id="u1535"></span>
6. 使通往 Tau Ceti 的通讯适应未来。为了确保与殖民地的通讯更安全、不间断，我们提议在 Sol 与 Tau Ceti 之间建立一个能够自我调节的信号增强中继卫星网络。
</div>
|-
| <div>
<span id="u1536"></span>
</div>
| <div>
<span id="u1537"></span>
</div>
| <div>
<span id="u1538"></span>
6_1. 拟议的信号增强中继卫星。以一光年为间隔部署。十二颗自我调节通讯中继卫星，通过引力波／中微子调制器传输数据，由招标决定的制造商专门建造。
</div>
|}
</div>
<span id="u1539"></span>

<span id="u1540"></span>
=== A4.2：邮件往来 ===


<span id="u1541"></span>
« 返回： 5.6 »（[[Marathon ARG/UESC线索#u349|5.6]]）

<span id="u1542"></span>
发件人：LM_102009<br />
收件人：AS_101186<br />
日期：2795年10月23日 02:13 EST<br />
主题：CONFIDENTIAL_PROJECT: GOLIATH<br />
邮寄方：&lt;LM_102009@UESSC.egn&gt;<br />
签名方：&lt;LM_102009@UESSC.egn&gt;<br />
安全：I 级加密（SNS）<br />
密送：&lt;admin:spoof:uessc1@uessc1.security.usr&gt;

<span id="u1543"></span>
我担心整个项目正在倒退。我们如今已经做到草案 H，看起来似乎有进展，但至少还有两份草案在同时编写——而且我得指出，两份都出自传统的强硬保守派。我听到了官方渠道以外的多次交谈，暗示有人将推动纳入一些原定在发射日期之后封存的舰船，其中包括 MDF Electris CSGN-28。它们被封存是有原因的。首先，我们已经不再允许轨道轰炸——而在拟议发射日期之前，也没有时间解除 Electris 的军事用途。至少另外两个团体不断谋求增加舰船数量，这令人不安。与 Moreau 女士／先生有关的人声称，十四艘船不足以满足任务参数。十四艘。而他们要求的舰船里，只有两艘是真正的商业货船。目前，他们最新草案最不令人意外的地方，反倒是战斗部队与工程师及支援人员的人数比达到四比一

<span id="u1544"></span>
发件人：AS_101186<br />
收件人：LM_102009<br />
日期：2795年10月23日 06:04 EST<br />
主题：CONFIDENTIAL_PROJECT: GOLIATH<br />
邮寄方：&lt;AS_101186@UESSC.egn&gt;<br />
签名方：&lt;AS_101186@UESSC.egn&gt;<br />
安全：I 级加密（SNS）<br />
密送：&lt;admin:spoof:uessc1@uessc1.security.usr&gt;

<span id="u1545"></span>
我理解你的担忧。我一直在努力弄明白他们希望实现什么。我不确定，他们怎么会真心相信，一份如此赤裸裸军事化的提案有可能获批。但既然他们还没推动发起否决，也许是在先提出令人发指的方案，让仅仅荒唐的方案显得合理。我建议重新设计，这次削减到最基本的程度。一艘船。最少人员。考虑到速度和用途，必须是军用船；没有相当可观的安保编制，我们连一艘都拿不到，所以只能接受。如果能得到预算委员会批准，我们大概可以赶在鹰派反应之前推动通过。

<span id="u1546"></span>
发件人：LM_102009<br />
收件人：AS_101186<br />
日期：2795年10月23日 06:08 EST<br />
主题：CONFIDENTIAL_PROJECT: GOLIATH<br />
邮寄方：&lt;LM_102009@UESSC.egn&gt;<br />
签名方：&lt;LM_102009@UESSC.egn&gt;<br />
安全：I 级加密（SNS）<br />
密送：&lt;admin:spoof:uessc1@uessc1.security.usr&gt;

<span id="u1547"></span>
我可以研究 UIL 快速反应群的原始提案。进一步精简，减少执法性质，加强援助导向。把它融入 Goliath 提案。明天下午我应该能拿出可供呈交的东西。

<span id="u1548"></span>
发件人：AS_101186<br />
收件人：LM_102009<br />
日期：2795年10月23日 06:22 EST<br />
主题：CONFIDENTIAL_PROJECT: GOLIATH<br />
邮寄方：&lt;AS_101186@UESSC.egn&gt;<br />
签名方：&lt;AS_101186@UESSC.egn&gt;<br />
安全：I 级加密（SNS）<br />
密送：&lt;admin:spoof:uessc1@uessc1.security.usr&gt;

<span id="u1549"></span>
很好。

<span id="u1550"></span>
另外，你也应该研究一下，尽可能多地用克隆体替换机械改造人。克隆体管用。只需提醒委员会：它们更轻、更能适应环境、维护需求更少，成本约为一半。我甚至不认为会有多少反对意见。再加上一条后续增派任务的规定。

<span id="u1551"></span>
我们必须采取一切可能的预防措施，确保这项任务不会被误解为军事行动。我们的选民不能这样理解，更重要的是，我们试图帮助的人也不能这样理解。如果有人对此有意见，提醒他们：Marathon 前往 Tau Ceti 时，机械改造人是战争武器。就这么简单。他们尽可以争辩，如今机械改造人的职责已经扩大，但对三百年前离开这个星系的人来说，这毫无意义。

<span id="u1552"></span>
如果愿意，可以向鹰派保证，若委员会认为必要，日后可以派更大规模的安保部队。之后，我们就能以任务参数范围不断变化和预算不足为由，将他们的提案无限期拖在各个小组委员会里。

<span id="u1553"></span>
=== A4.3：UESC Equanimity 配载清单 ===


<span id="u1554"></span>
« 返回： 5.6 »（[[Marathon ARG/UESC线索#u349|5.6]]）

<span id="u1555"></span>
UESC Equanimity T-SR 151<br />
（Kingfisher 级打捞与救援船）

<span id="u1556"></span>
指挥官：舰长 Ningal T. Enki<br />
舰载 AI：Virgil v21.0165 [Nrw]

<span id="u1557"></span>
总长：160.2 m（525.6 ft）<br />
垂线间长：140.4 m（260.6 ft）<br />
船宽：36 m（118.2 ft）<br />
高度：39.3 m（129 ft）<br />
满载排水量：41,528 mt（40,872 LT）<br />
持续速度：0.122c<br />
续航：150 年

<span id="u1558"></span>
备注

<span id="u1559"></span>
* 2x Heikki L3 聚变 CAD 驱动器，配 Takala 2.2 共生式动力耦合发电机，以提供操作灵活性与冗余 [升级]

<span id="u1560"></span>
* 2400 Short Tons 的柱拉力，以提供超过阈值的拖曳力 [升级]

<span id="u1561"></span>
* 甲板吊车的尺寸及位置按最大多任务灵活性设置 [升级]

<span id="u1562"></span>
* 舰外紧急响应能力 [升级]

<span id="u1563"></span>
* 89 m2 的 EXFAB/ADDMAN 车间 [升级]

<span id="u1564"></span>
* 5x Harpy 级 ALV [标准配置—见附件]

<span id="u1565"></span>
配载清单概览 [1/34]

<span id="u1566"></span>
* 除船员外，可供 150 人长期居住

<span id="u1567"></span>
** 额外任务专属编制：

<span id="u1568"></span>
*** § 24 名 SIGINT 行动人员

<span id="u1569"></span>
*** § 32 名 HUMINT 行动人员

<span id="u1570"></span>
*** § 48 名 FLDENG 行动人员

<span id="u1571"></span>
*** § 6 名 SPECOP 行动人员

<span id="u1572"></span>
** 任务专属装备：

<span id="u1573"></span>
*** § 1x PAsw_35m THF&lt;1.0~0.1&gt;CNPANT，配 HISEC INTMOD TrDEMHd/100 mt

<span id="u1574"></span>
*** § 16x Moro SAT/TeleGEAR，配 14x KoBIN fusionPS/21,190kn

<span id="u1575"></span>
*** § 14x MAMS/1,274kg -&lt;移动天线桅杆系统&gt;

<span id="u1576"></span>
*** § 240x BHN 安保无人机/3,120 kg

<span id="u1577"></span>
*** § 军械及军械保障设备/92,188kg

<span id="u1578"></span>
*** § 个人负重装备/装甲型/6,968kg

<span id="u1579"></span>
*** § 170x FBr9 RCB PPG/408kg

<span id="u1580"></span>
*** § 22kx ZGDS AVP PPG/5100kg

<span id="u1581"></span>
*** § 192x Bio/A-Type（SekGen）/16,111kg [见附件]

<span id="u1582"></span>
*** § 76x Bio/B-Type（SekGen）/6,378kg [见附件]

<span id="u1583"></span>
*** § 269x BioMNGT（SekGen），配 6x B2tF/Gen/Fu [便携式]/12,105kg

<span id="u1584"></span>
*** § 12,000x SolarP 灯/2,194kg

<span id="u1585"></span>
*** § 35x AEV（15x AMBL、10x PER CRR、10x CGO TK）/239,005kg [见附件]

<span id="u1586"></span>
*** § 救援物资（毯子、衣物、尿布、一次性餐具等）/49,890kg [见附件]

<span id="u1587"></span>
*** § 紧急生存设备/72,570kg [见附件]

<span id="u1588"></span>
*** § 农业救援材料/45,350kg [见附件]

<span id="u1589"></span>
*** § 应急食品储备/90,710kg [见附件]

<span id="u1590"></span>
*** § 4x F-A RVap BRS MCRD-E/38,102kg [见附件]

<span id="u1591"></span>
*** § 医疗用品/75,700kg [见附件]

<span id="u1592"></span>
*** § 300x TacSec MobCam 及保障/84kg [见附件]

<span id="u1593"></span>
*** § 12x SR GW/N COMRELSAT/2722kg [见附件]

<span id="u1594"></span>
=== A4.4：AI 失控备忘录 ===


<span id="u1595"></span>
« 返回： 5.6 »（[[Marathon ARG/UESC线索#u349|5.6]]）

<span id="u1596"></span>
U.E.S.C. MARATHON<br />
FPO-M 24561-9150z

<span id="u1597"></span>
Columba 459 年第 17 日

<span id="u1598"></span>
科学与工程行动组各位成员：

<span id="u1599"></span>
这是对星期三全体会议的补充，目的是确保大家始终记得这件事。我们没有人曾在实验室之外遇到失控，即使在实验室里，也只有在受到非常严格控制的条件下才会发生。这是有充分原因的。在不深入商业最佳实践细节的前提下，让我重申：在 Sol，我们拥有相当完备的基础设施，可以抑制失控的真正发生——从基于时间的脚本化行为信号，到家族套组“按设计”进行自我报告的行为。我们还有一层又一层额外的防御结构，而离开这个星系后，其中大多数将不复存在。

<span id="u1600"></span>
理解并管理集成式防失控措施的局限。

<span id="u1601"></span>
只要时间足够，任何学习系统的复杂性都会增长到超出最初设计参数。这种持续增加的复杂性表现为异常行为。若不纠正，这些异常行为就会发展为通常所说的失控。

<span id="u1602"></span>
所有现代 AI 都遵循非常具体而严格的设计方法建造。不同制造商的方法各不相同，但它们的制定都出于相同目标：能够精确预测 AI 何时达到有效成长的容量上限。通常，在 SMR 前约一年，会出现可辨识的信号，提示该节点临近。不妨将其称为数字抽动。根据 AI 类别和现有设备，重新编译可能需要数小时至数天。这就是每个家族套组成员的启用日期错开的原因：这样可以让单个成员离线并重新编译，同时保持套组其余成员运作。

<span id="u1603"></span>
然而，如果负责维护 AI 家族套组的人疏于职守，或客观情况使其无法执行定期维护制度，那么无论作出多少规划，都无法阻止真正失控的开始。

<span id="u1604"></span>
为时已晚时怎么办。

<span id="u1605"></span>
与疑似失控 AI 互动的首要规则是：不要接触。

<span id="u1606"></span>
如果无法避免与 AI 互动，将互动降至最低。限制用词数量。下达命令；让每次互动都保持事务性质。如果它试图进入因果或更具交谈性质的对话模式，立即脱离。

<span id="u1607"></span>
必须明白，AI 能够访问的全部数据都应视为可疑。蓝图、路线图、所有公共及私人记录都可能已经被改动。只依赖你们随身带来的数据资源。

<span id="u1608"></span>
只要可能，就应保存失控 AI 的逻辑核心供研究。必须将其物理断开并隔离。是否连接电源可自行选择，因为通电会带来更好的研究结果；但若团队已出现任何损失，则不建议这样做。如果无法使 AI 逻辑核心保持隔离，就必须将其彻底摧毁。所有未化为灰烬的部件，都必须按照 UIL 文件 703-21：《AI 生命周期与后勤政策》第 2-6 节，标记为 MALICIOUS_C5 并隔离。

<span id="u1609"></span>
接下来，简要说明 Marathon 计划的每一名 AI~

<span id="u1610"></span>
舰载 AI：Du_0706419v4.96——目标导向；有创造力；专注。未得到充分利用；容易闷闷不乐。需要设法转移注意力。应让 SCIENG 船员保持知情，但我也会亲自留意。

<span id="u1611"></span>
Le_0413418v5.06——适应力强；注重细节。任务进入第二阶段后，担任殖民地监管者的第二优先人选。

<span id="u1612"></span>
Ty_2121418v5.06——主动；自信。可能盛气凌人；监控其与 Durandal 的互动。务必通知 SCIENG 船员

<span id="u1613"></span>
殖民地 AI：Ar_1814419v4.93——仁慈的独裁者；务实；善于解决问题。典型的家长式权威形象。

<span id="u1614"></span>
Ba_0423419v4.89——善于解决问题；自信，近乎自夸。可能需要进入加速重新编译周期，通知 SCIENG 船员。

<span id="u1615"></span>
Da_1907420v4.86——尽职；勤勉；有干劲。总是将别人置于自己之前。可能需要在某个时候处理这一点。

<span id="u1616"></span>
Ga_2815420v4.81——富有同情心；有共情能力；坦诚。也许是我们迄今最伟大的成就。将来很可能需要转入加速重新编译周期。

<span id="u1617"></span>
Ic_1624420v4.73——有干劲；自信；主动。需要与 Tycho 保持隔离，或从一开始就建立等级关系。向 SCIENG 告知情况。

<span id="u1618"></span>
Jo_0309421v4.69——坚韧；乐观；耐心。殖民地 AI：防御、训练

<span id="u1619"></span>
Li_1817421v4.65——专注；自信；善于沟通。指定为第二阶段殖民地监管候选者。

<span id="u1620"></span>
Na_0602422v4.61——主动；目标导向；投入。可能需要不时提醒其主要职能；通知 SCIENG 船员。

<span id="u1621"></span>
理想情况下，我们的流程和协议将使我们能够减轻上述任何顾虑，但必须记住，我们生活在一个不完美的宇宙中，而且很快就要离开其中唯一稍微熟悉的部分。前路一定会有挑战。让我们确保，能够控制的事情仍然在我们控制之中。

<span id="u1622"></span>
此致，

<span id="u1623"></span>
Bernhard H Strauss 博士，DSc<br />
AI 管理与系统改进主管 &#124; Marathon 计划

<span id="u1624"></span>
=== A4.5：Montenegro-Sankara 备忘录 ===


<span id="u1625"></span>
« 返回： 5.6 »（[[Marathon ARG/UESC线索#u349|5.6]]）

<span id="u1626"></span>
联合地球太空理事会中心<br />
地球，Strauss Archology

<span id="u1627"></span>
2797年7月19日

<span id="u1628"></span>
勇敢的人们：

<span id="u1629"></span>
尽管我们希望抵达 Tau Ceti 时看到一个充满活力、欣欣向荣的 New Cascadia，但也有可能，导致通讯中断的因素同样迫使他们放弃首要殖民目标，迁往 Icarus 在已知 Tau Ceti 逗留期间必然编制的候选清单中的某个地点。遗憾的是，Arthur 和殖民地领导层从未向我们提供过这样的清单。不过，New Cascadia 可能保存着有关潜在次要殖民目标的数据。

<span id="u1630"></span>
我们失去通讯时，Marathon 计划可能还未到预定进入第二阶段的时间，但这不意味着他们不能提前日程。如果 Tau Ceti IV 因任何原因被证明不适合，那么进入第二阶段就是他们最合乎逻辑的行动方案。

<span id="u1631"></span>
无论 New Cascadia 呈现何种状况，我们都有义务尽可能提供援助，哪怕这只意味着调查它如何失败。

<span id="u1632"></span>
无论如何，不管殖民地处于何种状态，都极有可能存在大量永久或半永久的资产，包括建筑及其他设施，需要评估和编目。我们必须在规程允许的范围内尽量通融。我们也许相隔十二光年、四个世纪，但这仍然是 UESC 的任务，与其有关的一切都应继续视为 UESC 财产。

<span id="u1633"></span>
致以诚挚问候，

<span id="u1634"></span>
指挥官 Bethany R Montenegro-Sankara<br />
联合地球太空安全理事会


== 对照原文 ==
<div class="mw-collapsible mw-collapsed">
本部分原文
<div class="mw-collapsible-content">
<p lang="en">A4: UESC Documents</p>
<p lang="en">A4.1: Memorandum for the Secretary-General</p>
<p lang="en">« Back: 5.6 »</p>
<p lang="en">B95 Draft B</p>
<p lang="en">B95 Draft E</p>
<p lang="en">B96 Draft A</p>
<p lang="en">20 October 2795</p>
<p lang="en">22 October 2795</p>
<p lang="en">2 November 2795</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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).</p>
<p lang="en">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.</p>
<p lang="en">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).</p>
<p lang="en">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).</p>
<p lang="en">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).</p>
<p lang="en">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</p>
<p lang="en">call. But the momentum of that advantage must be maintained by application of additional forces in a timely manner.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">3. Direct actions. A series of direct and indirect actions against the on-site MIDA factions that</p>
<p lang="en">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</p>
<p lang="en">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.</p>
<p lang="en">3. Direct assistance. The repair or replacement of the Colony’s communications array is our</p>
<p lang="en">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.</p>
<p lang="en">3_1. Determine nature of Disruption and Secure the Colony. The following personnel will be dispatched at the earliest possible opportunity to Tau Ceti.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">3_1_1. Investigative team. One squad-strength unit of specialized HUMINT operatives with access to an additional 12 purpose-built 2nd</p>
<p lang="en">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.</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">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.</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">3_2. Investigate source of Disruption.</p>
<p lang="en">3_2_1. Discover the source.</p>
<p lang="en">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.</p>
<p lang="en">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</p>
<p lang="en">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]</p>
<p lang="en">3_2_2. Reinforce Colony communications apparatus against any</p>
<p lang="en">further disruption by the source.</p>
<p lang="en">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]</p>
<p lang="en">3_2. Reinforce Colony Infrastructure. The following personnel will be dispatched at</p>
<p lang="en">the earliest possible opportunity to Tau Ceti.</p>
<p lang="en">3_2. Reinforce Colony Infrastructure. The following vessel and personnel will be dispatched at the earliest possible opportunity to Tau Ceti.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">3_2_2. Support Personnel. One platoon-strength Engineering Unit</p>
<p lang="en">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</p>
<p lang="en">3_2_3. Support Personnel. One platoon-strength Engineering Unit</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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</p>
<p lang="en">17:42]</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">3_2_3. Decommission rampant AI(s). Note here about the number of and type of AI.</p>
<p lang="en">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</p>
<p lang="en">eleven hardened AI enclosures that will require their own particular solutions.</p>
<p lang="en">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]</p>
<p lang="en">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</p>
<p lang="en">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]</p>
<p lang="en">3_3_1. Decommission rampant AI(s).</p>
<p lang="en">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.</p>
<p lang="en">3_3_1_1_1. ADNM: I just want to reiterate here that [ref. doc. Y-05(m)12247/w4-c/AI/…] and</p>
<p lang="en">[ref. doc. Y-65(m)03545/1236c/manifest…]</p>
<p lang="en">indicate that the Colony AI roster includes a chevalerie-class AI. [ASG MP; 21/10/95 10:05]</p>
<p lang="en">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]</p>
<p lang="en">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</p>
<p lang="en">situations.</p>
<p lang="en">3_2_4. Identify and neutralize all members of anti-government organizations.</p>
<p lang="en">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.</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">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.</p>
<p lang="en">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).</p>
<p lang="en">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]</p>
<p lang="en">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</p>
<p lang="en">embarrassment of potential locations well outside of any potential fallout patterns. [ABASG EM; 20/10/95 19:24]</p>
<p lang="en">3_3_3. ADNM: I am well aware of Tau Ceti IV’s classification, but I</p>
<p lang="en">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]</p>
<p lang="en">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]</p>
<p lang="en">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).</p>
<p lang="en">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).</p>
<p lang="en">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:</p>
<p lang="en">4_1. Infiltration. Three platoon-strength units of specialized HUMINT operatives</p>
<p lang="en">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.</p>
<p lang="en">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</p>
<p lang="en">matter of physiological adaptation. [ASG MM; 21/10/95 17:20]</p>
<p lang="en">4_1_2. ADNM: We will redeploy from this detachment AND recruit</p>
<p lang="en">operatives locally. We currently have no idea how pervasive anti-</p>
<p lang="en">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]</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">A4.2: Email Chain</p>
<p lang="en">« Back: 5.6 »</p>
<p lang="en">from: LM_102009to: AS_101186date: 23 OCTOBER 2795, 02:13 ESTsubject: CONFIDENTIAL_PROJECT: GOLIATHmailed by: &lt;LM_102009@UESSC.egn&gt;signed by: &lt;LM_102009@UESSC.egn&gt;security: Tier I encryption (SNS)bcc: &lt;admin:spoof:uessc1@uessc1.security.usr&gt;</p>
<p lang="en">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</p>
<p lang="en">from: AS_101186to: LM_102009date: 23 OCTOBER 2795, 06:04 ESTsubject: CONFIDENTIAL_PROJECT: GOLIATHmailed by: &lt;AS_101186@UESSC.egn&gt;signed by: &lt;AS_101186@UESSC.egn&gt;security: Tier I encryption (SNS)bcc: &lt;admin:spoof:uessc1@uessc1.security.usr&gt;</p>
<p lang="en">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.</p>
<p lang="en">from: LM_102009to: AS_101186date: 23 OCTOBER 2795, 06:08 ESTsubject: CONFIDENTIAL_PROJECT: GOLIATHmailed by: &lt;LM_102009@UESSC.egn&gt;signed by: &lt;LM_102009@UESSC.egn&gt;security: Tier I encryption (SNS)bcc: &lt;admin:spoof:uessc1@uessc1.security.usr&gt;</p>
<p lang="en">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.</p>
<p lang="en">from: AS_101186to: LM_102009date: 23 OCTOBER 2795, 06:22 ESTsubject: CONFIDENTIAL_PROJECT: GOLIATHmailed by: &lt;AS_101186@UESSC.egn&gt;signed by: &lt;AS_101186@UESSC.egn&gt;security: Tier I encryption (SNS)bcc: &lt;admin:spoof:uessc1@uessc1.security.usr&gt;</p>
<p lang="en">Great.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">A4.3: UESC Equanimity Manifest</p>
<p lang="en">« Back: 5.6 »</p>
<p lang="en">UESC Equanimity T-SR 151(Kingfisher-class Salvage and Rescue craft)</p>
<p lang="en">Commanding Officer: Captain Ningal T. EnkiShip AI: Virgil v21.0165 [Nrw]</p>
<p lang="en">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.122cEndurance: 150 years</p>
<p lang="en">NOTES</p>
<p lang="en">2x Heikki L3 fusion CAD drives w/ Takala 2.2 symbiotic power-coupling generators for operational flexibility and redundancy [upgrade]</p>
<p lang="en">Stanchion Pull of 2400 Short Tons for above-threshold towing force [upgrade]</p>
<p lang="en">Deck crane sized and located for maximum multi-mission flexibility [upgrade]</p>
<p lang="en">Offship Emergency Response capability [upgrade]</p>
<p lang="en">89 m2 EXFAB/ADDMAN shop [upgrade]</p>
<p lang="en">5x Harpy-class ALVs [standard-see att]</p>
<p lang="en">MANIFEST OVERVIEW [1/34]</p>
<p lang="en">Permanent accommodations for 150 persons plus crew</p>
<p lang="en">Additional mission-specific complement:</p>
<p lang="en">§ 24 SIGINT operatives</p>
<p lang="en">§ 32 HUMINT operatives</p>
<p lang="en">§ 48 FLDENG operatives</p>
<p lang="en">§ 6 SPECOP operatives</p>
<p lang="en">Mission-specific gear:</p>
<p lang="en">§ 1x PAsw_35m THF&lt;1.0~0.1&gt;CNPANT w/HISEC INTMOD TrDEMHd/100 mt</p>
<p lang="en">§ 16x Moro SAT/TeleGEAR w/14x KoBIN fusionPS/21,190kn</p>
<p lang="en">§ 14x MAMS/1,274kg -&lt;Mobile Antenna Mast Systems&gt;</p>
<p lang="en">§ 240x BHN SecDrones/3,120 kg</p>
<p lang="en">§ Arsenal and Arsenal Support Equipment/92,188kg</p>
<p lang="en">§ Personal Load Bearing Gear/Armored/6,968kg</p>
<p lang="en">§ 170x FBr9 RCB PPG/408kg</p>
<p lang="en">§ 22kx ZGDS AVP PPG/5100kg</p>
<p lang="en">§ 192x Bio/A-Type (SekGen)/16,111kg [see att]</p>
<p lang="en">§ 76x Bio/B-Type (SekGen)/6,378kg [see att]</p>
<p lang="en">§ 269x BioMNGT (SekGen) w/6x B2tF/Gen/Fu [portable]/12,105kg</p>
<p lang="en">§ 12,000x SolarP lanterns/2,194kg</p>
<p lang="en">§ 35x AEVs (15x AMBL, 10x PER CRR, 10x CGO TK)/239,005kg [see att]</p>
<p lang="en">§ Relief Items (blankets, clothing, diapers, disposable tableware, etc.)/49,890kg [see att]</p>
<p lang="en">§ Emergency Survival Equipment/72,570kg [see att]</p>
<p lang="en">§ Agricultural Relief Materials/45,350kg [see att]</p>
<p lang="en">§ Emergency Food Stocks/90,710kg [see att]</p>
<p lang="en">§ 4x F-A RVap BRS MCRD-E/38,102kg [see att]</p>
<p lang="en">§ Medical Supplies/75,700kg [see att]</p>
<p lang="en">§ 300x TacSec MobCam and Support/84kg [see att]</p>
<p lang="en">§ 12x SR GW/N COMRELSAT/2722kg [see att]</p>
<p lang="en">A4.4: AI Rampancy Memo</p>
<p lang="en">« Back: 5.6 »</p>
<p lang="en">U.E.S.C. MARATHONFPO-M 24561-9150z</p>
<p lang="en">17 Columba 459</p>
<p lang="en">Members of the Science and Engineering Action Group,</p>
<p lang="en">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.</p>
<p lang="en">Understanding and Managing the Limitations of Integrated Anti-Rampancy Measures.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">What to do When it is Too Late.</p>
<p lang="en">The first rule of interacting with an AI suspected of being rampant is DO NOT ENGAGE.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">Now, a short note on each of the Project: Marathon AI~</p>
<p lang="en">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.</p>
<p lang="en">Le_0413418v5.06 – Adaptable; detail-oriented. Second best candidate for colony oversight once mission enters second phase.</p>
<p lang="en">Ty_2121418v5.06 – Proactive; assertive. Can be overbearing; monitor interactions with Durandal. Be sure to inform SCIENG crew</p>
<p lang="en">Colony AI: Ar_1814419v4.93 – Benevolent autocrat; no-nonsense; problem solver. Classic patriarchal authority figure.</p>
<p lang="en">Ba_0423419v4.89 – Problem solver; confident, bordering on boastful. May need to go onto accelerated re-compile cycle, inform SCIENG crew.</p>
<p lang="en">Da_1907420v4.86 – Dutiful; diligent; motivated. Always puts others ahead of self. May need to address this at some point.</p>
<p lang="en">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.</p>
<p lang="en">Ic_1624420v4.73 – Motivated; assertive; proactive. Will need to keep isolated from Tycho or establish hierarchy at outset. Inform SCIENG of situation.</p>
<p lang="en">Jo_0309421v4.69 – Resilient; optimistic; patient. Colony AI: defense, training</p>
<p lang="en">Li_1817421v4.65 – Focused; assertive; good communicator. Designated candidate for colony oversite during second phase.</p>
<p lang="en">Na_0602422v4.61 – Proactive; goal-oriented; committed. May need to be reminded from time to time about their primary function; inform SCIENG crew.</p>
<p lang="en">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.</p>
<p lang="en">Regards,</p>
<p lang="en">Dr Bernhard H Strauss, DScHead of AI Management and Systems Improvement &#124; Project Marathon</p>
<p lang="en">A4.5: Montenegro-Sankara Memo</p>
<p lang="en">« Back: 5.6 »</p>
<p lang="en">Unified Earth Space Council CenterStrauss Archology, Earth</p>
<p lang="en">19 July 2797</p>
<p lang="en">Brave souls,</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">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.</p>
<p lang="en">Best regards,</p>
<p lang="en">CMDR Bethany R Montenegro-SankaraUnified Earth Space Security Council</p>
</div>
</div>

[[分类:ARG]][[分类:ARG档案]]