FDE-Gym evaluates agents that must deliver useful changes for a simulated enterprise customer, not just pass a code test. Each task places an agent among stakeholders, editable systems, partial or hidden requirements and costs for unnecessary messages, delays or incidents. The decisive problem is often finding the right requirement before modifying…
Inspect the ClaimsCase · 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.
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.
Evidence basis: CLM-CP13-FDE-DISCOVER · CLM-CP13-FDE-RESOLVED · CLM-ENRICH-FDE-BASELINE · FDE-Gym: realistic enterprise agent deployment workflows
At a glance
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.
Read the implicationsSimulated stakeholders are not a representative sample of real consulting engagements. Human professional reference and external site effects were not exhaustively compared.
Limits and uncertaintyFull account
FDE-Gym evaluates agents that must deliver useful changes for a simulated enterprise customer, not just pass a code test. Each task places an agent among stakeholders, editable systems, partial or hidden requirements and costs for unnecessary messages, delays or incidents. The decisive problem is often finding the right requirement before modifying anything: success depends on the customer's actual business outcome rather than the visible task description alone.
The benchmark contains 95 tasks inspired by 20 projects across 18 sectors. Its highest reported mean score was approximately 0.56, yet that configuration satisfied the study's stricter resolved condition on only 14 of 95 tasks. The threshold combines a reference-relative uplift of at least 0.8 with no incident. Even where the leading agent discovered all essential facts on 23 tasks, only 10 reached the uplift threshold. A different tested model performed worse than leaving the customer's system unchanged on 79 of 95 tasks. These are separate measures and should not be presented as one rate.
The cases are designed and graded simulations, not reports that named corporate customers were damaged by agents. The study provides an especially useful distinction between question-answer accuracy, stakeholder discovery, an implemented technical artifact and measurable end-state improvement. A production replication would require consented real customer work, independent outcome measurements and an accounting of review time and mistakes, not simply another benchmark score.
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
- supportsFDE-Gym: realistic enterprise agent deployment workflowsprimary disclosure
Requirement discovery/outcome decomposition
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
- supportsFDE-Gym: realistic enterprise agent deployment workflowsprimary disclosure
Scoring definition, resolved threshold and main results
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
- supportsFDE-Gym: realistic enterprise agent deployment workflowsprimary disclosure
Abstract and Key Findings, do-nothing baseline and 14-of-95 resolution result
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
- Oct 18, 2026 · Canonical change recorded · new in release · revision 171