I guess part of and second question is that when setting attributes does that re-query the api for features that match. For instance if I write feature sets based on company and a user switches account (presuming they have multiple) then calling

setAttributes

would I then need to manually re call the api or is that part of the async action from setAttributes

yes, setAttributes overwrites existing attributes and does rerun which features are shown, and may change the assigned feature values.

So if I'm reading the docs right all features are sent and the rule engine is in context. So there isn't a 'server' side resolver where you would say give me features for company x. It looks like the resolved json would have to hold all the details for all the outcomes. Not that there would be that many to be honest. But I might have concern of using a company id for instance for eval.

that's right

Ok

but you can abstract them as much as you like

So it might behove you to map the id's somewhere else.