End-to-end governance scenarios

These implementation patterns are not built-in automated workflows. Confirm licenses, roles, scope, and approvals. Preserve stable system, schema, table, field, and metric identifiers across modules.

Customer data governance

Make customer data discoverable, understandable, testable, cataloged, and requestable.

Stage	Owners	Actions and evidence
Inventory	Metadata administrator, steward	Register sources, harvest, sample tables, fields, dependencies
Standardize	Standards administrator, business owner	Define customer IDs, names, and status standards; publish and map
Validate	Quality administrator, issue owner	Check uniqueness, completeness, and reference values through tasks and verification
Publish	Asset administrator, data owner	Register and publish in a customer catalog; test visibility
Consume	Consumer, approver, delivery team	Request through marketplace, approve, deliver offline, accept

Accept when sources and definitions are confirmed, key issues have verification outcomes, ownership and visibility are correct, and request, approval, delivery, and acceptance correspond.

Sensitive data governance

Identify sensitive fields, publish reviewed classifications, and verify actual access and audit.

Stage	Owners	Actions and evidence
Scope	Owner, security administrator	Select harvested objects and record policy/legal basis
Discover	Security administrator, steward	Design classification, run discovery or collaborative review
Review	Security reviewer	Check evidence, correct false positives, publish in workbench
Control	Security/gateway administrators	Define policies, configure server and JDBC
Verify	Consumer, auditor	Test allowed and restricted identities and audit

Accept evidence-based decisions, explicit identities, objects, and purposes, expected results, and matching user/time/object audit records. Classification publication does not prove enforcement.

Metric governance

Align definitions, calculations, dimensions, sources, quality, and delivery.

Stage	Owners	Actions and evidence
Define	Metric owner, standards administrator	Publish name, definition, algorithm, owner, and dimensions in metric standards
Model	Metric administrator, engineer	Use Metric Management for atomic/calculated/qualified metrics; see DDM documentation (Chinese) for modeling
Associate	Steward, metadata administrator	Verify tables, fields, lineage, and change impacts
Validate	Quality administrator	Check completeness, timeliness, range, and dimensions
Deliver	Asset/service administrator	Publish assets or APIs; verify visibility, authorization, and results

Accept consistent definitions, formulas, dimensions, sources, publication, mappings, executed checks, and approved value granularity and periods. A definition alone does not produce queryable data.

Handoff requirements

Record IDs, owner, state, evidence, and open items. A module's success does not replace downstream acceptance. After source, standard, or permission changes, return to the relevant journey stage.