{
  "schemaVersion": "gships-review-packet-1",
  "packetId": "academy:precursors-and-action",
  "stableId": "precursors-and-action",
  "family": "academy",
  "slug": "precursors-and-action",
  "title": "Precursors, partners & action",
  "status": "prepared-human-review-not-started",
  "release": {
    "releaseId": "public-alpha-2026-07-26-research-visuals-r14",
    "sourceCommit": "3eb036fce3d711336c8c605625895e8a2e799ab0",
    "corpusGeneratedAt": "2026-07-25",
    "frozenAt": "2026-07-26T22:50:50.000Z",
    "canonicalOrigin": "https://gships.dammonburden.com"
  },
  "paths": {
    "human": "/review/academy/precursors-and-action",
    "family": "/review/academy",
    "packet": "/review-packets/academy/precursors-and-action.32b9835d0e022c2b.json",
    "decisionTemplate": "/review-packets/academy/precursors-and-action.32b9835d0e022c2b.decision-template.json",
    "worksheet": "/review-packets/academy/precursors-and-action.32b9835d0e022c2b.worksheet.md",
    "byFingerprint": "/review-packets/by-fingerprint/32b9835d0e022c2b5fb62f0256dc1c4016dbb24cdcc8ca8aa95b15137a480f0e.json"
  },
  "boundary": "Prepared review packet; human review has not started. This packet is not a completed review, endorsement, reviewer appointment, partnership, or authorization to act.",
  "governingPolicies": [
    {
      "id": "policy-editorial-governance-001",
      "version": "0.1.0",
      "path": "/editorial-policy",
      "recordType": "governing-policy",
      "fingerprint": "1f6a1f823e8bfe891b6a707c5dce2ee2337c0bb7d915b48d6060ca82b8da1b47",
      "snapshot": {
        "id": "policy-editorial-governance-001",
        "version": "0.1.0",
        "status": "foundation-policy-controls-not-yet-staffed",
        "adoptedForFoundation": "2026-07-25",
        "title": "Editorial governance and independent review",
        "publisher": "GShips Project",
        "maintainer": "Dammon Burden",
        "publisherInterest": "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.",
        "currentBoundary": "No independent domain reviewer or review council is currently appointed. Foundation records and outlines may not be represented as independently reviewed.",
        "reviewerSelection": [
          "Publish the reviewer’s name, relevant credentials or lived expertise, review scope, compensation status, and declared conflicts with consent.",
          "Select for the actual claim domain rather than general prestige; include affected-community and disability-led expertise where rights or access are involved.",
          "Do not treat an employee, investor, customer, sponsor, source author, or directly supervised collaborator as independent for the affected claim."
        ],
        "reviewProcess": [
          "Provide the exact claim, sources, locators, assumptions, counterevidence, transfer limits, and proposed evidence dimensions.",
          "Record approve, revise, contest, or reject at claim level; silence and event attendance never count as review.",
          "Publish material minority findings and the editor’s reasoned response.",
          "High-consequence medical, reproductive, nuclear, radiation, cybersecurity, governance, and dual-use claims require two qualified independent reviewers with complementary scopes.",
          "A reviewer may recuse at any time; unresolved conflicts or missing expertise block the reviewed label."
        ],
        "appealAndCorrection": [
          "A correction receives a reference identifier and triage record; safety-critical allegations receive priority.",
          "A material editorial decision may be appealed to a reviewer not involved in the original decision once such a panel exists.",
          "Substantive reversals, unresolved disputes, and removed conclusions receive a dated public record that protects reporter privacy.",
          "No sponsor, customer, founder, or reviewer may purchase, suppress, or unilaterally assign an evidence grade."
        ],
        "publicationGate": "Public 1.0 requires named review coverage across every Academy track, documented high-consequence two-person review, a material-corrections log, reviewer conflict records, and an operating appeal path.",
        "correctionPath": "/corrections"
      }
    },
    {
      "id": "policy-dual-use-001",
      "version": "0.1.0",
      "path": "/dual-use",
      "recordType": "governing-policy",
      "fingerprint": "81637e2849f9c0866d23f7174eb9a2ce522b86313167ebf5022fca122d6e506c",
      "snapshot": {
        "id": "policy-dual-use-001",
        "version": "0.1.0",
        "status": "planned-controls-not-yet-operational",
        "adoptedForFoundation": "2026-07-25",
        "title": "Civil, defensive, and rights-preserving use boundary",
        "summary": "GShips may research safety, resilience, logistics, communications, recovery, and cyber defense only within explicit end-use, rights, and independent-review controls. Calling an activity defensive is never sufficient by itself.",
        "scopeTrigger": "Apply dual-use review before accepting or materially advancing customer, funder, collaborator, operational, procurement, or publication-sensitive work whose capability, data, end use, or transfer could reasonably enable a prohibited use. Public non-actionable education still follows prohibited-content and sensitive-publication controls.",
        "allowedInPrinciple": [
          "Safety engineering and independently assessed protection",
          "Resilience, graceful degradation, recovery, and disaster response",
          "Civil logistics, maintenance, communications, and knowledge continuity",
          "Cyber defense, secure software, incident response, and recovery",
          "Rights-preserving health, accessibility, ecology, education, and governance research"
        ],
        "prohibited": [
          "Identification, tracking, prioritization, or engagement of people or assets for force, weapons, repression, or offensive operations; safety navigation, astronomy, collision avoidance, search and rescue, and independently governed planetary defense are not prohibited by this clause",
          "Weapons command-and-control or targeting support",
          "Offensive access, persistence, exploitation, or destructive cyber payloads",
          "Mass surveillance, biometric repression, or political-control systems",
          "Autonomous force application",
          "Coercive reproductive, medical, genetic, disability, or civic control",
          "Nonconsensual experimentation or treating residents as research instruments"
        ],
        "reviewRequiredBeforeAnyRelevantWork": [
          "Customer, funder, collaborator, jurisdiction, beneficial-owner, and end-use screening",
          "Export-control and sanctions review by qualified counsel when applicable",
          "Written scope, allowed-use, prohibited-use, audit, termination, and incident clauses",
          "Independent stop-work authority with a named alternate and founder recusal",
          "Sensitive-publication and information-hazard review",
          "Whistleblowing, escalation, incident response, appeal, and anti-retaliation paths",
          "Aggregate transparency reporting that protects legitimate privacy and security"
        ],
        "currentBoundary": "No screening body, independent stop-work authority, contractual controls, or appeal body currently exists. Therefore no relevant customer, defense, dual-use, or operational engagement is authorized by this policy.",
        "changeControl": "Material changes require a dated public rationale, independent review, and may not be approved by the founder alone.",
        "correctionPath": "/corrections"
      }
    }
  ],
  "reviewContract": {
    "questions": [
      {
        "id": "question-1",
        "text": "Are the five lessons accurate, comprehensible, appropriately bounded, and complete enough for the declared audience?",
        "required": true
      },
      {
        "id": "question-2",
        "text": "Do citations, assumptions, transfer limits, uncertainty, and change conditions support every substantive conclusion?",
        "required": true
      },
      {
        "id": "question-3",
        "text": "What important affected-community, accessibility, safety, or disciplinary perspective is missing?",
        "required": true
      }
    ],
    "exclusions": [
      "A track review does not approve linked claim records; those remain primary in system packets.",
      "A favorable curriculum review is not mission, product, medical, legal, or operational authorization."
    ],
    "requestedScopeCodes": [
      "information-science",
      "institution-building",
      "systems-engineering"
    ],
    "dispositions": [
      "approve",
      "revise",
      "contest",
      "reject",
      "recuse"
    ],
    "prohibitedInputs": [
      "private legal names or contact details",
      "identity documents or raw credential files",
      "accessibility or medical records",
      "confidential conflict evidence",
      "classified, export-controlled, proprietary, or exploit material"
    ],
    "freshness": {
      "maximumDecisionAgeFromFreezeDays": 365,
      "eventOccurrenceRule": "Not applicable to this packet family."
    },
    "completionRule": "Every primary record must receive the required number of valid, current-fingerprint approvals; every complementary scope group and required domain must be covered; any unresolved revise, contest, or reject disposition blocks publication.",
    "highConsequenceRule": "Named medical, reproductive, nuclear, radiation, cybersecurity, governance, and dual-use conclusions require two distinct qualified independent humans covering complementary domain-method and rights/public-interest scopes."
  },
  "primaryRecords": [
    {
      "recordType": "academy-track",
      "recordId": "precursors-and-action",
      "title": "Precursors, partners & action",
      "publicPath": "/academy/precursors-and-action",
      "recordFingerprint": "f091f799de3df94e27bf77663223ddab115d331d3e07dc03f7122a6246b59528",
      "reviewRequirements": {
        "minimumIndependentApprovals": 1,
        "highConsequenceDomains": [],
        "requiredDomainCodes": [],
        "requiredComplementaryScopeGroups": [
          {
            "id": "bounded-competence",
            "scopeClass": "bounded-competence",
            "oneOf": [
              "institution-building",
              "systems-engineering"
            ]
          }
        ],
        "unresolvedNegativeFindingBlocksPublication": true
      },
      "referenceIds": [],
      "snapshot": {
        "slug": "precursors-and-action",
        "number": 12,
        "title": "Precursors, partners & action",
        "kicker": "Build useful proof now",
        "summary": "Turn the systems map into Earth analogs, Solar System demonstrations, partner relationships, fundable products, standards, and leadership practice.",
        "coreQuestion": "What can a serious person or organization do in the next year?",
        "image": "/images/chapters/17-building-venture.avif",
        "systems": [
          "analogs-verification",
          "assembly-logistics",
          "institutions-workforce"
        ],
        "lessons": [
          {
            "slug": "earth-analogs",
            "title": "Earth analogs and honest transfer",
            "summary": "Compare Biosphere 2, HERA, CHAPEA, Concordia, HI-SEAS, and industrial analogs.",
            "minutes": 18,
            "level": "Foundation"
          },
          {
            "slug": "solar-system-ladder",
            "title": "The Solar System proof ladder",
            "summary": "Move from component rigs through orbital and lunar habitats before stellar commitments.",
            "minutes": 18,
            "level": "Foundation"
          },
          {
            "slug": "ecosystem-map",
            "title": "Who is already building the pieces?",
            "summary": "Navigate agencies, labs, universities, companies, societies, and public-interest groups.",
            "minutes": 18,
            "level": "Foundation"
          },
          {
            "slug": "venture-wedges",
            "title": "Products before starships",
            "summary": "Evaluate assurance software, life support, remote medicine, manufacturing, and resilient power.",
            "minutes": 18,
            "level": "Foundation"
          },
          {
            "slug": "leadership-practice",
            "title": "Leadership as stewardship",
            "summary": "Build credibility through useful work, standards, transparent evidence, succession, and restraint.",
            "minutes": 18,
            "level": "Foundation"
          }
        ]
      }
    },
    {
      "recordType": "academy-lesson",
      "recordId": "lesson-12-01",
      "title": "Earth analogs and honest transfer",
      "publicPath": "/academy/precursors-and-action/earth-analogs",
      "recordFingerprint": "e59542a5bb7f4a4c2eaa94caf60ce0a2d98de51ab2096a4c50482871a254bfac",
      "reviewRequirements": {
        "minimumIndependentApprovals": 1,
        "highConsequenceDomains": [],
        "requiredDomainCodes": [],
        "requiredComplementaryScopeGroups": [
          {
            "id": "bounded-competence",
            "scopeClass": "bounded-competence",
            "oneOf": [
              "institution-building",
              "systems-engineering"
            ]
          }
        ],
        "unresolvedNegativeFindingBlocksPublication": true
      },
      "referenceIds": [],
      "snapshot": {
        "slug": "earth-analogs",
        "title": "Earth analogs and honest transfer",
        "summary": "Compare Biosphere 2, HERA, CHAPEA, Concordia, and industrial testbeds without pretending that resemblance is validation.",
        "minutes": 30,
        "level": "Foundation",
        "id": "lesson-12-01",
        "trackSlug": "precursors-and-action",
        "trackTitle": "Precursors, partners & action",
        "href": "/academy/precursors-and-action/earth-analogs",
        "preparedBy": "GShips Project",
        "lastEditedAt": "2026-07-25",
        "reviewRequiredDomains": [
          "analog-research",
          "human-factors",
          "closed-ecology",
          "reliability",
          "systems-verification",
          "research-ethics"
        ],
        "claimIds": [
          "claim-18-01",
          "claim-18-02",
          "claim-18-05",
          "claim-18-10"
        ],
        "exactMdx": "---\nid: \"lesson-12-01\"\ntrack: \"precursors-and-action\"\nslug: \"earth-analogs\"\ntitle: \"Earth analogs and honest transfer\"\nsummary: \"Compare Biosphere 2, HERA, CHAPEA, Concordia, and industrial testbeds without pretending that resemblance is validation.\"\nminutes: 30\nlevel: \"Foundation\"\npreparedBy: \"GShips Project\"\nlastEditedAt: \"2026-07-25\"\nconflicts: \"Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, customer, sponsor, partner, or analog-facility relationship currently exists.\"\nreviewRequiredDomains: \"analog-research, human-factors, closed-ecology, reliability, systems-verification, research-ethics\"\nclaimIds: \"claim-18-01, claim-18-02, claim-18-05, claim-18-10\"\n---\n\n# Earth analogs and honest transfer\n\n> **Evidence boundary:** This is a cited substantive editorial draft, not an independently reviewed analog program or a human-subjects protocol. The facilities below test different slices under Earth conditions. Their inclusion does not imply partnership, endorsement, access, or that any result transfers unchanged to space.\n\n## Plain-language summary\n\nAn analog is useful when it makes one important part of the real problem observable at lower cost and risk. It becomes misleading when surface resemblance—an isolated crew, a sealed building, a harsh landscape—is treated as proof that a much larger system will work.\n\nNASA’s first CHAPEA crew completed 378 days in a 1,700-square-foot Mars-simulation habitat. The exercise included resource limits, isolation, delayed communications, maintenance, crop work, and simulated surface operations. ESA uses the remote Concordia station to study isolation, darkness, disrupted sleep, hypoxia, and small multicultural teams. Biosphere 2 exposes researchers to large controlled ecosystems and unusually visible energy and water infrastructure. HERA runs shorter controlled isolation campaigns. The International Space Station supplies real microgravity, radiation, spacecraft operations, life support, resupply, and emergency experience.\n\nNone combines centuries of duration, children and aging, no rescue, no resupply, industrial renewal, interstellar hazards, institutional succession, and an unknown destination. The right question is not “Which analog is most like a generation ship?” It is “Which claim does this analog test, under what boundary, and what harder test follows?”\n\n## An analog is a model with people and hardware\n\nEvery analog has at least six boundaries:\n\n1. **Environment:** gravity, radiation, pressure, atmosphere, temperature, lighting, microbial exposure, and surrounding infrastructure.\n2. **Duration:** hours, months, a year, or repeated campaigns—not merely the date range, but the number of maintenance and social cycles exercised.\n3. **Scale:** people, floor area, mass flows, equipment count, ecological diversity, and organizational complexity.\n4. **Intervention:** rescue, resupply, remote advice, spare parts, medical evacuation, and researchers changing the protocol.\n5. **Fidelity:** what is physical, what is simulated, what is scripted, and what is absent.\n6. **Measurement:** preregistered outcomes, sensor coverage, participant reports, failure logging, missing data, and publication access.\n\nAn analog result should be written as a bounded conditional:\n\n> Under these stated conditions, for this duration and group, the observed system produced these outcomes while receiving these interventions.\n\nIt should not be written as “Mars living works” or “closed ecosystems are feasible.” Those conclusions are larger than the test.\n\n## What the major analog families can teach\n\n### CHAPEA and HERA: controlled human-performance campaigns\n\nNASA describes CHAPEA as a series of year-long Mars-surface simulations with four-person crews. Mission 1 ran from June 25, 2023 through July 6, 2024. Mission 2 began October 19, 2025. The program can impose workloads, equipment faults, restricted resources, communication delay, exercise, hygiene, maintenance, crop growth, and private-quarters conditions while collecting structured health and performance data.\n\nThat makes CHAPEA valuable for questions about schedule design, food acceptability, task conflicts, resource decisions, communication latency, team process, and maintenance workload. It is weak evidence for gravity effects, radiation, spacecraft atmosphere, ecological closure, manufacturing, pregnancy, childhood, lifetime medicine, or a society containing thousands of people. Participants know they are on Earth; safety staff and external infrastructure exist even when operational communication is deliberately delayed.\n\nHERA offers shorter, repeatable controlled campaigns. Shorter runs can be a strength when the research needs replication, controlled protocol changes, or rapid iteration. They are not long-duration evidence simply because the habitat looks spacecraft-like.\n\n### Concordia: real isolation, logistics, darkness, and maintenance\n\nConcordia is a French–Italian Antarctic research station used by ESA for human research. Winter conditions can isolate a crew for months, with extreme cold, darkness, altitude-related hypoxia, small-team interdependence, and real responsibility for maintaining an inhabited station. Unlike a scripted habitat fault, Antarctic weather and logistics have consequences that participants cannot switch off.\n\nConcordia can inform sleep, mood, cognition, group dynamics, remote medicine, winter-over selection, supplies, maintenance, and handover. It also confounds variables: hypoxia, cold, darkness, volunteer selection, national programs, and Earth-normal gravity occur together. A result from a small adult crew cannot establish outcomes for children, disabled residents, pregnancy, old age, or a culturally diverse city.\n\n### Biosphere 2 and MELiSSA: coupled ecological and process evidence\n\nBiosphere 2 is now a research user facility with systems including the Landscape Evolution Observatory, rainforest, ocean, agrivoltaics, and the Space Analog for the Moon and Mars. Its published facility information also makes a crucial boundary visible: the enclosed research complex depends on substantial external energy and thermal infrastructure. “Airtight” is not synonymous with energetically closed, materially self-sufficient, or autonomous.\n\nESA’s MELiSSA program decomposes regenerative life support into compartments for organic-waste processing, carbon removal, nitrification, photosynthetic food and oxygen production, higher plants, and crew demand. This process-oriented approach is useful because it exposes streams and unit operations instead of treating “nature” as a black box. Its pilot plants and organisms are evidence about particular loops, not a demonstrated permanent human ecosystem.\n\nBoth point toward a better metric than a single recycling percentage: a time series of every imported, exported, stored, accumulated, vented, discarded, and biologically transformed material, plus energy, labor, sensors, replacement parts, and external expertise.\n\n### The International Space Station: flight evidence with a supply chain\n\nThe ISS provides operational evidence in microgravity. NASA reported a system-level water-recovery milestone near 98 percent after adding a brine processor, while its broader ECLSS description emphasizes filters, catalytic processing, sensors, electrolysis, carbon-dioxide removal, and continuing hardware support.\n\nThe milestone is important and bounded. Water recovery is not food closure, nutrient closure, industrial closure, or zero maintenance. A percentage also hides inventory, contaminant buildup, consumables, off-nominal events, reject streams, crew labor, spares, and resupply. The ISS is a continuously supported orbital laboratory, not a detached civilization.\n\n## Build an analog portfolio, not a champion\n\nNo single facility should carry the validation burden. A useful portfolio assigns different claims to different test environments:\n\n- Component rigs characterize membranes, catalysts, bearings, crops, sensors, and fault behavior.\n- Human-in-the-loop habitats test workload, interfaces, privacy, handover, maintenance, and emergency procedures.\n- Ecological facilities test coupled material cycles, community dynamics, contamination, and recovery.\n- Remote stations test real logistics, isolation, local authority, medical escalation, and winter-over maintenance.\n- Orbital platforms test microgravity, radiation, vacuum interfaces, spacecraft operations, and limited resupply.\n- Industrial plants test throughput, quality control, tooling, contamination, operator training, and economic maintenance.\n- Communities and critical infrastructure test whether resilience work produces present public value.\n\nAn evidence graph should show exactly which requirement each experiment touches. If an experiment is described only as “generation-ship research,” it is probably too vague to evaluate.\n\n## A transfer ledger\n\nFor every result, record:\n\n- claim tested and requirement identifier;\n- analog environment and omitted hazards;\n- participant or system population and selection;\n- duration, duty cycles, and interruptions;\n- external power, water, data, personnel, spares, and rescue;\n- planned versus unplanned interventions;\n- failure chronology and recovery;\n- measurement uncertainty and missing data;\n- adverse events and participant protections;\n- whether the result replicated;\n- what cannot be inferred;\n- the next harder, still-reversible test.\n\nThe transfer factor is not a single number. It is a structured argument. A maintenance procedure may transfer well from a submarine or chemical plant even when the social environment does not. A crew-cohesion observation may transfer poorly from four carefully selected adults to a multigenerational population. A closed-loop mass balance may transfer only after gravity, organism, temperature, and scale effects are retested.\n\n## Failure is an output\n\nAnalog programs are vulnerable to branding pressure. A dramatic habitat, crew patch, countdown, and “mission” narrative can make the experiment feel more successful than its measurements justify. Sponsors and facilities may fear that publishing faults will hurt future funding.\n\nA responsible program reverses that incentive:\n\n- preregister important measures and stopping rules;\n- publish protocol deviations and rescue interventions;\n- separate participant safety decisions from performance scoring;\n- preserve raw-enough data for lawful reanalysis;\n- reward fault discovery and negative results;\n- disclose conflicts and facility relationships;\n- allow independent reviewers to challenge transfer claims;\n- avoid ranking crews as morally fit or unfit for future settlement.\n\nHuman-subjects research requires ethics review, consent, privacy, withdrawal protections, and careful handling of identifiable health and behavior data. “The mission needs it” does not waive those duties.\n\n## Evidence ledger\n\n- **L12-01-A — Present analogs cover different slices.** Basis: observed institutional programs. Readiness: operational at their stated scales. Confidence: strong that the programs exist; transfer remains claim-specific. Support: NASA CHAPEA and ECLSS, ESA Concordia and MELiSSA, Biosphere 2.\n- **L12-01-B — No single analog validates a generation ship.** Basis: modeled systems comparison. Readiness: operational as an evidence-policy rule. Confidence: strong because every reviewed analog omits multiple defining conditions.\n- **L12-01-C — External interventions must be counted.** Basis: observed operations and normative verification practice. Readiness: operational. Confidence: strong.\n- **L12-01-D — Negative results improve the proof ladder.** Basis: normative research policy supported by verification practice. Readiness: operational when governance and publication terms permit. Confidence: supported; incentive effects require continued study.\n- **L12-01-E — Human analogs do not authorize coercive selection.** Basis: normative rights boundary. Readiness: operational as project policy. Confidence: strong as a GShips red line; independent ethics review remains required.\n\nLinked corpus claims: `claim-18-01`, `claim-18-02`, `claim-18-05`, and `claim-18-10`. See the claim registry for each record's current evidence grade and independent-review state.\n\n## Assumptions and limits\n\n- Official program descriptions are used to establish scope, not to independently validate unpublished outcomes.\n- Facility pages can emphasize intended value; peer-reviewed results and protocols should be checked claim by claim.\n- The lesson does not evaluate participant medical risk or recommend enrollment.\n- Analog populations are generally small and selected, limiting generalization.\n- Earth gravity, rescue, law, supply chains, and outside expertise remain available in ways a stellar vehicle may not share.\n- No analogy substitutes for flight evidence, and no flight evidence substitutes for multigenerational evidence.\n\n## What would change this conclusion?\n\nA replicated analog program combining long duration, materially accountable ecology, autonomous industry, mixed-age residents, genuine communication delay, constrained rescue, transparent fault injection, independent ethics, and open failure reporting would strengthen transfer across several domains. A sustained Solar System habitat could add flight evidence. Neither would make one facility sufficient. Evidence that a cheaper test answers a claim better should redirect work away from a more theatrical analog.\n\n## Sources and locators\n\n- [NASA — About CHAPEA](https://www.nasa.gov/humans-in-space/chapea/about-chapea/). Locator: goals, habitat, mission schedule, stressors, and research scope; accessed 2026-07-25.\n- [NASA — First Mars Crew Completes Yearlong Simulated Red Planet Mission](https://www.nasa.gov/missions/analog-field-testing/chapea/first-mars-crew-completes-yearlong-simulated-red-planet-nasa-mission/). Locator: 378-day Mission 1, four-person crew, operations, resource limits, and communication delay; accessed 2026-07-25.\n- [ESA — Isolation studies in Antarctica](https://www.esa.int/Science_Exploration/Human_and_Robotic_Exploration/Exploration/Isolation_studies_in_Antarctica). Locator: isolation, sleep, hypoxia, small-team, and countermeasure research at Concordia; accessed 2026-07-25.\n- [Biosphere 2 — User Facility Information](https://biosphere2.org/research/user-facility-information). Locator: research systems, access model, durations, and user-program boundary; accessed 2026-07-25.\n- [Biosphere 2 — Energy and Water](https://biosphere2.org/research/user-facility-information/energy-and-water). Locator: external power, cooling, heating, and water-system figures; accessed 2026-07-25.\n- [ESA — MELiSSA Closed Loop Compartments](https://www.esa.int/Enabling_Support/Space_Engineering_Technology/Melissa/Closed_Loop_Compartments). Locator: five compartments, unit functions, and incomplete waste conversion; accessed 2026-07-25.\n- [NASA — ISS Water Recovery Milestone](https://www.nasa.gov/missions/station/iss-research/nasa-achieves-water-recovery-milestone-on-international-space-station/). Locator: 98-percent system goal, brine processor, treatment chain, and prior recovery range; accessed 2026-07-25.\n- [NASA Systems Engineering Handbook](https://www.nasa.gov/wp-content/uploads/2018/09/nasa_systems_engineering_handbook_0.pdf). Locator: product verification, product validation, intended environment, stakeholder expectations, and captured evidence; NASA/SP-2016-6105 Rev 2.\n\n## Editorial record\n\n- Prepared by: GShips Project\n- Last edited: 2026-07-25\n- Required review: analog research, human factors, closed ecology, reliability, systems verification, and research ethics\n- Conflicts: Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, customer, sponsor, partner, or analog-facility relationship currently exists\n- Corrections: [Suggest a correction](https://gships.dammonburden.com/corrections)\n"
      }
    },
    {
      "recordType": "academy-lesson",
      "recordId": "lesson-12-02",
      "title": "The Solar System proof ladder",
      "publicPath": "/academy/precursors-and-action/solar-system-ladder",
      "recordFingerprint": "2eb33989b9b97520ef4bc51abd166a31ec14056e541143b5b0f329bc55cbe7ae",
      "reviewRequirements": {
        "minimumIndependentApprovals": 1,
        "highConsequenceDomains": [],
        "requiredDomainCodes": [],
        "requiredComplementaryScopeGroups": [
          {
            "id": "bounded-competence",
            "scopeClass": "bounded-competence",
            "oneOf": [
              "institution-building",
              "systems-engineering"
            ]
          }
        ],
        "unresolvedNegativeFindingBlocksPublication": true
      },
      "referenceIds": [],
      "snapshot": {
        "slug": "solar-system-ladder",
        "title": "The Solar System proof ladder",
        "summary": "Advance from component rigs to integrated Earth testbeds, orbital operations, and autonomous Solar System habitats before any stellar commitment.",
        "minutes": 30,
        "level": "Foundation",
        "id": "lesson-12-02",
        "trackSlug": "precursors-and-action",
        "trackTitle": "Precursors, partners & action",
        "href": "/academy/precursors-and-action/solar-system-ladder",
        "preparedBy": "GShips Project",
        "lastEditedAt": "2026-07-25",
        "reviewRequiredDomains": [
          "systems-architecture",
          "test-and-verification",
          "human-spaceflight",
          "logistics",
          "reliability",
          "planetary-protection",
          "governance"
        ],
        "claimIds": [
          "claim-18-01",
          "claim-18-10",
          "claim-19-03",
          "claim-19-10"
        ],
        "exactMdx": "---\nid: \"lesson-12-02\"\ntrack: \"precursors-and-action\"\nslug: \"solar-system-ladder\"\ntitle: \"The Solar System proof ladder\"\nsummary: \"Advance from component rigs to integrated Earth testbeds, orbital operations, and autonomous Solar System habitats before any stellar commitment.\"\nminutes: 30\nlevel: \"Foundation\"\npreparedBy: \"GShips Project\"\nlastEditedAt: \"2026-07-25\"\nconflicts: \"Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, customer, sponsor, partner, or space-agency relationship currently exists.\"\nreviewRequiredDomains: \"systems-architecture, test-and-verification, human-spaceflight, logistics, reliability, planetary-protection, governance\"\nclaimIds: \"claim-18-01, claim-18-10, claim-19-03, claim-19-10\"\n---\n\n# The Solar System proof ladder\n\n> **Evidence boundary:** This is a cited substantive editorial draft, not a mission manifest or flight-safety determination. NASA and other programs are referenced as evidence sources, not partners. A proof ladder orders learning; it does not create a duty to climb, launch, settle, or continue when alternatives are better.\n\n## Plain-language summary\n\nA generation ship should not be the first place humanity discovers whether its habitat can repair a pump, recover a crop, transfer authority, deliver a baby safely, rebuild a controller, or survive a corrupted software update.\n\nThe Solar System offers progressively harder environments while Earth remains much closer than another star. Hardware can move from laboratory rigs to integrated terrestrial habitats, low Earth orbit, cislunar space, lunar surfaces, deep-space transits, and eventually long-lived autonomous habitats. Each step should retire specific uncertainties and provide present scientific or public value.\n\nNASA’s Moon-to-Mars Architecture demonstrates one useful planning method: define objectives before choosing implementations, decompose them into needs and functions, publish gaps, and update the architecture as evidence changes. NASA explicitly describes its Architecture Definition Document as an evolving architecture tool rather than a manifest or requirements document. GShips can borrow that discipline without treating Moon-to-Mars work as a generation-ship plan.\n\nThe ladder has two rails:\n\n- **Capability:** harder duration, distance, closure, autonomy, repair, and integration.\n- **Legitimacy:** stronger rights, consent, governance, public value, environmental review, and authority to stop.\n\nA rung passes only when both advance.\n\n## Start with claims, not destinations\n\n“Build a lunar base” is not a verification plan. It is a place and a possible program. The testable form is narrower:\n\n- demonstrate a water processor for a stated influent range and duration;\n- isolate a power island, black-start it, and restore loads without unsafe control coupling;\n- reproduce a failed mechanical part with verified material and dimensional properties;\n- operate a food subsystem through a defined crop disease and nutrient imbalance;\n- transfer operational authority between independent teams without losing configuration control;\n- recover from a compromised software zone while life support remains in a safe state.\n\nFor each claim, define:\n\n1. requirement and stakeholder;\n2. current evidence and uncertainty;\n3. test article and environment;\n4. success measure and stop condition;\n5. faults to inject;\n6. outside support allowed;\n7. artifacts captured;\n8. independent reviewers;\n9. rights and environmental constraints;\n10. decision after the test.\n\nThe next rung is earned by evidence, not calendar momentum.\n\n## A seven-rung ladder\n\n### Rung 0 — models, records, and interface definitions\n\nBefore building hardware, create traceable requirements, mass and energy balances, fault trees, material ledgers, hazard analyses, decision rights, and evidence records. Models at this rung can expose contradictions cheaply. They cannot validate the real system.\n\nAn evidence graph should link every major conclusion to assumptions, sources, model versions, tests, reviewers, and counterevidence. An LLM may help extract or compare records, but it cannot serve as the source, approval authority, or sole failure detector.\n\n**Exit evidence:** a reproducible baseline; unresolved interfaces visible; independent review; no hidden “magic” imports or emergency interventions.\n\n### Rung 1 — component and material rigs\n\nTest valves, membranes, seals, bearings, catalysts, batteries, crops, bioreactors, shielding coupons, controllers, and sensors across relevant cycles and contaminants. Exercise accelerated aging carefully without claiming it reproduces all long-duration mechanisms.\n\n**Exit evidence:** failure distributions, calibration history, maintenance labor, consumables, contamination pathways, and inspectable teardown results.\n\n### Rung 2 — coupled terrestrial loops\n\nIntegrate power, thermal control, air, water, waste, food, data, maintenance, and operators. Count external utilities and expert interventions. Faults should cross domains: loss of cooling during crop stress, sensor drift during a maintenance backlog, cyber isolation during a water-quality anomaly.\n\nEarthside facilities should do useful work: resilient water treatment, remote-clinic support, controlled agriculture, microgrids, circular manufacturing, or emergency logistics. Present beneficiaries are an ethical requirement and a reality check.\n\n**Exit evidence:** bounded closure ledgers, degraded-mode operation, recovery without unsafe improvisation, and published negative results.\n\n### Rung 3 — delayed and disconnected operations\n\nIntroduce realistic communication delays and blackouts. Local operators need authority, offline procedures, evidence access, and escalation rules. Remote experts may advise only inside the declared delay model.\n\nMars analogs can simulate tens of minutes of delay. Interstellar communication takes years. The rung therefore tests the institution as much as the radio: can residents act without pretending Earth is the commander?\n\n**Exit evidence:** locally resolved incidents, auditable decisions, no hidden backchannel, and successful recovery after contradictory or stale advice.\n\n### Rung 4 — orbital integrated demonstrations\n\nFlight adds vacuum, microgravity, radiation, launch loads, constrained volume, spacecraft fire behavior, limited logistics, and real operational risk. The ISS demonstrates important subsystems and long-running international operations, but it also benefits from continuous ground expertise, routine cargo, evacuation possibilities, and component replacement.\n\nOrbital tests should target gaps that Earth cannot represent. Do not spend flight risk to reproduce an experiment better performed on the ground.\n\n**Exit evidence:** flight performance with margins, off-nominal history, repair and resupply accounting, and an explicit statement of what remained Earth-dependent.\n\n### Rung 5 — cislunar and lunar autonomy\n\nCislunar distance increases communication delay and logistics difficulty. Lunar surface systems add dust, thermal cycles, partial gravity, radiation, local-resource possibilities, and long night or polar-light constraints. NASA’s Moon-to-Mars architecture and gap tables provide a current example of tracing objectives into functions and identifying missing data and technology.\n\nThis rung should test logistics, maintainable surface power, habitats, communications, navigation, mobility, dust control, local materials, governance among operators, and environmental responsibility. It should not be used to claim that the Moon validates interstellar dust, centuries of culture, or a fully closed population.\n\n**Exit evidence:** multi-year operation, realistic logistics cadence, measured local-resource products, safe power recovery, and transparent dependence on Earth.\n\n### Rung 6 — autonomous Solar System habitats\n\nThe hardest responsible precursor would be a long-lived habitat that can survive extended periods without resupply while remaining close enough for eventual rescue and voluntary departure. It would integrate mixed-age community life only after medical and rights evidence supports doing so. It would replenish selected industrial capabilities, not merely stock spare boxes.\n\nThe goal is not artificial isolation. Rescue should never be withheld to make a test realistic. Instead, the architecture should record when outside intervention becomes necessary and treat that as evidence that the intended autonomy was not achieved.\n\n**Exit evidence:** repeated leadership and workforce succession, industrial replenishment, long-duration health evidence, legitimate governance, ecological recovery, and continuing resident consent.\n\n## Rung 7 is not automatically a starship\n\nAfter the Solar System ladder, the decision set remains:\n\n- continue Earthside and Solar System work;\n- send better robotic probes;\n- wait for propulsion, medicine, or governance evidence;\n- redesign the mission;\n- choose a nearer or nonstellar objective;\n- stop;\n- conclude that a crewed interstellar voyage is unnecessary or illegitimate.\n\nA megaproject often turns prior investment into an argument for proceeding. A proof ladder must do the opposite. Each rung increases the quality of the next decision, including a decision not to climb.\n\n## What does not transfer\n\nSolar System habitats still differ from a generation ship:\n\n- light-time is seconds to hours, not years;\n- launch windows and rescue can exist;\n- known celestial mechanics and mapped destinations reduce uncertainty;\n- interstellar gas and dust exposure is absent;\n- voyages last years, not necessarily centuries;\n- Earth supply chains and institutions remain culturally present;\n- no tested habitat includes many generations of birth, disability, aging, dissent, and succession;\n- mission populations are selected workers, not complete voluntary societies.\n\nThese gaps should remain visible even after successful demonstrations.\n\n## Quantitative proof records\n\nEvery rung should report more than “mission success”:\n\n- total operating hours and cycles;\n- planned and unplanned downtime;\n- mean and worst repair time;\n- external labor, data, energy, mass, and money;\n- spares consumed and remanufactured;\n- fraction of material streams measured;\n- fault-detection coverage and false alarms;\n- degraded-mode duration;\n- medical evacuations and near misses;\n- resident-reported autonomy, privacy, workload, and trust;\n- requirements verified and validations still open;\n- irreversible impacts;\n- stop rules triggered, waived, or changed.\n\nNASA systems engineering distinguishes verification—whether a product meets specified requirements—from validation—whether it fulfills intended use in the intended environment for stakeholders. A component can verify and the integrated habitat can still fail validation.\n\n## Planetary protection and dual use\n\nClimbing outward increases environmental and security consequences. Biological loops, autonomous mining, nuclear power, high-energy beams, cyber autonomy, and asteroid handling can be beneficial and dual use. A rung must not pass by demonstrating capability while ignoring misuse, contamination, export control, community consent, or environmental damage.\n\nCivil and defensive resilience is within GShips’ boundary. Autonomous weapons and offensive weapon integration are excluded. No habitat claim overrides planetary-protection obligations or the rights of people affected on Earth.\n\n## Evidence ledger\n\n- **L12-02-A — Objectives should precede implementations.** Basis: demonstrated institutional architecture practice. Readiness: operational. Confidence: strong as a planning method; it does not select a universal objective. Support: NASA Moon-to-Mars strategy and architecture.\n- **L12-02-B — Capability evidence should advance in bounded rungs.** Basis: normative synthesis of verification practice. Readiness: operational as program governance. Confidence: supported; rung contents require domain review.\n- **L12-02-C — Solar System habitats are relevant but incomplete precursors.** Basis: observed environment and modeled comparison. Readiness: major scale-up. Confidence: strong.\n- **L12-02-D — A successful rung does not compel the next.** Basis: normative anti-escalation rule. Readiness: operational when governance preserves stop authority. Confidence: strong as GShips policy.\n- **L12-02-E — Rescue cannot be withheld for experimental realism.** Basis: normative rights and research-ethics boundary. Readiness: operational. Confidence: strong; legal and ethics review remains required for real programs.\n\nLinked corpus claims: `claim-18-01`, `claim-18-10`, `claim-19-03`, and `claim-19-10`. See the claim registry for each record's current evidence grade and independent-review state.\n\n## Assumptions and limits\n\n- The seven rungs are a GShips editorial synthesis, not a NASA or international standard.\n- Current Moon-to-Mars documents establish a planning precedent, not proof of sustained lunar or Martian settlement.\n- Flight demonstrations will depend on program budgets, law, launch access, and international conditions not modeled here.\n- A test can produce important evidence even when it fails its success criterion.\n- Human participation requires independent medical, ethics, accessibility, labor, and rights review.\n- “Autonomous” always needs a declared time, function, environment, and outside-support boundary.\n\n## What would change this conclusion?\n\nNew test methods may reorder or split rungs. A capability demonstrated safely at scale could skip redundant tests, while a newly discovered coupling could require stepping back. Cheaper robotic evidence could delay human exposure. Better propulsion might change useful distances but would not erase rights, validation, or arrival obligations. Evidence that Solar System habitats deliver the desired resilience and discovery without a stellar voyage could make “do not launch” the best endpoint.\n\n## Sources and locators\n\n- [NASA — Moon to Mars Strategy and Objectives](https://www.nasa.gov/moontomarsarchitecture-strategyandobjectives/). Locator: objectives-first approach, ten objective areas, and annual architecture evolution; accessed 2026-07-25.\n- [NASA — Moon to Mars Architecture Definition Documents](https://www.nasa.gov/moontomarsarchitecture-architecturedefinitiondocuments/). Locator: Revision B, objective mappings, architecture-driven technology and data gaps; accessed 2026-07-25.\n- [NASA NTRS — Moon to Mars Architecture Definition Document Revision B](https://ntrs.nasa.gov/citations/20240015571). Locator: architecture definition, objective decomposition, functions, use cases, segments, and explicit non-manifest boundary; published 2024.\n- [NASA Systems Engineering Handbook](https://www.nasa.gov/wp-content/uploads/2018/09/nasa_systems_engineering_handbook_0.pdf). Locator: lifecycle, stakeholder expectations, requirements, technical assessment, verification, validation, risk, and decision analysis; NASA/SP-2016-6105 Rev 2.\n- [NASA — Architecture white papers](https://www.nasa.gov/moontomarsarchitecture-whitepapers/). Locator: data gaps, integrated lunar power, communications and navigation, cargo, mobility, and planetary protection; accessed 2026-07-25.\n- [NASA — ISS Water Recovery Milestone](https://www.nasa.gov/missions/station/iss-research/nasa-achieves-water-recovery-milestone-on-international-space-station/). Locator: operational regenerative-water evidence and system boundary; accessed 2026-07-25.\n- [NIST — AI RMF Generative AI Profile](https://doi.org/10.6028/NIST.AI.600-1). Locator: governance, content provenance, predeployment testing, incident disclosure, and generative-AI risk treatment; NIST AI 600-1, 2024.\n\n## Editorial record\n\n- Prepared by: GShips Project\n- Last edited: 2026-07-25\n- Required review: systems architecture, test and verification, human spaceflight, logistics, reliability, planetary protection, and governance\n- Conflicts: Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, customer, sponsor, partner, or space-agency relationship currently exists\n- Corrections: [Suggest a correction](https://gships.dammonburden.com/corrections)\n"
      }
    },
    {
      "recordType": "academy-lesson",
      "recordId": "lesson-12-03",
      "title": "Who is already building the pieces?",
      "publicPath": "/academy/precursors-and-action/ecosystem-map",
      "recordFingerprint": "8a39ce740d4b81fc4e0a52ee731960bfc6c0a8faced8ed9196ea61d57c1f7e57",
      "reviewRequirements": {
        "minimumIndependentApprovals": 1,
        "highConsequenceDomains": [],
        "requiredDomainCodes": [],
        "requiredComplementaryScopeGroups": [
          {
            "id": "bounded-competence",
            "scopeClass": "bounded-competence",
            "oneOf": [
              "institution-building",
              "systems-engineering"
            ]
          }
        ],
        "unresolvedNegativeFindingBlocksPublication": true
      },
      "referenceIds": [],
      "snapshot": {
        "slug": "ecosystem-map",
        "title": "Who is already building the pieces?",
        "summary": "Map capabilities, evidence, facilities, and entry paths across institutions without confusing an index with a partnership.",
        "minutes": 28,
        "level": "Foundation",
        "id": "lesson-12-03",
        "trackSlug": "precursors-and-action",
        "trackTitle": "Precursors, partners & action",
        "href": "/academy/precursors-and-action/ecosystem-map",
        "preparedBy": "GShips Project",
        "lastEditedAt": "2026-07-25",
        "reviewRequiredDomains": [
          "research-infrastructure",
          "systems-engineering",
          "institutional-design",
          "public-interest-governance",
          "procurement",
          "science-policy"
        ],
        "claimIds": [
          "claim-20-01",
          "claim-20-03",
          "claim-20-08",
          "claim-20-09"
        ],
        "exactMdx": "---\nid: \"lesson-12-03\"\ntrack: \"precursors-and-action\"\nslug: \"ecosystem-map\"\ntitle: \"Who is already building the pieces?\"\nsummary: \"Map capabilities, evidence, facilities, and entry paths across institutions without confusing an index with a partnership.\"\nminutes: 28\nlevel: \"Foundation\"\npreparedBy: \"GShips Project\"\nlastEditedAt: \"2026-07-25\"\nconflicts: \"Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, customer, sponsor, partner, or indexed-organization relationship currently exists.\"\nreviewRequiredDomains: \"research-infrastructure, systems-engineering, institutional-design, public-interest-governance, procurement, science-policy\"\nclaimIds: \"claim-20-01, claim-20-03, claim-20-08, claim-20-09\"\n---\n\n# Who is already building the pieces?\n\n> **Evidence boundary:** This is a cited substantive editorial draft and an ecosystem-mapping method, not a partner list, endorsement, procurement recommendation, or claim of access. Organizations mentioned are independent. GShips has no relationship with them unless a future disclosure says otherwise.\n\n## Plain-language summary\n\nNo organization is building a complete generation ship. Many organizations are already building, operating, regulating, researching, funding, or teaching pieces of the problem: power systems, water treatment, controlled agriculture, remote medicine, robotics, materials, astronomy, long-duration operations, software assurance, standards, rights, and public infrastructure.\n\nThe leadership challenge is not to assemble a long logo wall. It is to make capability gaps and possible collaboration paths legible.\n\nA useful ecosystem map answers:\n\n- What capability does this organization actually possess?\n- What evidence is public?\n- At what scale and maturity?\n- Who benefits from the work today?\n- What facility, program, job, working group, procurement, dataset, or event offers a legitimate entry point?\n- What risks, restrictions, conflicts, and dual-use boundaries apply?\n- Is the organization merely indexed, or is there a formal relationship?\n\nThe map should help a student find a field, an expert find a bounded review task, a facility operator find a test need, and a founder find a credible next conversation. It must never imply that being indexed makes an organization a supporter of GShips.\n\n## Map capabilities before organizations\n\nStart with the twenty GShips capability areas and decompose each into testable functions. “Life support” is too broad. Useful subfunctions include water collection, contaminant removal, microbial monitoring, trace-gas control, oxygen generation, carbon recovery, nutrient processing, crop production, waste stabilization, sensors, maintenance, and degraded operation.\n\nThen link each function to several institutional roles:\n\n- **Basic research:** mechanisms, measurements, theory, and datasets.\n- **Applied research and prototyping:** hardware, software, experiments, and integration.\n- **Operations:** facilities and systems that work under real duty cycles.\n- **Standards and assurance:** requirements, verification methods, safety cases, interoperability, and incident learning.\n- **Public-interest and affected-community work:** rights, environmental justice, labor, accessibility, consent, and accountability.\n- **Education and workforce:** courses, apprenticeships, laboratories, and professional formation.\n- **Funding and procurement:** grants, contracts, user facilities, prizes, and purchasing pathways.\n- **Regulation and governance:** safety, environmental review, spectrum, nuclear, export, medical, privacy, and planetary-protection boundaries.\n\nAn organization may occupy several roles. Its marketing category should not substitute for evidence.\n\n## Use existing taxonomies, but do not inherit their blind spots\n\nNASA’s 2024 Technology Taxonomy organizes mission-relevant work into seventeen areas including propulsion, flight computing, power, robotics, communications and navigation, health and habitation, autonomous systems, software and modeling, manufacturing, surface systems, thermal management, and guidance/navigation/control. NASA uses the taxonomy to communicate and track its technology portfolio.\n\nThis is valuable scaffolding. It is not a complete generation-ship ontology. It is mission- and technology-centered, while a multigenerational habitat also needs law, childhood, disability, political legitimacy, labor, culture, education, economics, family life, archives, and the standing option not to travel.\n\nThe map should therefore crosswalk rather than replace:\n\n- NASA technology categories;\n- systems-engineering functions and lifecycle stages;\n- medical and public-health disciplines;\n- ecological and agricultural domains;\n- industrial and critical-infrastructure capabilities;\n- cybersecurity and AI assurance;\n- humanities, social science, law, ethics, labor, and disability expertise;\n- affected-public knowledge.\n\nIf a taxonomy makes a necessary stakeholder invisible, change the taxonomy.\n\n## Institutional families\n\n### Space agencies and mission organizations\n\nNASA, ESA, and other civil agencies publish mission records, standards, technology programs, architecture documents, datasets, solicitations, and lessons from operations. These sources help establish what has flown, what is being tested, and what remains proposed.\n\nDo not treat an agency as one potential partner. A large agency contains centers, mission directorates, programs, facilities, procurement offices, safety authorities, public-affairs boundaries, and individual research groups. A useful record names the relevant unit and official path.\n\n### National laboratories and user facilities\n\nThe U.S. Department of Energy laboratory system and Office of Science user facilities hold capabilities in materials characterization, high-performance computing, energy systems, nuclear science, manufacturing, biology, chemistry, and large experimental infrastructure. NSF supports major and mid-scale research facilities spanning astronomy, oceans, Earth systems, biology, and computing.\n\n“User facility” is not shorthand for free access. Facilities have proposal processes, eligibility, schedules, costs, safety rules, publication terms, export controls, and limited capacity. A founder should arrive with a precise scientific question and a credible team, not a vague request to “test a starship.”\n\n### Universities and research institutes\n\nUniversities can connect disciplines that firms and agencies separate. They also have institutional review boards, research-compliance offices, student protections, publication norms, technology-transfer interests, and funding constraints.\n\nMap laboratories and principal capabilities, not only university brands. Include teaching and early-career routes. A project that depends on a professor but offers no benefit or credit to students is not a responsible partnership model.\n\n### Companies and operators\n\nCompanies can bring manufacturing discipline, supply chains, reliability data, products, operators, and customers. They also have confidential information, commercial incentives, procurement constraints, and legitimate reasons not to disclose every failure.\n\nDistinguish:\n\n- a product already operating in a relevant environment;\n- a prototype or funded development program;\n- a press release or concept;\n- a capability inferred from adjacent work;\n- a capability explicitly unavailable for collaboration.\n\nNever convert a vendor relationship into editorial preference.\n\n### Professional societies and standards communities\n\nWorking groups can offer vocabulary, peer review, reference models, standards, conferences, and cross-institutional networks. INCOSE’s Space Systems Working Group, for example, states that it promotes systems-engineering practice in space and develops a CubeSat reference model. That is an inspectable entry path, not endorsement of GShips.\n\nStandards work is slow and valuable. A project can contribute small artifacts—failure taxonomies, interface definitions, test scenarios, evidence schemas—without asking a standards body to adopt a generation-ship agenda.\n\n### Civil society, labor, rights, and communities\n\nTechnical maps systematically underrepresent people who bear risk. Residents near test facilities, launch sites, mines, energy projects, biological work, or waste streams are not “nontechnical stakeholders.” Workers who maintain infrastructure often know failure modes absent from design records. Disability communities can reveal exclusion in interfaces and emergency plans. Indigenous governance and environmental expertise matter where land, resources, heritage, and planetary narratives are involved.\n\nThese groups should shape requirements early, not approve a finished plan.\n\n## A profile that earns its place\n\nEvery organization profile should include:\n\n- stable name and official URL;\n- entity type and relevant unit;\n- geography and operating scope;\n- capability tags with evidence;\n- facility, program, dataset, product, standard, or publication supporting each tag;\n- readiness and scale boundary;\n- public-benefit relevance;\n- potential collaboration mechanism;\n- eligibility, cost, schedule, and access limits when known;\n- export, classification, privacy, medical, environmental, or dual-use constraints;\n- conflicts and sponsorship disclosure;\n- freshness date;\n- relationship state: indexed only, contacted, exploratory, formal, former, or declined;\n- what would change the profile.\n\nThe default state is **indexed only**.\n\n## Rank tasks, not prestige\n\nThere is no universally “top” organization. The best potential collaborator depends on the next bounded task.\n\nFor a water-contaminant challenge, rank facilities by relevant influent range, instrumentation, safe operating scale, publication rights, and operator expertise. For a governance curriculum, rank by rights knowledge, plural participation, independence, and teaching capacity. For a materials problem, rank by characterization method, sample constraints, and ability to reproduce failure.\n\nA defensible match score can be expressed as separate dimensions:\n\n```text\ntask fit\nevidence relevance\naccess feasibility\npublic-benefit alignment\nindependence and conflict risk\nrights and environmental compatibility\ndual-use risk\nlearning value if the test fails\n```\n\nDo not collapse vetoes into an average. A technically excellent facility may be unsuitable if the work requires offensive integration, coercive research, hidden environmental harm, or an implied endorsement.\n\n## Entry paths for humans\n\nPeople can enter the work without joining a hypothetical starship company:\n\n- study a needed discipline and publish careful work;\n- apply to a user facility with a bounded research question;\n- join an analog, laboratory, infrastructure operator, standards group, or public-interest organization;\n- contribute to open datasets, replication, negative-results repositories, and accessible education;\n- work in water, energy, food, health, manufacturing, cybersecurity, disaster response, or institutional design;\n- review one claim within a real area of expertise;\n- organize a cross-disciplinary workshop with explicit deliverables and dissent;\n- build an Earthside product whose customers exist now.\n\nThe leadership task is to make these paths visible and give credit to the institutions already doing the work.\n\n## Avoid ecosystem theater\n\nWarning signs include:\n\n- counting logos instead of verified capabilities;\n- naming famous people without a role or consent;\n- calling an indexed organization a partner;\n- ranking sponsors more highly;\n- hiding failed outreach;\n- treating conference attendance as a relationship;\n- overcontacting the same institution through many units;\n- asking experts for broad unpaid validation;\n- requesting restricted or classified work that violates the civil boundary;\n- using “humanity” to bypass local authority.\n\nA credible project can say: “We have no relationship with this organization. We index its official work because it is relevant to this capability.”\n\n## Evidence ledger\n\n- **L12-03-A — Enabling capabilities are distributed.** Basis: observed institutional portfolios. Readiness: operational across many bounded domains. Confidence: strong; integrated generation-ship readiness is not implied.\n- **L12-03-B — Capability-first mapping is more actionable than a logo list.** Basis: modeled information architecture and normative editorial policy. Readiness: operational. Confidence: supported.\n- **L12-03-C — Existing taxonomies need social and institutional extensions.** Basis: observed scope comparison. Readiness: operational as mapping work. Confidence: strong.\n- **L12-03-D — Potential-partner ranking must be task-specific and evidence-backed.** Basis: normative governance rule. Readiness: operational. Confidence: strong as GShips policy.\n- **L12-03-E — Indexing never establishes a relationship.** Basis: factual and normative disclosure boundary. Readiness: operational. Confidence: strong.\n\nLinked corpus claims: `claim-20-01`, `claim-20-03`, `claim-20-08`, and `claim-20-09`. See the claim registry for each record's current evidence grade and independent-review state.\n\n## Assumptions and limits\n\n- Official portfolio pages show stated capabilities, not independent performance audits.\n- Organizations, programs, eligibility, leaders, and URLs change; profiles require periodic review.\n- Public sources may omit confidential, restricted, failed, or discontinued work.\n- A collaboration path may be unavailable even when technical fit is high.\n- The map is English-first and institution-heavy; translation and underrepresented-community review remain needed.\n- Legal, procurement, export, medical, and research-ethics advice must come from qualified professionals in a real project.\n\n## What would change this conclusion?\n\nA verified central program with broad capability ownership would change parts of the coordination map, but not the need for independent review and affected-public authority. Formal agreements would change specific relationship states only after disclosure authorization. Evidence that a profile is stale, promotional, harmful, or wrong should narrow or remove it. New taxonomies, facilities, community institutions, and open programs should be incorporated when they improve a real task—not merely the index count.\n\n## Sources and locators\n\n- [NASA — 2024 Technology Taxonomy](https://www.nasa.gov/otps/2024-nasa-technology-taxonomy/). Locator: purpose, three-level structure, seventeen technology areas, changes, and TechPort use; accessed 2026-07-25.\n- [NASA — TechPort 4.0](https://www.nasa.gov/directorates/stmd/five-ways-to-explore-nasas-portfolio-of-technologies-with-techport-4-0/). Locator: public portfolio search, fields, taxonomy, and funding-opportunity functions; accessed 2026-07-25.\n- [U.S. Department of Energy — Office of Science](https://www.energy.gov/science/office-science). Locator: national laboratories, user facilities, research areas, workforce, and funding paths; accessed 2026-07-25.\n- [U.S. National Science Foundation — Research Infrastructure](https://www.nsf.gov/od/ori/research-infrastructure). Locator: major facilities, mid-scale infrastructure, lifecycle stages, research, education, data, and workforce roles; accessed 2026-07-25.\n- [INCOSE — Space Systems Working Group](https://www.incose.org/group/space-systems-working-group/). Locator: mission, scope, networking, professional information, and CubeSat reference-model activity; accessed 2026-07-25.\n- [National Academies — The Science and Practice of Team Science](https://nap.nationalacademies.org/resource/29043/interactive/). Locator: collective leadership, team charters, psychological safety, collaboration infrastructure, evaluation, and institutional support; consensus study highlights, 2025.\n- [NASA Systems Engineering Handbook](https://www.nasa.gov/wp-content/uploads/2018/09/nasa_systems_engineering_handbook_0.pdf). Locator: stakeholder expectations, interfaces, technical data, configuration, decision analysis, verification, validation, and independent assessment.\n\n## Editorial record\n\n- Prepared by: GShips Project\n- Last edited: 2026-07-25\n- Required review: research infrastructure, systems engineering, institutional design, public-interest governance, procurement, and science policy\n- Conflicts: Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, customer, sponsor, partner, or indexed-organization relationship currently exists\n- Corrections: [Suggest a correction](https://gships.dammonburden.com/corrections)\n"
      }
    },
    {
      "recordType": "academy-lesson",
      "recordId": "lesson-12-04",
      "title": "Products before starships",
      "publicPath": "/academy/precursors-and-action/venture-wedges",
      "recordFingerprint": "80d95f17c3fae1175c54eb9aa53320039c46555b077ef90764d8bd299082bb45",
      "reviewRequirements": {
        "minimumIndependentApprovals": 1,
        "highConsequenceDomains": [],
        "requiredDomainCodes": [],
        "requiredComplementaryScopeGroups": [
          {
            "id": "bounded-competence",
            "scopeClass": "bounded-competence",
            "oneOf": [
              "institution-building",
              "systems-engineering"
            ]
          }
        ],
        "unresolvedNegativeFindingBlocksPublication": true
      },
      "referenceIds": [],
      "snapshot": {
        "slug": "venture-wedges",
        "title": "Products before starships",
        "summary": "Choose Earthside and Solar System products with real users, measurable capability gaps, safe boundaries, and value even if no starship launches.",
        "minutes": 30,
        "level": "Foundation",
        "id": "lesson-12-04",
        "trackSlug": "precursors-and-action",
        "trackTitle": "Precursors, partners & action",
        "href": "/academy/precursors-and-action/venture-wedges",
        "preparedBy": "GShips Project",
        "lastEditedAt": "2026-07-25",
        "reviewRequiredDomains": [
          "venture-design",
          "critical-infrastructure",
          "software-assurance",
          "remote-medicine",
          "life-support",
          "manufacturing",
          "public-benefit-governance"
        ],
        "claimIds": [
          "claim-20-04",
          "claim-20-05",
          "claim-20-06",
          "claim-20-10"
        ],
        "exactMdx": "---\nid: \"lesson-12-04\"\ntrack: \"precursors-and-action\"\nslug: \"venture-wedges\"\ntitle: \"Products before starships\"\nsummary: \"Choose Earthside and Solar System products with real users, measurable capability gaps, safe boundaries, and value even if no starship launches.\"\nminutes: 30\nlevel: \"Foundation\"\npreparedBy: \"GShips Project\"\nlastEditedAt: \"2026-07-25\"\nconflicts: \"Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, revenue, customer, sponsor, investor, or partner relationship currently exists.\"\nreviewRequiredDomains: \"venture-design, critical-infrastructure, software-assurance, remote-medicine, life-support, manufacturing, public-benefit-governance\"\nclaimIds: \"claim-20-04, claim-20-05, claim-20-06, claim-20-10\"\n---\n\n# Products before starships\n\n> **Evidence boundary:** This is a cited substantive editorial draft and a venture-screening method, not investment, medical, legal, regulatory, or procurement advice. GShips has no customers or validated demand. Product examples are hypotheses to test, not claims that a market exists.\n\n## Plain-language summary\n\n“Generation ships” are not a market. A founder cannot responsibly build a company on the assumption that a civilization-scale interstellar vehicle will be ordered soon.\n\nThe useful company question is smaller:\n\n> What product helps a real person or institution manage a measurable long-duration resilience problem now, while generating evidence relevant to more autonomous habitats?\n\nCandidate areas include assurance software, maintenance and spares planning, offline knowledge support, resilient power, water and life-support operations, remote care, circular manufacturing, and integrated test infrastructure. Each already has customers or public beneficiaries outside a generation ship. Each also has safety, regulation, cybersecurity, procurement, and incumbent alternatives that must be understood.\n\nThe product should remain worthwhile if the generation-ship research concludes “wait” or “never launch.”\n\n## The six tests for a responsible wedge\n\n### 1. A present user has a costly job\n\nName the operator, not an abstract market. Examples might include a remote facility manager, water-system operator, habitat-test director, microgrid engineer, maintenance planner, clinical team, disaster-response organization, or spacecraft integrator.\n\nWrite the job in observable terms:\n\n- decide which failure to address first;\n- understand which requirement or evidence is affected;\n- plan spares and maintenance under constrained logistics;\n- rehearse a degraded mode;\n- trace a procedure to a current source;\n- recover service after power, network, or supplier loss;\n- document why an operator overrode an automated recommendation.\n\n“Advance humanity” is a mission, not a purchasing job.\n\n### 2. The gap is measurable\n\nA wedge needs a baseline. Depending on the problem, measure:\n\n- time to locate applicable evidence;\n- unresolved requirement links;\n- false alarms and missed faults;\n- downtime and recovery time;\n- spare stockouts and obsolete parts;\n- water, energy, or material loss;\n- maintenance labor and rework;\n- incident reconstruction time;\n- percentage of critical operation available offline;\n- user error and accessibility barriers;\n- cost of an existing workflow.\n\nA founder should know what improvement would count and what result kills the thesis.\n\n### 3. The first product is bounded\n\nThe initial product should not control life-critical hardware, diagnose patients, decide reproduction, allocate political rights, or autonomously authorize dangerous actions.\n\nFor Autonomous Habitat Assurance, a bounded first product could:\n\n- connect requirements, evidence, assumptions, tests, failures, and maintenance records;\n- compare digital-twin scenarios without presenting a model as reality;\n- generate a spares or inspection plan for human approval;\n- provide offline cited retrieval over approved documents;\n- produce an auditable incident timeline;\n- show disagreement and missing evidence.\n\nIt should not be the only copy of a procedure, the sole alarm path, or a hidden authority layer. Every critical function must retain a safe non-generative path.\n\n### 4. The Earthside value is independent\n\nResilient microgrids can support critical loads during outages and deliver ordinary-day services. DOE describes islanding and black-start use cases, along with “blue sky” grid value. Water recovery, contaminant sensing, and process control can serve remote communities, disaster response, industry, and controlled agriculture. Maintenance assurance can serve infrastructure that already struggles with aging equipment and sparse expertise.\n\nThe Earthside deployment must not treat a community as a convenient Mars analog. The community defines its needs, owns appropriate data, shares benefits, and can decline the experiment.\n\n### 5. The regulatory and assurance path is visible\n\nRemote medicine is not simply a chat interface. In the United States, FDA guidance distinguishes categories of clinical decision-support software and explains that some software functions remain medical devices. Intended use, user, explainability, and how an output affects a healthcare decision matter.\n\nLikewise:\n\n- energy products face utility, electrical, interconnection, fire, and local rules;\n- water products face public-health and environmental requirements;\n- aerospace products face program assurance, export, safety, and configuration controls;\n- cybersecurity products handle sensitive infrastructure information;\n- AI products need model, data, human-factors, security, and incident governance.\n\n“Decision support” is not a magic phrase that eliminates responsibility.\n\n### 6. The work has a stop condition\n\nStop or redirect when:\n\n- interviews reveal no urgent user job;\n- the buyer and user cannot be aligned safely;\n- required data cannot be lawfully or ethically obtained;\n- a simpler non-AI tool performs as well;\n- integration cost overwhelms the benefit;\n- operators cannot audit or override the result;\n- the product increases surveillance or concentrates dangerous authority;\n- a regulated path exceeds the company’s competence or resources;\n- present harms exceed speculative long-term value.\n\nKilling a bad wedge protects the broader mission.\n\n## Candidate wedge: Autonomous Habitat Assurance\n\nThe founder package proposes four linked product objects:\n\n1. **Evidence and requirements graph:** claims, requirements, sources, assumptions, tests, failures, owners, and review status.\n2. **Scenario and digital-twin registry:** models, configurations, inputs, outputs, calibration, divergence, and applicability boundaries.\n3. **Maintenance and spares planner:** failure modes, inspections, lead times, substitutes, tool dependencies, stock, and replenishment.\n4. **Offline auditable AI support:** cited retrieval and constrained assistance over approved local records, with provenance and non-AI fallbacks.\n\nThe narrow pilot hypothesis is not “AI will run a habitat.” It is:\n\n> A small operations or engineering team can reduce traceability and planning time without increasing critical decision error, data exposure, or authority ambiguity.\n\n### A pilot acceptance test\n\nUse synthetic or public data first. Give participants a bounded system, known faults, stale documents, contradictory evidence, and a supply constraint. Compare the proposed tool against their current workflow.\n\nMeasure:\n\n- correct evidence and requirement links;\n- unsupported assertions;\n- missing or wrong source locators;\n- time to produce a reviewable plan;\n- inappropriate automation reliance;\n- ability to work disconnected;\n- recovery after model removal or corruption;\n- operator comprehension and accessibility;\n- audit-log completeness;\n- security boundary violations.\n\nThe pilot fails if it invents critical evidence, conceals uncertainty, cannot operate without a hosted model, or makes the fallback workflow worse.\n\n## LLMs changed the cost curve—and the attack surface\n\nLLMs can make requirements, manuals, incidents, and cross-disciplinary literature more navigable. They can help create drafts, translate technical language, compare models, and preserve explanations during staff turnover.\n\nNIST’s Generative AI Profile identifies governance, content provenance, testing, incident disclosure, confabulation, data privacy, information security, human overreliance, and other risks relevant to such systems. A habitat-assurance product should assume:\n\n- retrieved documents can be poisoned;\n- model output can sound certain when wrong;\n- tool instructions can be injected;\n- hosted services can disappear;\n- model updates can change behavior;\n- operators can overtrust polished answers;\n- confidential infrastructure data can leak;\n- a shared model can create correlated failure.\n\nControls include signed approved corpora, deterministic retrieval views, source locators, sandboxed tools, least privilege, offline operation, version pinning, evaluation suites, incident reporting, manual approval, and a documented path that removes the model entirely.\n\n## Other wedge families\n\n### Resilient power and black start\n\nMicrogrid controls, load prioritization, storage planning, and black-start rehearsal have present users. The high-value work is often integration and operations, not a novel generator. A habitat analog can become a demanding customer for Earthside resilience tools.\n\nSafety boundary: power controls must be deterministic, independently protected, and tested against cyber and physical faults. A generative model should not close a breaker.\n\n### Water and regenerative-process assurance\n\nISS life support demonstrates high water recovery with multiple processors, sensors, filters, catalysts, and continuing maintenance. Earthside wedges might improve contaminant monitoring, membrane maintenance, recovery accounting, or operator training.\n\nSafety boundary: a recovery percentage cannot replace drinking-water quality, reject-stream handling, or public-health validation.\n\n### Remote-care logistics\n\nUseful products may focus on stock management, referral preparation, offline guidelines, device maintenance, translation, documentation, or communication under disruption.\n\nSafety boundary: do not claim diagnosis or treatment capability without qualified clinical leadership, evidence, regulatory analysis, privacy, and validation in the intended setting.\n\n### Circular maintenance and manufacturing\n\nProducts can map part criticality, obsolescence, inspection, substitution, tool dependencies, and repair evidence. A digital thread that survives supplier change may be more valuable than exotic in-space fabrication.\n\nSafety boundary: a printed part is not qualified because its geometry matches. Material, process, inspection, environment, and configuration determine acceptability.\n\n## Funding without mission capture\n\nNASA’s SBIR/STTR program illustrates staged non-dilutive funding for eligible U.S. small businesses and research-institution collaborators. Phase I examines feasibility; Phase II focuses on development, demonstration, and delivery. User facilities, grants, prizes, contracts, paid pilots, philanthropy, and equity financing have different incentives and restrictions.\n\nFunding source must never buy an evidence grade, partner ranking, or suppression of negative results. Defense-related funding requires the civil-and-defensive boundary, export review, and explicit rejection of autonomous weapons or offensive integration.\n\nA company should separate:\n\n- public editorial work;\n- open commons artifacts;\n- customer-confidential product work;\n- regulated data;\n- restricted or export-controlled information;\n- sponsor disclosures;\n- independent review authority.\n\n## Evidence ledger\n\n- **L12-04-A — The generation-ship market does not currently exist.** Basis: observed absence of a validated procurement category or customer program. Readiness: unknown for such a market. Confidence: strong for the current venture boundary; future programs could change it.\n- **L12-04-B — Near-term products need independent present value.** Basis: normative venture and public-benefit rule. Readiness: operational. Confidence: strong as GShips policy.\n- **L12-04-C — Assurance software can begin below the control layer.** Basis: proposed product architecture. Readiness: early research. Confidence: tentative until interviews and pilots.\n- **L12-04-D — LLM support adds both navigation value and correlated risk.** Basis: demonstrated general capability plus documented risk. Readiness: major scale-up for safety-relevant offline use. Confidence: supported.\n- **L12-04-E — Funding cannot buy editorial treatment.** Basis: normative independence policy. Readiness: operational when governance and disclosure enforce it. Confidence: strong.\n\nLinked corpus claims: `claim-20-04`, `claim-20-05`, `claim-20-06`, and `claim-20-10`. See the claim registry for each record's current evidence grade and independent-review state.\n\n## Assumptions and limits\n\n- No customer discovery has been conducted or is claimed.\n- Examples span different countries and regulatory systems; specific counsel is required for a real product.\n- Official funding pages change and do not guarantee eligibility or award.\n- The product thesis may fail; that is an acceptable discovery outcome.\n- Public-benefit claims require evidence from actual beneficiaries, not founder intent.\n- No medical, utility, water, or flight-critical deployment should occur on this lesson’s authority.\n\n## What would change this conclusion?\n\nRepeated interviews, paid pilots, independent evaluations, safe performance, and measurable user outcomes could support one wedge. Failure to outperform a spreadsheet, document system, conventional rules engine, or established vendor would weaken it. Regulatory or data barriers could narrow the product. Evidence that a product increases surveillance, unsafe automation, or mission hype should stop it. A future funded generation-ship program might create a direct market, but would not remove the need for Earthside benefit, assurance, and editorial independence.\n\n## Sources and locators\n\n- [NASA — SBIR/STTR Program](https://www.nasa.gov/sbir_sttr/). Locator: eligible small businesses, non-dilutive support, technology maturation, mission and commercialization intent; accessed 2026-07-25.\n- [NASA — SBIR/STTR Phase II](https://www.nasa.gov/sbir_sttr/phase-ii/). Locator: development, demonstration, delivery, and Phase-I eligibility boundary; accessed 2026-07-25.\n- [NIST — AI RMF Generative AI Profile](https://doi.org/10.6028/NIST.AI.600-1). Locator: risk taxonomy and actions for governance, provenance, testing, security, confabulation, privacy, and incident disclosure; 2024.\n- [NIST — Cybersecurity Framework 2.0](https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf). Locator: Govern, Identify, Protect, Detect, Respond, and Recover outcomes; 2024.\n- [U.S. Department of Energy — Power in the Storm](https://www.energy.gov/oe/articles/power-storm-capturing-value-microgrids-resilience). Locator: islanded operation, resilience, ordinary-day value, and community/customer use cases; published 2026.\n- [U.S. Department of Energy — Microgrids for Resiliency](https://www.energy.gov/sites/default/files/2024-01/28-01-2021_doe-voe-microgrids-for-resiliency-report-2.pdf). Locator: controller functions, black start, islanding, resynchronization, ownership, and operational lessons.\n- [NASA — ISS Water Recovery Milestone](https://www.nasa.gov/missions/station/iss-research/nasa-achieves-water-recovery-milestone-on-international-space-station/). Locator: water-recovery architecture, measurement, processing chain, and system boundary; accessed 2026-07-25.\n- [FDA — Clinical Decision Support Software Guidance](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/clinical-decision-support-software). Locator: intended use, healthcare-professional decision support, non-device criteria, and continuing device policies; reissued January 2026.\n\n## Editorial record\n\n- Prepared by: GShips Project\n- Last edited: 2026-07-25\n- Required review: venture design, critical infrastructure, software assurance, remote medicine, life support, manufacturing, and public-benefit governance\n- Conflicts: Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, revenue, customer, sponsor, investor, or partner relationship currently exists\n- Corrections: [Suggest a correction](https://gships.dammonburden.com/corrections)\n"
      }
    },
    {
      "recordType": "academy-lesson",
      "recordId": "lesson-12-05",
      "title": "Leadership as stewardship",
      "publicPath": "/academy/precursors-and-action/leadership-practice",
      "recordFingerprint": "46fd7ce7f6a65c875954f0506d6134f750154ac21720b0f7652d7ef1184711dd",
      "reviewRequirements": {
        "minimumIndependentApprovals": 1,
        "highConsequenceDomains": [],
        "requiredDomainCodes": [],
        "requiredComplementaryScopeGroups": [
          {
            "id": "bounded-competence",
            "scopeClass": "bounded-competence",
            "oneOf": [
              "institution-building",
              "systems-engineering"
            ]
          }
        ],
        "unresolvedNegativeFindingBlocksPublication": true
      },
      "referenceIds": [],
      "snapshot": {
        "slug": "leadership-practice",
        "title": "Leadership as stewardship",
        "summary": "Build credibility through useful work, transparent evidence, plural teams, rights, succession, and the practiced ability to stop.",
        "minutes": 32,
        "level": "Foundation",
        "id": "lesson-12-05",
        "trackSlug": "precursors-and-action",
        "trackTitle": "Precursors, partners & action",
        "href": "/academy/precursors-and-action/leadership-practice",
        "preparedBy": "GShips Project",
        "lastEditedAt": "2026-07-25",
        "reviewRequiredDomains": [
          "institution-building",
          "team-science",
          "public-benefit-governance",
          "ethics",
          "labor",
          "disability",
          "systems-leadership",
          "conflict-resolution"
        ],
        "claimIds": [
          "claim-20-01",
          "claim-20-07",
          "claim-20-08",
          "claim-20-10"
        ],
        "exactMdx": "---\nid: \"lesson-12-05\"\ntrack: \"precursors-and-action\"\nslug: \"leadership-practice\"\ntitle: \"Leadership as stewardship\"\nsummary: \"Build credibility through useful work, transparent evidence, plural teams, rights, succession, and the practiced ability to stop.\"\nminutes: 32\nlevel: \"Foundation\"\npreparedBy: \"GShips Project\"\nlastEditedAt: \"2026-07-25\"\nconflicts: \"Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, revenue, customer, sponsor, investor, partner, or leadership appointment currently exists.\"\nreviewRequiredDomains: \"institution-building, team-science, public-benefit-governance, ethics, labor, disability, systems-leadership, conflict-resolution\"\nclaimIds: \"claim-20-01, claim-20-07, claim-20-08, claim-20-10\"\n---\n\n# Leadership as stewardship\n\n> **Evidence boundary:** This is a cited substantive editorial draft, not proof that the project, maintainer, or reader is qualified to lead a generation-ship program. Leadership claims must be earned through bounded work, peer and public accountability, succession, and affected-person participation. Independent review is pending.\n\n## Plain-language summary\n\nThe person who speaks most confidently about humanity’s future is not therefore qualified to lead it.\n\nA generation-ship-scale venture touches medicine, childhood, law, ecology, power, manufacturing, cybersecurity, culture, labor, astronomy, and the rights of people who did not choose the founder. No individual can master or legitimately own that whole problem. The durable leadership product is an institution that:\n\n- learns faster than it promotes;\n- publishes uncertainty and failure;\n- protects dissent and whistleblowing;\n- shares authority with relevant experts and affected people;\n- separates evidence from fundraising;\n- develops successors;\n- delivers present public value;\n- preserves the option to pause or stop.\n\nLeadership begins long before a company, habitat, or starship. It begins with one useful, reviewable contribution and the willingness to let better evidence change the story.\n\n## The founder is not the mission\n\nCharismatic-founder dependence is a technical and governance failure mode. If an organization cannot survive the founder’s absence, it cannot credibly study century-scale institutions.\n\nThe founder may contribute:\n\n- an integrative thesis;\n- capital or fundraising;\n- coordination;\n- product judgment;\n- public explanation;\n- early culture;\n- willingness to take risk.\n\nThe founder must not personally own:\n\n- scientific truth;\n- medical or reproductive authority;\n- the rights charter;\n- incident adjudication involving the founder;\n- editorial grades on sponsored work;\n- all partner relationships;\n- all financial controls;\n- succession;\n- the decision to continue after a stop rule.\n\nSeparate roles and escalation paths early. A board, review council, ethics function, safety authority, worker voice, resident or affected-public forum, and editorial process should not all report to the same unreviewable person.\n\n## Leadership at four scales\n\n### Self: evidence habits\n\nA prospective leader should be able to:\n\n- distinguish observation, demonstration, model, proposal, and value judgment;\n- state assumptions and confidence;\n- trace claims to primary sources;\n- identify what would change a conclusion;\n- correct public errors;\n- separate private interest from public evidence;\n- say “I do not know” without losing direction;\n- decline work outside the project’s rights or dual-use boundary.\n\nThese are not branding exercises. They are daily operating controls.\n\n### Team: collaboration and conflict\n\nThe National Academies’ 2025 team-science study emphasizes collective leadership, explicit team charters, psychological safety, communication norms, mentorship, and evaluation. Cross-disciplinary work needs more structure, not less.\n\nA team charter should cover:\n\n- purpose and current scope;\n- roles and decision rights;\n- authorship, credit, and compensation;\n- meeting and documentation norms;\n- data and confidentiality;\n- conflict and appeal;\n- respectful conduct and accessibility;\n- safety and stop authority;\n- sponsor disclosure;\n- departure, handover, and succession.\n\nPsychological safety does not mean agreement or comfort. It means people can raise uncertainty, bad news, and dissent without retaliation. Safety-critical teams also need technical challenge: a respectful team that cannot confront a weak model is not safe.\n\n### Institution: checks that outlast people\n\nInstitutional leadership creates:\n\n- versioned requirements and evidence;\n- independent review;\n- configuration and change control;\n- incident learning;\n- financial and sponsor transparency;\n- privacy and data minimization;\n- accessible participation;\n- protected reporting;\n- leadership rotation and emergency succession;\n- dissolution, archive, and asset-transfer rules.\n\nNASA systems engineering treats stakeholder expectations, requirements, verification, validation, technical assessment, decision analysis, configuration, and data management as linked lifecycle work. A GShips institution should apply that discipline to its own governance: define what the institution is for, who its stakeholders are, how performance is measured, and what evidence shows that it remains legitimate.\n\n### Field: commons and plural ownership\n\nThe generation-ship problem is too broad for vertical integration. Field leadership invests in shared language, open reference scenarios, negative-results repositories, test infrastructure, education, interoperability, and reproducible evidence that many organizations can use.\n\nThe commons should not become a funnel into one company. Commercial product work can coexist with public knowledge only with disclosed boundaries, fair access, independent editorial authority, and clear licenses.\n\n## A 30/90/365 practice\n\n### First 30 days: learn and bound\n\n- Write the thesis and the reasons it may be wrong.\n- Adopt public-benefit and civil/defensive boundaries.\n- Select one narrow capability gap with a present beneficiary.\n- Read primary sources and map stakeholders.\n- Publish an evidence policy and correction path.\n- Begin a conflict register.\n- Identify missing voices, especially operators and affected communities.\n- Do not incorporate, recruit a grand council, announce partners, or promise a launch on momentum alone.\n\nEvidence of progress is not follower count. It is a reviewable thesis, clear red lines, a map of unknowns, and one credible next test.\n\n### First 90 days: test usefulness\n\n- Conduct authorized, non-leading discovery interviews.\n- Build a small public or synthetic-data prototype.\n- Compare it with the current workflow and simpler alternatives.\n- Recruit bounded advisors with explicit scope and compensation or credit.\n- Ask domain reviewers to review claims, not endorse the whole project.\n- Publish negative results and change the roadmap.\n- Draft succession, authorship, disclosure, and incident rules.\n- Choose one event because it advances a specific task.\n\nEvidence of progress is a measured user problem, a safer or faster workflow, reviewed claims, and a list of killed assumptions.\n\n### First 365 days: build an institution, not a persona\n\n- Deliver an Earthside pilot with measurable benefit and no inflated starship claim.\n- Maintain a reviewed public knowledge corpus.\n- Establish independent technical, ethics, security, accessibility, and editorial review appropriate to actual work.\n- Create financial controls, board responsibilities, worker protections, and founder-recusal rules if an entity exists.\n- Exercise an incident, leadership absence, data restore, and project-stop scenario.\n- Develop at least two people who can lead major functions without the founder.\n- Publish an annual evidence, conflicts, corrections, failures, and public-benefit report.\n\nEvidence of progress is that the work continues safely when the founder leaves the room.\n\n## Expertise without expert theater\n\nAn expert should be asked:\n\n- to review a bounded claim or artifact;\n- within a named domain;\n- with sources and assumptions visible;\n- for a defined time and credit or compensation;\n- with conflicts disclosed;\n- without being turned into a project-wide endorser.\n\n“Advisory board” pages often overstate relationships. An advisor’s name should not appear publicly without permission and a current role definition. A single conversation is not advisory service. Event co-attendance is not collaboration.\n\nThe project should also distinguish credential from relevance. A maintainer, nurse, farmer, operator, machinist, teacher, disabled resident, or community organizer may hold critical knowledge not represented by prestige rankings.\n\n## LLMs and leadership\n\nLLMs make it easier to draft, synthesize, translate, simulate stakeholder questions, and maintain a large evidence graph. They also make it easier to create the appearance of depth without accountable expertise.\n\nLeadership rules for AI-assisted work:\n\n- disclose material AI assistance where relevant;\n- verify sources and locators;\n- never fabricate reviewers, interviews, relationships, or consensus;\n- keep private and restricted data out of unauthorized models;\n- record model and prompt provenance for critical artifacts when feasible;\n- separate generated suggestions from approved requirements;\n- require human responsibility for decisions;\n- preserve non-AI access to critical records;\n- test for correlated error, automation bias, and tool injection;\n- let qualified reviewers reject the AI-produced frame.\n\nNIST’s Generative AI Profile makes governance, provenance, testing, human overreliance, privacy, information security, and incident disclosure part of risk management. A leader who uses AI to accelerate output must also fund the review and controls that acceleration demands.\n\n## Decision rights and vetoes\n\nNot every decision should use simple majority vote, founder decree, or averaged scoring.\n\nNoncompensatory vetoes include:\n\n- coercive reproduction or medical experimentation;\n- inherited corporate rule over residents;\n- denial of meaningful exit where exit is possible;\n- offensive weapons integration;\n- concealed high-consequence risk;\n- knowingly false partnership or evidence claims;\n- environmental or community harm that is merely priced into a benefit score;\n- a safety-critical system with no independent fallback.\n\nReal programs would need lawful, plural governance developed with the people affected. GShips cannot pre-authorize future residents or claim to speak for humanity.\n\n## Restraint is a leadership capability\n\nMegaprojects reward optimism, commitment, and public certainty. Long-horizon leadership must reward:\n\n- waiting for better evidence;\n- choosing a robotic precursor;\n- narrowing the mission;\n- returning resources to Earthside work;\n- cancelling a product;\n- declining a sponsor;\n- changing a public conclusion;\n- dissolving an institution that no longer serves its purpose.\n\nA stop decision is not automatically failure. Continuing after the legitimate basis has disappeared is.\n\n## Evidence ledger\n\n- **L12-05-A — No individual can integrate or legitimately own the full problem.** Basis: observed disciplinary and institutional breadth plus normative rights boundary. Readiness: operational as organizational design. Confidence: strong.\n- **L12-05-B — Collective leadership and explicit collaboration structures support team science.** Basis: consensus synthesis. Readiness: operational. Confidence: supported; local effectiveness must be evaluated. Support: National Academies 2025.\n- **L12-05-C — Founder dependence is incompatible with century-scale credibility.** Basis: modeled continuity risk and normative governance. Readiness: operational to mitigate through succession and controls. Confidence: strong.\n- **L12-05-D — AI acceleration increases the need for provenance and review.** Basis: observed capability and documented risk. Readiness: operational controls exist, but safety-relevant use remains a major scale-up. Confidence: supported.\n- **L12-05-E — The institution must preserve pause, stop, and dissolution.** Basis: normative anti-escalation policy. Readiness: operational when embedded in governance. Confidence: strong as GShips policy.\n\nLinked corpus claims: `claim-20-01`, `claim-20-07`, `claim-20-08`, and `claim-20-10`. See the claim registry for each record's current evidence grade and independent-review state.\n\n## Assumptions and limits\n\n- Leadership research does not supply one universal team design.\n- The 30/90/365 sequence is a GShips founder practice, not an employment or legal standard.\n- Real entities require jurisdiction-specific corporate, labor, tax, nonprofit, privacy, safety, and fiduciary advice.\n- Institutional documents do not create psychological safety unless behavior, incentives, and enforcement support them.\n- Representation must include actual authority and resources, not images or advisory labels.\n- No current team, board, reviewer group, or public mandate is claimed.\n\n## What would change this conclusion?\n\nEvidence that a different leadership structure produces stronger safety, learning, rights, and continuity should change the model. Repeated failures to disclose, correct, share authority, protect dissent, or develop successors would be evidence that the founder or institution should not lead. A genuine public mandate and lawful governance could expand authority; a funding round or audience cannot. If the best outcome is an open commons, a smaller product company, or no organization at all, stewardship requires accepting it.\n\n## Sources and locators\n\n- [National Academies — The Science and Practice of Team Science](https://nap.nationalacademies.org/resource/29043/interactive/). Locator: collective leadership, team charters, psychological safety, mentorship, evaluation, collaboration technology, and institutional incentives; consensus study highlights, 2025.\n- [National Academies — Enhancing the Effectiveness of Team Science](https://nap.nationalacademies.org/catalog/19007/enhancing-the-effectiveness-of-team-science). Locator: team composition, leadership, collaboration planning, interdisciplinary integration, and institutional support; consensus study, 2015.\n- [NASA Systems Engineering Handbook](https://www.nasa.gov/wp-content/uploads/2018/09/nasa_systems_engineering_handbook_0.pdf). Locator: stakeholder expectations, lifecycle, requirements, technical assessment, decision analysis, configuration, data management, verification, and validation; NASA/SP-2016-6105 Rev 2.\n- [NASA — Systems Engineering Handbook Appendix](https://www.nasa.gov/reference/system-engineering-handbook-appendix/). Locator: stakeholder, standing review board, specification, verification-and-validation plan, responsibility, change authority, and acceptance testing; accessed 2026-07-25.\n- [NIST — AI RMF Generative AI Profile](https://doi.org/10.6028/NIST.AI.600-1). Locator: governance, provenance, testing, incident disclosure, privacy, security, confabulation, and human overreliance; 2024.\n- [NIST — Cybersecurity Framework 2.0](https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf). Locator: organizational profiles and Govern, Identify, Protect, Detect, Respond, and Recover outcomes; 2024.\n- [United Nations — Universal Declaration of Human Rights](https://www.un.org/en/about-us/universal-declaration-of-human-rights). Locator: equality, dignity, privacy, family, expression, association, participation, work, education, and remedy; used as a foundational rights reference, not a complete space-governance instrument.\n\n## Editorial record\n\n- Prepared by: GShips Project\n- Last edited: 2026-07-25\n- Required review: institution-building, team science, public-benefit governance, ethics, labor, disability, systems leadership, and conflict resolution\n- Conflicts: Maintainer intends to explore a commercial venture based on some GShips work; no entity, funding, revenue, customer, sponsor, investor, partner, or leadership appointment currently exists\n- Corrections: [Suggest a correction](https://gships.dammonburden.com/corrections)\n"
      }
    }
  ],
  "linkedRecords": [
    {
      "recordType": "claim",
      "recordId": "claim-18-01",
      "title": "Worldship capability must climb a transparent proof ladder from components to integrated analogs to autonomous space habitats; no single analog validates the whole mission.",
      "publicPath": "/claims/claim-18-01",
      "recordFingerprint": "77117d77c9cb8341e62b6814aa513f9a9eac87ced6ba1c1437f0579b4b8f8bd6"
    },
    {
      "recordType": "claim",
      "recordId": "claim-18-02",
      "title": "ISS, HERA, CHAPEA, Concordia, Biosphere 2, MELiSSA, Lunar Palace, and habitat laboratories each test different slices.",
      "publicPath": "/claims/claim-18-02",
      "recordFingerprint": "c1a07e65803cf9368db208d581c604d0e94ff34fea2b3b68403d7853f0234cad"
    },
    {
      "recordType": "claim",
      "recordId": "claim-18-05",
      "title": "Short duration, small crew, Earth support, 1 g, and easy rescue limit transfer from present analogs.",
      "publicPath": "/claims/claim-18-05",
      "recordFingerprint": "68d0ab4d0f7a73ef2d7348837ebe78606482c52da7fbcaaebd6f505ef57bc7ee"
    },
    {
      "recordType": "claim",
      "recordId": "claim-18-10",
      "title": "Every claimed capability must identify its environment, duration, scale, intervention, failure history, evidence boundary, and next harder test.",
      "publicPath": "/claims/claim-18-10",
      "recordFingerprint": "e298befeb55ba21ccee84294ad8676ec7ae82e52d1ebe456ee4ed7f52d056f49"
    },
    {
      "recordType": "claim",
      "recordId": "claim-19-03",
      "title": "Solar System habitats can test many enabling systems with shorter communication and possible rescue, but do not directly validate centuries of duration, interstellar gas and dust, or multigenerational institutional continuity.",
      "publicPath": "/claims/claim-19-03",
      "recordFingerprint": "2f9d99d2205a1d1fc6cb6017c64ebba6a7855fe37d5107530e49906243030f9c"
    },
    {
      "recordType": "claim",
      "recordId": "claim-19-10",
      "title": "At every major stage, rerun launch, wait, habitat, probe, and do-not-go alternatives; treat pause or abandonment as valid outcomes.",
      "publicPath": "/claims/claim-19-10",
      "recordFingerprint": "47b15ed3c825ade63115963137b3e62f9392d2cde38ee2c97ce4bafb49f5eedf"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-01",
      "title": "The enduring product is an institution that can learn, publish failure, transfer leadership, fund useful modules, and coordinate many organizations without pretending one company can vertically integrate a civilization.",
      "publicPath": "/claims/claim-20-01",
      "recordFingerprint": "827e964c87481699e350c161167088452b1c36d96285ca284f925f2e35ad0f2c"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-03",
      "title": "NASA, ESA, DOE, universities, national labs, professional societies, startups, and analog facilities already own many enabling capabilities.",
      "publicPath": "/claims/claim-20-03",
      "recordFingerprint": "a70b9ffa91f2b35eecac74a26f48e0badafeee9c934186059ea15bd68e2e39dd"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-04",
      "title": "SBIR/STTR, user facilities, Space Act Agreements, prizes, philanthropy, venture capital, and paid studies provide staged funding paths.",
      "publicPath": "/claims/claim-20-04",
      "recordFingerprint": "deb1849794e646250119b3cf8d320e63e6e705c56f24bd2c681f15ad5ed03911"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-05",
      "title": "No procurement market for generation ships was identified in the reviewed corpus; any near-term product needs a separately validated customer and measurable Earth or Solar System outcome.",
      "publicPath": "/claims/claim-20-05",
      "recordFingerprint": "88a7262686e0cb6d7c9f94158edce798c0044a7b2f0356721b7a9928dbd6e48e"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-06",
      "title": "Open knowledge, public trust, proprietary product work, defense funding, export controls, and sponsor influence require explicit firewalls.",
      "publicPath": "/claims/claim-20-06",
      "recordFingerprint": "471e63c021974d31d5e871549f8cae2a51cf51dfcd96f5cdcabd6ff3442b4f43"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-07",
      "title": "Charismatic-founder dependence is incompatible with a century-scale mission.",
      "publicPath": "/claims/claim-20-07",
      "recordFingerprint": "facd0bea2a655bd3f62da9e5f338b863bcc39bb5145ae4ec35b3b69ecc5cd02c"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-08",
      "title": "Open standards, shared test infrastructure, transparent evidence, and leadership succession improve any long-horizon public-interest program.",
      "publicPath": "/claims/claim-20-08",
      "recordFingerprint": "c5bf0192c7b4612b0f9000804751a2f691237c261e1dfc3aeb4316df044514e3"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-09",
      "title": "A trusted capability map helps researchers, students, funders, and customers find useful work now.",
      "publicPath": "/claims/claim-20-09",
      "recordFingerprint": "f4a6be7207212595e175b2c4684a70913518ff2897fd7949e8d9a0d4955a29e5"
    },
    {
      "recordType": "claim",
      "recordId": "claim-20-10",
      "title": "Fund only work with a real near-term beneficiary, a measurable capability gap, reversible tests, transparent conflicts, and an independent review path.",
      "publicPath": "/claims/claim-20-10",
      "recordFingerprint": "4b1369389b84c13a8bef231751cb0741fa4b13c4793e87cc8942a847f6b3684a"
    }
  ],
  "referenceSnapshots": [
    {
      "sourceId": "src-cd-bis-ear",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "622d3178f5899e5fcb02ff404fcd533a9408344fbf538e9263f441a5e8467b87",
      "snapshot": {
        "id": "src-cd-bis-ear",
        "title": "Export Administration Regulations",
        "authors": [
          "Bureau of Industry and Security"
        ],
        "publisher": "U.S. Department of Commerce",
        "year": 2026,
        "url": "https://www.bis.gov/regulations/ear",
        "kind": "government-regulatory-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Current U.S. dual-use export-control framework; applicability is item, destination, end-user, end-use, and jurisdiction specific."
      }
    },
    {
      "sourceId": "src-cd-iaea-nuclear-security",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "60f87f44a4c371347b1b1084d686ee508d40ae5372a42e16c25a313d69a297e1",
      "snapshot": {
        "id": "src-cd-iaea-nuclear-security",
        "title": "Nuclear Security",
        "authors": [
          "International Atomic Energy Agency"
        ],
        "publisher": "IAEA",
        "year": 2026,
        "url": "https://www.iaea.org/topics/nuclear-security",
        "kind": "intergovernmental-security-program-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Current international nuclear-security prevention, detection, response, material, facility, and transport context."
      }
    },
    {
      "sourceId": "src-cd-nasa-open-science",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "97a09c788cd8ed1efb6c0d704d9d40a3e55f7c8eaadce2c2a993375041fbc8ae",
      "snapshot": {
        "id": "src-cd-nasa-open-science",
        "title": "Open Science",
        "authors": [
          "National Aeronautics and Space Administration"
        ],
        "publisher": "NASA Science",
        "year": 2026,
        "url": "https://science.nasa.gov/open-science/",
        "kind": "active-institutional-policy-program",
        "checkedAt": "2026-07-25",
        "scopeNote": "NASA open-science policy, data, software, publication, participation, and reproducibility context."
      }
    },
    {
      "sourceId": "src-cd-nasa-partnerships",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "9f9cb5a3fcb6b5b3024569b8c222d5c4477c3fcd7404118a64448418e0f100e6",
      "snapshot": {
        "id": "src-cd-nasa-partnerships",
        "title": "Partnerships",
        "authors": [
          "National Aeronautics and Space Administration"
        ],
        "publisher": "NASA",
        "year": 2026,
        "url": "https://www.nasa.gov/partnerships/",
        "kind": "active-institutional-partnership-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Current NASA partnership pathways and agreement context; inclusion does not imply a GShips relationship or eligibility."
      }
    },
    {
      "sourceId": "src-gr-ohchr-ungp",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "132ba6eefd78883256538b2bdc3da80889617dac29b369a5a599b6cf0ae0ecc1",
      "snapshot": {
        "id": "src-gr-ohchr-ungp",
        "title": "Guiding Principles on Business and Human Rights",
        "authors": [
          "Office of the United Nations High Commissioner for Human Rights"
        ],
        "publisher": "United Nations",
        "year": 2011,
        "url": "https://www.ohchr.org/documents/publications/guidingprinciplesbusinesshr_en.pdf",
        "kind": "un-endorsed-normative-framework",
        "checkedAt": "2026-07-25",
        "scopeNote": "State duty, corporate responsibility to respect human rights, human-rights due diligence, remediation, and grievance-mechanism effectiveness criteria."
      }
    },
    {
      "sourceId": "src-gr-un-future-generations",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "387cb09c176fc27be59c0ba75399e8d0f33b1510db9e2308d9661afcd30b03aa",
      "snapshot": {
        "id": "src-gr-un-future-generations",
        "title": "Declaration on Future Generations",
        "authors": [
          "United Nations General Assembly"
        ],
        "publisher": "United Nations",
        "year": 2024,
        "url": "https://www.un.org/pact-for-the-future/en/annex-ii-declaration-future-generations",
        "kind": "un-general-assembly-normative-declaration",
        "checkedAt": "2026-07-25",
        "scopeNote": "Guiding principles and commitments concerning future interests, inclusive decision-making, intergenerational dialogue, diversity, accountability, and long-term consequences."
      }
    },
    {
      "sourceId": "src-mp-hoang-ism",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "246c03a26bf9141a4e636e84121374c0dc4d55b43ea2f90acc240fa954e35f0b",
      "snapshot": {
        "id": "src-mp-hoang-ism",
        "title": "The Interaction of Relativistic Spacecrafts with the Interstellar Medium",
        "authors": [
          "Thiem Hoang",
          "Alex Lazarian",
          "Blakesley Burkhart",
          "Abraham Loeb"
        ],
        "publisher": "The Astrophysical Journal",
        "year": 2017,
        "url": "https://doi.org/10.3847/1538-4357/aa5da6",
        "kind": "peer-reviewed-model",
        "checkedAt": "2026-07-25",
        "scopeNote": "Conditional gas and dust damage, erosion, heating, charging, and shielding mechanisms at 0.2c."
      }
    },
    {
      "sourceId": "src-mp-nasa-hvit",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "4a027c81adb7f7762463767cf234e950f12bfe201613c3f3f9e1dca903beb19d",
      "snapshot": {
        "id": "src-mp-nasa-hvit",
        "title": "Hypervelocity Impact Technology Reference Documents",
        "authors": [
          "NASA Johnson Space Center"
        ],
        "publisher": "NASA",
        "year": 2026,
        "url": "https://hvit.jsc.nasa.gov/reference-documents/",
        "kind": "institutional-test-and-design-library",
        "checkedAt": "2026-07-25",
        "scopeNote": "MMOD shielding, ballistic-limit methods, impact tests, and qualified regime boundaries."
      }
    },
    {
      "sourceId": "src-mp-nasa-se-handbook",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "3337ce334909311c3ab1c604773fdcc31a01dd8e0e781d040debd3b6e33cea22",
      "snapshot": {
        "id": "src-mp-nasa-se-handbook",
        "title": "NASA Systems Engineering Handbook",
        "authors": [
          "National Aeronautics and Space Administration"
        ],
        "publisher": "NASA",
        "year": 2016,
        "url": "https://www.nasa.gov/wp-content/uploads/2018/09/nasa_systems_engineering_handbook_0.pdf",
        "kind": "institutional-handbook",
        "checkedAt": "2026-07-25",
        "scopeNote": "Lifecycle, requirements, interfaces, verification, validation, decision analysis, and risk."
      }
    },
    {
      "sourceId": "src-pa-biosphere-energy-water",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "412602f73e4a7ea574d79f59d2b9a841c1ce19f150d7f57ad4fc34e737bc2071",
      "snapshot": {
        "id": "src-pa-biosphere-energy-water",
        "title": "Energy and Water",
        "authors": [
          "University of Arizona Biosphere 2"
        ],
        "publisher": "University of Arizona",
        "year": 2026,
        "url": "https://biosphere2.org/research/user-facility-information/energy-and-water",
        "kind": "research-facility-technical-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "External power, cooling, heating, and water infrastructure supporting the enclosed research facility."
      }
    },
    {
      "sourceId": "src-pa-doe-microgrids",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "74396b6f9d8fb2430311685ac2173717c0b967aaa92d8a1306d94c3ecb7f3f5d",
      "snapshot": {
        "id": "src-pa-doe-microgrids",
        "title": "Microgrids for Resiliency",
        "authors": [
          "United States Department of Energy"
        ],
        "publisher": "U.S. Department of Energy",
        "year": 2021,
        "url": "https://www.energy.gov/sites/default/files/2024-01/28-01-2021_doe-voe-microgrids-for-resiliency-report-2.pdf",
        "kind": "government-technical-report",
        "checkedAt": "2026-07-25",
        "scopeNote": "Controller functions, islanding, black start, resynchronization, ownership, and operating lessons."
      }
    },
    {
      "sourceId": "src-pa-doe-office-science",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "12f7364376353fdf9b20312d393fa084654aa38d880813935bf252b74943a5aa",
      "snapshot": {
        "id": "src-pa-doe-office-science",
        "title": "Office of Science",
        "authors": [
          "United States Department of Energy"
        ],
        "publisher": "U.S. Department of Energy",
        "year": 2026,
        "url": "https://www.energy.gov/science/office-science",
        "kind": "institutional-program-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "National-laboratory, user-facility, research, workforce, and funding roles."
      }
    },
    {
      "sourceId": "src-pa-esa-concordia",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "43ec053dddc5b835520a04b8f3d66f34c7369efd300eb39ca9b22f3d2be3eb1b",
      "snapshot": {
        "id": "src-pa-esa-concordia",
        "title": "Isolation studies in Antarctica",
        "authors": [
          "European Space Agency"
        ],
        "publisher": "ESA",
        "year": 2026,
        "url": "https://www.esa.int/Science_Exploration/Human_and_Robotic_Exploration/Exploration/Isolation_studies_in_Antarctica",
        "kind": "active-analog-program-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Isolation, hypoxia, sleep, small-team, and countermeasure research at Concordia Station."
      }
    },
    {
      "sourceId": "src-pa-esa-melissa",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "90915f60b25154aeb56cd818aa4e039f67f99b7f1324b4f80ea2cc7c1e133e43",
      "snapshot": {
        "id": "src-pa-esa-melissa",
        "title": "MELiSSA Closed Loop Compartments",
        "authors": [
          "European Space Agency"
        ],
        "publisher": "ESA",
        "year": 2026,
        "url": "https://www.esa.int/Enabling_Support/Space_Engineering_Technology/Melissa/Closed_Loop_Compartments",
        "kind": "active-technology-program-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Five-compartment regenerative life-support concept, unit functions, and incomplete waste-conversion boundary."
      }
    },
    {
      "sourceId": "src-pa-fda-cds-2026",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "7762e93039a1b4bdecef5b28f15006618e0a691680bac99138380839853217f5",
      "snapshot": {
        "id": "src-pa-fda-cds-2026",
        "title": "Clinical Decision Support Software: Guidance for Industry and Food and Drug Administration Staff",
        "authors": [
          "U.S. Food and Drug Administration"
        ],
        "publisher": "FDA",
        "year": 2026,
        "url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/clinical-decision-support-software",
        "kind": "government-regulatory-guidance",
        "checkedAt": "2026-07-25",
        "scopeNote": "Intended use, healthcare-professional decision support, non-device criteria, and continuing device-policy boundaries."
      }
    },
    {
      "sourceId": "src-pa-nasa-chapea",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "6cd53784e44d0b1aa513a944a0cea3c6ec9be3c0cea643aa29258f41114bab1b",
      "snapshot": {
        "id": "src-pa-nasa-chapea",
        "title": "About CHAPEA",
        "authors": [
          "National Aeronautics and Space Administration"
        ],
        "publisher": "NASA",
        "year": 2026,
        "url": "https://www.nasa.gov/humans-in-space/chapea/about-chapea/",
        "kind": "active-analog-program-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Habitat, schedule, stressors, research goals, and stated limits of NASA's Mars surface simulation."
      }
    },
    {
      "sourceId": "src-pa-nasa-moon-mars",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "a6d6ee3a2c6a911b59805537f738347ad0b375e0860e6a2b7ebd1cedc0ab5253",
      "snapshot": {
        "id": "src-pa-nasa-moon-mars",
        "title": "Moon to Mars Architecture Definition Documents",
        "authors": [
          "National Aeronautics and Space Administration"
        ],
        "publisher": "NASA",
        "year": 2026,
        "url": "https://www.nasa.gov/moontomarsarchitecture-architecturedefinitiondocuments/",
        "kind": "active-architecture-program-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Objectives-first architecture, annual revision process, use cases, segments, and documented technology and data gaps."
      }
    },
    {
      "sourceId": "src-pa-nasa-sbir",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "9f336a52ea6d8e6a633301ad953ab7ba2cb86f26189181a43cb2027700ad8e07",
      "snapshot": {
        "id": "src-pa-nasa-sbir",
        "title": "NASA SBIR/STTR Program",
        "authors": [
          "National Aeronautics and Space Administration"
        ],
        "publisher": "NASA",
        "year": 2026,
        "url": "https://www.nasa.gov/sbir_sttr/",
        "kind": "active-funding-program-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Eligibility, non-dilutive support, technology maturation, mission relevance, and commercialization intent."
      }
    },
    {
      "sourceId": "src-pa-nasa-taxonomy",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "87d47de6cbbc1a4457881fef14a44e22fd463bc17a64dbdf794f22e208fc7915",
      "snapshot": {
        "id": "src-pa-nasa-taxonomy",
        "title": "2024 NASA Technology Taxonomy",
        "authors": [
          "National Aeronautics and Space Administration"
        ],
        "publisher": "NASA",
        "year": 2024,
        "url": "https://www.nasa.gov/otps/2024-nasa-technology-taxonomy/",
        "kind": "institutional-capability-taxonomy",
        "checkedAt": "2026-07-25",
        "scopeNote": "Three-level classification of seventeen technology areas for portfolio communication and discovery."
      }
    },
    {
      "sourceId": "src-pa-nasem-team-science-2015",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "3e2a454dc0d40c40147cf73a69135649d0abb076552b726be83041ede4041c54",
      "snapshot": {
        "id": "src-pa-nasem-team-science-2015",
        "title": "Enhancing the Effectiveness of Team Science",
        "authors": [
          "National Research Council"
        ],
        "publisher": "National Academies Press",
        "year": 2015,
        "url": "https://nap.nationalacademies.org/catalog/19007/enhancing-the-effectiveness-of-team-science",
        "kind": "consensus-study",
        "checkedAt": "2026-07-25",
        "scopeNote": "Team composition, leadership, collaboration planning, interdisciplinary integration, and institutional support."
      }
    },
    {
      "sourceId": "src-pa-nasem-team-science-2025",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "a3fab330d13623cf46ab40800fadb9ded54218cbf943b34c6e94b01f384bf5ba",
      "snapshot": {
        "id": "src-pa-nasem-team-science-2025",
        "title": "The Science and Practice of Team Science",
        "authors": [
          "National Academies of Sciences, Engineering, and Medicine"
        ],
        "publisher": "National Academies Press",
        "year": 2025,
        "url": "https://nap.nationalacademies.org/resource/29043/interactive/",
        "kind": "consensus-study",
        "checkedAt": "2026-07-25",
        "scopeNote": "Collective leadership, team charters, psychological safety, collaboration infrastructure, evaluation, and institutional support."
      }
    },
    {
      "sourceId": "src-pa-nsf-infrastructure",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "f162274f5f17a2b7f5ea4dfcf0ee2f85d339c1db799e736fc46fb88f9b1e777c",
      "snapshot": {
        "id": "src-pa-nsf-infrastructure",
        "title": "Research Infrastructure",
        "authors": [
          "U.S. National Science Foundation"
        ],
        "publisher": "National Science Foundation",
        "year": 2026,
        "url": "https://www.nsf.gov/od/ori/research-infrastructure",
        "kind": "institutional-infrastructure-record",
        "checkedAt": "2026-07-25",
        "scopeNote": "Major and mid-scale facilities, lifecycle stages, data, education, and workforce roles."
      }
    },
    {
      "sourceId": "src-pa-un-udhr",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "76b5e1ece5856aeab6c21041a99a08471e25a38c6e310eeb39620a6ec3c68044",
      "snapshot": {
        "id": "src-pa-un-udhr",
        "title": "Universal Declaration of Human Rights",
        "authors": [
          "United Nations General Assembly"
        ],
        "publisher": "United Nations",
        "year": 1948,
        "url": "https://www.un.org/en/about-us/universal-declaration-of-human-rights",
        "kind": "international-rights-instrument",
        "checkedAt": "2026-07-25",
        "scopeNote": "Foundational reference for equality, dignity, privacy, family, expression, association, participation, work, education, and remedy; not a complete space-governance instrument."
      }
    },
    {
      "sourceId": "src-po-oecd-citizen-participation",
      "sourceRecordType": "claim-source",
      "sourceFingerprint": "2fcb0a0d2c7f8211e53ec1f000ef94f2486f1a2b18e16a39511ce3c25b2130c2",
      "snapshot": {
        "id": "src-po-oecd-citizen-participation",
        "title": "OECD Guidelines for Citizen Participation Processes",
        "authors": [
          "Organisation for Economic Co-operation and Development"
        ],
        "publisher": "OECD Publishing",
        "year": 2022,
        "url": "https://www.oecd.org/en/publications/2022/09/oecd-guidelines-for-citizen-participation-processes_63b34541.html",
        "kind": "intergovernmental-governance-guidance",
        "checkedAt": "2026-07-25",
        "scopeNote": "Ten-step participation process and quality principles for purpose, accountability, transparency, inclusion, accessibility, feedback, and evaluation."
      }
    }
  ],
  "packetFingerprint": "32b9835d0e022c2b5fb62f0256dc1c4016dbb24cdcc8ca8aa95b15137a480f0e"
}