Six analytically notable features. (1) Third-party proxy reporter — first in the dataset. @MasonVersluis is not the affected account holder; he is the account holder's husband reporting on his wife's (@megbzk) enforcement action. All prior records in the dataset were filed by the account holder directly. This introduces a new source type: proxy/family reporter. The proxy context affects the record in two ways: (a) the reporter's knowledge of the enforcement details is secondhand, though the enforcement notice screenshot is direct evidence; (b) the emotional framing ('emotional turmoil, income loss, and psychological damage') reflects family-unit harm rather than only individual harm. The livelihood dimension is explicit: 'My wife makes a living through her Instagram account and this has directly resulted in income, and sponsorship loss.' See also @MasonVersluis's escalation targets: @Meta @instagram @AIatMeta @andymstone — tagging Meta's own AI infrastructure account and the Director of Policy Communications by name, indicating awareness of both the exploit discourse and the public acknowledgment record. (2) Meta AI exploit attribution — fifth case in dataset. Reporter explicitly states: 'My wife and Jett's Instagram accounts BOTH were victims of the recent Meta AI exploit.' This is explicit public-discourse attribution to the credential-manipulation mechanism confirmed by TechCrunch on June 1, 2026 and acknowledged by Andy Stone. Unlike the first four cluster members (PA-2026-0024, -0032, -0033, -0036), who reported before public confirmation, PA-2026-0046 is filed after Andy Stone's June 1 and June 3 public statements — meaning the reporter is using the public-discourse framing. The mechanism description is consistent with the confirmed pattern (Meta AI exploit → credential compromise → disable without appeal), and the 'fix claimed but documented as incomplete' note in [[finding___meta-ai-credential-exploit]] is relevant: PA-2026-0046 may represent a post-patch disable that occurred before the fix or a case where the claimed fix did not extend to the cascade. See [[finding___meta-ai-credential-exploit]]. (3) Meta Verified failure — both accounts. Reporter explicitly states: 'These were both innocent PAYING Meta Verified subscriber accounts.' This is the ninth record in the dataset documenting Meta Verified failure in an enforcement context. Both affected accounts were Verified — extending the pattern across two simultaneously affected accounts in the same household. See [[finding___meta-verified-false-assurance]]. (4) Cross-platform enforcement inconsistency — first explicit argument in dataset. Reporter states: 'Facebook account AND Threads are STILL up with the exact same content on them, proving that there was NOTHING wrong with the content being posted and it was a completely WRONGFUL ban.' This is the clearest cross-platform inconsistency argument in the dataset: the same content that triggered Instagram enforcement is simultaneously live on Meta's own Facebook and Threads platforms without enforcement action. This is not an inference from the curator — it is the reporter's direct analytical argument. If accurate, it establishes that Meta's Instagram enforcement system flagged content that Meta's own Facebook and Threads systems evaluated and did not flag — an internal inconsistency across the same corporate infrastructure. This warrants a dedicated finding. See [[finding___cross-platform-enforcement-inconsistency]]. (5) Bare 'Community Standards' citation — no specific policy. The enforcement notice reads: 'Your account, or activity on it, doesn't follow our Community Standards.' No sub-policy, no behavior identified, no actionable basis for appeal. Consistent with the opacity pattern documented across the dataset. See [[finding___enforcement-notice-policy-opacity]]. (6) Terminal disable — ninth in dataset. 'You cannot request another review of this decision.' Extends the terminal-close cluster. Two accounts affected (@megbzk confirmed from enforcement screenshot; @Jettman17 mentioned by reporter without separate enforcement notice in available screenshots). Date uncertain: reporter states 'WEEKS' of attempted human support contact at time of posting (~June 9, 2026). Date recorded as approximate 2026-05-26; actual enforcement date may differ by several days in either direction.