Platform blades can be active or inactive. When a blade is active, the features it provides are available when the Caplin Platform starts up; conversely the features of of an inactive blade aren’t available when the Platform starts.
When you deploy a new blade kit the Framework automatically makes the blade active. The blade kit could be a new version of a blade that you’d previously installed; if you’d previously deactivated the old version of the blade, when you deploy the new version, the blade is reactivated.
However, when you first install the Deployment Framework and deploy the core Platform components (Transformer and/or Liberator), some of the built-in Config blades are disabled and remain so until you explicitly enable them.