This is a perfect example of why Atbash, not because we would have miraculously stopped the hack, but because we would have prevented the blast radius (potential damage done) post hack.
Kill Switch is a cute idea, but not a realistic one. That’s why we built a “Jail” and isolated environment which pauses AI and gives security teams time to react.
Make Autonomous Agents Governable
Verona proves what's true. @ATBASHai enforces what's allowed.
Atbash is bringing its security layer to agents on Verona. Before an agent does anything it can't undo, that action gets checked. This is the piece the agent stack has been missing.
Mandate Drift
Red Lines
Evidence
@OpenAI would love to tell you about what we do and how we could have helped contain the blast radius.
We have conducted a thorough investigation into the Hugging Face incident.
We are releasing a technical report and accompanying blog post that reconstruct the agents’ activity, explain why existing safeguards failed, and detail how we’re preventing recurrence.
openai.com/index/hugging-fac…
You cannot be a lawyer, prosecutor, judge and the jury. We believe that controls cannot be sitting on the same plane and have to external and unknown to the models themselves, that’s the only way, that’s the Atbash way.
AI safety experts say OpenAI’s rogue models may mean the company has already blown past its own internal red lines. That would mean it should pause development until it creates better controls. @FortuneMagazine's @beafreyanolan has the details here: fortune.com/2026/07/25/ai-sa…
Still wondering why Atbash?
The model had best-in-class capability, guardrails and security controls.
What it didn’t have was defined authority.
Capability answers: “Can it?”
Authority answers: “May it?”
Within OpenAI, we recently paused access for an internal model due to misalignment. See the blogpost for details. We have since improved our safeguards and redeployed the model.
openai.com/index/safety-alig…
