Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:25:20 UTC

A.19.CN:11 - SCR / RSCR Harness (acceptance & regression)

These are concept‑level checks; notation‑agnostic.

A.19.CN:11.1 - SCR — Acceptance (first introduction)

  • SCR‑A19.4‑S01 (Completeness). CN-Spec has every applicable mandatory value. Each cs_basis position declares its Scale and value meanings, Unit when that Scale has one, and any preference rule used for desirability ranking. Descriptive comparisons need no preference rule. The chart names its reference state and coordinate patch; measured values cite their C.16 measurement method/protocol, while evaluated or otherwise ascribed values cite the rule and basis that establish them, as required by CC-A19.D1-2 and CC-A19.D1-3.
  • SCR‑A19.4‑S02 (Normalization clarity). When normalization is used, normalization identifies the admitted mechanism and provides the normalization references required by A.19.UNM (methods / invariants / fix, and instances when used). If instances are referenced in assurance logs, their evidence/backing and validity constraints are handled by C.16, not by A.19.CN.
  • SCR‑A19.4‑S03 (Comparability test). Provide one worked coordinatewise or normalization-based comparison and the source/evaluation basis needed for its result. Use an Evidence Graph reference when that is how the required basis is represented.
  • SCR‑A19.4‑S04 (Γ‑fold audit). When aggregation is used, the rule states the intended result, law and applicability basis, with only the required property claims; the reviewer reconstructs the result on a toy set under that model.
  • SCR‑A19.4‑S05 (Required certification). Identify the receiving claim/control and relied-on CN-Spec edition or admission basis. If independent certification is required, check the certifier against authoring/material-selection history, then the applicable authority and examination conditions. Replay both successive same-holder assignments and overlapping different-holder assignments. When neither an independent-certification claim nor a control applies, keep the sufficiently grounded comparison; add a certification status only when it matters to the receiving use.
  • SCR‑A19.4‑S06 (Bearer and basis recoverable). For each CN-Spec characteristic used in the worked example, retain its bearer, Characteristic and Scale editions, reference/comparison basis, any qualifying scope/window, and the measurement, evaluation or other value-ascription grounds required for the reading. Shared frame-level values need not be repeated for every characteristic. Use A.10 when provenance or bounded reliance must remain replayable.

A.19.CN:11.2 - RSCR — Regression (on change)

  • RSCR‑A19.4‑R01 (UNM edit). When normalization changes, flag every comparison and Bridge-use claim that cites that normalization for affected-only reassessment, then rerun the corresponding worked comparisons.
  • RSCR‑A19.4‑R02 (Slot or basis change). A changed definition receives a new edition. Preserve old results with their original basis; their present admissibility still depends on their evidence and intended use. A display-only correction that preserves the definition is handled as such.
  • RSCR‑A19.4‑R03 (Chart drift). Updating measurement protocol bumps edition; historic Work keeps old edition link.
  • RSCR‑A19.4‑R04 (Fold change). A changed fold requires reassessment of roll-ups that rely on the changed rule. Recompute dependent results; reuse unaffected results and retain historical outputs with their original rule.
  • RSCR‑A19.4‑R05 (Changed relation or use basis). After either endpoint or its relation-semantic basis changes, test the applicable F.9 predicate for the new candidate. Reassess the separate use direction, correspondence rule, loss tolerance and reliance when their grounds change; reopen only dependent claims.
  • RSCR‑A19.4‑R06 (Deprecation rule). On deprecating a CN-frame, the re