C.4 Measurement
Measurement models represent quantitative properties of the running system and the bounds against which they are evaluated. In review, they expose what is measured, what bound applies, and what evidence supports that bound.
Engineering question. What quantity matters, how is it measured, what bound has been declared, and what should happen when the bound is exceeded?
Representation.
Measure
id
quantity
unit
scope
observation_source
Bound
measure_id
threshold
aggregation
Disposition
bound_id
mode # report | warn | gate
The disposition stays separate from the measured bound; its mode records whether a bound is report-only, warning-producing, or admission-blocking. Measurability alone does not justify enforcement.
Figure C.4-1 separates the measurement from the authority that may or may not attach to it.
Property. A measurement model can state that request latency remains below a declared bound for a defined request class, queue depth below a declared ceiling, or processing cost within a specified envelope. Scope, statistic, and aggregation window are part of the property; a threshold without them is underspecified.
Authority and correspondence. Sensors supply observations; the model supplies their scope, interpretation, and declared bounds. Measurements remain observations unless the evidence warrants warning or gate authority.