Enterprise Metadata Management System  ·  View 19 of 22  ·  Operations

The Active Metadata Loop

The cycle that has to close for this to be a governance platform rather than a search index.

Editable source SVG draw.io All views
Harvest
200 systems
Harvest...
Enrich
classify · profile
Enrich...
Curate
steward · glossary
Curate...
Certify
domain owner
Certify...
Activate
push to enforcement
Activate...
Observe
usage · quality · gaps
Observe...
Active Metadata
Active Metadata
raw technical metadata
raw technical metadata
candidate labels
candidate labels
approved definitions
approved definitions
trusted asset
trusted asset
policy applied at source
policy applied at source
gaps become tasks
gaps become tasks
The Active Metadata Loop
The Active Metadata Loop
Interface / broker
Interface / broker
Application we own
Application we own
Security / platform
Security / platform
If the loop stops at Curate the system is a catalog. Activate and Observe are what make it a hub.
If the loop stops at Curate the system is a catalog. Activate and Observe are what make it a hub.
v 1.0 · owner Data & AI Architecture · date 2026-08
v 1.0 · owner Data & AI Architecture · date 2026-08
Text is not SVG - cannot display

Why the loop is the architecture

  • Harvest and enrich are automatable and cheap. Curate and certify are human and expensive. Activate and observe are what repay them.
  • If the loop stops at Curate, the platform is a catalog: a place where descriptions are written and nothing changes downstream.
  • Activation is what makes stewardship worth doing — a label a steward applies here becomes a masking policy at the source within minutes.

Closing evidence

  • Observe feeds gaps back as tasks, so the loop generates its own next iteration rather than needing a campaign to restart it.
  • Certification expiry ensures the loop runs at least annually per asset even when nothing changes.

Risk

  • Activation writes to systems that enforce access. A wrong label propagates into a real access decision, which is why classification changes are authorised, versioned and audited (view 21).