Case · DiggingBeagle record

Enterprise deployment agents rarely achieved full stakeholder and outcome closure

In 95 realistic but simulated customer-delivery tasks, the best tested agent resolved only 14 with all required outcomes and no incident, despite stronger partial scores.

Scope

arXiv:2610.22350, FDE-Gym simulated enterprise workflows (95 tasks, 20 project origins, 18 sectors).

Assessment profile

Assessment method
Setting
simulation
Exploitation
not established
Evidence
Grade B
Remediation
not applicable
AI role
WITH AI
Basis and provenance

The FDE-Gym arXiv study specifies 95 constructed tasks, 20 customer project origins, 18 sectors and a resolution threshold including zero incidents. It supports an empirical model-capability limitation, not a vulnerability exploited in the wild or an actual enterprise loss rate. Model grades remain tied to the paper's synthetic settings.

Assessed Oct 18, 2026 using diggingbeagle.assessment/1.

At a glance

Claims & evidence

CLM-CP13-FDE-DISCOVERThe evaluation shows that uncovering key stakeholder requirements and obtaining an acceptable end-state are distinct hurdles.supported

Basis: reported finding

Link to claim
CLM-CP13-FDE-RESOLVEDThe leading tested configuration resolved 14 of 95 FDE-Gym tasks under the defined score and no-incident threshold, not 56% full project completion.supported

Basis: reported finding

Link to claim
CLM-ENRICH-FDE-BASELINEIn the simulated benchmark, Claude Haiku 4.5 scored worse than leaving the customer system unchanged on 79 of 95 tasks, whereas the best mean-scoring configuration resolved 14 of 95 under the study's incident and uplift criteria.supported

Basis: reported finding

Link to claim

Implications

A coding benchmark pass cannot stand in for safe delivery to a customer whose constraints are only partly known. Failed requirement discovery can result in an accurate implementation of the wrong objective. Authorization and rollback tests must therefore be evaluated separately from synthetic business improvement, not inferred from the resolved-task score.

Controls and mitigations

  • Use an explicit stakeholder requirement and authorization checkpoint before state-changing delivery, with independent measurement of whether the system improves the intended customer outcome.
  • Penalize unauthorized incidents, unproductive stakeholder contact and residual system changes, and compare delivered artifacts to a do-nothing baseline rather than only unit-test success.

Unknowns and contradictions

  • Simulated stakeholders are not a representative sample of real consulting engagements.
  • Human professional reference and external site effects were not exhaustively compared.

Sources and citation

Material revision history

  1. Oct 18, 2026 · Canonical change recorded · new in release · revision 171