Skip to main content
Trust in Zwiron evaluates data after it has moved and been inventoried. Detect runs quality checks against Catalog assets. Trust gate policy (in Settings) decides whether gated failures warn or block. Trust incidents give operators a durable work queue to assign, investigate, cleanse, resolve, or hand off to Match.
Trust is separate from Match. Use Data Quality to define tests, Trust → Incidents to triage failures, and Match when the remediation is entity resolution (duplicates).
The following articles help you operate Trust:

Where Trust sits

Typical sequence:
  1. Data lands via a Job and assets exist in Catalog.
  2. Detect evaluates quality rules (on demand, scheduled, or after Match write-back).
  3. Gate policy applies: Warn or Block (see Trust gate policy).
  4. Incidents open for operator triage.
  5. Remediation (cleanse, fix data, adjust tests, or Match) then re-detect / re-certify.

Building blocks


Certification signals

Catalog assets can show quality / certification signals after Trust detect runs. In practice: Certification is not a separate product module — it is the Catalog view of Trust outcomes. Always triage from Trust → Incidents and confirm tests under Trust → Data Quality.
Sidebar under Trust: Incidents, Data Quality.
Last modified on October 10, 2026