> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/gym/llms.txt.
> For full documentation content, see https://docs.nvidia.com/nemo/gym/llms-full.txt.

# Engineering Notes

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

<Cards>
  <Card title="System Design" href="/latest/infrastructure/engineering-notes/system-design">
    How NeMo Gym components interact during startup, execution, and rollout collection.

    <Badge minimal outlined>
      architecture
    </Badge>

    <Badge minimal outlined>
      server-infra
    </Badge>
  </Card>

  <Card title="Responses API Evolution" href="/latest/infrastructure/engineering-notes/responses-api-evolution">
    Why NeMo Gym uses the Responses API and how it differs from Chat Completions.

    <Badge minimal outlined>
      api-design
    </Badge>

    <Badge minimal outlined>
      schema
    </Badge>
  </Card>

  <Card title="SWE RL Infrastructure Case Study" href="/latest/infrastructure/engineering-notes/swe-rl-case-study">
    Infrastructure challenges and deployment topology for SWE RL training.

    <Badge minimal outlined>
      swe-rl
    </Badge>

    <Badge minimal outlined>
      case-study
    </Badge>
  </Card>

  <Card title="aiohttp vs httpx" href="/latest/infrastructure/engineering-notes/aiohttp-vs-httpx">
    Why NeMo Gym uses aiohttp instead of httpx for async HTTP.

    <Badge minimal outlined>
      server-infra
    </Badge>

    <Badge minimal outlined>
      performance
    </Badge>
  </Card>
</Cards>