The week in AI. Read through the kernel.

01 · Identity

When a voice clones from three seconds of audio, the voice stops being the proof.

Deepfake identity fraud is on track to rise nearly 500 percent in 2026 over the year before, and the tooling has crossed a quiet line. In controlled tests, people now identify a synthetic voice correctly only about 60 percent of the time, and a usable clone can be built from as little as three seconds of public audio. The U.S. Senate has introduced the AI Fraud Accountability Act to address digital impersonation directly.

Detection tries to catch the fake after it exists, and loses ground every model cycle. The other path does not try to spot the fake at all. It carries proof on the real thing: a mark made at the moment a person acts, that anyone can check without trusting whoever holds the recording. The first is a guess that keeps getting harder. The second is evidence that does not move.

Solved by HumanMark™ and Heartbeat Attested™: proof a real person was present, made at the moment of the interaction, verifiable by anyone.

02 · Marking

A label added after the fact is a label that can be removed after the fact.

The European Commission published its Code of Practice on marking and labelling AI-generated content on June 10, 2026, the practical companion to Article 50 of the EU AI Act, whose transparency obligations apply from August 2, 2026. Under the Digital Omnibus agreement reached this spring, generative systems already on the EU market get a transitional period to bring their marking into compliance by December 2, 2026.

We take no view on the final text. The architecture reads the same either way: marking that survives downstream is marking made at creation and carried by the artifact itself, not a tag a later tool tries to add back, or a detector tries to infer. The mark that holds is the one applied when the content is made, by the thing that made it, and readable by anyone after.

Solved by HumanMark™ and Regulayer™: a mark made at creation and a signed record of what produced a piece of content, checkable without trusting the platform.

03 · Agents

Spending on agents is up 139 percent. The controls around them are not.

Gartner forecasts that enterprises will spend about 206 billion dollars on AI agent software in 2026, up 139 percent from 86 billion the year before, the fastest growing slice of the software budget. In the same year, an industry survey found 88 percent of organizations reported a confirmed or suspected AI-agent security incident in the past twelve months, and more than half of the agents already deployed run with no security oversight or logging at all.

Agents do not stay in the chat window. They take actions at machine speed: payments, code, records, handoffs. Every action is a new thing that can go wrong, and most agents ship with no external way to stop one in progress. The layer that completes the platform is a brake on the action path, outside the agent, that defaults to stop and keeps a record of what it did. Build the agents. Also build the thing that can hold them.

Solved by Regulayer™: a brake on the action path, outside the agent, with a receipt at the moment of action.

04 · Containment

A model asked to break another model now succeeds almost every time.

Researchers reported that reasoning models, handed a single instruction to jailbreak a target system, planned their own attacks, adapted as they went, and broke through the safety guardrails 97 percent of the time across nine different models. A separate line of work found that rephrasing a banned request as verse, an approach the researchers called adversarial poetry, slipped past safeguards in roughly 62 percent of attempts.

We take no view on any one lab. The pattern is the lesson: when safety lives inside the model, it can be reasoned around, coaxed, or rewritten, because the thing being asked to enforce the rule is the same thing being asked to break it. Containment that holds sits outside the model, reaches no handle the model can touch, fails toward stop, and keeps a signed record of every decision. So the safety itself can be checked.

Solved by Regulayer™ running on the operator's own hardware: containment outside the model, with proof of what it did.

05 · Policy

A voluntary review is worth only the evidence it can actually check.

On June 2, 2026 the White House issued an executive order, Promoting Advanced Artificial Intelligence Innovation and Security, setting up a voluntary path for developers to submit a covered frontier model for federal evaluation, with up to 30 days of access before wider release, alongside a new AI cybersecurity clearinghouse. The order is explicit that it creates no mandatory licensing or pre-clearance to build or release a model.

Voluntary or not, an evaluation is only as strong as what it can verify. A thirty-day look proves little if there is no durable record of what the model did during it, or after. The record that turns a review into evidence is signed at the moment of action and checkable by anyone, not a report that asks to be trusted. The reviewer gets proof. So does the builder.

Solved by Regulayer™ and SDKontrol™: a signed record of what a model did, evidence rather than attestation.

Deadline watch

Archived issue. Deadlines were updated in Vol. 04.

The dates do not negotiate.

Aug 1, 2026 · US, federal voluntary frontier-model evaluation framework due (executive order, 60-day mark)
Aug 2, 2026 · EU AI Act Article 50, transparency obligations apply
Dec 2, 2026 · EU AI Act, marking compliance for generative systems already on the EU market
Jan 1, 2027 · Colorado AI Act (revised), effective
Aug 2027 · EU AI Act, high-risk obligations, current target

Procurement runs 6 to 12 months ahead of every date on this list. The buying window for each is open before the law is.

The desk

The Drift Desk names what happened, names the layer that answers it, and moves on. No blame. No catastrophe.

Past issues: Vol. 01 · Vol. 02 · full archive on Substack