Crosswalks And Identity

Summary

Crosswalks connect provider-specific identities to stable internal concepts so downstream workflows can reason about people, vendors, customers, jobs, and prospects consistently.

Problem

Provider IDs are not enough. The same business object may appear in multiple systems, and each system may use different keys, naming, or lifecycle states.

Principle

Represent identity resolution explicitly. Build crosswalks as data products and surface ambiguity instead of hiding matching policy inside each consumer.

Platform Shape

The lakehouse docs describe technician and vendor crosswalk jobs and silver canonical layers. Crosswalk jobs such as technician_xwalk_build and vendor_xwalk_build are execution wrappers over reusable lakehouse logic.

Source Evidence

• docs/domains/lakehouse.md
• jobs/lakehouse/technician_xwalk_build/run.py
• jobs/lakehouse/vendor_xwalk_build/run.py
• pipelines/lakehouse/transform/silver

Related Reading

• docs/engineering/concepts/canonical-entities.md
• docs/engineering/concepts/failures-are-data.md