NASA Jet Propulsion Laboratory

Packet identity

Packet ID

organizations:entity-nasa-jet-propulsion-laboratory

Packet SHA-256 identity

0dc39088e840dee23eac85a21c44f9bbe63a5e003e417581e3a5a4a289fa4ba6

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-jet-propulsion-laboratory

   NASA Jet Propulsion Laboratory

   Record fingerprint

   bcf93fb9fa2c31914f3c9670d47071bec19ab95624cf5d6a0c2b0eb87978e7a2

   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-jet-propulsion-laboratory

   Legacy ID

   org-agency-s-007

   Slug

   nasa-jet-propulsion-laboratory

   Name

   NASA Jet Propulsion Laboratory

   URL

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

   Category

   Agency, standards, and public research infrastructure

   Geography

   California, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: study public mission lessons, software, and reports and identify one civil research question; any agreement, licensing, facility work, or proposal requires an official NASA or Caltech/JPL route and separate authorization.

   Capability

   Robotic deep-space missions, autonomous navigation, planetary robotics, communications, mission operations, flight software, instruments, systems engineering, and long-distance fault management.

   Entity Kind

   federally funded research and development center managed by a university

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   NASA's Jet Propulsion Laboratory is a federally funded research and development center managed by Caltech. It designs, builds, and operates robotic planetary and Earth-science missions and develops deep-space navigation, communications, autonomy, robotics, instruments, and mission systems.

   Potential Fit

   JPL mission heritage could inform autonomous fault response, deep-space navigation, communications, robotics, software, operations, and evidence-driven mission design. These systems generally retain Earth support and do not establish self-sufficient century-scale operation.

   Risks

   1. Access depends on NASA mission priorities, agreements, procurement, export controls, security, and staff capacity.
   2. Long-lived robotic missions rely on ground teams, one-off hardware, and finite consumables.
   3. Autonomy and flight software can be safety-critical, cyber-sensitive, and difficult to maintain across technology generations.
   4. JPL association cannot be represented as endorsement.

   Evidence Boundary

   The official JPL site supports robotic mission and technology heritage; it does not establish availability, a GShips programme, autonomous civilization-scale operation, or validation of the proposed architecture.

   Conflicts

   1. GShips could seek public technology, licensed software, research access, or reputational benefit from JPL association.

   What Would Change

   An eligible authorized project, reusable open artifact, completed representative autonomy demonstration, or independent review of a mapped subsystem would sharpen fit.

Linked records—not review targets here

These records provide dependency or relationship context. Their decisions belong to their single primary packet, preventing double counting.

• robotic-destination-characterization · entity-nasa-jet-propulsion-laboratory partner-task-match:match-robotic-destination-characterization-jpl · 0388aa1d8ef438d3478ddee1f07ae7e2dd65a4e8f95163957d8bbcd468821352

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