C.25:13.1 - Use one U.Characteristic when

A quality claim should terminate in one admissible CHR characteristic only when all of the following hold together:

• one measurable aspect is actually doing the evaluative work,
• one declared scale is enough to compare relevant cases,
• the bearer and scope are already clear without introducing extra quality slots,
• mechanism or status presence is not itself part of the core quality head,
• and downstream gates can read the claim without needing a bundle decomposition.

Examples include a narrowly declared AvailabilityRatio[%], a specific latency percentile, or one response-time threshold under one fixed window.