Bayes with No Shame: Admissibility Geometries of Predictive Inference

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2603.05335v4 Announce Type: replace-cross Abstract: Modern predictive systems combine predictors, sequential monitors, prediction sets, and online strategies, each with a different certificate of optimality. We study four criterion-relative geometries: Blackwell risk dominance, anytime-valid admissibility, fixed-level marginal coverage with expected-length efficiency within a declared rank-indexed family, and choice-based approachability (CApp) boundary-feasibility. We embed the four procedure types in a common product space and prove witness-based pairwise non-nesting: for every ordered pair of criterion classes, an explicit predictive system is active in both relevant coordinates, belongs to one class, and fails the other. The result records non-nesting across different object spaces and partial orders; it does not assert practical incompatibility. We separate three measure-relative coherence notions. In conditionally i.i.d. models, posterior predictive means under a single prior are martingales under the prior predictive law. For a point null, anytime-valid admissibility within e-processes is equivalent to the nonnegative martingale property. Self-consistency under a predictor's own predictive law does not imply Blackwell admissibility, as shown by a Bernoulli log-loss counterexample. Coverage admissibility is certified by exchangeability ranks within the declared rank-indexed family, while CApp boundary-feasibility uses Cesaro steering. A constrained-Bayes design schema organizes the four paradigms without collapsing their distinct decision spaces, partial …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2603.05335
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.