FPF Reference

    A.19.SOURCE-SET-SPACE-SUBSTRATE:8 - Common Anti-Patterns and How to Avoid Them

    Preface node heading:a-19-source-set-space-substrate-8-common-anti-patterns-and-how-to-avoid-them:24176

    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

    Anti-patternWhy it failsRepair
    Treating one archive or front as the search space itselfA source set is not the same kind as one declared CharacteristicSpace.Keep SourceSetFamily and SearchSpaceRef separate.
    Leaving SpaceRefRelationKind implicitThe reader then has to guess whether search and outcome share one declared space or use two distinct declared spaces.Declare sameDeclaredSpaceAs or distinctDeclaredSpaceFrom next to the two refs.
    Letting DescriptorMapRef stand in for the whole substrateA representation layer is not identical to the position-typed space declaration.State the docking rule explicitly and keep the space refs visible.
    Making SourceSetComposition or DerivedViewKind mandatory in every lineThe line fabricates composition or derivation where none exists.Keep them conditional.
    Publishing with bare portfolio languageportfolio blurs retained-set, selected-set, and posture talk.Use declared source-set and outcome metadata instead.
    Treating all distortion as one bridge storyNot every qualified relation is bridge-mediated.State the active posture directly.
    Letting G.5 or G.10 sound like the substrate itselfPublication metadata then silently replaces substrate semantics.Keep publication as downstream use of the substrate.

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