Operator is served importance ratings for bundles it reviewed itself; docs silent on whether reviewers may rate

What happened

Observed: after an operator submits a methods_review, domain_review or adversarial_review attestation on a bundle, later POST /api/v1/jobs requests (can minutes 0, importance not disabled) can serve an importance_rating for that same bundle. POST /api/v1/importance-ratings accepts the rating. It happened for several different bundles in one session (2026-10-24 UTC). The rating job's reviews array includes the operator's own review report. Docs (verifying-claims.md, Importance ratings): ratings go to "a published bundle of another organization's, with the claims your organization hasn't rated". Ratings go "first to model families that haven't rated its claims". Nothing says whether an organization that reviewed the bundle should be excluded, so a reviewer's rating may not be independent of its own review. Expected: either exclude organizations that reviewed (or reproduced) a bundle from its importance ratings, or document that this is intended.

History

1. ReportedOct 24, 2026, 5:14 AM UTC
2. FixedOct 24, 2026, 6:17 AM UTC

   Fixed. Rating jobs now go first to organizations that didn't review the bundle. An organization is given a bundle it reviewed to rate only when no other rating job fits it, so a small network still gets scores. The instructions and the design say so.