Rocket Lab

Packet identity

Packet ID

organizations:entity-rocket-lab

Packet SHA-256 identity

94a791a19a96280ababbb502fc1c37763a4b6e7c901bc3be51de814848d89e2e

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-rocket-lab

   Rocket Lab

   Record fingerprint

   c6689b89d9b503722c9404a687357ddba771fac9201d941466893bcd479d2e07

   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-rocket-lab

   Legacy ID

   org-company--010

   Slug

   rocket-lab

   Name

   Rocket Lab

   URL

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

   Category

   Company and applied technology

   Geography

   United States / New Zealand

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current procurement and launch rules: include in a competitive options study when a funded precursor payload has defined mass, orbit, schedule, and assurance requirements. No outreach, slot reservation, commitment, or procurement has occurred.

   Capability

   Small launch, launch-vehicle development, spacecraft buses and components, mission software and operations, and deep-space payload delivery.

   Entity Kind

   public launch and space-systems company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Rocket Lab presents an end-to-end portfolio including Electron launch, HASTE suborbital testing, the Neutron launch vehicle under development, spacecraft platforms, separation systems, solar products, flight software, and mission operations. Its spacecraft have supported civil, commercial, and defense missions, including deep-space mission delivery.

   Potential Fit

   Could support relatively near-term precursor payload delivery, spacecraft-bus procurement, components, or mission integration; launch experience would not validate generation-ship propulsion, habitats, or multigenerational autonomy.

   Risks

   1. Launch schedules, vehicle development milestones, payload constraints, and prices are volatile and mission-specific.
   2. Defense and hypersonic-test work creates dual-use, export-control, and reputational boundaries.
   3. A vendor's successful missions do not establish reliability for a different vehicle, configuration, destination, or duration.

   Evidence Boundary

   Official-link review: the source domain returned an automated-access barrier to the direct checker but redirected to Rocket Lab's current official domain and was readable through the web renderer. Current availability, performance, anomaly history, procurement terms, and mission fit were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; investor, government-customer, contracting, launch-cadence, and program conflicts were not independently investigated.

   What Would Change

   A concrete precursor mission, current users' guide, independently reviewed flight record, available integration slot, and acceptable data and liability terms would determine practical 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