
Define revenue, activation, retention, and product measures once, then let Vuon use those definitions whenever someone asks a question.
Capture the business definition
Analysts define the measure, approved dimensions, exclusions, and source tables.
Query it in plain language
Operators ask for the metric in Vuon or Slack without translating the request into SQL.
Inspect the source trail
The answer carries the metric version, SQL, snapshot, and related lineage.
Definition state
Metrics are not prompt snippets. Vuon treats them as durable business objects with formulas, dimensions, filters, owners, and warehouse context.
Every answer can point back to the exact metric definition and snapshot used to produce it.
The surface explains what a metric means in business language before exposing the SQL behind it.
The same metric can power a Slack answer, a report, or a live artifact without rewriting logic.
Definitions change. Vuon keeps history visible so teams can see when a number changed because reality moved, not because the logic silently shifted.
Track edits to formulas, dimensions, and exclusions as part of the analysis record.
Keep metric logic connected to real tables and columns instead of isolated BI metadata.
Metric definitions become executable context for the agent, not passive documentation.
How it works
The same operating rhythm runs through the product: gather trusted context, show the work, then ship an output that can be reviewed.
Analysts define the measure, approved dimensions, exclusions, and source tables.
Operators ask for the metric in Vuon or Slack without translating the request into SQL.
The answer carries the metric version, SQL, snapshot, and related lineage.
Next step