C.22.2:20.1a - Compact P2W-ready Disposition Slice
A support team sees repeated failed hand-offs after a new interface policy. The incoming request says “rewrite the escalation workflow.” A conforming ProblemCard first repairs the problem-side record instead of accepting the work-shaped request.
| Card field | Filled value |
|---|---|
| Source signal | Escalations reopen after hand-off from first-line support to specialist support. |
| Problem-side EntityOfConcern | The hand-off ambiguity at the support interface, not the whole escalation process. |
| Effective ReferenceScheme and ClaimScope | Scheme: support-interface hand-off under the new policy edition. ClaimScope: SupportOps-EU. |
| Claim family | Anticipated-condition claim: while the ambiguity remains under the current policy wording, reopened escalations are expected to continue. The card asserts no actual-PFR occurrence, causal-use result, or solvability result. |
| Not-wish, not-ticket, and not-preselected-Work reason | The incoming request to “rewrite the escalation workflow” is a proposed Work request. It neither identifies the joint concern nor shows that a rewrite is the needed Method or Work. |
| Improvement check or acceptance probe | Sample reopened cases; accepted improvement means fewer reopened hand-offs within that ClaimScope and window without increasing unresolved safety, compliance, or customer-impact exceptions. |
| Honest next use | Use E.18.1 to carry only the hand-off-ambiguity claim and acceptance probe into one next relation question. Do not select a method, approve a rewrite, pass a gate, or authorize Work. |
| Qualification window (current here) | Two-week incident window under the stated policy edition. |
| Problem-formulation follow-up reason (current here) | Separate interface wording, System, assignment, Method, and Work alignment, evidence, currentness, and possible policy-boundary relations before any Method or WorkPlan choice. |
| Validation boundary (current here) | Same support interface, policy edition, ClaimScope, incident window, and source logs; refresh if the scheme, scope, source logs, window, or acceptance probe changes. |
| Readiness disposition | P2W-ready only for the narrow next use above, because the card carries the ambiguity claim, rejects the preselected Work request, and supplies an acceptance probe. |
| Subject-pattern cues (current here) | A.6 for policy or interface wording; A.2, A.2.1, F.6, and A.15 for System, assignment, Method, and Work alignment; A.10 only if evidence reliance becomes current; G.11 for currentness; A.21 only if a gate claim later becomes current. |
The P2W export is narrow: signal, joint EntityOfConcern, effective ReferenceScheme, ClaimScope, claim family, not-wish or not-preselected-Work reason, improvement check or acceptance probe, and honest next use. In this case it also carries the qualification window, validation boundary, follow-up reason, and subject-pattern cues because the stated next use relies on them. Add freshness, unknown handling, source-set, representation, evidence, or other conditional content only when it is current. If the improvement check or acceptance probe is missing, the card stays reviewable-only or source-finding and cannot claim P2W-ready. If the next user wants evidence sufficiency, a gate decision, Work authorization, or selected method, the card preserves the cue and its direct governor carries that downstream claim.