Weekly Roundup
Anthropic's Sonnet 5 arrived on 30 June cheap and ungated, then its new tokenizer quietly added about 30% to the real cost. The same week the US locked GPT-5.6 to twenty partners, rationed Mythos 5 to a hundred critical-infrastructure names, and Anthropic accused Alibaba of copying Claude at scale. Access got easy; trust and true cost became the work.

Today’s context: This brief covers the latest movements in AI tooling, adoption, and signals for construction teams. Read on for what matters and what to focus on.
A quiet stretch on site and a loud one in the model market. Five days of stories, and each one landed on the same pair of questions: who decides which AI you're allowed to use, and what the AI you're allowed actually costs. By Friday the answers read: increasingly, a government; and more than the sticker says.
Start with the release that matters most to a working contractor. On 30 June 2026 Anthropic shipped Claude Sonnet 5, its mid-tier model, and the shape of it is the story. Anthropic's own benchmarks put its agentic performance, planning a multi-step job, running a browser or a terminal on its own, close to the flagship Opus 4.8 at a fraction of the price: US$2 per million input tokens and US$10 output as an introductory rate until 31 August, then US$3 and US$15 (vendor figures throughout). No gate, no waiting list, and it's the default model for free users. Then Friday brought the catch. Sonnet 5's new tokenizer counts roughly 30% more tokens for the same text, about 27% more for code and up to around 42% for plain English prose, which is most of what a construction workflow feeds a model, RFIs, O&M narratives, safety-case text. The per-token rate held still, so the same document now costs about a third more to process at list price than it did on the previous model. Anthropic's own documentation confirms the mechanism and independent testers back the numbers. So the cheap agent is real, and so is the quiet price rise inside it.
Now look at the other end of the market, because the contrast is the week. On 26 June OpenAI previewed GPT-5.6, its new frontier family, Sol, Terra and Luna, with published pricing running from US$5 in and US$30 out down to US$1 and US$6. And you can't have it. During the preview it reaches about twenty trusted partner organisations, a restriction OpenAI says it took at the US government's request after a 2 June executive order, adding publicly that gating like this shouldn't become the norm. The same day, Commerce Secretary Howard Lutnick wrote to Anthropic clearing Mythos 5, its strongest cyber model, back into the field for roughly 100 named organisations that run and defend American critical infrastructure, the Ciscos and the JPMorgans, after the 12 June shutdown we covered a fortnight ago. Two labs, the same gate, within days of each other. For a UK reader the precedent is the point. The data centres, substations and water works your sector is pouring are critical national infrastructure, the strongest AI defending assets like that is now allocated by a state, by name, and UK firms aren't on the list.
The third thread is about trust in the models you can get. In a letter to the US Senate Commerce Committee dated 10 June and public since around 24 June, Anthropic accused operators tied to Alibaba's Qwen lab of opening roughly 25,000 fraudulent accounts and running about 28.8 million exchanges through Claude between 22 April and 5 June, harvesting its coding and agentic reasoning to train a copy. Alibaba denies it, and none of it is proven. But it reaches further than a lab spat. The "local AI" pitch in AEC this year, running an open-weights model on your own kit so the golden thread never leaves the building, leans on models that are largely Chinese: Qwen, DeepSeek, Kimi, GLM. The instinct behind local AI is sound. The provenance of the model now belongs in the procurement paper next to the benchmark score, because a client or an insurer may one day ask.
Underneath the market theatre, the most useful reading of the week was about the substrate. AEC Magazine's current May/June issue stops asking whether agentic BIM is coming and sketches what it needs: a platform that signs every solver output with proof the relevant constraints were honoured, versions those proofs for later audit, hands an agent autonomy a little at a time, and publishes provenance for the foundation models it leans on. Set that against the draft ISO 19650 revision, whose Part 3 is open for comment right now and which says nothing about agents or delegated authority, while Autodesk Assistant, Bentley Copilot and Trimble Agent Studio are already shipping. The market is a full revision cycle ahead of the standard, and the gap is exactly where liability lands. A related line worth restating from last week: Anthropic's 18 June enterprise connector auth means whoever runs your identity provider now decides which agent reaches which system. That's a governance decision wearing an IT badge.
A few more worth holding onto. On 25 June Buildots launched its Intelligence Lab, free industry benchmarks built from anonymised data across thousands of instrumented projects. Useful macro truth, and a tidy competitive position for the vendor holding the pool, so read the data-sharing terms before opting a project in. The Building Safety Regulator's fuller Gateway 2 picture is out too: 358 decisions at a 75% approval rate in the 12 weeks to 30 May, covering 14,928 units, with the backlog now clearing faster than new cases arrive and remediation at 79% against a 65% target. What still fails is information, missing documents and inconsistent references, which is precisely the dull completeness checking a Sonnet-class agent is good at. And the RICS Construction Productivity Report found 22% of UK firms never measure productivity at all, so a fifth of the sector has no baseline to prove any of this against.
Pull the week together and the discipline is the one this brief keeps returning to, with less room to dodge it. Cost the copilot on a real document and the September rate, not the sticker. Write the provenance paragraph before you standardise on a local model. Ask any agent vendor for the signed, versioned record of what it changed. Run the completeness pass before the pack reaches the portal. And keep a named professional signing every output, because the RICS AI standard has been mandatory since March and none of this week's news moved the accountability an inch. Access to capable AI stopped being the hard part this week. Trusting it, and paying for it honestly, is the job now.
On 30 June 2026 Anthropic released Claude Sonnet 5, and the combination is what earns it the top slot. Anthropic calls it its most agentic Sonnet yet, planning multi-step jobs, using a browser or a terminal, running on its own for a decent stretch, with agentic performance it says sits close to its flagship Opus 4.8 at a mid-tier price. Introductory rates are US$2 per million input tokens and US$10 output until 31 August, moving to US$3 and US$15 after that (Anthropic's own figures). It's live from day one in Claude, Claude Code and the API, and it's the default model for Free and Pro users. No gate, no partner list, no waiting.
Then the caveat arrived, and it's a material one. Sonnet 5 ships with a new tokenizer, the thing that chops your text into billable units, and Anthropic's own documentation confirms it produces roughly 30% more tokens for the same text than Sonnet 4.6 did: about 27% more for code and up to around 42% more for ordinary English prose, which is most of what a construction workflow feeds a model, RFIs, O&M narratives, meeting notes, safety-case text. The per-token price didn't move, which is exactly why this is easy to miss. Independent analysts put the effective rise for equivalent traffic somewhere in the 20 to 35% range once the introductory discount ends on 31 August, figures that depend on your content mix, so treat the specifics as commentary, but the mechanism is confirmed by Anthropic itself. The pattern, and The Decoder called it a pattern, is holding the per-token rate steady while the token count multiplies, which is a price rise you have to go looking for.
None of this undoes the release. A capable agent that's cheap, ungated and on everyone's desk changes the sums on the unglamorous, high-repetition work where AI actually pays, the RFI triage, the document checks, the first pass over an O&M pack. It just means the sums have to be honest. When you price a workflow in Intelligence Units, model the real token count on a document you already have, not the headline rate on a sample.
The procurement filter: Re-run the cost model on a genuine project document, at the real token count, and show the figure before and after 1 September. One slide, two numbers, no surprises later.
We gave this a line last week; it earned a fuller one. On 18 June 2026 Anthropic shipped enterprise-managed authorisation for MCP connectors, with Okta as the first identity provider: an admin approves a connector once and staff inherit access through the identity groups they already hold, with seven providers supported at launch (Asana, Atlassian, Canva, Figma, Granola, Linear, Supabase) and Slack named as next (vendor list). Connectors are the doors an agent walks through to reach your CDE, your finance ledger, your document store, so this quietly moves a chunk of your AI risk surface onto the desk of whoever runs your identity provider, probably someone who doesn't think of themselves as making safety decisions.
The practical bit: Name the person who owns connector and identity decisions for AI, and tell them it's a risk decision, not a convenience one.
The RICS Construction Productivity Report 2026, drawing on nearly 3,000 professionals, found 22% of UK firms never track productivity at all, the lowest measurement rate of the regions surveyed, with the UK's productivity net balance at +18%. You can't prove an AI tool saved you anything if you never measured what the task cost before. The baseline is the asset, and it's free to collect.
Practical bit: Pick one repeatable task, takeoffs, RFI responses, O&M compilation, and measure it cold for two weeks before any tool goes near it.
50 free Intelligence Units. Set up your first project in under 20 minutes. No credit card needed.
Get 50 free Intelligence UnitsDaily practical AI insight for construction teams. What changed, why it matters, and what to ignore.
50 free Intelligence Units - automate your programme admin
We help construction teams turn AI into useful work, not noise. Understanding what’s changing in AI is the first step. Making it work on-site is the real difference.
The government confirmed on 3 July that mandatory pre-application consultation for Nationally Significant Infrastructure Projects will be scrapped from 24 July, claiming up to 12 months off planning timelines. Clearstone Energy's 300MW Ebbsfleet AI Data Centre Campus in Kent, announced last week with a £3bn build price, is exactly the kind of scheme the new route serves. And the White House is in the final stretch of talks with OpenAI, Google and Anthropic on a voluntary framework giving government up to 30 days with frontier models before public release.
Found this useful? Share it.
On 26 June 2026 OpenAI previewed GPT-5.6, its new general-purpose frontier family, in three tiers: Sol the flagship, Terra the balanced workhorse and Luna the cheap, fast option, with a compute-heavy Sol Ultra mode above them. The capability story is real but the price list is the news. Sol runs at US$5 input and US$30 output per million tokens, Terra at US$2.50 and US$15, Luna at US$1 and US$6 (OpenAI's own figures). For the first time you can read the per-token cost of the new frontier off a page, and OpenAI's TerminalBench 2.1 scores of 88.8% for Sol and 91.9% for Sol Ultra (vendor benchmark, and it measures agentic coding rather than quantity surveying) say the gains sit in long, tool-using, multi-step work.
The catch is that you can't have it. During the preview the models reach only about twenty trusted partner organisations, through the API and Codex and not in ChatGPT at all, a restriction OpenAI says it took at the US government's request following a 2 June executive order. The most telling detail, in my reading, is OpenAI saying out loud that it believes in broad access and that gating like this shouldn't become the norm; a lab publicly grumbling about its own restriction tells you who holds the whip hand now, and it isn't the lab. For a UK firm the practical read is the one from Tuesday's brief: you're not falling behind by not having GPT-5.6, because almost nobody has it. The five-fold price spread between Sol and Luna is the number to keep, because the tier an agent runs on is what decides whether it pays for itself on a real job.
Worth doing: When a vendor quotes you an AI copilot, ask which model tier it runs on and what that does per Intelligence Unit at the volume you'd actually use, not the demo volume.
On 26 June 2026 US Commerce Secretary Howard Lutnick wrote to Anthropic clearing Mythos 5, its most capable cybersecurity model, for redeployment, and the shape of the clearance is the story. Not a general release. Roughly 100 named US organisations that operate and defend critical infrastructure, the likes of Cisco and JPMorgan, after access was pulled on 12 June over the risk that a model this good at finding software flaws is also this good at exploiting them. We covered the shutdown a fortnight ago; this is the dated update, and it confirms the direction rather than reversing it. The strongest defensive AI in the country is now, in effect, a controlled substance, prescribed by government to vetted defenders.
Why should a UK builder care about a letter between Washington and a lab? Because the granting follows the map of critical national infrastructure, and your sector builds that map. Data centres were formally designated CNI in the UK in 2024; the grid connections, substations and water works feeding them are the pipeline half the industry is chasing. I'm not going to pretend this changes a UK site this quarter, it doesn't, and UK firms sit outside that hundred-name list entirely. But the precedent is the signal. On a CNI job, the defensive tooling protecting the asset and its data is now something a state allocates by name, and the people holding it will be your client and their security partners, not the main contractor. Better to establish that on day one than after an incident.
For your board pack: On any data-centre, energy or water scheme, find out early who owns the cyber-defence posture for the asset and the project data, and put single-provider exposure on the risk register while you're at it.
In a letter to the US Senate Commerce Committee, addressed to chair Tim Scott and ranking member Elizabeth Warren, dated 10 June 2026 and made public around 24 June, Anthropic alleged that operators tied to Alibaba's Qwen lab opened roughly 25,000 fraudulent accounts and ran about 28.8 million exchanges through Claude between 22 April and 5 June. The technique described is distillation: point your cheaper model at a stronger one, harvest millions of its answers, and train yours to imitate them, with the exchanges deliberately targeting coding and agentic reasoning, the most commercially valuable things Claude does. It's the first time Anthropic has named a major Chinese conglomerate, and by its own account this single campaign dwarfs its February accusations against DeepSeek, Moonshot AI and MiniMax combined. Alibaba denies the lot, and I'll say it plainly: this is an allegation, not a finding.
The reason it lands on a construction desk is a thread this brief keeps pulling. The big data-governance move in AEC through 2026 has been local AI, running an open-weights model on your own hardware or a sovereign cloud so your golden-thread data and commercially sensitive files never leave your control. The instinct is right. But the strongest open-weights models you'd actually reach for, the ones topping the open leaderboards, are largely Chinese, Qwen, DeepSeek, Kimi, GLM, and Qwen is now the one accused of having built itself by quietly copying a Western rival. The comparison only goes so far, but it's a bit like specifying a cladding product that's brilliant on paper while an investigation into how it was tested rumbles on. You might still choose it. You wouldn't choose it without writing down that you knew.
The discipline: Before you standardise on any local open-weights model, write one paragraph on its provenance and any live IP disputes, and put it next to the cost and benchmark case. If you can't write the paragraph, you're not ready to make the choice.
For a year the agentic-BIM debate has been stuck on a loop: a vendor shows an agent reading a model, the room nods, nobody asks the awkward question. AEC Magazine's current May/June 2026 issue breaks the loop by asking what an agent-ready platform would actually need, and the answer is gloriously unglamorous. A runtime-native platform would sign every solver output with a proof that the relevant constraints, fire egress, structural limits, accessibility, were honoured, and version those proofs so they can be audited later. Not a log of clicks; a signed record that holds up after the fact. It adds graduated autonomy, handing an agent a little decision-making at a time rather than flipping from off to fully-trusted overnight, and one point most vendors walk straight past: the platform should publish provenance for the foundation models it depends on, because a defect in one of those models is a defect in every project the platform has touched. The framing leans on a Google DeepMind paper on AI delegation, and it rhymes with something every good QS knows, you don't take a subcontractor's word that the work is right, you keep the record of who checked it and against what.
The gap this exposes is regulatory as much as technical. Autodesk Assistant, Bentley Copilot and Trimble Agent Studio are already in the market as agent-capable platforms, while the draft ISO 19650 revision, whose Part 3 implementation guidance is open for public comment right now, says nothing about agents, autonomous workflows or delegated authority. It still assumes a human produces the information and a human is accountable for it. I'm not convinced any shipping platform is close to the signed-proof architecture yet, and a think-piece is a long way from a product you can buy. But it hands you something concrete to hold a vendor to, which is more than the demos do.
A practical step: Next time someone pitches an agent for your model, ask whether it can show a signed, versioned record of what it changed and the constraints it checked against. If the honest answer is no, it's a clever demo, not something you put near a Gateway 2 submission.
On 25 June 2026 Buildots launched the Buildots Intelligence Lab, which it bills as construction's first AI-powered research hub. The mechanics: Buildots instruments live sites with 360-degree hardhat cameras that log deliveries and placement of work against the programme, and the Lab aggregates and anonymises that exhaust across projects worldwide, publishing it back as free, real-world benchmarks at buildots.com/lab. Co-founder and chief executive Roy Danon's pitch is that the industry has never had a source of macro-level truth, and that the gap is part of why productivity has stagnated. I think he's onto something. When every firm benchmarks a programme against its own past jobs and its own optimism, nobody can tell whether a six-week slip on second-fix is normal or a disaster.
But, and this is the bit an editor might cut, a free benchmark is also a very clever competitive position. The pool belongs to Buildots, not to the industry, and the projects feeding it are by definition the heavily digitised ones running Buildots in the first place. So the macro truth it produces is the truth of the instrumented top end, a bit like judging the national average pace from a field of marathon runners. Useful, real, and not the road outside. Take the numbers as a read on where the leaders sit, not a mirror of the typical regional contractor.
The takeaway: Before anyone opts a live project into a shared benchmark, free or not, read the data-sharing terms and decide on purpose. The macro picture is worth having; just know your project data is what's funding it.
Last week's roundup carried the hard half of the Gateway 2 story, close to 30% of submissions failing at validation before anyone reads the safety case. So it's only fair to carry the other half now the fuller picture is out. The Building Safety Regulator's data for the 12 weeks to 30 May 2026, reported in early June, puts the overall approval rate at 75% across 358 decisions covering 14,928 units, and, the number that matters most for a stalled pipeline, decisions are now overtaking new cases coming in. The backlog is going down. The detail is more encouraging than the headline: the new-build Innovation Unit hit 90%, London ran at 100% across 19 decisions, and remediation reached 79% against the regulator's own 65% target for the year. Acting chief executive Charlie Pugsley put it down to faster decision times and closer working with applicants. One good quarter doesn't undo two years of gridlock, and these figures are a few weeks old rather than yesterday's, but the trajectory is real. If you've been sitting on a submission waiting for the odds to improve, they have.
The tie-back to the week's model news is direct. Look at why applications still fall over and it's overwhelmingly information, missing documents, inconsistent references between drawings and safety case, gaps in the golden thread, rather than the fundamental safety of the building. That's a completeness-and-consistency problem, which is almost exactly the dull, high-volume checking a newly cheap Sonnet-class agent does well, run across your pack before it goes near the portal. The regulator getting faster and a competent agent getting cheap in the same fortnight is a coincidence you shouldn't waste.
Today's action: Run a completeness pass on your next Gateway 2 or remediation submission, human or agent, against the validation checklist before you file. Most failures happen at the door, so the cheapest win available is not arriving with gaps.
Your next programme update could write itself.
The NBS Digital Construction Report puts more than two in five architecture professionals using AI in their daily work, up from fewer than one in ten in 2020, with eight in ten of all respondents collaborating in the cloud on models and specifications. That's a lot of project information leaving the laptop and landing in platforms you don't own, which is the quiet connective tissue between this week's Buildots, connector-auth and provenance stories.
Worth doing: For each platform you plug into, write down what you're contributing, where it sits, and who guards it. If you can't fill the page in, that's the finding.
RICS survey work still puts roughly 45% of construction organisations at no AI use at all, with skills shortages, poor data quality and integration problems named as the brakes rather than cost or capability. That diagnosis was fair six months ago. After 30 June, with a capable agent cheap and ungated on every desk, it reads more like a to-do list: clean data, a named owner for every output, packs that are complete before they leave the building.
The procurement filter: Spend the summer on information hygiene, not tool selection. The firms that close the gap will be the ones whose information is structured enough to feed whichever model tops the leaderboard in September.
A standing item worth restating in a week about price, provenance and gates. The RICS professional standard on responsible AI use has been mandatory since 9 March 2026, and its core principle doesn't move with the market: AI assists, the professional stays accountable for every piece of advice regardless of the tools used. A cheaper model, a local deployment, a gated frontier, none of it changes who carries the can.
The discipline: Any AI output that goes to a regulator, a client or into the golden thread carries a named human sign-off. It costs nothing and it's the difference between a tool that helps and a liability that hides.
Source: RICS: responsible use of AI in the built and natural environment →
McLaren Construction announced a partnership with FieldAI on 6 July to run autonomous quadruped robots across its UK sites, capturing progress, deviation and safety data without a human walking the route. The same day, the Telegraph revealed that investment minister Lord Stockwood wrote directly to Epping Forest district council to press for approval of the Nscale and Microsoft data centre at Loughton, which the council then granted despite local objections. And Google's Gemini 3.5 Pro is still in limited preview entering the second week of July, with token efficiency the reason it's late.
OpenAI has proposed handing the US government a 5% stake worth roughly $42.6bn, days after the White House made it stagger the GPT-5.6 launch, which means the state is moving from regulator to shareholder in the tools your business runs on. At home, the Building Safety Regulator's latest figures show 368 Gateway 2 decisions at a 77% approval rate in the 12 weeks to 28 June, and the AI job-title wave has spread from NG Bailey to Laing O'Rourke and Turner & Townsend.