2.6 Measurement Models: How Much, and Against What Bound?
Every system emits numbers, and most of them are just telemetry: observations with no engineering meaning attached. A measurement model gives selected observations meaning by relating them: usage to cost, cost to a budget, concurrency to a capacity. It answers the quantitative question the earlier families set aside — how much, and against what bound?
2.6.1 The Canonical Move: Quantities, Relations, and Bounds
Engineering has many quantitative representations: performance and parametric models, capacity models, cost models, and the budgets and envelopes they are compared against; queueing and resource models appear where contention matters11. Edward D. Lazowska et al., Quantitative System Performance: Computer System Analysis Using Queueing Network Models (Prentice-Hall, 1984).. The move they share is small but decisive. Telemetry is observation; a measurement model relates quantities so that a bound becomes statable. A node is a quantity; a relation is an accounting or functional link between quantities — usage times price is cost, concurrent jobs are capacity demand; a bound is the envelope a quantity is compared against (Figure 2.6-1).
Once quantities are related to a bound, the claims a designer wants become expressible: upper and lower bounds, budgets, capacity constraints, rates, conservation relations, tolerances, and margins. The analyses follow — aggregation, comparison against a bound, sensitivity and capacity analysis, forecasting. Figure 2.6-2 draws the core relation: a current value read against a separately declared reference. The payoff is that "are we within budget?" becomes a comparison against a modeled bound rather than a guess over a dashboard.
2.6.2 DocAble: GenAI Cost and Capacity
DocAble's consequential quantities are the cost of its GenAI usage and the capacity its concurrent work demands. The model keeps two chains deliberately separate, because they answer different questions and are compared against different bounds.
MODEL CARDGenAI cost and capacity · Measurement
- Engineering question — What does GenAI usage cost against budget, and what capacity does concurrent work demand?
- Model — two related chains: usage and pricing determine an attributable cost; concurrency determines a capacity demand.
- Property — attributable cost can be compared against a declared budget; capacity demand can be compared against a capacity envelope.
- Quality attribute — cost-awareness; capacity planning; operability.
Figure 2.6-3 draws the two chains. Note the deliberate wording of the property: the model says cost can be compared against a budget, not that cost must not exceed one. The cost chain is observational — a computed ratio, surfaced and reported, that never blocks work as it is spent. The capacity chain is a runtime-tunable cap, adjustable rather than proven. A cost figure is evidence; whether crossing a budget should block work, raise an alarm, or simply be recorded is a separate question of enforcement.
DocAble does not attach a hard invariant to either quantity. Cost is routed to the administrative pane for observation and accounting, while capacity is controlled through a runtime-tunable limit. The model makes both quantities available for engineering use without requiring either to become an enforced obligation.
2.6.3 Tolerance and Margin
A bound is rarely a single line. A budget usually carries a margin; a capacity envelope leaves headroom. Those are the measurement family's version of the tolerance idea from the opening chapter: the model represents not just a target but the band of acceptable variation around it, so that "within tolerance" and "over the line" are both statable. The point is only that a measurement model can carry a margin — not to reopen the degrees-of-freedom discussion the opening chapter already settled.
The cost-and-capacity model makes spending attributable and demand comparable to an envelope. It does not decide the budget, guarantee the numbers are collected correctly, or enforce the bound. Figure 2.6-4 draws that separation: the model defines the quantity and the reference; whether a comparison is merely observed, used to adapt behavior, or enforced by a gate is Alignment's decision. This is the clearest case in the Part of a model that earns its place by exposing a property while leaving every question of enforcement open.
Measurement counts what is happening now. The last family asks what already happened, and what records it.
Works Cited
- Lazowska, Edward D., John Zahorjan, G. Scott Graham, and Kenneth C. Sevcik. Quantitative System Performance: Computer System Analysis Using Queueing Network Models. Prentice-Hall, 1984.