The implementation, at least in Sabre, is kind of interesting.

AA filed the fares with bundles as applicable to non-default passenger types (i.e. non ADT): PRO for Essential and TIM for Plus.

• PRO is a so-called private passenger type
• TIM has a legacy definition of "Timesaver"

Also, in order to prevent mix and match of the above with the default "ADT" (base) fares, agents must manually add a command to the pricing to tell the system to use "Passenger Type Specified Only".

The fares themselves are filed as "promotional" and won't appear in the default fare display. They also appear as "private" fares, a technical distinction of no import for all practical matters.

As I said, a bit kludgey but doable, and within the full-content agreement between AA and Sabre (and probably other GDSs).