> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/build/get-started/the-three-stage-flow.md).

# The Three-stage flow

### How the three-stage flow works

<details open>

<summary><strong>Stage 1: Discover</strong></summary>

Understand the data before you build.

* [Explore products](/build/stage-1-discover/explore-products.md): look for existing products you can reuse.
* [Inspect metadata](/build/stage-1-discover/inspect-metadata.md): review the structure and signals already available.
* [Explore data](/build/stage-1-discover/explore-data.md): query and inspect the data you may want to productize.
* [Bring data in](/build/stage-1-discover/bring-data-in.md): Make the required data or metadata available to the selected engine when the source is not ready yet.

</details>

<details>

<summary><strong>Stage 2: Productize</strong></summary>

Turn the idea into a governed, tested Data Product.

* [Set up local development](/build/readme/ldk-setup.md): It is a prerequisite. Prepare the environment and initialize the project.
* [Connect to engine](/build/stage-2-productize/connect-to-engine.md): configure the engine connection.
* [Configure project](/build/stage-2-productize/configure-project.md): define project-level settings.
* [Define models](/build/stage-2-productize/define-models-and-logic.md): build transformation models, then add the semantic layer and business metrics.
* [Define the contract](/build/stage-2-productize/define-the-contract.md): configure the linter and add tests, assertions, and data-quality checks.
* [Define governance](/build/stage-2-productize/define-governance.md): configure governance policies and controls.
* [Validate and test locally](/build/stage-2-productize/validate-and-test-locally.md): run checks before deployment.
* [Explore recipes](/build/stage-2-productize/explore-recipes.md): use templates and reusable patterns.

</details>

<details>

<summary><strong>Stage 3: Publish</strong></summary>

Publish the Data Product so others can discover and use it.

* [Configure product deployment](/build/stage-3-publish/configure-product-deployment.md): define how the product is deployed and managed.
* [Publish the product](/build/stage-3-publish/deploy-data-product.md): validate, deploy, and publish the product to DPH.

</details>

### You can also explore

* [Build journey with AI](/build/get-started/build-journey-with-ai.md): AI-assisted path aligned to the same structure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/build/get-started/the-three-stage-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.