RESULT-TO-NEXT-MOVE — Route an obtained result to the next probe or option
Preface node
heading:result-to-next-move-route-an-obtained-result-to-the-next-probe-or-option:583
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: A DPF or project calls something information gain, learning progress, or novelty, or has articulated a result from an earlier cue, and wants to use it to choose the next probe or option.
- Question: What result actually exists, and which downstream question, if any, is current?
- First useful result or honest blocker: The direct result plus the first needed reliance disposition, characterization, possibility-space claim, configuration-relative comparison,
ChoiceResult, or missing basis. - Mantra: Name the result; split ambiguous learning claims; keep each with its direct pattern. Move only to the current question: relied-on evidence, characterization or possibility space, realizable configuration comparison, or live choice. Stop when the present question is answered.
- Start with: Use
E.10.LRNonly to recover a result hidden by learning; otherwise its direct pattern. Then useA.10only for actual reliance,C.17/C.18only for characterization/space change,C.11.CRConly for a missing finite configuration comparison, andC.11only for a live choice. - Stop or return: Stop before every non-current question. Observations, objectives, and characterizations retain their identities. Route the result articulated from a cue through its direct pattern; if its
A.16.1cue pack remains current as a source or provenance, retain it separately.
Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)