<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/9efbab21775a422fb88194264f29a2e8&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9efbab21775a422fb88194264f29a2e8-20fd56e72ba0210c.gif</thumbnail_url><duration>44.554</duration><title>Themis Lex</title><description>Everyone says you should use AI. Court staff handle some of the most protected data in the state: case parties, witnesses, victims, jurors, sealed records, personnel files. Generic AI guidance doesn&apos;t address any of that. So how can courts use AI safely? That&apos;s what Themis Lex answers. A court employee enters their role, describes their workflow in their own words, picks a data sensitivity level. They get back two lists: where AI can safely help, and where AI must never touch their work. Each item includes plain-English guardrails written for a court professional, not a developer. The whole thing downloads as a PDF they can hand to their supervisor. Built solo over three weeks for the Build Club Women in AI Accelerator. Try it at themislex.org.</description></oembed>