Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:55:20 UTC

C.22.2 - ProblemCard

Type: Calculus (C) Status: Stable Normativity: Normative

Plain name. Problem-side card.

Intent. Give a practitioner one compact C.2.1 episteme that turns a messy signal into reviewable problem-side claim content before Principles-to-Work or selector use. The card preserves practical formulation functions while every world-side relation, evidence use, decision, method, plan, and Work occurrence remains with its direct governor.

Use this when. Use this pattern when work starts from a signal, anomaly, drift, risk, hypothesis, stakeholder demand or concern, set-derived candidate, underused capability, new constraint, new environment, opportunity-like cue, or solution-shaped request, and a downstream task-typing, method-family, planning, evidence, gate, autonomy, or P2W use needs one reviewable problem-side episteme.

Do not use this when. Use another pattern directly when the current question is already actual PFR obtaining, task typing, method selection, Work planning, evidence, provenance, assurance, gate decision, autonomy, archive or selected-set governance, mathematical-lens use, or ordinary discussion with no receiving use. C.22.PFR governs the actual Problem; C.22 governs TaskSignature constitution and assignment.

Boundary summary. C.22.2 yields one reviewable ProblemCard, a P2W-ready problem-side input for downstream C.22, or a stop naming the direct pattern for the claim, relation, or boundary now current. It yields no world-side Problem, task assignment, selected method, WorkPlan, Work occurrence, gate result, or evidence verdict.

C.2.1 constitution. One ProblemCard is one U.Episteme constituted by one ClaimGraph, one independently identified joint EntityOfConcern, and one effective reference scheme. U.ClaimScope, assumptions, horizons, qualification windows, viewpoints, and receiving uses qualify only the claims and direct relations that need them. No setting, carrier, organization, card id, or publication is a fourth constitution component or identifies an actual Problem.

A composite or component U.Work under A.15.6 may be referenced by a claim or receiving use; it neither constitutes the card nor identifies the Problem.

Claim-family, actuality, and solvability boundary. A card may carry several claims only while their ClaimGraph has that one joint EntityOfConcern. An actual-problem assertion states affirmative or negative polarity for the exact ProblematicForRelation obtaining predicate. An affirmative assertion may designate an independently established occurrence only when both participants and its adverse episode are established under C.22.PFR; negative polarity creates, ends, erases, or reidentifies no occurrence.

Judge support under the assertion’s direct subject rule. A.2.4 governs a question about an episteme’s evidence-use or status-use relation, A.10 supplies a replayable evidence, provenance or bounded-reliance account when needed, and B.3 applies only when a named assurance claim is made. G.11 separately governs assertion-edition currentness.

Forecast, scenario, counterfactual, and anticipated-condition claims retain their assumptions, horizon, and direct governor and do not assert a current PFR.

A method-availability or solvability claim concerns the admitted method set, evidence, constraints, and intended use; selecting a method changes that claim, not an independently obtaining PFR. Only non-adversity or cessation of the actual-condition or criterion-applicability participant can end its maximal continuous adverse episode; missing, stale, refuted, or absent evidence cannot.

C.22.2:1 - Problem Frame

A working team can begin with symptoms, anomalies, stakeholder signals, constraints, risks, old solution evidence, comparison ideas, solution temptations, underused capabilities, new environments, opportunity-like cues, or members of a retained set. Opportunity-like signals still need an exact EntityOfConcern, effective ReferenceScheme, ClaimScope, claim family, not-wish reason, improvement or acceptance probe when the next use needs one, and next use.

Problematization becomes useful here when it produces claim content a practitioner can inspect. The card distinguishes:

  • the observed signal from the claim family being considered;
  • the one joint EntityOfConcern from nearby affected entities;
  • the effective scheme and scope from generic setting words;
  • actual-PFR assertions from forecasts and solvability claims; and
  • problem-side readiness from method, Work, gate, or evidence conclusions.

The first-minute question is:

Can I state one concern, claim family, scheme, scope, improvement or acceptance probe when the next use needs one, and next use without turning a signal, card field, setting label, evidence result, or proposed method into the actual Problem?

C.22.2:2 - Thin First Use and Output Kind

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.

Develop the content from accessible material. If the concern is still a rough signal, use the constructive examination in B.5:4.1.2 at the scale needed here:

  1. Follow an actual episode, inspect the artifact or recover the source statement that prompted attention. Separate what it shows from a proposed cause or solution. Trace what result is used, by whom or by what next operation, and what happens there.
  2. Recover why that consequence matters. Read the applicable purpose, acceptance condition, commitment or constraint, or ask the participant responsible for that use. Identify the entity affected in that use and trace how the observed condition bears on its criterion. The person reporting the signal and the subject of the card can each differ from the affected entity. If the criterion or connection is unknown, preserve that specific inquiry rather than asserting an actual Problem.
  3. Form the claim at the extent the material supports. Identify the participants and relation, the cases or conditions covered, and the meaning of the terms used. Distinguish a reported current condition from a forecast, an explanation to test or a claim about available means. Inspect a contrasting case when it can distinguish materially different formulations; retain an adequate existing formulation directly.
  4. When the next use needs a check, derive it from the claim the recipient must decide. A clarification can be tested by asking which recorded event satisfies the applicable rule. An improvement in service needs a comparison of service outcomes across the relevant work under comparable conditions. Identify the observation or argument that can settle the claim. Use an adequate existing result or method; obtain the particular missing observation, interpretation or subject assistance when it prevents that check. A source inquiry can still be the sufficient next use before such a check is available.
  5. Carry the supported formulation and its consequential uncertainty into the Thin form below. Choose the next operation because its available inputs and attainable result answer the remaining question. If no useful operation can yet be described, return to the episode or request help on that missing connection.

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 reference scheme, 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. what observation, need or constraint makes the concern worth addressing, independently of a proposed solution;
  5. what would count as improvement or as an acceptance probe when the next use needs one, or what remains missing; and
  6. one 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.

The local not-wish reason label means the positive grounds for addressing the concern; a stakeholder need can supply such grounds, while a proposed solution alone cannot.

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.

C.22.2:2.2 - Required Solution Use

The Solution turns observed signal material into one C.2.1 episteme and one governed next use, not a completed form.

  1. Capture the symptom, anomaly, risk, stakeholder cue, drift, hypothesis, or other observed signal before naming an actual Problem. If the concern is not yet clear, put available source entries side by side and compare the events or meanings they record. Use what this comparison reveals to develop the question, as in the support example.
  2. Recover the one joint EntityOfConcern, effective ReferenceScheme, ClaimScope, and claim family. If the claims concern unrelated entities, split the ClaimGraph and card.
  3. Separate the signal detector, actual-PFR assertion if independently grounded, anticipated-condition claim, improvement check, candidate acceptance criterion, method-availability claim, monitored risk signal, and proxy-distortion risk. These are not one card status or one PFR participant set.
  4. Pay only for current complexity. Add conditional content only when it changes the current next use; otherwise stop at the lighter card or name the direct pattern for the claim now current.
  5. If a reformulation changes the represented concern, meaning, scope or intended use, establish the actual relation on which reuse of an earlier disposition depends. Use the applicable representation-transition, retargeting or structural-reinterpretation rule; F.9 is needed only when a relied-on semantic correspondence meets its Bridge conditions. Ordinary wording cleanup can preserve the disposition without a new relation.
  6. Close by the next use. A filled card without a truthful next use is not a successful result.

Cheap stop. The smallest card that gives a truthful next use is sufficient. A conforming use does not require heavier fields merely because the full inventory exists.

Open the relation-boundary aid only when another claim or relation changes the next use.

C.22.2:2.3 - Relation Boundary Aid

Once the Thin card is legible, use this aid for an unresolved claim or relation that changes its next use:

Which claim being made, relation, or boundary changes the problem-card use, and which FPF pattern defines or constrains that claim, relation, or boundary?

If the claim, relation, or boundary does not change the current problem-card use, leave it out of the card. If it does change the move, keep only the local cue or reference that makes the card reviewable, then apply the subject pattern for that claim, relation, or boundary.

Current claim, relation, or boundary that changes the card useLocal ProblemCard contentSubject pattern
Characterization, measurement, indicator, Q-bundle, comparison, acceptance, or parityCharacterization cue, acceptance probe, candidate criterion, comparator cue or window cue, and the current reason the relation changes the problem formulation.C.16, A.19, C.25, G.0, G.4, or G.9 according to the relation named by value.
Archive, pool, front, shortlist, selected set, retained candidate, or set-return sourcesourceSetRef, source-set kind, selection or retention criterion, budget or window when current, and declared next use.C.18, C.19, G.5, G.9, G.11, A.6.P:7a, or C.16.Q according to the relation named by value.
Method family, work planning, work-entry readiness, performed work, result record, evidence, provenance, assurance, gate, or autonomyProblem-side cue, source reference when it changes formulation, and stop condition before that outside use.G.5, A.15, A.15.5, A.10, G.6, B.3, A.21, or E.16 according to the claim named by value.
Temporal, causal-use, representation-transition, retargeting, bridge, structural-reinterpretation, or wording-use relationRelation reference plus the inheritance boundary: what can be reused from the old card and what relation is reopened.C.27, C.28, A.6.3.RT, A.6.4, E.17, F.9, E.18, or E.10 according to the relation named by value.
First-principles or mathematical structure cueCandidate structure, preserved and lost structure when current, practical payoff for problem formulation, problem-formulation follow-up reason, and stop condition.C.29 for mathematical-lens use; A.6.0 for a FormalSubstrate U.Signature declaration when that signature declaration is current.
Agentic safe probe or world-affecting next actionProbe need, risk condition, bounded next action, and the safety, autonomy, gate, work, evidence, or assurance claim kind that blocks local action.C.24, E.16, A.21, A.15, A.10, G.6, or B.3 according to the relation named by value.

Over-capture symptom: the practitioner spends the pattern use classifying FPF patterns while one or more core Thin items in C.22.2:2.1 remain unstable.

Repair: return to the Thin form in C.22.2:2.1 and complete only its core items. Reopen this aid only for the claim, relation, or boundary that changes the next use.

C.22.2:2.4 - Use Boundaries and Record Budgets

Use C.22.2 when a signal is not yet a problem-side record and downstream task typing, P2W, method-family selection, work planning, evidence use, gate passage, autonomy control, or selected-set use depends on such a record. A known method does not close this pattern when the problem signal, scope, acceptance probe, or EntityOfConcern remains unstable.

Use another pattern directly when the question under repair is already that pattern’s EntityOfConcern or governed relation:

  • A.15 for work planning or performed work;
  • A.2.4 for an episteme’s evidence-use or status-use relation, A.10 for a needed replayable evidence/provenance/reliance account, G.6 for a needed evidence-graph representation, or B.3 for a named assurance claim;
  • A.21 for gate decision;
  • E.16 for autonomy;
  • C.11 for a local choice among explicit options;
  • C.18, C.19, or G.5 for archive, pool, front, or selected-set governance.

C.22.2 may still preserve the problem-side cue or reference that explains why that pattern is now current.

Use record budgets:

  • Thin record budget: signal, joint EntityOfConcern, effective ReferenceScheme, ClaimScope, claim family, not-wish, not-slogan, not-ticket, or not-preselected-work reason, provisional improvement check or acceptance probe when needed, and one next use.
  • Standard record budget: Thin fields plus the current comparison, acceptance, risk, validation, freshness, unknown-handling, or P2W-readiness fields needed for downstream use.
  • High-relation record budget: Standard fields plus only the relation references needed when public, disputed, high-risk, set-derived, cross-scheme, cross-use-boundary, evidence-adjacent, autonomy-adjacent, gate-adjacent, agentic, temporal, causal, representation, or Part-G relations are current.

Stop at Thin when it gives a truthful next use. Stop at Standard when it supplies enough problem-side input for a minimal TaskSignature, TaskKind, or ProblemProfile under C.22. Apply the governing FPF pattern for the claim being made, relation, or boundary instead of enlarging the card when the issue under repair is no longer the problem-side record itself.

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 ClaimGraph, joint EntityOfConcern, effective ReferenceScheme, and ClaimScope;

  • actual-PFR assertion with 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 declared 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 classRequired treatment
C.2.1 constitutionState the 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 claimsState the signal, ClaimScope, claim family, not-wish reason, improvement check or acceptance probe when needed, and next use.
Conditional claims and referencesAdd only the characterization, comparison, risk, validation, freshness, set-source, representation, forecast, solvability, PFR, or other direct relation content that changes the move.
Subject-pattern cueKeep 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 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 needs the applicable G.11 currentness qualification.

An irrelevant field can be omitted silently; explain an omission only when the receiving reader could otherwise rely on a missing value or mistake it for a completed check.

When a comparison of options, retained candidates or rival formulations is part of the claim, state its basis and applicable comparison or parity relation. Merely preserving alternatives does not assert comparability or require a parity result. Any claimed parity or selected-set result remains under its direct governor.

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?

Evaluate generated problem descriptions and evaluator feedback by their content and the support required for the receiving use. They may supply problem-side claims or supporting grounds; a generated description may itself serve as the card when it satisfies the C.2.1 constitution and current card use. Apply the relevant validation, currentness and action-entry conditions to the claims and proposed action.

C.22.2:2.6 - Anti-Pattern Checks and Worked Slices

Anti-pattern checks start from the local card use:

  • card-as-executable-work request: the card is treated as executable work while method, plan, and work occurrence remain undecided;
  • form-completion: every field is filled because the template exists, even though the Thin next use would be truthful;
  • readiness shortcut: P2W-ready is declared from signal and scope alone, without improvement check or acceptance probe;
  • source-claim shortcut: a preselected solution, work request, proof-looking reference, gate-looking cue, or authority-looking cue replaces one or more core Thin items in C.22.2:2.1;
  • scalar shortcut: archive, set-return, Goldilocks, NQD, OEE, partial-order, stepping-stone, or indicator material collapses into one readiness score;
  • prestige shortcut: first-principles or mathematical wording is kept without practical payoff, preserved and lost structure when current, problem-formulation follow-up reason, and stop condition.

Local stop rule: if the encountered material tries to carry a claim outside C.22.2, the card keeps only the cue or reference that changes problem formulation or the next use, then names the governing FPF pattern and claim kind named by value to use before that claim is relied on.

The worked cases in §20 show both a Thin card and set-derived recognition. Use the applicable case to recover a needed distinction; an ordinary card need not reproduce both examples or acquire their conditional fields.

C.22.2:2.7 - Conformance Checklist Requirements

The checklist protects a completed or reviewed card from overread; the writing order remains the Thin form and next use.

CheckRequired test
C.2.1 identityThe card has one ClaimGraph, one independently identified joint EntityOfConcern, and one effective ReferenceScheme. Unrelated PFRs or other concerns force ClaimGraph/card split.
Claim-family separationActual-PFR assertion polarity, reliance result, anticipated-condition claim, and method-availability or solvability claim remain distinct.
PFR boundaryAny affirmative actual-PFR assertion names an occurrence independently established by C.22.PFR. A card, signal, label, viewpoint, evidence item, method, or negative assertion creates or ends none.
Core usabilityThe card states signal, ClaimScope, claim family, not-wish reason, improvement check or acceptance probe when needed, and next use.
P2W-ready reasonP2W-ready appears only with an improvement check or acceptance probe and one named downstream use; it is problem-side readiness only.
Field budgetConditional content appears only when current; absence and admitted unknown remain distinct.
Exact source and setA set-derived card preserves exact sourceSetRef, set kind, retention or selection criterion, and declared next use without becoming an archive or portfolio object.
Direct-governor cueClaims outside C.22.2 remain local cues or references and name the pattern and claim kind used next.
Constitution stays exactOnly ClaimGraph, one joint EntityOfConcern, and effective ReferenceScheme constitute the card. ClaimScope, assumptions, windows, viewpoint, receiving use, and any A.15.6 Work reference stay in their claims and direct relations; no setting, carrier, or organization is added as a participant.
Currentness and changeFreshness, changed representation, retargeting, or unknown-blocked use states refresh, retirement, bounded use, abstainOrNoChange, or the exact relation reopened.
Scalar and proxy guardGoldilocks, NQD, OEE, set-return, priority, indicator, or stepping-stone wording does not become one readiness score or substitute for value.
First-principles payoffA mathematical cue changes the formulation through a supported consequence. Domain mathematics can be used directly; C.29 governs a live representation or transfer question, with its correspondence and limits.
External wording recoveryPassport, rule-of-choice card, evidence pack, autonomy budget, logs, gates, portfolio, factory, and similar source terms enter only as signal, set, characterization, comparison, or follow-up material under their direct governors.
Record-budget invariantThe card is as small as the current next use permits; a template, relation aid, or worked example is not another FPF kind.

C.22.2:3 - Problem-Kind Recovery

Problem remains an ordinary word when no FPF-governed claim is being made. Recover it only when wording changes a governed kind, relation, selector use, evidence claim, causal-use claim, assurance claim, decision, or use boundary.

FPF-governed useCurrent recoveryC.22.2 disposition
Symptom, anomaly, deviation, risk signal, or stakeholder signalProblem signal or exact signal referenceMay trigger a card but is not an actual Problem or complete problem-side claim by itself.
Problematic situationPlain cue for an exact condition, entity, Work, transformation, or relation under its direct patternThe phrase introduces no U.Situation; an actual Problem still requires one obtaining C.22.PFR relation.
Actual ProblemOne obtaining ProblematicForRelation with exact condition and applicability participantsC.22.PFR governs actuality and identity; the card can assert or designate it only after that settlement.
Forecast, scenario, counterfactual, or anticipated conditionNon-actual claim with assumptions, horizon, and direct governorPreserve the claim family; do not turn affirmative wording into current PFR obtaining.
Method availability or solvabilityClaim over admitted methods, evidence, constraints, and one intended useSelecting a method revises this claim but does not end an actual PFR.
Framed problem-side representationClaimGraph about one joint EntityOfConcern under one effective ReferenceScheme and ClaimScopeCenter of ProblemCard; representation change uses its direct transition, retargeting, Bridge, or wording-use governor.
Candidate from archive or retained poolMember of an exact source set under a retention relationPreserve sourceSetRef, set kind, criterion, budget/window, and declared next use; set semantics remain outside the card.
Selected problem from a set-return treatmentExact selected member under a direct selection relationThe card may carry the member, but selection, parity, archive, and set-return claims remain with G.5, C.18, C.19, G.9, G.11, A.6.P:7a, or C.16.Q as applicable.
Problem ready for selector-facing useCard sufficient to prepare or assign TaskSignatureC.22 constitutes and assigns TaskSignature; card content is not copied wholesale into it.
Downstream task, method, plan, or performed-Work cueExact value or relation under C.22, G.5, A.15, or another direct patternKeep only the problem-side cue and stop before claiming the downstream result.
E.8 or E.9 Problem frameAuthoring or decision-rationale sectionNot a ProblemCard and not an actual Problem by heading alone.

The card may reference candidate ProblemProfile, TaskSignature, source set, PFR, forecast, solvability claim, or first-principles cue only when that reference changes its use. No reference is promoted into a local kind or card constitution component.

C.22.2:4 - Problem, Task, Method, Work, and Result Split

ProblemCard remains usable while a method is unknown, contested, or not yet selected. A known method does not make the card ready while any core Thin item in C.22.2:2.1 remains unstable. If the problem-side episteme and method are accepted and only planned execution remains, apply A.15.

Term or local nameCurrent FPF recoveryLocal disposition
ProblemOrdinary wording, ProblemCard claim content, or actual PFR according to the sentenceC.22.2 governs the card; C.22.PFR governs the actual relation. Label alone decides neither.
ProblemCardC.2.1 episteme about one joint EntityOfConcernCompact problem-side result before P2W; not a work request or world-side Problem.
ProblemProfileC.2.1 episteme used by a named receiving selection useOne episteme can serve as both ProblemCard and ProblemProfile when it satisfies both uses and C.2.1 constitution; TaskSignature membership and assignment remain separately tested under C.22.
TaskKind, TaskFamilyRef, TaskSignatureC.22 selector-facing declaration content and epistemeDownstream typing values; not WorkPlan entries.
TaskSignatureAssignmentRelationObtaining relation among exact problem-side episteme, TaskSignature, and receiving-use epistemeSeparate from all three participants and from card fields.
Method-family selection claimG.5 comparison or selection resultNot a card field and not PFR cessation.
U.Method, U.MethodDescriptionMethod and method-description valuesGoverned by their direct method patterns.
U.WorkPlan and its declaration-local SlotFillingsPlanItem contentIntended Work and planned-filling rows addressed only through that WorkPlanDefined and tested by A.15.2 and A.15.3; not a TaskSignature or ProblemCard.
U.WorkPerformed dated WorkGoverned by A.15.1; its record or evidence is separate.
Result, measurement, assertion, evidence, or relianceOutput or claim governed by C.16, C.2.1, A.10, G.6, B.3, G.11, or its direct subject patternA claim-bearing result can supply card content or support. It can serve as the card when it satisfies the card’s C.2.1 constitution and problem-side use; other results are represented by claims about them.

Use C.22 to prepare the TaskSignature from the exact problem-side episteme or ProblemProfile needed by one receiving use. Report the adequate signature actually adopted for the stated problem-side episteme and use under C.22:5.2. Another adequate description can remain available. If adequacy or adoption is unresolved, identify the candidates and the missing grounds. When the question becomes selection, planning, performed Work, result, gate, evidence, or reliance, apply its governor instead of expanding the card.

C.22.2:5 - Relation to C.22

C.22 governs TaskSignature constitution and TaskSignatureAssignmentRelation. ProblemCard comes earlier: it states which problem-side claims are ready for P2W, search, comparison, characterization, refresh, retirement, or another direct pattern.

A card may prepare TaskKind, characteristic bindings, scope, and candidate TaskSignatures. C.22 assigns one only when the exact problem-side episteme, TaskSignature, and receiving-use episteme satisfy its obtaining rule. A plausible signature remains a candidate until its adequacy and actual adoption for that use are established.

No card detail is copied wholesale into TaskSignature. Downstream method, Work, result, evidence, gate, autonomy, archive, portfolio, and selected-set claims remain with their direct patterns.

C.22.2:6 - Characterization, Indicators, and Comparability

State the characterization and comparison basis when the formulation or next use depends on it. A card that only preserves a signal or proposes an inquiry can finish without a measurement or parity account.

These FPF patterns supply the relevant subject content:

  • C.16 carries measurement characterization, backing, and comparability discipline;
  • A.19 carries characteristic, scale, unit, polarity, and indicator-use discipline;
  • C.25 governs engineering-quality bundles; C.16.Q helps recover other quality-like descriptions and the Characteristics their use needs;
  • G.9 carries parity, comparison-window, comparator, budget, unit, repeatability, and reproducibility pins;
  • G.0 carries comparison-frame and CG-Spec governance;
  • G.4 carries acceptance clauses and threshold predicates;
  • use G.5 for selector-facing selected-set result declaration when the problem enters a selected set; when actual audience availability is separately current, use E.17 for a source-backed publication face and return to source and E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability.

Missing characterization or parity relation is a current disposition. When that relation is current, apply the characterization, parity, search, or pool pattern before treating the problem as ready for P2W.

The C.22.2 candidate acceptance criterion separates functional check, constraint compliance, risk or safety boundary, parity or comparison relation, and freshness window when those relations are current. Apply G.0 for the comparison frame, CG-Spec, or comparability governance. Acceptance clauses and acceptance threshold predicates apply G.4; C.22.2 may name only the needed relation, cue, or reference. Passing a test, improving one observed indicator value, or naming an acceptance phrase is not by itself sufficient for P2W use.

C.22.2:7 - Source Record-Form Recovery

Source record names are recovered by use, not by label shape. This section prevents source prose from becoming local C.22.2 subobjects.

Source form familyC.22.2 preservationSubject pattern named by value for outside use
Problem card, problematization passport, problem-side note, or ordinary problem signalCarry the signal, joint EntityOfConcern, effective ReferenceScheme, ClaimScope, claim family, not-wish or not-preselected-work reason, improvement check or acceptance probe when needed, and next use.C.22.2 governs only the problem-side episteme; downstream selector-facing use remains with C.22.
Archive, portfolio, palette, front, shortlist, selected set, LivePool, set-return, or retained candidatePreserve sourceSetRef, source-set kind, selection or retention criterion, budget or window when current, and declared next use.C.18, C.19, G.5, G.9, G.11, A.6.P:7a, and C.16.Q according to the relation named by value.
Characterization passport, characteristic card, parity plan, comparison note, rule-of-choice card, or acceptance-looking rowPreserve the cue, candidate criterion, comparator cue or window cue, and current reason the relation changes formulation.C.16, A.19, C.25, G.0, G.4, G.9, or C.11 according to the relation named by value.
Evidence pack, provenance note, assurance row, gate log, autonomy budget, runbook, rollback plan, method selection, work plan, performed-work note, result record, or result measurementPreserve only the problem-side cue, risk or validation boundary, source reference, and stop condition before that use.A.10, G.6, B.3, A.21, E.16, G.5, A.15, C.16, or G.11 according to the claim named by value.
Candidate solution, described system, ordinary log, budget, ledger, protocol, plan, pack, or factory wordingRecover the use under repair: problem-side source material, problem-side source relation, selected-set material, work, evidence, gate, or autonomy material, or ordinary example.Apply the subject pattern for the recovered relation; do not introduce a local C.22.2 kind from the label.

If the source supplies problem-side material, make the needed content available in the card, directly or through an accessible return to the exact source content. The receiving reader must be able to interpret what that return supplies; when the card travels without access to the source, include the content and interpretation needed for its next use. If the source supplies another FPF-governed claim, keep only the local cue and apply the pattern that defines or constrains that claim.

C.22.2:8 - Portfolio, Archive, and Set-Return Treatment

Archive, portfolio, pool, front, shortlist, selected-set, and set-return material remain source and set cues for the current problem-side record. ProblemCard preserves sourceSetRef, source-set kind, selection or retention criterion, and the declared next use when current; portfolio and archive governance stays with the named subject patterns and does not become a local problem-card kind.

Source wordingCurrent FPF pattern or relationRequired problem-card preservation when the corresponding claim is being made
Problem archiveC.18, C.19, A.10, G.6Preserve source set or reference, retention criterion, candidate status, and provenance relation.
Problem portfolioG.5, C.19, G.9, G.11Preserve selection or retention criterion, budget or window, review cadence, and selected-set or LivePool relation.
PaletteC.18, C.19, G.5Preserve candidate-family or option-set interpretation without turning it into evidence or approval.
FrontC.18, A.19, C.25, G.5Preserve declared characteristics and non-dominated set interpretation.
ShortlistG.5, with G.9 when comparison pins matterPreserve selected-set criterion and downstream use.
Ranked shortlistG.5 only when an order is declaredPreserve ranking criterion or narrow to selected set with tie notes.
Selected setG.5Preserve selected-set output, selection pins, and unknown handling.
LivePoolC.19Preserve pool policy, current treatment, and change trigger.
Set-returnG.5, C.18, C.16.Q, declared comparison recordsPreserve set-valued result when no total order is declared.

A singleton problem card is the degenerate case. If it came from a portfolio, front, archive, or pool, the selected problem remains traceable through sourceSetRef: the lightweight reference to the source-set kind, source reference, selection or retention criterion, budget or window, review cadence, and direct pattern when current. sourceSetRef is a reference field, not a new kind and not a downstream claim carrier.

sourceSetRef preserves the recoverable set-source relation when current: Palette, Front, Archive, ExplorationArchive, Shortlist, RankedShortlist, SelectedSet, LivePool, or another accepted source-set form. If the set-source relation is not recoverable, the card may keep a set-finding cue, but it does not claim selected-set readiness or archive-derived readiness.

When multiple plausible problem formulations remain current, C.22.2 does not bind one TaskSignature prematurely. Each optional rivalProblemFormulationRef states the rival formulation, EntityOfConcern, effective ReferenceScheme, ClaimScope, preserved concern, lost concern, reason not selected yet, and next discrimination action. It is not a CG-Frame, not the E.8 Problem Frame, and not a representation-frame kind.

The next discrimination action may be to characterize, compare, retarget, reopen the source material or source relation, choose a local problem formulation, or apply the relation-bearing pattern. Reframing is triggered when EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, or cause-theory cue changes the problem representation enough that readiness or use-boundary cannot be inherited by wording continuity.

C.22.2:9 - Goldilocks and Set-Return Docking

Use a Goldilocks interpretation only when a declared search or learning policy seeks a problem of suitable difficulty for current capability. Explain that fit through the applicable characteristics, constraints and comparison or retention rule. It supplies neither a universal readiness score nor a new problem kind.

A Goldilocks, stepping-stone, or archive-derived problem is represented by its source-set reference, selection or retention criterion, and current next use, not by one difficulty, priority, or readiness score.

ProblemCard carries only the problem-side readiness fields and relation references:

  • source set kind when archive, pool, front, shortlist, selected set, or portfolio language is current;
  • solvability band;
  • characteristic-space, declared problem-side characteristic descriptor, or Q-bundle relation;
  • declared difference criterion when novelty or diversity is claimed, or apply the governing characterization or comparison pattern;
  • non-scalar trade-off, dominance, partial-order, or set-return relation when that relation is being made;
  • measurability or explicit unknown handling;
  • reversibility or containment for safe probing when current;
  • stepping-stone option value when retention matters;
  • expiry or refresh condition;
  • selected-set, archive, pool, front, or parity relation when that relation is being made.

The local solvability band label means a scheme-and-scope-qualified interpretation of feasible-but-not-trivial fit under current capability, constraints, validation boundary, and optional set-return relation. The declared search or learning policy supplies its difficulty and feasibility criteria; a scalar criterion or ranking remains usable with its measurement and policy basis. No universal difficulty or readiness scale is introduced.

If the band cannot be tied to a characteristic, Q-bundle, comparison, retention, or capability relation and its qualification, treat Goldilocks wording as informal recognition only and bind any selection, set-return, or parity claim to its direct governor.

The governing family is C.18, C.19, G.5, G.9, G.11, A.6.P:7a and C.16.Q, selected for the relation needed. C.22.2 can state this qualified problem-side fit before P2W. C.22:15 addresses difficulty targets only when a declared search or learning policy uses them; a TaskSignature includes the resulting trait only when it can change the receiving eligibility, acceptance or selection question.

C.22.2:10 - Structure Cue That Improves Formulation

Use an adequate domain equation, model or calculation directly when it answers the formulation question. Enter C.29 when choosing or transferring a representation could supply a missing inference, or when reliance on a representation exceeds its supported correspondence.

firstPrinciplesCue is a local label for a structure that may change the formulation. It is neither a mathematical-lens kind nor a requirement to produce a C.29 record.

The problem card may ask whether a first-principles or mathematical structure helps find or improve the problem formulation, not only whether an already-mentioned mathematical expression helps the problem formulation. Useful cues include state space, graph, boundary, topology, symmetry, invariant, variational or constrained-optimization structure, probability or information structure, resource bound, obstruction, scale window, composition, or coarse-graining choice.

The practitioner-facing use is:

Identify the structure, obtain its relevant consequence, and say how that consequence changes the formulation. When the inference relies on a representation or transfer, explain the correspondence, assumptions and omitted distinctions that bound its use.

Distribution by principles:

Source-side cueCurrent FPF pattern or relationC.22.2 use
Zero-principles and first-principles invariants, constraints, symmetry, composition, multi-scale description, variational structure, probability or information, and resource limitsThe subject pattern for the claim; C.29 when mathematical representation choice, transfer or reliance remains unresolved; A.19, C.16, C.25 or G.9 when their characteristic, measurement, quality-bundle or parity question is currentCarry the structure and consequence that help formulate the problem, with the assumptions and limitations needed for their use.
Second-principles method-family implicationsG.5, A.15, E.18, A.19 as applicableName the method-family cue; do not perform method selection in the problem card.
Third-principles reproducibility, checks, templates, records, logs, rollback, evidenceA.10, G.6, B.3, A.21, G.11, E.16 as applicableName the reproducibility or evidence cue and apply the subject pattern for the claim kind named by value before relying on that claim.

When no useful mathematical construction is needed, proceed with the ordinary formulation. Keep an unresolved candidate cue only when it can guide the next observation or construction.

C.22.2:11 - Validation, Reliance, AI-Agent Cues, and Safe Probing

ProblemCard exposes three local fields for downstream use:

  • problem-formulation follow-up reason: why this formulation is worth keeping, reviewing, discriminating, or moving onward now;
  • validation boundary: what has been checked for the current next use, what may be used now, and which use is governed by another pattern;
  • risk condition: the monitored risk, cost-of-error concern, or containment concern that may change the safe next action.

Use these fields to state a local reliance disposition, not to authorize downstream action.

Card-use conditionLocal dispositionNext pattern application
The current reason is sufficient for the named reversible P2W use.P2W-ready only for that named use, with effective ReferenceScheme, ClaimScope, qualification window, validation boundary, and stop condition.Apply measurement, evidence, temporal, refresh, representation, gate, autonomy, Work, or assurance patterns only when those claims are part of the use.
The reason is useful but narrower than the attempted use.Narrow the attempted use; name the narrowed use, blocked attempted use, and stop condition.Apply the subject pattern for the missing claim, relation, or boundary.
Source material, source relation, validation, or currentness is stale, conflicted, uncalibrated, or untied to the current relation.Choose abstainOrNoChange, refresh, or reopen; name the missing relation, evidence-needed cue when current, and decision point.Use A.10, G.6, B.3, C.16, C.27, G.11, A.6.3.RT, A.6.4, E.17, F.9, or E.18 according to the reopened relation.
The proposed next action requires a safety, release, gate, autonomy or Work basis beyond the card.Use the independently applicable grounds or authorization; if missing, block only the dependent action and retain the usable problem-side claim.Apply B.3, A.21, E.16, A.15, A.10, G.6, or B.2.5 when its governed claim is current.

Cause-theory cues may focus problem formulation inside ProblemCard. Association, intervention, counterfactual, responsibility, expected-effect, or causal-evidence claims are governed by C.28 plus evidence, provenance, or assurance patterns when those claims are being made.

Environment design and safe probing may appear as problem signal reference, validation boundary, risk condition, or subject-pattern cue. For a probe affecting a controlled EntityOfConcern, identify the applicable safety or authorization condition. Existing adequate grounds may permit the action; the card itself supplies no missing permission, release authorization or gate result.

C.22.2:12 - Freshness, Expiry, and Unknown Handling

C.22.2 includes a section-local state and disposition vocabulary for ProblemCard; this vocabulary is not a new FPF kind. These labels describe the card’s current governed use; they are not required states in a transition sequence, event kinds, or gate records. The local labels are:

State or disposition labelRequired interpretation
draftSignalA problem signal has been captured, but the card is not yet reviewable.
reviewableThe problem-side record can be inspected, challenged, sent onward, or refined, but it is not necessarily P2W-ready.
P2W-readyLocal disposition label with plain gloss: problem-side input ready. The problem-side record is sufficient for downstream P2W or selector-facing use; it is not ReadyForWork, GateReady, MethodReady, AutonomyReady, or work authorization.
subject-pattern cueA claim, relation, or boundary outside C.22.2 changes the current problem-card use; the card names the governing FPF pattern and claim kind named by value to use next without claiming that use inside C.22.2.
staleFreshness or expiry blocks the intended downstream use until refreshed, retired, or otherwise disposed.
refreshedThe relevant signal, source material, source relation, ReferenceScheme, ClaimScope, characterization, parity, evidence, provenance, assurance, representation relation, or wording-use relation has been updated enough for the named use.
retiredThe problem-side record is no longer used as a current problem for downstream work.
archivedThe record is retained under the relevant archive, pool, front, or selected-set pattern without being current for P2W.
abstainOrNoChangeNo downstream receiving use is selected because the signal is stale, duplicate, already solved, already absorbed, unnecessary, or not worth current downstream Work.

Freshness names the affected locus:

  • Problem signal. Ask whether it is still present, recurring, solved, absorbed, duplicate, unnecessary, or no longer worth downstream work.
  • Effective ReferenceScheme or ClaimScope. Ask whether the applicable meaning, cut, assumptions, window, or receiving use changed enough to alter the formulation.
  • Characterization or parity relation. Ask whether measurement, comparison, and parity relations are current enough for the intended use.
  • Problem-formulation reason, source material, or source relation. Ask whether cited sources, provenance, reason references, and source references remain current.
  • Source-set reference. Ask whether archive, front, pool, shortlist, or selected-set membership and its selection or retention criterion remain current.
  • Representation or wording-use relation. Ask whether wording, diagram, functional description, transformation-flow path, Bridge, retargeting, or other representation change alters the EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, comparison relation, governed next use, or relation needed for inheritance.

A stale source material, source relation, or evidence reference does not always retire the problem; it may require refresh while the problem remains reviewable. A stale problem signal may lead to refresh, retire, archive, abstain or no-change, or a subject-pattern cue for the claim, relation, or boundary that is checked.

Freshness or expiry failure is a current disposition. A stale or unknown-bearing problem card may remain reviewable as a problem-side record, but it does not become P2W-ready unless freshness and unknown handling permit the intended downstream use. A stale problem card does not silently remain usable as P2W input.

When freshness, expiry, or unknown handling fails, choose one of these current dispositions:

  • refresh the problem card or its characterization or comparison relation under G.11, C.16, A.19, C.25, or G.9;
  • retire or deprecate the problem-side record under the relevant archive, pool, selected-set, or refresh pattern;
  • continue only as explicitly governed bounded-risk use under the subject pattern for the claim being made, relation, or boundary.

Unknown-handling fields state whether they permit use, require degraded use, abstention, or sandbox treatment, or make the current problem formulation blocked. No P2W, no change, or abstain-for-now may be a successful next use when the signal is stale, duplicate, already solved, already absorbed, unnecessary, or not currently worth downstream work. Before using the ProblemCard as input to TaskSignature preparation or assignment under C.22, check whether the problem signal is still present and whether prior work has already solved or removed the problem.

C.22.2:13 - Representation and Wording-Use Relation Continuity

C.22.2 names A.6.3.RT, A.6.4, E.17, F.9, E.18, and E.10 only when changed problem formulations, diagrams, functional descriptions, transformation-flow paths, wording, or PathSlice examples carry a current representation, bridge, retargeting, structural-reinterpretation, or wording-use claim. The card may preserve the local cue, reference, or problem-formulation follow-up reason, but it does not prove continuity or use-boundary inheritance by wording similarity.

Framing is not wording repair. A framing change applies when EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, comparison relation, use-boundary inheritance, or next use changes.

Wording-use repair is current only when wording, diagram, functional description, transformation-flow path, Bridge, retargeting, or another representation change alters the carried problem-side representation, EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, comparison relation, governed next use, or subject-pattern cue.

Ordinary wording cleanup triggers no representation-continuity relation and does not block a Thin ProblemCard.

Pattern or pattern familyWhen it matters for the cardC.22.2 use
C.22Problem-side record, ProblemProfile, and TaskSignature are being related.Keep TaskSignature minimal and apply representation-transition, bridge, retargeting, structural-reinterpretation, or wording-use patterns only when a current relation claim or use-boundary appears.
C.16, A.19, C.25, G.9, and G.11Characterization, characteristic, Q-bundle, parity, or freshness representation changes the selected entity or comparison relation.Preserve only the problem-card cue and apply the characterization, parity, bundle, or refresh relation named by value when that relation is being made.
C.29, A.6.3.RT, or A.6.4, as applicableAn unresolved mathematical representation choice, transfer or reliance question needs C.29; an asserted representation-transition or retargeting relation needs its own governor.Retain the object, representation, correspondence and limits actually used. Reuse a sufficient domain result directly; obtain a separate relation or lens-use account when the receiving question requires it.
C.18, C.19, and G.5Archive, pool, front, shortlist, selected set, method-family, or selected-set output uses transformed representations.Preserve source-set reference, criterion, and downstream use; keep selection semantics outside the card.
A.6.P, C.16.Q, E.10, E.17, F.9, E.18, A.10, G.6, B.3, A.21, E.16, and A.15Source wording, quality wording, multi-view, bridge, structural reinterpretation, evidence, provenance, assurance, gate, autonomy, method, or work relation is current.Keep the local cue only; apply the subject pattern for the claim being made, relation, or boundary before reusing readiness or relying on the transformed material.

C.22.2 may not treat changed-problem examples as governed relations unless the appropriate accepted FPF relation is named.

C.22.2:14 - Source and P2W Carry-Forward

Apply the following source details as constraints on C.22.2 use and its P2W-facing input.

Source detailCurrent FPF recoveryC.22.2 carry-forward relation
Source examples: person, team, organization, System, community, episteme, and WorkRecognition material for the EntityOfConcern or A.15.6 Work when it changes problem-card use; not a new FPF kind taxonomyA domain or practice locus may qualify the effective ReferenceScheme, ClaimScope, horizon, indicators, cost of error, the exact system-role kind or assignment, participation, viewpoint, or comparison, but it neither constitutes the card nor identifies an actual Problem.
Engineering language for reproducibility and management language for coordination, rights, resources, and responsibilityVerification and reproducibility, coordination, right, resource, system-role classification or assignment, participation, and responsibility claims are different FPF relationsC.22.2 may retain bare role only as an E.10.ROLE cue; any exact kind, assignment, participation, budget, right, or responsibility field or relation reference follows its direct pattern. Claims outside the problem-side record stay there.
Problem factory, solution factory, and factory-of-factoriesSource exposition for three related work families, not FPF process kindsC.22.2 covers only the problem-side output. Solution and P2W relations use G.5, A.15, E.18, A.10, G.6, B.3, A.21, E.16, and G.11; organizational-development or platform-capability questions are outside this pattern.
Characterization protocol: ReferenceScheme, ClaimScope or slice, compared set, exact system-role-kind, assignment, participation, or viewpoint qualification, scale, polarity, measurement Method, freshness, repeatability, budget, missing data, and comparison rulesC.16, A.19, C.25, G.9, and the exact qualification patternProblemCard cites characterization, qualification, and comparability relations when current; available measurement or a visible label alone is not an accepted use relation.
Indicator uses: mandatory constraints, optimization objectives for the current cycle, and risk signalsCharacteristic and Q-bundle use under selected comparison or acceptanceC.22.2 preserves whether an indicator is used as a mandatory constraint, optimization objective, or monitored risk signal when that distinction affects acceptance; the use is not a system-role kind or assignment.
Problem portfolio as a period-bounded selected set with budget, assignment or participation cue, review cadence, and not-selected dispositionG.5, C.19, G.9, G.11, A.6.P:7a, C.16.Q, and E.10.ROLE when bare role is the source cueProblemCard preserves the source set or reference, selection or retention criterion, budget or window, review cadence, and not-selected or stepping-stone disposition. If an actual System, local system-role kind, assignment, participation, or responsibility relation matters, cite that independently obtaining direct claim rather than the portfolio wording.
Goldilocks as zone-of-growth selection calibrated to current capability, effective ReferenceScheme, and ClaimScopeProblem-side entry to current NQD, OEE, and set-return familyC.22.2 preserves the declared difficulty and feasibility criteria; it supplies no global difficulty scale or readiness verdict.
Stepping stones as option value: new actions, tools, data, interfaces, environments, or experiment modes that may expand downstream searchA possible contribution to a later inquiry or action; retention or selection is a separate use when currentExplain what continuation the proposed stepping stone could enable and under which conditions. When claiming archive, pool or selected-set retention, also supply that pattern’s retention or tie-break basis.
P2W chain: signatures and principles help select formalism, ontology, characterization, and method-family materialA.6.0, A.6.1, C.16, A.19, C.29, G.5, and E.18C.22.2 supplies problem-side cues and relation references; it does not select the formalism, ontology, mechanism, or method family by itself.
P2W chain: condition measurement and comparison help select a concrete methodC.16, A.19, C.25, G.9, G.5, and A.15State the comparison-and-acceptance cue or acceptance-criterion reference and parity and characterization relations needed by downstream method selection.
P2W chain: work planning makes planned work inspectableA.15.2 and A.15.3C.22.2 may supply problem-side input for TaskSignature preparation and assignment under C.22; the identifiable plan is one exact U.WorkPlan, and any planned-filling row remains declaration-local content addressed through that plan.
P2W chain: performed work produces work-result recordsA.15, A.10, G.6, and B.3C.22.2 does not treat performed work or result records as problem-card fields beyond problem-side cues or named relation references.
P2W chain: result measurement can trigger refresh or return to earlier source materialC.16, G.11, A.10, G.6, B.3, C.18, and C.19C.22.2 states freshness or expiry and unknown-handling dispositions that let downstream result measurement refresh, retire, or re-open the problem-side record.
Runbook, rollback plan, canary, SafeStop, error budget, and override protocolWork, gate, autonomy, evidence, and control recordsThese source forms are not C.22.2 subobjects; apply A.15, A.21, E.16, A.10, G.6, or B.3 when the corresponding claim is current.
Trust debt after reliance-window expiryFreshness and decay indicator and bounded-risk continuation questionTreat trust debt as an indicator or problem-formulation follow-up reason, not as punishment, proof failure, or gate passage by itself.

C.22.2 remains the problem-side output. P2W carries its problem-side cues and, when current, receiving-use and Work references into method-family selection, work planning, performed-work interpretation, and result measurement.

C.22.2:15 - SoTA Decision-Use Source Material

The following external sources are adopted or adapted only where they change this pattern’s answer.

Current source or relation lineReferencePattern useDisposition
Problem framing turns an ill-structured situation into a solvable design problem and requires care because “framing” is ambiguous.2025 CEEA paper “Towards a Theoretical Framework of Framing in Engineering Design”, https://doi.org/10.24908/pceea.2025.19713Contributes deconfliction of symptom, situation, framed problem representation, and task.Adopted as field and kind-recovery cue; wording is expressed in current FPF terms.
Strategic problem framing distinguishes symptoms and attention allocation from causal problem formulation.2025 Organization Science article “Looking at the Trees to See the Forest: Construal Level Shift in Strategic Problem Framing and Formulation”, DOI suffix 2024.19134, https://doi.org/10.1287/orsc.2024.19134Motivates the fields for problem signal, problem hypothesis/cause-theory cue, and improvement check.Adapted; causal claims still apply C.28 plus evidence, provenance, or assurance patterns when current.
QD and OEE work motivates collections, fronts, archive retention, set-return, and non-single-winner treatment.2026 survey “A survey on Quality-Diversity optimization: Approaches, applications, and challenges”, https://www.sciencedirect.com/science/article/pii/S2210650225003979; QD-as-MOO reference https://arxiv.org/abs/2602.00478Motivates set-source-reference and Goldilocks docking into current C.18, C.19, G.5, G.9, G.11, A.6.P:7a, and C.16.Q.Adopted as field and relation cue; no local QD or OEE vocabulary or scalar readiness score is introduced.
Open-ended coding agents use archives, self-improvement, problem variants, evaluator feedback, and stepping-stone retention.Darwin Godel Machine https://arxiv.org/abs/2505.22954, FrontierSmith https://arxiv.org/abs/2605.14445, and AlphaEvolve https://arxiv.org/abs/2506.13131Contributes record-form, set-source reference, Goldilocks, safe-probe, and freshness fields and relation references for archive, problem generation, safe probes, evaluator feedback, no-change and abstain dispositions, and autonomy and evidence boundaries.Adapted as a recent trend cue.
Agentic action can require independent authorization and evidence.FPF E.16, A.21, A.10, G.6, B.3, A.15 and G.11Keeps the problem-side cue distinct from the applicable autonomy, gate, Work and reliance claims.Use the governing pattern only when that claim is current; a generated draft or tool trace supplies no missing authorization.

For a claim extending beyond these uses, obtain its support under the pattern that defines or tests that claim; the dispositions above supply no additional warrant.

The following questions connect the source contributions to decisions in the card. Use the row whose distinction is current:

Source or relation cueShortcut rejectedRequired local resultReopen condition
Problem framing is ambiguous and abstraction shifts matter.Symptom, root-cause story, request, or ticket is treated as the problem.Recover signal, framed problem representation, EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, and an improvement check or rival formulation when the current use needs them.Reopen when scheme, scope, viewpoint, rival formulation, evidence need, or improvement or acceptance probe changes.
P2W uses only a reviewable problem-side record.P2W-ready is treated as Work authorization, gate passage, method selection, evidence proof, assurance, or selected solution.State problem-formulation follow-up reason, validation boundary, readiness disposition, retained P2W use, blocked attempted use, and subject-pattern cue when an outside claim is current.Reopen when the signal, EntityOfConcern, ReferenceScheme, ClaimScope, acceptance probe, follow-up reason, validation boundary, freshness, or named outside claim changes.
QD, OEE, and set-return work produce archives, fronts, pools, and selected sets.A score or winner label substitutes for the source-set and selection basis.Preserve sourceSetRef, source set kind, selection or retention criterion, and a declared next use; apply the governing set, parity, archive, pool, or refresh pattern when current.Reopen when the source set, retention criterion, parity relation, archive, pool, front, selected set, budget, window, or freshness disposition changes.
Open-ended agents, problem variants, evaluator feedback, and stepping stones change signal interpretation.Generated output is accepted on its origin without examining its content and needed support.Recover what the source contributes to the claim or proposed continuation; retain adequate support and obtain validation, currentness or action-entry grounds still needed for that use.Reopen when the contributing content, its support or a condition of the proposed use changes.
First-principles or mathematical structure can improve formulation.Naming a formalism or using mathematical or ontological language is treated as sufficient for adequacy or rigor.Record the candidate structure, either its relation to the problem-side EntityOfConcern or the C.29 mathematical-lens-use relation, preserved and lost structure when current, practical formulation payoff, problem-formulation follow-up reason, and stop condition.Reopen when candidate structure, preserved or lost structure, problem-formulation follow-up reason, stop condition, or C.29 result changes.
Early class or kind taxonomy looks available.A class list or ontology-first taxonomy is treated as the problem formulation.Keep the formulation question current; record candidate structure, preserved and lost structure when current, and representation or retargeting relations before freezing kind structure.Reopen when formulation question, kind structure, relation, representation-transition relation, or retargeting relation changes.
Object model looks clarifying.Object-model clarity freezes the wrong EntityOfConcern or relation.Keep EntityOfConcern and relation reviewable; name representation-transition, retargeting, or bridge relation references before reusing a local cue or readiness disposition.Reopen when EntityOfConcern, relation, view, bridge relation, or representation-transition relation changes.

C.22.2:16 - Rationale

ProblemCard gives the practitioner one compact problem-side record between vague problem talk and downstream P2W. The card is useful because it is light enough for ordinary use and specific enough to show when comparison, characterization, evidence, selection, mathematical-lens use, method, work, gate, autonomy, bridge, representation transition, or refresh requires another FPF pattern.

The card gives the practitioner one thing to write, inspect, and challenge. A practitioner can see whether a problem is ready without first assembling the problem-side record from TaskSignature, Q-bundle, parity report, evidence note, selected-set output, and refresh record. Claims beyond the problem-side record stay with their subject patterns.

The archive and portfolio distinctions remain current when they matter because the card preserves sourceSetRef and names the subject pattern for any current set, archive, or portfolio claim. Changed problem formulations, diagrams, functional descriptions, or transformation-flow path interpretations require the accepted representation or retargeting relations before a local cue or readiness disposition is reused. Current SoTA and first-principles cues matter only when they change fields, relation references, boundaries, or the problem formulation itself.

C.22.2:17 - Problem-Card Use Invariants

InvariantRequirement
One card, one joint EntityOfConcernOne ProblemCard has one ClaimGraph, one independently identified EntityOfConcern, and one effective ReferenceScheme. Several PFR references may share the card only when one direct pattern identifies their joint concern; otherwise split the claims and card. C.22.2:20.1b illustrates three cases: one card for a joint concern, a forced split, and several cards for one PFR.
ProblemCard is not PFRThe card may assert, deny, forecast, describe, or discuss solvability, but only C.22.PFR establishes actual Problem obtaining and identity.
Claim families remain distinctActual-PFR assertion polarity, support and bounded reliance, G.11 currentness, anticipated-condition claims, and method-availability or solvability claims do not collapse.
P2W-ready is problem-side readinessThe card can be ready as input to P2W or C.22 without being ready for Work execution, gate passage, method selection, evidence reliance, or autonomy.
Constitution and qualification stay separateClaimGraph, one joint EntityOfConcern, and effective ReferenceScheme constitute the card. ClaimScope, assumptions, window, viewpoint, receiving use, and any A.15.6 Work reference stay in their claims and direct relations; no carrier, organization, or setting constitutes the card or PFR.
Claims outside C.22.2 stay outsideEvidence, assurance, gate, autonomy, Work, archive, selected-set, comparison, acceptance, representation, temporal, causal, and mathematical-lens claims remain with their governors.
Stale or blocked cards state a dispositionA stale, unknown-blocked, changed-representation, or missing-governor card states refresh, retirement, bounded use, abstainOrNoChange, or the exact relation reopened.

C.22.2:18 - Misuse Modes and Repairs

Misuse modeSymptomRepair
Card-as-executable-work requestA solution-shaped task or implementation request is treated as a problem-side record.Recover the signal, joint EntityOfConcern, effective ReferenceScheme, ClaimScope, claim family, reason this is not a preselected Work request, improvement check or acceptance probe when needed, and next use before applying a Work pattern.
Content creepThe card starts carrying claims outside the problem-side record.Keep only the cue or reference needed by the problem-side record and apply the pattern that defines or constrains the claim being made.
Hidden scalarizationGoldilocks, readiness, priority, OEE, QD, or indicator wording is reduced to a score without its declared characteristic, scale, scope and policy basis.Preserve source-set kind, selection or retention criterion, characteristic or Q-bundle relation, and declared next use.
Silent retargetingA changed EntityOfConcern, representation language, diagram, functional description, or transformation-flow path interpretation inherits old readiness by wording continuity.Name the representation-transition, retargeting, bridge, structural-reinterpretation, or wording-use relation before reuse.
Refresh dead endExpiry or unknown handling is recorded as a passive note.State refresh, retirement, bounded use, abstainOrNoChange, or the relation that is reopened.

C.22.2:19 - Use-Quality Checks

These checks protect the card’s practical use.

CheckQuality question
RecognitionCan the practitioner recognize the working situation before outside-governed relation material appears?
Thin affordanceCan the Thin contract in C.22.2:2.1 fit under one page when only its core items are current?
Next useDoes the card choose P2W-ready, characterize, compare, search, refresh, retire, archive, abstainOrNoChange, or the FPF pattern governing the named claim kind, relation kind, or boundary?
Record budgetAre heavier fields present only because they change the current move?
P2W exportDoes the card state what P2W may use now and which subject-pattern cues remain outside the card?

C.22.2:20 - Worked Slices and Anti-Cases

C.22.2:20.1 - Five-Case Worked Slices

These rows are recognition slices, not complete Thin cards. Before using one, complete the Thin contract in C.22.2:2.1; add the relation cues shown here only when they change that card’s next use. The compact filled Thin example follows in 20.1a.

CaseProblem-side signalRepaired card useBoundary preserved
AI and human task transfer reworkRepeated rework appears after transfer between human and agent.Stabilize signal, EntityOfConcern, effective ReferenceScheme, ClaimScope, acceptance probe, and safe-call or Work relation before another delegation.The card is not a prompt retry instruction and does not justify another delegation.
Musical mastery tempo driftPractice tempo drifts away from the intended mastery band.State the temporal claim, practice scheme and scope, acceptance probe, and C.27 relation when tempo, rhythm, recovery, or learning rate changes the next use.A trend line is not an intervention model or evidence of mastery.
Customer-service escalation after a policy or interface changeEscalation volume rises after the change.Stabilize affected customer hand-off, acceptance probe, risk boundary, measurement relation, and causal-use relation when that relation is being made.Escalation volume is not an automatic fix request, staffing plan, rollback order, or causal proof.
Literature-synthesis anomaly before method selectionAn anomaly does not fit current category labels.Preserve rival formulation, EntityOfConcern, evidence need, bridge, representation, or mathematical-lens relation when that relation is being made, and next discrimination action.The anomaly is not proof for a new theory or a selected research method.
Selected-set candidate before P2WA retained candidate from a front or pool looks promising.Preserve sourceSetRef, source-set kind, selection or retention criterion, declared next use, and only the currentness or window on which that use relies.Set membership is not selected-solution proof, priority score, or work authorization.

C.22.2:20.1a - Compact P2W-ready Disposition Slice

Consider a support team seeing repeated reopened hand-offs after a new interface policy. Its source episteme SupportHandoffPolicy-E7 contains the two clauses compared below. The incoming request says “rewrite the escalation workflow.” The card first identifies the concern and improvement probe; selecting a rewrite requires its own grounds.

The first-line entry uses “complete” when a case is sent. The specialist entry uses it when the case is accepted. Both events can be recorded correctly. The shared queue must decide when to remove an item from the sender’s list. For a case that has been sent but is still awaiting acceptance, the two readings give different decisions. The team can now ask which event authorizes that change. If the queue already distinguishes dispatch from acceptance and applies a single unambiguous rule, the two labels alone give no reason to revise it. The reopened cases still merit inquiry.

Card fieldFilled value
Source signalEscalations reopen after hand-off from first-line support to specialist support.
Problem-side EntityOfConcernThe identified source episteme SupportHandoffPolicy-E7, whose two clauses use the same completion label for different events.
Effective ReferenceScheme and ClaimScopeScheme: support-interface hand-off under the new policy edition. ClaimScope: SupportOps-EU.
Claim familyDescriptive claim about the two policy clauses and their different completion meanings. The prediction that reopened escalations will continue while this wording remains is an untested hypothesis, not an established forecast or causal result. No actual PFR is asserted.
Ground for addressing the concernFor a sent case still awaiting acceptance, the two readings disagree on whether it belongs in the sender’s queue. Identify which event governs removal. To establish who remains accountable for follow-up, consult the rule assigning that responsibility.
Improvement check or acceptance probeFor the pending case, establish which event the rule requires for removal from the sender’s list and check what the queue does before and after that event.
Next useCarry the two clause meanings and the queue question into E.18.1. Obtain the governing rule or refer the unresolved choice to the person authorized to settle it.
Qualification window (current here)Two-week incident window under the stated policy edition.
Problem-formulation follow-up reason (current here)Resolve which event the policy means by completion. Examine System, assignment, Method, Work or policy-boundary relations only if that clarification exposes a question that depends on them.
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 dispositionP2W-ready for resolving the queue rule. A sent case still awaiting acceptance lets the receiver check whether the shared queue follows the agreed removal rule.
Subject-pattern cues (current here)Use the applicable A.6 declaration or interface rule if completion semantics remains unresolved. Retain the direct grounds for a relied-on claim; use A.10 when its evidence or provenance needs a replayable account and G.11 when its currentness is at issue. Add A.2/A.2.1/A.13/A.15 for an actual classification, assignment or dated Work claim; F.6 only for precise assignment attribution, and A.21 only for a gate claim.

A claim that the service improved would need different evidence. To compare reopening rates, identify all eligible hand-offs in comparable periods, or use a sample that supports an estimate for them. For each period, determine which hand-offs reopened within the same follow-up time and compare their proportions, accounting for changes in the case mix that affect the comparison. Check the unresolved safety, compliance and customer-impact exceptions. Looking only at reopened cases can reveal how a hand-off went wrong. It leaves the reopening rate unknown.

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 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.

C.22.2:20.1b - Card/PFR Cardinality Replay

Every PFR reference below designates a world-side occurrence established under C.22.PFR; no card-side fact supplies its participants, adverse extent, or identity. PFR-InspectionAssignment-17 and later PFR-InspectionAssignment-18 are the two Robot-7 occurrences described in C.22.PFR:5.

For the unrelated branch, InspectionReleaseAssignment is a declared U.SystemRoleAssignment species. Occurrence InspectionAssignment-27 has admitted System Robot-8 as holder and local kind InspectorSystemRole as assigned-kind value. It obtains without interruption on [2026-07-13T10:00, 2026-07-13T10:30]; MaintenanceRoles-2026, Maintenance-Scheme-A, and the interval description interpret or describe the assertion but are not extra assignment participants.

Robot8ReleaseCriterionApplicability-4 uses predicate NoInspectorSystemRoleBeforeValidation-v2, maps the occurrence’s assigned-kind participant to the adverse nominal coordinate and its holder to Robot-8, and names Robot-8, its release ClaimScope, and [2026-07-13T09:30, 2026-07-13T12:00] as the other applicability participants. Those facts establish PFR-InspectionAssignment-27 on [2026-07-13T10:00, 2026-07-13T10:30] under C.22.PFR.

BranchExact card-side objectsResult
One joint multi-PFR cardRobot7ReleaseEpisodesCard-E1 = <CG-Robot7-ReleaseEpisodes-E1, Robot-7, Maintenance-Scheme-A>. The ClaimGraph contains two affirmative assertion nodes designating PFR-InspectionAssignment-17 and PFR-InspectionAssignment-18. A.1 independently identifies Robot-7 : U.System, and both PFRs have that same System as their applicability-derived problem-for entity.One ClaimGraph has one direct, joint EntityOfConcern, so one card carries both PFR references. The card records two occurrences; it does not merge them.
Unrelated PFRs force splitProposed CG-Mixed-RobotReleaseProblems-E0 contains PFR-InspectionAssignment-17 about A.1-identified Robot-7 and PFR-InspectionAssignment-27 about separately A.1-identified Robot-8. No direct pattern in this replay identifies one joint EntityOfConcern for those claims; a list of the two Systems is not one.E0 cannot constitute one ProblemCard. Split it into CG-Robot7-ReleaseProblem-E1 in Robot7ReleaseProblemCard-E1 and CG-Robot8-ReleaseProblem-E1 in Robot8ReleaseProblemCard-E1, each with its own exact System EntityOfConcern and effective scheme.
Several cards retain one PFRRobot7SafetyCard-E1 = <CG-Robot7-Safety-E1, Robot-7, RobotSafety-Scheme-A> qualifies its designation by SafetyAssuranceViewpoint-E1 and receiving use AutonomousInspectionReleaseReview-E1. Robot7StaffingCard-E1 = <CG-Robot7-Staffing-E1, Robot-7, MaintenancePlanning-Scheme-B> qualifies its designation by MaintenancePlanningViewpoint-E1 and receiving use InspectionAssignmentRepairPlanning-E1. Both ClaimGraphs designate PFR-InspectionAssignment-17.The differing ClaimGraphs, schemes, viewpoints, and receiving uses identify or qualify two cards and their claims; the PFR reference remains exactly PFR-InspectionAssignment-17. Revising, merging, splitting, publishing, or replacing either card changes no PFR participant or adverse episode.

C.22.2:20.2 - Anti-Cases

Anti-caseCorrect result
The card is cited as safety acceptance, gate passage, tool-call action invitation, or work authorization.Apply the pattern for the safety, gate, autonomy, work, evidence, provenance, or assurance claim; keep only the problem-side cue in the card.
A mathematical phrase is added because it sounds rigorous.Remove it unless a supported consequence improves the formulation. Use domain mathematics directly when adequate, and C.29 for a live representation or transfer question.
A source archive’s single-score “best” is used without its declared comparison or selection basis.Use the governing source-set and selected-set patterns; the card preserves the source-set reference, criterion, and problem-side next use, including any admissible scalar criterion or ranking and its limits.

C.22.2:21 - Machine-Assisted Drafting Boundary

Machine-assisted ProblemCard drafting is only a drafting aid. Before the draft is used for P2W or selector-facing work, a practitioner checks the card’s local fields and any subject-pattern cues for claims outside C.22.2.

Check the Thin content in §2.1 against the available source material. A machine-generated field value is a proposal until its claim is supported; the same record budget applies as for a human draft.

Check problem-formulation follow-up reason, validation boundary, freshness or expiry, unknown handling, source-set reference, representation or retargeting relation, and outside-pattern cues only when that content is current for the chosen next use. Omit a non-current field; do not invent a value or write unknown merely because the drafting aid exposes that field.

C.22.2:22 - First Practical Entry Aid

This section is a discoverability aid only. It helps a practitioner or assistant find a candidate pattern; it does not prescribe a transition sequence and does not require opening C.22.2 for every problem-sounding text.

These likely practitioner entry phrases point to C.22.2:

  • “We have a problem, but it is not yet clear what work should be done.”
  • “This looks like a ticket, but I am not sure the problem is stated.”
  • “A signal or anomaly keeps recurring before method selection.”
  • “We selected this candidate from a front, archive, pool, or selected set, but need to state why it is a problem now.”
  • “P2W would otherwise use ‘implement X’ as if it were reviewable problem-side output.”
  • “There is a symptom, but we do not yet know what to solve.”
  • “We need to know whether this problem is ready for P2W or should apply another pattern.”

Direct-entry cues that are not C.22.2:

  • accepted method or work planning: use A.15;
  • proof, provenance, reliability or assurance claim: use its direct subject rule; add A.10 for a needed replayable account, G.6 for a needed graph representation, or B.3 for a named assurance claim;
  • local choice among explicit options: use C.11; use G.5 when selector-facing set-result declaration is current; when that result already exists and actual audience availability is current, use E.17 for its source-backed publication face and return to source and E.24.PUB for the publication occurrence and availability;
  • agent tool-call, gate, or autonomy claim: use C.24, E.16, or A.21; ProblemCard may only name the problem-side cue or relation named by value;
  • ordinary discussion with no downstream receiving use: no C.22.2 use.

First-use Thin-card test:

Aim for a Thin card that fits on one page when only the core content is needed. Use 2.1 to recover: signal; one joint EntityOfConcern, effective ReferenceScheme, and ClaimScope; claim family; not-wish or not-preselected-Work reason; improvement check or acceptance probe when needed; and one governed next use.

That use may be P2W-ready, characterize, compare or parity, search or pool, refresh, retire, abstainOrNoChange, or apply the FPF pattern that defines or constrains the claim, relation, or boundary outside the card.

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;
  • claim family and polarity: actual-PFR assertion, anticipated-condition claim, method-availability or solvability claim, or another named direct claim;
  • the observation, need or constraint that warrants addressing the concern independently of a proposed solution;
  • improvement check or acceptance probe when needed, or the gap that prevents P2W-ready use;
  • one 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.

Choose the next pattern by the receiving question:

  • For P2W carry-through, use E.18.1 with the accepted problem-side distinctions.
  • For TaskSignature constitution and assignment, use C.22.
  • For selector-facing selected-set use, apply G.5 when that relation is current.
  • When the missing contribution is development of reusable material through feasible variations, use C.40; use C.18 to preserve the generation or archive account when needed.
  • For intended or performed Work, use A.15 only after its 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.

C.22.2:24 - Consequences

C.22.2:24.1 - Benefits

  • FPF gains a clear problem-side output for problematization as the input P2W can use.
  • P2W uses a typed problem-side record rather than a slogan, ticket-shaped wish, or preselected method.
  • A source-grounded formulation can expose that a requested rewrite, selected candidate or indicator change does not yet answer the concern. The next use can then seek the missing distinction, retain alternatives or stop before unnecessary work.
  • Current archive, pool, front, shortlist, set-return, parity, refresh, evidence, and C.29 patterns are reused instead of duplicated.
  • The positive use of mathematical and first-principles thinking is preserved: it can find missing structure, not only check already-written mathematics.
  • Characterization and parity are required when problem reviewability depends on them.
  • Representation-change relations are handled through named relation references rather than local proof inside the problem card.

C.22.2:24.2 - Costs of Use

  • A ProblemCard adds a small writing step before P2W. The cost is justified only when the signal is not yet reviewable before downstream use.
  • The practitioner keeps the card small: preserve the split between problem, task, method, work, and result; keep TaskSignature minimal; and add conditional fields only when their relation is current.
  • For problems emitted from archives, pools, fronts, selected sets, or portfolios, the practitioner preserves sourceSetRef or the set-source relation without turning the card into a portfolio, archive, selected-set, or work-planning carrier.
  • Keep source-local or ordinary domain wording when it supplies the needed meaning. Recover its governed object or relation only when that distinction changes the card or its next use.

C.22.2:25 - Relations

C.22.2:End

Referenced in the corpus

55 literal mentions in other sections. Read their context to establish the relation.