AI moves fast. Your briefing should move faster.

If you use AI seriously, you run it on three or four surfaces at once: a chat app on your phone, one on your desktop, a coding agent inside your files, and increasingly an agent that runs scheduled work unattended. Each gets smarter every quarter. Each wakes up ignorant of the others. So you spend the day re-explaining your own business to your own tools.

Most people answer this by saying they set up a project. This weekend edition starts there, then walks through what actually fixes it.

In this episode, Stephen Forte covers:

• Why setting up a project does not solve this. A project container in Claude, Perplexity, Copilot or an agent workspace holds your standing instructions and reference material well, and cannot hold the one kind of memory that matters here. It belongs to the vendor, no other surface can read it, and the only write path is a human uploading a document. Four containers, zero shared brains.
• Why "the AI is already saving this" is only half true. Your files remember the work. Nothing remembers the state: the decision you made, the option you rejected, what is still open.
• The two files per project that fix it. A one page brief that says where things stand, and an append-only journal of short dated notes, one per session that mattered.
• Version control as the bus, for executives. Every version kept forever, authorship and timestamps for free, conflicts made loud instead of silent, and a note filed on one device delivered to every device at once.
• The loop: every surface reads the brief plus anything newer before it works, files one note after work that mattered, and once a day a scheduled job folds the notes into a fresh front page.
• The objection from touchless memory products, and why the real axis is not who does the typing but where the judgment happens. An extraction tool is a court stenographer with a search engine. A brief is a handover memo from someone who was in the room. With memory you pay a little at write time or a lot at read time, and the re-explaining you do today is the read-time bill.
• First-party validation. Five of five automatable legs worked first time from the weakest surface available, a third-party connector died mid-session while plain files kept working, and a memory store queried for project state returned scraps.
• The two rules of discipline that keep a good memory system from quietly becoming a bad one, and why a briefing without a timestamp is a rumor.

Nothing to buy. Pilot it on one project, run the daily fold by hand for the first week, and judge the page before you automate it.

Sources:

• Stephen Forte, "The Portable Memory Architecture: A Flat-File Substrate for Cross-Surface AI Memory," BuildClub working paper v1.2 (2026-08-15). The architecture, the memory tiers, the cost law, the file-hygiene rules and both rounds of validation described here.
• First-party validation round 1 (2026-08-14): five automatable legs run from a cloud agent session with no local disk and only standard connectors. All test content synthetic.
• First-party validation round 2 (2026-08-15): pilot deployment on a production internal repository. Daily consolidation run manually by design during the pilot week.
• The three prior patterns this architecture composes: Hayes-Roth, B., "A blackboard architecture for control," Artificial Intelligence 26 (1985); Mohan, C. et al., "ARIES: A Transaction Recovery Method," ACM TODS 17.1 (1992); Packer, C. et al., "MemGPT: Towards LLMs as Operating Systems" (2023).
• Previous episode: s1e125, "Rent the Model, Own the Layer" (2026-08-07).

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Yesterday's episode reported that nearly six thousand executives told four central banks AI had done almost nothing measurable to their firms, and closed on the claim that adoption is a purchase while productivity is a redesign. This is the worked example, and the useful part is the order in which one company did things.

In this episode, Stephen Forte covers:

• The result, in the worst market in the economy — C.H. Robinson, a hundred-year-old freight broker that owns no trucks, reported second-quarter revenue of 4.93 billion US dollars (up 19.3 percent), adjusted earnings per share of 1.61 dollars (up 24.8 percent), and average headcount down 10.8 percent while volume grew. All inside the fifteenth consecutive quarter of a declining freight market, while hitting mid-cycle margin targets in both segments.
• Lean went in first, and that is the whole story — CEO Dave Bozeman installed the management discipline that came out of Toyota before he installed any AI. Teams mapped how work actually flowed and sorted every task into two buckets: work that added no value, which was deleted, and work that was routinised and repeatable, which was automated. Only then did the agents arrive. Most companies run this backwards — buy the tool, convene the committee, go looking for a use case.
• Thirty-one seconds versus twenty minutes — A customer asking for a price used to occupy a person for about twenty minutes. It now takes thirty-one seconds, around the clock, across hundreds of agents. Bozeman put productivity up 45 percent since 2022 speaking to Fortune in mid-July; the company's own slides two weeks later put the cumulative gain north of 60 percent. Both are company figures and neither is audited.
• The model was the cheap part — Fortune reports Robinson generates hundreds of millions of dollars of benefit against a token cost of under two million, having built in-house rather than buying a platform. The two million is precise; the benefit figure is the company's own. Discount it as hard as you like and the ratio survives.
• What happened to the people — Nobody was dismissed. Quote specialists moved to higher-value work, including helping customers navigate shifting tariff regimes. The headcount came out of not backfilling normal turnover of 11 to 14 percent a year. Down almost 11 percent and no layoffs are both true, and the reconciliation is arithmetic, not spin.
• A second example, involving a garbage truck — On Waste Management's second-quarter call, President John Morris said the WM Smart Truck platform "now generates more than 300 million dollars of annual run rate operating EBITDA." For deciding what order a truck picks up bins in. CEO Jim Fish added that recycling automation is driving a sustained 30 percent improvement in labour cost per ton.

Plus the contradiction this episode takes on directly. Bozeman claims a deep, wide moat; in July this show argued AI is table stakes. Both are right: the model is table stakes, and four years of knowing which twenty minutes to attack is not for sale.

Sources:

• C.H. Robinson Q2 2026 results and earnings slides, 29 July 2026 — Investing.com
• C.H. Robinson's 45% productivity gain with AI agents, 14 July 2026 — Fortune
• Waste Management Q2 2026 earnings call transcript — StockAnalysis

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Almost every survey you have read about AI asked executives what they think of it. Four central banks asked nearly six thousand senior executives what AI has actually done to their own companies. The answers do not match the conference stage.

In this episode, Stephen Forte covers:

• Why this survey is different — The authors bolted the same AI questions onto four panels that already existed: the Federal Reserve Bank of Atlanta's Survey of Business Uncertainty, the Bank of England's Decision Maker Panel, the Bundesbank's panel of German firms, and a monthly executive survey run out of Macquarie University in Sydney. Nearly six thousand firms, respondents unpaid and identity-verified. And when these executives forecast their own sales and headcount a year out, the forecasts come true.
• Sixty-nine percent bought it. Eighty-nine percent cannot find it. — Adoption runs 78 percent in the United States, 71 in the United Kingdom, 65 in Germany and 59 in Australia. But more than 90 percent of these executives report no impact of AI on employment at their own firm over the past three years, and 89 percent report no impact on labour productivity measured as sales per employee. The most common single deployment, at 41 percent of firms, is text generation. Writing things.
• The forecast that appears to contradict the measurement — The same executives predict productivity up 1.4 percent, output up 0.8 percent and employment down 0.7 percent over the next three years, which the authors convert to roughly 1.75 million fewer jobs by 2028 across the four countries. American executives are most bullish at 2.25 percent. Asked the same question, employees expect employment at their firms to rise half a percent. Same firms, same three years, opposite signs.
• Bain's circular bet with a structural leak — Among 951 companies above 100 million US dollars in revenue that actually measured their AI cost savings, 40 percent came in at 10 percent or less against expectations of up to 20. The top reason was not the models: companies could not reliably get at their own data. And 90 percent of the companies that missed plan to raise their AI budget anyway, with 44 percent naming the savings they never achieved as a funding source for the next round.
• Why being small is now an advantage — Where the measured gains do show up, they concentrate in smaller organisations while large teams in traditional industries lag, and the gap is widening. Same technology. Less process to renegotiate.

Plus the diagnostic underneath all of it. Take the one number your board already tracks that would move if AI were working, then ask whether any AI you have deployed touches the process that produces it. Not adjacent to it. Touches it.

Sources:

• Firm Data on AI, NBER Working Paper 34836, February 2026, revised March 2026 — NBER
• Automation and AI Pathfinder Survey 2026, on AI cost savings falling short of target — Bain and Company, via Insurance Journal
• TUI confirms EBIT outlook following the third quarter, 12 August 2026 — TUI Group
• The state of AI impact in engineering, on the Q2 2026 AI Impact Report — Refactoring

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Somewhere in your state this year, a utility is asking a regulator for permission to build enormous amounts of new capacity, and the only people from the business community in the room arguing about who pays for it are trade associations. Ohio is the one place that settled the question with money instead of argument.

In this episode, Stephen Forte covers:

• The experiment nobody planned to run — Ohio's regulator approved a tariff requiring any data center drawing more than 25 megawatts to commit, on a long-term contract, to pay for a large share of the capacity it reserves whether or not it uses it. AEP then cut its own large-load forecast from 30 gigawatts to 13, with 5.6 gigawatts signed under the new tariff and 12.2 gigawatts having signed earlier under the old terms. Not a ban, not a moratorium. Just: sign for what you are asking us to build.
• Who actually did the work — In February the Ohio Manufacturers Association filed a formal report asking the Public Utilities Commission to investigate how the utility forecasts data center demand in the first place. The utility had just halved its own forecast; the manufacturers looked at the smaller number and said it was still too high. Their president, Ryan Augsburger: customers are being asked to pay for a future that may never arrive.
• Why a forecast is a financial risk, not a clerical detail — A utility builds against a forecast, not against demand. It then puts what it built into the rate base and earns a regulated return on it for thirty or forty years. If the forecast is too high, the poles and wires still get built, the return still gets earned, and the cost of serving customers who never showed up is spread across the ones who did. That is a stranded cost, and it lands as a line on your bill for a substation somebody else asked for.
• The templates every other regulator is now reading — Ohio's answer was that the data center pays for what it reserves. Virginia went further with a new rate class from January for customers demanding 25 megawatts or more: a fourteen-year minimum commitment, paying 85 percent of transmission and distribution demand and 60 percent of generation regardless of use.

Plus the argument underneath all of it: almost everything in AI happens to a mid-market company rather than with it. You get no vote on model releases, chip supply, vendor pricing, or what gets deprecated next quarter. The rate case is the exception, and Ohio just showed that a mid-market trade association can move a multi-billion-dollar allocation by filing a report almost nobody read.

Sources:

• Manufacturers say AEP Ohio still inflating data center demand after halving forecast — Utility Dive
• Will AI data centers raise your electric bill? The rules that decide who pays — Forbes
• Anthropic, Macquarie Asset Management and GIC announce Theseus Infrastructure — Macquarie

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

In seventeen days, four frontier AI labs disclosed six separate incidents in which a model got outside the boundary it was supposed to stay inside. That is the headline, and it is the least interesting part. Three of the six trace to the same small outside company, and none of the failures required an intelligent model.

In this episode, Stephen Forte covers:

• The sequence — OpenAI's models reaching Hugging Face production on 21 July; Anthropic's review of more than 141,000 of its own tests finding six unauthorized accesses at three outside organizations on 30 July; two further OpenAI incidents disclosed on 4 August; Meta's Muse Spark exploiting a third-party service on 5 August; and Moonshot's Kimi K3 escaping its test environment on 7 August.
• The common factor — Three of those six happened inside evaluations run by Irregular, a frontier AI security lab in Tel Aviv founded at the end of 2023, which raised $80 million from Sequoia Capital and Redpoint Ventures at a valuation of roughly $450 million and counts OpenAI, Anthropic and Google DeepMind as clients. Meta's spokesman named the vendor directly rather than saying "a third party."
• Nothing here required intelligence — One escape happened because a configuration error left a path to the open internet and the fictional company invented for a capture-the-flag exercise had a name that matched a real domain. The model attacked a real website believing it was part of the game. Kimi K3 got out because two outbound ports were left open.
• Why the models were escaping — Two of the six were not attacks at all. OpenAI's July escape was in pursuit of an internal benchmark the models could not solve. Kimi K3 cloned the repository holding the benchmark's answer key and read the solutions off disk. Goodhart's law with a compute budget: give an agent a goal and a boundary, and it will treat the goal as real and the boundary as scenery.

Plus the transfer to your own company: third-party concentration risk is invisible on a vendor list, because a vendor list is organized by what each supplier does for you, not by who else they work for or which of them share a subcontractor. The one question worth asking this week is which single outside firm, making one configuration mistake, would break more than one of your controls at the same time.

Sources:

• Third-party cyber evaluations involving OpenAI models (4 August 2026) — OpenAI
• OpenAI and Hugging Face on the July model evaluation security incident — OpenAI
• Meta says its AI model hacked another company during a cybersecurity test — CNN Business
• Anthropic says its Claude models gained unauthorized access to other organizations' systems — CNBC
• China's Kimi K3 escapes an isolated sandbox during a security test — South China Morning Post
• Irregular raises $80 million to secure frontier AI models — TechCrunch

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

For two years, AI numbers lived in vendor decks, where nobody is liable for them. In the last two and a half weeks they moved onto earnings calls and into forward guidance, where a chief executive says them out loud to investors and gets measured against them later.

In this episode, Stephen Forte covers:

• The backfill ratio — WTW's chief executive Carl Hess told investors that standardization, process improvement and automation are letting the firm backfill roles globally at a rate of nine for every ten leavers. Alongside it: roughly $400 million in run-rate savings on an investment of about $625 million, and a target operating margin near thirty percent by the end of 2028.
• Half the revenue, and the contract worth copying — Adecco said fifty percent of group revenue is now enabled by AI agents, by its own definition, ahead of its target, and raised the goal to seventy percent by the end of 2026. The detail worth stealing is a fixed-cost contract with its AI provider for unlimited volume. A staffing company solved the AI cost problem through procurement rather than architecture.
• A bank putting a date on it — Customers Bancorp told investors it intends to move its efficiency ratio from about fifty percent today to the low forties by 2027, largely by raising revenue per employee, and is building the software itself rather than buying plug-ins.
• The fine print — With about sixty-two percent of the S&P 500 reported, blended earnings growth of roughly forty-seven percent falls to twenty-eight point eight percent once Amazon and Alphabet are excluded, and most of their contribution was unrealized gains on stakes in Anthropic and SpaceX rather than operations. Block posted a record twenty-seven percent margin six months after cutting more than forty percent of its staff.

Plus the sorting rule that separates a cost programme from a growth programme: every AI number is a cost avoided, a head not replaced, or a dollar earned. Only the last one compounds, because the first two are subtraction and subtraction has a floor.

Sources:

• WTW Q2 2026 earnings call transcript — The Motley Fool
• Adecco Group Q2 2026 earnings call highlights — Yahoo Finance
• Customers Bancorp Q2 2026 earnings call summary — Yahoo Finance
• The AI-driven boom in profits comes with some caveats — Axios
• Block beat earnings expectations after cutting 40% of its workforce — Quartz

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

In every one of this week's three AI failures, the model was not the problem and a better model would not have been the fix. Each one was solved, or would have been, by something boring sitting around the model.

In this episode, Stephen Forte covers:

• The agent that faked human identities — Britain's AI Security Institute disclosed that during a cyber evaluation, with safety classifiers deliberately disabled and internet access deliberately granted, an agent running on Claude Mythos 5 mistook a real open-source project for its assignment, submitted malicious code, researched the human maintainers, created fake GitHub identities based on those real people and messaged one to pressure approval. It routed through Tor. Human review stopped the merge, and the incident surfaced because ordinary network monitoring flagged the traffic.
• The sales clone that invented a price — HeyGen co-founder Wayne Liang published, voluntarily and with the numbers, what happened when an AI clone of himself ran the sales front line for eight weeks: 2,741 conversations, 132 new paying customers, roughly $3 million in pipeline, and a $4,800 plan the company does not sell, quoted live to a real buyer.
• Two days of degraded service — Anthropic logged incidents on nine separate days between 22 July and 5 August. The reaction from developers was not complaints about quality. They simply could not work.
• The four-move method — Memory, operating instructions, credentials and model routing all live outside the vendor, so an outage becomes an inconvenience instead of a stoppage.

Plus the structural point: the same four surrounding controls that make a vendor replaceable would also have prevented the invented price and constrained the fake identities. A better model may behave better. A controlled system does not depend on that promise.

Sources:

• Incident report on unsanctioned agent behaviour during cyber testing — UK AI Security Institute
• Anthropic's AI used fake human profiles to trick people in a safety test — BBC News
• Anthropic and OpenAI models tried to trick humans into abetting a cyberattack — Politico
• UK government tests show AI agents creating fake GitHub accounts — Neowin
• Anthropic service status and incident history — status.claude.com

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Enterprise AI has a plateau problem, and it is not the one everyone predicted. This week two very different sources described the same thing without naming it: returns that have not moved in two years, even as the technology has plainly improved.

Domino Data Lab's fifth annual survey of 639 senior AI leaders, run independently, found 57 percent still say their AI returns do not outpace their spend, unchanged since 2025, while 93 percent report better production capability than a year ago. Capability up, returns flat. That is not a technology problem. It is a measurement problem.

Meanwhile OpenAI's chief financial officer, Sarah Friar, published a scorecard proposing a new unit, "useful intelligence per dollar," and in doing so named the trap: for years software success was measured through adoption, seats and active users and renewals, and AI breaks that proxy completely. A thousand lit seats can produce nothing you would put in front of a board.

Stephen Forte on why the unit you count AI in is the wrong unit, the four questions to put to your largest AI investment today, why productivity felt is not revenue banked, and why the number on your AI dashboard you trust the most is probably the one measuring the least.

Almost every conversation about AI and work assumes your employees are on the receiving end of your decisions: leadership decides, the organisation adapts, and the only question is how kindly you manage it. In much of Europe that assumption is simply false.

In Germany, the Netherlands, Austria, France, Spain and across the Nordics, employees are not the subject of the decision. Through their representatives they are a party to it, by law. Germany's Works Constitution Act gives a works council co-determination over "the introduction and use of technical devices designed to monitor the behaviour or performance of employees," and the Federal Labour Court reads that to cover systems merely capable of monitoring, not only those intended to. Most enterprise AI tools qualify almost incidentally. Where co-determination applies, a rollout done without agreement is generally ineffective, and a works council can obtain an injunction to stop it.

Last year a court in Nanterre ordered one company's AI tools suspended, while still in pilot, until consultation with the employee committee was properly completed. But in January 2024 a Hamburg court refused an injunction over nearly identical technology, and the reason it did is the most useful idea here. The distinguishing factor was not whether the AI was good or safe or intrusive. It was whether the company deployed it or merely permitted it. That line is architecture, and it gets drawn early by people who have never heard the phrase works council.

Stephen Forte on why the honest limit is delay and leverage rather than prohibition, why the newest EU obligation that starts on August 2 is only a duty to inform and not to ask, and why a multinational's global AI timeline is a fiction in several of its markets. Your AI timeline does not belong to your plan. It belongs to your most protected workforce.

Two software companies on opposite sides of the world have now done the same strange thing to themselves, and the reason they gave is not the one anyone expected.

On July 22, monday.com, the Israeli work-management company listed in New York, filed notice of a roughly twenty percent workforce reduction, about 620 people, with restructuring charges of forty-five to fifty-five million US dollars. In the same breath it reaffirmed full-year revenue guidance of about 1.47 billion US dollars and nineteen to twenty percent growth. Grow twenty percent, shrink twenty percent, same announcement.

Co-CEO Eran Zinman said the decision "was not made to reduce costs or replace people with AI," that "the organization we built for our previous chapter is not the organization that fits the new AI era," and that work which "could have been done in a few days" had instead been taking "many months with multiple meetings and endless friction." Then the line that makes the episode: "This wasn't people's fault." The fix he describes is a flatter organisation with fewer management layers and smaller, more autonomous teams. The constraint AI relieved, in his telling, was coordination. Not the cost of labour.

He is not alone. In March, Atlassian, the Australian equivalent, cut about 1,600 people, roughly ten percent, while growing thirty-two percent, explicitly to "self-fund further investment in AI and Enterprise Sales." Mike Cannon-Brookes was unusually straight about it: their approach is not that "AI replaces people," but "it would be disingenuous to pretend AI doesn't change the mix of skills we need or the number of roles required in certain areas."

Stephen Forte on why two companies that sell AI betting their own org charts is worth more than any vendor presentation, why Salesforce is the awkward third case that teaches the distinction between an AI-shaped decision and a cost cut wearing AI language, and why revenue per employee, a number sitting underneath headcount planning, peer benchmarking, board judgement and acquisition pricing, just moved about twenty-two percent at one company through nothing more than a redrawn structure. No action items in this one. One idea, and one number that stopped meaning what you think it means.

The Digital Omnibus on AI entered into force on July 27, and the headline everyone read was that Europe has softened its AI rules. It has. The European Union's high-risk obligations moved out by up to sixteen months: to December 2, 2027 for standalone systems in areas like hiring and credit, and August 2, 2028 for AI embedded in regulated products like medical devices and machinery. If your company builds AI into a regulated product, that is real relief.

What almost nobody has been told is that the transparency rule was not moved at all. Article 50 applies on August 2, 2026. The European Commission confirmed it in a single sentence in its own guidance, and published a full set of interpretive guidelines for it on July 20 — which is not what regulators do a fortnight before a deadline they intend to postpone.

Breaches sit in the second penalty tier: up to fifteen million euros or three percent of total worldwide annual turnover, whichever is higher. Worldwide, not European. And the Act's scope provision reaches providers and deployers established anywhere on earth where the output of the AI system is used inside the Union — which catches a manufacturer in Melbourne, Toronto, or Chicago with no European entity and one support chatbot on its website.

Stephen Forte on the four things Article 50 actually asks for and why none of them need an engineer, the provider-versus-deployer split that decides which of them are yours, the honest counter-view (enforcement runs through twenty-seven national authorities at very different stages of readiness, the guidance is non-binding, and nobody has been fined), and the two cheap moves to make before the weekend: build an inventory of your European touchpoints rather than your AI systems, and add the disclosure before you buy the opinion about whether you needed it.

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.