CONSEQUENCE-BEARERS — Find omitted Systems before closing a decision

Preface node heading:consequence-bearers-find-omitted-systems-before-closing-a-decision:752

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 change may reach a System outside the project, or someone needs to know how far an existing finding extends.
  • Question: Which Systems may be affected, and does the recipient need one possibility, the complete set within stated bounds, or a decision about several Systems together?
  • First useful result or blocker: A qualified finding the recipient can use. A supported possibility may justify retaining an alternative. A rule that decides inclusion for the entire domain can establish a complete class or an empty list. To return a named list, recover its members’ identities. A bound on joint demand may settle a shared limit. State what remains open.
  • Start with: Use A.1.CSD to recover the focus, decision, criterion and intended scope. Vary the surrounding use and the distribution of a reported total. Keep established relations, possible paths and actual changes distinguishable. Use A.1.SCR for a material question of systemhood and the direct domain method for any needed measurement, comparison or causal claim.
  • Stop or return: Return a useful account with its material limit; it may change or hold open the named decision or investigation. Reopen when the focus, configuration, horizon, whole, relation support, bearer, observation, or receiving use changes.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)