The institutional knowledge agents build on.

The Context Graph grounds every action in your organization's standards — including the tribal knowledge that rarely makes it into documentation. Encode it once; every pipeline inherits it by default.

What it captures

A living map of how your data actually works.

// standards

Conventions

Naming, modeling patterns, architecture preferences — applied to everything Blunox builds.

// semantics

Business entities

Semantic definitions and metric logic, mapped to the physical tables behind them.

// contracts

Data contracts

Schemas, SLAs, and ownership — enforced so changes never silently break consumers.

// policy

Compliance rules

Security classifications and governance policies the agents must respect on every run.

// lineage

Lineage

A complete map of data flows and dependencies, kept current as pipelines evolve.

// metadata

Metadata

Discoverable across your estate — query assets, lineage, and dependencies directly.

Why it matters

Less brute force, more judgment.

Instead of guessing at ambiguous schemas, Blunox understands your estate and builds efficiently. New engineers onboard to your standards in hours, and agent outputs inherit those standards automatically.

Onboard new standards once — applied everywhere after
Consistency and governance across all data products
Grounded decisions, fewer hallucinated assumptions
context_graph · query
orders
customers
customer
entity
LTV metric
churn model
12 contracts · 48 entities
· 1,204 assets mapped

Encode it once.

See how the Context Graph grounds every pipeline Blunox builds.