The Foundation

OpenAI, Anthropic, and Google are all building or expanding forward-deployed engineering and consulting capacity. That is a strategic signal: the models are powerful enough, but organisations cannot absorb the capability without help redesigning workflows, data access, governance, and operating rhythm.

Concrete proof landed in late May 2026: Anthropic announced joint centres of excellence with Accenture, Deloitte, and PwC, and committed to training and certifying 30,000 PwC professionals on Claude. Even AGI-believing labs now treat diffusion work as essential. As one observer put it: “Anthropic knows they are weeks away from AGI, which is why they are working with Accenture, Deloitte, PwC…”

Governance response: Treat deployment support as part of the AI stack. A small business does not need a forward-deployed engineer, but it does need the same function: one accountable person who translates tools into workflows, documents what works, and keeps verification loops alive. Solo operators are already doing what the labs are paying the Big Four to teach.

Companies will increasingly cite AI when announcing layoffs. Sometimes that will be true. Sometimes AI will be a convenient cover for overhiring, market contraction, margin pressure, or management restructuring. Coinbase and Cloudflare made this narrative discipline visible: the public explanation is not always the whole operational story.

Governance response: Ask for business context before accepting AI displacement claims. Compare usage evidence, revenue pressure, hiring history, operating model changes, and role-level workflow redesign. AI impact is real, but lazy attribution produces bad strategy.

AI Is Officially Political

Vendor selection is now policy risk. Government contracts have been revoked overnight based on CEO statements (the Dario Amodei memo incident, March 2026). Blue Rose Research data shows AI ranked 29th of 39 tracked issues but rising faster than any other. 72% of voters fear wage depression, 77% fear industry elimination. Even Trump voters choose “protect jobs” over “keep innovating” by 2:1. The Pentagon vs Anthropic dispute is now in federal court — Judge Rita Lynn called Pentagon conduct “troubling.”

Governance response: Vendor neutrality as a principle. Multi-vendor capability as risk management. Political risk is now a vendor selection criterion, not just a policy footnote.

The White House released a 6-point AI legislative framework. Key positions: no new regulatory body (sector-specific approach using existing agencies), strong state preemption push (federal floor for AI rules), IP and copyright deferred to courts, and a workforce section that observers called “hand-wavy.” Dean Ball described it as “an opening move in a multidimensional public negotiation.” Meanwhile, states are acting independently — NY chatbot restrictions, CA AI bills, a 291-page federal bill from Blackburn. No resolution expected before midterms; 12-18 months of compliance uncertainty.

Governance response: Track state-level AI regulation where you operate. Federal preemption is aspirational, not enacted. Prepare for a patchwork compliance landscape through at least 2027.

Agent Compliance Precedent

The Amazon vs Perplexity dispute is setting legal precedent for how AI agents access third-party services. Key distinction: first-party agents vs third-party agents.

Governance response: Audit agent access patterns. Ensure agents operate within ToS boundaries.

Memory Portability

As AI agents accumulate context and memory about your organisation, that data becomes strategically significant. Data portability regulations may extend to AI memory and context.

Governance response: Vendor-agnostic context architecture. Own your knowledge layer.

Internal AI tool deployments at sophisticated organisations have been linked to security incidents exposing confidential client data. The root causes have not been exotic: basic API security, data classification, and access controls missing or under-specified before internal tools went live.

Governance response: AI security isn't optional or “phase 2.” Basic API security, data classification, and access controls must be in place before internal AI tools go live. If sophisticated firms can miss this, so can you.

Hollywood unions are negotiating a fee for studios that use AI-generated actors instead of human performers. Named after Tilly Norwood — an AI actress created by Particle 6 Productions — this is the first formal AI displacement compensation mechanism to move from concept to the negotiation table.

Governance response: Every sector will face this conversation. Whether it's called a “Tilly Tax,” an automation levy, or a transition fund — organisations using AI to replace roles need a position on workforce impact before unions or regulators define one for them.

The UK government has established a task force on AI-generated content, working on labelling best practices and transparency standards. An interim report is expected by autumn 2026. This sits alongside existing debates on training data rights and IP ownership.

Governance response: UK organisations should track this actively. Labelling and provenance requirements are likely to become compliance obligations. Build transparency into AI-generated content workflows now, rather than retrofitting later.

The Governance Enforcement Gap

In creative industries, writers are signing declarations that they haven't used AI — while privately using it extensively. The same pattern is emerging across professional services, journalism, and consulting. Policies exist, but enforcement is performative.

Governance response: Realistic governance beats theatrical governance. Policies that acknowledge AI use and set quality standards work better than blanket bans that everyone quietly ignores. The question isn't “did you use AI?” — it's “is the output good enough?”

Opus 4.8 (28 May 2026) is reported to be 4x less likely than its predecessor to let a significant flaw pass without flagging it, and more likely to push back on plans it judges to be unsound. This has direct governance relevance: the agent is taking on more of the verification role.

The governance implication is not that human review becomes optional. It is that the agent is a more active participant in catching errors, which changes how review workflows should be designed. A model that challenges a plan mid-task is surfacing a decision point, not a failure. Build review checkpoints that can receive a challenge and route it to a human, rather than treating all agent output as finished work.

Governance response: Treat agent pushback as signal, not obstruction. Update review loops to capture flagged issues, not just final outputs.

Two features in research preview as of late May 2026 signal the next shift in how agentic work is structured. Dynamic Workflows lets Claude coordinate a fleet of parallel subagents within a single session, useful for large tasks like multi-document analysis, codebase-wide checks, or phased research (Max, Team, and Enterprise plans currently). Agent View adds background dispatch: you kick off an agent, it works while you focus elsewhere, and you return only when it flags a decision.

For solo operators, this is a meaningful shift in work pattern. The human role moves from step-by-step prompting to staging the task, setting the success condition, and monitoring progress rather than driving it. That is a governance question as much as a workflow question: who defines what “done” looks like, and who reviews it when the fleet returns?

Governance response: Before delegating to background agents, define the completion condition, the review criteria, and the escalation path. The /goal pattern (available now on any Opus 4.8 plan) is a good place to build this habit before Dynamic Workflows becomes broadly available.

In a single week in late May 2026, the concept of a tax on AI token usage moved from fringe to mainstream policy discourse. Elizabeth Warren published an op-ed in Time calling for AI taxation. A Michigan Senate candidate included a token tax in her platform. Mark Cuban proposed 50 cents per million tokens at the provider level. DuckDuckGo’s CEO called for a 10% surcharge matched to employer payroll contributions. Anthropic’s own CEO floated 3% of revenue going to government redistribution.

The first-principles argument is coherent: when AI agents perform work that humans previously performed, the existing tax framework creates a fiscal preference for automation (human labour carries a 35% average tax burden; AI inference carries none). Some form of fiscal parity mechanism will be debated seriously over the next 2-3 years. The token mechanism specifically has strong technical objections (tokenizer endogeneity, 200x annual price declines, geographic routing). Consumption-based approaches at the point of final use are likely to be more technically defensible.

Governance response: no action required now. Signal-watch: any token-cost mechanism would most likely reach small operators through higher provider prices, not direct filing obligations. For those with a stake in AI adoption remaining affordable, the conversation is worth following and engaging with constructively.

Strategy to Execution

AI strategies often stall because they don't translate into practical capability. We help bridge the gap – taking strategic priorities and building the context systems, skills architecture, and team fluency to deliver on them.

Governance in Practice

Good governance isn't just policies – it's embedded in how AI is actually used. Our context engineering and skills-based approach builds governance into workflows, not documents.

Leadership Fluency

Directors and senior managers need AI fluency to govern effectively. We help build this capability through practical understanding, not technical training.