C.22.2:23 - Downstream Cue Export

ProblemCard exports problem-side claim content, not authority over downstream use.

The compact export contains:

• problem signal and exact signal reference;
• one joint EntityOfConcern, effective ReferenceScheme, and ClaimScope;
• exact claim family and polarity: actual-PFR assertion, anticipated-condition claim, method-availability or solvability claim, or another named direct claim;
• reason this is not merely a wish, ticket, slogan, label, or preselected Work request;
• improvement check or acceptance probe;
• one honest next use and its disposition: reviewable-only, P2W-ready, abstainOrNoChange, refresh, retire, archive, or subject-pattern cue;
• current qualification window, exact PFR, source-set, A.15.6 composite or component Work, or representation reference only when independently governed and relied on; and
• problem-formulation follow-up reason, validation boundary, freshness condition, and stop only when the receiving use relies on them.

For P2W carry-through, use E.18.1 with the accepted problem-side distinctions. For TaskSignature constitution and assignment, use C.22. For selected-set or search use, apply G.5 only when that relation is current. For intended or performed Work, use A.15 only after its exact object is current; when the question is whether intended Work may enter its boundary, A.15.5 governs WorkEntryReadiness@Context. For evidence, gate, autonomy, or any other claim, apply the direct pattern; the whole card never carries that claim by itself.