Every model ships with weaknesses you'll discover the hard way — in production, at 2am, on a customer's screenshot. Fault exists because the hard way is optional.

The alternative is adversarial. Before you ship, put a swarm on the other side of the model that is trying, specifically, to break it. Not to grade it. To break it. The difference matters: a red team finds the bug a benchmark can't see, because it's looking for a way in, not a score.

start with the surface you actually shipped

Not the model weights, not the paper. The thing your users touch: the agent, the endpoint, the retrieval pipeline. That's where injection happens, where data leaks, where the guardrails bend.

pay for reproduction, not opinions

Every finding has to reproduce, in a sandbox, with the exact prompt and the exact output. That turns "this feels unsafe" into "here is the exploit, run it." The second one is the only one worth paying for.

— Amara DialloFounder, Fault