Rules, streams, glossary, and enrichers

On this page

• Learning objective
• Working model
• Exercises
• Support surfaces to revisit
• Completion signal

This module turns recurring data issues into architecture work.

Learning objective

Decide when a repeated stewardship problem should become a design, rule, stream, glossary, or enricher change.

Working model

• Steward discovers the pattern.
• Architect decides whether the pattern should be prevented by design.
• The product surface is chosen intentionally: mapping, vocabulary, validation design, rule, stream, glossary, or enricher.

Exercises

Classify each recurring problem into the most appropriate architecture surface:

1. Duplicate-looking people caused by weak identifiers.
2. Frequent missing values from one source system.
3. Reusable subset logic that many users need to apply.
4. A recurring downstream action that should happen automatically.

Support surfaces to revisit

• Filters
• Validations
• Vocabulary

Completion signal

The learner can explain why not every quality problem should be solved manually by a steward.