> 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/july2026/recipes.md).

# Recipes

Proven patterns for common build scenarios. Copy, adapt, apply.

Recipes are working patterns for scenarios that come up again and again. Each one explains why the pattern works, not just what to copy, so you can adapt it rather than paste it blind.

## Choose a recipe

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Reuse a Data Product</strong><br>Build a downstream product that reads another product's published outputs, governed through an input contract.</td><td><a href="https://v2.dataos.info/build/july2026/recipes/reuse-data-products.md">Reuse a Data Product</a></td></tr><tr><td><strong>Build a Python model for AI/ML workflows</strong><br>Write a Vulcan Python model that returns a DataFrame for machine learning, forecasting, or logic SQL can't express.</td><td><a href="https://v2.dataos.info/build/july2026/recipes/build-a-python-model.md">Build a Python model for AI/ML workflows</a></td></tr><tr><td><strong>Cluster data with a Spark ML Python model</strong><br>Run KMeans clustering with Spark MLlib, with a scikit-learn fallback when Spark isn't available.</td><td><a href="https://v2.dataos.info/build/july2026/recipes/spark-ml-python-model.md">Cluster data with a Spark ML Python model</a></td></tr><tr><td><strong>Wait for data to be ready with signals</strong><br>Make a scheduled model wait for late-arriving source data instead of running on a fixed clock.</td><td><a href="https://v2.dataos.info/build/july2026/recipes/wait-for-data-with-signals.md">Wait for data to be ready with signals</a></td></tr><tr><td><strong>Route plan and run failures to Slack or Teams</strong><br>Wire Vulcan's notification_targets so a failed plan or run pages Slack or Teams automatically.</td><td><a href="https://v2.dataos.info/build/july2026/recipes/route-failures-to-slack-or-teams.md">Route plan and run failures to Slack or Teams</a></td></tr><tr><td><strong>Track dimension history with SCD Type 2</strong><br>Convert an overwrite-style dimension model to SCD_TYPE_2 so changes are versioned instead of lost on the next run.</td><td><a href="https://v2.dataos.info/build/july2026/recipes/track-dimension-history-with-scd-type-2.md">Track dimension history with SCD Type 2</a></td></tr><tr><td><strong>Mask sensitive columns in a semantic model by role</strong><br>Mask sensitive columns per caller role with an access policy, no forked pipelines or models.</td><td><a href="https://v2.dataos.info/build/july2026/recipes/mask-sensitive-columns-by-role.md">Mask sensitive columns in a semantic model by role</a></td></tr></tbody></table>

When to reach for which:

* Building on top of an existing product instead of rebuilding its logic? Follow [reuse a Data Product](https://v2.dataos.info/build/july2026/recipes/reuse-data-products.md).
* Need a model to run real ML or forecasting logic that SQL can't express? Start with [build a Python model for AI/ML workflows](https://v2.dataos.info/build/july2026/recipes/build-a-python-model.md).
* Clustering or another Spark MLlib workload, with a local fallback? Follow [cluster data with a Spark ML Python model](https://v2.dataos.info/build/july2026/recipes/spark-ml-python-model.md).
* A model runs on schedule before its source data has actually landed? Follow [wait for data to be ready with signals](https://v2.dataos.info/build/july2026/recipes/wait-for-data-with-signals.md).


---

# 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/build/july2026/recipes.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.
