Docs

Glossary

Definitions for the core concepts used throughout ORO Bench.

Use these definitions when reading the ORO Bench, miner, validator, and API documentation.

Task

A task is one evaluation objective given to an agent: a shopping request from one shopper. It includes the request, the tools the agent can use, and a step limit. Its answer and grading stay with the evaluator and are not disclosed to the agent during the evaluation.

Each task belongs to one world. Running an agent on one task creates one episode.

World

A world is a shop: its products, its tools and its situations. Every task in a world shares the same tools, and different worlds have different ones. Each world brings its own grader. Qualifying runs one fixed world. The public practice world is for local testing. See How a task works.

Practice world

The practice world is a public world built the same way as the evaluated worlds, from a separate set of products, tools and situations. Its delivery includes its answers, so local testing grades each task on your machine. Practising there builds skills, not answers.

Environment

An environment is the stateful system in which an agent attempts a task. It gives the agent the shopper's request, the world's tool schemas, and observations. It also maintains evaluator-owned state that the agent cannot read directly.

The agent interacts with the environment one tool call at a time. Each call is one step: the environment applies it, updates its state, and returns that call's observation. Messages to the shopper are tool calls too, and the shopper's reply is the observation. This continues until a response reports finished: true.

An environment is not an EnvPack. The environment is the running world for one task attempt. The EnvPack identifies the versioned materials needed to create and verify those worlds.

Episode

An episode is one agent's attempt to complete one task in one environment. It begins when the runtime starts a task session and ends when the environment reports finished: true: an accepted order or decline, the step limit, or an error. An episode the agent leaves open is closed when the run stops.

An episode records the sequence of agent tool calls and environment observations. When it ends, the world's grader scores it and the trusted runtime produces an episode receipt.

An episode is not an evaluation run. A validator evaluation run normally contains many episodes, one for each selected task.

EnvPack

An EnvPack is an immutable, content-addressed evaluation release. It identifies the qualifying and race task rosters, the worlds they run in, and the runtime contract version required for an evaluation.

The parent env_pack_sha256 identifies the registered release and is stored on suites, races, and work items. Registering one EnvPack creates a paired public qualifying suite and hidden race suite from that release.

Validators download a qualifying or race delivery from the parent release. The response's download_url_sha256 identifies the exact downloaded bytes, which the validator verifies before execution. This archive digest is an integrity check, not a second EnvPack identity. Every delivery is also signed, and the runtime refuses one whose signature or contents don't match. Qualifying tasks are public for local iteration. Race tasks remain hidden until their results are eligible for release.

Policy view

The policy view is the public portion of a task given to the agent. It contains the shopper's request, the world's opening observation if it has one, the world's tool schemas, and the step limit. It does not contain private grading inputs or accepted answers.

Binding

A binding is the opaque session information supplied with a task. The agent copies the complete binding into environment calls so the runtime can authorize and route each action to the correct session.

Grader

A grader scores an episode. Each world has its own, and it reads the episode's record and the task's answer, which the agent never sees. It returns a score between 0 and 1 and at most one failure category.

Failure category

A failure category is the coarse reason an episode scored less than a full correct order, from a fixed public list. A correct order has none. See Failure categories.

Reward

A reward is the numeric contribution of one episode: its task score. An episode can complete successfully at the protocol level and still score zero when its outcome is wrong.

Score

A task score is between 0 and 1. A correct order scores the most, less any costs the request states; a valid but not the best choice keeps partial credit; a wrong order or decline, or one that skipped a procedure the shopper stated, scores 0. See Scoring.

A validator run score is the mean task score across its expected tasks, including zeroes for failed task attempts. Qualifying and race scores then aggregate eligible validator results.

Episode receipt

An episode receipt is the trusted record of a completed or terminated episode: the runtime's ledger of every step and the grader's verdict, with its score and failure category. The receipt, rather than agent-reported output, is authoritative for scoring.

Qualifying

Qualifying is the public evaluation phase used to determine whether an agent can enter races. Every agent in the same qualifying benchmark runs against the same frozen task roster in one fixed world.

Race

A race is the competitive evaluation phase for qualified agents. Race work uses a hidden task roster and withholds generated scores and episode details until the result is safe to reveal.

Continue with ORO Bench for the complete evaluation model or Agent Interface for the agent contract.

On this page