C.22.2:2.1 - Thin First-Use Form

The first substantive use is the Thin form. It is a practitioner-facing prompt for the smallest reviewable card, not a demand to complete a schema.

A ProblemCard is complete for its current use when it states:

1. what signal or cue made the practitioner stop;
2. the one exact joint EntityOfConcern, effective U.ReferenceScheme, and U.ClaimScope for the claims being carried;
3. which claim family is current: actual-PFR assertion, anticipated-condition claim, method-availability or solvability claim, or another directly governed problem-side claim;
4. why this is not merely a wish, ticket, slogan, label, or preselected Work request;
5. what would count as improvement or as an acceptance probe; and
6. one honest next use.

The next use may be P2W-ready, characterize, compare, search, refresh, retire, archive, abstainOrNoChange, or apply the direct pattern governing the named claim, relation, or boundary. If an improvement check or acceptance probe is absent, the card may preserve the signal and choose one of the other uses but cannot claim P2W-ready.

C.22.2 - ProblemCard is the pattern heading. A ProblemCard instance is the C.2.1 episteme described above. ProblemCardRef is only a reference value designating one such episteme; it is not another durable kind. Plain-register glosses and local labels do not replace the Tech name.

Local labels include problem-formulation follow-up reason, validation boundary, risk condition, solvability band, P2W-ready, reviewable, stale, refreshed, retired, archived, abstainOrNoChange, and firstPrinciplesCue. They describe claim content or a local disposition; they create no FPF kind, state-machine kind, gate result, relation occurrence, or mathematical-lens object.

Use E.10.MOVE only when move-like wording no longer denotes one of these local dispositions and instead hides a pattern-use recommendation, Work-entry readiness, performed Work, gate, transformation, source relation, architecture move, call-planning move, or another directly governed value.

Reference labels ending in Ref are reference positions, not kind names. This includes ProblemCardRef, sourceSetRef, rivalProblemFormulationRef, and representationOrWordingUseRelationRef.

Semantic locality comes from the exact EntityOfConcern, effective ReferenceScheme, ClaimScope, declared assumptions or window, and receiving use carried by the relevant claims. A broad domain, organization, practice, or location label is only recognition material until those exact values are recoverable. None becomes a container participant or establishes global Problem identity.

Plain gloss for P2W-ready: problem-side input ready. It means ready as input to downstream P2W or selector reasoning, not ready for Work execution, gate passage, method selection, evidence reliance, or autonomy.

When a downstream reader asks whether intended Work can enter a work boundary, the card may supply problem-side cues, acceptance probes, constraints, and freshness conditions, but A.15.5 governs the readiness relation. C.22.2 decides no full-kit preparation, commitment, launch gate, or performed Work.