docs(warehouse-native): add mode architecture diagrams

docs/web-console-docs/warehouse-native/get-started.mdx

@@ -27,7 +27,7 @@ Getting started takes three steps:
 To begin, navigate to **Settings → Data Sources** and click **Add data source**.
 
 :::note The default data source
-Every installation ships with a built-in **default** data source — ABsmartly's managed ClickHouse. In [Hybrid mode](./modes#hybrid-warehouse-native) you keep this default and add external data sources for your goals. In [Fully mode](./modes#fully-warehouse-native) your own warehouse becomes the default. Exposure events always come from the default data source, so which one is the default determines your mode.
+Every installation ships with a built-in **default** data source, managed by ABsmartly. In [Hybrid mode](./modes#hybrid-warehouse-native) you keep this default and add external data sources for your goals. In [Fully mode](./modes#fully-warehouse-native) your own warehouse becomes the default. Exposure events always come from the default data source, so which one is the default determines your mode.
 :::
 
 You'll see a form with two sections: general information about the data source, and the connection credentials specific to your warehouse type.
@@ -183,15 +183,15 @@ ABsmartly will show a preview of the computed schedule in both UTC and your loca
 Match the frequency to your actual ETL schedule. If your data lands once a day at 8 AM UTC, use **Daily at specific time** with a 480-minute offset. Querying more often than data arrives just adds unnecessary load to your warehouse.
 :::
 
-Save the data source. If this is your **default** data source (a [Fully Warehouse Native](./modes#fully-warehouse-native) setup, or the standard managed ClickHouse), you're done — ABsmartly will start querying your warehouse on the configured schedule and your experiment data will flow through automatically. If you're connecting an **external** data source for [Hybrid mode](./modes#hybrid-warehouse-native), continue to Step 4.
+Save the data source. If this is your **default** data source (a [Fully Warehouse Native](./modes#fully-warehouse-native) setup, or the standard ABsmartly-managed data source), you're done — ABsmartly will start querying your warehouse on the configured schedule and your experiment data will flow through automatically. If you're connecting an **external** data source for [Hybrid mode](./modes#hybrid-warehouse-native), continue to Step 4.
 
 ---
 
 ## Step 4: Configure exposures import _(Hybrid only)_
 
 This step only applies to **external** (non-default) data sources — the setup used in [Hybrid Warehouse Native](./modes#hybrid-warehouse-native). If your warehouse is the default data source, you can skip it.
 
-In Hybrid mode, a goal can live in an external warehouse, but exposures come from the default data source (ABsmartly's managed ClickHouse). To compute metrics for such a goal, ABsmartly needs to make those exposures available to your external warehouse. It does this through an object store that you provide — you point ABsmartly at a storage location it can use, and your warehouse reads the exposures from there.
+In Hybrid mode, a goal can live in an external warehouse, but exposures come from the default data source (managed by ABsmartly). To compute metrics for such a goal, ABsmartly needs to make those exposures available to your external warehouse. It does this through an object store that you provide — you point ABsmartly at a storage location it can use, and your warehouse reads the exposures from there.
 
 The **Exposures import** section configures that storage location:
 

docs/web-console-docs/warehouse-native/modes.mdx

@@ -4,66 +4,134 @@ title: "Warehouse Native Modes"
 description: "Understand the two Warehouse Native modes — Hybrid and Fully — and choose the right one for your data and compliance needs."
 ---
 
-import Image from "../../../src/components/Image";
-
 # Warehouse Native Modes
 
 ABsmartly supports two ways of running Warehouse Native, depending on how much of your experiment data you want to keep inside your own warehouse:
 
-- **Hybrid Warehouse Native** — ABsmartly handles assignment and exposures in its managed ClickHouse, while your **goals and metrics** can be computed against your own warehouse. This is set per goal, so you can mix goals that stay in ABsmartly's ClickHouse with goals sourced from your warehouse.
+- **Hybrid Warehouse Native** — ABsmartly handles assignment and exposures, while your **goals and metrics** can be computed against your own warehouse. This is set per goal, so you can mix goals that stay with ABsmartly with goals sourced from your warehouse.
 - **Fully Warehouse Native** — your warehouse holds **everything** — exposures, goals, and attributes — and nothing user-level ever leaves your infrastructure.
 
 Both modes are built on the same foundation: **[data sources](./get-started)**. The mode you're in is determined by which data source is your **default**.
 
 ## The default data source
 
-Every ABsmartly installation has exactly one **default data source**. Out of the box, that's ABsmartly's built-in, managed **ClickHouse** — the same engine that powers the standard cloud experience. You can then connect additional **external** data sources (BigQuery, Snowflake, Redshift, Databricks, or your own ClickHouse) for your goals and metrics.
+Every ABsmartly installation has exactly one **default data source**. Out of the box, that's a data source **managed by ABsmartly** — the same one that powers the standard cloud experience. You can then connect additional **external** data sources (BigQuery, Snowflake, ClickHouse, Redshift, or Databricks) for your goals and metrics.
 
-<Image maxWidth="48rem" centered img="warehouse-native/datasources-list.png" alt="Data Sources list showing the managed ClickHouse marked as Default alongside an external BigQuery data source" />
+The Data Sources list shows this default data source alongside any external ones you connect, with a **Default** badge marking which one supplies exposures.
 
 The default data source is special: **exposure events can only come from the default data source.** This single rule is what separates the two modes.
 
-- In **Hybrid**, the default stays ABsmartly's managed ClickHouse, so exposures live there.
+- In **Hybrid**, the default stays managed by ABsmartly, so ABsmartly handles exposures.
 - In **Fully**, your own warehouse becomes the default, so exposures live in your warehouse alongside everything else.
 
 ## Hybrid Warehouse Native
 
-In Hybrid mode, you keep ABsmartly's managed ClickHouse as the default data source and attach one or more external warehouses that your **goals** can draw from.
-
-- **Assignment and exposures** are handled by ABsmartly and stored in the managed ClickHouse.
-- **Goals and metrics** are assigned a data source per goal. A goal can be sourced from an external warehouse — where your business data already lives, so results line up with what your BI and finance teams report — or from ABsmartly's managed ClickHouse. You can mix both: some goals stay in ClickHouse while others come from your warehouse.
-- When a goal is sourced from an external warehouse, ABsmartly makes the exposures that live in the default ClickHouse available to that warehouse so the two can be evaluated together. You enable this by pointing ABsmartly at an object store through the **[Exposures import](./get-started#step-4-configure-exposures-import-hybrid-only)** section on each external data source.
-
-Hybrid lets you bring metrics into your warehouse at your own pace: you keep ABsmartly's battle-tested assignment and exposure pipeline, and move as many (or as few) of your goals into your warehouse as you like.
+In Hybrid mode, you keep the ABsmartly-managed data source as your default and attach one or more external warehouses that your **goals** can draw from.
+
+- **Assignment and exposures** are handled by ABsmartly.
+- **Goals and metrics** are assigned a data source per goal. A goal can be sourced from an external warehouse — where your business data already lives, so results line up with what your BI and finance teams report — or it can stay managed by ABsmartly. You can mix both.
+- When a goal is sourced from an external warehouse, ABsmartly makes the default source's exposures available to that warehouse so the two can be evaluated together. You enable this by pointing ABsmartly at an object store through the **[Exposures import](./get-started#step-4-configure-exposures-import-hybrid-only)** section on each external data source.
+- Because that import lands the exposures inside your warehouse, **goals sourced from your warehouse can filter and enrich those exposures** the same way Fully mode does — strip out bots and internal traffic, or join in your own attributes table. **Goals that stay managed by ABsmartly don't get this**, since their exposures never leave ABsmartly's default data source.
+
+```mermaid
+%%{init: {"theme": "base", "themeVariables": {"fontFamily": "Manrope, system-ui, sans-serif", "primaryColor": "#ffffff", "primaryBorderColor": "#CA3721", "primaryTextColor": "#28293d", "lineColor": "#9296a6", "tertiaryColor": "#ffffff", "fontSize": "15px"}}}%%
+flowchart TB
+    SDK(["Your app - ABsmartly SDK"])
+
+    subgraph ABC["ABsmartly (default)"]
+        DEFAULT[("Exposures and<br/>managed goals")]
+    end
+
+    subgraph EWH["Your warehouse (external)"]
+        IMPORT[("Imported<br/>exposures")]
+        WGOALS[("Your goals")]
+        ATTR[("Your attributes")]
+        FILTER("Filter and enrich")
+    end
+
+    RESULTS(("Experiment<br/>results"))
+
+    SDK --> DEFAULT
+    DEFAULT -.->|"exposures import"| IMPORT
+    IMPORT --> FILTER
+    WGOALS --> FILTER
+    ATTR --> FILTER
+    FILTER ==>|"filtered and enriched"| RESULTS
+    DEFAULT -->|"managed goals<br/>no filtering"| RESULTS
+
+    style ABC fill:#FBEDEA,stroke:#CA3721,stroke-width:1.5px,color:#28293d
+    style EWH fill:#EEF1FF,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style DEFAULT fill:#ffffff,stroke:#CA3721,stroke-width:1.5px,color:#28293d
+    style IMPORT fill:#ffffff,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style WGOALS fill:#ffffff,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style ATTR fill:#ffffff,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style FILTER fill:#465BFF,stroke:#465BFF,stroke-width:1.5px,color:#ffffff
+    style RESULTS fill:#28293d,stroke:#28293d,stroke-width:1.5px,color:#ffffff
+    style SDK fill:#ffffff,stroke:#9296a6,stroke-width:1.5px,color:#28293d
+```
+
+Hybrid lets you bring metrics into your warehouse at your own pace: you keep ABsmartly's battle-tested assignment and exposure pipeline, and move as many (or as few) of your goals into your warehouse as you like — gaining filtering and enrichment for each one you move.
 
 ## Fully Warehouse Native
 
 In Fully mode, **your own warehouse is the default data source.** Exposures, goals, and attributes all live in your warehouse, and no user-level data is ever sent to ABsmartly's cloud. ABsmartly still handles experiment management, assignment logic, statistics, and metric governance — but the underlying data never leaves your environment.
 
-Because exposures come from the default data source, going Fully unlocks two things Hybrid can't offer:
+Because every exposure already lives in your warehouse, Fully extends Hybrid's warehouse-side capabilities to **every goal**, not just the ones you explicitly source from your warehouse:
 
 - **Filter exposures yourself.** You control the exposures table, so you can strip out bots, scrapers, internal traffic, or any other unwanted exposures before ABsmartly analyzes them — using your own logic in your own warehouse.
-- **Enrich exposures with your own attributes.** You can join in an external **attributes** table to add segmentation dimensions that ABsmartly never sees in Hybrid mode, then slice experiment results by those attributes.
+- **Enrich exposures with your own attributes.** You can join in an external **attributes** table to add segmentation dimensions, then slice experiment results by those attributes.
+
+```mermaid
+%%{init: {"theme": "base", "themeVariables": {"fontFamily": "Manrope, system-ui, sans-serif", "primaryColor": "#ffffff", "primaryBorderColor": "#CA3721", "primaryTextColor": "#28293d", "lineColor": "#9296a6", "tertiaryColor": "#ffffff", "fontSize": "15px"}}}%%
+flowchart TB
+    SDK(["Your app - ABsmartly SDK"])
+
+    subgraph WH["Your warehouse (default)"]
+        EXP[("Exposures")]
+        GOALS[("Goals")]
+        ATTR[("Your attributes")]
+        FILTER("Filter and enrich")
+    end
+
+    subgraph ABC["ABsmartly Cloud"]
+        ENGINE("Assignment logic, stats and<br/>metric governance<br/>no user-level data stored")
+    end
+
+    SDK --> EXP
+    EXP --> FILTER
+    ATTR --> FILTER
+    FILTER ==>|"filtered and enriched, every goal"| ENGINE
+    GOALS -->|"queried on your schedule"| ENGINE
+
+    style WH fill:#EEF1FF,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style ABC fill:#FBEDEA,stroke:#CA3721,stroke-width:1.5px,color:#28293d
+    style EXP fill:#ffffff,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style GOALS fill:#ffffff,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style ATTR fill:#ffffff,stroke:#465BFF,stroke-width:1.5px,color:#28293d
+    style FILTER fill:#465BFF,stroke:#465BFF,stroke-width:1.5px,color:#ffffff
+    style ENGINE fill:#ffffff,stroke:#CA3721,stroke-width:1.5px,color:#28293d
+    style SDK fill:#ffffff,stroke:#9296a6,stroke-width:1.5px,color:#28293d
+```
 
 :::info Why the exposure source matters
-Exposure-side filtering (robots, scrapers, internal traffic) and attribute enrichment both operate on the exposure stream. Since exposures can only come from the default data source, these capabilities are only available when **your** warehouse is the default — that is, in **Fully Warehouse Native**. If you need either, choose Fully.
+Exposure-side filtering (bots, scrapers, internal traffic) and attribute enrichment both operate on the exposure stream, and only work once that stream lives inside your warehouse. In **Hybrid**, that's true for goals you source from your warehouse — their imported exposures can be filtered and enriched. It's **not** true for goals that stay managed by ABsmartly, since their exposures never leave the default data source. In **Fully**, every exposure lives in your warehouse, so filtering and enrichment apply to every goal.
 :::
 
 ## Choosing a mode
 
 | | Hybrid Warehouse Native | Fully Warehouse Native |
 |---|---|---|
-| **Default data source** | ABsmartly's managed ClickHouse | Your own warehouse |
-| **Where exposures live** | ABsmartly's managed ClickHouse | Your warehouse |
-| **Where goals & metrics are computed** | Per goal: ABsmartly's ClickHouse or your warehouse | Your warehouse |
-| **User-level data in ABsmartly cloud** | Exposures, plus any goals kept in ClickHouse | None |
-| **Filter exposures yourself (bots/scrapers/internal traffic)** | ❌ | ✅ |
-| **Enrich exposures with your own attributes table** | ❌ | ✅ |
+| **Default data source** | Managed by ABsmartly | Your own warehouse |
+| **Where exposures live** | ABsmartly's default data source | Your warehouse |
+| **Where goals & metrics are computed** | Per goal: managed by ABsmartly or your warehouse | Your warehouse |
+| **User-level data in ABsmartly cloud** | Exposures, plus any goals kept managed by ABsmartly | None |
+| **Filter exposures yourself (bots/scrapers/internal traffic)** | ✅ for goals sourced from your warehouse only | ✅ for every goal |
+| **Enrich exposures with your own attributes table** | ✅ for goals sourced from your warehouse only | ✅ for every goal |
 | **Setup effort** | Lower — keep ABsmartly's exposure pipeline | Higher — your warehouse owns exposures end to end |
 
-**Choose Hybrid** when you want some or all of your goals to draw from your warehouse data, but are happy to let ABsmartly manage assignment and exposures.
+**Choose Hybrid** when you want some or all of your goals to draw from your warehouse data, but are happy to let ABsmartly manage assignment and exposures for the rest.
 
-**Choose Fully** when data residency requires that no user-level data leaves your infrastructure, or when you need to filter exposures or enrich them with your own attributes.
+**Choose Fully** when data residency requires that no user-level data leaves your infrastructure, or when you need to filter exposures or enrich them with your own attributes for **every** goal, not just the ones you move to your warehouse.
 
 ## Next steps
 

docs/web-console-docs/warehouse-native/overview.mdx

@@ -28,8 +28,8 @@ You configure a **data source** that connects ABsmartly to your warehouse, map y
 
 Warehouse Native comes in two flavors, depending on how much of your data you want to keep in your own warehouse:
 
-- **Hybrid Warehouse Native** — ABsmartly manages assignment and exposures in its managed ClickHouse, while your **goals and metrics** can be computed against your own warehouse. It's set per goal, so you can mix goals sourced from ABsmartly's ClickHouse with goals sourced from your warehouse.
-- **Fully Warehouse Native** — **everything** lives in your warehouse: exposures, goals, and attributes. No user-level data ever leaves your infrastructure, and you can filter exposures or enrich them with your own attributes.
+- **Hybrid Warehouse Native** — ABsmartly manages assignment and exposures, while your **goals and metrics** can be computed against your own warehouse. It's set per goal, so you can mix goals managed by ABsmartly with goals sourced from your warehouse. Goals sourced from your warehouse can also be filtered and enriched with your own attributes.
+- **Fully Warehouse Native** — **everything** lives in your warehouse: exposures, goals, and attributes. No user-level data ever leaves your infrastructure, and you can filter or enrich exposures for every goal.
 
 Which mode you're in is determined by which data source is your **default**. See **[Warehouse Native Modes](./modes)** for a full comparison and guidance on choosing.