Papers
Topics
Authors
Recent
Search
2000 character limit reached

AgentMercury: Your Agent Can Synthesize Verifiable Environments for Business Scenarios at scale

Published 21 Aug 2026 in cs.CL and cs.AI | (2608.20634v1)

Abstract: Agents learn to act through interaction with environments, yet the environments used for training are often manually constructed or synthesized around predefined tasks and benchmarks. This task-centric paradigm makes it difficult to scale environments that reflect realistic and evolving workflows where diverse tasks can naturally emerge from the underlying world. We introduce AgentMercury, a scalable framework for synthesizing executable environments from high-level business scenarios. Rather than constructing an environment for a specific task, AgentMercury first instantiates a persistent world with entities, services, tools, state, and executable cross-service invariants, from which diverse tasks and interaction trajectories can subsequently emerge. We construct 4,783 executable environments spanning 14 industries and 50 countries, and use them as training substrates for reinforcement learning. Despite being generated without targeting the evaluation benchmarks, policies trained on these business-oriented environments improve substantially on both enterprise workflows and out-of-domain benchmarks spanning reasoning, coding, scientific computing, and tool use. In our experiments, Qwen3.5-4B improves from 12.3 to 15.7 on EnterpriseOps-GYM and from 45.9 to 56.0 on AIME26 after training on AgentMercury environments. We further show that the construction process itself can be learned: fine-tuning Qwen3.5-35B-A3B on construction traces increases executable-world authoring success from 3.3% to 83.3% on held-out business scenarios. These results show that scenario-grounded environments can provide useful and generalizable learning signals beyond benchmark-specific training, while their construction can itself become a learnable capability.

Authors (2)

Summary

  • The paper presents the AGENTMERCURY framework, which reorganizes agent-environment interfaces for high-level business scenarios.
  • AGENTMERCURY constructs persistent, stateful, multi-service environments, enabling agents to learn from multiple tasks and interactions sampled from coherent business worlds.
  • Training on executable environments improves metrics in various benchmarks like ENTERPRISEOPS-GYM on 8 tasks, including AIME26 by over 100% and SCICode by over 12%, by 14 on average.

AGENTMERCURY proposes a reorganization of the agent-environment interface around three distinct roles: PLANET constructs the world, a task generator instantiates objectives within that world, and a policy acts through executable tools. The paper’s central claim is that scalable agent training should not be organized exclusively around benchmark-specific tasks. Instead, high-level business scenarios should be compiled into persistent, stateful, multi-service environments from which multiple tasks and interaction trajectories can be sampled. The framework is intended to make environment construction an explicit and potentially learnable component of the agent system (2608.20634).

Scenario-grounded environment construction

The paper identifies a structural limitation in conventional agent environments. Manually authored environments and task-conditioned synthesis pipelines generally begin with a predefined task, user instruction, or benchmark specification. This facilitates controlled evaluation, but it couples the underlying world to the objective used to define it. Increasing task count can therefore increase instance volume without substantially increasing diversity in services, state transitions, entities, or cross-system dependencies.

AGENTMERCURY reverses this construction order. Given a high-level business scenario σ\sigma, PLANET produces an executable world ww containing:

  • entities and company identity;
  • a service graph;
  • persistent state schemas and seeded data;
  • executable tools and observation interfaces;
  • transition dynamics;
  • world-level invariants represented as executable verification conditions.

Tasks are generated only after the world exists. A task generator modifies the initial state, produces a natural-language objective, and derives a task-specific rubric. Multiple task instances can consequently share the same services, state schema, transition logic, and invariants while differing in user intent, initial conditions, and required actions.

This factorization is technically important because it separates three types of semantics that are often conflated. The transition function determines how tool calls modify the software state. The task rubric determines whether a particular objective has been achieved. World-level invariants specify cross-service properties that should hold but are not automatically enforced by the simulator. For example, a workflow may require an agent to create a downstream record after an upstream business event. The environment does not perform that action on the agent’s behalf; it evaluates the resulting state against the invariant after interaction.

The distinction between visible and hidden invariant views further separates agent information from evaluation logic. An invariant may be discoverable through documents, policies, or service interactions, while its hidden executable form is retained by the grader. This arrangement allows the agent to reason about requirements without being given a direct evaluation oracle, while preserving deterministic post-episode verification.

Executable worlds and deterministic grading

The environments are implemented as executable software worlds rather than static text-generation tasks. Agents interact through MCP-style tools, receive observations through an environment interface, and modify persistent state through deterministic transitions. With a fixed initial seed and action sequence, trajectories can be replayed and re-evaluated. The resulting “golden reasoning trace” provides a reproducible basis for reward computation and failure analysis.

The grader evaluates the terminal state and trajectory against task-specific assertions and hidden world-level constraints. Whenever possible, these checks operate directly over database state and include record-existence, field-equality, and field-inequality assertions. This design is particularly suitable for long-horizon tool use because textual plausibility is insufficient: a successful trajectory must produce the required state changes across the relevant services.

The framework therefore avoids relying exclusively on LLM-based judging for the central training signal. The paper does use an LLM judge in selected interactive benchmark evaluations and includes a reward implementation with behavior penalties, but the synthesized environments themselves are grounded in programmatic execution and verification. This improves reproducibility and reduces ambiguity in reward assignment, although it does not eliminate possible specification errors in the generated worlds.

Scale and structural composition

The paper reports 4,783 executable environments spanning 14 industries and 50 countries. The RL corpus is described more specifically as containing 43,300 tasks instantiated from 4,326 company environments. These environments expose heterogeneous tools, state tables, and service combinations. The reported task corpus includes 2,287 industry descriptions, 842 tools, 222 state-table types, and 148 service combinations. Each environment exposes between 10 and 26 tools, with a mean of 16.1; each task touches between one and five services, with a mean of 2.9; and each task contains a mean of 5.4 programmatic assertions.

Corpus property Reported value
Executable tasks 43,300
Company environments used for RL 4,326
Industry descriptions 2,287
Unique tools 842
State-table types 222
Service combinations 148
Tools per environment 10–26, mean 16.1
Services per task 1–5, mean 2.9
Assertions per task 2–10, mean 5.4

The corpus contains substantial cross-system structure: 25,991 of the 43,300 tasks are flagged as involving cross-system action risk. In the principal Qwen3.5-4B GRPO run, only 3,200 task instances received gradients over 200 training steps, representing 7.4% of the full task corpus. Nevertheless, those tasks covered 53.5% of environments, 62.9% of industries, 75.8% of tools, 61.7% of state tables, and 62.8% of service combinations. The authors use this result to argue that world-level coverage, rather than raw task count, is a more informative measure of training diversity.

The appendix qualifies this diversity claim. Textual descriptions are often generated from shared templates, and nearest-neighbor analysis yields a median TF-IDF similarity of 0.83, with 8.3% of tasks having a nearest neighbor above 0.99. Only 17% of these near-twin pairs originate from the same environment, suggesting that redundancy is driven substantially by shared templates across environments rather than merely by repeated seeds. More meaningful separation appears in tool-set space, where tasks cluster according to executable service structure. However, the number of exposed tools takes only five values—10, 14, 18, 22, and 26—because each additional resource contributes a fixed group of four tools. Thus, the task space has substantial operational variation but is not an unconstrained continuum.

Policy optimization results

AGENTMERCURY trains Qwen3.5 policies with GRPO and, at the larger model scale, SAO. The training environments are constructed independently of the evaluation benchmark tasks. This experimental separation is intended to test whether the environments provide transferable policy-learning signals rather than reproducing benchmark-specific task distributions.

On ENTERPRISEOPS-GYM, Qwen3.5-4B improves from an average score of 12.3 to 15.7 after GRPO training, a gain of 3.4 points or 27.6%. The strongest domain-level improvements occur in Drive and Email, each increasing by 9.4 points, from 6.2 to 15.6 and from 23.9 to 33.3, respectively. Hybrid increases from 11.7 to 17.0, Calendar from 10.4 to 13.1, Teams from 20.8 to 23.0, and HR from 9.5 to 10.8. CSM is the exception, declining from 9.2 to 5.6. The aggregate gain therefore coexists with a domain-specific regression, indicating that transfer is not uniformly distributed across enterprise workflows.

At the 35B-A3B scale, the base average is 24.8. GRPO raises it to 28.1, while SAO raises it to 28.3. These correspond to improvements of 13.3% and 14.1%, respectively. Both methods improve all eight enterprise domains in the reported results. The comparable performance under two optimization procedures supports the claim that the learning signal is not specific to GRPO, although the experiments do not establish equivalence between the algorithms or identify which environmental properties drive the gains.

Model and training EnterpriseOps-GYM average
Qwen3.5-4B 12.3
Qwen3.5-4B + GRPO 15.7
Qwen3.5-35B-A3B 24.8
Qwen3.5-35B-A3B + GRPO 28.1
Qwen3.5-35B-A3B + SAO 28.3

The out-of-domain results are the paper’s strongest empirical support for scenario-grounded training. Qwen3.5-4B + GRPO improves on AIME26 from 45.9 to 56.0, HMMT from 28.5 to 35.4, LiveCodeBench from 36.6 to 44.0, SciCode from 22.6 to 25.7, BFCL from 30.3 to 31.7, GPQA-Diamond from 76.5 to 77.5, Tau-3 Airline from 48.8 to 58.7, and Tau-3 Retail from 70.4 to 73.6. Tau-3 Telecom slightly decreases from 92.5 to 91.9.

The transfer is particularly pronounced for the smaller model on mathematical reasoning and coding, despite those benchmarks not being represented as target tasks during environment construction. At 35B-A3B scale, the absolute improvements are smaller on already strong reasoning benchmarks but remain substantial for tool-oriented evaluation. SAO increases BFCL from 31.1 to 42.1, LiveCodeBench from 74.3 to 78.6, HMMT from 77.0 to 83.3, and GPQA-Diamond from 82.8 to 84.0. The BFCL result is consistent with the hypothesis that training on structured, multi-step tool interactions preferentially improves function selection and argument formation.

The authors also report reduced variance on interactive benchmarks. For example, Qwen3.5-35B-A3B’s base performance on Tau-3 Telecom is 49.1 ± 49.8, compared with 65.5 ± 23.8 after SAO training. On Retail, the standard deviation falls from 22.1 to 10.2, while Airline improves from 39.1 ± 10.6 to 50.9 ± 8.1. The implication is not merely higher expected reward but more consistent sequential behavior across sampled interactions. This interpretation is plausible for stateful tool-use tasks, although the number of independent evaluation runs is only three and the reported variance estimates should therefore be treated cautiously.

Training diagnostics indicate that reward increases while truncation declines and degenerate-response rates remain near zero. For the 4B GRPO run, reward rises toward approximately 0.55–0.60, while truncation falls from roughly 0.35 to nearly zero. For the 35B runs, GRPO reward increases from about 0.4 to 0.55–0.60, and SAO reward rises from approximately 0.35 to above 0.6. These observations argue against a simple reward-hacking explanation based on pathological output growth or response collapse. They do not, however, prove that the reward captures all aspects of competent business behavior; the environments’ own validators remain the operative definition of success.

Learning to author executable worlds

The second experiment treats environment construction as an agentic capability. Models receive held-out high-level business briefs and must produce executable world specifications. Success requires passing all 12 structural validators, rather than merely generating plausible text.

Strong API models achieve zero-shot oracle-pass rates ranging from 66.7% to 90.0%. The paper reports a mean of 80.7% in the detailed authoring analysis, while one displayed summary reports 78.3%; this inconsistency is not resolved in the text. Recipe conditioning, which supplies an invariant digest and a trimmed construction exemplar, does not reliably improve performance. Across the API models, the mean reportedly decreases from 80.7% to 78.0%, and exact McNemar tests yield p0.375p \geq 0.375 for every individual model. The result contradicts the straightforward expectation that more explicit procedural information should monotonically improve structured generation.

The dominant failure mode concerns cross-service invariants. Models frequently place both the trigger and target of an invariant within the same service, thereby preserving superficial syntactic validity while violating the intended inter-service dependency. GPT-5.4 exhibits this error on 10 of the 30 held-out briefs. Recipe conditioning can also increase formatting and parsing failures by imposing a longer output protocol. These results establish why executable validation is necessary: surface-level inspection cannot reliably detect semantically incorrect service graphs or invalid cross-service constraints.

Construction traces provide a substantially stronger intervention. The authors fine-tune Qwen3.5-35B-A3B on 29,823 samples covering brief-to-world generation, intermediate-stage completion, validator-guided repair, and intent-to-diff prediction. Full oracle success rises from 3.3% to 83.3% on the 30 held-out briefs. The model passes an average of 11.5 of 12 validators, with truncation and formatting failures nearly eliminated. A Fisher exact test reports p=1.2×1010p = 1.2 \times 10^{-10}, and the reported Wilson 95% confidence intervals are [0.6, 16.7] for the base model and [66.4, 92.7] after fine-tuning.

The recipe interaction produces an especially strong and contradictory result. For the base Qwen3.5-35B-A3B, recipe conditioning increases success from 3.3% to 20.0%. After fine-tuning, the same recipe reduces success from 83.3% to 10.0%; 27 of 30 recipe-conditioned generations fail cross-service validation. This asymmetry suggests that parameter-level learning and in-context procedural prompting are not interchangeable. Once the construction procedure is internalized, an external recipe may interfere with the learned serialization format or structural policy. The finding also argues against interpreting the fine-tuning gain as mere generic instruction following.

Limitations and open questions

The evidence is persuasive for feasibility but narrower than the framing of general environment scaling. The environment distribution is limited to synthetic business scenarios, and its realism is established primarily through structural properties—services, tools, state, and validators—rather than through comparison with operational enterprise traces or expert judgments of workflow fidelity. The scenarios, company identities, schemas, and invariants are generated within one construction pipeline, so correlated errors between authoring and grading remain possible.

The transfer experiments also lack several controls needed to isolate the source of improvement. The paper does not report matched training on an equal number of task-centric environments, ablations removing persistent state or cross-service invariants, or comparisons against synthetic tasks with equivalent tool and token budgets but reduced world structure. Consequently, the results demonstrate that AGENTMERCURY training is useful, but do not establish that scenario-grounded construction is superior to all alternative forms of executable task synthesis.

The out-of-domain evaluation is based on three independent runs, and some benchmark results show substantial variance, particularly for Tau-3. Several evaluations use repeated sampling per problem or task, so the effective statistical dependence and confidence intervals are not fully characterized. Moreover, the 4B SAO run was excluded from the principal comparison because its learning signal was judged insufficiently stable. This is a reasonable methodological decision, but it limits conclusions about optimizer–scale interactions.

The authoring evaluation uses only 30 held-out briefs. The large change from 3.3% to 83.3% is statistically strong under the reported test, but the interval remains broad because of the small sample. The discrepancy between the reported authoring means—78.3% in the displayed results and 80.7% in the accompanying analysis—also warrants clarification. Finally, PLANET is not yet coupled to policy failures or a learned world model. The generator does not select new scenarios adaptively based on capability gaps, and the system therefore does not yet demonstrate a closed environment-generation and policy-learning loop. The specific unresolved question is whether a policy can identify informative missing interaction structures and cause PLANET to synthesize environments that improve those capabilities without introducing exploitable artifacts.

Conclusion

AGENTMERCURY presents executable business worlds as the primary unit of scalable environment construction. Its separation of world synthesis, task instantiation, interaction, and deterministic grading supports persistent multi-service workflows and reusable training substrates. Training on 4,783 synthesized environments yields measurable gains on enterprise and unrelated reasoning, coding, scientific-computing, and tool-use benchmarks, while construction traces raise held-out world-authoring success from 3.3% to 83.3%. The results support treating environment construction as both a first-class systems role and a learnable capability, while leaving open whether the same framework can achieve empirically validated realism, stronger causal transfer controls, and adaptive generation driven by policy-level deficiencies.

Paper to Video (Beta)

No one has generated a video about this paper yet.

Whiteboard

No one has generated a whiteboard explanation for this paper yet.

Explain it Like I'm 14

1. What is the paper about?

The paper introduces AGENTMERCURY, a system for creating realistic computer “worlds” in which AI agents can practice completing business tasks.

An AI agent is a computer program that can make decisions, use tools, and interact with software. For example, an agent might read emails, update a customer record, schedule a meeting, or change information in a company database.

Usually, researchers create an environment for one specific task, much like designing one puzzle for a student. AGENTMERCURY takes a different approach: it creates an entire business world first. Many different tasks can then be created inside that world.

The authors also investigate whether AI can learn to build these worlds itself.

2. Main research questions

The paper mainly asks two questions:

  1. Can realistic, automatically created business environments help AI agents learn? In other words, if an AI practices in many different business worlds, will it become better not only at business tasks but also at mathematics, coding, and other problems?
  2. Can an AI learn how to create executable environments? The researchers want to know whether an AI can read a description such as “a healthcare company with billing and appointment systems” and turn it into a working computer simulation.

The paper also explores a larger idea: instead of focusing only on making more test questions, should researchers create more varied and realistic worlds for AI agents to explore?

3. How did the researchers conduct the study?

Creating complete business worlds

AGENTMERCURY begins with a high-level business scenario, such as a company in a particular industry and country. A component called PLANET then constructs a working environment containing:

  • Companies, customers, employees, products, and other entities
  • Software services, such as email, calendars, databases, or customer-management systems
  • Tools that the AI agent can use
  • Information that remains saved over time
  • Rules connecting different services
  • Starting conditions for the world

For example, imagine a retail company. An agent might receive a request to refund a customer. To succeed, it may need to:

  1. Find the customer’s order.
  2. Check the payment system.
  3. Issue the refund.
  4. Update the customer-support record.
  5. Send an email confirmation.

The environment checks whether all these actions led to a correct final result.

Persistent state

“Persistent state” means that the world remembers what has happened. This is similar to a video game save file. If an agent changes a customer’s address or cancels an order, that change remains in the system and can affect later actions.

This is more realistic than a simple question-and-answer test, where every problem starts from zero.

Cross-service rules

The environments include cross-service invariants. These are rules that connect different parts of the system.

For example:

If an order is refunded in the payment system, the customer-support system should also contain a record of that refund.

The environment does not automatically fix mistakes for the agent. Instead, it checks afterward whether the agent followed the rule.

Deterministic grading

The researchers use executable graders to judge the agent’s performance. A grader is like an automatic referee. It checks the final database and interaction history to see whether the task was completed correctly.

Because the starting situation and the agent’s actions are recorded, the researchers can replay the same sequence and check the result again. This makes evaluation more reliable than asking another AI to decide whether an answer “sounds correct.”

Training the AI agent

The researchers trained Qwen3.5 models using reinforcement learning. This is similar to training a student through practice:

  • The AI tries to complete a task.
  • It receives a reward for successful actions.
  • It receives a lower reward or no reward when it fails.
  • Over time, it learns which actions are more likely to work.

They trained on:

  • 4,783 environments
  • 14 industries
  • 50 countries
  • 43,300 task examples

They used two reinforcement-learning methods, called GRPO and SAO, to check whether the results depended on only one training method.

Finally, they tested the trained models on both business benchmarks and unrelated tests involving mathematics, coding, science, knowledge, and tool use.

Training an AI to build environments

The researchers also collected “construction traces.” These are records showing the steps used to turn a business description into a working environment.

They used nearly 30,000 examples of these steps to fine-tune a Qwen model. They then tested whether the model could build environments for 30 new business descriptions that it had not seen before.

A generated world counted as successful only if it passed all 12 structural checks. This meant the world had to be executable and logically consistent, not merely well-written.

4. Main findings

The environments helped AI agents improve

Training in AGENTMERCURY environments improved performance on business tasks.

For example, the smaller Qwen3.5-4B model’s average score on EnterpriseOps-GYM increased from 12.3 to 15.7. The larger model improved from 24.8 to 28.1 using GRPO.

The model improved in most business areas, including:

  • Email
  • Calendars
  • File storage
  • Team communication
  • Human resources
  • Customer-service workflows

Some individual areas did not always improve. For instance, the smaller model’s score on one customer-service category decreased. This shows that the results were not perfect in every area.

Improvements transferred to unrelated subjects

A particularly important result is that the training environments were not designed around the tests used later. Even so, the agents improved on several unrelated benchmarks.

For the Qwen3.5-4B model:

Test area Before training After training
AIME26 mathematics 45.9 56.0
HMMT mathematics 28.5 35.4
LiveCodeBench programming 36.6 44.0
SciCode scientific programming 22.6 25.7
Airline tool-use tasks 48.8 58.7

The model also improved on many tests involving tool use and general knowledge. One telecom benchmark stayed almost the same, showing that the benefits were not universal.

This suggests that practicing in complex business worlds may teach general skills such as:

  • Remembering information across many steps
  • Planning actions in the correct order
  • Using different tools
  • Tracking changes in a system
  • Following rules and constraints
  • Recovering from complicated workflows

These skills can be useful in many different subjects.

The training made some agents more reliable

For the larger model, performance became less variable across repeated tests. This means the agent was not only sometimes successful; it behaved more consistently.

Consistency matters for real-world AI systems. An agent that succeeds once but fails unpredictably the next time would be difficult to trust with important business work.

AI can learn to create working environments

The researchers found that powerful existing AI models could already create valid environments from business descriptions. Several outside models had success rates between about 67% and 90%.

However, the original Qwen3.5-35B-A3B model succeeded on only 3.3% of the test scenarios.

After being trained on AGENTMERCURY’s construction examples, its success rate rose to 83.3%. It also passed an average of 11.5 out of 12 structural checks.

This is a major improvement. It suggests that creating an environment can become a learned AI skill rather than something humans must always program by hand.

The hardest errors involved rules connecting multiple services. For example, a model might understand an order system and a payment system separately but fail to correctly connect them.

5. Why are these findings important?

Many AI training environments are built around one task, one question, or one benchmark. This can cause the AI to learn narrow tricks that work only on familiar tests.

AGENTMERCURY tries to create richer worlds instead. A single world can support many tasks, just as a real company’s software can be used for thousands of different activities.

The paper’s results suggest that:

  • More realistic environments may teach broader skills.
  • Training does not always need to target the exact test that will be used later.
  • Business workflows are useful practice because they involve many tools, steps, rules, and changing information.
  • AI may eventually help researchers create new training worlds automatically.

This could make it faster and cheaper to train agents for jobs such as customer service, office administration, software support, logistics, healthcare management, and finance.

Simple conclusion

AGENTMERCURY is a method for building large numbers of realistic, computer-based business worlds for AI agents to practice in. Instead of making one environment for each task, it creates a complete world from which many tasks can arise.

The study found that agents trained in these worlds became better at business tasks and also improved at mathematics, coding, science, and tool use. It also showed that an AI could learn to construct new environments when trained on examples of the building process.

The potential impact is significant: future AI systems might learn in many automatically generated, testable worlds before being used in real workplaces. However, the environments are still simulations, so further research is needed to determine how well improvements transfer to real companies and real-world situations.

Knowledge Gaps

The paper leaves the following knowledge gaps, limitations, and open questions unresolved:

  • Semantic realism is not established: The paper evaluates whether generated environments are executable and structurally valid, but does not demonstrate that their business processes accurately reflect real organizational workflows or expert expectations.
  • Human and domain-expert validation is missing: No systematic assessment by professionals from the 14 industries is reported to verify the plausibility, usefulness, or operational relevance of the synthesized companies, services, data, and policies.
  • The scope of business scenarios is unclear: The paper does not specify how scenarios were collected, authored, or sampled, making it difficult to determine whether the 4,783 environments represent genuine diversity or repeated templates with superficial variation.
  • Synthetic-data artifacts may explain transfer gains: The study does not isolate whether performance improvements arise from generalizable interaction skills or from regularities, formatting conventions, and tool schemas specific to AGENTMERCURY.
  • Causal attribution is underdeveloped: There is no comprehensive ablation comparing the contributions of multi-service structure, persistent state, cross-service invariants, deterministic grading, scenario diversity, and task diversity.
  • The benefit of scenario-grounded construction over task-centric synthesis is not directly tested: The experiments do not include a matched task-centric baseline with comparable scale, compute, task count, and tool complexity.
  • Environment diversity is not quantitatively characterized: The paper reports industry and country counts but does not measure diversity in workflows, transition graphs, schemas, tool affordances, invariant types, difficulty, or trajectory distributions.
  • Country and industry variation may be superficial: It remains unresolved whether environments differ meaningfully across countries and industries or primarily vary in names, metadata, and surface-level business context.
  • Generalization to real-world environments is unknown: Transfer is measured on other benchmarks, but not on live enterprise systems, human-designed simulators, real business datasets, or deployment-oriented workflows.
  • Out-of-domain improvements lack stronger controls: The study does not compare against continued pretraining, supervised fine-tuning, tool-use demonstrations, generic RL tasks, or additional RL compute to determine whether AGENTMERCURY provides uniquely effective learning signals.
  • Possible benchmark contamination is not fully ruled out: Although the training environments were not intentionally built from evaluation tasks, the paper does not provide a detailed provenance or overlap analysis for scenarios, tools, instructions, code, and benchmark data.
  • Evaluation breadth is limited by sample size: Each benchmark is evaluated over only three independent runs, and the authoring experiment uses just 30 held-out briefs, limiting confidence in reported means, variance estimates, and statistical conclusions.
  • Statistical testing is incomplete: Apart from the authoring comparison, the paper does not report significance tests, confidence intervals, effect sizes, or corrections for multiple benchmark comparisons.
  • The EnterpriseOps-GYM evaluation remains relatively low-performing: Even after training, absolute performance remains modest on several domains, and the causes of persistent failures—especially CSM, ITSM, and Hybrid tasks—are not analyzed in depth.
  • Training and evaluation distribution separation is incomplete: The paper states that environments are independent of evaluation benchmarks, but does not clearly establish separation between training and evaluation industries, countries, service types, invariant patterns, or task templates.
  • Robustness to adversarial or malformed environments is untested: The policy is not evaluated against inconsistent state, deceptive observations, broken tools, conflicting invariants, distribution shifts, or environments containing authoring errors.
  • The deterministic environment assumption may reduce realism: Real business systems include stochastic failures, delays, concurrent updates, permission changes, and ambiguous or incomplete observations, none of which are substantially modeled.
  • Concurrency and multi-agent interaction are unexplored: The environments appear to involve a single agent acting sequentially, leaving unresolved how the framework handles concurrent users, asynchronous services, collaboration, competition, or conflicting changes.
  • Security, privacy, and access-control behavior are not evaluated: The paper does not examine authorization boundaries, sensitive data exposure, prompt injection, unsafe tool calls, auditability, or policy compliance in the synthesized business worlds.
  • Deterministic grading may permit reward hacking: Agents could exploit implementation details, hidden-state assumptions, or verifier weaknesses without performing the intended business objective; no adversarial verifier audit or human judgment comparison is provided.
  • The relationship between visible and hidden invariants is underspecified: It is unclear how much invariant information is exposed to agents, how discoverable it is through interaction, and whether hidden checks create an unrealistic evaluation mismatch.
  • Task generation may still constrain the claimed task diversity: Tasks are generated from the world’s invariants and seeded state, but the paper does not measure how many genuinely distinct objectives and trajectories each world supports.
  • Long-horizon difficulty is not systematically evaluated: The paper does not report performance as a function of horizon length, number of services, branching factor, state size, or dependency depth.
  • Environment construction cost and scalability are not reported: The computational, human, and engineering costs of producing and validating 4,783 environments, including failed generations and repair cycles, remain unclear.
  • Reproducibility details are incomplete in the provided paper: Important implementation information appears to be deferred to appendices that are not included, including task-generation procedures, hyperparameters, validator definitions, environment schemas, and training budgets.
  • The construction pipeline may rely on hidden engineering intervention: The extent to which human-written templates, manual corrections, validator-guided repair, or post-generation filtering contribute to the final environment quality is not quantified.
  • Authoring success is narrowly defined: Passing all 12 structural validators does not establish that a generated world correctly captures the intended scenario, supports meaningful tasks, or has valid business logic.
  • The authoring benchmark may be too easy or too closely aligned with the training procedure: The held-out briefs are sampled from the same country–industry distribution as the library, so generalization to novel industries, countries, organizational structures, and invariant types is unresolved.
  • The recipe-conditioning results are not explained: The sharp degradation from 83.3% to 10.0% for the fine-tuned model is reported but not diagnosed through controlled prompt, formatting, ordering, or content ablations.
  • Authoring-model generalization beyond Qwen3.5-35B-A3B is unknown: Only one model is fine-tuned on construction traces, so it is unclear whether the learned authoring capability transfers across architectures, model sizes, or training methods.
  • Construction traces may encode procedural or implementation-specific shortcuts: The paper does not test whether models learn general principles of world construction or merely imitate the particular schemas, code-diff formats, and validator patterns used by AGENTMERCURY.
  • No iterative authoring loop is evaluated: The work does not test whether a model can generate a world, execute validators, diagnose failures, revise the specification, and converge reliably without extensive external engineering.
  • The role of learned world models remains unexplored: Although the paper motivates world modeling, it does not train or evaluate a predictive world model on the synthesized environments, nor compare direct execution with model-based planning.
  • Transfer mechanisms are not identified: The paper shows aggregate gains on reasoning, coding, and tool-use benchmarks but does not determine which learned behaviors—planning, state tracking, tool syntax, persistence handling, or constraint satisfaction—produce those gains.
  • Negative transfer and capability trade-offs receive limited analysis: Some results decline or remain unchanged, such as CSM and Telecom for particular models, but the causes and broader conditions for negative transfer are not investigated.
  • Training stability across seeds and configurations is uncertain: The policy-learning experiments do not report a broad range of training seeds, curriculum choices, environment subsets, or reward configurations sufficient to establish robustness.
  • The release’s long-term maintainability is unresolved: The paper does not address how synthesized environments should be updated when business software APIs, policies, schemas, or real-world workflows change.

Practical Applications

Immediate Applications

  • Enterprise-agent training and evaluation platforms — software, consulting, and enterprise IT. Organizations can use the released AGENTMERCURY environments, construction code, and trained policies as reinforcement-learning substrates for agents that operate across email, calendars, document storage, HR, ITSM, CRM, and collaboration tools. A practical workflow would be: define a business scenario, instantiate a persistent synthetic company world, generate multiple tasks from it, train an agent, and replay its trajectories against deterministic verifiers before limited deployment. Evidence: training on synthesized environments improved EnterpriseOps-GYM performance, including the overall 4B score from 12.3 to 15.7 and the 35B score from 24.8 to 28.1. Dependencies: integration with the organization’s APIs, accurate modeling of permissions and workflows, privacy-preserving data generation, and validation that synthetic behavior transfers to the company’s real software stack.
  • Regression testing for tool-using agents — software engineering and quality assurance. The deterministic transition functions, seeded initial states, executable invariants, and replayable “golden reasoning traces” can support automated regression suites for agents. After a model, prompt, tool schema, or API changes, teams could replay identical trajectories and detect failures such as missing downstream records, invalid state transitions, or incorrect cross-service actions. Potential products: agent CI/CD systems, workflow simulators, tool-call replay services, and state-based acceptance-test generators. Dependencies: stable environment versions, representative service graphs, comprehensive validators, and protection against agents overfitting to known seeds or verification rules.
  • Benchmark and red-team generation — academia and industrial research. Researchers can generate multiple tasks from the same persistent world rather than building each benchmark around an isolated instruction. This enables tests of long-horizon planning, partial observability, state tracking, service coordination, constraint satisfaction, and recovery from errors. Hidden invariants can be used to evaluate whether an agent completed the intended workflow rather than merely produced plausible text. Dependencies: independent held-out scenarios are needed to avoid contamination; validators must cover semantic correctness, not only structural validity; results should be compared with human-authored environments.
  • Training for enterprise workflow automation — finance, retail, logistics, telecommunications, manufacturing, and energy. Companies can use industry-specific synthetic environments to train or fine-tune agents for tasks such as reconciling financial records, updating inventory across systems, scheduling logistics, handling service tickets, coordinating manufacturing orders, or managing energy-service workflows. The multi-service design is particularly relevant to operations where one action creates obligations in another system. Dependencies: domain experts must review scenarios and invariants, and deployment should initially use read-only or approval-gated actions. Synthetic environments may omit rare operational exceptions, regulatory requirements, or informal human practices.
  • Agent observability and reliability assessment — platform engineering and governance. Because trajectories are deterministic under fixed seeds and action sequences, developers can measure success rates, tool-call consistency, failure modes, response truncation, and run-to-run variance. This can be incorporated into model cards, deployment gates, and operational risk dashboards. The reported reduction in variance on some interactive benchmarks suggests a use for reliability testing in addition to average-score measurement. Dependencies: reliability in synthetic environments does not establish reliability in production; tests should include adversarial permissions, ambiguous requests, service outages, delayed responses, and changing data.
  • Automated authoring of internal training simulators — corporate learning and process design. Strong LLMs can already produce structurally valid executable worlds from high-level business briefs. Organizations could provide a process description and automatically obtain a simulator for onboarding, tool-use practice, or process certification. Human reviewers could inspect the generated service graph, state schema, and invariants before use. Evidence: off-the-shelf models achieved roughly 66.7%–90.0% oracle-pass rates on the held-out authoring set. Dependencies: generated worlds require executable validation; cross-service invariants are a known failure point, so model output should not be accepted based on textual plausibility alone.
  • Safe sandboxing for agent experimentation — education, academia, and daily productivity software. Students, developers, or users can experiment with agents in synthetic versions of email, calendars, file storage, ticketing, shopping, or scheduling systems without risking real data. This can support classroom exercises, developer prototyping, and consumer-facing “preview before execution” workflows. Dependencies: the sandbox must clearly distinguish simulated from real actions, and interfaces should prevent accidental connection to production credentials or services.
  • Policy and operational training simulations — government and public-sector administration. Public agencies can model scenarios involving procurement, case management, benefits administration, emergency logistics, or interdepartmental coordination. Agents and human operators can practice satisfying procedural and cross-system requirements before interacting with live systems. Dependencies: policy scenarios require legally reviewed rules, accessibility, auditability, and careful treatment of sensitive populations. Synthetic rules must not be mistaken for authoritative legal guidance.

Long-Term Applications

  • Self-improving environment-generation pipelines — AI research and developer tooling. PLANET’s construction traces could enable models to generate, modify, repair, and expand executable worlds from business briefs. A mature pipeline could automatically propose a service graph, create database schemas and tools, run structural validators, repair failed invariants, and produce new tasks for policy training. Evidence: fine-tuning Qwen3.5-35B-A3B on 29,823 construction traces increased held-out full-validator success from 3.3% to 83.3%. Dependencies: larger and more diverse authoring corpora, robust validators, protection against reward hacking, human review, and evaluation on real-world scenarios rather than only synthetic briefs.
  • Digital twins for enterprise operations — manufacturing, logistics, energy, healthcare, and finance. The framework could evolve from synthetic business worlds into calibrated digital twins that mirror an organization’s services, entities, persistent state, and constraints. Agents could rehearse process changes, forecast the consequences of tool calls, compare alternative workflows, and identify bottlenecks before changes are applied to production. Dependencies: secure synchronization with real data, accurate transition models, uncertainty estimation, handling of nondeterministic human and market behavior, and strict separation between simulation and live execution.
  • Pre-deployment certification for autonomous agents — regulated industries and policy. Regulators or industry consortia could require agents to pass standardized executable scenarios covering authorization, data handling, audit trails, multi-step obligations, and failure recovery. Hidden invariants would make it harder for systems to optimize merely for visible task instructions. Dependencies: agreement on sector-specific standards, independent benchmark governance, coverage of distribution shifts, explainable failure reports, and evidence that passing simulated tests predicts real operational safety.
  • Agent-assisted software integration and migration — enterprise software and robotics. Agents trained in multi-service environments could help migrate records, coordinate APIs, configure workflows, or operate heterogeneous software platforms. The same principle could extend to robotics fleets, where the environment includes physical assets, scheduling systems, maintenance databases, and warehouse-management tools. Dependencies: real APIs and physical systems introduce latency, stochastic failures, irreversible actions, and safety constraints absent from deterministic simulators. Hardware-in-the-loop testing and formal safety boundaries would be required.
  • Adaptive education and professional certification — education, healthcare, finance, and public administration. A system could generate persistent, branching simulations in which learners manage evolving cases rather than answer isolated questions. For example, trainees might coordinate a hospital workflow, resolve a supply-chain disruption, process a financial exception, or manage a public-service case while being assessed on final state and cross-system consistency. Dependencies: validated pedagogical objectives, expert-authored rubrics, fairness audits, calibrated difficulty, and safeguards against evaluating learners on artifacts of simulator design rather than genuine competence.
  • Scientific and engineering experimentation with agent policies — research and energy. Scenario-grounded environments could provide training and planning substrates for laboratory automation, computational science, energy-grid operations, and engineering design. The reported transfer to mathematical reasoning, coding, scientific computing, and tool-use benchmarks suggests that interaction-rich training may improve general procedural capabilities. Dependencies: transfer to scientific domains remains indirect; high-fidelity simulators, reproducible tool interfaces, domain constraints, and validation against physical experiments are necessary before consequential use.
  • Personalized daily-life automation with verifiable safeguards — consumer software and accessibility. Future assistants could construct a private synthetic model of a user’s calendars, files, subscriptions, travel plans, and household services. They could simulate alternatives—such as rescheduling appointments or planning travel—then execute only plans that satisfy explicit invariants such as budget limits, deadlines, accessibility requirements, or conflicting commitments. Dependencies: consent, local or privacy-preserving computation, accurate user preferences, secure authentication, transparent approval steps, and robust handling of ambiguous or changing information.
  • Large-scale policy and economic scenario analysis — government, finance, and energy. Collections of industry- and country-specific worlds could support stress testing of supply chains, financial operations, telecommunications services, energy demand, or regulatory changes. Agents could explore how decisions propagate across services and identify policies that maintain specified system-level invariants. Dependencies: the paper’s environments are synthetic and deterministic, whereas economies and public systems are stochastic and adaptive. Reliable use would require empirical calibration, uncertainty-aware simulation, causal validation, and safeguards against treating generated scenarios as forecasts.
  • Foundation models specialized for world construction — long-term AI architecture. The PLANET/policy/world-model separation suggests a future architecture in which one model constructs environments, another acts within them, and a third predicts their evolution. Such systems could continuously generate training worlds, evaluate policies, and update scenarios as workflows change. Dependencies: preventing coupled-model errors, maintaining diversity rather than generating repetitive worlds, detecting specification bugs, and establishing independent evaluation are central research problems. The inconsistent effect of recipe conditioning in the authoring experiment also indicates that prompting alone is not a dependable substitute for learned construction procedures.

Glossary

  • Agent–environment interaction: The iterative process in which an agent selects actions, an environment updates its state, and the agent receives observations; “We depict this overall flow at the Figure 1(A).”
  • Agentic system: A system that autonomously performs actions and interacts with an environment to achieve objectives; “Modern agentic systems learn to interact with environments through complementary capabilities for acting and modeling the world”
  • Cross-service constraint: A requirement linking states or events across multiple software services; “Each environment contains persistent state, multiple services and tools, and executable cross-service constraints that can be verified through interaction.”
  • Cross-service invariant: A property that must hold between entities or events belonging to different services; “For example, a cross-service invariant may require a downstream record to exist after an upstream business event”
  • Deterministic grading: Evaluation that produces the same result for the same trajectory and state; “The executable world provides not only an interaction substrate but also a deterministic basis for evaluating agent behavior.”
  • Deterministic transition: A state update whose result is fully determined by the prior state and action; “The environment then executes the selected action and deterministically updates its underlying state”
  • Environment authoring: The process of constructing an executable environment specification; “This experiment treats environment authoring as an agentic task with an explicit executable oracle”
  • Executable environment: A computationally runnable representation of a scenario that supports direct agent interaction; “We consider an environment as an executable representation of a business scenario in which an agent can directly interact with software services”
  • Executable oracle: A programmatic evaluator that runs and validates a generated environment; “This experiment treats environment authoring as an agentic task with an explicit executable oracle”
  • Executable transition function: The implementation that updates an environment’s state in response to an action; “T is the executable transition function implemented by the environment, rather than a model inferred during interaction.”
  • Execution substrate: The underlying software, data, and logic that enable an environment to run; “persistent data, services, tools, and transition logic forming the underlying execution substrate.”
  • GRPO (group relative policy optimization): A reinforcement-learning optimization method that compares sampled outcomes within groups to update a policy; “We use Qwen3.5-4B and Qwen3.5-35B-A3B (Qwen Team, 2026) as the primary training models and optimize the policy with group relative policy optimization (GRPO)”
  • Golden reasoning trace: A reproducible record of the state sequence implied by an initial state and action sequence; “We refer this as a golden reasoning trace.”
  • Held-out authoring set: Evaluation examples withheld from training to test generalization in environment construction; “We construct a held-out authoring set of 30 synthetic business briefs sampled from the country–industry distribution of the environment library.”
  • Hidden invariant view: The non-exposed form of an invariant containing executable checks used for evaluation; “The hidden view contains executable verification conditions used for deterministic evaluation.”
  • Horizon: The number of interaction steps represented in a trajectory; “A trajectory of horizon H is given by”
  • Invariant digest: A compact representation of the invariants required in a generated environment; “where the model is additionally provided with an invariant digest and a trimmed example of a previously constructed environment.”
  • Interaction trajectory: The ordered sequence of states, actions, and observations produced during an agent episode; “from which diverse tasks and interaction trajectories can subsequently emerge.”
  • Partially observable environment: An environment in which the agent cannot directly access the complete underlying state; “in the partially observable environments considered here, however, the underlying state is not directly exposed to the agent.”
  • Policy optimization: The adjustment of a policy’s parameters to improve its expected reward; “This evaluation provides a stringent test of whether the learning signals provided by synthesized environments capture general agentic capabilities rather than benchmark-specific behaviors.”
  • Persistent state: Information maintained across interactions rather than reset after each action; “The resulting world contains persistent state, multiple services and tools, and executable cross-service constraints that can be verified through interaction.”
  • PLANET role: The environment-authoring component that determines and constructs the world in which an agent operates; “We distinguish three roles: (1) a PLANET role that determines what world exists”
  • Recipe-conditioned generation: Generation performed with an additional construction procedure or example supplied in the prompt; “We evaluate five off-the-shelf models in two settings: zero-shot, where the model is given only the business brief, and recipe-conditioned”
  • Reinforcement learning: Machine learning in which a policy learns from rewards obtained through interaction with an environment; “We train policy models with reinforcement learning directly in environments synthesized by AGENTMERCURY”
  • Scenario-grounded world generation: Constructing executable environments from high-level scenarios rather than from individual tasks; “This motivates a shift from task-centric environment construction toward scenario-grounded world generation”
  • Seeded initial state: A reproducibly initialized environment state determined by a seed; “T is the executable transition function, O is the observation function, and s0 is the seeded initial state.”
  • Service graph: A structured representation of the services and their relationships within an executable world; “Let C denote the grounded company identity, G the service graph, and Σ the state schema.”
  • State schema: A formal specification of the structure and organization of an environment’s state data; “Let C denote the grounded company identity, G the service graph, and Σ the state schema.”
  • Structural validator: An executable check that tests whether a generated world satisfies required structural properties; “The generated worlds are evaluated using structural validators adapted from the AGENTMERCURY construction oracle.”
  • Task-centric paradigm: An approach that designs environments primarily around predefined tasks or benchmarks; “This task-centric paradigm has enabled researchers to efficiently build controlled environments for training and evaluating agents”
  • Task rubric: A specification of the assertions and conditions used to judge task completion; “The task rubric ρ is derived from the world-level structure together with the task-specific state changes.”
  • Tool-mediated decision making: Selecting actions through interactions with external software tools or services; “diverse executable worlds can expose policies to reusable patterns of interaction, state tracking, constraint satisfaction, and tool-mediated decision making”
  • Trajectory replay: Re-executing an interaction sequence to reproduce and reassess its outcome; “This property also enables trajectories to be replayed and deterministically re-evaluated after interaction.”
  • Transition dynamics: The rules governing how an environment changes after agent actions; “A world model provides a predictive representation of how an environment evolves in response to agent actions”
  • World model: A learned predictive representation of how an environment changes in response to actions; “A world model provides a predictive representation of how an environment evolves in response to agent actions”
  • Zero-shot authoring: Constructing an executable world without being given construction examples or additional procedural guidance; “Zero-shot provides only the business brief”

Open Problems

We haven't generated a list of open problems mentioned in this paper yet.

Tweets

Sign up for free to view the 2 tweets with 65 likes about this paper.