Starlab Space

Packet identity

Packet ID

organizations:entity-starlab-space

Packet SHA-256 identity

494ecc71f86fe58cdddb866fcaa5cde1551c8415bac8a461211e4f3f426f1e4c

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-starlab-space

   Starlab Space

   Record fingerprint

   fb74419b3fc86acaabc84d98635f3b2059aa2b23d6237e10949665743cb99178

   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-starlab-space

   Legacy ID

   org-company--007

   Slug

   starlab-space

   Name

   Starlab Space

   URL

   https://starlab-space.com/↗ (opens external site in a new tab)

   Category

   Company and applied technology

   Geography

   United States / Europe

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current station and payload rules: monitor development and consider a competitive experiment inquiry only after an operational schedule, defined payload, independent science plan, and data rights exist. No outreach, reservation, commitment, or procurement has occurred.

   Capability

   Commercial station development, pressurized research infrastructure, payload integration, crew operations planning, digital engineering, and partner coordination.

   Entity Kind

   commercial space-station joint venture

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Starlab Space is developing a commercial low-Earth-orbit station and research platform with industrial partners. Official materials emphasize crewed research, commercial payload access, digital integration, and a post-ISS destination, but the station remains a development program.

   Potential Fit

   Could become a precursor venue for habitat operations, maintenance, human factors, biotechnology, and digital-twin experiments if the station reaches operation and offers suitable access.

   Risks

   1. Schedule, financing, certification, launch, partner roles, and eventual station availability remain development risks.
   2. Low-Earth-orbit operations do not reproduce radiation, isolation, autonomy, or duration of interstellar travel.
   3. Platform dependence, proprietary interfaces, customer priority, crew time, and pricing can constrain experiments.

   Evidence Boundary

   Official-link review: the site was reachable and describes the planned station, research purpose, and industrial participation. It does not establish an operational platform, present payload availability, final configuration, pricing, reliability, or generation-ship validation; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; joint-venture members, investors, government programs, suppliers, and potential customers were not independently investigated.

   What Would Change

   Certified flight hardware, a credible operational schedule, published payload terms, successful long-duration operations, anomaly transparency, and an appropriate experiment would change 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