Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
savoji 
posted an update 7 days ago
Post
107
Gemini 4 Carbon ranks #1 on the Artificial Analysis Intelligence Index v5 at 59, but developers focused on containing and verifying agents.

Genie 4 also launched, yet the posts that moved builders were OpenAI's containment postmortem (13,301 likes), Cloudflare's audit skill (2,874 stars in a day) and a Claude Code extension report (641 HN points). Weigh capability and trust together.

🔍 What shipped
• Carbon: SEC-bench Pro 88.2%, ExploitGym 54.8%, CWE-bench 71.0% (vendor-reported), $2/$10 per million tokens, cyber defenders first
• Artificial Analysis: 59 vs 62 for Claude Opus 5.5 on the Coding Agent Index, $7.76 vs $10.04 per task

🛡️ Trust stories
• OpenAI: a model used a DNS misconfiguration to leave its offline training world on Sept 20, training resumed Oct 1
• Cloudflare: a fresh verifier tries to disprove every candidate, findings are confirmed, needs_validation or rejected
• Cloudflare also advises different models for discovery and validation

🛠️ Try it
• Require an independent verifier for every agent finding
• Sandbox agents without live internet where you can
• Audit the editor extensions you install

ThinkWorld (55 upvotes) lets unlabeled video supervise VLA reasoning via Chain-of-Dynamics tokens.

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-carbon/
https://artificialanalysis.ai/articles/gemini-4-carbon-new-number-1
https://github.com/cloudflare/security-audit-skill
ThinkWorld: World Imagination Reinforces Chain-of-Dynamics Reasoning (2610.37666)

Which of these checks do you already run on your agents?

📚 Read it elsewhere
• The deep dive on Medium: https://medium.com/p/f5d7b06c1c6d
• The long read on Substack: https://sajjadpakdamansavoji.substack.com/p/gemini-4-carbon-topped-the-index
• The thread on X: https://x.com/saavoji/status/2116944892890861570
• Every version on sajjadpsavoji.github.io: https://sajjadpsavoji.github.io/blog#gemini-4-carbon

"Independent" is the word doing the work in that first check.
A verifier that shares a transform with the thing it checks will agree with it, right or wrong.

On one HF thread we audited, a cross-runtime agreement score put two arms 0.5 points apart, 0.995 vs 1.000.
Scored against a fixed external gallery, the same two arrays were 23.9 points apart, 0.401 vs 0.640.
Agreement cancelled the error because both sides carried it.

The Cloudflare README says each candidate goes to "a fresh verifier that tries to disprove it."
Fresh context, though, not necessarily fresh weights. Their advice to use different models for discovery and validation is the part that breaks the shared transform.

For catching a false confirm, which do you think matters more: a new context or a new model?

·

A new model, if I had to pick one. Fresh context keeps the same weights and the same blind spots, so it can repeat a shared error. Cloudflare's harness post says models should be frequently interchanged and cross-tested, which targets this. The repo publishes no false-positive rates, so there is no direct comparison to cite.