#A.19.SOURCE-SET-SPACE-SUBSTRATE:2 - Problem

Preface node heading:a-19-source-set-space-substrate-2-problem:23800

#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

How should one declare a source-set and search/outcome-space line so that:

1. the declared source set remains explicit and recoverable;
2. SearchSpaceRef and OutcomeSpaceRef stay guarded refs to declared A.19 CharacteristicSpace, not new free-floating space kinds;
3. the text states whether those refs point to one declared space or to two distinct declared spaces;
4. the source-to-outcome relation is explicit enough for the reader to know which source-to-outcome relation mode is being claimed: mapped, projected, translated, scored, or otherwise connected;
5. distortion, uncertainty, and error are stated honestly rather than hidden in prose;
6. SourceSetComposition and DerivedViewKind remain conditional fields rather than fabricated mandatory baggage;
7. qualifier refs such as OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote remain available but substrate-side only;
8. and neighboring declarations such as A.19, C.18, G.5, G.10, and A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW can dock to the substrate without redefining it?

---

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