Structure - vPlan

Within vPlan we divide our objects in basically 3 sections:

Configuration

Third party data

Base data

The configuration section are objects that are generally setup at the start and should not change that often.
Integrations will probably create a lot of these objects, or otherwise retrieve these objects to use the IDs later on.

The third party data section are objects that are pure informational for the front end users.
It exists primarily to facilitate integrations to update their data, and give the front end users the option to change values like the title, without losing the original information on screen.
Most integrations use these objects to push their plannable objects to vPlan.

The base data section consists of object used in the normal day to day usage of vPlan:
Most integrations use these objects to retrieve information about the planning and send it back to the original system.