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

G.3 - CHR Authoring for a CG‑Frame: Characteristics, Scales, Levels, Coordinates

Status: Stable

Tag. Architectural pattern (CHR kit; publishes lawful measurement primitives; constrains CAL authoring and selector/dispatch use) Stage. design‑time (authoring & publication; enables admissible run-time consumption by G.4 / G.5) Primary output. CHR Pack@CG‑Frame — a notation‑independent, UTS‑published CHR bundle that provides: typed Characteristics/Scales/Levels/Coordinates, legality + guard surfaces, aggregation/comparison specs, RSCR hooks/tests, and provenance pins.

G.3:1 - Problem frame

A team defining or revising a CG‑Frame (G.1) draws on competing SoTA traditions and constructs (G.2). Its CHR publication tells downstream users which measurements and operations the frame supports:

  • CAL authoring (G.4) needs typed, admissible operands and guard/legality surfaces to build admissibility and acceptance rules (thresholds and policy cut‑offs remain governed by CAL).
  • Selector/dispatch (G.5) needs CHR‑typed quantities and explicit provenance pins so selection can remain set-returning and auditable under admissible orders.
  • Reuse beyond the defining source or use must name the exact characteristic and scale editions, bearer, scope and any temporal qualification required by the definition or receiving use, reference plane, evidence, and intended downstream use. Cite an F.9 relation only when it actually obtains between the named F.17 cells; any claim that relies on the relation for this use remains a separate bounded-use claim under C.2.1 and F.9; its evidence-bearing reliance follows A.10 and any applicable B.3 assurance requirement.

The resulting publication is a CHR Pack that is CG‑Frame‑scoped, notation‑independent, and UTS‑published, with explicit edition/policy pins sufficient for reproducibility and RSCR.

G.3:2 - Problem

Numbers alone do not tell a downstream user which measurements and operations are admissible. Common failures include:

  • Meaning leaks when the same token is reused after its referent or sense, bearer, scope, applicable validity window, evidence basis, or intended use has changed.
  • Illicit arithmetic (e.g., averaging ordinals, mixing units, laundering polarity).
  • Hidden normalizations that silently change scale type, polarity, or admissible transforms.
  • Unreproducible comparisons (missing edition pins for methods/distances/policies; unclear reference plane).
  • Unscoped reuse (the characteristic or scale lacks an exact edition, bearer, scope and any required temporal qualification, reference plane, evidence basis, or intended downstream use; any relation needed for reuse is left unstated).
  • Un-auditable aggregation (no explicit legality surface and guard surface; no proof hooks; unclear governing definition for the Γ‑fold).
  • Refresh chaos (changes in names/editions/policies do not map to typed RSCR causes).

G.3:3 - Forces

ForceTension
Pluralism vs comparabilityPreserve tradition‑specific meaning ↔ enable admissible cross‑tradition use.
Expressiveness vs legalityModel rich measurement semantics ↔ block illegal operations “by construction”.
Portability vs honestyEncourage reuse ↔ forbid implicit crossings and hidden loss.
Ease of authoring vs auditabilityKeep authoring teachable ↔ require explicit pins, provenance, and tests.
Downstream flexibility vs upstream disciplineLet CAL/selector choose policies ↔ keep thresholds/policy cut‑offs out of CHR.

G.3:4 - Solution — CHR authoring kit and publication surface

G.3:4.1 - G.Core linkage (normative)

Builds on: G.Core (Part‑G core invariants; citation/delegation hub)

GCoreLinkageManifest (normative).

GCoreLinkageManifest := ⟨
CoreConformanceProfileIds := {
GCoreConformanceProfileId.PartG.AuthoringBase,
GCoreConformanceProfileId.PartG.TriStateGuard,
GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted
},
CorePinSetIds := {
GCorePinSetId.PartG.AuthoringMinimal,
GCorePinSetId.PartG.CrossingVisibilityPins
},

// Pins strengthened for CHR authoring (delta over PinSets)
CorePinsRequired := {
// NOTE: the frame pin inherited from `GCorePinSetId.PartG.AuthoringMinimal` denotes only the exact
// declared CG-frame, which is the framing episteme here; it supplies no universal setting, scope, or reuse authority.
// Identify each measured bearer as the `entityOfConcern`. Inherit `CNSpecRef.edition` and `CGSpecRef.edition` when the kit or receiving use requires them. Each card adds its use-specific pins.
UTSRowId[],                      // required: CHR terms are public ids (Name Cards plus public-id continuity records)
PathId[]?/PathSliceId[]?,        // when G.6 paths are used or required by the receiving contract
ReferencePlane,                  // required: definitional claims are plane-scoped
Φ/Ψ/Φ_plane policy-ids?,         // when the applied loss/assurance model uses them or an applicable rule for the receiving use requires them (G.Core:4.2.3)
ΓFoldRef.edition?                // iff an explicit Γ-fold artefact is pinned (otherwise use DefaultId)
// NOTE: method-/discipline-specific pins (e.g., DescriptorMapRef/DistanceDefRef/DHCMethodRef/InsertionPolicyRef)
// are declared only inside Extensions (e.g., `G.3:Ext.QD_OEE_Wiring`) to keep core linkage universal.
},

// consumed iff any published `CHR.AggregationSpec` relies on default Γ-fold (no explicit override pinned)
DefaultsConsumed := { DefaultId.GammaFoldForR_eff },

RSCRTriggerKindIds := {
RSCRTriggerKindId.EvidenceSurfaceEdit,
RSCRTriggerKindId.TokenizationOrNameChange,
RSCRTriggerKindId.CrossingBundleEdit,
RSCRTriggerKindId.ReferencePlaneEdit,
RSCRTriggerKindId.EditionPinChange,
RSCRTriggerKindId.PolicyPinChange,
RSCRTriggerKindId.DefaultGoverningDefinitionChange,
RSCRTriggerKindId.FreshnessOrDecayEvent,
RSCRTriggerKindId.LegalitySurfaceEdit,
RSCRTriggerKindId.BaselineBindingEdit
}
⟩

Apply G.Core:4.2 for conformance profiles, pins, nil-elision and expansion. The manifest names the applicable trigger kinds (G.Core:4.3) and uses G.Core:4.4 to locate the governing definition of each default it consumes.

G.3:4.2 - Output surface: CHR Pack@CG‑Frame (normative)

CHR Pack@CG‑Frame is the CHR kit payload that downstream patterns cite and pin. Its CN/CG references identify the governing specifications.

Minimum exported objects (kit surface):

  • CHR.Characteristic[]
  • CHR.Scale[]
  • CHR.Level[] (when the scale type requires explicit level sets / order structure)
  • CHR.Coordinate[] (encodings + legality annotations; never an implicit “upgrade” of measurement structure)
  • CHR.Guards (guard macro surface; semantics governed by cited definitions; see G.Core and A.18)
  • CHR.LegalityMatrix (admissible operations per scale type / unit / polarity regimes)
  • CHR.AggregationSpecs (typed aggregators/comparators + proof hooks + edition pins where applicable)
  • UTS publication bundle: Name Cards with designations under F.17/F.18, public-id continuity notes, and (when applicable) bridge and loss notes
  • RSCR artefacts: RSCRTestId[], worked examples and their source/proof/measurement provenance, with applicable plane, path and policy pins

Mandatory provenance pins (conceptual, notation‑independent):

  • ReferencePlane
  • source/carrier references for worked examples and tests, including PathId/PathSliceId when G.6 is used or a receiving contract requires them
  • R-anchors to the supporting evidence under A.10. For evidence tagged under KD-CAL, retain its lane under C.2.2:4.6. Use G.6 paths when shared path citation or the receiving contract requires them.
  • policy pins used by crossings or plane moves (when exercised)
  • edition pins for any referenced method or metric definitions that affect interpretation

G.3:4.3 - CHR authoring chassis (S1–S8)

S1 — Charter the measurement scope (scope anchor). If the needed characteristics are not established, use A.19.ECS:4.2 to derive them from the receiving use and consequential success/failure cases. G.0:4.5.1 connects that construction to the frame’s comparison and evidence requirements. Identify the exact declared CG-frame (the framing episteme). For this CHR work, state the bearer or bearers and identify each as an entityOfConcern. Also state the scope, any applicable qualification and evaluation windows, ReferencePlane, evidence basis, intended downstream use, currentness conditions relevant to that use, and any contested expression whose reuse may require an actual F.9 relation. Output a design-time MeasurementCharter and KindMap. When the receiving use depends on currentness, apply B.3.4 to the exact claim and use. Retain any binding calibration, regulatory or qualification window; use G.3:Ext.DecayWiring when pinning a currentness or decay model or policy. If evidence-lane tags are used, declare the lane regime and its meanings here so downstream evidence discipline can remain lane-pure. B.3 and B.3.3 govern the assurance claim, receiving use and selected contributions; C.2.2:4.6 defines the KD-CAL TA/VA/LA lanes when that regime is selected. Evidence-path representation and audit remain governed by G.6; this pattern records wiring. Lane docking (wiring‑only; normative). If EvidenceLanes are used, the charter MUST:

  • enumerate the lane tags used and cite the definitions of the selected regime, plus the upstream provenance for their use when available (e.g., SoTAPaletteDescriptionId via G.3:Ext.SoTAPackInputs);
  • expose any lane‑dependent tolerances / proof requirements via explicit pins (policy‑id and/or edition‑pinned refs), not prose;
  • treat lane tags as provenance metadata (not Contexts): they MUST NOT be “bridged away” or silently mixed;
  • for a cross-lane comparison or aggregation, cite the governing policy that permits this use (typically G.4) and the grounds for the operation on these measurements. Retain G.6 paths when used or required.

If a crossing applies, use G.Core for its crossing rules and penalty routing.

S2 — Mint or reuse terms (UTS‑first). For each candidate characteristic, scale, level, or coordinate term: attempt reuse; otherwise mint via UTS Name Cards under F.17/F.18, with public-id continuity notes. When importing a term across contexts, identify its source-local meaning and the correspondence the receiving use relies on. Cite any required bridge and loss account.

S3 — Define CharacteristicCard (the per-characteristic publication unit). A CharacteristicCard is the minimum unit CHR publishes for downstream legality. It SHOULD include (field names are indicative; semantics governed by cited definitions):

CharacteristicCard := ⟨
  UTSRowId,
  CharacteristicRef.edition,
  entityOfConcern,
  ClaimScope,
  ApplicableSliceRef[],
  QualificationWindow?,
  EvaluationWindow?,
  MeasurementMethodRef.edition?,
  MeasurementModelRef.edition?,
  EvidenceRef[],
  IntendedDownstreamUse,
  ReferencePlane,
  ObjectKind,
  Intent,
  Definition (typed),
  ObservableOf := ⟨instrument or determination protocol (cite its source or carrier under A.10), uncertainty treatment when it affects interpretation or use, temporal basis when consumed by the definition or receiving use⟩,
  EvidenceLanes? (tags under the declared regime; supporting evidence refs; G.6 paths when used; cross-lane use under its cited acceptance/evidence policy),
  ScaleRef.edition,
  Polarity ∈ {↑, ↓, ⊥},
  Domain/Range,
  UnitSet,
  Bounds / zero semantics (as applicable),
  CurrentnessBasis? (for a use that depends on currentness; applicable window or decay model/policy under B.3.4),
  Missingness semantics (typed; include a classification/mapping when non‑trivial; downstream tri‑state handling is per G.Core),
  Stability/Reliability notes,
  RoleDecls? := RoleDecl[] (wiring‑only; each role declaration names its governing pattern + required pins; see `G.3:4.5`),
  QD.Role? ∈ {Q, D, QD-score} (interop alias for `RoleDecl` with `GoverningPatternId = C.18`; see `G.3:Ext.QD_OEE_Wiring`),
  Micro-examples (source/proof/measurement anchors; G.6 paths and lane tags when applicable)
⟩

Actual C.16 measurement results retain the time stance, measurement Work and interpretation basis required by C.16:5.2–5.5.

Polarity gives the preferred direction for IntendedDownstreamUse: ↑ means higher-is-better, ↓ lower-is-better, and ⊥ no preferred direction assigned. Use ⊥ for a descriptive measurement. A target, range or other preference that has no single direction uses the applicable evaluation predicate and its Method; the Scale retains its measurement meaning under A.17/A.18.

Where RoleDecl := ⟨ roleLabel, GoverningPatternId, EditionPins?, PolicyPins? ⟩ (wiring-only; the value of GoverningPatternId names the FPF pattern that governs the role declaration semantics).

Rules (CHR‑governed intent, semantics governed by cited definitions where indicated):

  • Scale/unit/polarity legality obligations cite MM‑CHR governing definitions (A.18 and C.16) and must be checkable by downstream patterns.
  • Missingness must be typed so downstream can apply tri‑state outcomes without silent coercion (tri‑state semantics are governed by G.Core).
  • When recording EvidenceLanes, use the lane tags defined by the selected regime. Cite G.6 for evidence-path audits and the governing acceptance or evidence policy (typically G.4) for any permitted cross-lane use.
  • If RoleDecls are used, each declaration MUST cite the FPF pattern that governs the declaration, for example C.18 or C.19, and surface the edition and policy pins required by that governing pattern; CHR does not define role semantics locally.
  • Role docking (normative, wiring-only): if any RoleDecl is present with GoverningPatternId = X, then G.3 MUST include (or explicitly cite) a corresponding GPatternExtension block whose governing definition is X (or whose Uses includes X) and that surfaces the required pins for that role family. Otherwise the role declaration is non-conformant (it is an undocked semantic fragment).
  • Freshness docking (normative, wiring-only): if a characteristic’s freshness/half-life is defined via a named decay model or policy, the relevant policy or reference MUST be pinned and cited through B.3.4 via G.3:Ext.DecayWiring.
  • If a characteristic is intended to be promoted into CG‑Spec, the linkage is explicit and edition‑pinned (wiring lives in an Extension; semantics governed by G.0).

S4 — Define ScaleCard and LevelCard (lawful measurement). Publish the scale type and admissible transforms, plus levels or orders when applicable. Cite the MM‑CHR definitions that justify those operations for the frame’s characteristics.

Represent the distinctions needed by the measurement. A scale type may be combined with counting, exposure or cyclic constraints:

  • Nominal / categorical: equality + counting; transforms are permutations.
  • Ordinal: order‑preserving transforms; no arithmetic that presupposes intervals.
  • Interval: positive affine transforms preserve order and ratios of differences. Differences are meaningful, and means may be lawful if justified.
  • Ratio: positive scalar transforms; ratios meaningful; products/sums subject to unit discipline.
  • Count / rates: explicit exposure/timebase requirements; rate conversions must be explicit.
  • Cyclic: wrap‑around discipline + principal interval declaration.

S5 — Define CoordinatePolicy (encodings without hidden cardinalization). When a numeric coordinate/embedding is used for convenience or tooling, CHR MUST publish:

  • what invariants are preserved (order only / ratios / topology / wrap‑around),
  • what remains illegal,
  • what proof hooks are required if a structure with higher scale-type commitment is claimed.

Use the coordinate only for operations justified by the preserved invariants. A claim to stronger measurement structure needs the proof specified by the governing MM‑CHR definitions.

S6 — Publish legality + guard surfaces (Guard Macros + LegalityMatrix). CHR publishes a CHR.LegalityMatrix and a CHR.Guards surface that downstream operators can reference.

Authors may give a guard macro a convenient name. Its definition MUST cite the governing rule for the check. The examples pair illustrative macro names with their governing sources:

  • CSLC_PROOF_REQUIRED(x) (MM‑CHR legality governing definitions: A.18/C.16)
  • UNKNOWN_TRI_STATE(x) (tri‑state semantics governed by G.Core)
  • UNIT_CHECK(x) (MM‑CHR legality governing definitions)
  • RETURN_SET_FOR_PARTIAL_ORDERS() (set‑return semantics governed by G.Core)
  • METRIC_EDITION_REF(...) (edition‑pin discipline governed by G.Core; metric semantics governed by C.18/C.21 as applicable)

S7 — Publish AggregationSpecs (typed, admissible, reproducible). CHR may publish typed aggregation/comparison specs whose admissibility follows from their declared scales, constraints and proof basis, for use by G.4 and G.5. For any published spec:

  • The legality regime is explicit (scale/unit/polarity constraints + required proof hooks).
  • If a contributor folding policy (Γ‑fold) is used and not explicitly overridden, cite DefaultId.GammaFoldForR_eff through G.Core.DefaultGoverningDefinitionIndex; do not restate the default here.
  • If method‑role declarations imply metric‑driven comparisons (e.g., QD roles), the relevant edition/policy pins are surfaced (wiring lives in an Extension; semantics governed by the referenced patterns).

S8 — Publish, test, and evolve (UTS + RSCR readiness). Publish the CHR pack and associated Name Cards to UTS. Attach:

  • RSCR tests that check legality and guard coverage and reject illegal ops,
  • worked examples with recoverable source, proof or measurement grounds; G.6 paths when used or required,
  • applicable currentness and refresh conditions, plus deprecations with lexical continuity.

The pack supplies tests, examples and refresh conditions to the RSCR loop. G.11 governs its orchestration.

G.3:4.4 - Interfaces (normative)

InterfaceConsumesProduces
G.3-1 Charter_CHRexact declared CG-frame (the framing episteme), bearer or bearers identified as EntitiesOfConcern, scope and applicable windows, ReferencePlane, evidence basis, intended downstream use, and SoTA inputs (G.2)MeasurementCharter, KindMap
G.3-2 MintOrReuse_Termscandidate characteristic, scale, level, or coordinate expressions; their effective scheme, source-local sense, and intended CHR use; UTS registryreused or minted ids and Name Cards where public ids are needed; exact F.17 cell refs and F.9 relation refs only when an actual relation between local meanings is required for the stated reuse and obtains
G.3‑3 Define_CharacteristicMeasurementCharter, candidate semanticsCHR.Characteristic[] (CharacteristicCards)
G.3‑4 Define_ScaleLevelCharacteristicCard + MM‑CHR rulesCHR.Scale[], CHR.Level[]
G.3‑5 Define_CoordinatePolicyScale/Level + use‑case constraintsCHR.Coordinate[] + legality annotations
G.3‑6 Publish_GuardsAndLegalityScale/Level/Coordinate setCHR.Guards, CHR.LegalityMatrix
G.3‑7 Publish_AggregationSpecsCHR set + legality hooks + (optional) metric refsCHR.AggregationSpecs (+ proofs/refs + pins)
G.3‑8 Publish_CHRPackall CHR artefacts + tests/examplesCHR Pack@CG‑Frame + UTS rows + RSCR tests

G.3:4.5 - Extensions (pattern‑scoped; non‑core)

All blocks below are GPatternExtension modules (PatternScopeId-scoped; not new PatternIds). They store wiring only and cite governing patterns.

GPatternExtension: SuiteBoundaryLinkage

  • PatternScopeId: G.3:Ext.SuiteBoundaryLinkage

  • GPatternExtensionId: SuiteBoundaryLinkage

  • GPatternExtensionKind: InteropSpecific

  • GoverningPatternId: A.19.CHR

  • Uses: {A.19.CHR, A.15.2, A.15.3}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • CHRMechanismSuiteDescriptionRef.edition? (when the suite description is cited as a reproducibility baseline)
    • WorkPlanRef and local baseline locator (when a planned baseline binds CHR artefacts into WorkPlanning under A.15.2)
    • CHRMechanismSuiteSlotFillingsPlanItem in that WorkPlan (when the plan fills an independently declared operation argument or relation position under A.15.3; cite the governing declaration and member designator, and locate the filling row within the plan)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.BaselineBindingEdit, RSCRTriggerKindId.EditionPinChange}

  • Notes (wiring-only): A.19.CHR governs suite semantics and membership; A.19.CHR:4.1.2 distinguishes ordinary planned baselines from typed filling.

GPatternExtension: SoTAPackInputs

  • PatternScopeId: G.3:Ext.SoTAPackInputs

  • GPatternExtensionId: SoTAPackInputs

  • GPatternExtensionKind: DisciplineSpecific

  • GoverningPatternId: G.2

  • Uses: {G.2}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • ClaimSheetId[] / operator & object inventory refs (as cited inputs)
    • SoTAPaletteDescriptionId? (when palette/traces are cited; used to dock contested‑term inventory and (if present) lane tags/tolerances)
    • BridgeMatrixId? (when terms/constructs are imported across traditions)
    • UTSRowId[] drafts/aliases from synthesis
  • RSCRTriggerKindIds: {RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.TokenizationOrNameChange, RSCRTriggerKindId.CrossingBundleEdit}

  • Notes (wiring‑only): SoTA pluralism inputs are governed by G.2; this module only specifies which synthesis artefacts are cited while authoring CHR. When CHR authoring relies on pack coverage, cite the same CoverageJudgementRef and HarvestPolicy basis, retaining the counted population and receiving question. CHR terms or cards do not redefine the counted family unit; lineage plurality remains a separate result.

GPatternExtension: CGSpecPromotionWiring

  • PatternScopeId: G.3:Ext.CGSpecPromotionWiring

  • GPatternExtensionId: CGSpecPromotionWiring

  • GPatternExtensionKind: InteropSpecific

  • GoverningPatternId: G.0

  • Uses: {G.0}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • CGSpecRef.edition (when a characteristic is promoted/linked into CG‑Spec)
    • CHR.Characteristic.id pointers included in CG‑Spec.Characteristics := [...] (no shadow ids; CG‑Spec stores pointers, see G.0)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.LegalitySurfaceEdit, RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange}

  • Notes (wiring‑only): G.0 governs promotion semantics and the legality gate; CHR only pins and cites.

GPatternExtension: MMCHRLegalityWiring

  • PatternScopeId: G.3:Ext.MMCHRLegalityWiring

  • GPatternExtensionId: MMCHRLegalityWiring

  • GPatternExtensionKind: DisciplineSpecific

  • GoverningPatternId: A.18

  • Uses: {A.17, A.18, C.16}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • CSLC legality proof anchors/carriers (ids/refs as defined by MM‑CHR governing definitions; cite A.18/C.16)
    • Unit coherence references (where units exist)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.LegalitySurfaceEdit, RSCRTriggerKindId.ReferencePlaneEdit}

  • Notes (wiring‑only): This module wires CHR artefacts to MM‑CHR legality proof obligations; legality semantics are governed by the referenced patterns.

GPatternExtension: DecayWiring

  • PatternScopeId: G.3:Ext.DecayWiring

  • GPatternExtensionId: DecayWiring

  • GPatternExtensionKind: DisciplineSpecific

  • GoverningPatternId: B.3.4 (freshness/decay semantics)

  • Uses: {B.3.4, G.6}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • the currentness claim and receiving use, with any applicable FreshnessWindowDeclRef or equivalent window pin
    • DecayPolicyIdRef? (policy-bound; if decay model is referenced by id)
    • references to affected sources, carriers and any worked examples used to show drift. Include PathSliceId[] when G.6 paths are used or required.
  • RSCRTriggerKindIds: {RSCRTriggerKindId.FreshnessOrDecayEvent, RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.BaselineBindingEdit}

  • Notes (wiring-only): Cite the B.3.4 currentness basis and any window/model actually used. A change in relied-on conditions or support can trigger refresh without assigning an expiry time or half-life.

GPatternExtension: QD_OEE_Wiring

  • PatternScopeId: G.3:Ext.QD_OEE_Wiring

  • GPatternExtensionId: QD_OEE_Wiring

  • GPatternExtensionKind: MethodSpecific

  • GoverningPatternId: C.18

  • Uses: {C.18, C.19}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • DescriptorMapRef.edition (if any Characteristic declares descriptor roles)
    • DistanceDefRef.edition (if any Characteristic declares distance roles)
    • DHCMethodRef.edition? (when a C.21 discipline-health measurement definition is actually used; a Q / QD-score role alone does not select it)
    • InsertionPolicyRef? (when archive insertion semantics are declared for reproducibility)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}

  • Notes (wiring‑only): QD/OEE semantics are governed by C.18 and C.19. CHR only surfaces method‑role declarations (via RoleDecls or the interop alias QD.Role) and the edition/policy pins required for reproducible archive/front interpretation.

G.3:5 - Archetypal Grounding

AG‑1 — ML fairness auditing. System: deployed classifiers evaluated across cohorts in a CG‑Frame that makes abstention or deferral explicit. CHR authoring: publish DemographicParityGap and EqualizedOddsGap as Characteristics with:

  • explicit ReferencePlane, with deployment population and sampling regime recorded separately as scope and protocol conditions,
  • ObservableOf (audit protocol + uncertainty model + window),
  • interval scale (bounded; zero semantics explicit),
  • missingness semantics (cohort sparsity and label noise are typed),
  • legality surfaces and guard surfaces that forbid illicit cohort mixing and require explicit proof hooks for aggregation across cohorts.

Downstream: CAL acceptance binds thresholds and failure behavior; selector remains set‑returning under partial orders and may treat “defer/abstain” as a first‑class outcome (tri‑state semantics pinned through G.Core).

AG‑2 — Clinical diagnostics. System: diagnostic pipelines compared in a CG‑Frame as datasets and protocols evolve. CHR authoring: publish Sensitivity and Specificity as ratio‑scale, dimensionless Characteristics on [0,1], with:

  • explicit ObservableOf (trial protocol, inclusion criteria, uncertainty model),
  • freshness/decay expectations for the stated use,
  • legality surfaces that forbid averaging incompatible ordinal labels (e.g., severity grades) and require explicit unit/exposure constraints for any derived rate.

Downstream: CAL acceptance governs thresholds and guard-bands; source/proof/measurement references, including G.6 paths when used, identify the basis to reconsider after a relevant change.

AG‑3 — Quality‑Diversity / Illumination (MAP-Elites/CMA-ME lineage). System: a quality-diversity search system supplies an archive or front. In the CG-Frame, that set is the source for a declared set-result outcome under G.5. CHR authoring: declare which Characteristics play Q/D/QD‑score roles and pin the metric definitions (descriptor map, distance definition, method editions) so archives are reproducible across runs and refresh can be triggered on edition changes. CHR does not scalarize partial orders; set‑return semantics are pinned through G.Core.

G.3:6 - Bias‑Annotation

CHR authoring is where many biases become “baked in” as measurement choices. Typical risks:

  • Proxy bias: a convenient observable substitutes for the intended construct. Mitigation: require ObservableOf + ReferencePlane + micro‑examples; force explicit “what is being measured” rather than relying on labels.
  • Population and protocol shift: a change in sampling or protocol can alter the interpretation or applicability of a reported value, or the characteristic’s meaning when that procedure is part of its definition. Retain the population, protocol edition and use conditions, including any applicable validity or freshness window. Reconsider dependent claims when those conditions change. Use the corresponding RSCR trigger for a freshness/decay event or a change to the supporting evidence.
  • Ordinal misuse bias: ordinal ratings treated as interval/ratio by convenience. Mitigation: publish scale type + admissible transforms; legality matrix + guard macros; reject coordinate upgrades without proof hooks.
  • Cross-tradition meaning bias: an imported expression erases its source-local meaning or makes a changed bearer, scope, window, reference plane, evidence basis, or intended use disappear. Mitigation: name those values, cite exact F.17 cells and an F.9 relation only when it obtains, and keep any downstream bounded-use claim explicit under C.2.1 and F.9, with evidence-bearing reliance governed by A.10 and any applicable B.3 assurance requirement. Retain any mapping limitation and any justified penalty under the applicable G.Core rule.
  • Metric gaming bias (QD and evaluation): changing descriptors/distances changes what “diverse” means. Mitigation: edition‑pin metric definitions and make role declarations explicit (wiring via C.18 and C.19).

G.3:7 - Conformance Checklist (normative)

ConformanceIdStatement
CC‑G3‑CoreRefG.3 is conformant only if the applicable G.Core obligations declared in G.3:4.1 are satisfied (effective expansion of profiles/sets + deltas; explicit pins; typed RSCR triggers; defaults with one governing definition).
CC‑G3‑01CHR Pack@CG‑Frame is published as a notation‑independent kit payload with the minimum exported objects listed in G.3:4.2.
CC-G3-02Every CHR.Characteristic names its exact characteristic and scale editions, its bearer as the entityOfConcern, claim scope and applicable slices, any applicable qualification and evaluation windows, ReferencePlane, method or model edition when it affects interpretation, evidence refs, intended downstream use, and a filled ObservableOf field (instrument or determination protocol, uncertainty treatment when it affects interpretation or use, and any temporal basis consumed by the definition or receiving use).
CC‑G3‑03Every CHR.Characteristic declares its ScaleRef, Polarity, and UnitSet (or an explicit “unitless” declaration), plus bounds/zero semantics where applicable.
CC‑G3‑04Missingness is typed in the CHR artefacts such that downstream tri‑state handling is possible without silent coercion. (Tri‑state semantics are governed by G.Core; the typing obligation is CHR‑local.)
CC‑G3‑05CHR.Scale / CHR.Level artefacts encode the scale type and admissible transforms, and make illicit arithmetic checkable by downstream consumers.
CC‑G3‑06Any published CHR.Coordinate includes a CoordinatePolicy that states preserved invariants and explicit non‑entitlements; coordinates do not silently upgrade measurement structure.
CC‑G3‑07CHR.LegalityMatrix and CHR.Guards exist and are referenced by downstream operator authoring; semantics are governed by cited definitions (MM‑CHR and G.Core), not duplicated locally.
CC‑G3‑08CHR.AggregationSpecs are typed and legality‑constrained; where Γ‑fold is required and no explicit override is pinned, cite DefaultId.GammaFoldForR_eff through G.Core.DefaultGoverningDefinitionIndex.
CC‑G3‑09If any characteristic is intended for promotion into CG‑Spec, the linkage is explicit and edition‑pinned (no shadow ids). (Governing definition: G.0; wiring via G.3:Ext.CGSpecPromotionWiring.)
CC‑G3‑10UTS Name Cards exist for public ids minted or evolved by the CHR pack (designations under F.17/F.18 plus public-id continuity notes). (Delegation target: CC‑GCORE‑UTS‑1 via CC‑G3‑CoreRef.)
CC‑G3‑11Worked examples and RSCR tests retain their source, proof or measurement basis, with G.6 path citations when used or required. They cover illegal-operation refusal, unit and scale constraints, polarity invariants and coordinate non-entitlements.
CC‑G3‑12Thresholds/guard‑bands are not embedded in CHR artefacts; they remain governed by CAL acceptance clauses (G.4).
CC‑G3‑13When method‑role declarations are present (via RoleDecls and/or QD.Role alias), each declaration is docked to its governing pattern via a corresponding G.3:Ext.* module, and the edition and policy pins required by the governing pattern are surfaced to make downstream interpretation reproducible. (QD/OEE governing patterns: C.18 and C.19; wiring via G.3:Ext.QD_OEE_Wiring.)
CC‑G3‑14Evidence wired. Each CHR.Characteristic cites the grounds of its legality and guard claims through A.10 source/carrier references, or G.6 paths when shared path citation or a receiving contract requires them. The chosen representation preserves the actual claim and support relations.
CC‑G3‑15An Archetypal Grounding section exists with at least two domain‑distinct examples that demonstrate lawful CHR typing/legality and the CHR↔CAL separation (notably: no thresholds in CHR).
CC‑G3‑16If EvidenceLanes are used, declare their tags with the selected regime’s definitions and pin any lane-dependent tolerances/proof requirements. Cross-lane comparison or aggregation requires both a governing policy that permits the use (typically G.4) and grounds for the operation on these measurements. Cite both, with G.6 paths when used or required.
CC‑G3‑17When CHR outputs are bound into a planned baseline, identify the A.15.2 WorkPlan and its local baseline locator. If the plan fills an independently declared operation argument or relation position under A.15.3, also use CHRMechanismSuiteSlotFillingsPlanItem with its governing declaration reference, member designator and plan-local filling-row locator, as governed by A.19.CHR:4.1.2 (wiring via G.3:Ext.SuiteBoundaryLinkage).
CC‑G3‑18Use-qualified currentness. A claim whose receiving use depends on currentness retains its B.3.4 basis and any applicable validity window or decay policy. Named models/policies are pinned through G.3:Ext.DecayWiring. Changes to relied-on windows, policies or other support conditions participate in RSCR under G.3:4.1.

G.3:8 - Common Anti‑Patterns and How to Avoid Them

  • Hidden cardinalization. Don’t treat ordinal encodings as interval/ratio; do publish coordinate policies that explicitly preserve order‑only invariants and forbid arithmetic upgrades.
  • Unit laundering. Don’t add or average quantities with incompatible units; do force explicit unit discipline and legality checks via MM‑CHR governing definitions.
  • Polarity drift. Don’t rely on “higher is better” implicitly; do publish polarity explicitly and make downstream use auditable.
  • Threshold leakage into CHR. Don’t embed policy cut‑offs in CHR; do keep thresholds in CAL acceptance artefacts.
  • Unpinned semantics. Don’t cite “the metric” or “the distance” without edition pins; do require edition‑pinned references when semantics affect interpretation.
  • Unscoped reuse. Don’t reuse a characteristic or scale beyond its defining source and use on token continuity alone. Name the exact editions, bearer, scope and applicable window, reference plane, evidence, and intended downstream use; cite F.9 only when an actual relation between the named local senses is needed and obtains.

G.3:9 - Consequences

  • Legality becomes checkable. Downstream patterns can reject illegal operations and rely on explicit legality surfaces rather than implicit conventions.
  • Comparability without semantic flattening. Plural traditions remain representable because CHR preserves local meaning while making lawful relations explicit.
  • Reproducible downstream behavior. Edition/policy pins make “why did this change?” answerable and RSCR actionable.
  • Authoring overhead. The pattern shifts effort to up‑front authoring: explicit cards, pins, and tests are non‑optional when CHR becomes a public kit surface.

G.3:10 - Rationale

CHR authoring states which measurements and operations downstream reasoning may use. By making scale/unit/polarity explicit, publishing legality and guard surfaces, and requiring provenance pins, CHR authoring prevents downstream mechanisms from silently inventing their own legality assumptions.

Using shared rules from G.Core keeps tri-state guards, penalty routing, set-return semantics and RSCR trigger kinds consistent across Part G. Its default index points to the pattern that defines each default. CHR defines the frame’s measurement kit.

G.3:11 - SoTA‑Echoing

The pattern connects these evaluation practices to measurement authoring:

  • treating abstention/defer and set‑valued outcomes as first‑class design objects (as in selective prediction and set-valued reporting),
  • keeping multiobjective and archive‑based reasoning set‑returning rather than silently scalarizing (as in QD/illumination and open-ended evaluation),
  • making evaluation semantics reproducible through explicit edition/policy pinning so users can recover how a reported metric was evaluated,
  • modularizing method‑family specifics (QD/OEE, explore‑exploit) via explicit wiring and governing-definition assignment rather than embedding method semantics into universal measurement admissibility.

G.3:12 - Relations

Builds on: G.Core, G.1, G.2, G.6 when EvidenceGraph/Path citation is used or required, A.19.CHR, A.15.2 (WorkPlan baselines), A.15.3 (planned fillings of independently declared positions), A.17–A.18/C.16 (MM-CHR), F.0.1 (source-local meaning), F.1 (source selection), F.9 (actual relations between local-sense cells), F.17 (scheme-sense cells), F.18 (naming settlement), C.2.1 (bounded-use claims), B.3 / B.3.4, A.10, E.10, E.5.1–E.5.3. Uses (via Extensions): G.0 (promotion/linkage to CG‑Spec), optional C.18 and C.19 (QD/OEE wiring). Publishes to: G.4 (typed measurements, their permissible operations, any published aggregation or comparison specs, guard macros and applicable freshness pins), G.5 (role declarations and pins for reproducibility), UTS (Name Cards and public-id continuity notes), RSCR tests and hooks. Constrains: any CAL/LOG/selector usage that consumes CHR (must treat CHR artefacts as typed/legal surfaces, not as prose hints).

G.3:End

Referenced in the corpus

30 literal mentions in other sections. Read their context to establish the relation.