C.25:5 - Archetypal Grounding

Tell. A quality family is not automatically one metric. Use one Characteristic when one measure and Scale carry the claim; use a Q-Bundle only when several differently typed contributors are jointly load-bearing.

Minimal completed availability case. Under ServiceQualityScheme-v4, the claim says: CheckoutAPI maintained at least 99.9% availability for customer-facing request handling over the rolling 30-day window. Its exact bearer is the independently identified CheckoutAPI System. Its Q-Bundle content has Name: Availability, ClaimScope: customer-facing request handling, Measures: AvailabilityRatio[%] >= 99.9, and QualificationWindow: rolling 30 days. WorkScope, Mechanisms, Status, and Evidence are omitted because this drafting use does not rely on them. If evidence reliance, a failover prerequisite, or a gate later becomes current, add only the direct relation or slot that question needs.

Escalation examples. A resilience or security claim often needs several measures, scenario or attack-class scope, mechanisms or control statuses, and a qualification window. Those contributors belong in the bundle only when they are part of that claim’s truth conditions; treating the family as one scalar score would erase which contributor failed.