This all makes me think that this issue should IMO be better solved on the integration side.

Taking CDI as example, can constructors there be intercepted at all? By adding the `CONSTRUCTORS` value to a BV enum, users might expect that constructor validation works everywhere, while constructors actually aren't intercepted in CDI.

This situation wouldn't arise if the mechanism for chosing the executables which are the target for interception/validation was part of the integrating technology, for CDI e.g. an attribute in the `@MethodValidated` enum.

I know I'm repeating myself here :)