A.19.SOURCE-SET-SPACE-SUBSTRATE:1 - Problem frame
In many search, synthesis, and source-set/space-substrate lines, the substrate-bearing line is not just one CharacteristicSpace and not just one published shortlist or archive either. The line depends on a stack such as:
- one declared source set, such as a front, archive or palette, or a composition of identified source sets;
- one search-side reference to an
A.19CharacteristicSpace; - one outcome-side reference to an
A.19CharacteristicSpace; - one
SpaceRefRelationKindover 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 a 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.