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

C.22:1 - Intent

Make the task distinctions relevant to a selector decision explicit in a typed TaskSignature. A problem reaches C.22 when its problem-side episteme is stable enough to constitute and assign that declaration without selecting a method in advance. The signature is the smallest CHR-typed A.6.0 declaration sufficient for eligibility, acceptance, and policy-governed selection without inadmissible arithmetic or silent coercions.

C.22:1.1 - Term split used in this pattern

  • TaskSignature assignment means one obtaining TaskSignatureAssignmentRelation among an exact problem-side episteme, exact TaskSignature, and exact receiving-use episteme; it does not pre-bind a method.
  • ScopeSlice(G) means the exact A.2.6 U.ClaimScope value used by this declaration; it is not an evidence-path slice, baseline-set slice, container, or assignment participant.
  • threshold has three distinct uses here:
    • articulation and closure thresholds stay with cue or prompt subject patterns such as B.4.1 and B.5.2.0;
    • acceptance-gate thresholds stay with G.4;
    • a work-measure threshold target used in a specialization claim is only the declared success mark for that task family or work target.

Name and kind map for code-shaped heads. The names below identify different structural positions; capitalization does not make them peer kinds.

Head used in this patternRecoverable kind or positionDirect governance boundary
TaskSignatureC.2.1 episteme and species of U.Signature; this pattern’s primary EntityOfConcernC.22 governs its A.6.0 direct fields, Vocabulary, Laws, and Applicability; C.2.1 governs constitution; E.17 supplies reader-facing publication forms, and E.24.PUB governs publication and carrier relations.
ProblemSideEpistemeRef and ReceivingUseEpistemeRefParticipant designations in an assertion or description of TaskSignatureAssignmentRelation, not content or identity positions of TaskSignatureC.22.2 or the direct problem-side pattern defines or constrains the first episteme; the receiving-use episteme states the use but does not prove that an assignment obtains.
TaskKindTaskSignature position filled by one exact C.3 U.Kind value that types the current task or work targetC.3 governs the kind value; the field does not introduce U.Task.
TaskFamilyRefOptional reference position for the comparison-relevant task familyC.22 and C.22.1 govern task-family anchoring; the reference is not the family or a selected method.
ProblemProfileC.2.1-conformant U.Episteme that describes the stabilized problem and may reference the TaskSignature assignmentTaskSignature membership requires its A.6.0 declaration content; the assignment is a separate obtaining relation. One episteme may serve both descriptive uses only when their content and C.2.1 constitution conditions hold.
ScopeSlice(G)Local position whose filler is the exact A.2.6 U.ClaimScope value that bounds claims about the exact EntityOfConcernRefA.2.6 governs membership; the position is not an E.18 path slice or a new slice kind.
CHR field heads in 5.1TaskSignature positions filled by characteristics, scales, units, polarity values, scope values, evidence relations, and currentness conditionsC.16 and each subject-pattern locator identify the exact definitions and constraints for the fillers; C.22 states why the selector-facing use needs them.
QD and OEE extension heads in 5.1Optional TaskSignature positions filled by exact characteristic-space, archive, policy, telemetry, generator-family, validity-region, and transfer-rule values or referencesC.18, C.19, G.5, G.11, and the named direct patterns keep authority over those fillers. ArchiveConfig, TelemetryHooks, and GeneratorIntent do not become root kinds here.

C.22:1.2 - ProblemCard relation

ProblemCard is the C.22.2 C.2.1 episteme used to stabilize one problem-side representation before downstream Principles-to-Work.

A ProblemCard can prepare TaskKind, scope, and characteristic bindings for a candidate TaskSignature. Identify which adequate signature was adopted for this problem-side episteme and receiving use under §5.2. Other adequate descriptions may be available. If adequacy or adoption is unresolved, retain the candidate signatures and identify what would settle it.

Assigning a TaskSignature does not transfer the card’s claims into it. The signature keeps only its A.6.0 declaration content; the card remains the reviewable problem-side episteme that explains why this problem can proceed to characterization, comparison, search, refresh, retirement, or another subject pattern.

The corresponding claims remain with their named subject patterns.