100 Charges, Zero AI Logs: Building Cryptographic Account Enforcement and Law Enforcement Referral Provenance with CAP-SRP v1.1

On March 17, 2026, Florida charged a man with 100 counts including 46 for AI-generated CSAM. On February 3, the UK ICO opened a formal investigation into Grok's generation of non-consensual imagery. In both cases, the question no one could answer was the same: what did the AI system actually refuse, and can anyone prove it? This article walks you through building the answer — with full working Python code for CAP-SRP v1.1's three new event types. TL;DR A Florida prosecution, a UK regulatory investigation, and an EU compliance deadline all converged on the same structural gap: AI providers can claim their safety systems work, but no one can independently verify it. The previous version of CAP-SRP (v1.0) addressed generation-level refusal logging. Version 1.1, released March 5, 2026, extends the framework upstream — to account enforcement, law enforcement referral decisions, and tamper-evident policy versioning. This article: Fact-checks the five events that motivated v1.1's design Expla