Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions fern/versions/latest/pages/about/concepts/key-terminology.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,18 @@ Training data format for DPO consisting of the same prompt with two different re

The primary LLM being trained or evaluated - the "decision-making brain" you want to improve.

**Resources Server**

The FastAPI service (under `resources_servers/`) that holds per-task state, exposes the environment's tools, and implements `verify()` to score a rollout into a reward — the verifier-and-state component of an environment. (In Gym an *environment* is a resources server together with an agent and dataset(s); see the `environments/` directory.) Every environment has exactly one resources server.

**Agent Server (Responses API Agent)**

The FastAPI service (under `responses_api_agents/`) that drives the model through a task — the harness that runs the multi-step / tool-calling loop against a resources server. Gym ships several built-in harnesses (e.g. `simple_agent`, `aviary_agent`, and others under `responses_api_agents/`); pick whichever fits your control flow, or bring your own.

**Model Server (Responses API Model)**

The FastAPI service (under `responses_api_models/`) that wraps an LLM endpoint (vLLM, OpenAI, etc.) behind NeMo Gym's Responses API and manages the token IDs needed for training. Agents refer to it by name (commonly `policy_model`).

**Orchestration**

Coordination logic that manages when to call models, which tools to use, and how to sequence multi-step operations.
Expand Down
12 changes: 12 additions & 0 deletions fern/versions/v0.3.0/pages/about/concepts/key-terminology.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,18 @@ Training data format for DPO consisting of the same prompt with two different re

The primary LLM being trained or evaluated - the "decision-making brain" you want to improve.

**Resources Server**

The FastAPI service (under `resources_servers/`) that holds per-task state, exposes the environment's tools, and implements `verify()` to score a rollout into a reward — the verifier-and-state component of an environment. (In Gym an *environment* is a resources server together with an agent and dataset(s); see the `environments/` directory.) Every environment has exactly one resources server.

**Agent Server (Responses API Agent)**

The FastAPI service (under `responses_api_agents/`) that drives the model through a task — the harness that runs the multi-step / tool-calling loop against a resources server. Gym ships several built-in harnesses (e.g. `simple_agent`, `aviary_agent`, and others under `responses_api_agents/`); pick whichever fits your control flow, or bring your own.

**Model Server (Responses API Model)**

The FastAPI service (under `responses_api_models/`) that wraps an LLM endpoint (vLLM, OpenAI, etc.) behind NeMo Gym's Responses API and manages the token IDs needed for training. Agents refer to it by name (commonly `policy_model`).

**Orchestration**

Coordination logic that manages when to call models, which tools to use, and how to sequence multi-step operations.
Expand Down
Loading