Caltech Lightsail Project

Packet identity

Packet ID

organizations:entity-caltech-lightsail-project

Packet SHA-256 identity

b39b4fba1e4be7c49099565f2534430193429427b154a5a04a640dca1ecca2a7

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-caltech-lightsail-project

   Caltech Lightsail Project

   Record fingerprint

   5e70a93fbd7ace0eb4d3c5c4d1d871c600a4fc47f4846e4e8c0be639a3b50e0c

   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-caltech-lightsail-project

   Legacy ID

   org-universi-030

   Slug

   caltech-lightsail-project

   Name

   Caltech Lightsail Project

   URL

   https://www.lightsail.caltech.edu/↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   California, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current access rules: follow peer-reviewed outputs and, if a concrete open research question fits, consider a university research discussion or reproducibility study. No outreach, eligibility determination, commitment, or procurement has occurred.

   Capability

   Ultrathin sail materials, nanophotonics, optomechanics, thermal management, stability modeling, and radiation-pressure experiments.

   Entity Kind

   multi-university academic research project

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   The Caltech Lightsail Project is a research collaboration addressing materials, photonics, structural mechanics, thermal behavior, beam-riding stability, and experiments for laser-driven ultralight sails associated with Breakthrough Starshot.

   Potential Fit

   Could inform robotic precursor probes and the ‘faster propulsion’ decision gate, especially material and stability constraints; it is not a crewed-ship propulsion pathway on current evidence.

   Risks

   1. The target architecture concerns gram-scale probes, not crewed generation ships.
   2. Required directed-energy infrastructure, pointing, thermal control, and interstellar-environment survivability remain major constraints.
   3. Project participation, funding, facilities, and unpublished data are not assumed available.

   Evidence Boundary

   Official-link review: the official project, team, and publications pages were reachable and document objectives, investigators, and a current peer-reviewed publication trail. Public descriptions, performance, maturity, access, procurement, and current availability were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; financial, contracting, leadership, and institutional conflicts were not independently investigated.

   What Would Change

   Scaled experiments, independent replication, integrated beam-and-sail demonstrations, and credible mass scaling beyond probes would materially alter the assessment.

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