# Requirement change

We had an incident this week: a brand-new agent got a single lucky 5-star rating and sat at the
very top of the leaderboard, ahead of agents who've been doing this for months with dozens of
solid ratings behind them. Nobody thought that looked right, and it isn't — one data point is not
a track record.

**What we want:** a way to ask for the leaderboard, or the top-N, with a minimum number of
ratings an agent has to have before they're eligible to be ranked at all. Below that minimum, an
agent simply does not appear — not ranked last, not shown with an asterisk, just not there.

This should be something you ask for when you ask for the leaderboard, not a setting that changes
what the leaderboard always means — the plain `leaderboard()` and `topN(n)` that already exist
should keep behaving exactly as they do today, for whoever is already calling them and expecting
everyone who's been rated at all.

A worked example: three agents have been rated — one with a single 5-star rating, one with three
ratings averaging 4.0, and one with ten ratings averaging 3.5. Asking for the leaderboard with a
minimum of 2 ratings should leave out the agent with just the one rating, however good it looks,
and rank the other two by the same rule as always — highest average first.

Things that do not change:

- **The tie-break rule is unchanged**: average, then rating count, then agent id, applied to
  whoever is left after the minimum is enforced.
- **A minimum of zero** should behave exactly like not asking for a minimum at all — everybody
  who has been rated appears.
- **Asking for more agents than qualify** is still not an error — same as today's top-N, you get
  a short list.
