{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69ab3b7c7036d739021982df/6a161589c92816b544ec00fd?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"How to verify AI-generated Office files before they ship","description":"<p>For deeper playbooks and analysis: <a href=\"https://natesnewsletter.substack.com/\" rel=\"noopener noreferrer\" target=\"_blank\">https://natesnewsletter.substack.com/</a></p><p><br></p><p>AI can make PowerPoint decks, Excel workbooks, and Word documents faster, but faster is not the same as trustworthy. In this episode, Nate breaks down a practical workflow for AI Office files: prepare the sources, define the structure, constrain the artifact creation, and verify the output like a skeptical reviewer.</p><p><br></p><p>The key idea: the file is not the whole thing. The file is the visible output of a knowledge-work system. If the claims, numbers, sources, assumptions, charts, and formulas cannot be traced, the artifact may look finished while quietly breaking trust.</p><p><br></p><p>Hosted on Acast. See acast.com/privacy for more information.</p>","author_name":"Nate B. Jones"}