Approval, queue and block rates
How much of the lane still clears automatically, and what proportion already requires review to stay safe?
NORNR
A cold reporting frame for what agent spend teams should measure before they trust a lane.
NORNR / State of agent spend
Category assetThis edition is intentionally cold. It defines the metrics, failure classes and export expectations that decide whether a lane is merely autonomous or actually governable.
What to measure
These are the category metrics NORNR cares about first.
How much of the lane still clears automatically, and what proportion already requires review to stay safe?
If the lane spends but cannot export a calm packet later, it is not production-ready in finance or risk terms.
These are often the earliest signs that a lane widened faster than the mandate did.
A lane that is technically safe but operationally unreadable still fails the institutional test.
The month-end view matters because many lanes look fine until the close bundle has to survive outside the control room.
Production maturity often fails not on budget amount but on unexplained destination drift.
Failure classes
A report becomes useful when it names recurring failure modes and ties them to the control surface that neutralizes them.
Most model-spend lanes fail through repetition before they fail through one obviously catastrophic action.
Browser lanes fail when the expensive moment is hidden inside many harmless-looking steps.
Desktop and local-agent lanes fail when teams mistake capability exposure for control.
A lane often looks safe operationally and only reveals weakness when finance asks for one defended record.