Roundup
The promise for each relation now lives in the repository
A data contract is now a canonical artifact in the Domain repository, one list holds personal and install-provided connections, and teams in the Design partner open band can run Databricks notebooks and jobs from the agent.
This week the promise for each relation became a canonical artifact in the Domain repository, and two more changes shorten the work around it.
What got easier
Read the contract that states the promise for a relation. A data contract is now a canonical artifact in the Domain repository, beside the logical model and ontology. It states the promise for one relation: grain, properties and types, keys, relationships, quality rules and the platform that serves it. The semantic model now builds from the Domain's Ossie logical model, so the meaning lives in one place and the contract carries the promise to the consumer. Each semantic model asset carries its columns and metrics from that logical model. The domain CI bundle now includes the data-contract gates, so the contract is checked in the same build as the model.
Try it: in your Domain repository, read a data contract beside its logical model and ontology.
The same team ships more with Vibedata: less time to PR and less time per PR, once the team changes what it focuses on and how it builds. Review compounds, so each accepted change shrinks the next review.
More things that make your week easier
One Data platforms list shows the connections you sign in to and the ones your install provides. The Connections inventory now covers both in one list, with a detail URL you can reload or share. One table serves both, so you no longer check two places. The old Domain resources URL redirects.
Design partner open: Databricks notebooks and jobs from the agent. For teams in the Design partner open band, the Databricks CLI is now in the agent's environment, and the OAuth contract asks for the jobs and workspace scopes, so a notebook or job can run and its output can come back to the conversation. The scopes are the ones the Jobs and Workspace APIs need. The CLI is pinned and its artifact is verified before use. Register both scopes and reconnect Databricks before the first run.
Try it yourself
Build governed metrics in the canonical semantic model. The recipe rebuilds selected BI calculations as governed metrics in the canonical semantic model, so one definition serves every consumer instead of one per dashboard. It is the practical half of this week's semantic model change: define the metric once, then let the model carry it.
Where data engineering is heading
A data contract states the whole promise for a relation. The post explains why a contract is not the same as a set of tests, and what the contract boundary covers. It argues that the contract is the published boundary for a relation, and it is the argument behind this week's lead.
New to Vibedata?
Start in the hosted sandbox, or install from your cloud marketplace.
Get the weekly roundup by email
One email a week: what got easier in Vibedata, a recipe to try yourself, and where data engineering is heading.
Or follow the RSS feed.
