<?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/588ed635099f4187acc398ca3ce095c2&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/588ed635099f4187acc398ca3ce095c2-ef091114a70acf6c.gif</thumbnail_url><duration>766.889</duration><title>RAG Screenplay Coach Architecture Walkthrough</title><description>In this Loom, I walk through my screenplay instructor product with three parts, React front end, a FastAPI back end, and a retrieval pipeline. The UI sends analyze once to produce structure, then reuses that analysis and the current draft so every follow up gets re layered with the screenplay for instructor feedback, while keeping the API key off the browser. On the backend I parse scenes into metadata, embed chunks into ChromaDB using MiniLM on CPU, retrieve and rerank top k with a cross encoder. I ran three studies, error analysis, an ablation study, and a prompt comparison where full system analyst plus RAG performed best. No specific action was requested from viewers.</description></oembed>