B.3:4.3 - Name each characteristic by its bearer and scale
Include a characteristic result only when the assurance argument consumes it. State:
AssuranceCharacteristicResult:
bearerRef:
characteristic:
scaleAndUnit:
valueOrInterval:
interpretationForThisUse:
basisRef:
One characteristic name must not silently change meaning between subjects. System reliability, replication quality, evidential support, proof inspectability, and relation congruence are different characteristics even when a local source labels several of them R or CL.
The legacy letters F, G, R, and CL may appear inside a declared local scheme, but B.3 assigns them no universal cross-domain meaning:
- Formality or inspectability. Formal structure can make assumptions and inference steps easier to check. It raises assurance only when the named argument explains which uncertainty or verification need it closes. Making a wrong model proof-grade does not improve truth or empirical adequacy.
- Claim scope.
U.ClaimScopestays an A.2.6 value. It is not a quality coordinate. Widening or narrowing scope changes the claim and its applicable use under the declared scope rules. - Reliability-like characteristics. Use the exact domain definition, bearer, population or trials, conditions, scale, unit, and qualification window. A system reliability measure and an evidence-quality judgment are not interchangeable.
- Relation congruence. Characterize one exact mapping, calibration, interface, or other relation occurrence only under a declared scale and interpretation. The value neither changes the participants nor supplies a universal penalty.
Never average ordinal values. Do not subtract an ordinal value from a ratio quantity. Thresholds and order comparisons are valid only under the scale that defines them.