TruaceTracing the truth around AIFriday, August 28, 2026
TRV-2026-0912Version 1 · Certified

Written 2026-08-28 06:04:23 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-0912
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-08-28T06:04:23.390042Z
status: published
lens: trace
sector: health
headline: Naïve adaptive immune receptor repertoires in celiac disease assessed by machine learning; impact of the HLA-DQ2.5 allotype on the TCR repertoire
dek: 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…
gain_title: 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.
problem_title: 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.
trace_subject: machine-learning classification of celiac disease status from naive adaptive immune receptor repertoires
gain_reading: 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.
gain_evidence: TCR variable gene frequencies predicted HLA-DQ2.5 status with high accuracy
problem_reading: 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.
problem_evidence: controlling for HLA-DQ2.5 abolished TCR-based diagnosis classification
quick_read: The study used machine learning on naive CD4+ TCR and naive BCR AIRR-seq repertoires to test classification of celiac disease versus controls, building on prior work linking germline HLA variation to naive repertoire composition and earlier BCR-based classification attempts.

It matters because the observed moderate TCR-based classification was not a direct disease signature but was driven by HLA-DQ2.5 frequency differences, raising uncertainty about whether naive repertoires alone contain independent celiac biomarkers and highlighting the need to control for germline HLA effects in future diagnostic models.
limitation: TCR-based celiac classification was confounded by germline HLA variation, limiting direct disease signal from naive repertoires.
tag: Dual reading
key_points: Study applied machine learning to naive CD4+ TCR and naive BCR AIRR-seq repertoires to distinguish celiac disease from controls. | TCR variable gene frequencies predicted HLA-DQ2.5 allotype with high accuracy. | Controlling for HLA-DQ2.5 abolished TCR-based diagnosis classification. | Naive BCR repertoires could not be used to classify celiac disease in this analysis.
rundown: Researchers analyzed naive CD4+ TCR and naive BCR AIRR-seq data with machine learning to test whether repertoire features distinguish celiac disease subjects from controls and to identify drivers.

Results showed moderate TCR-based diagnosis classification that tracked HLA-DQ2.5 enrichment, with TCR V-gene frequencies predicting HLA-DQ2.5 status, while controlling for HLA removed the diagnostic signal and BCR repertoires showed no classification ability.
sources:
- peer_reviewed | Immunogenetics | https://doi.org/10.1007/s00251-026-01412-3 | 2026-08-27
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
6e815b0bfa1b80b14e93b068fc86eabbb9339138d26041bdd9a1e93242084bb5
previous
0000000000000000000000000000000000000000000000000000000000000000
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.