When a feature is developed, its inventory elements are defined in inside ansible-playbooks':
* group_vars - common variables that will typically be reused between both development and production hosts
* host_vars - specific variables that need to exist in both places but will typically differ, or must be configurable in production
This is important because of [Ansible variable precedence](https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable) implies that inventory group_vars gets overridden by whatever is in playbook group_vars.
In addition, development has Vagrant integration variables that affect things in a different way than how production handles stuff with a private inventory. For example:
* vagrant_groups is a variable that does group assignments in development; in production, that group assignment is done natively in a private ansible inventory
> * when creating a production deployment of a new feature, the engineer doing so must make sure to implement all such group assignments
* vagrant_playbooks is a variable that defines what vagrant provision does in development; in production, that list of ansible-playbook invocations is done manually
> * when creating a production deployment of a new feature, the engineer doing so must make sure to run all such playbooks in order
