Current maturity vs target maturity
Current maturity is where you are, target maturity is where you intend to be, and the distance between them drives priority.
Last updated June 1, 2026
Every capability in CAMP carries two maturity values: where you are now, and where you want to be. The gap between them is what gives Forest something to act on.
Current maturity
Current maturity is your assessed state today, scored 0 to 5 based on your gate answers and the detail behind them. It is a snapshot, not a goal. It reflects the practice as it actually runs.
Target maturity
Target maturity is the level you intend to reach. It is not always 5. Pushing every capability to Optimized would waste effort on functions that do not warrant it. A nice-to-have capability might have a target of 2 or 3, while a compliance-required one may need to reach 4 or higher. Setting realistic targets is part of building a roadmap you can actually deliver.
Why the gap drives priority
Forest calculates Priority as (target maturity minus current maturity) times criticality. Two forces shape that number:
A wider gap between current and target raises priority.
Higher criticality multiplies the result, so important capabilities rise faster.
This is why a capability sitting at maturity 1 with a target of 4 and compliance-required criticality will outrank a low-criticality capability with the same gap. See Criticality ratings for the multiplier.
Targets are a planning decision, not a default. Set them deliberately, because they directly shape what Forest recommends you do next.
Because the Forest Intelligence Service is deterministic, the same current and target values always produce the same priority. Adjust either one and the roadmap updates predictably.