AI & ML
The Endogeneity of Miscalibration: Impossibility and Escape in Scored Reporting
arXiv cs.MA0 views
arXiv:2605.07671v4 Announce Type: replace-cross Abstract: An agent's probability report is paid for twice: by a strictly proper scoring rule, which rewards accuracy, and by an approval rule for the decision it triggers. An approval rule that is not affine is known to defeat truthful reporting. We show the conflict is built in: whenever perfect screening is attainable, the welfare-maximizing approval rule is never affine. The distortion is predictable: there is a reserve report at which pretending to be the marginal type costs exactly what approval is worth. Approving every report at or above the reserve sorts agents as if their beliefs were observed, under every strictly proper score and for any belief distribution. So does a continuous rule with one corner; under strict feasibility no continuously differentiable rule does. The binding constraint is steepness, not smoothness: a slope-capped rule sorts perfectly if and only if the cap reaches the critical slope, the steepest chord of the pretending cost up to the reserve; below it the welfare loss is cubic in the shortfall. For the Brier, log and power scores, and whenever the pretending cost is convex up to the reserve, the critical slope has a closed form. The instances are AI-agent oversight and marketplace operation.
Source:https://arxiv.org/abs/2605.07671PreviousSelf-Evolving Multi-Agent Framework for Efficient Decision Making in Real-Time Strategy ScenariosNextDAST: A VLM-LLM Framework for Cross-Interface Anomaly Detection in O-RAN
Related posts
Reading project health off a download page — faster than star count
0dev.to
Best time trackers for developers, for code and for AI
0dev.to

Serving Qwen3.5-0.8B with a 0.016% weight edit: measure the loops, pin the sampling on the server
0dev.to
Design Tokens for AI: Extract a Website's Real Colours, Fonts, Shadows and Icons So an LLM Builds On Brand
0dev.to
Trying to get our Arms around AI efficiency
0Stack Overflow Blog
Why an Embedded Game Fails on Some Phones, and How to Debug It
0dev.to