> 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/v1/productize/assets.md).

# Assets

Assets are the components you create inside a data product. You declare what the product reads, write the transforms, and expose the result as business-friendly measures and metrics. Vulcan reads your SQL and works out the run order itself. You declare what you want; Vulcan handles the orchestration.

Build them in this order:

* [**Inputs**](/build/v1/productize/assets/inputs.md) - the upstream tables your models read from, declared as external models
* [**Seeds**](/build/v1/productize/assets/seeds.md) - small static CSV files loaded as tables
* [**Data model**](/build/v1/productize/assets/data-model.md) - SQL or Python files that transform data; each produces a table or view
* [**Semantic model**](/build/v1/productize/assets/semantic-model.md) - maps physical columns to dimensions, measures, segments, and joins
* [**Metrics**](/build/v1/productize/assets/metrics.md) - a measure plus a time column, as a queryable time series

These pages cover what each asset is and the shape you create, using the `orders-analytics` example project throughout. They stay deliberately minimal. For the full property reference, model kinds, Python models, statements, and macros, follow the links into [References → Vulcan](https://v2.dataos.info/references/resources/vulcan). Build shows you the path; References holds the syntax.

The chain runs in one direction:

```
Inputs + Seeds  -->  Data model (bronze -> silver -> gold)  -->  Semantic model  -->  Metrics
```


---

# 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/v1/productize/assets.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.