<?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/54683866a75b4fe5bf4342d85c958a45&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/54683866a75b4fe5bf4342d85c958a45-f069ceeab6c8a164.gif</thumbnail_url><duration>345.09</duration><title>Round 2</title><description>This Loom walks through Shaurya’s approach to tracking persona drift in a fully offline-first adaptive rack system. The raw dataset lacked real-time timestamps, so Shaurya implemented a synthetic chronological clock that bucketed every 15 messages into a simulated day to analyze sentiment and tone across 734 continuous days. To detect drift triggers without heavy LLM summarization, he used a lightweight TF-IDF keyword extractor combined with relationship tags to isolate what caused tone shifts.</description></oembed>