FPF Reference

    PROBLEM-SHAPING - Turn early pressure into an honest problem-side result

    Preface node heading:problem-shaping-turn-early-pressure-into-an-honest-problem-side-result:530

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    • Situation and question. Something matters, but it may still be an early cue, a set of possible inquiry routes, an abductive question, or a problem ready for acceptance. Ask how far articulation has actually progressed.
    • Template A. A.16.1 Solution -> U.PreArticulationCuePack. Select when a cue nucleus and its witness or anchor should be preserved before a route or problem claim is stable.
    • Template B. B.4.1 Solution -> RoutedCueSet. Select when cue content is stable enough to publish route plurality or one selected route with explicit rationale, while no later endpoint is yet warranted.
    • Template C. B.5.2.0 Solution -> U.AbductivePrompt. Select when prompt species, open question, scope, and cue provenance are stable enough to seed abductive search.
    • Template D. C.22.2 Solution -> ProblemCard@Context. Select when the affected EntityOfConcern, constraints, unresolved relations, distinctions to preserve, and acceptance basis can be stated without smuggling in a selected solution.
    • Conditional continuation. When an accepted problem-side record must become usable by later eligibility, acceptance, or method-family selection, inspect C.22 Solution -> TaskSignature. The TaskSignature types only the current problem traits and receiving use; it does not select a method, issue a selector verdict, plan work, or prove that work occurred.
    • Boundaries. Stop at the earliest result that is both truthful and useful. Return or back off when the cue anchor, route rationale, prompt contrast, affected EntityOfConcern, constraint, or acceptance basis changes. Do not force a cue into a ProblemCard merely to make the work look started.
    • Result test. The selected branch can promise only the named U.PreArticulationCuePack, RoutedCueSet, U.AbductivePrompt, or ProblemCard@Context. Identify it under its direct Solution, then name the exact inquiry, acceptance evaluation or decision, or later method-family-selection object it would answer and the relation, binding, or supported claim that makes it this shaping use's result. TaskSignature is a continuation only when a later use needs typed problem traits; otherwise stop with the exact missing cue anchor, route, affected entity, acceptance basis, governor, or information.
    • Public coarsening. "Problem shaping" restores to the exact cue pack, routed cue set, abductive prompt, or accepted ProblemCard under its articulation condition.

    Last Updated: 2026-07-29 — upstream FPF commit 2ada4136 (github.com/ailev/FPF)