Developers · Reference architecture
A metadata-driven data mesh, in the open.
A generic, illustrative reference implementation: one governed metadata contract drives the medallion pipelines, the published semantic layer, and warehouse serving — with classification and lineage enforced end to end. Synthetic data only. Free to read, run, and adapt.
View the repositoryExplore
Five ways in — versioned and access-governed.
Model registry
Versioned BDMs, PDMs & semantic models, governed by semver.
OpenData model
Navigate the ERD; watch attributes mask by role in real time.
OpenAPI explorer
A live endpoint — responses filtered per attribute by clearance.
OpenSemantic layer
Query governed metrics; MNPI/PII measures block without clearance.
OpenAccess control
The full role × attribute visibility matrix and the policy model.
OpenData-product catalog
5 products, generated from the contract.
These cards render the reference's own machine-readable catalog — the same descriptors a consumer would discover. Nothing here is hand-written; it is generated from contracts/.
Counterparty
one row per legal counterparty
Currency
one row per ISO 4217 currency
Instrument
one row per tradable instrument
Position
one row per book / instrument / as-of date
Trade
one row per executed trade
The components
Six packages, one source of truth.
Governed metadata spec
The single, versioned source of truth — entities, attributes, relationships, each carrying a classification. Sits on top of the controlled BDM/PDM.
Medallion framework
A declarative registry generates bronze → silver → gold jobs, schedules, lineage, and an ops view. One entry defines a full medallion path.
Semantic publisher
Cube-style semantic models — cubes, measures, dimensions, governed access — generated from the contracts and published as machine-readable contracts.
Warehouse serving
Snowflake-style DDL and serving views generated from the physical model, with classification carried through to masking and access roles.
Governance CI
Gates that enforce classification coverage, registry consistency, and propagation completeness — preventing drift between spec, pipeline, semantic, and warehouse.
Data-product catalog
Machine-readable descriptors for each data product — schema, classification, owner, freshness, lineage — the discoverable face of the mesh.
Governed propagation
A change flows in one direction — and CI proves it arrived.
Edit the contract and the downstream surfaces regenerate. Classification coverage, registry consistency, and propagation completeness are enforced as gates — a change that stops at the contract is incomplete.