This is a tracking task to define the scope of version of the initial Edit Check (references) and coordinate its development.

Scope

Version 1 of the reference Edit Check will be made up of four core components:

1. Heuristic: a heuristic Edit Check will use to determine what edits should cause the reference check to be triggered
2. Auditing: a mechanism volunteers and members of the Editing Team can use to evaluate whether the reference check is being triggered with, what they agree to be, acceptable levels of false positives and negatives
3. Iteration: a mechanism members of the Editing Team [i] can use to refine the heuristic to minimize the levels of false positives and negatives
4. In-edit experience: the user experience newcomers and Junior Contributors will be met with when they attempt to publish a qualifying edit [ii] without a reference

Reminders

The contents of this section will eventually get migrated to other sections of this ticket.

• Preserving the progress people have made: per T327709#8576584, we'll need to ensure we store the “dialog” state

i. Eventually, the Editing Team will create tool/abstraction that will enable individual projects to refine the reference check. This work will happen in TICKET. Although to start, the Editing Team will likely need to make these refinements on projects' behalves.
ii. "Qualifying edit" in this context refers to edits that meet the rules being defined in T324730