C.22.2:2.5 - Field Labels and Current-Use Conditions

Use these readable labels only when current for the case:

problem signal and exact signal reference;
one exact ClaimGraph, joint EntityOfConcern, effective ReferenceScheme, and ClaimScope;
actual-PFR assertion with exact polarity and PFR reference only when C.22.PFR independently establishes the occurrence;
anticipated-condition, forecast, scenario, or counterfactual claim with assumptions and horizon;
method-availability or solvability claim with admitted method set, evidence qualification, constraints, and intended use;
primary viewpoint or an explicitly recovered system-role-kind, assignment, relation-participation, responsibility, or other direct concern as claim qualification, never as card or PFR identity;
symptom detector, problem hypothesis or cause-theory cue, and rival formulation when current;
improvement check, acceptance probe, characterization relation, characteristic or Q-bundle relation, indicator selection, and parity or comparison relation when current;
mandatory constraints, risk condition, validation boundary, freshness or expiry condition, and unknown handling;
problem-formulation follow-up reason when it changes review, discrimination, or receiving use;
representation-transition, retargeting, Bridge, structural-reinterpretation, or wording-use reference when an earlier disposition may no longer transfer;
sourceSetRef, source-set kind, selection or retention criterion, budget or window, and non-scalar next use when the signal comes from a set, pool, front, archive, shortlist, or selected set;
firstPrinciplesCue when a mathematical structure changes the formulation; and
subject-pattern cue naming the direct pattern, claim kind, exact receiving-use reference, and stop condition when an outside claim changes the card use.

Field current-use class	Required treatment
C.2.1 constitution	State the exact ClaimGraph, one joint EntityOfConcern, and effective ReferenceScheme. These constitute the card episteme; ClaimScope, viewpoint, assumptions, windows, and receiving use qualify the relevant claims and relations, while id, carrier, and publication remain outside constitution.
Core problem-side claims	State the signal, ClaimScope, claim family, not-wish reason, improvement check or acceptance probe, and honest next use.
Conditional claims and references	Add only the exact characterization, comparison, risk, validation, freshness, set-source, representation, forecast, solvability, PFR, or other direct relation content that changes the move.
Subject-pattern cue	Keep only the local cue or reference needed by the card, then name the direct pattern and claim kind that govern the outside use.

If a conditional value is not current, omit it rather than writing unknown. Use unknown only where the exact current value rule permits that result. If a required current value is unavailable, state whether the next use is blocked, degraded, sandboxed, or must be reconsidered under a named condition. A stale value gets the exact G.11/currentness assertion; an intentionally omitted value states the record-budget reason without implying it was checked.

When the card compares options, retained candidates, or rival formulations, it states the exact comparison or parity relation or why comparison is not current. Absence is a disposition, not an automatic defect; any positive parity or selected-set result remains outside C.22.2.

problemCardWitnessRefs may be used as a local recoverability group, not as a new kind or evidence graph:

problemCardWitnessRefs:
  problemSignalRef?
  sourceSetRef?
  selectionOrRetentionCriterion?
  characterizationRelationRef?
  parityRelationRef?
  freshnessRef?
  representationOrWordingUseRelationRef?

Generated variants, evaluator feedback, and open-ended mutation remain signal or source-set cues. They do not constitute the card, supply evidence sufficiency, make PFR obtain, or authorize action.