Patterns: replace 'On-chain → API bridge' with sanctions screening

The Twilio/OpenAI bridge was a generic example. Sanctions screening
on token transfers is a concrete pain point developers actually have:
the Lit Action holds the signing authority and checks each recipient
against a sanctions list inside the TEE before signing, so flagged
wallets simply can't receive.

Author: glitch003

src/components/LandingHowItWorks/LandingHowItWorks.tsx

@@ -57,8 +57,8 @@ const patterns = [
     v: 'Poll one or more LLMs in a TEE, sign the consensus, post it on-chain — no UMA, no dispute window.',
   },
   {
-    k: 'On-chain → API bridge',
-    v: 'Smart contract event triggers a verified call to Twilio, OpenAI, or your own API.',
+    k: 'Compliance-gated transfers',
+    v: 'Lit Action screens every recipient against a sanctions list before signing — flagged wallets simply can’t receive.',
   },
 ];
 

src/components/Prototypes/Prototype1.tsx

@@ -193,8 +193,8 @@ export default function Prototype1() {
                 v: 'Poll one or more LLMs in a TEE, sign the consensus, post it on-chain — no UMA, no dispute window.',
               },
               {
-                k: 'On-chain → API bridge',
-                v: 'Smart contract event triggers a verified call to Twilio, OpenAI, or your own API.',
+                k: 'Compliance-gated transfers',
+                v: 'Lit Action screens every recipient against a sanctions list before signing — flagged wallets simply can’t receive.',
               },
             ].map((p) => (
               <div