Working drafts, whitepapers, protocol RFCs and replication runs from across the eight pilot modules. Everything ships with the code that produced it; nothing is paywalled. DOI-stamped at public alpha.
Open drafts produced by the module teams and pilot collaborators. Each has a public review thread and a maintainer responsible for the next revision. Status badges reflect the live state of the draft.
Drafts move through four states: scoping (problem outlined, no methods locked) → writing (methods + early results) → in review (open community + module-lead review) → DOI-stamped (at public alpha, with frozen artefact hashes attached). Anyone can comment on any draft; comments are public and resolution is logged with the document.
New modules and major architectural changes enter AURORA through an RFC. The list below is the current queue. Public RFCs open at Q4 2026.
AURORA does not own data. We connect to permissively-licensed open datasets and to federation partners' on-prem registries. Each dataset is annotated against the modules that depend on it.
The Cancer Genome Atlas glioma collections — foundational for AURORA-GLIO foundation-model pre-training and evaluation.
Multi-institutional MRI segmentation challenge data; benchmark substrate for AURORA-GLIO and infiltration modules.
Public summaries from the Management of Myelomeningocele Study underpin AURORA-SPINA prenatal decision priors.
Population priors on brain anatomy and CSF compartment volumes across modules.
Long-horizon imaging used in compartment lifetime modelling and incidental-finding triage.
BIDS-formatted open datasets across paediatric and adult imaging used for federated evaluation.
Every module ships with an evaluation protocol — held-out splits, metrics, stratifications, and the explicit failure modes the protocol catches. Protocols are versioned alongside the models they evaluate.
Patient-level (never image-level), stratified by site, ancestry, sex and age band. Splits are pinned and signed.
One per module — AUC for triage, sigma for tension fields, Brier for calibration. Secondary metrics carry their own thresholds.
Every metric reported per stratum, not just aggregate. A drop below the equity threshold blocks release.
Adversarial slices the protocol must catch — domain shift, missing modality, sample-size cliff. Listed publicly per module.
Calibration reported with each metric. Brier and ECE on top-line outputs; confidence bands on derived fields.
Continuous evaluation against the same protocol every quarter. Drift > threshold opens an RFC, not a hotfix.
A running ledger of independent reruns of AURORA results. Pinned commit + image + weights + dataset hash means anyone with the right hardware can re-execute. If a result stops replicating, we say so — the tracker turns red and an issue auto-opens.
a1b2c3d4e5f6sha256:c9a4…f17esha256:7b1e…aa9dsha256:f2c0…12bbP-04 · v1.2CUDA 12.4 · py 3.11One command pulls the pinned commit, pinned image, pinned weights and the dataset hash for the cohort the result was reported on. Anyone with the hardware can run it.
Replication ≠ external validation. A result replicating on its own bench does not mean it works at your site. That's exactly why federation matters and why module pages carry both numbers.
The tracker monitors drift on every quarterly rerun. A red row creates a public GitHub issue tagged with the responsible maintainer. Resolution is logged in the artefact's history.
If a result stops replicating, we say so. The tracker is a feature, not a press kit.
Reproducibility is unsexy infrastructure work. The current state of clinical-AI literature is what happens when it is treated as optional. AURORA treats the ledger above as the canonical record — papers are interpretations of it, not the other way around.
Every AURORA result, model and dataset has a citable artefact with a DOI at public alpha. Cite the artefact you actually used — not a higher-level umbrella paper that obscures which version of which subsystem ran.
@software{aurora_glio_2026,
title = {AURORA-GLIO: An open substrate for glioma},
author = {{AURORA Collective}},
year = {2026},
version = {0.9.0-pilot},
url = {https://aurora.health/glio},
doi = {10.0000/aurora.glio.0.9.0},
note = {Pinned commit a1b2c3, weights sha256: c9a4…f17e}
}Module-specific entries (e.g. aurora_glio_infil_2026) exist for every subsystem. The note field carries the pinned commit and sha256 of the artefact you ran — that's the line that lets reviewers replicate you.