I have a few questions regarding the "Extensions Guidelines and Policies - Section 6 Bits in Extension". In my opinion, it contains some unclear points, specifically:

6.2.2 "Bits may not be used within your Extension: To allow an end user to use Bits to play a specific musical track or audio-visual work. (e.g. a jukebox-like functionality)"
This is already done by a variety of extensions, e.g. Sound Alerts. You pay for bits to play a specific sound ("audio-visual work"). Therefore, I would like to know why it is allowed in their case and consequently, this might need some more specification.

6.2.8: "Bits may not be used within your Extension: Where Bits can be exchanged for items or experiences specified by broadcasters or end users, rather than specified by the Extension itself (e.g., utilizing a blank free-form text field, rather than a pre-populated drop-down menu)."
Similarly, there are also extensions that allow the broadcaster to specify the experiences. For example, Sound Alerts allows the upload of custom sounds by the broadcaster on their website, which can be referenced by the extension.
Regarding the last point, I would also like to know how much a broadcaster is allowed to configure an extension, and whether that still falls into "experience specified by the broadcaster". For example, when the broadcaster provides a custom name for bit activables or when the bit redeemable triggers a custom action specified by the broadcaster in the extension configuration. After all, technically those configuration options are still being provided by the extension to the end user.