TruaceTracing the truth around AIFriday, August 28, 2026
TRV-2026-0912Certified recordPeer-reviewed

Naïve adaptive immune receptor repertoires in celiac disease assessed by machine learning; impact of the HLA-DQ2.5 allotype on the TCR repertoire

The adaptive immune receptor repertoire (AIRR) - the collection of an individual's B-cell and T-cell receptors (BCRs and TCRs, respectively) - encodes cumulative immune history and is shaped by both germline genetics and environmental exposures. Skewed repertoires have been linked to infections, vaccination responses and autoimmune diseases such as celiac disease (CeD) where biased usage of immunoglobulin and T-cell receptor genes reactive to disease relevant antigens has been reported. Motivated by evidence tha…

Health · The Trace — both readings · certified 2026-08-28 · v1 · article view · machine-readable

Current reading — gain

Naive CD4+ TCR repertoire features enabled moderate machine-learning classification of celiac disease status and high-accuracy prediction of HLA-DQ2.5 status by publication date.

Current reading — problem

After accounting for HLA-DQ2.5 enrichment, machine-learning classification of celiac disease from naive TCR repertoires was abolished, and naive BCR repertoires failed to classify disease.

What this doesn’t fix

TCR-based celiac classification was confounded by germline HLA variation, limiting direct disease signal from naive repertoires.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0912, v1: “Naïve adaptive immune receptor repertoires in celiac disease assessed by machine learning; impact of the HLA-DQ2.5 allotype on the TCR repertoire.” Truvace, 2026-08-28. /record/TRV-2026-0912 (accessed at citation time). sha256 6e815b0bfa1b80b1

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv16e815b0bfa1b

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0912 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.