AI Change Desk | EP022: Access Lifecycle Check

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.

AI Change Desk | EP030: Always-On Agent Control Check

Microsoft and OpenAI moved agent work closer to persistent identity, internal apps, and publishable work surfaces. The operator question is who owns the standing permission before an agent keeps acting in the background.

AI Change Desk | EP029: Agent Reliability Evidence Check

Date: 2026-06-01 Agents are getting longer leashes: remote work sessions, stronger coding/workflow behavior, and practical observability/test tooling are all moving at the same time. This episode turns that into an operator question: when an agent can do more, what proof comes back before the work is trusted? When the agent can do more, what proof do you require before you trust the work? Run one agent reliability evidence check this week: 1. Scope receipt: what can it reach? 2. Effort receipt: how long, how hard, and how expensively can it work before checkpoint? 3. Quality receipt: what tests or reviews prove the output is usable? 4. Drift receipt: what changed since the last good run? 5. Fallback receipt: who stops, reroutes, or explains it when it fails? * 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 Codex cloud documentation: https://developers.openai.com/codex/cloud/ [https://developers.openai.com/codex/cloud/] * Anthropic Claude Opus 4.8: https://www.anthropic.com/news/claude-opus-4-8 [https://www.anthropic.com/news/claude-opus-4-8] * AWS LLM observability: https://aws.amazon.com/blogs/machine-learning/comprehensive-observability-for-amazon-sagemaker-ai-llm-inference-from-gpu-utilization-to-llm-quality/ [https://aws.amazon.com/blogs/machine-learning/comprehensive-observability-for-amazon-sagemaker-ai-llm-inference-from-gpu-utilization-to-llm-quality/] * AWS deep-agent evaluations: https://aws.amazon.com/blogs/machine-learning/evaluating-deep-agents-using-langsmith-on-aws/ [https://aws.amazon.com/blogs/machine-learning/evaluating-deep-agents-using-langsmith-on-aws/] * AWS agent test-suite datasets: https://aws.amazon.com/blogs/machine-learning/build-a-test-suite-that-grows-with-your-agent-with-dataset-management-in-amazon-bedrock-agentcore/ [https://aws.amazon.com/blogs/machine-learning/build-a-test-suite-that-grows-with-your-agent-with-dataset-management-in-amazon-bedrock-agentcore/] * OpenAI May 28 model lifecycle note: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] 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.

AI Change Desk | EP027: No-New-Delta Verification Discipline Check

Today is Memorial Day in the United States, and there will be no Wednesday AI Change Desk episode this week. This Monday episode keeps the feed useful without forcing novelty into a quiet official-news cycle. The core operating point: no-new-delta days are not skip days. They are verification days. The May 25 source check did not find a newer relevant OpenAI release-note date displacing the May 21 Codex update. That means the operating frame should stay date-bounded: the Codex execution signal remains current, while provenance, creator distribution, and community pulse remain supporting context. Teams get into trouble when they confuse "checked today" with "changed today." A refreshed page, community chatter, or a useful trade report can create pressure to say something new. The discipline is to separate confirmed change, continuity context, and directional signal. Memorial Day is observed on the last Monday of May and honors those who died in service to the country. The episode includes a brief respectful segment acknowledging the day and the value of restraint before returning to the operational topic. Before locking any AI release note, script, stakeholder update, or internal status memo this week, add three fields: * net new official delta: yes or no * latest official date seen: source and date * carry-forward justification: why the prior frame still stands There will be no Wednesday episode this week. AI Change Desk returns with the next Monday main episode. * OpenAI ChatGPT release notes: https://help.openai.com/en/articles/6825453-release-notes [https://help.openai.com/en/articles/6825453-release-notes] * OpenAI provenance post: https://openai.com/index/advancing-content-provenance/ [https://openai.com/index/advancing-content-provenance/] * Podnews Report Card 2026 Results: https://podnews.net/article/report-card-2026-results [https://podnews.net/article/report-card-2026-results] * YouTube news from Google I/O 2026: https://blog.youtube/news-and-events/youtube-news-google-io-2026/ [https://blog.youtube/news-and-events/youtube-news-google-io-2026/] * U.S. Census Bureau Memorial Day 2026: https://www.census.gov/newsroom/stories/memorial-day.html [https://www.census.gov/newsroom/stories/memorial-day.html] 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 Michael's opinions and are not representative of any organization.

AI Change Desk | EP026: Agent Toolchain Ownership Check

AI agents are moving from chat windows into toolchains: managed execution environments, SDKs, MCP servers, mobile approvals, workspace integrations, search agents, shopping agents, and enterprise platforms. This episode translates the week of announcements into one operator question: who owns the toolchain when the agent starts acting? * Google I/O 2026 pushed agentic Gemini deeper into developer tools, Search, Workspace, shopping, app development, and personal agent surfaces. * Anthropic announced it is acquiring Stainless, an SDK and MCP server tooling company that has generated official Anthropic SDKs. * Anthropic and KPMG announced a global alliance to embed Claude into KPMG Digital Gateway and make Claude available to more than 276,000 employees. * OpenAI Codex mobile and ChatGPT personal finance remain active control signals from the prior week: approvals and sensitive data context are moving closer to always-on workflows. Do not treat agent access as a one-time tool approval. Treat it as a toolchain lifecycle: owner, connector, permission boundary, evidence, fallback, and shutdown authority. By Wednesday, May 27, 2026, complete one agent-toolchain ownership review for your highest-impact AI workflow. Fields to capture: workflow name, agent surface, SDK/API/tool dependencies, connector owner, permission boundary, human approval point, evidence trail, fallback route, shutdown owner, and next review date. * Anthropic: Anthropic acquires Stainless — https://www.anthropic.com/news/anthropic-acquires-stainless [https://www.anthropic.com/news/anthropic-acquires-stainless] * Anthropic: KPMG integrates Claude across its core business and workforce of more than 276,000 — https://www.anthropic.com/news/anthropic-kpmg [https://www.anthropic.com/news/anthropic-kpmg] * Google: I/O 2026 collection — https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-collection/ [https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-collection/] * Google: I/O 2026 developer highlights — https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-developer-highlights/ [https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-developer-highlights/] * Google: I/O 2026 opening keynote — https://blog.google/innovation-and-ai/sundar-pichai-io-2026/ [https://blog.google/innovation-and-ai/sundar-pichai-io-2026/] * OpenAI: Work with Codex from anywhere — https://openai.com/index/work-with-codex-from-anywhere/ [https://openai.com/index/work-with-codex-from-anywhere/] * OpenAI: ChatGPT release notes — https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] 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 Michael's opinions and are not representative of any organization.