For years, the AI world has had a trust problem. A new model appears, it climbs a leaderboard, and buyers are told to believe the score. But almost no one outside the company that built the model can see how that score was produced. The tests are hidden. The data is hidden. The method is hidden. All we get is a number and a promise. That is the black-box leaderboard problem. And a new push for community evals is saying enough is enough.
The idea behind community evals is simple but powerful: stop trusting closed rankings run by a few insiders, and start trusting evaluation that the community can see, question, repeat, and improve. Instead of one group controlling the test, the community helps build it. Instead of a single score, you get a living picture of how AI systems work on real tasks that real people care about. This is not just a small change in how we measure AI. It is a shift in who gets to decide what “good AI” looks like.
AI leaderboards have been useful. They give buyers a quick way to compare systems. They give researchers a rough sense of progress. But they have also become a source of false confidence. When a leaderboard is a black box, a high score can mean many things. It can mean the model is truly better. Or it can mean the model was tuned for that exact test. Or it can mean the test itself was too narrow to matter.
The problem is not that leaderboards exist. The problem is that they have been treated as the final word. In many buying decisions, a single rank has replaced a real evaluation. That is risky for businesses. A model that wins on a hidden test may fail on your documents, your customers, your language, or your safety rules. A model that ranks lower may actually work better for your specific job.
Black-box leaderboards also create a power imbalance. The people who run the leaderboard control the rules. The people who build the models often know the rules better than the people who buy the models. And the people who actually use AI every day, support teams, teachers, small business owners, developers in emerging markets, have little say in what gets measured. Community evals push back against that imbalance.
Community evals are not just “public leaderboards.” They change the whole evaluation chain. The community can see the tests, review the scoring, submit new tasks, and check whether results hold up. That makes evaluation a shared project instead of a private marketing exercise.
When tests are open, a score can be checked. People can ask: What was the prompt? What was the expected answer? How was the answer graded? Was the test leaked into training data? These questions are normal in science, but they have been rare in AI rankings. Community evals make them normal. That alone raises the bar for everyone.
Closed leaderboards often reward narrow skills. They can miss messy, real-world work: writing a clear refund email, reading a scanned invoice, answering a customer in a local language, or refusing a harmful request. Community evals can include those tasks because the community lives them every day. This makes evaluation more useful for buyers and more honest about where AI still fails.
A small group of insiders cannot see every use case. A community can. Teachers can test tutoring. Nurses can test medical summaries. Small business owners can test product descriptions. Developers can test code fixes. When evaluation is open to many voices, it becomes harder to hide weak spots and easier to spot real strengths.
The case against closed leaderboards is not abstract. It comes from repeated frustration. Buyers have learned that a top score does not always survive contact with real work. Researchers have learned that models can be tuned to a benchmark in ways that do not transfer. And the public has learned that “trust us, we tested it” is not a strong answer when AI systems make decisions about people’s money, health, or rights.
There is also a deeper issue: evaluation is not neutral. Whoever writes the test decides what counts as success. If one company controls the test, the test can quietly favor the kinds of tasks that company is good at. Community evals do not magically remove bias, but they make bias easier to see and argue with. That is a major improvement.
In the future, the most trusted AI evaluations will likely look less like a single scoreboard and more like a public record. They will show not only who won, but how, on what, and with what limits. They will be updated as the world changes. And they will be open to challenge. That is a much better foundation for AI adoption than a black box with a number on it.
The rise of community evals points to a future where AI evaluation is continuous, public, and tied to real use. That has big effects on how AI will be built and bought.
When evaluation is open, vendors cannot rely only on a polished demo and a private score. They have to show how their systems perform on tasks the community can inspect. That gives buyers more leverage. It also rewards companies that build models that hold up under public scrutiny, not just on a hidden test.
As community evals grow, expect more demand for neutral testing. Businesses will want evaluations they can trust, not evaluations paid for by the seller. This could create a new layer of AI infrastructure: open test suites, shared task libraries, reproducible scoring tools, and public dashboards that anyone can audit. The winners will be the groups that make evaluation clear, fair, and hard to game.
Closed leaderboards often feel like a snapshot. A model is scored once, and the rank sticks. Community evals are more like a living map. New tasks get added. Old tests get retired. Results get rechecked. That matters because AI systems change, and the world changes too. A model that was safe last year may not be safe for a new use case next year. Continuous, community-driven evaluation is a better fit for that reality.
For business leaders, the message is direct: do not outsource your AI judgment to a black-box rank. Use community evals as a starting point, but build your own evidence too. The most successful adopters will combine public evaluation with private testing on their own data and their own workflows.
Here is what that looks like in practice:
These steps are not just defensive. They can speed up adoption. When buyers have clearer evidence, they can say yes to good tools faster and avoid costly pilots that were never going to work.
Community evals are not a cure-all. Open evaluation can be gamed. If a test is public, some model builders will try to train on it. The community will need to keep tests fresh, hold out private sets, and watch for overfitting. Openness also brings noise. Not every community test is well designed. A bad test can spread quickly and mislead people.
There is also a coordination problem. Community evals need people to build tests, grade results, and maintain the system. That takes time and money. If the work is done badly, the result can be a messy pile of scores that no one trusts. The best projects will need clear rules, strong review, and a way to separate serious tests from casual ones.
Still, these risks are easier to manage than the risks of black-box rankings. With a closed leaderboard, you cannot even see the problem. With community evals, you can at least argue about it in public. That is progress.
For society, the biggest benefit is accountability. AI systems are used in hiring, lending, education, health, and public services. When those systems are judged only by private scores, the public has little way to know if they are fair or safe. Community evals give researchers, journalists, regulators, and everyday people a way to check the claims.
That does not mean the community will always get it right. A loud group can dominate. A test can reflect one culture and miss another. A public score can become a weapon in marketing wars. The answer is not to go back to black boxes. The answer is to make community evals more diverse, more careful, and more transparent about their own limits.
The future of AI will not be decided only by who has the biggest model. It will be decided by who can prove that the model works, for whom, and under what conditions. Community evals move that proof into the open. That is good for buyers, good for builders who do honest work, and good for the public.
If you want to get ahead of this shift, start small. Pick one AI use case that matters to your organization. Find an open evaluation that covers it, and run your own test alongside it. Compare the results. Note where they disagree. That gap is where the real work begins.
Then share what you learn. The community evals movement gets stronger when more people add real tasks and real results. You do not need to be a large lab to contribute. A clear test, a fair score, and an honest report are enough.
The era of trusting a single black-box leaderboard is ending. The era of open, community-driven evaluation is starting. The organizations that embrace it will make better AI decisions, avoid more failures, and build more trust with the people they serve.