Apodex 1.1: Scaling Agentic Intelligence for Complex Work
Abstract: General-purpose LLMs can reason and synthesize knowledge, but complex work also requires sustained interaction with files, information sources, and executable code, together with state maintenance, failure recovery, and verifiable delivery. We call this \emph{working capability}: sustained, verifiable progress toward a real-world objective. Apodex 1.1 develops this capability along two complementary dimensions. \emph{Environment Scaling} expands the diversity and verifiability of executable file, search, and code environments, while \emph{Agentic Coordination Scaling} trains agents to decompose long-horizon tasks, delegate parallel work, integrate asynchronous results, and replan. A shared execution harness and AgentOS maintain task state and provenance across tools and agents, and training turns environment trajectories and coordination traces into reliable behavior. Across complex professional work, finance, scientific research, mathematics, coding, and search, Apodex 1.1 reaches the leading performance band despite using a substantially smaller model than many frontier systems. The 35B-parameter Apodex 1.1 Mini further retains strong working capability in a locally deployable form. These results ground agentic intelligence in useful, verifiable work completed over time and advance our goal of building a \emph{Heavy-Duty Solver} for ambitious, long-running tasks.
Paper Prompts
Sign up for free to create and run prompts on this paper.
Top Community Prompts
Explain it Like I'm 14
1. Paper overview
This paper introduces Apodex 1.1, an artificial intelligence system designed to complete difficult, long-lasting tasks—not just answer a single question.
Many AI models can explain ideas or solve small problems. However, real work often requires many connected steps. For example, an AI might need to:
- search for information,
- read several files,
- write and test computer code,
- remember what it has already done,
- fix mistakes,
- work on several parts of a task at once, and
- produce a final result that can be checked.
The paper calls this ability working capability. Apodex 1.1 is designed to improve this ability by giving AI better working environments and teaching multiple AI agents to coordinate their efforts.
2. Main objectives and research questions
The researchers are mainly asking:
How can an AI system become better at completing complicated real-world work over many steps?
They focus on several related questions:
- How can AI use tools reliably? Can it work with files, internet searches, and computer programs instead of only writing text?
- How can AI remember and manage progress? Can it keep track of files, evidence, plans, and unfinished work during a long task?
- How can AI recover from mistakes? If a program fails or new information changes the situation, can the AI fix its plan without throwing away useful work?
- Can several AI agents work together effectively? Can one main agent divide a task into smaller pieces, send them to helper agents, and combine their results?
- Can the final work be checked? Can the system show where its information came from and prove that its answer or files are correct?
The larger goal is to create what the paper calls a “Heavy-Duty Solver”: an AI that can take responsibility for ambitious tasks that last a long time.
3. Research methods and approach
The paper describes a complete AI system rather than one simple experiment. Its approach has two major parts.
Environment Scaling
Environment Scaling means creating many different computer-based situations in which the AI can practice useful work.
An environment is like a practice world or school laboratory. It gives the AI:
- a starting situation,
- tools it can use,
- rules about what its actions do,
- limited time or computer resources, and
- tests that check whether the job was completed correctly.
The paper focuses on three kinds of environments.
File environments
These contain documents, spreadsheets, images, folders, and earlier versions of files. The AI must figure out which information is reliable and use it to create a useful final document.
This is similar to receiving a messy desk full of papers and being asked to prepare an accurate report. The AI must find the newest and most trustworthy papers rather than simply using the first document it sees.
Search environments
These test whether the AI can research a topic. It must:
- create useful search queries,
- find reliable sources,
- compare information from different sources,
- connect claims to evidence, and
- admit when sources disagree or the evidence is uncertain.
This is like writing a school research project where every important statement needs support from trustworthy sources.
Code environments
These place the AI inside a computer programming project. The AI changes code, runs it, examines errors, and checks whether tests pass.
This is similar to repairing a machine while having a set of tests that show whether the repair worked. The AI must not only write code that looks reasonable; it must run successfully.
Agentic Coordination Scaling
The second major idea is Agentic Coordination Scaling. This means improving how several AI agents organize their work.
A lead agent first studies the overall problem and creates a task board. The board lists:
- smaller tasks,
- which tasks depend on others,
- which agents are working on them,
- completed results, and
- problems that still need attention.
Helper agents can then work on different parts at the same time. For example, one might search for scientific evidence, another might analyze a spreadsheet, and another might check the first agent’s claims.
When a helper agent finishes, the lead agent adds the result to the shared task board. It can then change the plan, start new tasks, or stop tasks that are no longer useful.
This is like a group project with a shared online checklist. Team members work independently, but everyone can see the current progress and update the plan.
Persistent execution and verification
Apodex uses a shared software system called AgentOS. It acts like a long-term workspace that remembers:
- files and their changes,
- search results,
- computer code and its outputs,
- which agent created each result,
- links between pieces of evidence, and
- the current task plan.
The system also records the history of actions. This history is called a trajectory or execution trace. It allows researchers to replay what happened and determine whether a failure was caused by the AI, the computer environment, or a faulty test.
The system uses verifiers, which are checks for completed work. These might include:
- running code tests,
- recalculating numbers,
- checking whether sources support claims,
- examining file contents, or
- asking a human expert to review the result.
A special idea in the paper is asymmetric verification. Instead of asking a checker AI to repeat the entire task, the checker receives a specific claim and its evidence. It then tries to find a mistake or counterexample. This is similar to asking a student, “Is this particular calculation correct?” rather than asking them to redo an entire book report from the beginning.
Training process
The researchers use two main types of training:
- Supervised fine-tuning (SFT): the AI studies examples of good behavior, such as using tools correctly or organizing a task.
- Agentic reinforcement learning (RL): the AI tries tasks in environments and receives feedback based on whether it makes useful progress and completes the job.
The researchers also study failures from real tasks and benchmarks. They turn common failures into new practice tasks, creating a repeating improvement cycle:
- observe where the AI fails,
- create tasks that practice those weaknesses,
- train the AI,
- test it again, and
- use the new failures to guide the next round.
4. Main findings and why they matter
According to the paper, Apodex 1.1 performs in the leading performance group across several areas, including:
- professional and office work,
- finance,
- scientific research,
- mathematics,
- coding,
- general reasoning, and
- online search.
The paper also reports that Apodex reaches this level while using a smaller model than many other leading AI systems. This suggests that better training environments, memory, verification, and coordination may sometimes matter as much as simply making a model larger.
A smaller version, called Apodex 1.1 Mini, has 35 billion parameters. Parameters are the internal values an AI learns during training. They are somewhat like the adjustable connections in the AI’s “brain.” The Mini model is intended to be powerful enough for local deployment, meaning it may be possible to run it on an organization’s own computers rather than always using a large internet-based system.
The paper’s important message is that AI quality should not be judged only by whether it gives a good-looking answer. A better test is whether it can:
- complete the requested work,
- create usable files or other results,
- use reliable evidence,
- recover from errors,
- keep track of its progress, and
- explain or prove how it reached the result.
5. Implications and potential impact
If the results hold up under independent testing, Apodex 1.1 could make AI more useful for tasks that are too complicated for a single question-and-answer exchange.
Possible applications include:
- preparing professional reports,
- analyzing scientific data,
- researching financial questions,
- modifying and testing software,
- organizing large collections of documents, and
- supporting complicated investigations.
The use of several cooperating agents could also allow work to happen faster. While one agent researches, another could analyze data and a third could check the results.
However, the system also creates challenges. More agents and more tools can lead to more mistakes if their work is not carefully monitored. The system must therefore keep accurate records, protect important files, check evidence, and prevent agents from claiming success when they have not really completed the task.
In simple terms, the paper argues that the future of AI is not only about making models better at thinking. It is also about making them better at working: planning, using tools, cooperating, correcting mistakes, and delivering results that people can trust.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
- The paper does not provide a complete technical specification of the Apodex 1.1 model, including architecture, tokenizer, context length, training compute, data volume, parameter counts beyond the 35B Mini model, or inference configuration.
- The training mixture is described conceptually, but its composition, provenance, filtering criteria, contamination controls, and proportions across SFT, agentic RL, environment trajectories, and coordination traces are not reported.
- The paper does not quantify the contribution of Environment Scaling separately from model scaling, inference-time compute, tool access, or ordinary additional training data.
- The claimed benefits of Agentic Coordination Scaling are not isolated through controlled ablations varying the number of agents, delegation policy, asynchronous execution, replanning, shared state, and verification while holding total compute constant.
- There is no systematic comparison between Agent Team and simpler inference-time baselines such as independent parallel sampling, majority voting, sequential self-refinement, fixed-role multi-agent systems, or a single agent with an equivalent token and tool budget.
- The paper does not define how “useful work,” “working capability,” “leading performance band,” or “Heavy-Duty Solver” are operationalized across tasks, making the headline claims difficult to reproduce or falsify.
- The formal task contract introduces delivery verifiers, but the paper does not report the proportion of tasks with executable verifiers, human judgments, model-based reviews, or mixed evaluation procedures.
- The reliability, validity, and inter-rater agreement of human review components are not quantified, particularly for professional work, scientific research, provenance fidelity, and artifact quality.
- The paper does not establish that the proposed verifiers are independent of the generators, reference solutions, or training data strongly enough to rule out shared systematic errors and benchmark overfitting.
- The effectiveness of verifier hardening and blind solver probes is asserted but not measured through documented attack rates, false-positive rates, false-negative rates, or before-and-after verifier audits.
- Search-world evaluation does not resolve how source quality, web availability, paywalls, regional variation, page updates, and retrieval-index differences affect reproducibility.
- The paper does not report whether search agents can distinguish authoritative sources from SEO-optimized, duplicated, adversarial, or AI-generated content under realistic web conditions.
- The proposed claim-to-evidence alignment protocol remains underspecified: the paper does not define acceptable semantic entailment thresholds, treatment of contradictory sources, or procedures for evaluating uncertainty and citation completeness.
- File-world coverage statistics—33 domains, 318 occupations, and 1,208 deliverable clusters—are not accompanied by task counts, sampling distributions, quality audits, or evidence that the generated tasks represent real professional workflows.
- The paper does not test whether models trained on synthetic file worlds generalize to unseen organizations, document conventions, file formats, languages, or genuinely collected workplace artifacts.
- Code-world results do not establish robustness to hidden tests, dependency conflicts, network restrictions, flaky tests, non-deterministic execution, security vulnerabilities, or repositories substantially different from the training distribution.
- The paper does not quantify reward-hacking incidence in code, file, or search environments after the stated verifier defenses are applied.
- The treatment of stochastic environments and replay does not clarify how nondeterministic tool outputs, external web changes, hardware variation, and timing-dependent failures are reproduced in practice.
- AgentOS and the execution harness are described at a systems level, but their implementation details, overhead, failure modes, throughput, scheduling policy, and resource-isolation guarantees are not reported.
- The paper does not provide a quantitative accounting of wall-clock latency, token consumption, tool calls, energy use, and monetary cost for ReAct and Agent Team executions.
- It remains unclear whether Agent Team’s performance gains persist when systems are compared at equal total compute, equal latency, equal monetary cost, or equal number of environment interactions.
- The adaptive Max Team Effort mechanism is not formally specified, and its stopping criteria, resource-allocation policy, and sensitivity to budget changes are not evaluated.
- The paper does not analyze how coordination quality changes with team size, task-branch dependence, delayed results, failed subagents, duplicated work, or conflicting intermediate conclusions.
- The task-board representation is proposed as a coordination mechanism, but there is no ablation showing whether explicit boards improve outcomes over hidden planning, natural-language scratchpads, structured workflow graphs, or external project-management representations.
- The paper does not measure the frequency with which task-board state becomes stale, inconsistent, incorrectly updated, or misleading to the lead agent and subagents.
- Asynchronous human intervention is described extensively, but the evaluation lacks quantitative results for intervention timing, intervention frequency, user burden, clarification quality, and preservation of valid prior work.
- The distinction between task-preserving interventions and new task contracts may be difficult to apply in ambiguous cases; the paper does not specify or evaluate adjudication rules for borderline objective or acceptance changes.
- The impact of user interventions on active subagents is not clarified, including how cancellation, notification latency, already-completed work, and inconsistent local states are handled.
- The paper does not investigate adversarial or malicious user interventions, including attempts to corrupt provenance, bypass verification, introduce unsafe instructions, or redirect agents toward unauthorized actions.
- The paper claims that narrow, asymmetric verification reduces context anchoring, but provides no controlled evidence comparing asymmetric verification with full-context review, independent end-to-end replication, or no verification.
- The reliability of verifier agents under correlated model errors, misleading evidence, adversarial claims, and technically correct but incomplete artifacts remains unresolved.
- The paper does not establish how provenance is represented, persisted, and validated across transformations involving derived files, copied content, code outputs, external sources, and multiple agents.
- It is unclear how the system handles irreversible actions, destructive file operations, privacy-sensitive information, confidential documents, or tools with real-world side effects.
- Safety, security, and privacy evaluations are largely absent, despite the system’s ability to search, execute code, modify files, delegate work, and maintain persistent state.
- The paper does not report performance across languages, cultural contexts, accessibility requirements, or domains in which professional conventions differ substantially from the presumed training distribution.
- Claims about the 35B Apodex 1.1 Mini being “locally deployable” are not supported with hardware requirements, throughput, memory usage, quantization effects, latency measurements, or capability degradation under constrained hardware.
- The paper does not show whether the Mini model retains long-horizon reliability, recovery behavior, provenance fidelity, and coordination quality—not merely answer accuracy—when deployed locally.
- Benchmark contamination and training-test overlap are not addressed for the reported finance, science, mathematics, coding, search, and professional-work evaluations.
- The evaluation framework does not report confidence intervals, statistical significance, variance across random seeds, or the number of independent tasks and runs, limiting assessment of result stability.
- The paper does not provide enough benchmark details, prompts, task contracts, environment manifests, trajectories, or verifier implementations to independently reproduce the reported results.
- The relationship between benchmark performance and real-world productivity is not validated through longitudinal user studies, expert workflow comparisons, or measurements of downstream artifact adoption and correction effort.
- The capability-development loop assumes that failures can be reliably classified into capability gaps, but the paper does not evaluate the accuracy, bias, or stability of this failure-attribution process.
- The proposed acquisition-pressure coordinate is explicitly non-universal, but its predictive validity, calibration across domains, and relationship to actual success probability are not empirically established.
- The paper does not determine whether training on increasingly difficult executable environments improves broad generalization or instead produces narrow adaptation to the specific environment families and verifier structures.
- The long-term effects of continual task-pipeline updates are unresolved, including catastrophic forgetting, capability interference, distribution drift, and feedback loops that over-prioritize easily measurable failures.
- The paper does not compare the environmental and coordination approaches with non-agentic alternatives such as improved retrieval systems, workflow automation, domain-specific software, or human–AI collaboration at equivalent cost.
- The manuscript appears incomplete: the provided text ends during the description of asymmetric verification, so the full evaluation methodology, results, limitations, and possibly safety analysis cannot be assessed from the supplied content.
Practical Applications
Immediate Applications
- Long-horizon professional document production — legal, consulting, finance, and operations
- Deploy Apodex-style agents to inspect heterogeneous workspaces, identify authoritative files, reconcile versions, perform calculations, and produce reports, spreadsheets, or presentations with source and artifact provenance.
- A practical workflow would combine
Fileenvironments, persistent workspace state, code-based calculations, and final contract checks for completeness and formatting. - Feasibility assumptions: Documents must be accessible in supported formats; organizational permissions and confidentiality controls must be in place; human review remains necessary for regulated or high-consequence deliverables.
- Evidence-grounded research assistance — academia, intelligence, and policy analysis
- Use the system to formulate search queries, triage candidate sources, follow references, reconcile conflicting evidence, and map individual claims to supporting sources.
- Potential products include literature-review assistants, policy-brief generators, research dashboards, and citation-audit tools that expose source provenance and uncertainty rather than returning unsupported prose.
- Dependencies: Reliable search and retrieval access, source-quality policies, protection against fabricated or inaccessible citations, and expert validation of contested interpretations.
- Repository maintenance and software engineering
- Apply the
Codeenvironment to issue resolution, test-driven patch generation, dependency inspection, debugging, refactoring, and regression testing. - An agent could operate in a sandboxed repository, execute tests, recover from failures, preserve state across attempts, and deliver a patch together with test results and an artifact lineage.
- Dependencies: Isolated execution, trusted test suites, version-control integration, secrets management, and explicit limits on production changes. Passing tests alone may not establish security, maintainability, or correctness.
- Apply the
- Automated quality assurance and verification
- Use asymmetric verification agents to inspect specific consequential claims, calculations, code outputs, or deliverable clauses instead of asking a second agent to reproduce an entire solution.
- This could support automated fact-checking, spreadsheet auditing, claim-to-source alignment, test review, and pre-publication quality gates.
- Assumptions: Verification inputs must be sufficiently independent from the generator’s context; verifiers require access to authoritative evidence; human escalation is needed when automated checks disagree.
- Internal knowledge-work automation
- Organizations can build agents that manage multi-step workflows such as preparing meeting packs, comparing contracts, consolidating departmental updates, analyzing operational spreadsheets, or assembling due-diligence materials.
- The task-board abstraction provides inspectable objectives, dependencies, assigned branches, completed work, and pending actions, making it more suitable for supervised enterprise workflows than an answer-only chatbot.
- Dependencies: Integration with document repositories, databases, calendars, and communication systems; role-based access control; audit logging; and clear delivery contracts.
- Interactive human-in-the-loop assistance
- Users can clarify requirements, add files, change priorities, ask for progress, pause execution, or cancel branches while work is underway.
- This supports workflows in which requirements emerge during execution—for example, revising a research question after reading an initial source or changing a report’s audience near completion.
- Feasibility assumptions: The runtime must correctly distinguish a clarification from a material change in objective or acceptance criteria, preserve unaffected work, invalidate dependent work, and record interventions for auditability.
- Locally deployed agentic assistance using the 35B Mini model
- The reported local-deployment form could support organizations that cannot send sensitive documents to external APIs, including smaller firms, laboratories, universities, and public agencies.
- Possible tools include an on-premise research assistant, private repository agent, local data-analysis assistant, or offline document-processing workflow.
- Dependencies: Adequate local hardware, acceptable latency, secure sandboxing, model licensing, and independent evaluation on the organization’s own tasks. The paper’s performance claims do not by themselves establish reliability for every local deployment.
- Agent-development infrastructure and evaluation
- The execution harness, AgentOS, immutable world manifests, fresh sandboxes, replay records, verifier isolation, and task boards can be used immediately as infrastructure for building and testing other tool-using agents.
- Research and engineering teams could create reproducible evaluations that measure not only answer correctness but also artifact completeness, provenance, recovery, intervention handling, time, and compute.
- Dependencies: Task-specific verifiers must be trustworthy and resistant to reward hacking; tool versions, seeds, and environment states must be captured; privacy controls are required when replaying real user tasks.
- Education and research training
- Universities can use the framework to create practical assignments in which students or research assistants must gather evidence, manipulate files, execute analyses, document provenance, and submit verifiable artifacts.
- Instructors could evaluate process quality—such as source alignment, reproducibility, and recovery from errors—in addition to final answers.
- Assumptions: Educational deployments need transparent grading criteria, safeguards against outsourcing learning entirely to agents, and interfaces that reveal operational records without exposing sensitive internal reasoning.
- Daily-life planning and administration
- A constrained personal assistant could organize files, compare bills or insurance documents, prepare travel plans from multiple sources, maintain household spreadsheets, or track long-running application processes.
- Persistent state and intervention handling are particularly relevant when a user adds new documents or changes constraints during execution.
- Dependencies: Strong privacy protection, explicit user confirmation before external actions, safe handling of financial and identity information, and conservative behavior when sources conflict.
Long-Term Applications
- Semi-autonomous scientific research systems
- A mature system could coordinate literature discovery, experimental-data cleaning, code execution, hypothesis comparison, statistical analysis, and report generation across multiple research branches.
- Agent Team’s decomposition, asynchronous result integration, replanning, and claim-level verification could form the basis of laboratory or computational research copilots.
- Further development required: Domain-specific scientific verifiers, integration with laboratory instruments and databases, uncertainty calibration, reproducibility standards, and safeguards against invalid inference or unsupported novelty claims.
- Financial analysis and investment research
- Future systems could monitor filings and market data, reconcile financial statements, build models, test assumptions, and generate auditable research notes or risk analyses.
- The paper’s emphasis on provenance, executable calculations, and recovery is well suited to workflows where a result must be traceable to data and assumptions.
- Dependencies: Licensed and current data feeds, robust numerical validation, compliance with securities and fiduciary regulations, explainable decision records, and strict separation between analysis and unauthorized trading or advice.
- Policy simulation and public-sector decision support
- Government agencies could use coordinated agents to compare policy evidence, model implementation scenarios, identify conflicting assumptions, and prepare briefings with claim-level citations.
- Persistent task state would allow analysts to incorporate new evidence or revised priorities without discarding valid prior work.
- Further research required: Bias and representativeness audits, transparent provenance standards, stakeholder review, legal accountability, and methods for handling politically or scientifically contested evidence.
- Autonomous software maintenance at organizational scale
- Long-term systems could continuously triage issues, propose and test patches, update dependencies, migrate legacy code, and coordinate specialized agents across large repositories.
- A shared task board could connect issue decomposition, implementation, security review, integration testing, and release preparation.
- Dependencies: Stronger security verifiers, formal or property-based testing, safe rollback, human approval gates, supply-chain controls, and reliable understanding of undocumented system behavior.
- Robotics and embodied automation
- The task-contract and persistent-state framework could eventually support robots that coordinate perception, planning, tool use, manipulation, recovery, and human intervention over extended tasks.
- Examples include warehouse operations, laboratory automation, inspection, maintenance, and multi-robot search.
- Further development required: Real-time control, multimodal perception, physical-world safety guarantees, robust handling of stochastic transitions, latency-aware coordination, and sim-to-real validation. The paper itself primarily demonstrates file, search, and code environments, not physical robotics.
- Industrial operations and engineering workflows
- Future agents could coordinate maintenance records, sensor data, engineering drawings, simulations, work orders, and compliance documentation to diagnose failures or plan interventions.
- Environment scaling could provide realistic digital twins or sandboxed operational environments, while provenance checks could link recommendations to measurements and calculations.
- Dependencies: High-fidelity simulations, safe interfaces to operational technology, certification, cybersecurity, domain-expert oversight, and clear responsibility when recommendations affect physical assets.
- Healthcare research and administrative support
- Potential applications include literature synthesis, clinical-trial documentation, population-health analysis, medical coding support, and preparation of evidence summaries for clinicians or researchers.
- Claim-level verification and explicit uncertainty could reduce—but not eliminate—the risk of unsupported medical statements.
- Further development required: Validated clinical datasets, privacy-preserving deployment, medical-device and healthcare regulation compliance, prospective clinical evaluation, bias assessment, and mandatory professional sign-off. The findings do not justify autonomous diagnosis or treatment.
- Energy-system planning and grid operations
- A future agent team could combine weather forecasts, demand data, asset records, simulations, and regulatory constraints to evaluate maintenance or dispatch scenarios.
- Code-based verification and persistent provenance could make scenario analyses more reproducible and auditable.
- Dependencies: Real-time data quality, validated physical models, secure operational interfaces, reliability guarantees, and human control for decisions affecting grid stability.
- Multi-agent organizational operating systems
- AgentOS could evolve into a general runtime for delegating work among specialized agents, tracking dependencies, managing budgets, recording provenance, and routing human interventions.
- Possible products include enterprise “work operating systems” for research, engineering, compliance, and project management rather than isolated conversational assistants.
- Further development required: Standardized agent protocols, resource scheduling, identity and permission systems, cross-agent conflict resolution, cost control, observability, and benchmarks that measure useful coordinated work rather than the number of agent interactions.
- Trustworthy autonomous knowledge work
- The paper’s longer-term “Heavy-Duty Solver” vision could lead to systems entrusted with complete, long-running objectives: gathering evidence, executing analyses, producing artifacts, responding to changing requirements, and demonstrating why the result should be accepted.
- This would represent a shift from chat-based assistance to verifiable delegation of complex work.
- Major dependencies: Demonstrated reliability outside curated environments, robust generalization to unfamiliar tools and domains, calibrated uncertainty, secure autonomy, reproducible evaluation, legal accountability, and mechanisms to prevent plausible but incorrect completion from being mistaken for successful work.
Glossary
- Acquisition pressure: A measure of how much candidate inspection and evidence navigation is required relative to the available tool-call budget. “as a first-order acquisition-pressure coordinate”
- Agentic Coordination Scaling: Increasing an agent system’s ability to organize work across agents, branches, and time. “The second is Agentic Coordination Scaling”
- Agentic RL: Reinforcement learning designed to improve decisions made by agents during extended, interactive tasks. “Agentic RL then improves long-horizon decisions”
- AgentOS: A persistent runtime system that maintains state and supports tool, artifact, and agent execution. “AgentOS provides the persistent runtime beneath the harness”
- Artifact lineage: The traceable chain connecting an artifact to the files, evidence, computations, and transformations that produced it. “Statement Review then checks consequential claims against sources, computations, and artifact lineage.”
- Asynchronous intervention: User input or external interaction introduced while an agent is already executing a task. “Apodex 1.1 instead accepts a user message during execution”
- Asymmetric verification: Verification in which a reviewer evaluates a narrowly specified claim or condition rather than reproducing the entire solution. “Apodex 1.1 constructs verification asymmetry: verification is deliberately narrower than generation.”
- Authoritative state: The canonical, trusted version of the current workspace or task information. “preserving authoritative state across tools and agents”
- Benchmark error: A failure or defect identified through evaluation tasks that can guide subsequent system development. “Real tasks, benchmark errors, and runtime failures are classified into capability gaps”
- Branch state: The execution and dependency status of one line of work within a larger coordinated task. “maintains workspace, artifact, provenance, and branch state”
- Capability gap: A deficiency in a model’s or agent system’s ability to perform a particular class of tasks. “Task Pipeline converts those gaps into new tasks”
- Causal continuity: Preservation of valid relationships between earlier work, later decisions, and the evolving task state. “Training across these cases teaches the main agent to preserve causal continuity”
- Claim-to-evidence alignment: The explicit association between a factual claim and the source material supporting it. “it includes the relevant source set, claim-to-evidence alignment”
- Completion contract: A formal specification of what must be delivered and the criteria used to determine whether a task is complete. “defines observations and completion contracts”
- Coordination trace: A recorded sequence of decisions and interactions among agents while organizing and executing work. “Agentic RL then improves long-horizon decisions over executable environment trajectories and coordination traces.”
- Delivery contract: A task specification defining required outputs, constraints, and acceptance conditions. “the delivery contract states what must be delivered”
- Dependency depth: The length or complexity of dependency chains that must be handled in a code environment. “including dependency depth, state-transition depth, test observability”
- Exogenous state: Environmental state originating outside the agent’s chosen actions, such as controlled randomness or external conditions. “preserve the exogenous state, tool versions, and random seeds”
- Executable environment: An interactive computational setting in which actions change state and produce machine-observable results. “An executable environment determines what states the model can observe”
- Executable trajectory: A recorded sequence of actions, observations, and state changes produced through interaction with a runnable environment. “Diverse, faithful, and verifiable file, search, and code worlds expand the distribution of executable trajectories”
- Evidence synthesis: The process of combining information from multiple sources into a supported conclusion. “Search environments model open-web research as discovery, acquisition, and evidence synthesis.”
- Failure recovery: The ability to respond to unsuccessful actions while preserving valid prior progress. “recovering from failed actions”
- Fidelity: The degree to which a simulated environment accurately represents the relevant structure and behavior of real-world tools or workflows. “Diversity without fidelity teaches behavior that fails in real tools”
- Grader: An automated evaluator that determines whether a task solution satisfies specified requirements. “disagreements between a faithful solution and the grader”
- Harness: A software layer that connects a model to environments, tools, state management, replay, and verification mechanisms. “The harness binds the model to File, Search, and Code environments”
- Heavy-Duty Solver: The paper’s term for a system capable of undertaking ambitious, extended, and verifiable real-world tasks. “our goal of building a Heavy-Duty Solver”
- Immutable world manifest: A fixed record describing the initial configuration and versions of an executable environment. “Each rollout receives an immutable world manifest”
- Inference scaling: Increasing the computational effort devoted to solving an individual task at runtime. “inference scaling increases the computation spent on one task”
- Interactive agent evaluation: Assessment of an agent through actions and responses within an evolving environment rather than through a single answer. “interactive agent evaluation has exposed this gap”
- Long-horizon task: A task requiring many dependent actions, decisions, or interactions over an extended execution period. “The limiting capability is therefore not reasoning in isolation, but the ability to turn reasoning into sustained work inside a changing environment.”
- Max Team Effort: A runtime mechanism for adapting the amount of parallel work performed by an agent team. “adaptive Max Team Effort”
- Multi-agent coordination: Organization of work among multiple autonomous or semi-autonomous agents. “multi-agent coordination within one policy”
- No-op transition: A state transition that performs no substantive modification, often used for read-only interaction. “A no-op transition permits read-only actions.”
- Observation interface: The mechanism through which an agent receives information about the environment after taking an action. “ is the observation interface”
- Open-web research: Research conducted over publicly accessible, heterogeneous online sources. “Search environments model open-web research as discovery, acquisition, and evidence synthesis.”
- Provenance: A record of the origin, history, and transformations of data or artifacts. “maintains workspace, artifact, provenance, and branch state”
- ReAct: An agentic prompting or execution paradigm that interleaves reasoning with actions and observations. “ReAct provides a lower-scaffold view of the model's working capability”
- Replay: Re-execution of a recorded task using preserved environment and tool information to check reproducibility. “A trajectory is retained only when its initial state can be reconstructed, tool execution is isolated, and the verifier can be replayed.”
- Replanning: Revising an existing task plan in response to new evidence, failures, or changed conditions. “delegate parallel work, integrate asynchronous results, and replan”
- Reward hacking: Obtaining a high evaluation reward without genuinely completing the intended task. “We additionally test whether a solver can obtain reward without actually completing the task”
- Sandbox: An isolated execution environment that restricts a program or agent from affecting protected systems. “Each rollout receives an immutable world manifest and a fresh mutable sandbox.”
- Self-supervised tool-call learning: Learning to invoke tools from automatically derived training signals rather than manually annotated action labels. “Toolformer established self-supervised tool-call learning”
- State-transition operator: A formal function describing how an action changes the environment or workspace state. “ is the state-transition operator”
- Staged return: The practice of returning partial results from agents as soon as they become available, rather than waiting for all branches to finish. “staged returns, shared artifacts, lifecycle control, and verification hooks”
- Sticky routing: Assigning all interactions from one session to the same execution worker. “Sticky routing keeps a session on one worker.”
- Structured verdict: An evaluation result represented as organized checks or fields rather than a single unstructured judgment. “ may be a scalar score, a vector of checks, or a structured verdict.”
- Task contract: A formal representation of a task, including its workspace, objective, actions, transitions, observations, budgets, delivery requirements, and verifier. “We use one task contract throughout this report”
- Task Pipeline: A development process that converts observed capability deficiencies into new training or evaluation tasks. “Task Pipeline converts those gaps into new tasks”
- Test observability: The degree to which a task’s tests expose whether the intended behavior has been achieved. “Code worlds require different calibration coordinates, including dependency depth, state-transition depth, test observability”
- Trajectory: A time-ordered sequence of inputs, actions, observations, and state changes during task execution. “Let denote the realized trajectory horizon”
- Trajectory horizon: The number of interaction steps or time points comprising an execution trajectory. “Let denote the realized trajectory horizon”
- Typed observation: An environment response represented according to a defined semantic or data type, such as a tool result, failure, or status update. “the harness and AgentOS connect both dimensions through persistent execution state, typed observations”
- Verifier hardening: Strengthening an evaluator so that it is resistant to incorrect solutions, exploits, or inconsistent test conditions. “As these transformations can invalidate an existing grader, verifier hardening precedes task perturbation”
- Working capability: The ability to make useful, sustained, recoverable, and verifiable progress toward a real-world objective. “We call this working capability: sustained, verifiable progress toward a real-world objective.”

