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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:05:10 UTC

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.
  • C.22.2 has practical value for FPF when it reduces at least one expensive failure: a wish enters P2W as TaskSignature; a preselected work request is treated as the problem; method selection happens before the problem is reviewable; a problem from a set loses sourceSetRef; an indicator is used without a declared indicator-use relation; problem-formulation follow-up reason is cited as proof; a stale problem remains active; scalar readiness replaces set-return; or the problem-formulation follow-up reason is inherited across a changed representation without the governing representation-continuity or wording-use relation.
  • 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 no longer optional background when they are prerequisites for problem reviewability.
  • 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.
  • External or source-local terms may guide recognition only when they change a concrete boundary, field, relation, or validation requirement. Otherwise they remain examples or local cues.