Vast

Packet identity

Packet ID

organizations:entity-vast

Packet SHA-256 identity

f00eaa94513a264bc1da1a72a2556a5c6e6f9874bb54497b5746d948922f077c

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

   Vast

   Record fingerprint

   c9ddeb3b25cfe062872e6b1fb9dc2a458ab657844b188985c888e2fbb5019003

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

   Legacy ID

   org-company--005

   Slug

   vast

   Name

   Vast

   URL

   https://www.vastspace.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 station and payload access: monitor independent milestones and consider a competitive experiment inquiry only after an operational platform and defined study exist. No outreach, reservation, commitment, or procurement has occurred.

   Capability

   Commercial station development, crewed habitat integration, station operations planning, life-support interfaces, payload access concepts, and an artificial-gravity roadmap.

   Entity Kind

   private commercial space-station developer

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Vast is developing crewed low-Earth-orbit infrastructure through the planned Haven station sequence and describes artificial gravity as a longer-term direction. Official materials distinguish nearer-term station hardware from future larger systems, all of which remain dependent on development, launch, certification, and operations.

   Potential Fit

   Could become a precursor platform for crew operations, maintenance, human factors, life-support, and research; future artificial-gravity work could provide test opportunities if it progresses beyond roadmap claims.

   Risks

   1. Station schedule, financing, certification, launch dependence, and operating lifetime remain development uncertainties.
   2. An artificial-gravity roadmap is not evidence of a rotating habitat, safe transition regime, or long-duration health benefit.
   3. Private platform control, proprietary interfaces, crew time, safety rules, and pricing can limit access and reproducibility.

   Evidence Boundary

   Official-link review: the site was reachable and describes the planned station sequence, infrastructure strategy, and artificial-gravity ambition. Operational status, payload availability, final configuration, reliability, price, and health outcomes were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; investors, launch and crew providers, government customers, suppliers, and station competitors were not independently investigated.

   What Would Change

   Successful crewed operations, published lifecycle and anomaly evidence, a demonstrated rotating system, independent human-research results, and accessible payload terms would refine 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