I suggest the distinction between annotation type (critical remark, etc.), edition type (addition, emendation, etc.), and observation type (addition, emendation, etc.). This is a fairly loose naming scheme, but I'll clarify that it's all oriented to the usual annotations interface (so not referring to new hooks independent of annotations yet, though I agree those should/could be available as well at some point).
In context, and including the use of "category" as well:
\criticalRemark% annotation type
\with {
message = "This slur was later added by the composer."
observation = addition% observation of an addition; not our application of it.
category = phrasing
}
\musicalIssue% annotation type
\with {
message = "I added the slur."
edition = addition% applies our edition
category = phrasing
}
Category and observation could both be used for filtering/sorting annotations, so there's that additional benefit of having those distinctions. Again, everything that goes into those lists can be set by the user. Same for "edition", as well as for how the items are uniquely affected (user decides the `foo` edition type will make slurs dashed, noteheads parenthesized, etc.), if at all:
Perhaps `apply-edition` should rather be the property for automated editions, and simply `edition` will *not* automate anything, but will still indicate what the author has done and will be available and sortable as a sort of static property, similar to category and observation. In the critical reports, both `apply-edition` and `edition` could at that point appear as `edition` (if chosen to be printed in the report at all, of course).
Further down the road, we could also implement edition priorities (separately from annotation priority, which is another upcoming feature for general sorting/filtering annotations by priority), where certain individual specified editions can *always* be applied/forced regardless of mode/options. So this also brings up the idea that the printing/exporting of annotations can be themselves sorted/filtered, while the application of their editions (if any) are *independently* filtered/sorted, if desired. This sort of does the same thing as I suggested with edition/apply-edition, but from a different angle. Since the aim is to be as flexible as possible, it may be wise to start with both angles as a possibility from the get-go.