NVIDIA · afourniernv · Aug 4, 2026 · Aug 4, 2026 · Aug 4, 2026 · Aug 4, 2026
@@ -1,7 +1,7 @@
 ---
 title: "Agent Runtime Primer"
 description: "Learn the NeMo Relay runtime model for scopes, middleware, events, and integration boundaries."
-position: 2
+position: 3
 ---
 import { MermaidStyles } from "@/components/MermaidStyles";
 

@@ -1,7 +1,7 @@
 ---
 title: "Architecture"
 description: ""
-position: 3
+position: 4
 ---
 import { MermaidStyles } from "@/components/MermaidStyles";
 

@@ -1,7 +1,7 @@
 ---
 title: "Codecs"
 description: ""
-position: 7
+position: 6
 ---
 {/* SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
 SPDX-License-Identifier: Apache-2.0 */}

@@ -1,7 +1,7 @@
 ---
 title: "Events"
 description: ""
-position: 4
+position: 2
 ---
 {/* SPDX-FileCopyrightText: Copyright (c) 2026, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
 SPDX-License-Identifier: Apache-2.0 */}

@@ -13,10 +13,10 @@ in a use-case workflow.
 NeMo Relay's shared runtime model has five parts:
 
 - **Scopes** decide where work belongs and which scope-local behavior is visible.
+- **Events** record what happened in the canonical lifecycle stream.
 - **Middleware** decides what can block, rewrite, sanitize, or wrap managed
   execution.
 - **Plugins** install reusable runtime behavior from configuration.
-- **Events** record what happened in the canonical lifecycle stream.
 - **Subscribers and exporters** consume that stream in process, write raw ATOF
   events, or project events into downstream formats.
 
@@ -38,7 +38,17 @@ runtime concept or integration boundary you need.
   href="/about-nemo-relay/concepts/scopes"
 >
 
-Ownership boundaries for agent runs, requests, workflows, tools, LLM calls, and nested runtime work.
+Scope hierarchy, lifetime, and isolation for agent runs, requests, tools, LLM calls, and nested work.
+</Card>
+
+<Card
+  title="Events"
+  icon="regular waveform-lines"
+  iconPosition="left"
+  href="/about-nemo-relay/concepts/events"
+>
+
+Canonical lifecycle records for scopes, tool calls, LLM calls, marks, subscribers, and exporters.
 </Card>
 
 <Card
@@ -61,16 +71,6 @@ Guardrails and intercepts that sanitize, transform, block, or wrap tool and LLM
 Configuration-driven bundles that install reusable middleware, subscribers, and adaptive behavior.
 </Card>
 
-<Card
-  title="Events"
-  icon="regular waveform-lines"
-  iconPosition="left"
-  href="/about-nemo-relay/concepts/events"
->
-
-Canonical lifecycle records for scopes, tool calls, LLM calls, marks, subscribers, and exporters.
-</Card>
-
 <Card
   title="Subscribers"
   icon="regular tower-broadcast"
@@ -82,23 +82,13 @@ Consumers for lifecycle events, including logs, traces, trajectories, analytics,
 </Card>
 
 <Card
-  title="Framework Integrations"
-  icon="regular diagram-project"
-  iconPosition="left"
-  href="/about-nemo-relay/concepts/framework-integrations"
->
-
-Integration patterns for frameworks that own invocation boundaries, scheduling, retries, or provider payloads.
-</Card>
-
-<Card
-  title="Codecs"
+  title="Provider Codecs"
   icon="regular arrows-rotate"
   iconPosition="left"
   href="/about-nemo-relay/concepts/codecs"
 >
 
-Normalization boundaries for typed application values, provider payloads, middleware, and exporters.
+Provider request and response normalization for middleware and observability.
 </Card>
 
 </CardGroup>
@@ -1,7 +1,7 @@
 ---
 title: "Middleware"
 description: ""
-position: 2
+position: 3
 ---
 import { MermaidStyles } from "@/components/MermaidStyles";
 

@@ -1,7 +1,7 @@
 ---
 title: "Plugins"
 description: "Understand NeMo Relay plugin configuration, lifecycle, ownership, and built-in components."
-position: 3
+position: 4
 ---
 import { MermaidStyles } from "@/components/MermaidStyles";
 

@@ -1,7 +1,7 @@
 ---
 title: "Ecosystem"
 description: "Understand how NeMo Relay fits with agent frameworks, providers, and the NVIDIA NeMo ecosystem."
-position: 4
+position: 2
 ---
 import { MermaidStyles } from "@/components/MermaidStyles";
 

@@ -25,7 +25,6 @@ These pages define or route the shared runtime model:
 - `docs/about-nemo-relay/concepts/subscribers.mdx`
 - `docs/about-nemo-relay/concepts/plugins.mdx`
 - `docs/about-nemo-relay/concepts/events.mdx`
-- `docs/about-nemo-relay/concepts/framework-integrations.mdx`
 - `docs/about-nemo-relay/concepts/codecs.mdx`
 - `docs/about-nemo-relay/agent-runtime-primer.mdx`
 - `docs/getting-started/about.mdx`

@@ -95,7 +95,7 @@ agent lifecycle hooks. If you are building or reviewing a framework integration
 that is not covered by a maintained guide, use the generic framework integration
 workflow instead.
 
-<CardGroup cols={3}>
+<CardGroup cols={2}>
 <Card
   title="Supported Integrations"
   icon="regular puzzle-piece"
@@ -115,18 +115,8 @@ LangGraph, Deep Agents, or OpenClaw.
 >
 
 Choose the generic workflow for unsupported frameworks, provider adapters, or
-new public-API integrations.
-</Card>
-
-<Card
-  title="Framework Integration Concepts"
-  icon="regular diagram-project"
-  iconPosition="left"
-  href="/about-nemo-relay/concepts/framework-integrations"
->
-
-Ensure you understand what the framework owns, what Relay owns, and which
-runtime semantics each integration boundary preserves.
+new public API integrations, including how to choose the Relay APIs that match
+the work your framework controls.
 </Card>
 
 </CardGroup>