A.19.SOURCE-SET-SPACE-SUBSTRATE:0 - Use this when
Preface node
heading:a-19-source-set-space-substrate-0-use-this-when:24292
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
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
CharacteristicSpaceor to two distinct declaredCharacteristicSpacedeclarations; - 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
CharacteristicSpaceitself, with no source-set or source-to-outcome requirement; useA.19; - you are publishing selector or shipping metadata such as
SelectorOutcomeKind,SetResultFamily,HandoffKind, or public shortlist identity; useG.5orG.10; - you are building one interpretive view over an already-declared substrate; use
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWor a local specialization such asG.2; - you are deciding live pool policy, frontier retention, or next-move planning; use
C.19orC.24.
Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)