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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:40:09 UTC

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.