C.22.PFR:1 - Problem frame

Use this when. Use this pattern when an actual condition may be adverse for one exact entity and use, and a receiving claim needs to distinguish the actual Problem from a signal, criterion description, evaluation, assessment claim, ProblemCard, or claim that no suitable method is currently known.

First useful move. Name the actual-condition relation. Then name the exact predicate, entity, scope, and interval for which that predicate applies. If the condition falls on the adverse side of that applicable predicate, say plainly: “This condition is a problem for this entity in this scope.” Expose a PFR occurrence only when another claim needs that Problem identity.

What goes wrong if missed. A card or evaluation result is allowed to create a Problem; the same criterion is applied to the wrong entity or scope; a new description edition creates a false new Problem; or one continuously adverse episode is split every time evidence is sampled. Conversely, two adverse episodes separated by actual non-adverse behavior collapse into one occurrence.

What this buys. Actual Problems can exist before discovery, can be referenced while still ongoing, and can be distinguished across repeated adverse episodes. One exact applicability relation supplies the predicate, problem-for entity, claim scope, and declared criterion-applicability window used by PFR; its actual occurrence extent is separately derived from uninterrupted obtaining. Measurements, evaluations, evidence, claims, cards, and method search remain available without becoming Problem identity.

Early battery stop. A low terminal-voltage reading can be a useful signal and can justify a ProblemCard, but it is not itself the actual-condition participant. Until a direct voltage-state pattern supplies the exact relation kind, participant meanings, obtaining rule, temporal extent, recurrence, and occurrence identity, the battery case remains explicitly non-conforming: the reading, alarm, report, assertion, and card establish none of that world-side relation. Once such a governor exists, the applicability relation can connect its selected voltage predicate to the exact vehicle, intended-start U.ClaimScope, and declared criterion-applicability window; discovering a method still changes solvability rather than PFR actuality.

Not this pattern when. Use C.22.2 when the current object is a problem-side card, signal, hypothesis, forecast, scenario, anticipated-condition claim, or reviewable formulation rather than an actual PFR. Use C.27 when a rate, rhythm, recovery, or regime claim is being used to change action, C.28 when causal support is at issue, or the exact direct forecast, scenario, counterfactual, or anticipated-condition governor when that claim is current. Use the selected A.19 comparison, G.4 acceptance, state, gate, or measurement pattern when the current question is how to evaluate or support the adverse predicate. Use E.18.1, E.23, and the direct NQD or OEE patterns for repeated problematization, search, work, evaluation, and continuation.