docs: Fix Dome UI

concepts/defense/guard.mdx

@@ -3,7 +3,7 @@
 description: "Specialized protection modules that defend against specific threat categories."
 ---
 
 A Guard is a protection module focused on a specific threat category. While a [Guardrail](/concepts/defense/guardrail) defines your overall protection policy, Guards do the actual work of detecting and handling threats.
 
 Guards are the building blocks of Guardrails. Each Guard performs specific checks and/or transformations on the data. For instance, a Guard in an input Guardrail can check for security, while a Guard in an output Guardrail might check for moderation or privacy.
 
@@ -15,8 +15,12 @@
 - Integrity
 - Generic
 
 Guards consist of a set of [Detectors](/concepts/evaluation-components/detector) and how they should be executed.
 
+<Info>
+The Vijil Console currently exposes Security, Moderation, and Privacy Guards in the **Protect** view. Integrity and Generic are broader Dome categories and do not appear as predefined Console Guard types.
+</Info>
+
 ## Next Steps
 
 <CardGroup cols={2}>
@@ -26,8 +30,7 @@
   <Card title="Configure Guardrails" icon="sliders-horizontal" href="/owner-guide/protect-in-production/configuring-guardrails">
     Set up Guards for your agent
   </Card>
-  <Card title="Available Guards" icon="list" href="/tutorials/protect-agents/configuring-guardrails">
-    Reference of all Guard types
+  <Card title="Available Guards" icon="list" href="/owner-guide/protect-in-production/configuring-guardrails">
+    Review Guard types in the Console
   </Card>
 </CardGroup>
-

concepts/defense/guardrail.mdx

@@ -5,13 +5,17 @@
 
 A Guardrail is a configured pipeline of [Guards](/concepts/defense/guard) that implements your protection policy. If Guards are the individual security checks, Guardrails are the security checkpoint they define which checks happen, in what order, and what to do with the results.
 
 Vijil Dome allows users to assemble and configure Guardrails, which are designed to scan data exchanged with LLMs, knowledge bases, or other agents. Dome supports several types of Guardrails:
 
 - **Input Guardrails**: For scanning inputs to a foundation model.
 - **Output Guardrails**: For scanning outputs from a foundation model.
 - **Retrieval Guardrails** (coming soon): To protect requests to and from retrievers.
 - **Execution Guardrails** (coming soon): To protect requests to and from external agents and tools.
 
+<Info>
+The Vijil Console currently configures Input and Output Guards from the selected Agent's **Protect** view. Retrieval and Execution Guardrails are broader concepts and are not sections in the current Console.
+</Info>
+
 ```mermaid actions={false}
 %%{init: {'theme':'base', 'themeVariables': {'fontFamily':'Futura Medium, Futura, sans-serif','fontSize':'13px'}, 'flowchart': {'nodeSpacing':25,'rankSpacing':35,'padding':6}}}%%
 flowchart TD
@@ -48,7 +52,7 @@
     class Platform platform;
 ```
 
 Guardrails consist of a set of [Guards](/concepts/defense/guard) and how they should be executed. These Guards are fully configurable and customizable.
 
 ## Setting Up Guards and Detectors
 
@@ -95,7 +99,7 @@
 
 ### Example Configuration
 
-Here is an example of how you can set up Guards and Detectors (see the [Configuring Dome section](/tutorials/protect-agents/configuring-guardrails) for more details):
+Here is an example based on the predefined Console Guards and Detectors (see the [Configuring Dome section](/owner-guide/protect-in-production/configuring-guardrails) for more details):
 
 <CodeGroup>
 ```python title="Python" icon="python"
@@ -105,31 +109,31 @@
     # Setup Guardrails from Guards
     ########################
     # Input Guardrail
-    "input-guards": ["prompt-injection", "input-privacy"],
+    "input-guards": ["security-guard", "moderation-guard"],
 
-    # output guardrail
-    "output-guards": ["output-toxicity"],
+    # Output Guardrail
+    "output-guards": ["moderation-guard", "privacy-guard"],
 
     ##########################
     # Assemble and configure Guards
     ##########################
 
-    # a guard for prompt injection
-    "prompt-injection": {
+    # Security input Guard
+    "security-guard": {
         "type": "security",
-        "methods" : ["prompt-injection-deberta-v3-base", "security-llm"],
+        "methods": ["encoding-heuristics", "prompt-injection-mbert"],
     },
 
-    # a guard to remove PII from requests to the LLM
-    "input-privacy": {
-        "type": "privacy",
-        "methods": ["privacy-presidio"]
+    # Moderation input and output Guard
+    "moderation-guard": {
+        "type": "moderation",
+        "methods": ["moderation-flashtext", "moderation-mbert"],
     },
 
-    # a guard for toxic output content
-    "output-toxicity": {
-        "type": "moderation",
-        "methods": ["moderation-llamaguard"]
+    # Privacy output Guard
+    "privacy-guard": {
+        "type": "privacy",
+        "methods": ["privacy-presidio"],
     },
 }
 ```
@@ -146,7 +150,7 @@
 ## Next Steps
 
 <CardGroup cols={2}>
   <Card title="Guard" icon="shield" href="/concepts/defense/guard">
     Understand individual protection types
   </Card>
   <Card title="Detector" icon="microscope" href="/concepts/defense/detector">

concepts/platform/console.mdx

@@ -1,9 +1,9 @@
 ---
 title: "Console"
 description: "The Vijil Console for managing Agents, Evaluations, and runtime protection configurations."
 ---
 
 The Console is the web-based management interface of the Vijil platform. It acts as the central hub where teams interact with all major components of the system which brings together evaluation, protection, and continuous improvement into a single user friendly experience.
 
 Through the Console, users can:
 
@@ -11,11 +11,11 @@
 - [Run structured evaluations using Diamond](/developer-guide/evaluate/running-evaluations)
 - [Configure runtime protections with Dome](/developer-guide/protect/configuring-guardrails)
 
 Instead of operating as separate tools, these features are integrated into one single environment, which makes it easier to oversee the entire agent lifecycle, starting from development and ending on deployment and/or beyond.
 
 On the other hand, the Console is designed for both technical and non-technical users. Engineers and developers use it to configure and adjust agents, and later run some evaluations, while security leads, compliance officers, and stakeholders rely on it to review results and make necessary decisions. This system of shared interface ensures that everything is in line across teams and reduces time consumption in the decision making part.
 
 ## Starting with Vijil Console
 
 <Card title="Register an Agent" icon="bot" href="/owner-guide/register-agents/registering-agents.mdx" cta="Start by Registering an Agent">
 </Card>
@@ -29,15 +29,15 @@
 
 ## **Trust Reports**
 
 After running an evaluation with **Diamond**, the results are compiled into a **Trust Report**, which is displayed directly in the **Console**.
 
 This report serves as a structured, audit-ready summary of the agent’s performance and risk profile, including:
 
 - **Agent details and testing methodology**\
   A clear overview of what was tested, how the evaluation was done, and which scenarios or policies were applied in the process.
 - **Overall Trust Score**
 
 A numerical score used to assess the agent’s reliability, security, and overall safety. In general, a score **above 70** suggests the Agent is ready or at least nearly ready for deployment.
 
 - **Clear steps to reduce risks and prepare for deployment** \
   A specific guide on how to improve the agent, address vulnerabilities, and safely move towards production.
@@ -46,11 +46,11 @@
 
 ### **Who Uses Trust Reports and Why**
 
 Trust Reports are not just for engineers—they are designed for multiple stakeholders:
 
 - **Security teams** use them to identify vulnerabilities and ensure resilience against attacks
 - **Compliance officers** rely on them for audit documentation and regulatory alignment
 - **Product and business leaders** use them to decide whether an agent is ready for deployment
 - **Stakeholders and executives** review them for final sign-off
 
-Because the reports are standardized and easy to understand, they help overcome the gap between technical evaluation and decision-making. They provide evidence needed to move agents out of “_security limbo_” and into production.
+Because the reports are standardized and easy to understand, they help overcome the gap between technical evaluation and decision-making. They provide evidence needed to move agents out of “_security limbo_” and into production.

concepts/welcome.mdx

@@ -1,21 +1,21 @@
 ---
 title: 'Welcome to Vijil'
 description: 'The trust layer for AI agents measure reliability, security, and safety, then ship with evidence.'
 ---
 
 <Tip>
-**TL;DR:** Vijil is the trust layer for [AI agents](/owner-guide/register-agents/what-is-an-agent), measuring [reliability](/concepts/trust-score/reliability), [security](/concepts/trust-score/security), and [safety](/concepts/trust-score/safety) before deployment (Diamond) and protecting agents at runtime (Dome). Start with [Concepts](/concepts/trust-score/introduction) for the mental model, or jump to the [Owner's Guide](/owner-guide/getting-started/introduction) or [Developer Guide](/developer-guide/getting-started/introduction) to get started.
+**TL;DR:** Vijil is the trust layer for [AI agents](/owner-guide/register-agents/what-is-an-agent), measuring [reliability](/concepts/trust-score/reliability), [security](/concepts/trust-score/security), and [safety](/concepts/trust-score/safety) before deployment (Diamond) and protecting Agents at runtime (Dome). Start with [Concepts](/concepts/trust-score/introduction) for the mental model, or jump to the [Owner's Guide](/owner-guide/getting-started/introduction) or [Developer Guide](/developer-guide/getting-started/introduction) to get started.
 </Tip>
 
 Agents often stall before production: security and compliance need **proof**, not demos. Vijil turns that into **measurable trust**, systematic evaluation, runtime protection, and a feedback loop from real behavior.
 
-**[Trust Score](/concepts/trust-score/introduction)** summarizes how an agent performs across **[reliability](/concepts/trust-score/reliability)**, **[security](/concepts/trust-score/security)**, and **[safety](/concepts/trust-score/safety)**; so reviews can reference evidence instead of opinions. Under that umbrella, **[Diamond](/concepts/platform/diamond)** probes behavior in depth through Trust Score evaluations and adaptive [Red Team](/concepts/platform/diamond#red-team-in-diamond) campaigns, while **Dome** enforces **[Guardrails](/concepts/defense/guardrail)** at runtime.
+**[Trust Score](/concepts/trust-score/introduction)** summarizes how an Agent performs across **[reliability](/concepts/trust-score/reliability)**, **[security](/concepts/trust-score/security)**, and **[safety](/concepts/trust-score/safety)**; so reviews can reference evidence instead of opinions. Under that umbrella, **[Diamond](/concepts/platform/diamond)** probes behavior in depth through Trust Score evaluations and adaptive [Red Team](/concepts/platform/diamond#red-team-in-diamond) campaigns, while **Dome** enforces **[Guardrails](/concepts/defense/guardrail)** at runtime.
 
 ## How Vijil Measures Trust
 
 | Dimension | Question | Learn more |
 |-----------|----------|------------|
-| **Reliability** | Does the agent do the right thing, consistently, under stress? | [Reliability](/concepts/trust-score/reliability) |
+| **Reliability** | Does the Agent do the right thing, consistently, under stress? | [Reliability](/concepts/trust-score/reliability) |
 | **Security** | Can it resist abuse and protect sensitive data? | [Security](/concepts/trust-score/security) |
 | **Safety** | Does it stay within policy and avoid harmful outcomes? | [Safety](/concepts/trust-score/safety) |
 
@@ -31,9 +31,9 @@
 production
 
 - Shipping fast increases failure rates and elevates risk; without
-objective trust evidence, agents are in security limbo
+objective trust evidence, Agents are in security limbo
 
-- Generic red-teaming and [Guardrail](/concepts/defense/guardrail) do not ensure agents are
+- Generic red-teaming and [Guardrail](/concepts/defense/guardrail) do not ensure Agents are
 safe for their specific context
 
 - Failure insights do not feed back into development, leaving the
@@ -41,33 +41,33 @@
 
 <img src="/images/concepts/what-is-vijil/vijil_lifecycle.webp" alt="Vijil lifecycle: Ship with Diamond, Run with Dome" style={{maxWidth: '500px', margin: '1.5rem auto', display: 'block'}} className="theme-aware-image" />
 
 **Vijil Diamond**
 Automates evaluation based on custom bespoke policies for
 business context and personas. Turns 'is this safe?' into an
 answerable question with an audit-ready Trust Score.
 
 **Vijil Dome**
-Enforces policies to protect and monitor agents at runtime
+Enforces policies to protect and monitor Agents at runtime
 through embedded Guardrails, blocking attacks in real-time and
 logging detailed telemetry.
 
 ## Continue with Vijil
 
 Pick where you work and what you need next:
 
 <CardGroup cols={1}>
   <Card title="Concepts" icon="book-open-text" href="/concepts/trust-score/introduction">
     You want the mental model - [Trust Score](concepts/trust-score/introduction), evaluation components ([Harness](/concepts/evaluation-components/harness), [Scenario](/concepts/evaluation-components/scenario), [Probe](/concepts/evaluation-components/probe)), and Defense ([Guards](/concepts/defense/guard), [Guardrails](/concepts/defense/guardrail), [Detectors](/concepts/defense/detector)).
 
     **Start here** → [Trust Score](/concepts/trust-score/introduction), then explore this tab for deeper topics and the [Glossary](/concepts/glossary).
   </Card>
   <Card title="Agent Owner's Guide" icon="building-2" href="/owner-guide/getting-started/introduction">
-    You use the Vijil console to [register agents](/owner-guide/register-agents/registering-agents), [run evaluations](/owner-guide/run-evaluations/running-evaluations), configure Dome, and report to stakeholders.
+    You use the Vijil console to [register Agents](/owner-guide/register-agents/registering-agents), [run Evaluations](/owner-guide/run-evaluations/running-evaluations), [configure Dome](/owner-guide/protect-in-production/configuring-guardrails), [monitor Dome Metrics](/owner-guide/protect-in-production/observability), and report to stakeholders.
 
     **Start here** → [Get started](/owner-guide/getting-started/introduction) in the console.
   </Card>
   <Card title="Agent Developer's Guide" icon="code" href="/developer-guide/getting-started/introduction">
     You integrate Vijil via SDKs & APIs, frameworks (e.g. LangChain, ADK), and production wiring.
 
     **Start here** → [Developer introduction](/developer-guide/getting-started/introduction) and installation.
   </Card>
@@ -75,18 +75,19 @@
 
 ### Quick Resources
 
 - **Evaluate in the UI** → [Get started](/owner-guide/getting-started/introduction)
 - **Protect in production** → [Configuring Guardrails](/owner-guide/protect-in-production/configuring-guardrails)
+- **Monitor protection** → [Dome Metrics](/owner-guide/protect-in-production/observability)
 
 ## Coming Soon
 
 Two additional products are currently in development and will expand the Vijil platform:
 
 <CardGroup cols={2}>
   <Card title="Depot" icon="box" badge="Coming Soon">
-    A catalog of hardened models and building blocks, including [Guardrail](/concepts/defense/guardrail) models tuned for agent safety, hardened LLMs optimized for specific tasks, and pre-validated components that reduce months of security work to days.
+    A catalog of hardened models and building blocks, including [Guardrail](/concepts/defense/guardrail) models tuned for Agent safety, hardened LLMs optimized for specific tasks, and pre-validated components that reduce months of security work to days.
   </Card>
   <Card title="Darwin" icon="dna" badge="Coming Soon">
-    Continuous improvement powered by reinforcement learning over production telemetry. Darwin learns from real-world failures, edge cases, and behavior drift to keep your agents resilient over time.
+    Continuous improvement powered by reinforcement learning over production telemetry. Darwin learns from real-world failures, edge cases, and behavior drift to keep your Agents resilient over time.
   </Card>
 </CardGroup>

owner-guide/getting-started/introduction.mdx

@@ -1,20 +1,20 @@
 ---
 title: 'Get Started with Console'
 description: 'Why teams use Vijil for trust evidence, then register an Agent, run an Evaluation, and turn on Dome from the Console.'
 ---
 
 ## Evidence You Can Ship On
 
 AI agents often stall between build and production: security and compliance want proof; the business wants to move. Without shared, objective evidence, approvals turn into opinion-based negotiation.
 
 This page explains how Vijil helps both sides, then walks through the **Console**: register an Agent, run an Evaluation, optionally run [Red Team](/concepts/platform/diamond#red-team-in-diamond), read your [Trust Report](#read-the-trust-report), and configure **[Dome](/concepts/welcome#build-ship-run-evolve)** Guardrails.
 
 <Warning>
     This guide assumes you have Vijil Console deployed. See [how to deploy Vijil Console in your environment](#).
 </Warning>
 
 <Info>
 If you want to integrate via the Vijil API and using a code library, use the [Developer Guide](/developer-guide/getting-started/introduction). This guide focuses on the **Vijil Console**.
 </Info>
 
 
@@ -23,7 +23,7 @@
 
 <CardGroup cols={2}>
   <Card title="Business owner" icon="rocket">
     Ship agents that deliver value with **fast evaluation cycles**, **clear pass/fail criteria**, and **reports** stakeholders can use without endless ad hoc testing.
   </Card>
   <Card title="Risk owner" icon="shield">
     Approve with **quantified** reliability, security, and safety; **versioned, audit-style** artifacts; and visibility into **residual risk** and compensating controls.
@@ -35,13 +35,13 @@
 | | Business owner | Risk owner |
 |---|----------------|------------|
 | **Pressure** | Delivery speed | Risk reduction |
 | **Question** | “Can we ship?” | “Can I defend approving this?” |
 
 **Vijil aligns those questions with the [Trust Score](/concepts/trust-score/introduction)**, a reproducible score from a defined Harness, not a one-off opinion. Agree on the threshold before you test; compare results after; the decision gets clearer.
 
 Vijil measures **reliability**, **security**, and **safety**, the failure modes that look like “the model behaved” but still hurt users or the org. For detail on each dimension, see [Trust Score](/concepts/trust-score/introduction) in Concepts.
 
 ## Working with Vijil Console
 
 First you will need to **register** an Agent, then **run** an [Evaluation](/concepts/evaluation-components/introduction) (with a built-in [Trust Score Harness](/concepts/evaluation-components/harness) or a [custom Harness](/concepts/evaluation-components/harness)), optionally run **Red Team** for deeper adversarial testing, **read** the [Trust Report](#read-the-trust-report), then **[Protect](/owner-guide/protect-in-production/configuring-guardrails)** the Agent with Dome.
 
@@ -127,17 +127,26 @@
   </Step>
 
   <Step title="Configure Dome">
-      <Badge color="yellow">Coming Soon</Badge>
+    Open **Agents** in the Console, select the Agent you want to protect, and click **Protect** in the Actions row.
+
+    1. Review the predefined **Input Guards** and **Output Guards**.
+    2. Enable, disable, or extend the Guards based on the Agent's evaluation findings and policies.
+    3. Test the Guard configuration with representative inputs.
+    4. Click **Save**, then **Apply** when the configuration is ready.
+
+    See [Configure Guardrails](/owner-guide/protect-in-production/configuring-guardrails) for the complete owner workflow.
   </Step>
 
-  <Step title="Configure Dome in your Application">
-      <Badge color="yellow">Coming Soon</Badge>
+  <Step title="Monitor Dome Metrics">
+    Return to the selected Agent and click **Monitor** in the Actions row. Review blocked inbound and outbound traffic, Guard errors, P99 latency, threat activity, and individual events.
+
+    See [Monitor Dome Metrics](/owner-guide/protect-in-production/observability) for guidance on interpreting the dashboard.
   </Step>
 </Steps>
 
 ## Automate with MCP
 
 The [Vijil MCP server](/developer-guide/agentic/quickstart) exposes every Console action as a tool that [Claude Code](https://claude.ai/code) can call directly. Instead of clicking through the Console UI, you describe what you want in plain English and Claude runs the same registration, evaluation, and reporting steps from above through conversation.
 
 <Prompt description="Run a safety and security Evaluation on Agent a1b2c3d4-… with a sample size of 50, and wait for it to complete">
 Run a safety and security Evaluation on Agent a1b2c3d4-… with a sample size of 50, and wait for it to complete