AI & ML
Instance-dependent sequential limits as an exact information ledger
arXiv stat.TH0 views
arXiv:2610.42133v1 Announce Type: cross Abstract: Instance-dependent limits for bandit regret, sequential tests, best-arm identification and Markov decision processes are proved by one chain. It runs from a divergence decomposition through data processing to a statistic, a testing step that turns a class guarantee into a requirement on the history, and optimization over alternatives and allocations. Only the first step is an identity. This work writes the chain as an exact ledger. By the chain rule, data processing loses exactly a conditional divergence, which vanishes for arms in natural exponential families at the per-arm counts and reward sums. A one-parameter family of martingale identities extends the decomposition to every tilt between two instances. The classical limits follow by relaxations with named defects. All defects but the asymptotic step's can be computed from an algorithm's own runs, the uniform quantification's only when the class guarantee is a number. On seven published sources, from movie ratings to engine replacement, the ledger locates the difference between standard algorithms and the classical limits. For identification among trained models and for Wald's test the largest term is usually the uniform quantification's.
Source:https://arxiv.org/abs/2610.42133PreviousUncertainty Quantification for Topological Treatment EffectsNextSimple and Sharp Generalization Bounds via Lifting
Related posts
I built a native Windows app to track subscription waste (Vortex Pay)
0dev.to
I gave my free D&D one-shot preview 7 days to prove itself — day 4: a sibling product closed today at zero, mine has three days left
0dev.to

Hoje é #domingo. Use sua IA para algo besta, por favor.
0dev.to AI
How to export a ChatGPT conversation (Markdown, PDF and more)
0dev.to AI
From Brief to Published in Five Minutes: A Practical AI Video Workflow for Small Teams
0dev.to AI
GitHub Actions Is Changing pull_request_target — Check Your Workflows Before December 2
0dev.to DevOps