FPF.Reference:5 - Local Closure Inside An Open World

Preface node heading:fpf-reference-5-local-closure-inside-an-open-world:1215

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

FPF assumes an open world. New evidence can arrive. A better mathematical model may appear. A source publication, source-use record, or telemetry relation may become stale. A competitor may change the state of the art. A user need may shift. A new concern may reveal that the same system should be described differently.

Engineering and management still need local closure: for a release, experiment, procurement, safety case or architecture review, establish what evidence and conditions are sufficient for the next action.

The open-world versus closed-world distinction provides a useful picture. Under open-world reasoning, absence of proof is not proof of absence. If a name is missing from a party guest list, the list may be incomplete. By contrast, a comparison can deliberately close over an accepted option set: an unlisted option is not compared in that bounded decision.

FPF supports local closure for declared purposes:

  • identify the source, scope, model-use organization, working situation, comparison basis or other subject-defined conditions needed for this decision;
  • name the project entity that the reasoning concerns: the EntityOfConcern;
  • state the proposed reliance and its conditions in the description;
  • qualify the claim’s support using the evidence and assurance required for the local use;
  • state the decision or gate result under its applicable rule;
  • state when the conclusion must be reconsidered.

FPF patterns use local closure to declare a scope for action while leaving the wider world open.

Before a method, route, or review makes an action mandatory, ask whether a materially plausible result can change a named substantive decision within the nearest substantive horizon, whether the action realizes an already selected result, or whether removing it changes an assurance or recovery condition on which the use relies.

This contribution is necessary but does not by itself make a proposed inquiry obtainable or worth requiring. Use A.11.OP for that screen and its boundary with direct duties and assurance. When the demand's worth remains open, C.11.DUA compares its attainable contribution and whole burden; a current local choice uses C.11. The result can be a qualified answer on the present basis.


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