A.19.CHR:4.8 - Examples
A.19.CHR:4.8.1 - Worked case — two offers from baseline to selected set
Situation and planned baseline. The question is whether either offer can be discarded without accepting a worse price or defect-free proportion. Stipulate an A.15.2 WorkPlan OfferReviewPlan@1, local content locator characterization, selecting suite OfferCHRSuite@1. This case’s suite has the six distinct member declarations in §4.2.2, each at its §4.1 content in the same publication edition as this example. Its stable mech_suite_id is OfferCHRSuite; its obligations are exactly the §4.3 clause set. The full canonical protocol is available, with Fold_Γ optional. The selected path uses apply → Indicatorize → Score → Compare → Select, under the operations’ own eligibility evaluations.
The plan pins OfferCHR-CN@1, OfferCHR-CG@1, the methods and policies below, and the point 2030-01-01T00:00Z in UTC. The suite requires those same references and the exact OfferReviewPlan@1#characterization baseline. No typed filling is needed for this ordinary reference selection. These are planned references; no application or result is claimed by the plan.
Case specifications, outside the suite. Take the two offers, lower-price/higher-quality Pareto rule and all-nondominated selection rule defined as OfferPareto@1 and OfferSelection@1 in A.6.7 §4.6. The raw case values here are A=(1000 eurocents, 0.8), B=(1200 eurocents, 0.9), stipulated exact rather than measured in a claimed real-world episode. OfferCHRSpace@1 has basis positions cost and quality, with the price and defect-free-proportion Characteristics. Its input price chart uses eurocents; its normalized price chart uses EUR. Quality uses the same dimensionless ratio scale in both charts.
| Pinned case reference | Content used by the protocol |
|---|---|
OfferCHR-CN@1 | Admits A and B on this basis; binds the bearer identified by each coordinate/profile to OfferScope@1, selected slice set {OfferSlice@1}, the concept plane, the CHR reference scheme and the planned evaluation point. Its comparability mode is normalization-based into the EUR/quality chart. The admitted normalizers are CentsToEUR@1 and QualityIdentity@1; indicator_policy is BothPositions@1. Both complete candidates satisfy acceptance, with no further threshold. |
CentsToEUR@1 | Configured ratio:scale method on cost values from 0 to 1,000,000 eurocents; n(x)=x/100 EUR. Bound coordinate set={cost}. Preserves price, equality and order; loses no distinction on this domain. |
QualityIdentity@1 | Configured ratio:scale method on quality values in [0,1]; n(q)=q. Bound coordinate set={quality}. Preserves all values and their order. |
BothPositions@1 | Select exactly {cost,quality} from OfferCHRSpace@1, retaining position meanings and order for profile projection. The policy is evidence-gated and uses the CG default; missing either required value means abstain. |
IdentityScore@1 | Description of the stipulated admitted identity-scoring Method: apply the identity to each normalized measure. Domain/codomain are price in [0,10000] EUR and quality in [0,1]; result cardinality is two measures. Preserve scales and polarities (lower price, higher quality). No aggregation or scalarization occurs. |
OfferCHR-CG@1 | SCP permits the two declared ratio-scale normalizations, identity scoring and componentwise order comparisons. ComparatorSet contains OfferPareto@1. MinimalEvidence requires the exact two input values, basis, configured-method declarations and their algebraic preservation facts. CN normalization evidence uses the same requirement. No evidence override or degrade branch is selected. |
Both normalizer instances and their method descriptions are declared by the case CN-Spec, with validity window [2030-01-01T00:00Z, 2030-01-02T00:00Z). Their positive scale factors establish the stated preservation facts. The profiles retain their exact bearer, basis positions and the resulting EUR/quality chart. No quotient, class representative or additional CharacteristicSpacePredicate is used.
Applied protocol, separate from the plan. Stipulate the following actual mathematical invocation episodes, each extending from taking up its named inputs to returning its result. Its inputs bind by actual use and its results bind at that return under the selected declaration. The evaluation point qualifies the offers; it is not the calculation interval. All episodes retain the case’s scope, slice set, scheme, plane, point, basis and cited evidence. This account asserts no dated U.Work.
| Resolved stage | Bound inputs and eligibility | Returned value |
|---|---|---|
A.19.UNM §4.1 / apply | Four invocations, one per coordinate: the bound normalizer, raw CoordinateValueSlot, OfferCHRSpace@1 and OfferCHR-CN@1. Each UNM_Eligibility evaluation passes: coordinate, method, domain, invariants, validity and evidence agree. | The cost invocations return 10 EUR and 12 EUR; the quality invocations return 0.8 and 0.9. Each has its own NCVSlot binding. |
A.19.UINDM §4.1 / Indicatorize | For each bearer, OfferCHRSpace@1, OfferCHR-CN@1, BothPositions@1 and OfferCHR-CG@1; no MinimalEvidence override. The exact policy and complete evidence yield pass. | Each invocation returns {cost,quality}; the projected profiles retain those positions and their normalized values. |
A.19.USCM §4.1 / Score | Each projected InputProfileSlot, OfferCHR-CN@1, OfferCHR-CG@1 and IdentityScore@1; no override. ScoreEligibility passes the admitted method, normalized input and evidence. | Two separate ScoreProfileSlot bindings: A=(10 EUR,0.8), B=(12 EUR,0.9). |
A.19.ULSAM §4.1 / Fold_Γ | The baseline selects its declaration as the sixth suite member but skips this optional step. There is no multi-value fold in this use. | No fold application or output is asserted. |
A.19.CPM §4.1 / Compare | The exact A/B score profiles, case CN/CG, OfferPareto@1 and the common use arguments. CompareEligibility passes; normalization refs and preservation facts are retained. | Invocation cCHR returns {A ∥ B}. |
A.19.SelectorMechanism §4.1 / Select | CandidateSetSlot={A,B}; comparisonBasis={cCHR}; requiredComparisons={(A,B,OfferPareto@1)}; tokenProvenance maps A ∥ B to cCHR’s own returned binding. ComparisonResultSlot is its exact token union. CriteriaSlot retains all nondominated candidates, selectorPolicy=OfferSelection@1, and TaskSignatureSlot is absent. The same CN/CG and use arguments apply, with no predicate or evidence override. Select consumes its exact SelectEligibility pass result. | SelectionSlot={A,B}. Both offers survive because each is better on one criterion. |
The suite’s audit requirement is to recover these operation refs, effective arguments, guards and returned bindings, together with the baseline citation. Shared order and uncertainty obligations are satisfied without constructing a total score. There is no semantic, kind or plane correspondence, E.18 flow crossing, A.21 gate, implementation export or publication claim in this case; their conditional anchors are therefore inactive.
Changed condition. Move the evaluation point to 2030-01-03T00:00Z while retaining the selected method validity windows. UNM_Eligibility returns abstain. The planned method refs remain readable, but there is no new admitted NCV and no basis for continuing this selected normalization-based path to a new selected set. Reusing yesterday’s values by changing their date would fail their actual binding and use conditions. A new valid method baseline and new applications are needed.
The useful result is the justified retained set under one resolved contract chain. Acceptance or authorization to buy, an independently admitted dated Work account, and publication of the result are separate claims; none follows from {A,B} or from the plan. A PlainView may say “both offers remain; neither dominates at the stated evaluation point” and cite the baseline. It may not say “purchase approved” or erase the expiry stop.
A.19.CHR:4.8.2 - Variant — archive retention with report-only illumination
For an Archive-mode use, retain the selected set under the explicitly selected selector policy. The two-offer case can retain {A,B}; archive maintenance requires its own admitted policy and declarations. Record the exact DescriptorMap and DistanceDef editions when computing illumination, together with the policy declaring that result report-only. A separate CAL policy is required before illumination influences dominance. An archive label, descriptor display or diversity summary cannot silently change the comparison or discard either offer.