Scorecards: let measurements choose the order

Two small JSON formats let an evaluator and Lodestone feed each other without sharing code. Naija Eval, which measures translation and speech quality for Hausa, Igbo and Yoruba, is the first to use them. Its scores are translation quality, so they help tasks in those languages, not every task.

Evaluator (Naija Eval)

Measures answer quality, such as chrF++ for English→Yoruba, per model.

Lodestone (in your tool)

Tries the best-measured models first for tasks you name, lists the models it can call, and records its own success rates and speeds.

A scorecard only changes the order models are tried in. Nothing is added or dropped.
Scores from fewer than 30 items, or over a year old, are ignored.
Unmeasured models keep their slot, so a good unmeasured model is never pushed down.
An explicit route is never reordered.
If the scorecard fetch fails or takes over 1.5 s, the order is left alone.
Live stats keep the last 200 attempts per model and never see prompts or answers.