Why we published a standards registry
Quality assessment is only credible if the criteria are public before the scores are. The reasoning behind making the 44 standards readable, versioned, and arguable.
“Quality” is the kind of word that survives meetings because everyone assumes they mean the same thing. For one editor it means accuracy; for another, prose; for a product team, whatever their model happens to score. If an assessment tool can’t say precisely what it measures, the score it produces is numerology.
That’s why our specification starts with a published registry: 44 named standards across four domains — professional, technical, legal, and ethical — each with a code, a name, and a severity.
What a registry buys
- A vocabulary. “Accuracy” (PROF-01) is a named standard; “key assertions cite a checkable source” is a criterion under it. Reviews, appeals, and model tests can refer to the same thing.
- Reproducibility. A report names the standard versions it was evaluated against. If the registry changes, old findings keep their context — they’re versioned, not silently re-scored.
- Auditability. External reviewers can disagree with a criterion without disputing the entire framework — or argue the framework itself, on the record.
- Weighting transparency. Different content types stress different standards — accuracy dominates hard news; structure and ethics carry opinion; AI-disclosure is mandatory for automated news. The variation is declared, not hidden in a single score.
What it deliberately doesn’t do
A registry defines the rubric, not the verdict on truth. PROF-01 (Accuracy) scores whether claims are evidenced and correct — it does not decide what is true. LEG-01 (Defamation Risk) flags legal exposure for a human to weigh — it is not a court. And no registry entry makes a publish/no-publish decision: the output is advisory, and the accountable human stays in the loop.
The honest limitation
Eleven standards per domain is a working subset, not a final canon. Some standards are easier to check than others — “headline accuracy” is more automatable than “independence.” The registry will grow, and its gaps are part of the published spec, not a secret.
The full registry is at config/standards_registry.yaml in the public specification, and the guide page walks through all four domains.