> 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

For a builder or owner, AI activation extends beyond consumption. The assistant can guide the user through a structured Data Product lifecycle.

## Stages

| Stage    | What the assistant helps with                                                                                                              |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Design   | Clarifies the business problem, consumers, entities, grain, measures, dimensions, freshness expectations, and quality contract.            |
| 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.                                        |
| Operate  | Uses runtime Data Product MCP tools to monitor runs, inspect quality failures, check lineage impact, profile tables, and answer questions. |

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