Editing Policy setup and structure (section)

== The need to improve [[Dynamic_CFEngine3|Dynamic CFEngine]] ==
Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />
Convergence is one of the fundamental principles of CFEngine the dynamic setup relies on too heavily, because policies are being used to identify dependent and subsequent policies. Policies are being derived from the concept of the 'role' a system has, components are defined in the role and convergently become available to the system. A role has one or more components that may depend on the platform or the flavor of the system. Convergence towards the Desired State is meant for configuring a system, not for the composition of the policy set.<br />
* This may lead to a temporarily inconsistent policy set
* Developers tend to reject this setup, they want to have the policy set available right from the beginning
* The role concept as it was, was far from perfect, because of the redundancy in the different roles.

Enter the Role Profile concept.