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

# Seeds

Seeds are static reference datasets included in a data product. They usually hold lookup values, mappings, tiers, codes, labels, or other controlled values used to enrich source data.

In `Orders Analytics Platform`, `ORDER_STATUS_LOOKUP` is a static lookup table for order status classification, used by the order analytics models.

## Open a seed

From the data product page, open **Assets**, expand **Seeds** in the left navigation, and click a seed.

The detail view shows the seed name and layer, a description, a summary row with **Kind**, **Last run**, and **Schedule**, plus the **Columns** and **Dependencies** tabs.

![Seed detail showing kind, schedule, and the columns tab](/files/p2zGoAiZ46hpjf7D5WoK)

## What to review

<table><thead><tr><th width="157.56048583984375">Area</th><th>Why it matters</th></tr></thead><tbody><tr><td>Description</td><td>What the seed represents and how it's used.</td></tr><tr><td>Kind</td><td>Confirms the asset is a seed of static reference data.</td></tr><tr><td>Last run</td><td>When the reference values were last refreshed.</td></tr><tr><td>Schedule</td><td>How often they're refreshed.</td></tr><tr><td>Columns</td><td>Lookup values you can join against, with Tags and Quality.</td></tr><tr><td>Dependencies</td><td>Which models rely on the seed, so you can see where the values land.</td></tr></tbody></table>

In `ORDER_STATUS_LOOKUP`, the **Columns** tab lists `order_status` (primary key), `status_group`, `is_fulfilled`, `is_active_sort`, and `description`.

## Seed metadata

To check what the reference values mean and who maintains them, open the metadata popover with the info (**i**) icon. It shows **Glossary terms**, **Owner**, and **Tags**.

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

## Filter columns

To quickly spot reference values you can trust, use the **Quality** column filter to narrow by **Passed**, **Issues**, or **Not evaluated**.

![Quality filter on the seed columns showing Passed, Issues, and Not evaluated](/files/o97oe2CzSEtbN9f3HN19)

## Dependencies

Open the **Dependencies** tab for upstream and downstream models linked to the seed. If there are none, the tab shows *No upstream or downstream models linked.*

![Seed dependencies tab showing no linked upstream or downstream models](/files/ZvMJ32AoVFIaUbr2RER4)

## Lineage

Click **View lineage** to open the full dependency graph. The seed is the base node, with its columns listed inside.

![Full-screen lineage view for the seed](/files/LYKVtdztdmVfBleIQ0OF)


---

# 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/seeds.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.