In T324730, we will implement an //initial// [i] heuristic/set of rules that will determine when the reference check will, and by extension, will NOT be triggered.
This task involves with making a more philosophical/abstract decision about how we envision the reference check evolving over time.
Said in the form of a question: will the reference check get triggered in a relatively narrow set of cases to start and grow to be more expansive over time? Will the reference check get triggered in a broad set of cases to start and grow to be more precise over time?
Answering this question will inform the initial set of rules we end up implementing in T324730.
=== Decision(s) to be made
- [x] 1. How will we assume the reference check will evolve to become more accurate and exhaustive over time? //E.g. will the reference check get triggered in a relatively narrow set of cases to start and grow to be more expansive over time? Will the reference check get triggered in a broad set of cases to start and grow to be more precise over time? Something else?//
To start, Edit Check will be implemented in a way to **minimize false positives.** //See T329988#8654867 for how the Editing Team arrived at this decision.//
=== Considerations
//See: T329988#8654867.//
=== Done
- [x] Actions for each `Decision to be made` are documented
---
i. Emphasis on "initial" because as T327959 suggests, we will be introducing a way for volunteers, on a per-project basis, to iterate upon these rules so that the reference check becomes more accurate and robust over time. //Read: Edit Check will cause fewer false positives and negatives.//