Enterprise Metadata Management System  ·  View 09 of 22  ·  Data

Metadata Flow and Precedence

The path from capture to activation, and the rule applied when two systems disagree.

Editable source SVG draw.io All views
Capture
Capture
Scheduled harvest
hourly incremental
Scheduled harvest...
Event push
webhook · CDC
Event push...
Manual & bulk
UI · CSV · API
Manual & bulk...
Normalise
Normalise
Source adapter
Source adapter
Canonical mapper
to URN + aspects
Canonical mapper...
Schema valid?
aspect registry
Schema valid?...
Dead letter
quarantine
Dead letter...
Enrich
Enrich
Profiler
sampled stats
Profiler...
PII classifier
rules + ML
PII classifier...
Term suggester
advisory only
Term suggester...
Drift detector
diff vs last
Drift detector...
Resolve
Resolve
Precedence engine
curated wins
Precedence engine...
Conflict
two sources disagree
Conflict...
Stewardship task
routed by domain
Stewardship task...
Commit
Commit
Aspect Store
version + 1
Aspect Store...
Change log
Kafka MCL
Change log...
Audit Log
who · what · before
Audit Log...
Activate
Activate
Knowledge Graph
Knowledge Graph
Search Index
Search Index
Policy Sync
labels outbound
Policy Sync...
Notify owners
Teams · email
Notify owners...
reject
reject
unresolved
unresolved
raise
raise
Metadata Flow — Capture to Activation
Metadata Flow — Capture to Activation
Interface / broker
Interface / broker
Queue / topic
Queue / topic
Application we own
Application we own
Decision point
Decision point
Risk / gap
Risk / gap
Data store
Data store
Security / platform
Security / platform
failure / alternate
failure / alternate
synchronous
synchronous
Precedence: certified curation > curation > source-declared > inferred. Inference never overwrites a human value; it only proposes.
Precedence: certified curation > curation > source-declared > inferred. Inference never overwrites a human value; it only proposes.
v 1.0 · owner Data Architecture · date 2026-08
v 1.0 · owner Data Architecture · date 2026-08
Text is not SVG - cannot display

The precedence ladder

  • Certified curation beats curation, curation beats source-declared, source-declared beats inferred.
  • Inference never overwrites a human value. A classifier that disagrees with a steward raises a suggestion, not a change.
  • When two sources disagree at the same rank, both values are retained as evidence and a stewardship task is raised. Silent last-writer-wins is how a catalog quietly becomes wrong.

Ingestion modes

  • Scheduled full harvest weekly, incremental hourly, event-driven within 5 minutes for sources that can push.
  • Batch and incremental share one code path; the watermark is the only difference, so incremental cannot drift from full.

Failure handling

  • A payload that fails aspect-schema validation is quarantined with the raw evidence retained, never silently dropped.
  • Dead-letter volume is an alert, not a dashboard: it means a source changed shape (view 18).