> 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/consume/activate/overview-1.md).

# Reusability

When multiple Data Products already exist for related use cases but none fully addresses a new requirement, you do not need to start from raw data. An existing published Data Product can become the upstream input for a new one.

This pattern avoids duplication: a platform product provides curated, governed, and trusted output, and a downstream product inherits and extends it to satisfy a specific use case.

## Why this matters

Data Products are designed to be composable. When one team has already built and published a reliable product, cleaned data, quality-checked models, a semantic layer, and metrics, another team should be able to build on top of it rather than recreate it.

Without this pattern, teams independently ingest the same sources, write the same transformation logic, and maintain duplicate quality rules. With it, the shared foundation is owned once and reused safely by anyone who needs it.

## Next steps

Ready to build? Follow the step-by-step guide in the Build section: [Reuse Data Products](/build/cookbook/downstream-data-droduct.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 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/consume/activate/overview-1.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.