<?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/a7fdb68257174972a2364c0d90ff7bc1&quot; frameborder=&quot;0&quot; width=&quot;1250&quot; height=&quot;937&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>937</height><width>1250</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>937</thumbnail_height><thumbnail_width>1250</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a7fdb68257174972a2364c0d90ff7bc1-2154804f0400f761.gif</thumbnail_url><duration>136.219</duration><title>Turning Operational Receipts into Agent Memory</title><description>This Loom discusses turning operational failure logs into native “operational memory” for Gbrain. The speaker describes documenting 63 structured operational receipts, with 14 merged into production systems, each capturing the signal, the decision, and downstream breakage. They show an example query asking Gbrain to find systems that received the correct rate limit signal yet retried incorrectly, which returned two systems including Gbrain and GSC, sharing the same failure structure across teams and stacks. They also note efforts to make these receipts a native extension in Gbrain’s FrontMatter inference system and mention scanning twice as many open source projects, finding the same failure pattern.</description></oembed>