<?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/ec9fc2aac7fa47efa67414ca17ca7c04&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/ec9fc2aac7fa47efa67414ca17ca7c04-1f7879d16d6e1c02.gif</thumbnail_url><duration>201.302</duration><title>How Analysts Fix AI Detection Errors</title><description>This Loom demonstrates Atlass, a triage tool that reviews AI-detected objects in overhead imagery and dispatches confirmed reports. The author shows how a truck depot image can be misclassified by the model at low confidence, while an analyst quickly reviews it in about 5 seconds, logs model failures, and flags images for rescans so mistakes are not silent. They then review another set from Bridge Sector 1 where all 26 images were detected as cars and explain integrated shortcut and one-button dispatch behavior. The PID section covers design tradeoffs, including time-to-dispatch with analyst-confirm precision, and notes the current build timeline of 5 days by one developer using Next.js, YOLOv8, and Supabase, deployed on Vercel.</description></oembed>