When refutations have been attached to an ORES score, they should be surfaced by including them in query results.
Open questions:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T148700 JADE: UI/API for reviewing/refuting how ORES classifies you and your stuff | |||
| Declined | None | T153143 [Spec] ORES query results should include Jade refutations |
From @Halfak
Here's a sample of what ORES data might look like with JADE judgments inlined: https://gist.github.com/halfak/6945c4763be32530dc0ab9c8906d72b5
Note that the judgments are under the damaging key. It seems that accomplishing this structure will require some interesting hooks in ORES, and that we might want to store the JADE data in the cache, alongside related ORES model scores. Here are more discussion notes sort-of explaining how we got here, https://etherpad.wikimedia.org/p/jade_ores_dataI've left some longer-term notes about the overall implementation: https://etherpad.wikimedia.org/p/JADE_extension_implementation