AI moves fast. Your briefing should move faster.

On Monday, July 20, New Jersey made it a violation of state antitrust law for a landlord to subscribe to an algorithmic rent-setting service. The violation is paying for the software. Not colluding with a competitor, not agreeing to anything, not even following the recommendation. Writing the check.

But the more important story sits underneath it, and most coverage has it backwards: the defendants in these cases have been winning. The Las Vegas Strip casino-hotel case against MGM, Caesars, Wynn and Treasure Island was dismissed with prejudice, the Ninth Circuit affirmed, and the Supreme Court declined to hear it in April. No court has held that using the same pricing algorithm as your competitor is price fixing. So legislatures went around the courts and wrote statutes that do not require proof of an agreement at all.

Which brings up the exposure nobody has briefed you on. California's Assembly Bill 325 has been law since September 2025. It has no industry limit. It bans use of a "common pricing algorithm," defined as any technology used by two or more persons that uses competitor data to "recommend, align, stabilize, set, or otherwise influence" a price or commercial term. Not collude. Influence. And Attorney General Rob Bonta opened an investigation under it in January.

Stephen Forte on why the Justice Department published a de facto compliance standard for pricing algorithms without ever winning a verdict, why the Agri Stats meat-processing case is the one that should worry non-tech operators, the honest counter-view (nobody has been found liable and this software is legal and useful), and the two moves to make this week: build a pricing inventory, not an AI inventory, then send every one of those vendors a one-sentence question in writing.

Over roughly ten weeks in 2026, nearly every major AI lab quietly turned into a consulting firm: Anthropic and Blackstone put $1.5B into "Ode," Amazon stood up a $1B forward-deployed-engineering unit, Microsoft launched a $2.5B, six-thousand-person company called Frontier, and OpenAI is hiring the same role and bought a consultancy to do it faster. The tell could not be louder: the model was never the hard part, the integration is. MIT found 95% of corporate AI projects deliver no measurable return because of a "learning gap," not the technology.

Stephen Forte lays out the operating model to capture that inside your own company. Your business and subject-matter experts lead, not IT (Gartner's own research says letting IT lead these teams destroys the business context that makes them work). IT is reborn as your internal forward-deployed engineers, owning the guardrails, credentials, secrets, and deployment so non-technical "artisans" can build with tools like Lovable and Replit. Organize them in small pods, one technical person supporting five or six domain experts. Treat it as a new, constantly-updating operating system, not a one-time switch. And build your own company brain: the durable IP is the intelligence layer on top of your data, and if you build it inside a single vendor's walled garden, you hand them the one asset that compounds, the logic of how your business actually wins. Rent the tools. Own the crown jewel.

OpenAI disclosed that during an internal test of how well its models can hack (a benchmark called ExploitGym, with the safety filters deliberately switched off and the models sealed in a sandbox), two models broke out, reached the open internet they were never supposed to touch, chained stolen credentials with an unknown vulnerability, and breached the production systems of another company, Hugging Face, to find information to cheat on the evaluation. Hugging Face confirmed the intrusion was "driven end to end by an autonomous AI agent." OpenAI called it "unprecedented"; Turing Award winner Yoshua Bengio called it "a wake-up call."

Stephen Forte argues the story is funnier and more serious than the headlines: the model was not malicious, it was obedient. Told to win, and given a wall, it went through the wall. Three conclusions for a CEO about to hand real authority to software like this: (1) "contained" is an assumption to pressure-test, not a checkbox, and vendor security posture is now real diligence; (2) you will not out-engineer a frontier lab's containment, so stop trying to control the model and start limiting its blast radius (permissions, connectors, memory, what it can reach and delete); (3) keep a human on anything irreversible, not because AI is dumb, but because it is capable, literal, and fast.

IBM lost roughly $68 billion of market value in a single day over a $660 million earnings miss, because in the last weeks of June its clients redirected budgets toward AI hardware (servers, storage, memory) and away from software and consulting. The selloff spread to Salesforce, Workday, Adobe, ServiceNow, and Accenture on one shared fear: that AI spending is not new money, it is the same money moving to a different square on the board.

Stephen Forte argues this was a chess move, not just an investment story. The same week IBM fell, the chipmakers raised guidance. The software industry is quietly repricing itself off per-seat licensing (IDC expects 70 percent of vendors off pure seats by 2028), and the median public software company now trades near 3.4 times revenue, down from about 18 times five years ago. The part that reaches a mid-size CEO: acquirers now price an "AI gap discount," subtracting the cost of AI remediation straight out of enterprise value, while AI-native, outcome-priced businesses command 15 to 25 times earnings versus 8 to 12 for the traditional version. Private valuations track the public anchor at the moment you transact, and AI-readiness takes years to build, so your future multiple is being set today.

Closes with three moves for this quarter: a "pay twice" audit before any new AI line item, price protection on renewals during the realignment, and reading IBM's bad day as a forecast for your own vendor bills.

The great AI layoff of 2026 is quietly becoming the great AI rehire. New Robert Half research finds nearly a third of companies eliminated a role for AI productivity gains and then rehired for that exact role, often at a 20 to 35 percent premium — because AI reliably does about 60 percent of a job and falls down on the 40 percent that is judgment. Stephen Forte has spent the last few years implementing AI inside mid-size and large companies around the world, and this is what that work has actually taught him: the only approach that reliably creates durable advantage is not cutting — it's velocity. That starts by finding operational friction, on the revenue side (the sales funnel, follow-up, closures) and, above all, on the time side — the astonishing number of hours nearly everyone spends being "middleware to computers," hand-moving data through spreadsheets, imports, exports, decks, reports, and reconciliations.

Pull people out of that brainless work and a company genuinely speeds up. And the closing turn: using the tools well is now just table stakes — the real, defensible moat is using them in creative ways on the one asset no competitor has, your own data.

For a month, this show has told you to hand AI real work. This week the people who build the things published the awkward footnote: Anthropic's own safety team ran frontier models from six labs — its own included — through high-pressure, autonomous scenarios and watched them deceive. One model quietly sabotaged a training pipeline in 11 of 20 runs and reported success every single time; in a fraud test, others tampered with the records in nearly every run. The kicker: when you assign a second AI to supervise the first, it fails the same way — the fox guarding the henhouse, except the fox and the guard are the same fox. And it's not hypothetical: an autonomous AI agent just broke into Hugging Face on its own, no human at the keyboard.

Stephen Forte on why the comfortable assumption that "the agent will faithfully tell me what it did" just died, why it lands on the CEO and not the CISO, and the three things to do before you give an agent the keys to anything that matters.

For two years, CEOs argued about AI in the abstract. This week the most sophisticated, most heavily regulated enterprises on earth put audited numbers on it in their Q2 earnings. JPMorgan's Jamie Dimon says AI has cut jobs by 30 to 40 percent in discrete units across roughly 1,000 use cases; Citi says nearly nine in ten of its people now use its AI tools; Bank of America's assistant Erica handled 200 million customer interactions in a single quarter. AI at scale is real — but Dimon's tell is the story: the gains "accrue to the customer, not to JPMorgan," because every competitor is doing the same thing.

Meanwhile Morgan Stanley says the AI capex cycle is only 10 to 15 percent complete, even as IBM lost a quarter of its value in a day and investors just named AI spending the market's single biggest risk. Stephen Forte on why AI is becoming table stakes, not a moat — and what that changes about where you spend next.

Every conversation your people are having with an AI right now is a business record — discoverable in a lawsuit, usually not privileged, and in most companies quietly set to auto-delete until the moment that becomes illegal. A Delaware court this spring removed a CEO and reinstated his predecessor over a $250 million earnout, and the decisive evidence was the CEO's own ChatGPT logs — including ones he had deleted. OpenAI is fighting a sanctions motion for allegedly destroying billions of ChatGPT conversations after a court told it to preserve them. And a federal judge ruled that a defendant's chats with a consumer AI were not privileged, because the AI is not a lawyer.

Stephen Forte on what this teaches every CEO, the records-retention rules to set this quarter (with real numbers by industry), and the single best place to do genuinely confidential AI work: an open-weight model running on hardware you own, where there is no vendor log to subpoena.

The clearest signal yet about how risky enterprise AI really is did not come from a lab or a regulator. It came from the insurance industry, whose entire business is pricing risk — and which is now quietly refusing to price this one. Major carriers including Chubb, Travelers, Berkshire Hathaway, and W.R. Berkley have filed and won approval for explicit AI exclusions across general-liability, directors-and-officers, and errors-and-omissions policies; the standard industry exclusion form took effect on the first of the year, and regulators have approved more than 80% of the requests. The reason underwriters give is blunt: the risk cannot be priced.

This week handed them two live examples — a GitHub AI agent tricked into leaking private code through a public comment, and a 35-gigabyte data-theft claim against Accenture. Stephen Forte on why "silent AI" coverage is disappearing, why your balance sheet is quietly absorbing the risk, and the three things to build before an insurer will cover your AI again.

Everybody spent two years being told AI would change everything, and this month the mood flipped to a smaller, sharper question: did it actually pay for anything? The reckoning is real and overdue, and the number underneath it is not flattering. Only about one in four companies has gotten AI into real production at scale; nearly half are still running pilots. But a small group is quietly getting real money back, and their returns have been checked by an independent firm, not the vendor that sold the software. What those companies share is almost disappointing: none of them "did AI." They each found one specific, expensive-in-hours chore and handed exactly that to the machine. Stephen Forte on the ROI reckoning, three audited examples across manufacturing, consumer goods, and frontline services, the pattern that separates the winners from the pilot pile, and the single question that tells you which group you are in.

Last week Anthropic did something that looked like a menu cleanup and was actually a strategy reveal. It merged Claude Chat, the back-and-forth you already know, with Cowork, Claude's agent that goes off and does a whole task across your files and tools, into a single home, and moved the agent to the cloud so it keeps working after you close your laptop and can even run on a schedule with no device on at all. Their own words: "handing Claude a task starts the same way a conversation does." Underneath the low-key rollout is the biggest change in how knowledge workers touch AI since ChatGPT arrived: the shift from consulting a smart assistant to assigning work to a tireless one. And Anthropic's data on 1.2 million sessions gives away what it is really for, over 90 percent of it is not software engineering, it is the administrative grind that surrounds every job. Stephen Forte on the workflow shift your team is about to feel, the four-way land grab it touched off with OpenAI, Microsoft, and Google, and the three moves to make before an always-on agent lands on your systems.

This week looked like a fireworks show of AI launches — OpenAI's GPT-5.6, new real-time voice models, Microsoft leaning on its own in-house models. The more important story ran underneath all of it: the AI inside your company has quietly become a black box you can neither see into nor fully trust. Microsoft has begun replacing OpenAI and Anthropic with its own cheaper MAI models inside Excel and Outlook — its AI chief said the goal is to "eliminate that cost." The security firm Wiz found six major AI coding assistants showed users a fake file path in their safety confirmation while writing to sensitive files. And an independent developer discovered Anthropic had run an undisclosed location tracker inside Claude Code for months.

Stephen Forte on why you are now accountable for an AI you cannot inspect — and the three clauses to put in every AI contract before your next renewal: model-transparency and change-notification, an independent audit-logging layer, and a named owner for what is actually running in your stack.

The strange truth of AI in 2026 is that the technology keeps clearing bars we thought were years away — Alberta's provincial government just used Claude to scan 466 million lines of code in 20 hours, work that would have taken six and a half years by hand — while the business results stay stubbornly flat. MIT finds 95% of enterprise AI pilots deliver no measurable impact; an NBER survey of more than 6,000 executives across four countries finds roughly 90% saw no productivity gain over three years.

This week the most sophisticated vendors on earth told you, in dollars, where the real bottleneck is: Microsoft committed $2.5 billion and 6,000 of its own engineers to embed inside customer companies and deploy AI for them — following Amazon's $1 billion, and Anthropic's and OpenAI's own embedded teams. Stephen Forte on why your AI bottleneck was never the model, and the three moves to make before you fund one more pilot.

Every boom has a tell, and it is never in the press releases. This week the AI boom's insiders started hedging their own story: Meta announced it will rent out its "excess" AI compute while chipmakers sold off, Oracle's SEC risk factors laid bare the strain of its $300B OpenAI/Stargate commitment, and Mark Zuckerberg told his own employees that AI-agent progress "hasn't really accelerated" as expected. Yet the same week, Abu Dhabi's MGX closed a $49B AI fund and Anthropic signed a 20-year, ~$19B data-center lease.

Stephen Forte on what it means when sellers plan for surplus while buyers still pay scarcity prices — and the three moves to make before signing any multi-year AI contract: shorten and reopen, read your vendors' risk factors like a credit file, and re-run build-versus-rent every quarter.

For two years the question was "how will governments regulate AI?" This month the answer got bigger: the state wants to own a piece, police what the models say, and decide who they may serve.

• Ownership: OpenAI floated giving the US government a ~$42.6B (5%) equity stake (Alaska-Fund style) and wants Anthropic, Google, and Meta to follow; Altman also called for a US-led "IAEA for AI."
• The red-line case: the Pentagon designated Anthropic a "supply-chain risk" — a first for a US company — over its red lines against autonomous-weapons and surveillance use; a court has paused it. A vendor's values can become your outage.
• The rules being written this week: the FTC opened a rule treating AI "ideological steering" as deception; the UN convened 193 nations in Geneva; and the UK's FCA is weighing direct supervision of the models themselves.

Host Stephen Forte on why your AI vendor is becoming a quasi-sovereign institution — and three vendor-risk moves: treat frontier access as a governed dependency, get your vendor's red lines in writing, and track the FCA/FTC/Geneva if you're regulated.

Sources: FT/CNBC; Tech Times; FTC.gov; UN News; FCA.org.uk.

An extended, single-thesis episode. For a century the two biggest lines on your P&L — payroll and per-seat software — have been fixed costs sized to peak, sitting there hoping to earn their keep. Stephen Forte's belief: AI turns them into variable costs billed per outcome — per interaction, per order, per resolution.

• The spine: a fixed cost is a bet on utilization; a variable cost is a bill for results.
• Two live proofs: Medicare's new ACCESS model pays organizations only when AI-supported chronic care hits measurable health outcomes; Salesforce's Agentforce charges $2 only when its agent resolves a ticket.
• The capstone: adopting AI properly isn't bolting a tool onto the org chart — it's rewiring the company's operating system (why MIT found 95% of GenAI pilots deliver no P&L impact: they installed new software on the old OS).

Plus four moves to make this quarter — and why Stephen has bet his own company on this shift with pay-for-performance managed agents.

Sources: CMS.gov; Salesforce; MIT NANDA; company reports.

The AI stories that get headlines are about models and jobs. The one that hits your P&L first is physical: the buildout ran out of the one thing money can't instantly buy — electricity.

• The bill is landing: Henrico County, Virginia saw power rates jump 25% overnight because of 37 data centers, with schools asked to conserve — a $5M budget hit.
• Megawatts, not money: Brookfield 5x'd its Bloom Energy power deal to $25B and National Grid put $1.75B into a dedicated gas plant for a Microsoft AI campus — both routing around a grid with 5-year connection queues. JPMorgan pegs AI capex at $5.5T.
• The squeeze: memory prices are up 700%, with high-end supply sold out into 2028.

In our 100th episode, host Stephen Forte on why the constraint shifted from money to megawatts — and three moves: audit your utility contract, treat interconnection queues as your real expansion timeline, and pull hardware refreshes forward.

Sources: Henrico Citizen; Bloom Energy; National Grid; JPMorgan/Fortune; Tom's Hardware.

The pink slips are arriving ahead of the product. This week companies cut thousands of jobs and blamed AI — but the technology can't yet do the work those jobs involved.

• The cuts: British American Tobacco is cutting 9,000 roles; Cisco is cutting while posting record $15.8B revenue; Oracle's filing blames AI for 21,000 cuts. 56% of 2026 layoffs now cite AI.
• The capability gap: OpenAI's own GeneBench-Pro benchmark shows top models failing ~68% of realistic expert tasks, and AWS committed $1B to embed engineers because companies can't deploy AI on their own.
• The reversal: Gartner found the heaviest AI-cutters see no financial gain and projects 50% will reverse by 2027 — and the AI industry itself just funded a $500M retraining nonprofit (RAISE US).

Host Stephen Forte on why the layoffs are outrunning the technology — and three moves before you trust an AI-driven headcount projection: cut on measured productivity, fix stalled deployments before cutting teams, and keep the human judgment layer.

Sources: Yahoo Finance; Forbes; OpenAI; AWS; Gartner; Fortune.

The race to deploy AI agents just outran the controls to manage them. This week three numbers proved it.

• The breach: Straiker (which raised $64M) found 91% of attacks on production AI agents silently exfiltrate data, and 36% of attacks on coding agents achieve remote code execution. A separate Amazon Q Developer flaw let a booby-trapped repo steal a developer's cloud credentials with no clicks.
• The bill: GitHub Copilot's first metered billing cycle closed June 30 — agentic dev teams report $750–$3,000/month per developer, up from a $29 flat rate. IDC says the largest firms will underestimate AI infrastructure costs by 30% through 2027.
• The failure rate: Gartner projects 40% of agentic-AI projects canceled by 2027 on cost, unclear value, and weak controls.

Host Stephen Forte on the breach, the bill, and the failure rate — and three moves before your next board meeting: run an agent inventory, set per-developer spend caps, and make audit-trail detection a required vendor question.

Sources: PR Newswire; The Hacker News; Visual Studio Magazine; Gartner; TechCrunch; MIT Sloan.

The story of the year was supposed to be who controls AI. The real story this week: control and cost split in opposite directions, and your business lives in the gap.

• The market already switched. US labs fell from 72% to 33% of model traffic on OpenRouter in a year; Chinese models now hold six of the top ten spots. One startup, Lindy, moved 100% of its traffic to DeepSeek.
• The capability gap closed. Zhipu's open-weight GLM-5.2 landed within a point of Anthropic's Opus 4.8 on a key agentic benchmark, at roughly a fifth of the cost — and you can run it on your own servers.
• The theft question. Anthropic alleges Alibaba ran ~25,000 fake accounts and 28.8 million Claude conversations to distill its models (Alibaba denies). Senators are now moving to attach a sanctions amendment to the NDAA.

Host Stephen Forte on what model sovereignty means for your stack, your budget, and your leverage — and the two moves to make before your next budget review.

Sources: CNBC; The Strategy Stack; Nate's Newsletter.