A.19.SOURCE-SET-SPACE-SUBSTRATE:5.4 - Use-situation spread

Preface node heading:a-19-source-set-space-substrate-5-4-use-situation-spread:37464

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 the pattern this way across different working situations:

Working situationWhat to do with this patternWhat must stay explicitCommon miss avoided
Archive-side QD line where navigation and evaluation stay in one declared behavior spaceUse the shared-space profile. Recover the source basis, both space uses, their same-space relation, the source-to-outcome connection and its limitations; add descriptor/metric qualifiers when used.The archive as source set, both role-refs, the same declared space and applicable qualifications.Treating the archive or descriptor map as if it were the space itself.
Derived tradition/front line that is judged against one different outcome spaceUse the cross-space profile. Keep the derivation and base palette recoverable where the receiving use depends on them; add DerivedViewKind and BasePaletteRef when needed or required by its selected publication contract.The derived view stays derived, the needed base palette remains recoverable, and the cross-space relation stays explicit.Letting the visible front replace the base palette or hiding the adoption model's limitations.
Learned, adaptive, or uncertainty-bearing line where the space is declared but heavier qualification remains case-boundKeep the substrate core recoverable and state the uncertainty, adaptation or refresh conditions that affect the receiving use. Add a posture token when the selected interface requires it.The reader can distinguish the declared substrate from unresolved accuracy, applicability or stability claims.Pretending every case is either fully transparent or fully described by one metric specification.
Shortlist or publication note that only says what set result or publication form is shown or shippedDo not use this pattern. Apply G.5 or G.10.The note stays publication-facing instead of imitating substrate depth.Padding publication metadata with pseudo-substrate language.

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