SpaceX

Packet identity

Packet ID

organizations:entity-spacex

Packet SHA-256 identity

1e9b8c2fef3ca6967101057d59d93b594e046d11023e738d32b9960ddd4c6386

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-spacex

   SpaceX

   Record fingerprint

   dc9fb340bbd826cc72d99b81140509ca8c3e78510980d9d166f7ef40f057a37d

   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-spacex

   Legacy ID

   org-company--009

   Slug

   spacex

   Name

   SpaceX

   URL

   https://www.spacex.com/↗ (opens external site in a new tab)

   Category

   Company and applied technology

   Geography

   California, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current service terms: include alongside alternatives only when a funded precursor has defined payload, orbit, schedule, assurance, independence, and data requirements. No outreach, reservation, commitment, or procurement has occurred.

   Capability

   Orbital launch, crew and cargo spacecraft, satellite communications, launch integration, mission operations, and heavy-lift vehicle development.

   Entity Kind

   private launch, spacecraft, and communications company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   SpaceX designs and operates Falcon launch vehicles, Dragon spacecraft, Starlink communications infrastructure, and the Starship launch system in development. It has substantial orbital launch and crew/cargo experience, while each vehicle and service has distinct readiness and risk evidence.

   Potential Fit

   Could be one option for precursor launch, cargo transport, communications, or rideshare services under competitive procurement; its architecture and public Mars narrative are not treated as validation of generation ships.

   Risks

   1. Vehicle development, schedules, pricing, licensing, and mission availability can change rapidly.
   2. Government and defense contracts, communications infrastructure, and launch technology create dual-use and geopolitical risks.
   3. Supplier concentration and proprietary interfaces can create lock-in, single-point dependence, and limited anomaly transparency.

   Evidence Boundary

   Official-link review: the site was reachable and identifies the company's launch, spacecraft, communications, and development programs. This review does not independently establish current availability, future performance, complete anomaly history, terms, or fitness for a specific mission; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; government customers, investors, related companies, launch customers, and executive interests were not independently investigated.

   What Would Change

   A concrete precursor need, current users' documentation, independently reviewed mission evidence, competitive alternatives, and acceptable liability, data, and interface terms would determine 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