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

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 reason for this downstream use; it does not define what counts as a problem.

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. In the TaskSignature, preserve a live unrecovered trait as unknown when its value rule permits it. Name the exact downstream policy that interprets a live unknown for the receiving use. C.22 introduces no universal outcome set; C.23, G.4, G.5, or another direct pattern defines or constrains the resulting eligibility, acceptance, or selection disposition.

When the receiving selector cannot recover the relevant task distinctions, it cannot filter or abstain on a justified basis. Acceptance criteria may leak into scoring, or cross-semantic reuse may proceed by a shared name instead of an obtaining relation.

The receiving use needs a use-bounded TaskSignature that:

  • establishes MM-CHR admissibility for Scale and applicable Unit and polarity before aggregation;
  • carries tri-state unknowns explicitly; and
  • states the exact scheme, scope, and only the basis and currentness relations needed by the current use.

Keep the direct support required for the claim; open A.10 when its evidence, provenance or bounded reliance needs a replayable account.

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.