Capital One linking incident: segment-membership sizing and cross-system root-cause attributionCustomer & Account Analytics

Task prompt

Closing out the Capital One linking incident review and I am short on time. I need two things for the writeup: how many of our contacts got caught in that linking issue, and the engineering defect that was the actual root cause of it. The contact data is sitting somewhere in our shared Drive. Reply with exactly one JSON object with two keys: impacted_contacts and root_cause_id.