AI & ML
ProxyGuard: Direct Reliability Inference for Randomized Data Release Mechanisms with Shared Targets
arXiv stat.ML0 views
arXiv:2608.18643v2 Announce Type: replace-cross Abstract: Researchers often choose a proxy dataset from many releases, transformations, or seeds. Search can make an invalid release appear adequate, while one adequate release does not establish that its generator is reliable. ProxyGuard controls both errors using prespecified bounded risks and a sealed target set. Named-release mode corrects for multiplicity and certifies specific releases. Direct shared-target mode evaluates independent mechanism draws on a common target, lower-bounds their favorable-score rate, and subtracts a bound on favorable scores contributed by invalid releases. Conditional on the target, release scores are independent, yielding a finite-sample mechanism-reliability guarantee without independent target batches or assumptions on release-level $p$-value dependence. We show that the mean-only penalty is sharp and derive a smooth-score certificate with additive target concentration. In a registered three-requirement study, direct mode raises power from $5.6\%$ to $64.2\%$ at reliability $0.95$, while named mode remains stronger under high-signal evidence. Prospective audits span full-pipeline Rice--TVAE, which retrains on every draw, and a non-tabular text mechanism.
Source:https://arxiv.org/abs/2608.18643PreviousCalArena: A Large-Scale Post-Hoc Calibration BenchmarkNextRevenge of Monosemanticity: Neuron Specialization as a New Form of Feature Learning in MLPs
Related posts
The Autonomous Edge — Issue #13: Cheaper Agents, Harder Governance (Week of November 2, 2026)
0dev.to AI

Plano Físico vs Plano Funcional en AWS Networking: cómo los arquitectos senior resuelven lo que otros no ven
0dev.to AWS
We built Origami Tutor: free paper-craft lessons you can turn and replay in 3D
0dev.to WebDev
From two authorized photos to a short AI rap video (consent-first workflow)
0dev.to WebDev
Check a File Hash in the Browser, Without Uploading the File
0dev.to WebDev
Your AI keys were leaked at a platform. A local guard you can paste catches the abuse before the invoice.
0dev.to Security