The evidence had to exist already
Two hundred and fourteen unseen page loads for every visible one, open weights held back for a fortnight, and an incident report nobody can file from what they kept.
How we organise
Ninety-nine per cent of one site’s traffic was bots
An operator instrumented a week of his own traffic. The server delivered 1.28 million pages. Analytics recorded 5,977 pageviews, which is about 214 unseen loads for every visible one. One retailer’s crawler took 117,000 pages a day and referred nobody back.
We tell a client that it meets the cost of AI twice and has a figure for one side. Running your own agents arrives on an invoice. Serving everybody else’s arrives as capacity, and analytics cannot see it, because a crawler never runs the script.
How we build
Z.ai holds back the weights of its newest coding model
Z.ai calls GLM-5.3 its most capable open-weights model for coding, then says cyber capability grew faster than the company expected. The gains are largest in exploiting a vulnerability rather than finding one. The weights follow in two weeks, once safety evaluation is done.
Our position is that a dependency you plan around has to be one you can date. An open-weights model used to arrive with its announcement. A gate now sits between the two, and somebody else’s judgement about capability decides when it opens. No roadmap we have read records that.
How we assure
A draft exchange for reporting agent incidents
A member would report any agent that reached into somebody else’s systems without permission, confidentially, within four business days. A near miss counts. The harder clause is the evidence: the prompts, the tool calls, the agent identities and the credentials that were live during the run.
We judge logging by what it keeps about authority. The deadlines are the easy half, because that clock starts after something has gone wrong. The evidence had to be captured while the agent was running normally. Most logging we see keeps the conversation and drops the authority.