Skip to content
Platform · Reference Data

Reference data sets & versions

This capability is arriving. Country codes, currencies, industry classifications, and your own code sets become versioned, stewarded reference sets, so every consumer reads the same values on the same date.

What you get01 / 03
01

Versioned reference sets with named stewards and effective dates.

02

Standard sets arrive maintained, and your internal sets live under the same lifecycle.

03

Every consumer sees which version it read, so reconciliation stops guessing.

How it works02 / 03
1

Curate

Stewards review incoming changes to a set and approve a new version through the decision door.

2

Publish

Consumers subscribe to sets, and the graph records who received which version when.

Questions it answers03 / 03

“Which standard sets ship maintained?”

Common international code sets ship first, with the update cadence published, and your internal sets join the same lifecycle from day one.

“When does this arrive?”

Behind the core proof work, with the design public first.

The next step

Start with proof, not a promise.

There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.

01

A 60-minute working session

Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.

02

A two-week guided sandbox

Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.

03

A six-week proof on your systems

We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.