{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/cf0d977691274b13902169a424618ff5\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/cf0d977691274b13902169a424618ff5-86201544ff07253b.gif","duration":415.059,"title":"Puzzle Changelog Tracks Decisions and Rationale","description":"This Loom introduces Puzzle’s new Changelog feature for documenting the rationale behind process, tools, and data model decisions. It explains that when you create a changelog entry, you can associate related steps across the workspace back to that decision, so you can answer client questions months later. In the example, the creator uses Claude to generate a detailed changelog owned by Brian Ragone, marked as completed after implementing changes to a Zap for emailable email verification before sending to Intercom. The changelog captures summaries, technical specifications, data model changes, and lets you click from workflow steps back to the specific historical change."}