Yuri

Packet identity

Packet ID

organizations:entity-yuri

Packet SHA-256 identity

d9f4a34a8a4515084e050fddf3ee612a3b311e0143f96b30546cfe030bad4585

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-yuri

   Yuri

   Record fingerprint

   6c1e088f199555a2e460d376673e8f62872d45a2eab959371b43f720b09a7a2a

   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-yuri

   Legacy ID

   org-company--036

   Slug

   yuri

   Name

   Yuri

   URL

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

   Category

   Company and applied technology

   Geography

   Germany

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current product and mission terms: compare a defined biological question across static controls, ground simulation, and actual flight before considering procurement. No outreach, hardware order, mission booking, commitment, or procurement has occurred.

   Capability

   Ground microgravity simulators, modular life-science experiment hardware, biotechnology research support, experiment automation, and spaceflight mission services.

   Entity Kind

   private microgravity life-science technology company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Yuri Gravity develops microgravity research hardware and services for life sciences and biotechnology, including ground-based microgravity simulation and spaceflight experiment support. Its current official site emphasizes research platforms and simulation rather than proof that simulated microgravity reproduces orbital biology.

   Potential Fit

   Could support early biological screening, experiment automation, payload miniaturization, and comparison of ground analogs with flight data for precursor health and biomanufacturing work.

   Risks

   1. Clinostats and random-positioning machines introduce shear and other artifacts and do not reproduce all aspects of orbital free fall.
   2. Small biological experiments may not translate to human health, complex ecosystems, or long durations.
   3. Product availability, flight access, proprietary protocols, sample handling, and data rights may constrain independent replication.

   Evidence Boundary

   Official-link review: the Yuri Gravity site was reachable and describes microgravity simulators, research hardware, and mission support. Comparative validity, flight history, current availability, pricing, anomaly data, and fit for a specific protocol were not independently verified; independent review pending.

   Conflicts

   The company sells microgravity products and services; investors, customers, research partners, and claims about simulator utility were not independently investigated.

   What Would Change

   Peer-reviewed comparison with flight controls, transparent hardware and motion profiles, reproducible protocols, current service terms, and independent biological review 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