UCSB DEEPSPACE

Packet identity

Packet ID

organizations:entity-ucsb-deepspace

Packet SHA-256 identity

ad758e348ddf49060ea410c109daf76abe1eb71d5c6ad5249a2ca7f4008b5945

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-ucsb-deepspace

   UCSB DEEPSPACE

   Record fingerprint

   2a8e255a5d19c47ff3571af9d9a2b773ef478313820d6184c3b5074b4017cd0c

   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-ucsb-deepspace

   Legacy ID

   org-universi-031

   Slug

   ucsb-deepspace

   Name

   UCSB DEEPSPACE

   URL

   https://www.deepspace.ucsb.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 university rules: use public papers to test calculations, then consider a bounded technical critique around a robotic precursor or scaling assumption. No outreach, invitation, commitment, or funding has occurred.

   Capability

   Directed-energy systems, laser-array concepts, beamed spacecraft propulsion, small interstellar probes, photonics, systems scaling, and planetary-defense studies.

   Entity Kind

   university directed-energy research program

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   UCSB's DEEPSPACE work within the Experimental Cosmology Group develops studies of large directed-energy systems, beam-driven propulsion for small spacecraft, planetary defense, and related photonics and systems concepts. The work is research and modeling, not an operational interstellar transport service.

   Potential Fit

   Could inform beamed-propulsion physics, pointing, phased arrays, wafer-scale precursor probes, heat loads, system scaling, and the distinction between robotic probes and crewed worldships.

   Risks

   1. Crewed-vehicle scaling, energy supply, optics, pointing, thermal loads, atmospheric effects, and braking remain profound gaps.
   2. High-power directed energy is inherently dual-use and could enable weapons or harmful illumination.
   3. Concept studies and component research do not establish an integrated, permitted, affordable, or safe system.

   Evidence Boundary

   Official-link review: the UCSB site was reachable and presents directed-energy and interstellar-precursor research. This review did not independently reproduce performance models, confirm current program activity, or establish readiness, funding, access, legality, or crewed applicability; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; government funding, patents, defense or planetary-defense interests, and researcher advocacy were not independently investigated.

   What Would Change

   Independent replication of scaling models, end-to-end subsystem demonstrations, explicit civil governance, credible energy and braking solutions, and transparent safety analysis 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