Skip to main content

Transparency

Methodology

Riyaan organizes starting-cell evidence around a program-specific decision. This page explains what the public demonstration does, what it deliberately does not claim, and how uncertainty remains visible.

Published

Scope of the demo

Riyaan frames readiness relative to a defined program rather than treating a source line as universally suitable. The demonstration groups evidence into identity and quality, pluripotency and differentiation, culture and reprogramming, HLA and population fit, genomics, commercial and regulatory readiness, and exclusion flags.

A display status is a workflow signal for further review. “Ready for review” does not mean clinically ready, regulatory-compliant, fit for manufacturing, or safe for use in people.

Source linkage and provenance

Each evidence item can retain a source document, source owner, retrieval information, extraction method, and extraction confidence. Where available, the workspace also records a source URL, publication date, or file hash so a reviewer can return to the material used for transcription.

A value without an adequate source link should be treated as unverified. An absent value is not proof that a characteristic is absent; it means the demonstration has not established that characteristic from the material reviewed. Linked third-party sources remain subject to their own context, terms, and update cycles.

Evidence and reviewer states are separate

The evidence state describes the item itself: present, partial, missing, failed, conflicting, not applicable, or not reviewed. A separate reviewer state describes the human review workflow:

Unreviewed
No named completed review is recorded.
In review
Assessment is under way; no final acceptance is implied.
Reviewed
A named review event and time are recorded.
Rejected
The item was not accepted for the current decision context.

“Reviewed” records a workflow event only. It does not assert independent reproduction, laboratory validation, regulatory acceptance, or clinical suitability.

Decision logic and blocker overrides

The demonstration separates supporting evidence from decision blockers. Explicit exclusion flags—such as a disease-model designation, genetic modification, abnormal karyotype, or a program-level exclusion—are evaluated before an aggregate readiness label. A blocker can therefore keep a line out even when other evidence appears strong.

Missing or invalid scoring dimensions remain unresolved rather than being averaged away. Commercial-use rights are also treated as a blocker in the illustrative scoring logic. These rules are conservative triage controls, not a validated biological, clinical, procurement, or regulatory model.

HLA computability requirements

The demonstration marks population-fit output as computable only when all 12 allele fields for HLA-A, HLA-B, HLA-C, HLA-DRB1, HLA-DQB1, and HLA-DPB1 are present in pairs, each value has at least two-field resolution, and a finite reference-set score between zero and one is supplied. A homozygous label by itself is not sufficient.

A meaningful population analysis would also need a documented population reference set, a defined matching method and version, quality controls, and a review of sampling assumptions. The current public demonstration has not established that validation.

Limitations and responsible use

  • Demo records may be incomplete, simplified, synthetic, or drawn from public documents that can change.
  • A source citation does not establish freedom to operate, commercial rights, regulatory status, or fitness for a particular purpose.
  • Scores and priority labels are illustrative workflow aids, not validated endpoints or probability estimates.
  • Any real program requires independent source verification, laboratory testing, quality review, rights review, and appropriate clinical and regulatory expertise.