SBAT.md recommends resetting vendor generation numbers after global generation number went up

[kukrimate]

For example:

However, once the global number is bumped for the next upstream CVE fix there will be no further need to carry that product-specific generation number. Satisfying the check of the global number will also exclude any of the older product-specific binaries.

If this same Vendor C has a similar event after the global number is incremented, they would again set their product-specific or version-specific number to 1. If they have a second event on the same component, they would set their product-specific or version-specific number to 2.

The current consensus seems to be for both generation numbers to only ever go up, so we should stop recommending people do this.

[aronowski]

Related explanation regarding such consensus in historical context, as well as the SbatLevel variable: rhboot/shim-review#355 (comment)

I'd highly recommend writing an introductory document akin to what @nicholasbishop provided here, but covering all the common scenarios, so people are immediately getting the knowledge of how the appropriate numbering system.

I can write a draft and suggest it, but first I need to make sure that I know, what is actually happening and that I was consulted on this before writing things that may be incorrect.