# Targets

The Targets page shows deploy-specific views of your application. Each target usually maps to a commit, branch, preview environment, or production deploy.

### Create a target

After you create a product, add a target for the deployment you want to test.

Each target includes:

* **URL:** The deployment URL Duku explores
* **Version:** A commit SHA, build ID, or release identifier
* **Metadata:** Optional context like branch name, PR number, or commit message

### Target detail

Open a target to inspect:

* **Merged state graph:** The aggregate graph across explorations for that target
* **Discovered pages:** Every state found so far
* **Identified goals:** Business-critical destinations extracted from the graph
* **Run history:** Exploration and intent runs for that target

From here, you can start new explorations or intent tests. Each exploration starts from the target URL.

{% hint style="info" %}
The target graph improves as Duku accumulates more exploration data for the same deployment.
{% 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/viewport-dashboard/targets.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.