CONSEQUENCE-BEARERS — Find omitted Systems before closing a decision

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

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 has one plausible receiver, but the list may omit other physical or operational wholes that can change.
  • Question: Which other Systems may undergo a relevant change, through what supported relation or still-modal path, and what should the receiver do next?
  • First useful result or honest blocker: A bounded consequence account with its focus, bearers or intended referents, obtaining or modal paths, changed characteristics, support, uncertainty, and material limit. A useful constraint, alternative, or explicit unknown can complete the answer; further discovery needs a worthwhile obtainable contribution.
  • Mantra: Name the focus and receiver; trace obtaining relations and modal paths separately; challenge the boundary; recover real holons; qualify each change; keep the sides distinct; return the useful answer and its limit. Select further inquiry by its individual and combined contribution and burden.
  • Start with: A.1.CSD; use A.1.SCR only when a candidate's systemhood is load-bearing, and leave through the direct evidence, causality, comparison, domain, or value pattern only when that stronger question is current.
  • Stop or return: Stop at the smallest account that changes or holds open the named decision or investigation. Return when the focus, configuration, horizon, whole, relation support, bearer, observation, or receiving use changes.

Last Updated: 2026-09-08 — upstream FPF commit f6ee315e (github.com/ailev/FPF)