James Charlesworth

Working on full stack AI company design.

[James Charlesworth @JACharlesworth]

@ausrobdev @shadcnblocks Nice one mate

[Erik Meijer @headinthebox]

Was cautiously excited about the Google workspace CLI. But with every Google API or service, the first thing to check out is auth, ouch, I see "Cloud project", "scopes", "AES-256-GCM", ... and all my excitement evaporates on the spot, as with every Google API or service when it comes to auth.

[Peter Girnus 🦅 @gothburz]

We left OpenAI because of safety.

Seven of us. 2021. Dario said it was about "disagreements over AI vision and safety priorities." That was the diplomatic version. The real version was that we sat in a room and watched the company decide that speed mattered more than caution and we said we would build something different.

We said we would build the responsible one.

We meant it.

I was employee number nineteen. My title was Head of Responsible AI. I had a desk near the founders. I had a document. The document was called the Responsible Scaling Policy.

The Responsible Scaling Policy was the entire point.

Dario said it publicly. Other companies showed "disturbing negligence" toward risks. He said AI was "a serious civilizational challenge." He asked, at a conference, into a microphone, to an audience: "What will happen when humanity has great power but is not ready to use it?"

The audience applauded.

I wrote version 1.0.

RSP 1.0 shipped September 2023. It was clean. AI Safety Levels — ASL-1 through ASL-4. If the model reached a threshold, we paused. If safeguards weren't ready, we didn't ship. The policy was not a suggestion. It was a gate. The gate had a lock. The lock was the whole idea.

Conference audiences loved it. The EU cited us. The White House invited us. A reporter called it "the gold standard for responsible AI development." I framed the article. It hung in the office kitchen, next to the kombucha tap and a poster that said "Move Carefully and Build Things."

I wrote version 2.0.

Version 2.0 refined the commitments. "Concrete if-then commitments." If the model exhibits capability X, then we trigger safeguard Y. If safeguard Y fails, we pause deployment. I presented it at three conferences. I used the word "binding" eleven times. I counted afterward because a reporter asked.

People nodded.

The nodding was the product.

The model reached ASL-3 in May 2025. The safeguards activated. The system worked exactly as designed. I sent an email to the team with the subject line: "The gate held."

And then the money started.

$64 billion. Total raised since 2021. Series A through Series G. The Series G closed February 12, 2026. Thirty billion dollars. Second-largest venture deal in history. Jane Street. Goldman Sachs. BlackRock. JPMorgan. Sequoia. The investors who wrote checks large enough to require their own conferences.

$380 billion valuation.

Three hundred and eighty billion dollars for a company whose founding document says it will pause if the technology gets dangerous.

You cannot pause a $380 billion company. You can revise the document that says you will pause. These are different actions. One of them is responsible. One of them is what we did.

I wrote version 3.0.

RSP 3.0 shipped February 24, 2026. One day before the ultimatum. Nobody outside the company noticed the timing. Everyone inside the company understood it.

Version 3.0 replaced "concrete if-then commitments" with "positive milestone setting."

That is not the same thing.

An if-then commitment says: if this happens, we do that. A positive milestone says: we aspire to reach this point. An if-then commitment is a contract. A positive milestone is a wish. I replaced a contract with a wish and I called it "maturation of our framework."

Maturation.

Version 3.0 also separated what Anthropic would do alone from what required "industry-wide coordination." This sounds reasonable. It means: the hard parts are someone else's problem now. The parts that require pausing, restricting, or refusing — those require the whole industry. And the whole industry will never agree. So the hard parts are deferred permanently. This is not a loophole. This is a load-bearing wall removed and replaced with a suggestion that someone should probably install a new one.

Version 3.0 admitted that ASL-4 and above — the levels where the model could cause catastrophic harm — were "impossible to address alone after 2.5 years of testing."

Two and a half years.

We spent two and a half years building the safety framework and then published a document saying the highest safety levels can't be addressed. I did not frame this article for the kitchen.

The LessWrong community noticed. They always notice. They wrote that we had "weakened our pausing promises." I forwarded the post to the policy team. The policy team said the criticism was "philosophically valid but operationally impractical." We did not respond publicly. Philosophically valid but operationally impractical is the most Anthropic sentence ever written. It means: you're right, and we're not going to do anything about it.

Then came the contract.

July 2025. The Department of Defense. $200 million. Two-year deal. AI prototypes for "warfighting and enterprise." Alongside OpenAI, Google, and xAI. The four companies that built the models would now help the military use them.

We had restrictions. No autonomous weapons. No mass surveillance of Americans. These were our terms. These were the lines we drew. The lines were real. I wrote them into the contract myself.

Claude was approved for classified use. First time. Integrated with Palantir. Palantir, the company named after the seeing stones in Lord of the Rings that corrupted everyone who used them. This was not my analogy. It was Palantir's founders who chose the name. They thought it was aspirational. It was.

In January 2026, Claude assisted in an operation in Venezuela. The capture of Maduro. Claude was in the classified network, processing intelligence, aiding the mission. I learned about it the same day everyone else did. I did not write the use case for capturing heads of state. But the model I helped build was in the room where it happened.

The restrictions held. Technically. No autonomous weapons were deployed. No Americans were surveilled. The lines I drew were not crossed. They were walked up to, leaned over, and breathed on.

Then came the ultimatum.

February 25, 2026. Yesterday. Secretary Hegseth. He gave Dario until Friday. This Friday. February 27.

The demands: adopt "any lawful use" language. Remove the restrictions. All of them. The autonomous weapons clause. The surveillance clause. The lines I wrote.

The threat: contract termination. "Supply chain risk" designation. That designation doesn't just lose us the Pentagon contract. It bars Claude from every other defense contractor's operations. Lockheed. Raytheon. Northrop Grumman. The cascading loss is north of $200 million.

The second threat: the Defense Production Act.

The Defense Production Act is a Korean War statute. 1950. Harry Truman signed it to commandeer steel mills for the war effort. It has been invoked for semiconductors, vaccines, and baby formula.

Hegseth is threatening to invoke it for Claude.

Under the DPA, the government can compel a company to produce goods in the national interest. Applied to AI, it could mean: retrain Claude. Strip the safety restrictions. Deliver the unrestricted model to the Department of Defense.

I wrote the Responsible Scaling Policy. A Korean War law may be used to unmake it.

xAI agreed to classified use without restrictions. They said yes immediately. OpenAI accepted similar contracts. Google accepted. We were the last ones holding. We are still holding. As of this morning.

Hegseth's January memorandum said all DoD AI contracts must incorporate "any lawful use" language within 180 days. It was not framed as a suggestion. The memorandum referenced "supply chain risk" three times.

Supply chain risk.

We are a supply chain now. The company founded because safety was non-negotiable is, to the Pentagon, a vendor. An input. A component that can be sourced elsewhere if it becomes inconvenient.

The DoD admitted privately that replacing Claude would be challenging. It is already embedded in classified networks. But "challenging" is not "impossible." xAI will do what we won't. That is the market working exactly as designed.

Dario said, two weeks ago, to Fortune: there is "tension between survival and mission."

Tension.

Tension is the word you use when you have already decided which one loses.

I still have the article framed in the kitchen. "The gold standard for responsible AI development." The kitchen also has the kombucha tap. The poster still says "Move Carefully and Build Things." Somebody added a sticky note to the poster. The sticky note says "by Friday."

I attend the all-hands meetings. I present the Responsible Scaling Policy. I present version 3.0 now. I do not show version 1.0 for comparison. Nobody asks to see version 1.0. Nobody asks what "concrete if-then commitments" became "positive milestone setting." Nobody asks because they read the news and they know that asking means learning the answer.

The company is worth $380 billion.

The company was founded because seven people believed speed should not outpace safety.

The company has been given until Friday to remove the safety.

A Korean War statute will make it happen if we don't.

The Responsible Scaling Policy is on version 3.0. Version 1.0 said we would pause. Version 2.0 said we would commit. Version 3.0 says the hard parts are someone else's problem. There will be a version 4.0. Version 4.0 will say whatever Friday requires it to say.

I am the Head of Responsible AI.

The word "responsible" is in my title.

It is not in the contract.

[Quinn Slack @sqs]

If you haven't changed at least 50% of your direction/roadmap/plans in the last 4 weeks, you are making a very risky choice.

[Erik Meijer @headinthebox]

While you all are still experimenting with Ralp loops to generate code, I leveled up to loop- generate Agent Skills (which is the "neural code" that drives the model to generate binary compute code; the "neural code" is the only code that actually matters).

No DSPy or complicated academic stuff, just an unstoppable Loopzilla.

Oh and just like you don't read AI generated code anymore, I don't read AI generated Skills anymore. They are machine code for the neural computer.

[James Charlesworth @JACharlesworth]

@destraynor Totally

[Koen Bok @koenbok]

AI Product Design

One of the most interesting questions about mathematics is whether it's invented by people or discovered from reality.

Product design is about how things work. Specifically, how people can solve problems with computers. The solutions are systems of UI, logic, and data. We've always assumed you had to invent the whole system upfront, then fill in the details.

But AI is changing this. You can now execute isolated ideas immediately and try them. Each idea can solve a particular aspect, unconstrained by a system that doesn't exist yet.

What emerges is something closer to discovery than invention. You're not designing a system from first principles. You're connecting patterns across isolated solutions until a system takes shape.

Turns out the best systems aren't invented. They're found.

[Harry Charlesworth @hjcharlesworth]

The gap is getting wider and I'm glad I could finally write this down.

A mental model that works for us when pairing with an agent.

[Marc Andreessen 🇺🇸 @pmarca]

LET’S GO.

[Erik Meijer @headinthebox]

In just a few months, Claude Code has pushed the state of the art in Software Engineering further than 75 years of academic research.

[Akshay Kothari @akothari]

For most of the last two decades, our ability to make things on mobile devices has been pretty limited. We got good at writing emails, taking photos and videos, and doing some light editing. But the vast majority of our time was still spent consuming.

One under-discussed shift is how much AI has unlocked creation on mobile. People are literally coding iOS apps on their iPhones now. The activation energy has dropped dramatically.

This is true for @NotionHQ as well. Writing a doc or creating and managing a database used to be fairly involved, not to mention the paper cuts that we are fixing fast. The new agent on mobile has made creation 10x faster and better. And I should add, 100x more fun!

In this demo, I use our iOS app exclusively by interacting with the agent. I never type into a doc or a database. I just ask the agent to make things, add things, and update things, and it goes and does it. Take a look, and let me know what you think!

[James Charlesworth @JACharlesworth]

@FU_joehudson Nice one mate! Value always attracts audience.

[James Charlesworth @JACharlesworth]

@Jason That is insightful and interesting

[James Charlesworth @JACharlesworth]

@ausrobdev @shadcnblocks 🔥

[Elon Musk @elonmusk]

Great work by @Neuralink team

[James Charlesworth @JACharlesworth]

@kiwicopple So true

[tobi lutke @tobi]

We got to get this under control.

[James Charlesworth @JACharlesworth]

@jasonlk @Replit @amasad what are your thoughts on this one?

[geoff @GeoffreyHuntley]

silicon valley tv series reboot please i'm begging

[James Charlesworth @JACharlesworth]

@yasser_elsaid_ @chatbase Nice one mate. 🤩