C.22:2 - Problem Frame

Selector-facing problem case For selector-facing C.22 use, a problem case applies when the problem-side episteme is stable enough to construct a minimal TaskSignature and assert its TaskSignatureAssignmentRelation for eligibility, acceptance, or policy-governed selection. Method absence or contestability is a common downstream reason, but not the ontology of problemhood. When the live question remains a symptom, contested framing, stale ReferenceScheme or ClaimScope, set-derived candidate, opportunity cue, or preselected work item, use C.22.2 before asserting one assignment. When selection becomes current, cite the A.19.SelectorMechanism relation and exact G.5 policy refs rather than moving selection policy into the signature. Unknown-first discipline. Author S2 with unknown traits rather than coercions. Name the exact downstream policy that interprets a live unknown for the receiving use. C.22 introduces no universal outcome enum; C.23, G.4, G.5, or another direct pattern defines or constrains the resulting eligibility, acceptance, or selection disposition.

Untyped “problems” collapse into informal prose; selectors cannot filter or abstain admissibly; acceptance-gate thresholds leak into scoring; and cross-scheme reuse proceeds by name rather than by an exact relation. The ordinary needed value is a use-bounded TaskSignature that (i) establishes MM-CHR admissibility for Scale, Unit, and Polarity before aggregation, (ii) carries tri-state unknowns explicitly, and (iii) states the exact scheme, scope, and only the basis and currentness relations needed by the current use. Open A.10 only when the use relies on a bounded evidence or provenance question. Open B.3 only when a named assurance claim about an exact target claim is current for this receiving use, including when a material-reliance rule requires that assurance claim; its assurance result is not a TaskSignature field.