Build the initial rule set and processing logic

Learning outcome

Create the first set of architect-owned rules that establish durable processing behavior for the domain without taking on day-to-day data cleaning.

Scenario

The ingestion and mapping pipeline is working, but the domain still needs repeatable business logic before it is ready for operational stewardship. Your task is to establish the initial rule set that should apply consistently to the modeled data.

Read

Exercise

  1. Identify one repeatable transformation or survivorship requirement that belongs in the platform architecture rather than in manual stewardship.
  2. Define the records and properties affected by the rule.
  3. Create the rule and document why this logic belongs in a durable rule rather than in a one-off correction.
  4. Process or reprocess a representative sample in a non-production environment.
  5. Inspect the resulting golden records and confirm that the rule produces the intended behavior.
  6. Record the rule order, dependencies, rollback or disablement approach, and any conditions that should instead be escalated back to the source system.

Do not use a Clean project as the solution in this module. Data Architects establish durable processing logic; Data Stewards perform operational cleaning when records need case-by-case or remediation-oriented work.

Deliverable

An initial rule specification containing purpose, scope, rule type, order, dependencies, validation evidence, and rollback approach.

Complete when

  • The rule addresses a repeatable architectural requirement.
  • Its effect is verified on actual golden records.
  • The design does not shift operational cleaning into the Architect role.

Next

Continue to Build matching projects and hand review to stewards.