Opaque terminal enforcement: Facebook issued a permanent disable with no policy citation and no remaining appeal path. The "no further appeal" language is boilerplate on Facebook permanent disables and does not constitute evidence of automated execution — it documents lifecycle state, not the nature of the decision. DETECTION is the appropriate value absent timestamped or mechanism-specific evidence of automated review. Over-enforcement victim framing: reporter states she was speaking out against antisemitism and that accounts that sent her death threats remain active, claiming asymmetric enforcement. Explicitly in scope under the political extremism exclusion carve-out (over-enforcement victim, not the extremist). The asymmetric enforcement claim cannot be independently verified but is analytically significant as a reporter-framed pattern. Reporter location: New Zealand (X "About this account" — account registered in New Zealand, connected via New Zealand Android App). X verification obtained May 2026 (paid tier, recent, not legacy identity-linked). Reported trigger mechanism: coordinated mass reporting — reporter describes "an army of antisemitic people reporting" her account. AI role is likely in processing/actioning report volume (classification or threshold-based actioning) rather than initiating detection autonomously. Staged enforcement likely: reporter uses the word "restrictions" in the LinkedIn post, suggesting enforcement may have been staged — restrictions first, then permanent disable after a failed review. This is consistent with Facebook's known graduated enforcement flow. LinkedIn post by @YifatGoddard (https://www.linkedin.com/posts/yifat-goddard-b090aa2b0_meta-antisemitism-hate-activity-7467377210241384448-DcpE) independently corroborates the Facebook enforcement action on a second platform — this is incident corroboration, not merely identity corroboration. Score 5 is unambiguous: enforcement notification screenshot + independent LinkedIn incident post. Consistent with [[finding___policy-citation-vagueness-and-inconsistency]] and [[finding___appeal-access-failure-patterns]].