One person. Eleven layers. One lifelong asset.
A continuously updated, computable representation of an individual. The genome is fixed; its meaning is re-read as knowledge, phenotype, nutrition and environment evolve.
The twin belongs to the platform.
Not to any one product. One identity, one consent record, one contiguous audit trail — which is the only way an interpretation written today remains readable and defensible at the point of care in ten years.
Every twin carries its own provenance.
A twin is not a data lake. Each layer declares where it came from, how fresh it is, and under what consent it may be used.
Data sources & provenance
Every observation records its origin, method, version and quality flags.
Consent status
Purpose-bound and revocable; revocation propagates to derived artefacts.
Twin & model versions
Which version of the twin, and which model versions, produced any given output.
Confidence & uncertainty
Calibrated intervals, separating missing-data uncertainty from model uncertainty.
Simulation boundaries
Where the model declines to predict, and why, stated rather than hidden.
Audit history
Every access and assertion logged immutably, available to the data custodian.
What was true, and what we knew.
Every observation carries two independent time axes: when the fact was true of the person, and when the system came to know it. That is what makes "what did the system know when this was signed?" a query rather than an investigation — and it is why data arriving late, which it always does, does not corrupt the record.
Build a twin on your population.
Anchor sites commit a defined cohort and named reviewers.
