FPF Reference

    A.19.SOURCE-SET-SPACE-SUBSTRATE:1 - Problem frame

    Preface node heading:a-19-source-set-space-substrate-1-problem-frame:23787

    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

    In many search, synthesis, and source-set/space-substrate lines, the live substrate-bearing line is not just one CharacteristicSpace and not just one published shortlist or archive either. The line actually depends on a stack such as:

    • one declared source set, for example one front, archive, palette, or another declared source-set family;
    • one search-side reference to an A.19 CharacteristicSpace;
    • one outcome-side reference to an A.19 CharacteristicSpace;
    • one explicit SpaceRefRelationKind over those two references, stating whether they resolve to the same declared space or to two different declared spaces;
    • one relation from the source-side line into the outcome-side line;
    • and one declared posture about whether that relation is transparent, approximate, learned, lossy, uncertain, or otherwise qualified.

    Without an explicit substrate declaration for that stack, nearby declarations start carrying loads they are not meant to carry. A.19 gets stretched from space typing into source-set governance. C.18 descriptor maps start masquerading as the whole search space. G.5 and G.10 publication fields start reading like ontology. Interpretive views or atlas views drift into default meaning instead of staying optional derived help.

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)