<?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/3e8fd981f2f44cc49eadaaa29b31d0d2&quot; frameborder=&quot;0&quot; width=&quot;2940&quot; height=&quot;2205&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2205</height><width>2940</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2205</thumbnail_height><thumbnail_width>2940</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/3e8fd981f2f44cc49eadaaa29b31d0d2-15223d6cacff9edd.gif</thumbnail_url><duration>191.192</duration><title>Send Four, Bring Back One Brain</title><description>This Loom explains a system for capturing conference session knowledge and turning it into a usable “team brain” graph for organizers. The speaker contrasts a failed approach where four engineers attend dozens of sessions for three days but bring back little learning, with an automated workflow that publishes dry data to the live web and pulls actual GitHub Universe documentation where each session becomes a node. It also generates team graphs using FalcoDB to connect repositories to talks via MCP, builds NFC stickers for check-in, and shows the evidence path during the TAP demo. The team can add a new node by typing one line and saving it, so information is shared once instead of staying in four separate brains.</description></oembed>