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

# Outputs

Outputs are the curated datasets a product publishes: the governed tables and views used by semantic models, BI tools, applications, APIs, and downstream pipelines. In `Orders Analytics Platform`, `CUSTOMERS` is generated customer master data with signup date and regional assignment, built from source inputs and reference data.

Open **Assets**, expand **Outputs**, and click an output. The detail view shows the name and layer, a description, a summary row with **Kind**, **Last run**, and **Schedule**, **View lineage**, and the **Columns**, **Dependencies**, and (when a policy applies) **Policies** tabs.

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

## What to review

<table><thead><tr><th width="199.4603271484375">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>Last run / Schedule</td><td>Whether the data is fresh, and how current it stays</td></tr><tr><td>Columns</td><td>Fields you can consume, with Tags and Quality</td></tr><tr><td>Dependencies</td><td>Where the output is already reused, so you can reuse it with confidence</td></tr></tbody></table>

Open the info (**i**) icon for glossary terms, owner, and tags. The **Dependencies** tab shows where the output is reused; in the example, `CUSTOMERS` feeds `SALES_FUNNEL_ANALYSIS`, `DIM_CUSTOMER_PROFILE`, and `FCT_DAILY_SALES`. Select **View lineage** for the full graph with the output as the base node.

Next: [Semantics](/consume/v1/evaluate/assets/semantics.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/v1/evaluate/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.