Why a No or Unknown affects maturity

When you answer No or Unknown to a gate question, Forest holds that capability's maturity at the low end of the scale. This is intentional, and it is one of the most useful things the assessment does for you.

A No is a real signal

If a capability is not in place, its maturity is genuinely low. Recording that accurately is what lets Forest find the gaps worth closing. A capability with high criticality and a No is exactly the kind of finding that should rise to the top of your priorities, because Priority is calculated as (target maturity minus current maturity) times criticality. A low current maturity widens that gap.

An Unknown is also a finding

Unknown does not mean the answer is neutral. If no one can confirm whether a capability exists or how it operates, that itself is a visibility gap. You cannot manage what you cannot see. Forest treats Unknown conservatively rather than giving credit you have not earned.

An Unknown today is a prompt to go find the owner, gather evidence, and answer it properly. Resolving Unknowns is often the fastest way to sharpen your assessment.

Why this matters for trust

Because the Forest Intelligence Service is deterministic and explainable, every low score traces directly back to the answer that produced it. There is no hidden penalty and no estimation. If a capability scores low, you can point to the exact gate answer behind it.

When you later confirm the capability and update the answer, the maturity score moves accordingly. See How gate questions work for the mechanics.