The map update

The change written back to the capability map, which is what makes the whole loop worth running.

The part

What it is

A capability confirmed and not recorded is a capability the organisation still believes it lacks.

This is the smallest step in the module and the one most often skipped, which is why capability maps age badly.

The smallest level

The attributes it carries

Each attribute is one of the framework’s shared types. What a date is, and how it is written, is defined once for the whole model — the note here says what it means in this particular place.

Capability entry
The map entry being updated, so the loop closes on the same record.
Reference shared type
Updated
Lets the age of the map be seen, which is the honest measure of whether it is current.
Date shared type