Skip to content

Commit 2e94514

Browse files
committed
docs: restore 3-point structure for Why QueryMode
1 parent 818a980 commit 2e94514

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

docs/src/content/docs/why-querymode.mdx

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,11 @@ title: Why QueryMode
33
description: Agents are the new users. They need dynamic pipelines, not pre-built ETL.
44
---
55

6-
## Agents need live data at the edge
6+
1. **Agents are becoming the majority of internet traffic.** They serve different owners across different parts of the world, but share the same training data and independently reach the same conclusions. When thousands of agents hit the same endpoints at the same millisecond, the traffic looks like a DDoS — except every request is legitimate. Data must live at the edge to survive this.
77

8-
Training data can't keep up with the speed the world produces information. Agents make API calls for live data — lots of them. And because agents serve different owners across different parts of the world, they independently reach the same conclusions and hit the same endpoints at the same time. The resulting traffic pattern looks like a DDoS, except every request is legitimate. Data must live at the edge to survive this.
8+
2. **Agents need live data.** Training data can't keep up with the speed the world produces information. Agents make API calls for live data — lots of them. That data needs to live at the edge, close to where agents run.
99

10-
## Pre-built ETL can't serve agents
11-
12-
Traditional data pipelines assume a human pre-defines what questions matter, builds a pipeline on a schedule, and stores the results. Agents don't ask pre-defined questions. They chain queries in ways no pipeline designer anticipated — funnel analysis, then retention for just those users, then attribution for just those retained users. The pipeline doesn't exist until the agent creates it.
10+
3. **Pre-built ETL can't serve agents.** Traditional data pipelines assume a human pre-defines what questions matter, builds a pipeline on a schedule, and stores the results. Agents don't ask pre-defined questions. They chain queries in ways no pipeline designer anticipated — funnel analysis, then retention for just those users, then attribution for just those retained users. The pipeline doesn't exist until the agent creates it.
1311

1412
## Fixed ETL vs dynamic pipelines
1513

0 commit comments

Comments
 (0)