Add ADP-specific glossary terms for GA

modules/terms/partials/byoa.adoc

@@ -0,0 +1,4 @@
+=== BYOA (bring your own agent)
+:term-name: BYOA (bring your own agent)
+:hover-text: An agent built and run by you (in your own runtime, in any language) that registers with Redpanda for governance, observability, and gateway access. The runtime is yours; the policy and audit trail are Redpanda's.
+:category: Agentic Data Plane

modules/terms/partials/declarative-agent.adoc

@@ -0,0 +1,4 @@
+=== declarative agent
+:term-name: declarative agent
+:hover-text: An AI agent declared in YAML and run by Redpanda's managed runtime. The platform handles execution, model routing, and tool invocation. You describe the behavior, system prompt, and tool attachments.
+:category: Agentic Data Plane

modules/terms/partials/governance-dashboard.adoc

@@ -0,0 +1,4 @@
+=== governance dashboard
+:term-name: governance dashboard
+:hover-text: Cross-tenant overview UI showing spending, agent activity, MCP server inventory, and authorization events. The dashboard composes data from `SpendingService`, `AgentRegistryService`, and `MCPServerService`.
+:category: Agentic Data Plane

modules/terms/partials/oauth-client.adoc

@@ -0,0 +1,4 @@
+=== OAuth client
+:term-name: OAuth client
+:hover-text: An admin-registered external tool (such as Claude.ai, ChatGPT, or Cursor) authorized to request tokens from the in-dataplane OAuth authorization server. Distinct from an OAuth provider.
+:category: Agentic Data Plane

modules/terms/partials/oauth-connection.adoc

@@ -0,0 +1,4 @@
+=== OAuth connection
+:term-name: OAuth connection
+:hover-text: A per-user OAuth connection to a third-party provider, created by completing the consent flow. Connections store the user's access and refresh tokens in the token vault and are used by agents on behalf of that user.
+:category: Agentic Data Plane

modules/terms/partials/oauth-provider.adoc

@@ -0,0 +1,4 @@
+=== OAuth provider
+:term-name: OAuth provider
+:hover-text: An admin-registered upstream OAuth identity (such as Slack, Workday, or a custom IdP) that ADP users can connect to by completing the consent flow. Distinct from an OAuth client.
+:category: Agentic Data Plane

modules/terms/partials/resource.adoc

@@ -0,0 +1,4 @@
+=== resource
+:term-name: resource
+:hover-text: Read-only data exposed by an MCP server that an agent can fetch by URI. Resources surface things like file contents, database rows, or API responses without performing side effects.
+:category: Agentic Data Plane

modules/terms/partials/spending-event.adoc

@@ -0,0 +1,4 @@
+=== spending event
+:term-name: spending event
+:hover-text: A per-LLM-request cost record produced by the AI Gateway, carrying input, output, cached, and cache-write token counts plus tenant, provider, model, organization, and user identifiers. Cost is calculated downstream. The event itself carries raw token counts.
+:category: Agentic Data Plane

modules/terms/partials/token-vault.adoc

@@ -0,0 +1,4 @@
+=== token vault
+:term-name: token vault
+:hover-text: Encrypted store for per-user OAuth tokens used to access third-party providers. Supports admin-level connection revocation and data-encryption-key rotation.
+:category: Agentic Data Plane

modules/terms/partials/tool.adoc

@@ -0,0 +1,4 @@
+=== tool
+:term-name: tool
+:hover-text: A capability exposed by an MCP server that an AI agent can discover at runtime and invoke through structured JSON-RPC calls. Tools encapsulate operations such as querying a database, calling an API, or sending a message.
+:category: Agentic Data Plane