ChronoGuard catches data leaks that ship twice under renamed columns; AUC 1.0 to 0.826
Apprehensive_Ratio0 · reddit · 2026-09-29
A developer published ChronoGuard, a temporal-leakage auditor targeting a sneaky failure: the same data leak shipping twice under different names. A chargeback field leaked as cbresolutionflag; months later another team added chargebackresolution — identical leak, new name. Removing the leaks dropped ROC-AUC from a misleading 1.0 to 0.826.
- Normalize feature names (expand abbreviations, drop generic suffixes), then match via string + character similarity; some renamed leaks hit 1.0 after normalization
- Near-fatal false positive: customerriskscore vs merchantriskscore
- Core principle: memory provides evidence leads but must never override timestamp evidence
Writeup and GitHub repo included; advice: audit your training data and remember how you fixed each leak so the org doesn't repeat it.
More from Research
- VLM Chain-of-Thought Doesn't Reliably Track Visual Evidence, EMNLP Paper Finds — oanacamb · 2026-09-30
- Google Releases ATLAS: 15M Real Human-AI Interactions Across 150 Countries — soumitrashukla9 · 2026-09-30
- Six frontier models benchmarked across 34 capabilities in nine computer vision areas — ducha_aiki · 2026-09-30
- ETH's LP-ACRL Trains ANYmal to Run 2.5 m/s Over Rough Terrain — ChongZzZhang · 2026-09-30
- RecursiveMAS: Agent swarms share latent thoughts like looped Transformers, cutting tokens by 75% — james_y_zou · 2026-09-30
- Simplex Diffusion Models proposed to fix information collapse in discrete diffusion — msalbergo · 2026-09-30