NASA Johnson Space Center

Packet identity

Packet ID

organizations:entity-nasa-johnson-space-center

Packet SHA-256 identity

39cf9e4e5f0cbce8e75a40e37a05b8c67bc2bfc5b1d8626f08353b926ccb4a77

Corpus SHA-256 identity

8fa944604ca189f5a9216ca59f640ad2ca20972ad512f2f4970764716782e18d

Release ID

public-alpha-2026-07-26-research-visuals-r14

Source commit

3eb036fce3d711336c8c605625895e8a2e799ab0

Frozen corpus date

2026-07-25

Primary records

1

Reference sources

1

Questions and exclusions

Required questions

1. Required question 1 (exact ID: question-1)
   Does the official source establish the entity, current program, and bounded capability described?
2. Required question 2 (exact ID: question-2)
   Are potential fit, risks, access, geography, and engagement boundaries current and proportionate?
3. Required question 3 (exact ID: question-3)
   Could any wording imply partnership, endorsement, availability, procurement, authority, or affiliation that does not exist?

Explicit exclusions

• Indexing is not endorsement, due diligence completion, outreach, procurement, or a relationship.
• No aggregate organization score or sponsor-purchased ranking is permitted.

Requested controlled scopes: ecosystem-due-diligence, information-science

Frozen-evidence decision window: 90 days from the packet freeze. Not applicable to this packet family.

Complete primary record set

Every record below has one primary packet owner. Decisions must bind to the exact record and packet fingerprints; a changed lesson body, evidence grade, citation, locator, source snapshot, requirement, policy, release, or commit expires the old packet.

1. ecosystem-organization · entity-nasa-johnson-space-center

   NASA Johnson Space Center

   Record fingerprint

   507837abf5e15689df217f3872b67675ab7919e5ac3ae7302a066ccc7f5bd80d

   Minimum approvals

   1

   Required scope groups

   bounded-competence: ecosystem-due-diligence

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   entity-nasa-johnson-space-center

   Legacy ID

   org-agency-s-002

   Slug

   nasa-johnson-space-center

   Name

   NASA Johnson Space Center

   URL

   https://www.nasa.gov/johnson/↗ (opens external site in a new tab)

   Category

   Agency, standards, and public research infrastructure

   Geography

   Houston, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: map one bounded requirement to a public dataset, report, software release, solicitation, or formal partnership route; any study, agreement, facility use, or proposal requires eligibility and separate authorization.

   Capability

   Human-spaceflight operations, ECLSS and habitat engineering, space medicine, astronaut training, mission control, human-system integration, testing, and exploration programme experience.

   Entity Kind

   United States government spaceflight and research center

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   NASA Johnson Space Center leads major United States human-spaceflight functions, including astronaut operations, mission control, spacecraft and habitat systems, life support, human health and performance, training, engineering, and exploration mission operations.

   Potential Fit

   Public Johnson work could inform environmental control and life support, crew health, mission operations, training, human-system integration, habitability, and failure response. Present programmes do not cover a closed multigenerational civilization or century-scale autonomy.

   Risks

   1. Access depends on NASA mission priorities, safety, funding, procurement, agreements, export rules, and staff capacity.
   2. Crewed-spaceflight evidence is high consequence and often based on small cohorts and finite missions.
   3. Operational systems rely on Earth logistics, ground teams, and replacement supply chains.
   4. NASA involvement cannot be represented as endorsement.

   Evidence Boundary

   The official center site supports Johnson's human-spaceflight roles; it does not establish availability, a generation-ship programme, validation of multigenerational habitability, or a relationship with GShips.

   Conflicts

   1. GShips could seek federal research, facility access, technical data, or reputational benefit from NASA association.

   What Would Change

   An eligible authorized programme, completed representative habitat or operations study, public results, and independent medical and engineering review would refine fit.

Frozen source snapshots

Source inclusion does not determine the disposition. Reviewers must inspect the cited locator and relation, note inaccessible material, and identify stronger or conflicting evidence.

Offline packet and worksheet

Downloads contain no reviewer contact details. Downloading does not create an account or store a review response in the GShips application. Ordinary provider request or analytics logs may record the download request. Work locally: the public site has no review account, upload endpoint, or decision-submission API.

Do not paste a completed decision, identity documents, private contact data, confidential conflict evidence, medical information, controlled material, or exploit details into a public form. Until a separately authorized private handoff exists, retain the completed worksheet locally.

Packet schema · JSON · Decision-bundle schema · JSON

Validate offline

Use Node.js 22.13.0 or later. Keep the packet, worksheet, completed decision, and all six kit files together in a local directory.

1. Download the six kit files below. Complete a copy of the JSON template offline and preserve its templateFingerprint.
2. Finalize a separate output file.

   node finalize-review-decision.mjs \
     --input DRAFT.json \
     --output COMPLETED.json

   This marks the copy complete and calculates an unkeyed canonical bundle fingerprint. A fingerprint detects changes; it is not a reviewer signature.

3. Validate the packet and completed copy.

   node check-review-decisions.mjs \
     --packet PACKET.json \
     --decision COMPLETED.json

   Add another --decision for each independent reviewer.

4. Interpret the result narrowly. A zero exit proves structural consistency only. Neither command appoints or qualifies a reviewer, establishes independence, accepts a decision, or authorizes publication.

• Bundle finalizer
• Validator command
• Decision policy module
• Fingerprint and packet-integrity module
• Review-domain policy module
• Canonical synthesis and interactive review specs