Data Workers Data Context Wizard

The Data Workers Data Context Wizard is the semantic and knowledge graph for your data platforms — the governed, federated context graph an enterprise’s data agents read, reason over, and write back to, so they stop answering confidently and wrong.

Tagline, and the actual design goal: context your agents can trust.

Why a context graph, not another catalog

A catalog is where you put context — and it goes stale between crawls. The Context Wizard is the layer a governed fleet keeps alive: agents harvest context from the systems you connect, write back what they learn under governance, and every fact carries provenance and confidence. One agent can edit a graph; a governed fleet can compound one — that’s the difference.

Three things make the write-back safe enough to trust:

Provenance and confidence on every fact. Nothing enters the graph anonymous.
Governed promotion. A fact only becomes authoritative when a named human approves it — promotion is a gate, not a default.
Isolation and audit. Tenant-scoped, with hash-chained audit on governed writes.

The graph is federated

The Context Wizard reads across the platforms you already run — warehouses, catalogs, dbt, lineage systems — through the same connector set as the rest of the platform, rather than requiring your estate to move into one vendor’s catalog first.

What’s included

Every plan (pilot, Scale, Enterprise): the context graph the agents read and write back to under governance, and the authoring surface — your team curates definitions, business rules, and ownership in the browser, runs the promotion workflow, and manages the graph’s warmth.
Enterprise adds: compliance export of the graph and audit chain, inside your deployment boundary.

Getting started

The graph starts cold and warms in phases — harvest, reconcile, curate, promote. The practical guide, including what’s automated versus what only you can provide, is Warming up your knowledge graph.

Two honest notes before you start: