# Core Concepts

Drizz’s automation model is built on four foundational concepts: commands that define user intent, a Vision Engine that interprets UI visually, an execution pipeline that guarantees deterministic behavior, and rich reporting that provides complete transparency into every run. Together, these components enable stable, repeatable, and scalable mobile test automation without dependency on fragile selectors or platform-specific APIs.

### 1. Commands

Drizz tests are structured as a sequence of commands (tap, type, validate, scroll, etc.).\
Each command is executed using Drizz’s AI-based interaction engine.

### 2. Vision Engine

Screens are interpreted using advanced visual analysis to recognize actionable components.

### 3. Execution Pipeline

\
Drizz applies a standardized execution lifecycle to every test step, ensuring reliability and repeatability:

### 4. Reporting

Every execution produces:

1. Step-level screenshots
2. Detailed Logs
3. Execution summaries
4. Error summaries
5. Execution timestamps<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drizz.dev/getting-started/overview/core-concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.