NASA Kennedy Space Center

Packet identity

Packet ID

organizations:entity-nasa-kennedy-space-center

Packet SHA-256 identity

ddc898f20087e1447b23c6cb21776f1afedb576afd90875d9e5affefc9a0ac94

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-kennedy-space-center

   NASA Kennedy Space Center

   Record fingerprint

   83ccc649e4c31c6a24d04a5838d21bde9774d12ca79289eb5f8cd13d1d7ab363

   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-kennedy-space-center

   Legacy ID

   org-agency-s-006

   Slug

   nasa-kennedy-space-center

   Name

   NASA Kennedy Space Center

   URL

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

   Category

   Agency, standards, and public research infrastructure

   Geography

   Florida, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: identify a public call, technology-transfer item, dataset, or facility pathway tied to one precursor experiment; any access or partnership requires official review, budget, eligibility, and separate authorization.

   Capability

   Launch and ground operations, payload processing, multiuser spaceport infrastructure, plant research, ISRU and Swamp Works activities, testing, and formal partnership mechanisms.

   Entity Kind

   United States government space center and launch research facility

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   NASA Kennedy Space Center is a multiuser civil spaceport and research center supporting launch and ground systems, payload processing, exploration systems, space-crop research, in-situ resource-utilization work, and public-private partnerships.

   Potential Fit

   Kennedy programmes could inform ground integration, launch processing, payload safety, space-crop experiments, ISRU precursors, and the operational handoff from development to mission. Those capabilities address launch and bounded tests, not interstellar vehicle completion.

   Risks

   1. Launch-site and facility access are tightly scheduled, safety-controlled, and often costly.
   2. Programmes depend on NASA priorities, procurement, partner agreements, export rules, and environmental review.
   3. Terrestrial or short-flight crop and ISRU tests do not establish closed-loop or industrial scale.
   4. NASA partnership language cannot be used before a formal agreement exists.

   Evidence Boundary

   The official center site establishes Kennedy's spaceport, research, and partnership functions; it does not establish GShips access, selection, endorsement, or validation of a generation-ship precursor.

   Conflicts

   1. GShips could seek federal support, test access, technology transfer, or reputational value from a NASA agreement.

   What Would Change

   A published eligible pathway, authorized facility response, selected precursor test, and independently reviewed public results would change engagement and readiness.

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