Domain-specific operational outcomes — the point where engineering health meets the customer's process.
How work moves once started: how long it takes, how much is in flight, and where it waits.
Problem definition, readiness and the decisions that must be settled before implementation begins.
Whether findings become improvements that verifiably hold, and whether obsolete things are actually retired.
Capacity, commitment and what erodes both between planning and delivery.
Whether shipped capability was adopted, and whether adoption produced value.
Service health in production, and whether the customer's process actually completed.
The path from implementation-ready to running, and how often it goes wrong.
Investment allocation, portfolio progress and forecast. The stage where a plan is either still credible or quietly is not.
Whether verification is adequate and whether its signals can be believed.