In the Jade pitch deck, we establish an overall direction with Jade. This epic is about bringing the user experience of Jade, as well as the underlying code, in line with the stated direction of Jade. This is mostly about replacing "judgment" with "label" and things that imply that Jade is only meant to be used in a specific domain (e.g. refuting ORES scores). (I am not totally sure if we do that in the code but I want to cover my bases.)
Process document for more (less interesting) information: https://docs.google.com/document/d/1T97c8EgC7hckHLMngRLBIwcvE-Rl05Loii8OgYLdi5Y
In T200365, we're discussing a new name to replace "judgment". This task is complete when we've made the substitution everywhere in code, documentation, and the beta cluster test data has been migrated.
We have decided on a new name, "Label." This task tracks completely updating all references in the code and documentation.