NASA Open Science Data Repository

Packet identity

Packet ID

organizations:entity-nasa-open-science-data-repository

Packet SHA-256 identity

62f740f7d7447eb9fb402a109205d6ea7b541c2c3d6811dc91b23dd7702f5e73

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-open-science-data-repository

   NASA Open Science Data Repository

   Record fingerprint

   9671e32a6403d58b73cead3e0904e82b741c51e646606dfaa1a7459b41a0e7d8

   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-open-science-data-repository

   Legacy ID

   org-agency-s-014

   Slug

   nasa-open-science-data-repository

   Name

   NASA Open Science Data Repository

   URL

   https://science.nasa.gov/biological-physical/data/osdr/↗ (opens external site in a new tab)

   Category

   Agency, standards, and public research infrastructure

   Geography

   United States / online

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: build a preregistered reproducible analysis from suitable public studies, preserve accession and version metadata, and use ordinary data-support channels only if clarification is authorized.

   Capability

   Open scientific datasets, metadata, omics and biological records, study discovery, analysis resources, data standards, and links across spaceflight and ground research.

   Entity Kind

   United States government scientific data repository programme

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   NASA's Open Science Data Repository is a public platform for biological and physical sciences data, including spaceflight and ground studies, omics, environmental information, metadata, and analysis resources intended to increase reuse and scientific value.

   Potential Fit

   OSDR datasets could support reproducible precursor analyses of space biology, environmental exposure, organism response, and experimental design. Repository inclusion does not make datasets representative of multigenerational habitation or sufficient for medical conclusions.

   Risks

   1. Studies may be small, heterogeneous, confounded, mission-specific, or incomplete for the proposed question.
   2. Metadata, processing pipelines, software, and repository records can change.
   3. Human or sensitive data may be restricted and require privacy, consent, and controlled-access governance.
   4. Secondary analysis cannot create evidence for unobserved multigenerational outcomes.

   Evidence Boundary

   The official page establishes OSDR's repository scope; it does not validate any GShips inference, guarantee completeness, provide access to restricted records, or constitute a research partnership.

   Conflicts

   1. GShips could publish analyses that support its venture thesis and therefore must preregister methods and expose negative results.

   What Would Change

   A registered analysis, independent reproduction, better representative datasets, longitudinal combined-hazard studies, and domain review would change evidentiary value.

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