Business ownership, implemented as reviewable artifacts.
Each role below maps to concrete artifacts: declared definitions with owners, observed schemas, implementation mappings and native semantic outputs — every change a reviewed diff, executed in your platform.
Detail by role
Schemas, mappings and native output.
Engineers observe the physical schema, connect business definitions to it, refine the model and deploy native semantic views — then maintain them as definitions and schemas change.
From your definition to your platform
From business meaning to platform execution
Defined by the business
Net revenue
= gross revenue − discounts − credits
- Owner
- Finance
- Used for
- Quarterly reporting
Model, mappings and native output
Your business meaning, ready for AI
One agreed definition with an owner, a time grain and the words people use to ask for it.
Choose your platform
Your platform executes the calculation. Pick one; you don't need both.
Answer in Cortex Analyst
Net revenue grew 5.4% from Q2 to Q3.
Definition used: net revenue = gross revenue − discounts − credits (owner: Finance), served through Semantic Views.
Fictional example
Start a free pilot
We work through one business question with you: agree its meaning, map it to the relevant data and review how it works on Snowflake or Databricks. We agree the scope together before we start.
- 01One business question
- 02One owner of the definition
- 03The data it depends on
- 04A review on your platform
- Start a free pilotWatch demo