Methods and limits
How red teams design tests and document failures without claiming more than a result supports.
We write about testing AI systems and responding to the results. The focus is what a test can actually prove and what the organization does once the report is delivered.
How red teams design tests and document failures without claiming more than a result supports.
Why technically sound work sometimes stalls after review, and what makes a finding usable to the people who can act.
How teams decide when a system needs another evaluation and compare the new result with the earlier one.
Essays and field notes for people who test AI systems or make decisions about their use.
Defense AI ships in weeks, is assured in years, and must be trusted in minutes. The gaps between those clocks are now part of the deterrent, and they can be measured.
Read the article →
Near-term AI harms feed one another, and the loops they form lead toward catastrophic risk.
Read →
It’s getting harder to know not just which AI you can trust, but whether you can trust AI at all.
Read →Bring the system, the decision ahead and the evidence that would help. We aim to reply within two business days with a useful next step.