Two reads, one habitat

Most maturity tools give you a single number. This assessment deliberately gives you two reads of the same team, because the single number hides the thing that actually predicts trouble.

What can think, vs what is built

The two reads measure different things:

• The cognitive ladder (L0–L5) measures what the team can think and do — its literacy, its practices, the disciplines its people have internalised.
• The habitat maturity model (fourteen dimensions, L1–L5) measures what the team's environment actually delivers — the agents, tests, observability, governance, and workflow that are really in place.

A team can be strong on one and weak on the other. A senior team can join a codebase with no habitat (high cognition, low operational). A junior team can inherit a richly-tooled platform they don't yet use well (low cognition, high operational). A single score would average these away — and the average is precisely the wrong summary, because the mismatch is the signal.

The model is the spine; the ladder is folded in

The assessment leads with the habitat maturity model as its spine — fourteen dimensions, scored with the model's own verbs — and folds the cognitive ladder in as the second read. That ordering is deliberate: the habitat is the thing you can most directly change, and it's where most of the leverage to lift a team actually lives.

The gap is the point

The distance between the two reads is the Habitat Build Gap. It turns two maps into one actionable diagnostic:

• thinking ahead of habitat → build the habitat;
• habitat ahead of thinking → lift the literacy;
• in step → keep both moving together.

That's something a single maturity number can never tell you. See Coherence, not level for why the gap, not the level, is the headline.