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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:25:14 UTC

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 useNot the card, TaskSignature, method, or Work request.
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 relianceExact output under C.16, C.2.1, A.10, G.6, B.3, G.11, or the direct result patternCan support a card claim but neither constitutes the card nor makes PFR obtain.

Use C.22 to prepare the TaskSignature from the exact problem-side episteme or ProblemProfile needed by one receiving use. Assert an assignment only when one TaskSignature is adequate for that use and C.22’s obtaining rule holds. If several profiles or signatures remain plausible, preserve candidates rather than asserting one assignment. When the question becomes selection, planning, performed Work, result, gate, evidence, or reliance, apply its governor instead of expanding the card.