| First-minute use | A practitioner has an accepted ProblemCard@Context and the sentence “the cooling fixture violates the heat-flow invariant.” State the accepted card, carried claim, decision or use needing the answer, and next practical question in conversation. Add a compact note only when another person or later action must replay the path. Then name the pattern whose Solution answers the question and the result it must return, or state the stop. | Apply C.29 to the preserved structure, lost structure, payoff, declared use, and stop condition. A later formal-substrate declaration under A.6.0 is separate; neither continuation selects a method or writes evidence. |
| Diagram and approval note in the same source publication or source-use record | The same source publication contains a diagram, a test photo, and a manager note saying “approved.” Keep P2W focused on the claim carried from the accepted problem card. | Diagram cue, evidence-looking cue, and gate-looking cue are separated by relation recovery; conversational use or the compact note keeps only the carried claim and current direct relation. |
| Principle story without accepted problem-side record | A source has an inspiring principle story but no accepted ProblemCard@Context. | P2W stops before it begins; the source remains a reduced-use cue until C.22.2 or the problem-side pattern named by value accepts a problem-side record. |
| Acceptance claim with and without a current acceptance rule | For Fixture-42, the project-local predicate-definition episteme ThermalTestAcceptanceRelations defines when a named fixture is accepted under a named criterion set for a named campaign. Its ClaimContent says that Fixture-42 is accepted under CriterionSet-T7 for Campaign-T7. CriterionSet-T7 requires leak rate at most 0.5 mL/min and mounting offset at most 0.2 mm; current measurements are 0.3 mL/min and 0.1 mm, so the stated acceptance relation obtains and P2W carries the positive claim. In the earlier dashboard record, only a green accepted label exists, the offset was measured from the wrong reference plane, and no current rule defining acceptance can be recovered. | Apply that acceptance rule in the positive case. In the earlier case, return A.6.RCD missing-governor because no current pattern or project-local rule defines the claimed acceptance relation. Independently repair the measurement: if the correctly referenced measurement is unavailable, return missing-information; once current facts support applying the rule, carry its positive or negative result. The label establishes no acceptance, and C.25 does not define a universal acceptance rule. Any ownership, maintenance, responsibility, or authority claim remains separate and needs its own obtaining relation. |
| Changed unit after source-currentness repair | Later source-currentness repair changes only the unit and reference plane used by the planning constraint. | P2W reopens the smallest affected applications; the earlier dated U.Work occurrence is cited, not rewritten. |
| Clinical differential carried into care planning | An accepted problem card distinguishes an adverse treatment effect from progression of the underlying condition. Diagnostic-method choice, care planning, performed clinical work, and outcome interpretation all depend on retaining that distinction. | The practitioner applies the clinical DPF and direct work, evidence, and measurement patterns. The problem-side claim does not grant permission to treat; a changed observation reopens the diagnostic continuation before any dependent plan, permission, or work-entry relation. |
| Learning difficulty carried into teaching and assessment | An accepted problem card distinguishes missing recall from a wrong conceptual model. Teaching-method selection, session planning, performed teaching work, and later assessment depend on that distinction. | The selected educational method and A.15 work relations keep their own values. A lesson plan or completed session does not prove changed learner capability; an assessment that challenges the distinction reopens the smallest method or problem continuation. |
| Near-sameness under a formal declaration | A mathematical near-sameness claim preserves heat-flow structure but loses deformation factors outside the model. | The practitioner applies C.29 for mathematical-lens use. Apply A.6.0 separately only when the signature’s subject, ranged value, and FormalSubstrate profile can be named; otherwise keep the signature wording as a stopped cue. P2W preserves the accepted claim across those continuations without settling empirical truth or granting permission to start work. |
| FPF relation rule changes after a P2W use | Reapply the exact guidance recorded for the earlier use and re-evaluate the independently identified relation result under its own predicate or test and current facts. When relation-occurrence identity is current, apply A.6.REL only after that judgement. If the result changed and a later continuation relied on it, record the changed result, what still follows, what no longer follows, and the smallest continuation to reopen. | The earlier use is replayed rather than trusted by age; only the changed relation and dependent continuation reopen. |
| Relation selection would over-select from one phrase | A source says “the new port contract proves integration readiness.” P2W splits module-interface relation, E.18 transformation-flow relation, a dated U.Work occurrence, evidence cue, gate cue, and architecture-description cue. | Only the relation that changes the P2W application being made is written; the remaining readings stop as named cues until their relations and participants are stated. |
| Formal claim loses payoff | A U.Signature(profile=FormalSubstrate) declaration preserves a neat invariant, but no practical payoff or downstream stop condition can be stated for the accepted problem-side record. | The mathematical phrase lowers to a reduced-use cue; P2W does not justify method selection, evidence, gate, or A.15.2 planning from mathematical prestige alone. |
| Result source-use relation becomes stale | A result-looking source-use relation or publication cue is later replaced by a fresher source-use relation with a different artifact reference and measurement reference. | The practitioner applies A.15.4 appearance-based reliance repair before continuing P2W; stale result wording cannot continue as evidence, acceptance, or quality evaluation. |