{"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/6a0f4cb011eba3cf15677661?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"AI Project Room: Organize Files Before Asking AI to Write","description":"<p>Now I have the full transcript. Building the deliverable.</p><p><br></p><p>What's really happening when prestigious law firms file motions full of AI hallucinations?</p><p><br></p><p>The common story is that better prompts prevent hallucinations — but the reality is more complicated.</p><p><br></p><p>In this video, I share the inside scoop on the project room workflow that makes hallucinations structurally unlikely:</p><p><br></p><p> • Why your first AI prompt should never be \"do the thing\"</p><p> • How agents now walk folder trees and compare files cleanly</p><p> • What artifacts make an agent's judgment visible and inspectable</p><p> • Where most serious knowledge work breaks down before the draft</p><p><br></p><p>Operators doing high-stakes knowledge work with AI agents need to shape the canvas before the writing starts, or they ship the same soft spots that landed Sullivan and Cromwell in front of a federal judge.</p><p><br></p><p>Subscribe for daily AI strategy and news. For deeper playbooks and analysis: https://natesnewsletter.substack.com/</p>","author_name":"Nate B. Jones"}