Red Hat Cloudforms ships with ruby gems included to provide functionality. These gems are provided for internal use of the product. Any coding against a gem or API is considered script support and will be handled according to Red Hat's standard policy on scripting:
https://access.redhat.com/site/articles/369183

Gems shipped with Cloudforms may be updated as Cloudforms itself is updated. Red Hat does not guarantee backwards-compatibility of gems. Red Hat suggests that customers that are using gems use semantic versioning.
http://guides.rubygems.org/patterns/#semantic-versioning

New Gems/newer versions of currently supplied Gems can be installed using the standard Gem install methods. Those new Gems/newer Gems can be used in Automate as the user space is loaded after the appliance internal space (bundle clean). This allows the Automate developer to install Gems without worries about collisions with internally used Gems. Again semantic versioning is always recommended. Please note that any Gems installed in this way must be installed on all appliances that have the Automate role that would execute the code calling for the newer Gems.

Red Hat suggests customers use standard APIs for interactions with the product. Red Hat provides support for any API that ships as part of their software, in accordance with the above scripting support policy.