C.22:9 - Conformance Checklist (normative)
-
Minimal A.6.0 declaration.
TaskSignatureexposes exactEntityOfConcernRef, effective reference scheme,SubjectKind,RangedValueKind, optionalResultKind,SliceSet, andExtentRule, plus Vocabulary, Laws, and Applicability. AddSignatureManifestonly when dependency replay needs imports and provided names; it does not supply signature identity. -
Signature and assignment present. Every exported selector-facing case names one TaskSignature identity and edition plus one
TaskSignatureAssignmentRelationwhose exact problem-side episteme, TaskSignature, receiving-use episteme, obtaining conditions, and occurrence extent are recoverable. No setting, carrier, or organization is added as a fourth participant. Current characteristic bindings are CHR-typed; a live unknown preservesunknown, while a non-current optional vocabulary item remains absent.1a. Publication and designators do not define identity. Two E.17 publications or serialized records that resolve to the same
<declaration content, EntityOfConcernRef, effectiveReferenceScheme>identify the same TaskSignature episteme. Carrier, layout, serialization,SignatureId, or edition label alone does not create a new identity component. -
CHR admissibility proven. Any numeric comparison or aggregation cites CG-Spec by Characteristic id and proves CSLC admissibility; no mean on ordinals; no unit mixing.
-
Unknowns remain typed. A live unknown remains
unknown, cites the direct downstream policy, and is not coerced. The acceptance, eligibility, or selector pattern records its own governed result. -
Evidence and assurance are conditional. For relied-on evidence or provenance, retain the supporting claim and its direct relation, with only the source edition, currentness and freshness conditions the use needs. Apply A.2.4 to an episteme’s evidence-use or status-use question and A.10 when replay of evidence, provenance or bounded reliance needs its account. When a named assurance claim about an exact target claim is current for this receiving use, including when a material-reliance rule requires it, cite its separate B.3 result, applicable assurance lanes, and declared fold. Otherwise the TaskSignature needs neither an evidence dossier nor an assurance fold.
-
Cross-semantic use is separated. Declare
ReferencePlanefor a value or objective head when its interpretation or comparison needs it. A scheme or plane difference alone creates neither a Bridge nor a penalty. Resolve two exact F.17 local senses, test the F.9 predicate, and state any proposed use separately. -
Acceptance thresholds live in CAL. G.4 AcceptanceClauses govern acceptance-gate thresholds. Signatures and implementations reference those clauses instead of redefining them as CHR properties or hidden constants.
-
Selector-use support. The TaskSignature exposes the scales, units, polarities, and admitted order relations needed by
G.5; it carries no mixed-scale scalarization or local selector verdict.G.5governs the emitted outcome and its source under G.5:4.4b–4.4e, including retained alternatives drawn from a non-dominated front. -
Bridge and use claims remain distinct. For current cross-semantic reuse, cite the two exact local senses and an F.9 Bridge only when its predicate is true. State the action, direction, correspondence rule, tolerated loss, and polarity in a separate bounded-use claim; if the predicate is false, keep the local values separate.
-
Packaging is conditional. Create an F.9 card, terminology row, Name Card, or reusable package only when a named receiving pattern independently needs that artifact. Packaging describes an already tested relation and separate use claim; it establishes neither.
-
Structure and gates are conditional. Apply E.18 crossing checks only when a selected transformation-flow structure and exact
GateCrossingare current. Apply A.21 only when a named gate decision is current. Each pattern supplies its own result; neither a structure nor a gate makes F.9 obtain, and C.22 requires no crossing or gate package otherwise. -
QD fields (when QD is in scope). A TaskSignature for an active QD search is complete only when it carries CHR-typed CharacteristicSpaceRef with the dimension required by its declared descriptor and comparison rules, the separate characteristicSpaceDescriptionRef to its exact defining episteme, ArchiveConfig (topology, resolution, K,
InsertionPolicyRef,DistanceDefRef.edition) and EmitterPolicyRef; each characteristic declares its ReferencePlane when interpretation or the receiving contract requires it.PortfolioMode=Archiveor a set-valued selector outcome alone activates none of these fields. -
DominanceRegime default.
DominanceRegimedefaults toParetoOnly. Illumination enters dominance only through a cited CAL.Acceptance policy enabling that relation; the SCR records the policy id. -
Telemetry (when used). The active telemetry record carries PathSliceId when an E.18 path slice is current, the applicable decay and refresh policy ids, and the exact space-description episteme and the editions of the distance and emitter definitions on which that telemetry depends. An illumination increase is traceable to its governing policy id. Ordinary evidence retention does not require an illumination record.
-
GeneratorIntent (when OEE is in scope). A TaskSignature supports the claimed OEE generator-family use only when
GeneratorIntentcitesEnvironmentValidityRegionandTransferRulesRefwith ids resolvable in G.5 and C.23. Any downstream abstention is their result, not a C.22 output. -
Budgets. When
Budgetingis live, its evaluation, time, and batch values carry declared units and the applicable E/E-LOG exploration-budget id. -
Archive-comparison support. The TaskSignature supplies the measurement and comparison basis required by the claimed comparison. When that comparison uses distance or novelty, its distance definition and novelty measures must be CSLC-admissible and editioned, including
DistanceDefRef.editionwhen used. Retaining the alternatives in an archive does not by itself require distance. The archive or selector pattern defines or constrains any downstream abstention or returned-set result. -
Planes. QD heads and characteristics declare a
ReferencePlanewhen their meaning or comparison depends on it. A plane difference alone creates neither correspondence nor an assurance adjustment. Use item 8 for a current cross-semantic claim and item 4 for any separately current B.3 assurance result. -
Unknown QD values. A live unknown QD field remains
unknown, cites the policy governing its downstream use, and is not coerced or mapped by C.22 itself. -
Specialization claims referenced. Name the holder or scoped portfolio, task family, work target, performance criterion and supporting basis. For an acquisition claim, support the relevant change; for a C.22.1 adaptation comparison, retain its budget, prior-exposure and threshold-crossing conditions. Keep the TaskSignature edition and assignment, freshness and provenance required by the receiving use.