multiple resolutions: if we can at least get playback to work, then infra can plug in... conditional on not becoming redundant or in conflict with fuutre adaptive streaming.

how are we dealing with category mapping? I believe it should be static, and creator should provide input in signup flow, but I don't know where we stand. This would also be a good place for a creator to discover that they may be trying to get into a service which does not match their content, it's not so clear how Gleev for example will signal this otherwise, perhaps a separate screen is needed about this regardless?

Continuation of prior point. Does Gleev need some more custom messaging to make sure its clear what its about? e.g. Updating YPP page?

Continuation of prior point. Should this be configurable so that Vintio and others can change?

What is status of YPP being configruable as on or off in Atlas instance?

How will we policy wise deal with people signing up, say with a cooking channel, even if we add all the messaging described? Obviously tehy should not receie a payout, but how will they learn about why they are not a fit?

It's very unclear for me how YPP should work outside of Gleev+Vinteo: YPP has distinct parts

1. who pays (until council does) and what are terms?: operationally it seems complex for us to start paying for all sorts of other gateways, so probably not?
2. what creator backend to use: if there are distinct backends, different gateways may end up onboarding same creator, but perhaps this is totally fine, as council in the end probably will not reward duplicates?
3. what synching infra to use: these could all be totally distinct.