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

# Seeds

Seeds are static reference datasets in a product: lookup values, mappings, tiers, codes, labels. In `Orders Analytics Platform`, `ORDER_STATUS_LOOKUP` classifies order statuses for the analytics models.

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

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

## What to review

<table><thead><tr><th width="186.0552978515625">Area</th><th>Why it matters</th></tr></thead><tbody><tr><td>Description</td><td>What the seed represents and how it is used</td></tr><tr><td>Last run / Schedule</td><td>When the reference values were last refreshed, and how often</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 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`. Use the **Quality** column filter (**Passed**, **Issues**, **Not evaluated**) to spot values you can trust, and the info (**i**) icon to see glossary terms, owner, and tags.

Open the **Dependencies** tab for linked upstream and downstream models, or **View lineage** for the full dependency graph with the seed as the base node.

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