Components

Components connect repeated barrier occurrences to the shared UI source that can resolve them. A component detail shows ownership, versions, affected experiences, occurrence blast radius, remediation status, and recurrence.

Component identity may come from Storybook imports, source metadata, semantic fingerprints, or confirmed human links. Automated matching proposes likely relationships; uncertain merges require review.

Use component scope to prioritize a shared fix, then verify representative affected checkpoints. Component status does not automatically close barriers: each affected occurrence still needs attributable post-remediation evidence.