<?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/2b61414bb980481d96c423e43e545bb1&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/2b61414bb980481d96c423e43e545bb1-afae969e43252ceb.gif</thumbnail_url><duration>170.933</duration><title>Anomaly Scoping Agent</title><description>In this video, I walk you through how to build an anomaly scoping agent in the Catrix platform to proactively analyze bugs and their potential impacts on our project. We&apos;ve heard from many of you that triaging bugs can be quite challenging, especially regarding their influence on requirements and design controls. By creating a custom agent, we can assess anomalies from our development history and understand their effects on various system components. I demonstrate this process using an existing agent that analyzed two anomalies, providing a detailed report on their impacts. I encourage you to explore this feature to help your teams make more informed decisions before our next release.</description></oembed>