<?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/6e8d1b6f84824a7fb8a765c25907e2fa&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/6e8d1b6f84824a7fb8a765c25907e2fa-310811926ba9ff6b.gif</thumbnail_url><duration>296.128</duration><title>Introducing the Deterministic Rule Conversion System for Policy Documents 📄</title><description>Hi, I’m Abbas, and in this video, I’m presenting our policy document to deterministic rule conversion system. I walk you through the process of uploading documents, running our extraction pipeline, and achieving 90 to 95 percent accuracy in rule extraction. I also explain how the system detects conflicts and notifies users via email. Additionally, I outline the system architecture, including components like the document loader, parser, and rule-based extractor. Please take a look at how this system can optimize our workflow and let me know if you have any questions.</description></oembed>