A.19.UINDM:7 - Conformance Checklist
A UINDM publication or use is conformant if it satisfies:
-
A.6.1 declaration completeness. Indicatorize and the separately reused IndicatorizeEligibility have local argument/result declarations, obtaining predicates and application identity/extent rules. Their declared selection and guard laws hold; SlotIndex projects those declarations. A binding requires the value used or returned by the identified application, not a compatible audit record.
-
SlotKind discipline. SlotKind tokens match the CHR SlotKind lexicon for the roles used (
CharacteristicSpaceSlot,CNSpecSlot,IndicatorChoicePolicySlot, etc.); no genericContextSlotis introduced. New SlotKinds, if any, first extend the suite lexicon rather than appearing ad hoc in the mechanism. -
Selection-only behavior.
Indicatorizereturns positions in the declared basis, retaining their Characteristic, Scale and meaning. A projected state keeps their original relative order. There is no implicit normalization or enlargement. After a basis change, resolve the policy again rather than reuse naked indices. -
No NCV shortcut. “Measurable/NCV” is not treated as sufficient for indicatorhood; indicatorhood arises only via
IndicatorChoicePolicySlotconsistent withCN‑Spec.indicator_policy. -
Evidence gating is explicit. When the chosen
IndicatorChoicePolicyis evidence‑gated,CGSpecSlotis present and the effective MinimalEvidence is explicit and auditable (MinimalEvidenceSlotwhen provided; otherwiseCGSpecSlot.MinimalEvidence); insufficient/unknown evidence must yielddegrade/abstainper the effective failure‑behavior policy, never a silentpass. -
Recheck eligibility for reuse. Another bearer, scope and window, basis, plane, or intended use gets a fresh eligibility decision; any F.9 Bridge, kind relation, or plane relation is cited only when the conclusion relies on that obtaining relation, with loss assessed under the receiving-use rule and any numerical assurance penalty applied under A.6.7:4.2(2).
-
Gate/guard separation + lexeme discipline. UINDM uses
…EligibilityreturningGuardDecision ∈ {pass|degrade|abstain}and does not embed GateDecision/GateLog in suite steps. Reserved gate‑lexemes (e.g.,…Guard) are not used for indicatorization eligibility predicates. -
Planning and actual use. On a P2W path, an A.15.2 WorkPlan selects the intended editions; A.15.3 governs typed filling only for independently declared positions. Record the application and its effective bindings under §4.1, keeping the refs and pins needed for replay in Audit.
-
Extension discipline (if extended). A proposed UINDM specialization MUST preserve the inherited SlotKind designators and their meanings, add no mandatory input to Indicatorize, and declare any additional output or operation (the local extension notation is ⊑⁺). A refinement, conservative-extension or equivalence claim additionally uses its own A.6.1 §4.8 preservation test and comparison predicate; those three claims are not interchangeable. Preserve inherited application/binding meanings, identity and extent to the degree required by the claimed comparison, and retain narrowed applicability or stronger conditions explicitly. A missing comparison predicate or substrate returns the applicable A.6.RCD gap.
For example, an extended Indicatorize may add an optional justification result while retaining the original inputs and selected-position result. To claim a conservative extension, establish that every inherited admitted use, result and application/binding rule remains as specified; the new output has its own declaration. Making a new explanation input mandatory fails the local restriction. A label such as ⊑⁺ does not settle the comparison: use the admitted comparison relation or A.6.RCD’s case-specific claim branch under A.6.1 §4.8, returning its missing-governor/substrate gap if necessary.