fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 32874–32892

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:15:10 UTC

A.19.SOURCE-SET-SPACE-SUBSTRATE:0 - Use this when

Use this pattern when one working line depends on all of the following at once:

  • one declared source set still matters and must stay recoverable by name;
  • one search-side space reference and one outcome-side space reference must both be explicit;
  • the line must say whether those refs resolve to one declared CharacteristicSpace or to two distinct declared CharacteristicSpace declarations;
  • the source-to-outcome relation is load-bearing enough that the reader must know what is being related, in which direction, and through which declared carrier, declared map ref, or qualifier ref;
  • and distortion, uncertainty, or error cannot be left as vague atmosphere.

This is the right pattern for QD, OEE, archive/front, or adjacent synthesis lines when the problem is no longer only “what space exists?” and not yet “what shortlist or shipped result do we publish?”.

Not this pattern when:

  • you only need to declare or compare CharacteristicSpace itself, with no source-set or source-to-outcome requirement; use A.19;
  • you are publishing selector or shipping metadata such as SelectorOutcomeKind, SetResultFamily, HandoffKind, or public shortlist identity; use G.5 or G.10;
  • you are building one interpretive view over an already-declared substrate; use A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW or a local specialization such as G.2;
  • you are deciding live pool policy, frontier retention, or next-move planning; use C.19 or C.24.