fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 60285–60314

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:45:10 UTC

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 A.10, G.6, or B.3;
  • 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:

Given a messy signal, a practitioner can produce a Thin ProblemCard in under one page with the exact core from 2.1: signal; one joint EntityOfConcern, effective ReferenceScheme, and ClaimScope; exact claim family; not-wish or not-preselected-Work reason; improvement check or acceptance probe; and one honest 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.

Entry relation:

The entry relation is local: C.22.2 is introduced under C.22, and C.22 names the ProblemCard relation. The C.22.2 body carries the Problem frame, first-entry phrases, tempting-wrong-pattern boundaries, and first-use Thin-card test needed for ordinary discovery.