# Explorations & State Graphs Exploration is how Duku learns your application. The state graph is the output. ### Explorations An **exploration** is an automated browser session against a target URL. Duku launches a real browser, follows reachable interactions, and records the resulting states and transitions. You can run multiple explorations in parallel to increase coverage. ### States A **state** is a unique page or screen discovered during exploration. Each state includes the URL, a screenshot, and any captured errors. ### Transitions A **transition** is an action that moves from one state to another, such as a click, form submission, or navigation event. ### State graphs The **state graph** is a directed graph of discovered states and transitions. Duku exposes this graph at several levels: | Level | What it shows | | ---------------- | ------------------------------------------- | | **Run graph** | States and transitions from one exploration | | **Batch graph** | A merged view across multiple runs | | **Target graph** | The aggregate graph for a target | {% hint style="info" %} The target graph gets more complete as you run more explorations against the same target. {% endhint %} --- # 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.duku.ai/core-concepts/explorations-and-state-graphs.md?ask= ``` 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.