A.19.UNM:4.1 - UNM operation declaration (normative)
UNM.IntensionRef is the citation name for the A.6.1 declaration episteme presented here. It does not identify a generic family in place of that declaration. The CHR baseline selects its edition before use; the normalize stage resolves to the declaration-local apply operation below. Its four named input meanings, NCV result and eligibility guard come from that selected declaration.
A different realizer of the same declaration changes no suite member. A corrected layout or citation can preserve its C.2.1 identity. A changed argument, law or guard changes the declaration contract and must be selected in the suite and protocol. For example, replacing pass|degrade admission with pass only would change whether apply may produce an NCV for degraded evidence; that hypothetical revision cannot enter through the unqualified name UNM. Whether two declarations concern the same operation family is a separate claim requiring that subject’s kind and identity rule; the UNM label supplies neither.
Scope note. A.6.1 governs this operation declaration. The selected use baseline supplies the project editions and policy references; A.15.2 governs a P2W baseline, and A.15.3 typed filling applies only to independently declared positions. UNM returns the declared operation results and tri-state GuardDecision; gate decisions remain with their governing pattern. Audit below states the information needed to recover an application.
IntensionHeader
IntensionId:UNMIntensionRef:UNM.IntensionRefName: Unified Normalization MechanismStatus: StableVersion:v1.0SuiteRole: CHR.normalize (when enabled by CN/CHR routing)
Imports (cite, don’t duplicate)
A.6.1(shape:U.Mechanism, specialization discipline)A.19.CHR:4.2(CHR suite boundary / membership)A.19.CHR:4.2.1(CHR SlotKind Lexicon)A.19.CHR:4.5(suite protocols: ordering/optionality; suite closure)A.19.CN(CN-frame routing:normalization,comparability.mode)G.0(CG-Spec admissibility and evidence conditions where required downstream)C.16(evidence carriers; calibration/validity for normalization legitimacy)A.17/A.18(measurement meaning & scale lawfulness; not redefined here)
SubjectBlock
SubjectKind: declared normalization methods, with their domains, output kinds and preserved/lost distinctions; functional methods may additionally supply≡_UNMover their admitted inputsRangedValueKind: coordinate values (CV) for named measurable slots in the resolvedDeclaredCharacteristicSpace, withcharacteristicSpaceDescriptionRefand the CN-Spec edition pinned; UNM normalizes values, not characteristicsBearerAndUseBoundary: the bearer, reference or comparison basis, evidence and intended use, with any scope, slices or data window that qualify those values- Input qualification: coordinate values admitted by the selected CN-Spec for this bearer and use, within the configured method’s declared validity window. This is not an operation-application extent or an A.6.1 slice-membership
ExtentRule. ResultKinds:NormalizedCharacteristicValue (NCV)- optional function-kernel equivalence (
≡_UNM) and its set of classes; a congruence claim only for separately checked operations - optional quotient objects and/or
Normalization-fixedrepresentatives (viaNormalizationFixSpec)
Space range and resolution. Use the DeclaredCharacteristicSpace criterion and paired reference resolution in A.19:5.1.1.1. CharacteristicSpaceRef selects the space; CN_Spec.characteristicSpaceDescriptionRef: U.EpistemeRef pins the description supplying its basis. Both must resolve and agree on that space before normalization; otherwise the dependent use remains unresolved and eligibility abstains. Membership establishes the input’s space structure; the selected operation must still resolve its positions, Scales and use conditions.
A changed basis requires a new space reference and position resolution, even if its label or document path is unchanged. Preserve the preceding space, description and results; reuse requires the correspondence and operation conditions of the receiving use.
Operation-local argument and result declarations
The names below are declaration-local designators. ByValue carries the stated value; each named Ref resolves to one value under this declaration’s effective reference scheme. An episteme reference selects its edition; the space reference and its separate description-episteme reference follow the rule above. Cardinality is per application. The first four arguments are shared declarations instantiated separately for apply and UNM_Eligibility.
| Operation and direction | Local designator | Meaning and ValueKind | Designation; cardinality |
|---|---|---|---|
| apply / UNM_Eligibility argument | NormalizationMethodInstanceSlot | Configured normalization method selected for the value; NormalizationMethodInstanceId | ByValue; 1 for apply, 0..1 for eligibility |
| apply / UNM_Eligibility argument | CoordinateValueSlot | Coordinate value to transform or assess; CV in the named chart | ByValue; 1 for apply, 0..1 for eligibility |
| apply / UNM_Eligibility / compose argument | CharacteristicSpaceSlot | Space that supplies the coordinate meanings and Scales; DeclaredCharacteristicSpace | CharacteristicSpaceRef; 1, or 0..1 for eligibility |
| apply / UNM_Eligibility / compose argument | CNSpecSlot | CN-Spec used for the bearer, basis, evidence requirements and intended comparison, including any scope, slices or qualification window | CNSpecRef; 1, or 0..1 for eligibility |
| apply result | NCVSlot | Transformed value returned under the selected method’s domain and preservation/loss basis; NCV | ByValue; 1 on successful return, 0 without a defined/admitted result |
| UNM_Eligibility result | GuardDecision | Eligibility judgment under the predicates below; pass, degrade or abstain | ByValue; 1 on completed evaluation |
| compose argument | NormalizationMethodInstancePairSlot | Ordered pair of configured methods, first inner and second outer; NormalizationMethodInstanceId2 | ByValue; 1 pair |
| compose result | NormalizationMethodInstanceSlot | Configured composed method, with its declared validity window and evidence basis; NormalizationMethodInstanceId | ByValue; 1 on successful construction |
| quotient argument | domain | Admitted domain D of the selected normalization function, with coordinate meanings recoverable; set of CV values | ByValue or one chart-domain reference; 1 |
| quotient argument | NormalizationMethodInstanceSlot | Configured functional method used to form equality-of-output classes; NormalizationMethodInstanceId | ByValue; 1 |
| quotient result | UNMEquivalenceSlot | Relation on D defined by equality of that function’s outputs | ByValue; 1 on successful construction |
| quotient result | classes | Set D/≡_UNM of all classes of that relation | ByValue; 1 on successful construction |
For each argument row, its bindingPredicate obtains exactly when that application uses the resolved value for the row’s stated purpose: as the transformation operand, selected method, governing space/CN-Spec, ordered composition pair or quotient domain. A supplied but unused value is not bound.
UNM_Eligibility may assess an incomplete proposal; an absent argument has no binding and the corresponding missing-input condition gives abstain. This does not relax apply’s inputs.
For each result row, its bindingPredicate obtains exactly when that application returns the resolved value as the row’s declared result, subject to the result laws below. A returned NCV binds the transformation value; compose binds the identifier of the method it constructed; quotient binds the relation and class set it constructed; the guard binds the judgment it evaluated.
Each binding has the A.6.1 identity and maximal continuous extent within its application; a result binds at return, not before. Equal values returned by different applications have distinct bindings because their applications differ.
SlotIndex (derived projection). Project the designators, ValueKinds, designation rules and cardinalities from these operation-local declarations; the index adds no meanings. The historical Slot suffix permits CHR lookup. A.6.5 relation SlotSpecs are not the source of these operation meanings. Method descriptions, invariants and any NormalizationFixSpec are resolved from the selected configured method and CN-Spec. They qualify the method or a separately chosen representative use; they are not additional arguments of every operation.
Relation note (not a SlotKind). A Bridge, kind relation, or plane relation is cited only when the use relies on that obtaining relation. Its declaration and receiving use remain separate from the UNM SlotIndex.
OperationAlgebra
-
apply- Preconditions:
UNM_Eligibility(…) ∈ {pass, degrade}(fail‑closed;abstain⇒ no NCV output). - Inputs:
NormalizationMethodInstanceSlot,CoordinateValueSlot,CharacteristicSpaceSlot,CNSpecSlot; the selected CN-Spec supplies the bearer, basis, evidence requirements, intended comparison and scope or data window. - Outputs:
NCVSlotfor an input in the selected transformation’s domain, with the declared preservation/loss basis. Undefined inputs produce no NCV; an eligibility result cannot create a transformation value. The optional class/operation results follow their separate conditions below.
- Preconditions:
-
compose- Purpose: build a composed method when the inner outputs lie in the outer operation’s domain and the claimed preservation laws compose. Losses and receiving-use restrictions remain explicit.
- Inputs:
NormalizationMethodInstancePairSlot(roles = {inner, outer}),CharacteristicSpaceSlot,CNSpecSlot; both instances must be admitted for the same declared bearer, basis, intended use and any scope/window. - Output:
NormalizationMethodInstanceSlot(new composedNormalizationMethodInstanceId), with a validity window and evidence pins.
-
quotient(≡_UNM)(optional)- Preconditions: one fixed functional normalization on its domain, with an explicit output equality. Recover that domain and the method/use basis.
- Inputs:
domain, resolved from the characteristic-space declaration or a declared chart domain, andNormalizationMethodInstanceSlot. - Outputs:
UNMEquivalenceSlotand itsclassesset. Inherited operations additionally require equivalent-output and representative-independent-availability proofs; a class query additionally requires constancy on each class. - Use the declared
NormalizationFixSpeconly when a representative is needed. It selects a member of a class rather than proving that member was the original input.
Applications of these operations
The ApplicationPredicate differs by operation:
apply: a calculation applies the selected configured method to the bound CV under the bound space and CN-Spec. Its defined, admitted return is the NCV required above. Anabstaindecision prevents this application from starting; passing eligibility alone does not start it.compose: a construction resolves the bound inner/outer methods, checks the domain and preservation conditions and constructs their composite for the bound space and CN-Spec. A failed condition yields no composed-method result.quotient: a mathematical construction uses the bound functional method and domain to determine equality of outputs and form its classes. A symbolic construction is sufficient; enumeration of an infinite domain is not required. Stronger inherited-operation and query claims retain their separate proofs.UNM_Eligibility: an evaluation assesses the bound proposal under the eligibility predicates below and returns the corresponding GuardDecision. Its result is separate from any subsequent normalization.
For each operation, the ApplicationIdentityRule identifies one invocation at its calculation or construction locus, from taking up those operands for that operation until return or termination. References to the same uninterrupted invocation reidentify one application. A second invocation, including a nested or later one with the same operands, method, qualification window and result, is another application. Changing an operand after beginning a fresh calculation starts another invocation; a continuation of an interrupted calculation counts as the same application only when continuity of that same invocation is established.
The ApplicationExtentRule takes that invocation’s interval: first use of its arguments through its return or termination. For the guard it is the eligibility evaluation; for compose it is the composite construction; for quotient it is the class construction; for apply it is the value calculation. An unfinished invocation has an open extent and no unreturned result binding. The data’s qualification window and the method’s validity window do not date these invocations. A trace may designate an invocation; a copied record, matching value or valid method identifier does not establish it. Ordinary function and projection guidance remains usable without an assertion of dated U.Work.
For example, with fixed method n(x)=x/10, domain [0,100] and the same CN-Spec, two separate calculations of n(20) both return 2. The first operand-to-return episode and the second are two apply occurrences; each binds 20 and its own return of 2. A third record containing 2, with no corresponding calculation, supplies no third result binding. Two constructions of g∘n, or of the same quotient, are likewise distinct when performed in separate construction episodes; their equal constructed mathematical values do not merge those episodes. Conversely, a second description of the first episode adds no application.
LawSet (UNM laws; identifiers are stable)
- UNM‑L0 (Values, not characteristics). UNM produces
NCVas a value under declared invariants; it does not redefine the underlying characteristic meaning (measurement meaning remains governed by A.17/A.18 and evidence by C.16). - UNM‑L1 (Declared method classes). A normalization method instance is admissible only if its method is declared in the allowed method class set:
{ratio:scale, interval:affine, ordinal:monotone, nominal:categorical, tabular:LUT(+uncertainty)}. - UNM‑L1a (Method semantics are governed by the method).
NormalizationMethoddefines invariants, closure (composition / inverses where defined), and validity rules. UNM consumes these declarations; it does not invent extra admissibility. - UNM-L2 (Directed result before narrower claims). Return the defined transformed value with its domain and preserved/lost distinctions. Functional equality of outputs forms equivalence classes on that domain. A receiving operation descends only after compatibility and, for a partial operation, representative-independent availability hold. A query descends only when constant on the classes; otherwise retain/refine the input or return the missing distinction.
- UNM-L2a (Declared-basis locality). Every transformed value, function-kernel equivalence and stronger operation/query claim retains the selected method, domain, characteristic space, its separately referenced description episteme, CN-Spec edition, bearer and comparison basis. Keep the scope and data window and the method’s declared validity window. Reusing an unchanged equivalence for a new query does not make that query recoverable; assess its own constancy/compatibility and the receiving-use conditions.
- UNM‑L3 (Fail‑closed). If admissibility/evidence is insufficient (or required inputs are missing/stale), UNM does not coerce; it yields
abstainordegrade(tri‑state guard discipline) and may surface a freshness/work request (see A.19.UNM:4.5). Didactic reading:abstain⇒ no admitted NCV from this proposed application, so a comparison depending on that output cannot proceed on this basis;degrade⇒ NCV may be produced but must be treated as policy‑gated and auditable (never “quietly good enough”). - UNM‑L4 (No implicit indicatorization).
NCVdoes not imply “indicator”; indicator status is a separate policy step (UINDM). - UNM-L5 (Relation before reuse). When a receiving comparison depends on an F.9 Bridge, kind relation or plane relation, establish that relation under its own rule and separately assess the receiving use. For an F.9 use, retain its direction, correspondence rule, loss tolerance and required reliance disposition. A change of bearer, scope, corpus, scale, method or window does not itself establish a relation. Assess losses under the receiving rule; a numerical assurance penalty requires an applicable domain model under B.3.
- UNM‑L6 (Time explicitness). Validity windows are named; no implicit “latest”.
- UNM-L7 (Auditability). The application’s selected specifications, supplied inputs, method, conditions, evidence, returned result and any relied-on relation must be recoverable under Audit below. Missing inputs or unresolved references remain explicit when eligibility abstains.
- UNM-L8 (Source references). Downstream uses cite the method, CN-Spec, basis and evidence editions on which they rely; a registry helps locate those sources but does not supply their content.
- UNM-L9 (Publication boundary). Publication and telemetry remain outside these operation declarations; any published normalization result retains the meaning defined here. The Audit information is separately recoverable.
AdmissibilityConditions
Definition (UNM‑Eligibility):
UNM_Eligibility(NormalizationMethodInstanceSlot, CoordinateValueSlot, CharacteristicSpaceSlot, CNSpecSlot) → GuardDecision
where GuardDecision ∈ {pass | degrade | abstain} and follows this predicate semantics:
- pass iff all of the following hold:
- (CN-Spec binding) the selected
NormalizationMethodInstanceIdis declared inCN_Spec.normalization.instances(or an equivalent declaration), its method kind is included inCN_Spec.normalization.methods, and (if present) it satisfiesnormalization.admissible_reparameterizations; the characteristic space, its separately referenced description episteme, CN-Spec edition, bearer, reference or comparison basis and intended comparison are recoverable, together with any scope, selected slices or qualification window required by those declarations or that use; - (Target coordinate binding) the input
CV’sslot_idbelongs to the method instance’s declared bound coordinate set and its value lies in the selected transformation’s input domain; - (Scale‑regime compatibility) the method kind is compatible with the coordinate’s regime (
ratio:scale | interval:affine | ordinal:monotone | nominal:categorical | tabular:LUT(+uncertainty)) and preserves the declaredNormalizationInvariant[*](fromCN_Spec.normalization.invariantsand/or the method description); - (Validity window) the method instance’s validity window covers the active slice/time policy (no implicit “latest”);
- (Evidence sufficiency when routed into governance) when
comparability.mode = normalization-based(or downstream usesNCVin gated decisions), the method instance’s evidence pins satisfyCN_Spec.comparability.minimal_evidence(minimal-evidence conditions defined inG.0; evidence semantics governed byC.16).
- (CN-Spec binding) the selected
- degrade iff all non‑evidence conditions above hold, but the evidence check does not pass and the declared failure behavior permits producing a policy‑gated degraded
NCVrather than abstaining. - abstain otherwise (including missing binding, coordinate mismatch, undefined input, out-of-window validity, or evidence failure when the declared failure behavior is abstain).
Applicability UNM is applicable when:
CN_Spec.comparability.mode = normalization-based, or- a declared downstream step requires “compare-on-invariants” and thus requires normalization.
UNM is typically skipped when comparability.mode = coordinatewise (unless an explicit downstream step requires a declared quotient/fix anyway).
Relation and reuse boundary
- A normalized value retains the method instance and edition, its declared validity window, characteristic space, separately referenced description episteme, CN-Spec edition, bearer, reference or comparison basis, evidence and intended comparison, with any scope or data window.
- If a receiving use depends on a relation between distinct source-local meanings, cite the F.9 Bridge, its direction, what it preserves or loses, and that receiving use. If reference planes differ and the comparison depends on their relation, cite the plane relation as a separate claim.
- A changed bearer, scope, corpus, scale, method or window does not by itself establish either relation. A correspondence between bearer kinds has its own grounds. Retain the receiving-use rule and its loss limits; quantify an assurance effect only under an applicable B.3 domain model.
Γ_timePolicy
- Default:
point(no implicit “latest”). - If normalization relies on time windows, the validity window is part of the method instance and must be declared.
PlaneRegime
- A normalized value keeps the reference plane declared for its input and intended comparison; normalization creates no implicit plane crossing.
- When a comparison relies on a relation between different planes, cite that relation, its direction and loss, and keep its use separate from the normalization result.
Audit
Make the following information recoverable from the specifications, inputs, evidence and results used. Retain a separate record when the receiving use requires one. For an incomplete eligibility proposal, identify missing inputs or unresolved references and the resulting abstain; do not invent an apply occurrence or an NCV.
- for a supplied and resolved CN-Spec,
CNSpecRef.edition+comparability.mode, theCharacteristicSpaceRef, the separatecharacteristicSpaceDescriptionRef: U.EpistemeRefpinned there, and the evaluated bearer - (when present)
CN_Spec.normalization.UNM_id(the selected UNM declaration identity for this CN-Spec) - the selected
NormalizationMethodInstanceId, when resolved, its validity window and anyNormalizationMethodDescriptionRef.edition - declared
NormalizationInvariant[*]andNormalizationFixSpec(if used) - any declared admissible re-parameterizations (if present in
CN_Spec.normalization) - reference or comparison basis, intended comparison, all evidence pins used, and any claim scope, selected slices or data window that qualify this use
- an F.9 Bridge, kind relation, or plane relation only when the recorded result or receiving use relies on it, including direction, preserved or lost meaning, and the receiving use
- the operation evaluated or applied, its returned value or absence of a result, and any emitted
FreshnessRequest/ work request identifiers (see §4.5)