UC Berkeley CUBES

Packet identity

Packet ID

organizations:entity-uc-berkeley-cubes

Packet SHA-256 identity

79707b1bbb40d27d0c93dbec89cd4acab24fb7c7a3bb34ca008a5cd0531b0968

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-uc-berkeley-cubes

   UC Berkeley CUBES

   Record fingerprint

   8ac71b7475de68e0050f1bf8def5ca19834f98846859f9958de2d56a589da995

   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-uc-berkeley-cubes

   Legacy ID

   org-universi-012

   Slug

   uc-berkeley-cubes

   Name

   UC Berkeley CUBES

   URL

   https://cubes.space/↗ (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 institute rules: use publications and education material first, then consider a bounded research discussion or sponsored experiment around one production pathway. No outreach, eligibility determination, commitment, or funding has occurred.

   Capability

   Space biomanufacturing, synthetic biology, food and pharmaceutical production, fuel and materials pathways, downstream processing, and systems analysis.

   Entity Kind

   NASA-funded university space biomanufacturing institute

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   The Center for the Utilization of Biological Engineering in Space, led by UC Berkeley with partner institutions, researches biomanufacturing pathways for food, pharmaceuticals, fuels, and materials during deep-space missions. Its official materials organize work across feedstocks, manufacturing, product recovery, systems analysis, and education.

   Potential Fit

   Could inform modular biological production, feedstock conversion, product purification, bioprocess control, and integrated mass-balance modeling for precursor habitats, not validate a complete closed economy.

   Risks

   1. Laboratory yields and demonstrations may not transfer to radiation, microgravity, restricted inputs, or long-duration operation.
   2. Engineered biology raises biosafety, biosecurity, containment, ecological, and governance concerns.
   3. NASA funding phase, investigator availability, intellectual property, and external access can change.

   Evidence Boundary

   Official-link review: the center site was reachable and documents research divisions, institutions, investigators, and target products. Current program phase, replicated performance, integrated closure, biosafety evidence, and access mechanisms were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; NASA awards, universities, patents, commercial translation, and investigator conflicts were not independently investigated.

   What Would Change

   Peer-reviewed end-to-end yields, independent replication, long-duration stability, containment and recovery evidence, transparent mass and energy balances, and a current access path 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