Capabilities

Five connected capabilities. The buyer is not purchasing MDM software or a marketplace — they are escaping fragmented databases, weak ownership, inconsistent identifiers, manual approvals, data unsafe for AI, no knowledge of prior-date truth, and no trusted path from data to action.

1. Trusted enterprise data foundation

The integrity layer: ingestion, contracts, matching, survivorship, golden records, bitemporal reconstruction, quality, lineage and publication reconciliation.

2. Governed product consumption

The consumption and governance layer: discovery, Trust Labels, ownership, access requests, entitlement packages, persona shelves, and reports, datasets, APIs and event feeds.

3. AI-ready interaction

The intelligence layer: governed analytics, discovery and access assistance, evidence and rationale for stewards, operational summaries, a shared contextual panel, and MCP tools for governed actions.

The demonstrative moment is this layer standing on the first one — asking the system what changed, which source is authoritative, what the company knew at a prior date, and which downstream products are affected.

4. Activation and distribution

The action layer: APIs, open sharing, events, CRM writeback, distribution reconciliation and idempotent publication.

5. Enterprise operating controls

The operating layer: cost controls, quotas, AI policy, role simulation, audit, recovery, preview disclosure, a status register, and CI and deployment evidence.

Open standards at the boundaries

Mainstream, transferable tooling at every boundary, so no business logic binds to a vendor API:

• Kafka protocol — events
• Postgres wire protocol — operational transactions
• Delta as the implementation format, with Iceberg REST as the table interoperability surface
• SQL — warehouse
• MCP — agents
• OpenTelemetry — observability
• Open sharing — external governed distribution
• HTTP/JSON with OpenAPI — governed APIs

Accessibility

WCAG 2.2 AA is the accessibility floor, operationalised rather than intended: automated accessibility checks run in CI, and no information is conveyed by colour alone. The temporal pair is the standing example — effective time carries a solid line, an Effective label and a calendar glyph; knowledge time carries a dashed line, a Known label and a history glyph.

Design tokens

Design values ship as CSS custom properties, so a client estate can re-theme without a rebuild. This site and the portal read the same token file.

Deployment