DFAH-Bench: Benchmarking Observable Agent Instability in Financial Decision-Making

· Source: cs.CL updates on arXiv.org · Field: Technology & Digital — Artificial Intelligence & Machine Learning, FinTech & Digital Financial Services, Data Science & Analytics · Depth: Expert, quick

Summary

DFAH-Bench is a new replay benchmark designed to measure observable behavioral instability in financial agent decision-making, introduced on June 10, 2026. Unlike standard evaluation methods that only assess final decisions, DFAH-Bench analyzes three distinct channels: tool-call trajectories, evidence contacts, and decision concentration, without requiring access to internal reasoning. Across 8,127 replay episodes involving 10 models and 3 financial tasks, the benchmark revealed that high decision agreement does not guarantee process stability. Frontier models achieved 95% decision agreement but only 77% tool path agreement, an 18-percentage-point gap (95% CI: [0.14, 0.22]). Over 55% of high-agreement frontier models showed meaningful trajectory divergence. The study identified three behavioral profiles: pattern matchers, stable executors, and trajectory divergers. The benchmark code, replay logs, and an interactive results explorer are publicly available.

Key takeaway

For MLOps Engineers deploying financial decision-making agents, relying solely on outcome agreement metrics is insufficient. You must integrate process-level stability checks, such as analyzing tool-call trajectories and evidence contacts, to identify hidden behavioral instability. This ensures your agents achieve consistent decisions through reliable, repeatable processes, mitigating risks associated with unpredictable execution paths even when final outputs appear correct. Implement benchmarks like DFAH-Bench to gain deeper insights into agent reliability.

Key insights

Outcome agreement alone is an incomplete signal for financial agent stability; process consistency matters.

Principles

Method

DFAH-Bench measures instability via tool-call trajectories, evidence contacts, and decision concentration across replay episodes. It does not require hidden reasoning access.

In practice

Topics

Code references

Best for: Research Scientist, AI Scientist, Machine Learning Engineer, MLOps Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.CL updates on arXiv.org.