> 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/references/interfaces/ai-activation/builder-journey.md).

# Builder journey

See how AI activation supports discovery, design, planning, build, and validation of Data Products.

For a builder or owner, AI activation extends beyond consumption. The assistant can guide the user through a structured Data Product lifecycle, from checking what already exists to a deployed product.

## Stages

| Stage    | What the assistant helps with                                                                             |
| -------- | --------------------------------------------------------------------------------------------------------- |
| Discover | Searches the Data Product catalog and table index for existing coverage before any design work starts.    |
| Design   | Clarifies the business problem, consumers, and key questions.                                             |
| Plan     | Locks entities, joins, measures, dimensions, grain, and freshness expectations into a reviewed spec.      |
| Build    | Generates a project scaffold, applies syntax templates, and reviews generated SQL or YAML before handoff. |
| Validate | Checks syntax, quality rules, tests, metadata, and assumptions before the Data Product is promoted.       |
| Deploy   | Hands the validated project to Git and deployment so it becomes a live, discoverable Data Product.        |

For the full walkthrough of these stages, see [Build journey with AI](https://v2.dataos.info/build/get-started/build-journey-with-ai).

## Workflow expectations

The builder workflow is grounded in the approved design spec and retrieved DataOS examples.

The assistant should mark assumptions, surface TODOs, and ask for confirmation at key checkpoints instead of silently filling gaps.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v2.dataos.info/references/interfaces/ai-activation/builder-journey.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
