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:15:20 UTC

A.19.CN:8 - Archetypal Grounding

The cases use plain-language normalization descriptions to illustrate the choices. Applying a selected normalization requires its A.19.UNM method and instance references and the backing required by C.16.

A.19.CN:8.1 - Industrial line — Weld‑quality CN‑frame (AssemblyLine_2026)

  • cs_basis: BeadWidth[mm] (target 6.0±0.2), Porosity[ppm] (↓), SeamRate[1/min] (↑ until limit)
  • chart: reference jig, fixture ID, torch type; MethodDescription#Weld_MIG_v3
  • normalization: affine rescale on gray‑level calibration → invariant = physical porosity
  • comparability: normalization‑based (UNM) (calibration tables applied)
  • aggregation: a minimum bound only for a declared bottleneck quality model; commutative count addition only for disjoint contributions; time = per-shift histograms
  • RSG hook: WelderRole.Ready requires Porosity ≤ 500 ppm & BeadWidth within ±0.2 mm admitted by this CN‑frame.

A.19.CN:8.2 - Software/SRE line — Latency CN‑frame (SRE_Prod_Cluster_EU_2026)

  • cs_basis: P50Latency[ms] (↓), P99Latency[ms] (↓), Load[req/s]
  • chart: client vantage, trace sampler v4; MethodDescription#HTTP_probe_v4
  • Before comparing a client end-to-end reading with a server processing reading, resolve their Characteristic and observation basis. Both may use ms yet answer different questions. Keep separate coordinates or obtain readings for the same declared characteristic and basis; a unit conversion alone cannot supply that match.
  • normalization: monotone time‑warp compensation for collector skew; invariant = percentile order
  • comparability: normalization‑based (UNM) with declared normalization
  • aggregation: use a max-of-mins latency fold only when the declared service model justifies it; a WLNK bound needs its own bottleneck model. Neither follows from latency percentiles alone.
  • RSG hook: DeployerRole.Active gated if P99 < declared SLO over the admission window.

A.19.CN:8.3 - Clinical/episteme line — Trial‑outcome CN‑frame (Cardio_2026)

  • cs_basis:
    • slot_id: ΔBP characteristic: BloodPressureChange scale: { type: ratio, unit: mmHg } polarity: down
    • slot_id: AdverseRate characteristic: AdverseEventRate scale: { type: ratio, unit: “%” } polarity: down
    • slot_id: Age characteristic: Age scale: { type: ratio, unit: years } polarity: none
  • chart: cohort definition; MethodDescription#TrialProtocol_v5
  • normalization: the named propensity-score case-mix adjustment uses its declared covariates and target population to estimate the specified ΔBP contrast. Preserve the estimand, adjustment assumptions and residual limitations; the adjusted estimate is an output, not an invariant guaranteed by the method name.
  • comparability: normalization‑based (UNM) (post‑adjustment)
  • aggregation: recombine subcohorts only under the declared population and weighting model; select the law or supported bound for each named safety outcome under its own justified dependency model.
  • RSG hook: evidence-use validation of an admission requires CN-frame acceptance. A named assurance claim uses B.3 and the relation or bounded-use evidence its argument needs; CL may summarize that evidence but supplies no automatic assurance result.

A.19.CN:8.4 - Worked mini-schemas (entity and relation mixtures across CN-frames, informative)

The three small schemas below show an operations use, an assurance use, and an alignment use. They are explanatory representations, not storage requirements. Each keeps the bearer, system-role kind and assignment, measurement or evaluation result, source-local relation, and evidence use distinct.

A.19.CN:8.4.1 - Operations CN‑frame — runtime gating and enactment

Entity graph view:

System ── classifiedAs ──> SystemRoleKind
System + SystemRoleKind + scope/window ── assignment ──> SystemRoleAssignment
Role-state graph ── lists ──> State
Checklist ── tested by evaluation Work ──> StateAssertion
Work ── performedBy ──> assigned System
Work ── enacts ──> Method

The System is classified under the local system-role kind and participates in the obtaining assignment used by this RSG account.

An asserted evaluation or operational Work additionally needs the complete A.13 core: the performing System, local agential-role kind and its membership criterion, and an obtaining assignment of its declared direct species for the relevant scope and time. A.15.1 independently admits the Work; F.6 applies afterward only when precise assignment-bound attribution is needed. The schema abbreviates these grounds; its arrows do not establish them.

A role-state graph lists states such as Ready, Waiting, or Degraded. Evaluation applies the state checklist and supports a StateAssertion. In this gating use, operational enactment requires an admissible assertion that an enactable state obtains; the Work, Method, assignment, and result remain different objects.

Relational stub:

TableKey columns (essential)
ROLE_ASSIGNMENTRA_ID; HOLDER_SYSTEM_ID; SYSTEM_ROLE_KIND_ID; REFERENCE_SCHEME_ID; SCOPE_REF?; WINDOW_FROM; WINDOW_TO
RCS_SNAPSHOTSNAP_ID; RA_ID; WINDOW_FROM; WINDOW_TO; CHAR_ID; VALUE; UNIT?; SCALE_TYPE; RESULT_REF
RSG_STATESTATE_ID; SYSTEM_ROLE_KIND_ID; NAME; ENACTABLE
CHECKLISTCHK_ID; STATE_ID; PREDICATE_TYPE; PREDICATE_SPEC
STATE_ASSERTIONSA_ID; RA_ID; STATE_ID; CHK_ID; WINDOW_FROM; WINDOW_TO; VERDICT; NORMALIZATION_INSTANCE_ID?; BRIDGE_USE_CLAIM_REF?
WORKWORK_ID; PERFORMER_SYSTEM_ID; METHOD_ID; WINDOW_FROM; WINDOW_TO; result and evidence refs as needed

The RCS snapshot keeps the characteristic, value, any applicable unit, scale, window, and result identity visible. A StateAssertion separately identifies any normalization instance and any claim that uses a Bridge. An enactment query can therefore ask whether the latest admissible assertion for this assignment has an enactable state and a passing verdict without treating a role label, CN-frame, or Bridge as the acting System.

A.19.CN:8.4.2 - Assurance CN‑frame — evidence freshness and related local meanings

Entity graph view:

NormalizationMethodInstance ── used for ──> characteristic re-expression
F.9 Bridge ── relates ──> exact source and target F.17 cells
ComparisonClaim ── cites ──> normalization instance and/or Bridge-use claim
RelianceClaim ── cites ──> evidence status and assurance limits

The normalization instance identifies the declared re-expression and its validity window. The Bridge identifies only an obtaining relation between two local senses. A comparison that relies on either one says so in its own use claim; its evidence and assurance limits remain explicit.

Relational stub:

TableKey columns (essential)
NORMALIZATION_METHODNORMALIZATION_METHOD_ID; KIND; DESCRIPTION_REF
NORMALIZATION_INSTANCENORMALIZATION_INSTANCE_ID; NORMALIZATION_METHOD_ID; SRC_CHAR_ID; TGT_CHAR_ID; FORMULA_SPEC_OR_LUT_REF; VALIDITY_WINDOW; EVIDENCE_REF
BRIDGEBRIDGE_ID; SOURCE_CELL_REF; TARGET_CELL_REF; PREDICATE_PROFILE
BRIDGE_USE_CLAIMBOUNDED_USE_CLAIM_ID; BRIDGE_ID; DIRECTION; CORRESPONDENCE_RULE; APPLICABLE_USE; TOLERATED_LOSS; POLARITY
COMPARISON_USEUSE_CLAIM_ID; RESULT_REF; NORMALIZATION_INSTANCE_ID?; BRIDGE_USE_CLAIM_REF?; EVIDENCE_USE_REF; ASSURANCE_REF?
ASSURANCE_EVENTAE_ID; USE_CLAIM_ID; EFFECT; DETAILS; WINDOW

The table can express the relevant claims and their audit path; its presence supplies no missing evidence. A changed assurance result, stale normalization instance, or revised evidence can reopen only the comparisons whose grounds it changes.

A.19.CN:8.4.3 - Alignment CN‑frame — design-time reuse across local schemes

Entity graph view:

Checklist for target state ← re-expression (N when normalization is used) ─ Checklist for source state
source F.17 cell ── obtaining Bridge under its predicate profile ──> receiving F.17 cell
SystemRoleKind' ── stated refinement relation ──> SystemRoleKind

A checklist re-expression cites the normalization instance when it uses normalization. When it also needs a semantic correspondence or difference between local senses, apply §4.3: test the F.9 predicate, retain any missing or unresolved required correspondence, and separately ground the use of an obtaining Bridge. A stated refinement between system-role kinds records how their state distinctions correspond; it must preserve the entailment needed for enactability rather than relying on similar role names.

Relational stub:

TableKey columns (essential)
RSG_REFINEMENTREFINEMENT_ID; SOURCE_SYSTEM_ROLE_KIND_ID; TARGET_SYSTEM_ROLE_KIND_ID; SOURCE_STATE_ID; TARGET_STATE_ID; ENTAILMENT_RULE; EVIDENCE_REF
CHECKLIST_REEXPRESSIONREEXPRESSION_ID; SRC_STATE_ID; TGT_STATE_ID; NORMALIZATION_INSTANCE_ID?; BRIDGE_USE_CLAIM_REF?; SOURCE_EDITION; TARGET_EDITION; VALIDITY_WINDOW?

At least one enactable source state must correspond under the stated rule to an enactable target state when that is the promised refinement. The re-expression record fixes the two editions and any validity window required by the re-expression or receiving use, so later changes can reopen the affected alignment rather than silently changing an old checklist. A referenced UNM instance retains its required validity window.

A.19.CN:8.5 - Same basis, different holder and timing cases

For this worked case, the receiving comparison cites CN-Spec E7, and its commissioning control requires independent certification of E7’s comparison basis. Alice authored that basis. After her stewardship assignment ends, she receives a certifier assignment and examines E7. The holder condition fails: the later assignment still certifies her own basis.

Bob’s certifier assignment instead overlaps Alice’s stewardship assignment. When Bob neither authored nor materially selected E7’s basis, this local holder condition is satisfied despite the overlap. The receiver must still establish Bob’s authority for E7, the required examination and any stronger organizational-independence condition from the commissioning control. Missing evidence for one of these conditions leaves that dependent certification conclusion open; different names alone do not establish it.

In an ordinary comparison with no independent-certification requirement or claim, Alice may use a sufficiently supported E7 basis and publish the comparison as uncertified. If E8 later changes the compared population or normalization basis, reopen only uses and certification claims depending on that changed basis. Correcting E7’s registry display while its content and evidence stay fixed does not have that effect.