NASA Ames Research Center

Packet identity

Packet ID

organizations:entity-nasa-ames-research-center

Packet SHA-256 identity

2c58ded5e93bb871a38dcf664425d015dcc71d67ccf4ecaa2baf31d28c1d7852

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-ames-research-center

   NASA Ames Research Center

   Record fingerprint

   6a2ec3cf696fdf3b172f2c702574082d764c1d593d01f36a9a6f76a7728647f7

   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-ames-research-center

   Legacy ID

   org-agency-s-003

   Slug

   nasa-ames-research-center

   Name

   NASA Ames Research Center

   URL

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

   Category

   Agency, standards, and public research infrastructure

   Geography

   California, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: identify a public solicitation, dataset, software release, or named civil programme matching one bounded requirement; any agreement, facility use, or proposal requires official eligibility and separate authorization.

   Capability

   Advanced computing, autonomy, astrobiology, space biology, human systems, thermal protection, simulation, small-spacecraft engineering, and government research facilities.

   Entity Kind

   United States government aerospace research center

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   NASA Ames Research Center conducts civil aerospace research in areas including advanced computing, autonomy, intelligent systems, aeronautics, astrobiology, life science, human systems, thermal protection, small spacecraft, and mission technology.

   Potential Fit

   Ames public research and eligible programmes could inform autonomous operations, bioengineering, closed-habitat studies, human factors, software assurance, and simulation. A fit would require one named programme and representative test, not a center-wide partnership assumption.

   Risks

   1. Access depends on NASA priorities, solicitations, agreements, funding, safety, export rules, and staff capacity.
   2. Research prototypes and analog studies may not represent multidecade deep-space operation.
   3. AI and autonomy capabilities require cyber, human-override, verification, and model-update controls.
   4. NASA involvement cannot be represented as endorsement.

   Evidence Boundary

   The official center site establishes broad research areas and facilities; it does not establish project availability, selection, a generation-ship programme, or validation of GShips requirements.

   Conflicts

   1. GShips could seek federal funding, facility access, licensed technology, or reputational benefit from NASA association.

   What Would Change

   An eligible public call, authorized center response, selected experiment, or completed representative test with public results would support a more specific assessment.

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