Editorial boundary: This public alpha is generated from version-controlled source without third-party application or build packages. It is not the reviewed 1.0 corpus: 60 Academy lessons are substantive editorial drafts, 0 remain foundation outlines, and independent domain review remains open.

Current state

  • Space, operational-technology, software-supply-chain, zero-trust, post-quantum, and cyber-resilience standards provide relevant but fragmented reference points; their existence does not establish integration or assurance.
  • Secure-update patterns, attestation, delay-tolerant networking, formally assessed kernels, software bills of materials, and reproducible-build practices exist in different contexts. Availability does not establish compatibility, flight qualification, century maintenance, or safe integration.
  • Within the public sources sampled for this foundation draft, we did not identify a generation-ship cybersecurity standard or a demonstrated century-scale cryptographic deployment.

Major unknowns

  • Trust anchors, identity, secure time, revocation, incident command, threshold recovery, crypto-agile migration, anti-rollback, and archival signature interpretation must work locally after permanent loss of Earth.
  • Insiders, collusion, governance capture, compromised suppliers, corrupted hardware, malicious maintenance, radiation faults, operator error, and generational loss of expertise must be addressed without turning safety monitoring into surveillance or political control.
  • Onboard manufacturing makes malicious designs, poisoned toolchains, compromised metrology, counterfeit replacement parts, and configuration drift cyber-physical threats.

Failure modes

  • A compromised build, spare, model, credential, or maintenance interface crosses isolation boundaries.
  • Cryptography, identity, or recovery procedures become obsolete while privileged operators lose the ability to re-establish trust.

Useful precursors

  • Secure-by-design operational technology, reproducible builds, signed evidence graphs, and offline recovery media.
  • Long-horizon incident exercises that include insider risk, degraded communications, hardware loss, and cryptographic migration.

Direct dependencies

Decision gate

Mixed crews must repeatedly isolate a compromised zone, maintain life support, investigate locally, rebuild from known-good material, and rejoin safely.

Claim records

Context sources—not claim citations

Foundation system synthesis · Linked claims editorially assessed · Independent system review pending · Suggest a correction

Accountability record

How to inspect this page

Scope: Capability synthesis cybersecurity

Page citations and accountability links

Assumptions and limits

  • The capability is modeled as one part of a coupled civilization-scale system rather than a separable component.
  • Context sources frame the area but do not support every synthesis statement; linked claims carry the claim-specific evidence burden.

What would change this page?

Mixed crews must repeatedly isolate a compromised zone, maintain life support, investigate locally, rebuild from known-good material, and rejoin safely. Material evidence that resolves the listed unknowns or changes a linked claim would trigger revision.

People, review, and conflicts

Prepared by
GShips Project
Editorial status
foundation system synthesis
Editorial reviewer
GShips Project AI-assisted accountability pass
Last editorial review
2026-07-26
Independent review
pending
Independent reviewer
No independent reviewer assigned
Last independent review
No independent-review date exists
Last content edit
2026-07-25

Declared conflicts

  • The maintainer intends to explore a commercial venture based on some GShips work. No entity, outside funding, customer, sponsor, or indexed-organization relationship currently exists.

Suggest a correction to this page