Docs Master data

Data model

Domains, objects, attribute groups, keys, the cross-reference, hierarchies and calendars, and the SQL surface.

All master-data docs Request access to the full tier

Overview Data model Golden-record API Match and survivorship Hierarchies API Data services Rules language Security and roles Audit and history Pivots and measures API Quality agents and packs

Domains and objects

A domain is a model: attribute groups, keys, hierarchies, rules, security and the objects it reads per system. The catalogue's thirty domains ship as templates; a new domain follows the same structure.

domainid, name, group, attribute groups, keys, hierarchies, rules, systems

attribute groupname, attributes, survivorship rule per attribute

attributename, type, unit or currency, sensitivity tag, list binding

keyattributes, method (exact, standardised, fuzzy, model), weight

objectsystem, table or resource, fields, freshness contract, write interface

SQL surface

golden.customer            -- one row per golden customer; AS OF supported
golden.customer_xref       -- golden_id, system, source_key, valid_from, valid_to
golden.customer_history    -- every version with who, why, rule
hier.customer_sales        -- version, node, parent, level, valid_from, valid_to
hier.customer_sales_leaf   -- version, node, golden_id
cal.fiscal · cal.planning  -- day → period, week
bed.sales_order_line       -- transactions read in place or from the replica; customer_source_key resolves through xref

Cross-reference

The cross-reference is a table per domain with one row per source key, kept as a join; a merge adds rows under the surviving golden id with a valid_from; an unmerge closes them. Consumers that keep local keys join on it.