nw-shared-artifact-tracking

Shared artifact tracking identifies data values appearing in multiple journey steps and centralizes their definitions in an artifact registry schema. This ensures a single source of truth and documented consumers, preventing horizontal integration failures caused by untracked variables.

Integration validation for shared artifacts works by applying validation checks that verify artifact sources exist and consumers correctly reference them. This ensures consistency by confirming every shared variable in the journey design points back to a defined source of truth.

Governance patterns for shared artifacts establish standardized definitions for common values like versions, install paths, repository URLs, configuration values, and command names. This enforces a single source of truth and clear ownership across journey integration scenarios.

Yes, an artifact registry schema is required before tracking shared journey data. You must define the schema with clear owners, specified sources of truth, listed consumers, and defined validation checks to verify sources and consumers across steps.

Untracked shared artifacts cause horizontal integration failures because data values appearing in multiple journey steps lack a single source of truth and documented consumers. When variables are not centralized in an artifact registry, integration validation cannot verify consistency across steps.