> 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/stage-2-productize/explore-recipes.md).

# Explore recipes

Recipes are proven patterns and practical code examples for common Data Product build scenarios. Use them as starting points: copy, adapt, and apply to your own project instead of writing everything from scratch.

***

## What is a recipe?

A recipe is a complete, working example that covers a specific scenario end-to-end. Each recipe explains why the pattern works, not just what to copy.

***

## Recipes in this section

| Recipe                                                                                        | Scenario                                                                                                                                           |
| --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Incremental by time](/build/stage-2-productize/explore-recipes/incremental-by-time.md)       | Build a time-series model that processes only new intervals on each run: the most important pattern for event, transaction, and log data at scale. |
| [Model selection](/build/stage-2-productize/explore-recipes/model-selection.md)               | Use `--select-model` to plan and run subsets of your DAG without processing every model: critical for large projects and CI/CD pipelines.          |
| [Full lifecycle example](/build/stage-2-productize/explore-recipes/full-lifecycle-example.md) | A complete Data Product from source declarations through final semantic layer, following the orders-analytics pipeline end-to-end.                 |

***

## When to reach for a recipe

* **You are starting a new project and want a reference implementation to copy from** --> follow [Full lifecycle example](/build/stage-2-productize/explore-recipes/full-lifecycle-example.md).
* **Your data is time-series and grows continuously (events, transactions, logs)** --> read [Incremental by time](/build/stage-2-productize/explore-recipes/incremental-by-time.md) before building your models.
* **You want to iterate on one model without re-running everything** --> see [Model selection](/build/stage-2-productize/explore-recipes/model-selection.md).
* **Your incremental model is processing the wrong intervals** --> re-read [Incremental by time](/build/stage-2-productize/explore-recipes/incremental-by-time.md) for the common mistakes section.
* **You are setting up CI/CD to deploy only changed models** --> see [Model selection](/build/stage-2-productize/explore-recipes/model-selection.md) for the `state:modified` selector.


---

# 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/stage-2-productize/explore-recipes.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.