In this analysis
A predictive dataset is an output of a particular model and processing history; changing either can change the meaning of a published result.
Once predictions become a shared reference, model versioning becomes a data-management question. AlphaGenome Atlas is a useful point in that progression because published results may outlive the model configuration that generated them.
The dated path
-
2023-09-19: Accurate proteome-wide missense variant effect prediction with AlphaMissense.
-
2025-06-25: AlphaGenome: AI for better understanding the genome.
-
2026-09-08: AlphaGenome Atlas becomes available for research.
Why a stable identifier is not enough
A stable item identifier tells a reader which object is being discussed. It does not necessarily identify the prediction procedure, the input representation or the calibration applied to a score. Our retrospective argument is that scientific reuse needs both object identity and result identity. Without that distinction, a researcher can revisit the same named item and unknowingly retrieve a materially different prediction, then mistake a resource update for a change in the underlying scientific evidence.
The counterfactual of invisible refreshes
Imagine an analysis that selects candidates above a score threshold. The atlas is refreshed, several scores move and the researcher reruns the analysis using the same query. A changed candidate list might be entirely reasonable, but its cause is ambiguous unless the reference snapshot is recorded. An explicit refresh version makes the change interpretable. It allows the reader to ask whether the updated procedure improved the intended task, rather than merely observing that the latest output differs.
The dependencies that should travel together
A reproducible record can connect model identity, input conventions, generated outputs and any post-processing definitions used by an analysis. This is a proposed provenance model, not a description of the private Atlas backend. The important systems principle is dependency consistency. A score explanation generated under an older procedure should not silently accompany a newer score. The same concern appears whenever inference outputs become durable data products and are consumed through more than one interface.
How to evaluate the maintenance promise
A useful maintenance test reconstructs a past result after the current resource has changed. Another compares old and new snapshots on a stable scientific task and explains important differences. Retaining lineage need not mean keeping every temporary computation forever; it means preserving enough information to identify what was published and why it changed. The path from predictive model to atlas therefore adds a continuing stewardship obligation. Scientific users gain a reference, while operators inherit responsibility for making its evolution inspectable. A publication should record the reference version it actually used rather than assuming that a future reader will be able to reconstruct that choice from today’s interface.
Technical background
Related engineering context: Trace identity; Model loading state.