Research
Fine-Grained Traceability for Transparent ML Pipelines
Overview Research area: Machine learning systems transparency and data provenance, combining pipeline instrumentation with cryptographic commitments (hashing, Merkle trees, blockchain anchoring) and i
- arXiv
- 2601.14971
- Published
- 2026-01-21
- Authors
- Liping Chen, Mujie Liu, Haytham Fayek
AI summary
Overview
- Research area: Machine learning systems transparency and data provenance, combining pipeline instrumentation with cryptographic commitments (hashing, Merkle trees, blockchain anchoring) and influence estimation.
- Technical level: Intermediate. The ideas are explained conceptually, but the paper assumes familiarity with training loops, gradients, and basic hashing intuitions.
- Scope: The paper introduces FG-Trac, a model-agnostic framework that records, scores, and cryptographically anchors sample-level events across a machine learning pipeline, and evaluates it on one vision pipeline and one clinical graph-learning pipeline.
What This Paper Is About
Modern machine learning systems are built as multi-stage pipelines, but existing transparency tools such as model cards and dataset documentation describe what a system is, not how each individual data sample was recorded, tracked, or verified as it moved through the pipeline. This means practitioners and users cannot determine whether a specific sample was used, when it was processed, or whether the records still match what was originally written. FG-Trac targets this gap by instrumenting pipeline stages to log sample-level lifecycle events, computing checkpoint-grounded contribution scores, and anchoring the resulting logs to tamper-evident cryptographic commitments.
Key Contributions
- Formalising the problem of operational, verifiable sample-level traceability and introducing FG-Trac, a general framework that couples provenance tracking directly with machine learning pipeline execution, clarifying what must be recorded and validated to capture how samples are used and how they influence model updates.
- A verifiable, tamper-evident influence estimation mechanism that integrates a structured, checkpoint-resolved variant of TracInCP with Merkle-root digests anchored to an immutable ledger, so contribution values are tied to concrete training events rather than being retrospective estimates.
- A plug-and-play design that requires no modification to model architectures or training objectives, organised as three modules (Traceable, Blockchain, Query) aligned with preprocessing, training, and prediction stages.
- Representative evaluations on heterogeneous pipelines — a canonical CNN and a multimodal graph learning pipeline — plus two real-world medical datasets, showing preserved predictive performance and reliable sample-level provenance.
Main Findings
- No degradation on a standard vision pipeline: After 100 epochs on CIFAR-10, the baseline CNN and the FG-Trac-instrumented CNN reached nearly identical test accuracies of 0.764 and 0.762 respectively.
- Low systems overhead on CIFAR-10: Average epoch time rose from 9.31 ± 0.33 s to 9.47 ± 0.49 s (less than 2%), and peak RAM rose from 1655.1 MB to 1712.2 MB, while GPU memory remained essentially unchanged because trace hooks run as asynchronous CPU callbacks. The accumulated ledger reached 1199 MB after 100 epochs.
- Complete, verifiable traces on vision data: All 60,000 CIFAR-10 samples could be retrieved together with their T0–T3 event histories, and recomputed Merkle roots from the NDJSON trace files exactly matched the on-chain commitments for every run.
- Semantically coherent contribution scores: A queried training example labelled deer showed strongly positive influence on other deer images (scores between +12.14 and +8.85) and weakly negative influence on unrelated classes such as frog, cat, and horse (scores around −1.6).
- Preserved diagnostic performance on clinical data: On ABIDE and ADHD-200, MM-GTUNets (82.00% ACC and 88.70% AUC on ABIDE; 82.40% ACC and 91.00% AUC on ADHD-200) retained its advantage with FG-Trac enabled (82.00% ACC / 88.70% AUC on ABIDE; 82.70% ACC / 91.20% AUC on ADHD-200), with sensitivity and specificity differences within one standard deviation. Sensitivity was in some cases slightly higher with tracing (for example 91.8% vs. 89.6% on ADHD-200).
- Training-time cost concentrated in the estimator: On ABIDE, average epoch time increased from 0.5293 s to 1.3125 s (a factor of 2.48); on ADHD-200, from 0.2846 s to 0.8330 s (2.93×). Inference latency was essentially unchanged (0.2353 s vs. 0.2366 s on ABIDE; the ADHD-200 figures are reported as unchanged in the text).
- Modest memory and ledger growth in the clinical setting: Peak RAM increased by about 8% (for example 1587.39 MB to 1715.54 MB on ABIDE), peak GPU memory was nearly identical, and ledgers occupied around 1.1 GB for ABIDE and 0.48 GB for ADHD-200.
- Cryptographic integrity holds in a high-risk domain: For every subject in ABIDE and ADHD-200, recomputed Merkle roots over all NDJSON logs matched the on-chain commitments with no discrepancies.
- Auditability in practice: For one ADHD-200 participant identified only by a pseudonymous hash, the audit interface reported an imaging-to-phenotype attention ratio of 0.53:0.47, positive influence on 22 peers and negative impact on 36, and a net influence score of 7486.968, with each influence entry accompanied by a Merkle proof.
Methodology in Plain English
The authors build tracing directly into the training loop rather than trying to reconstruct it afterwards. First, a Traceable Module instruments the pipeline to write five kinds of operational logs: a user mapping log that converts each user or subject identifier into a SHA256 pseudonymous hash, a training role log that records whether each sample was used for training, validation, or testing, a modality attention log that summarises which modalities (for example imaging versus clinical text) were emphasised for each sample or batch, a sample contribution score log, and a global training action log capturing timestamps, costs, model versions, and key events.
Second, for influence scoring they use TracInCP but only evaluate gradient alignment at a selected set of discrete checkpoints, rather than along the full optimisation trajectory. For a target sample and a candidate sample, the score sums the inner product of their loss gradients across checkpoints; positive values mean the candidate pushes the model toward the target prediction, negative values mean it competes with it. This keeps the estimator tractable while tying scores to real training states.
Third, a Blockchain Module batches the logs into a Merkle tree, producing a single root hash that changes completely if even one bit of the logs changes. Only this constant-size root is committed to a blockchain; the bulky log entries and intermediate tree nodes stay in an off-chain ledger. Because the root cannot be overwritten without leaving a trace, tampering is detectable.
Fourth, a Query Module lets an authorised user or auditor submit a pseudonymous identifier, retrieve the associated logs and their Merkle proofs, and recompute the root. If the recomputed root matches the on-chain commitment, the logs are released; if not, the system refuses the query and flags possible tampering.
The framework was tested on CIFAR-10 with the standard PyTorch tutorial CNN (100 epochs, batch size 128, learning rate 1×10⁻³) and on ABIDE and ADHD-200 with MM-GTUNets (10-fold cross-validation, fixed seed 911, learning rate 5×10⁻⁴, Adam, early stopping after 20 non-improving epochs), compared against BrainGNN, GATE, and MMGL. All runs used PyTorch on Google Colaboratory (Runtime Version 2025.07) with Python 3.11.13 on an NVIDIA T4 GPU.
Why This Matters
Impact on research. The paper argues that verifiable sample-level traceability is a structural gap rather than a usability issue, and that existing influence estimators — Influence Functions, TracIn/TracInCP, Data Shapley, Representer Point Selection — produce retrospective scalar scores that cannot be validated against the model's actual optimisation trajectory and carry no integrity guarantees. FG-Trac reframes traceability as an operational record anchored in training execution, which complements rather than replaces those estimators. It also unifies two previously separate lines of work: provenance systems such as ModelDB, OpenML, MLflow, and PROV-AGENT, which record rich metadata without verifiability, and blockchain or Merkle-logging approaches, which protect records but do not specify which operational events to capture.
Real-world applications:
- Healthcare and clinical machine learning, where patient data from multi-site studies such as ABIDE and ADHD-200 must be accounted for and where raw imaging data must not be exposed during auditing.
- Finance and security, identified by the authors as high-risk regulated domains that cannot responsibly deploy pipelines without verifiable data-usage evidence.
- Regulatory compliance and audit, where an organisation must demonstrate which data was used, in what role, and when.
- Individual data-subject queries, where a person can check whether their record was used, how it influenced model behaviour, and whether any log has been altered since it was written.
Industry relevance. The framework is described as plug-and-play, requiring no change to model architectures or training objectives, and the measured overhead is modest: under 2% epoch-time increase on the CIFAR-10 CNN, essentially unchanged inference latency on both clinical datasets, and roughly 8% higher peak RAM on the clinical pipeline. Blockchains retain only a constant-size Merkle root, so on-chain storage does not grow with the number of events, while the off-chain ledger grows linearly with logged events. Training-time cost — dominated by the influence estimator, scaling as O(|C| · K · N · |θ|) — can be scheduled offline in clinical workflows.
Future Directions
The provided paper content is truncated and does not report an explicit future-work section. The following open questions follow from what the paper does and does not address:
- Reducing estimator cost. Influence estimation is identified as the primary computational cost of FG-Trac, and the checkpoint set and number of target samples are the main levers. The paper does not report how accuracy-versus-overhead trade-offs behave at larger scales of checkpoints or targets.
- Scaling beyond the evaluated pipelines. FG-Trac requires pipelines whose ingestion, preprocessing, training, and inference stages are instrumentable and whose training exposes gradients at selected checkpoints; the paper does not report behaviour for architectures or scales outside the CNN and multimodal GNN tested.
- Interpreting contribution polarity in clinical settings. The authors deliberately avoid interpreting contribution polarity with respect to diagnostic labels on the medical datasets, offering mechanistic, auditable influence traces rather than semantic explanations of clinical patterns. Whether such interpretations can be made responsibly remains open.
- Quantifying privacy guarantees. Pseudonymous SHA256 identifiers and off-chain storage of raw logs are described as privacy-preserving mechanics, but the paper does not report a formal privacy analysis beyond that design choice.
Target Audience
This paper benefits ML systems engineers and platform teams who need auditable training pipelines; researchers working on provenance, transparency artefacts, and influence estimation; compliance, audit, and governance specialists in regulated sectors such as healthcare and finance; and students or practitioners with intermediate familiarity with training loops and cryptographic hashing who want to understand how verifiable, sample-level traceability can be added to an existing pipeline without changing the model.
Authors’ abstract
Modern machine learning systems are increasingly realised as multistage pipelines, yet existing transparency mechanisms typically operate at a model level: they describe what a system is and why it behaves as it does, but not how individual data samples are operationally recorded, tracked, and verified as they traverse the pipeline. This absence of verifiable, sample-level traceability leaves practitioners and users unable to determine whether a specific sample was used, when it was processed, or whether the corresponding records remain intact over time. We introduce FG-Trac, a model-agnostic framework that establishes verifiable, fine-grained sample-level traceability throughout machine learning pipelines. FG-Trac defines an explicit mechanism for capturing and verifying sample lifecycle events across preprocessing and training, computes contribution scores explicitly grounded in training checkpoints, and anchors these traces to tamper-evident cryptographic commitments. The framework integrates without modifying model architectures or training objectives, reconstructing complete and auditable data-usage histories with practical computational overhead. Experiments on a canonical convolutional neural network and a multimodal graph learning pipeline demonstrate that FG-Trac preserves predictive performance while enabling machine learning systems to furnish verifiable evidence of how individual samples were used and propagated during model execution.