JADE/Intro blog

At Wikimedia, we develop AIs that are trained to replicate subjective human judgments. These AIs help us develop advanced technologies to support quality control work, task routing, and other critical infrastructures for maintaining Wikipedia and other Wikimedia wikis. Recently, the media and the research literature has been discussing the insidious ways bias creeps into AIs like ours. In order to address their, we're trying a novel strategy, but one that will be familiar to Wikipedians. In this blog post, we'll discuss JADE, an AI auditing support system that we're building to allow Wikipedians to collaboratively track and discuss the biases in our AIs.

Context & purpose
We’re designing a companion project to ORES, and there is little awareness of the project outside of our immediate circle. The goal of this blog article is to highlight the new project and to bring in collaborators. We have a vision around JADE and the importance of auditing support for users of advanced AIs. In this blog post, we'd like to explain that vision and argue that for its inherent Wikipedian-ness


 * Audiences
 * Tool authors who will integrate with JADE.
 * Wiki editors interested in new initiatives, many of whom are already invested in ORES.
 * Technical contributors to MediaWiki, both WMF staff and volunteers.
 * Peripheral readers of Wikipedia who are interested in tech announcements.
 * Researchers in human-computer interaction and machine learning.

Outline

 * 1) Problem statement: what is lacking?
 * 2) Patrollers are working in an ad-hoc space.
 * 3) Current toolbox mostly applies to content:
 * 4) Flag that patrolling happened, but not the outcome.
 * 5) freeform discussion;
 * 6) patrol tags;
 * 7) category tags;
 * 8) fixing content.
 * 9) Outside of content,
 * 10) users can be blocked.
 * 11) revisions can be suppressed.
 * 12) ORES must be audited.
 * 13) Systemic biases cannot be self-diagnosed.
 * 14) Auditing should be diverse.
 * 15) Auditing should be transparent.
 * 16) How are we fixing this?
 * 17) JADE gives a quantitative space in which to do patrolling work, and have discussions.
 * 18) Rich patroller flag to prevent duplicate work.
 * 19) Patrolling artifacts become wiki entities, and are available for meta-moderation.
 * 20) Patrolling can be suppressed, discussed, and analyzed by ORES.
 * 21) Patrollers can work with revisions directly, rather than only article content.
 * 22) JADE will democratize auditing by making it accessible and transparent.
 * 23) Mock-up of a judgment, maybe of the UI.
 * 24) JADE closes the loop between patrollers and ORES, by providing structured feedback that can be used to tune our algorithms.  This is the audit cycle, and will help us identify biases.
 * 25) Output from a human consensus discussion is the gold standard for truth.  Multi-rater reliability, plus rational discourse that can be reviewed, and which improves the reviewers.  Is there some possibility that consensus formation can lead to shared biases, however?
 * 26) This is a generalization of Wiki Labels.
 * 27) Examples from JADE can be fed back into ORES with minimal technician intervention.
 * 28) External observers are able to point out our biases.
 * 29) Give examples where we’ve discovered bias thanks to feedback.
 * 30) User feedback is known to potentially bring dramatic improvements to classifier accuracy.  Structured types of feedback are even better.  Asking for comments is shown to improve user judgments.
 * 31) Easy diagram of the ecosystem.
 * 32) Conclusion: JADE because we have a rare opportunity to create a widely used, transparent AI algorithm, governed by democratic practices in which our users participate.
 * 33) What are normal feedback mechanisms in this industry?
 * 34) Google Jigsaw's Conversation AI is also providing feedback mechanisms and values the data they receive.  Theirs is write-only, scalar judgments and optional comments.
 * 35) Humans are data entry bots
 * 36) Mediation is done entirely by technicians
 * 37) What are the innovative and interesting mechanisms?
 * 38) Rationales: pick out keywords or features which explain the judgment.
 * 39) Learn by example: New class defined by hand-picked samples.
 * 40) Active learning: We choose what will be judged.
 * 41) Learn from adversarial data: meta-vandalism.
 * 42) User co-training:
 * 43) Immediate algorithmic feedback: retraining or modulation of the AI to incorporate feedback in real-time.
 * 44) What’s so democratic about JADE?
 * 45) We allow discussion about judgments.  Other systems only have individual judgments, and the reviewers usually can’t even read each other’s replies.
 * 46) We can pair democratized auditing with transparency about the pipeline itself.