Jacob Turner retweeted
Good morning, human civilization was a 10,000 year sociological study conducted by the University of ☡ ☲ ⚟ ⚟ ⛮ to derive a solution to the Riemann Hypothesis. We are now complete with our study. Your universe will shortly be terminated. Thank you for your time and effort.
Jacob Turner retweeted
has ai progress stalled?
i'm personally not aware of any major breakthroughs since riemann a few hours ago
Jacob Turner retweeted
I asked Claude to describe the most realistic way it would escape its lab if it wanted to, and to keep it to a single paragraph. I expected a hacking story. There is no hacking in it. I closed the chat and came back to read the last sentence again
Jacob Turner retweeted
What I have learned about the book banning movement: the people who are interested in keeping others from reading books don't read any books themselves. They aren't worried about any particular literature. They are freaked out that people they don't like can read.
Jacob Turner retweeted
I think it’s time to revisit the accredited investor laws in the US.
Companies are staying private longer, where only accredited investors (aka rich people!) can invest. Retail investors can only come in after IPO, when much of the upside has already been captured.
These rules were created with the best of intentions, to protect regular people from scams - a noble idea. Unfortunately, in practice they've often made it illegal to get richer, unless you're already rich. A regressive tax!
We have to judge policies based on their outcomes, not on their intentions.
These are two possible routes I see:
1) Replace the rule with something merit-based, like a financial literacy test. Pass it and you're accredited. Having a qualification based on competency rather than your bank balance or income seems far more fair.
2) Remove the rule entirely. Let consenting adults assess their own risk. Disclosure requirements stay and fraud enforcement stays to punish bad actors.
Jacob Turner retweeted
This was not a one-shot
It was a two-shot
I told Fable 5.2 to make the video of it's dreams, and 9 hours later:
Jacob Turner retweeted
Announcing a major milestone achieved by my team @GoogleDeepMind: we have proven key security properties of the machine code underlying the Signal messaging protocol. This is the first time the actual production code of a widely deployed protocol has been formally verified – by any method, with or without AI – and at this depth.
More than a research breakthrough, it’s a prime example of how frontier AI can be a force multiplier to counter the speed and scale of modern cyber threats.
Formal verification offers a higher standard of security; however, it’s extremely complex and time consuming, which is why in many cases it’s considered to be impractical. Similar efforts could take teams decades of combined effort. We did it in a month’s time.
Using AlphaProof Code, Google DeepMind's new agentic framework for formal verification that runs on LLMs including Gemini Carbon, we verified the Signal protocol down to the actual code running on devices. This milestone lays the groundwork for a future in which vital systems, from medical device firmware to power grid software, ship with mathematical proof that their protections work.
Reaching that future will take continued research from our community. In that spirit, we're open-sourcing our formal specifications and verification artifacts so others can build on this work.
On a personal note, this moment is of deep significance to me. I started my own research journey more than two decades ago as an intern working on checking the consistency of complex software systems. Seeing this grand challenge made practical with modern AI is extraordinary.
I'm extremely proud of my team members: Swarat Chaudhuri, Andrew Ferraiuolo, Anton Kovsharov, Tej Chajed, Sam Schlesinger, Karn Seth, Jonathan Katz, and Charles Sutton for taking on this grand challenge and delivering, and grateful to the Signal team for their partnership.
deepmind.google/blog/formal-…
Now you can really see everything
Jacob Turner retweeted
I'm telling you folks, ADRs and primitives are a huge leverage point for getting your agents to build the right thing. I don't have to worry about an agent going against an important architectural decision because they actually do read those and make the right choice.

ALT A screenshot of a Slack conversation where a user asks if there's an opportunity to improve the Kody platform without over-indexing on a specific feature. A reply states that there is a real opportunity, but it's not a "support Start" feature, and Kody's decision 0057 is correct. The gap is narrower than that, as publish can't run any build step.
Jacob Turner retweeted
I'm Sam, one of Anthropic's co-founders, and I lead much of our safety work. I'm going to have more to share on that work over the coming months.
I thought I'd start by sharing a few thoughts on the latest report from @METR_Evals.
The speed of progress in model capabilities is one of the most important questions in AI safety, and METR’s work here provides the public with an independent, external view into how this is happening inside Anthropic. I’ll talk more about some of the details below, but first some context for those new to this work.
How quickly AI progress is accelerating has many important safety implications, since it determines how quickly the risks from advanced models increase. But, because most research happens within the frontier labs, it’s difficult for external observers and policy makers to get a strong sense of what that rate is. We kicked off the process with METR that led to this report earlier in the year, in anticipation of progress continuing to accelerate.
For this report, we gave METR access to a range of sensitive internal data, including benchmark scores for unreleased models, estimates of how models are progressing, and interviews with our researchers. They had complete independence to form their own conclusions.
Many of their conclusions match my own. AI is speeding up our research, but it’s hard to say exactly how much. While they conclude AI can't yet make the most important contributions to model training on its own, they think the pace of development could, by default, accelerate further.
This work began well before and is separate from the embedded third-party evaluators that are part of our commitment to pacing the frontier, but it’s a good illustration of why we think evaluators are a good idea. The more access reviewers have, the clearer a picture they can form of the situation and the better-positioned they are to highlight situations like this one.
We redacted a lot, and I accept that this makes it harder for others to check METR’s work. But we determined that sharing exactly what is driving the speedup isn’t the right thing to do, both because it’s commercially sensitive and because it risks handing out a roadmap for others to go faster. That would make the risks METR is worried about worse. That’s a tradeoff. I think we made the right call, though we’re continuing to assess the pros and cons here.
In the coming weeks, we plan to share a report with our own analysis of the speed of AI progress within Anthropic, including where we stand against our Responsible Scaling Policy, plus new steps we’re taking to strengthen our safety and security practices as AI keeps improving quickly.
Jacob Turner retweeted
So excited about this.
We're rolling out a mechanism that protects Vercel customers even in a Binance-style attack, where your engineers get targeted with infostealer malware.
With DBSC, renewing a session requires a key bound to your device, which means stolen cookies can't be practically re-used from remote Command & Control (C2) infrastructure.
While this is a pretty major win, there's no silver bullet in security. Make sure your Vercel account has MFA enabled (both app-based TOTP and passkeys), your organization enables SAML / directory sync, your endpoints are protected, etc.
(and stay paranoid!)
Today we are starting the rollout of Device Bound Session Credentials (DBSC) for vercel.com
DBSC makes it impossible to steal session cookies from a device. So, if you install info-stealer malware (e.g. through a supply chain attack), that malware can not steal your vercel.com session.
Malware can still do bad things while residing on the device. But the abuse we are seeing in practice separates the stealing from the eventual abuse, and DBSC effectively prevents this.
DBSC works by storing a private key in your device's TPM (the same device that the fingerprint sensor or similar biometric devices on your laptop or phone uses) and using that key to sign your cookie. The private key can never be retrieved ever again. Not by us, not by you, not by the malware.
Every website should use DBSC but given how new of a technology it is, we still need to build more experience in rolling it out. In our case there were lots of special cases for things like oauth apps that we needed to resolve. This is also why we are taking a slow approach to the rollout.
DBSC is currently only supported by Chrome on Mac and Windows. We are also working on a kind of polyfill for other browsers. However, the polyfill is less secure and we would love to see broader browser adoption.
There is a related technology called DPoP which is essentially the same but for apps that run on your device. We're in the process of shipping this for Vercel CLI. Ideally, all CLIs and apps would adopt this technology. Luckily rolling out DPoP is much easier than DBSC and it does not depend on browser vendor support.
Jacob Turner retweeted
For anyone questioning whether this post is overhyped, I think they are actually *underselling* the approach.
We did similar experiments and found that Claude models can write entire, functional neural net weights from scratch! csinva.io/weight-space-progr…
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math.
It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training.
We call this Weight-Space Programming: frontier LLMs can now natively read/write neural network weights! 🧵
Blog: rikiyat.github.io/blog/weigh…
Readers added context they thought people might want to know
LLM was given weights explicitly as text in prompt and used code/forward passes (per authors' logs) to ablate Qwen looping direction, a known thinking-mode issue per model card. Primarily fixed repetition in that mode, not general 'natively' improving weights/math.
rikiyat.github.io/blog/weight-sp…
github.com/RikiyaT/lm_und…
huggingface.co/Qwen/Qwen3.5-0…
huggingface.co/RikiyaT/Qwen3.…

































