C.21:4.0a - One replay basis for every persisted coordinate
Every persisted, compared, aggregated or published C.16 measurement coordinate makes the following values recoverable. This is a field group, not another public kind. An ordinary non-measurement health claim retains its own support; writing or publishing it does not create a measurement chain:
DHCReplayBasis := <DisciplineRef, IntendedUse, ClaimScopeRef, ComparisonBasis, CharacteristicRef.edition, ScaleRef.edition, UnitRef.edition?, DHCMethodRef.edition, MethodRef, MethodDescriptionRef.edition?, MeasurementModelRef.edition?, CalibrationBasisRef?, TimeOrPopulationBasis, DHCDefinitionSetRef.edition?, TargetSliceRef?, DistanceDefRef.edition?>
DHCMethodRef.editionresolves the same Characteristic, Scale, Method, MethodDescription, model, calibration, and uncertainty semantics named by the active fields. A mismatch is not repaired by choosing one field as “primary.”DHCDefinitionSetRef.editionappears only when a named reusable definition selection exists.TargetSliceRefappears only when the named computation or publication consumes an A.2.6 selection. Every selected slice must be shown to belong to, or otherwise be covered by, the authoritativeClaimScope; the slice never substitutes for that scope.DistanceDefRef.editionappears only when the Scale comparison or target-distance rule uses a separately declared distance.- Evidence paths, lane tags, currentness, assurance, acceptance, public names, and publication refs are added only when the receiving use consumes those separate results.