Models
SQL that runs on a schedule and lands as a table, with tests. Export it all as a dbt project any time.
A model is a SQL file with {{ ref('other_model') }} in it, run in dependency order, stored as a table, a view, or an incremental table that only processes rows past a cursor. A test is a query that must return zero rows. It's dbt-shaped on purpose: a company that outgrows this can run real dbt on the same files.
Where they come from
You write them, your agent writes them, or the analyst keeps one: a clean table from a query worth keeping shows up under Models with a description, and you can edit or delete it. Nightly, the same calculation found in two places becomes a card; approve it and it's one definition.
Lineage
The Data screen draws the graph: sources, models, dashboards, and what depends on what. Click a node and see the SQL, the tests and who touched it.
Commands
ovs models ovs run sales # every model in the dish, in order ovs test sales ovs export # the lot as a dbt project (zip)