<?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/7071bbd8254140c4a01b612fb388f76c&quot; frameborder=&quot;0&quot; width=&quot;1668&quot; height=&quot;1251&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1251</height><width>1668</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1251</thumbnail_height><thumbnail_width>1668</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/7071bbd8254140c4a01b612fb388f76c-906c87484f22afe0.gif</thumbnail_url><duration>181.894</duration><title>Self Maintaining APIs Prevent Silent Downtime</title><description>This Loom presents a proactive approach to self-maintaining APIs that automatically detects vendor API changes and patches customer code before breaks occur. It is motivated by the claim that over 30% of AWS service downtime came from external API and package changes going unnoticed. Rather than relying on post-break dependency bumps, the system watches vendors directly and uses a pipeline built with two vendors, CrossData and Channel3. It reads a published migration guide, generates a patch, and opens a real GitHub pull request gated by human approval, and it works outside package manager workflows.</description></oembed>