UCF Exolith Lab

Packet identity

Packet ID

organizations:entity-ucf-exolith-lab

Packet SHA-256 identity

e70d2a2bf0a246c2ddf2c0be11d421e8b8e8d9fd3f68511875c09be76904a426

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-ucf-exolith-lab

   UCF Exolith Lab

   Record fingerprint

   a10aa147e75ccfd9fbc6b2337945e268d0acc929d3f62a5322b30de3d88900da

   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-ucf-exolith-lab

   Legacy ID

   org-universi-047

   Slug

   ucf-exolith-lab

   Name

   UCF Exolith Lab

   URL

   https://exolithsimulants.com/↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   Florida, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current product and laboratory access: procure or compare a characterized simulant only after the target material properties and test protocol are defined. No outreach, order, commitment, or procurement has occurred.

   Capability

   Planetary regolith simulant design and production, material characterization, analog testing support, educational access, and standardized test media.

   Entity Kind

   university planetary-regolith simulant laboratory

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   UCF's Exolith Lab develops and distributes lunar, Martian, and asteroid regolith simulants for research, education, hardware testing, construction, agriculture, and resource-utilization experiments. Simulants are engineered analog materials, not returned extraterrestrial samples.

   Potential Fit

   Could support repeatable dust, abrasion, construction, extraction, filtration, agriculture, and maintenance testing for lunar or asteroid precursor systems using characterized batches.

   Risks

   1. No simulant reproduces every physical, chemical, electrostatic, volatile, toxicological, or geological property of real regolith.
   2. Batch variation and an ill-matched simulant can produce misleading hardware or biological results.
   3. Availability, shipping, cost, handling rules, and access to characterization data may change.

   Evidence Boundary

   Official-link review: the site was reachable and lists simulant families, high-level compositions, applications, and purchasing pathways. Batch-specific certification, complete fidelity, inventory, price, and suitability for any planned test were not independently verified; independent review pending.

   Conflicts

   The laboratory sells simulants and therefore has a commercial interest in their use; no purchase, sponsorship, or other conflict with GShips was identified.

   What Would Change

   A target body's measured properties, batch certificates, independent comparison against returned samples, interlaboratory reproducibility, and a defined test sensitivity would determine 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