AI Change Desk | EP036: Preview Before Power Mode

AI Change Desk | EP036: Preview Before Power Mode

Frontier capability is arriving before broad access. This episode turns OpenAI's GPT-5.6 Sol preview, OpenAI's agent-work research, Microsoft's Copilot in Excel finance controls, and Anthropic's Claude Tag into one operator test: before power mode becomes normal mode, name the preview gate. Who gets frontier capability access, in which surface, with which data and tools, under which safeguards, with what evidence, and who can roll it back? 1. Eligible user group 2. Approved surface 3. Data boundary 4. Tool boundary 5. Safeguard routing 6. Spend and cache budget 7. Evidence log 8. Rollback and deprovision owner * OpenAI: https://openai.com/index/previewing-gpt-5-6-sol/ [https://openai.com/index/previewing-gpt-5-6-sol/] * OpenAI Help Center: https://help.openai.com/en/articles/20001325-a-preview-of-gpt-56-sol-terra-and-luna [https://help.openai.com/en/articles/20001325-a-preview-of-gpt-56-sol-terra-and-luna] * OpenAI agents/work research: https://openai.com/index/how-agents-are-transforming-work/ [https://openai.com/index/how-agents-are-transforming-work/] * Microsoft Copilot in Excel: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/25/copilot-in-excel-built-for-the-era-of-frontier-finance/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/25/copilot-in-excel-built-for-the-era-of-frontier-finance/] * Anthropic Claude Tag: https://www.anthropic.com/news/introducing-claude-tag [https://www.anthropic.com/news/introducing-claude-tag] AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice.

AI Change Desk | EP034: Patch Before Prod

AI security work is moving from "find the bug" toward "help draft the fix." In EP034 of AI Change Desk, Michael breaks down OpenAI's June 22 Daybreak and Patch the Planet announcements and turns them into a practical operator question: If AI can find vulnerabilities and draft fixes at machine speed, who validates the patch, approves the rollout, owns rollback, and proves the fix should ship? Run one 45-minute Patch Before Prod review. Use eight receipts: * Finding validator * Patch approver * Test evidence * Release owner * Rollback owner * Disclosure owner * Budget owner * Replacement path * OpenAI Daybreak: https://openai.com/index/daybreak-securing-the-world/ [https://openai.com/index/daybreak-securing-the-world/] * OpenAI Patch the Planet: https://openai.com/index/patch-the-planet/ [https://openai.com/index/patch-the-planet/] * OpenAI enterprise spend controls: https://openai.com/index/chatgpt-enterprise-spend-controls/ [https://openai.com/index/chatgpt-enterprise-spend-controls/] * OpenAI ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * Microsoft Copilot Cowork GA: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/] * Microsoft Work IQ APIs: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/02/announcing-the-new-work-iq-apis/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/02/announcing-the-new-work-iq-apis/] * Anthropic Fable/Mythos access statement: https://www.anthropic.com/news/fable-mythos-access [https://www.anthropic.com/news/fable-mythos-access] * YouTube AI labels update: https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/ [https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/] * Podnews on RSS AI disclosure flag: https://podnews.net/update/bumper-free [https://podnews.net/update/bumper-free] Production disclosure: AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval remain human-led. This is operational guidance, not legal advice.

AI Change Desk | EP033: Agent Runtime Budget Check

Agent work is not just an access question anymore. It is becoming a runtime budget question. This brief looks at Microsoft's Copilot Cowork general availability and Work IQ controls, then pairs that with Anthropic's statement that it is removing access to Fable 5 / Mythos 5 to ask a practical operator question: If an agent can retrieve context, call tools, run longer tasks, and consume metered credits, who owns the budget gate before the work continues? Run one Agent Runtime Budget Gate by June 24, 2026. Use: * Microsoft Copilot Cowork GA: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/] * Microsoft Work IQ APIs: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/02/announcing-the-new-work-iq-apis/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/02/announcing-the-new-work-iq-apis/] * Anthropic Fable/Mythos access-removal statement: https://www.anthropic.com/news/fable-mythos-access [https://www.anthropic.com/news/fable-mythos-access] * OpenAI ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * OpenAI Memory FAQ: https://help.openai.com/en/articles/8590148-memory-faq/ [https://help.openai.com/en/articles/8590148-memory-faq/] Production disclosure: AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval remain human-led. This is operational guidance, not legal advice.

AI Change Desk | EP032: Memory Summary Exit Check

If AI memory can be edited more visibly, turned off more easily, and still be rebuilt from old context later, the operating question is not whether the settings page looks cleaner. It is what evidence proves sensitive or stale context actually left the workflow. * Why OpenAI's June 12 memory-summary controls matter operationally. * Why deleting visible memories is not the same as deleting past chats or every source. * Why a partial memory summary creates a partial-ledger problem. * How Developer mode and model retirement add inspection and version-receipt pressure. * A forty-five minute Memory Summary Exit Check operators can run this week. * OpenAI ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * OpenAI Memory FAQ: https://help.openai.com/en/articles/8590148-memory-faq/ [https://help.openai.com/en/articles/8590148-memory-faq/] * OpenAI Codex browser docs: https://developers.openai.com/codex/app/browser [https://developers.openai.com/codex/app/browser] * OpenAI Lockdown Mode: https://help.openai.com/en/articles/20001061-lockdown-mode [https://help.openai.com/en/articles/20001061-lockdown-mode] * OpenAI memory product post: https://openai.com/index/chatgpt-memory-dreaming/ [https://openai.com/index/chatgpt-memory-dreaming/] * YouTube AI labels update: https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/ [https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/] * Podnews AI disclosure guidance: https://podnews.net/update/ai-disclosures [https://podnews.net/update/ai-disclosures] AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stay human-led. This is operational guidance, not legal advice.

AI Change Desk | EP031: Memory Control Plane Check

AI memory is becoming more useful, but usefulness creates a new operating surface. If the system can carry context forward, teams need a memory control plane: summary, source, correction, deletion, sensitive-work mode, and disclosure. * Why better memory is not just personalization; it is source-of-truth pressure. * What OpenAI's June 4 memory rollout changes for operators. * Why memory summaries, source tracing, correction, and deletion paths matter. * How Lockdown Mode fits sensitive browsing and hostile-input workflows. * Why audience disclosure still belongs in the release workflow. * A 45-minute memory-control-plane check for Monday teams. What would have to be true for your team to trust remembered AI context in production work? * OpenAI memory rollout: https://openai.com/index/chatgpt-memory-dreaming/ [https://openai.com/index/chatgpt-memory-dreaming/] * OpenAI Memory FAQ: https://help.openai.com/en/articles/8590148-memory-faq/ [https://help.openai.com/en/articles/8590148-memory-faq/] * ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * Lockdown Mode: https://help.openai.com/en/articles/20001061-lockdown-mode [https://help.openai.com/en/articles/20001061-lockdown-mode] * YouTube AI labels: https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/ [https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/] * Podnews AI disclosure guide: https://podnews.net/update/ai-disclosures [https://podnews.net/update/ai-disclosures] AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are my opinions and are not representative of any organization.