Merge pull request #13 from redpanda-data/adp-3a-reference-shell

Audit ADP landing page and replace glossary stub for GA

Author: micheleRP

local-antora-playbook.yml

@@ -26,6 +26,7 @@ content:
 ui:
   bundle:
     url: https://github.com/redpanda-data/docs-ui/releases/download/v2.14.0-adp.2/ui-bundle.zip
+  supplemental_files: ./supplemental-ui
 asciidoc:
   attributes:
   extensions:

modules/ROOT/nav.adoc

@@ -1,9 +1,8 @@
 * xref:index.adoc[Overview]
 * xref:get-started:index.adoc[Get started]
-** xref:get-started:signup.adoc[Sign up for ADP Cloud]
+** xref:get-started:byoc-prereqs.adoc[Prerequisites]
+** xref:get-started:byoc-quickstart.adoc[Quickstart]
 ** xref:get-started:first-agent.adoc[Build your first agent]
-** xref:get-started:byoc-prereqs.adoc[ADP BYOC prerequisites]
-** xref:get-started:byoc-quickstart.adoc[ADP BYOC quickstart]
 ** xref:get-started:invite-team.adoc[Invite your team]
 * xref:agents:index.adoc[Agents]
 ** xref:agents:overview.adoc[Overview]

modules/ROOT/pages/index.adoc

@@ -56,13 +56,19 @@ For more information, see xref:observability:concepts.adoc[Transcripts Overview]
 
 The AI Gateway manages LLM provider access with two priorities: keeping your application up and keeping costs under control.
 
-For high availability, the gateway provides provider-agnostic routing with intelligent failover. Your users don't care which provider serves a request. They care that the application stays up. For fiscal control, you get per-tenant budgets and rate limiting, so there are no runaway costs and no surprise bills.
+For high availability, the gateway provides provider-agnostic routing with intelligent failover. Your users don't care which provider serves a request. They care that the application stays up. You can also route different tasks to different models, such as a frontier model for analysis and a smaller model for classification or triage, and see usage and cost across every model in one view. For fiscal control, you get per-tenant budgets and rate limiting, so there are no runaway costs and no surprise bills.
 
 The gateway also supports tenancy modeling for teams, individuals, applications, and service accounts, giving you chargeback transparency for internal cost allocation. You can proxy both models and MCP gateways, centralizing compliance for all LLM interactions without locking into any single provider.
 
 For more information, see xref:ai-gateway:overview.adoc[AI Gateway Overview].
 
-== Enterprise governance
+== Governance
+
+The glossterm:governance dashboard[] provides a cross-tenant view of agent activity, spending, MCP server inventory, and authorization events. It composes existing services into a single overview built for platform administrators and finance partners, surfacing per-provider spending, agent state, and the authorization decisions that gate every tool invocation.
+
+For more information, see xref:governance:dashboard/index.adoc[Governance Dashboard Overview].
+
+== Built-in governance controls
 
 Redpanda ADP addresses critical enterprise requirements across all components.
 
@@ -72,19 +78,22 @@ Redpanda ADP addresses critical enterprise requirements across all components.
 
 * *Complete observability*: Redpanda ADP provides two levels of inspection. Execution logs (transcripts) capture every agent action with 100% sampling using OpenTelemetry standards. Real-time debugging tools allow you to inspect individual MCP server calls down to individual tool invocations with full timing data. You can view detailed agent actions in glossterm:Redpanda Console[] and replay data for agent evaluations.
 
-* *Compliance and audit*: For industries requiring multi-year audit trails, Redpanda ADP records every agent action and data source used in decision-making. Execution logs are stored in Redpanda topics and can be materialized to Iceberg tables for long-term retention and analysis.
+* *Compliance and audit*: For regulated industries with frameworks such as ISO 42001 and the EU AI Act, Redpanda ADP records every agent action and data source used in decision-making. Execution logs are stored in Redpanda topics and can be materialized to Iceberg tables for multi-year retention and analysis.
 
 == Use cases
 
-Some ways organizations can leverage Redpanda ADP include:
+Common Redpanda ADP use cases include:
 
-* *Automate operational workflows*: Create specialized agents for building management, infrastructure monitoring, compliance reporting, and other domain-specific tasks.
-* *Monitor manufacturing and operations*: Deploy multi-agent systems that analyze factory machine telemetry in real-time, detect anomalies, search equipment manuals, and create maintenance tickets automatically.
+* *Automate financial operations*: Build agents that reconcile invoices across vendors and ERP systems, monitor real-time spending against budget, or review contracts against approved templates and flag out-of-policy clauses for legal review.
+* *Streamline HR and people operations*: Answer employee questions against benefits, payroll, and HRIS systems; automate onboarding and offboarding workflows; or triage internal support tickets to the right team.
+* *Improve customer experience*: Route customer inquiries to the right team, summarize prior support history before an agent picks up the case, or surface relevant knowledge-base articles in real time.
+* *Modernize infrastructure operations*: Detect anomalies in real-time telemetry from cloud, network, or factory equipment, correlate signals across disparate monitoring systems, and auto-create maintenance tickets with the relevant context already attached.
 * *Extend enterprise productivity tools*: Integrate Microsoft Copilot or other workplace agents with internal data sources and systems that are otherwise inaccessible.
 
 == Next steps
 
-* xref:agents:overview.adoc[AI Agents Overview]
-* xref:mcp:overview.adoc[MCP Server Overview]
-* xref:observability:concepts.adoc[Transcripts Overview]
-* xref:ai-gateway:overview.adoc[AI Gateway Overview]
+* xref:agents:overview.adoc[]
+* xref:mcp:overview.adoc[]
+* xref:ai-gateway:overview.adoc[]
+* xref:governance:dashboard/index.adoc[]
+* xref:observability:concepts.adoc[]

modules/ROOT/partials/availability-block.adoc

@@ -1,28 +1,9 @@
-// Availability indicator for ADP pages
-// Shows which platforms support this feature
+// Availability indicator for ADP pages.
+// ADP ships as a single deployment shape at GA (BYOC). The block
+// renders only when a page explicitly opts in with :page-byoc: true.
 ifdef::page-byoc[]
-ifndef::page-cloud-only[]
 [.availability-block]
 ****
 *Available in:* BYOC
 ****
 endif::[]
-endif::[]
-
-ifdef::page-cloud-only[]
-ifndef::page-byoc[]
-[.availability-block]
-****
-*Available in:* Cloud
-****
-endif::[]
-endif::[]
-
-ifndef::page-byoc[]
-ifndef::page-cloud-only[]
-[.availability-block]
-****
-*Available in:* Cloud, BYOC
-****
-endif::[]
-endif::[]

modules/agents/pages/quickstart.adoc

@@ -17,7 +17,7 @@ After completing this quickstart, you will be able to:
 
 == Prerequisites
 
-* An ADP BYOC environment (agents are not available on ADP Cloud yet)
+* An ADP environment
 
 * xref:ai-gateway:gateway-quickstart.adoc[AI Gateway configured] with at least one LLM provider enabled (OpenAI, Anthropic, or Google AI)
 

modules/get-started/pages/index.adoc

@@ -1,3 +1,3 @@
 = Get started
-:description: Sign up for ADP Cloud, build your first agent, or set up your own ADP BYOC environment.
+:description: Set up your ADP environment, build your first agent, and invite your team.
 :page-layout: index

modules/get-started/pages/signup.adoc

@@ -51,22 +51,22 @@ Redpanda offers two kinds of MCP server backends:
 
 The Agentic Data Plane UI has four top-level areas:
 
-* *LLM Providers* — OpenAI, Anthropic, Bedrock, Gemini, OpenAI-compatible endpoints. See xref:ai-gateway:configure-provider.adoc[Configure your LLM provider].
-* *MCP Servers* — you are here. Both managed and self-managed servers live in this list.
-* *OAuth Providers* — reusable OAuth provider definitions used by user-delegated MCP auth (and elsewhere). See xref:user-delegated-oauth.adoc[User-delegated OAuth].
-* *My Connections* — per-user OAuth connections for user-delegated MCP servers. See xref:user-delegated-oauth.adoc[User-delegated OAuth].
+* *LLM Providers*: OpenAI, Anthropic, Bedrock, Gemini, OpenAI-compatible endpoints. See xref:ai-gateway:configure-provider.adoc[Configure your LLM provider].
+* *MCP Servers*: You are here. Both managed and self-managed servers live in this list.
+* *OAuth Providers*: Reusable OAuth provider definitions used by user-delegated MCP auth (and elsewhere). See xref:user-delegated-oauth.adoc[User-delegated OAuth].
+* *My Connections*: Per-user OAuth connections for user-delegated MCP servers. See xref:user-delegated-oauth.adoc[User-delegated OAuth].
 
 // TODO: screenshot of the four-area sidebar on adp-production once standalone-ADP wording is final.
 
 == Key capabilities
 
-* *Tool discovery.* After you create or register a server, Redpanda performs a live `tools/list` against it and populates the server's detail page so you can see what tools agents will see.
-* *Service-account and user-delegated auth.* Pick a single shared upstream identity for all callers, or have each end-user authenticate against the upstream system with their own credentials.
-* *Code mode.* Optionally expose `{name}_search` and `{name}_execute` helpers so an agent can discover and orchestrate tools through generated Python or JavaScript instead of calling them one at a time.
-* *Inspector.* Test each tool, resource, and prompt directly from the ADP UI before pointing an agent at the server. See xref:test-tools.adoc[Test a server's tools].
-* *Aggregation.* Connect your agent to a single MCP URL and have Redpanda fan out across multiple registered MCP servers. See xref:ai-gateway:aggregation.adoc[MCP aggregation].
+* *Tool discovery*: After you create or register a server, Redpanda performs a live `tools/list` against it and populates the server's detail page so you can see what tools agents will see.
+* *Service-account and user-delegated auth*: Pick a single shared upstream identity for all callers, or have each end-user authenticate against the upstream system with their own credentials.
+* *Code mode*: Optionally expose `{name}_search` and `{name}_execute` helpers so an agent can discover and orchestrate tools through generated Python or JavaScript instead of calling them one at a time.
+* *Inspector*: Test each tool, resource, and prompt directly from the ADP UI before pointing an agent at the server. See xref:test-tools.adoc[Test a server's tools].
+* *Aggregation*: Connect your agent to a single MCP URL and have Redpanda fan out across multiple registered MCP servers. See xref:ai-gateway:aggregation.adoc[MCP aggregation].
 
-== Where to go next
+== Next steps
 
 . *Create your first MCP server.* xref:create-server.adoc[Create an MCP Server] walks through the marketplace picker, the managed and self-managed flows, every authentication mode, and code mode.
 . *Test what you built.* xref:test-tools.adoc[Test a server's tools] uses the Inspector tab to call tools, resources, and prompts live.

modules/mcp/pages/overview.adoc

@@ -1,11 +1,22 @@
 = Glossary
 :description: Definitions of key terms used in Redpanda Agentic Data Plane documentation.
 
-- <<Agentic Data Plane>>
-- <<Redpanda Cloud>>
-- <<Redpanda Connect>>
-- <<Redpanda core>>
-- <<Redpanda features>>
-- <<Redpanda in Kubernetes>>
-- <<Redpanda licenses>>
-- <<Redpanda security>>
+== Agentic Data Plane terms
+
+* glossterm:Agentic Data Plane (ADP)[]
+* glossterm:AI agent[]
+* glossterm:AI Gateway[]
+* glossterm:declarative agent[]
+* glossterm:BYOA (bring your own agent)[]
+* glossterm:MCP server[]
+* glossterm:MCP tool[]
+* glossterm:tool[]
+* glossterm:resource[]
+* glossterm:OAuth provider[]
+* glossterm:OAuth client[]
+* glossterm:OAuth connection[]
+* glossterm:token vault[]
+* glossterm:transcript[]
+* glossterm:spending event[]
+* glossterm:governance dashboard[]
+* glossterm:subagent[]