> 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/understand/assets/outputs.md).

# Outputs

Outputs are the curated datasets a data product publishes. They're the governed tables or views used by semantic models, BI tools, applications, APIs, and other downstream pipelines.

In `Orders Analytics Platform`, outputs include datasets like `CUSTOMERS`: generated customer master data with signup date and regional assignment, built from source inputs and reference data.

## Open an output

From the data product page, open **Assets**, expand **Outputs**, and click an output dataset.

The detail view shows the output name and layer, a description, a summary row with **Kind**, **Last run**, and **Schedule**, a **View lineage** link, and the **Columns** and **Dependencies** tabs.

![Output detail showing kind, last run, schedule, and the columns tab](/files/nUknuAMf8pLlp2NZEjTC)

## What to review

<table><thead><tr><th width="162.51446533203125">Area</th><th>Why it matters</th></tr></thead><tbody><tr><td>Description</td><td>What the dataset is for. Decides whether it fits your use case.</td></tr><tr><td>Kind</td><td>How the output is refreshed or materialized.</td></tr><tr><td>Last run</td><td>Whether the data is fresh and the last run succeeded.</td></tr><tr><td>Schedule</td><td>How current the data stays, based on refresh frequency.</td></tr><tr><td>Columns</td><td>Fields you can consume, with Tags and Quality confirming meaning and reliability.</td></tr><tr><td>Dependencies</td><td>Where the output is already reused. Lets you reuse it with confidence.</td></tr></tbody></table>

## Columns

Use the columns list to confirm the output has the fields you need. Descriptions and tags clarify meaning and purpose.

## Output metadata

To check business meaning and find who owns the output, open the metadata popover with the info (**i**) icon. It shows **Glossary terms**, **Owner**, and **Tags**.

![Output metadata popover showing glossary terms, owner, and tags](/files/CtKKMySs1uHCen5Cga6h)

## Dependencies

Open the **Dependencies** tab to see where the output is reused. In the example, `CUSTOMERS` feeds `SALES_FUNNEL_ANALYSIS`, `DIM_CUSTOMER_PROFILE`, and `FCT_DAILY_SALES`.

![Output dependencies tab showing upstream and downstream models](/files/GnyI6GsHaffbjq0Ihqmp)

## Lineage

Click **View lineage** to open the full dependency graph. The output is the base node; downstream models fan out across the graph.

![Full-screen lineage view for the output](/files/FKF0NDE1FFDZ3WJajMQd)


---

# 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/understand/assets/outputs.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.