Contextualization Architecture
Design the model before building it.
Define canonical models, mapping rules, identity strategy, lineage, platform responsibilities, and data contracts.
SCOPE
Model, mappings, contracts
BEST FOR
Teams that know integration is required
What's included
Canonical entity model
A small, stable model of entities, events, and relationships, with vocabulary and identity strategy.
Source-to-canonical mappings
Mapping rules plus the event and temporal model.
Platform responsibilities
Edge and cloud split, platform selection or validation, and security boundary assumptions.
Lineage requirements
What must be traceable from every published record back to its sources.
- Entity
- Customer
- Identity
- customer_id (minted), source keys kept as aliases
- Relationships
- childOf → Customer, places → Order, billedBy → Invoice
- Mapping rule
- ERP.KUNNR → alias[erp]; CRM Account.Id → alias[crm]
- Contract
- Published to the warehouse; breaking changes need a version bump
OUTPUT
A canonical model, reference schemas, and a deployment backlog.
Usual next step: Integration PilotsNext step →