> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/gym/v0.6.0/infrastructure/engineering-notes/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemo/gym/_mcp/server.

# Engineering Notes

Technical notes that document infrastructure decisions, performance investigations, and design rationale behind NeMo Gym.

#### [System Design](/infrastructure/engineering-notes/system-design)

How NeMo Gym components interact during startup, execution, and rollout collection.

architecture

server-infra

#### [Responses API Evolution](/infrastructure/engineering-notes/responses-api-evolution)

Why NeMo Gym uses the Responses API and how it differs from Chat Completions.

api-design

schema

#### [SWE RL Infrastructure Case Study](/infrastructure/engineering-notes/swe-rl-case-study)

Infrastructure challenges and deployment topology for SWE RL training.

swe-rl

case-study

#### [aiohttp vs httpx](/infrastructure/engineering-notes/aiohttp-vs-httpx)

Why NeMo Gym uses aiohttp instead of httpx for async HTTP.

server-infra

performance

## Docs

- [aiohttp vs httpx](https://docs.nvidia.com/nemo/gym/v0.6.0/infrastructure/engineering-notes/aiohttp-vs-httpx.md): 
- [Responses API](https://docs.nvidia.com/nemo/gym/v0.6.0/infrastructure/engineering-notes/responses-api-evolution.md): 
- [SWE RL Case Study](https://docs.nvidia.com/nemo/gym/v0.6.0/infrastructure/engineering-notes/swe-rl-case-study.md): 
- [System Design](https://docs.nvidia.com/nemo/gym/v0.6.0/infrastructure/engineering-notes/system-design.md):