A.19.SOURCE-SET-SPACE-SUBSTRATE:5 - Archetypal Grounding

Preface node heading:a-19-source-set-space-substrate-5-archetypal-grounding:37407

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

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.1 - System

One QD line keeps saying that one archive is both the search-side role and the evaluation basis. Downstream readers need to see that the same declared CharacteristicSpace can still occupy two different role positions without turning the archive or the descriptor map into the space itself.

In this constructed case, Archive-12 is the selected candidate set. The declared descriptor map assigns behavior Coordinates to its members; the separately declared neighborhood metric is used to assess coverage in that same behavior space.

SourceSetFamily       = Archive
SourceSetRef          = Archive-12
SearchSpaceRef          = BehaviorCharacteristicSpace@ed=12
OutcomeSpaceRef         = BehaviorCharacteristicSpace@ed=12
SpaceRefRelationKind    = sameDeclaredSpaceAs
SourceToOutcomeRelation = QDDescriptorMap@ed=9 assigns each Archive-12 candidate
                          its Coordinates in BehaviorCharacteristicSpace@ed=12;
                          a coverage comparison uses ArchiveNeighborhoodMetric@ed=4
                          on those Coordinates
DistortionPosture       = metric/model-dependent; descriptor realization and
                          neighborhood metric qualifier are active
DescriptorMapRef        = QDDescriptorMap@ed=9
DistanceDefRef          = ArchiveNeighborhoodDistance@ed=4
SpaceMetricRef          = ArchiveNeighborhoodMetric@ed=4

The archive supplies the candidate members; both space references resolve to the same declared CharacteristicSpace. The descriptor map assigns Coordinates, and the distance and metric define the stated coverage comparison. Selection or archive maintenance can reuse these relations while keeping the archive distinct from the space.

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.2 - Episteme

One synthesis line presents one derived tradition front and then starts speaking as if the visible front were the default meaning of the whole palette.

SourceSetFamily        = Front
DerivedViewKind        = TraditionFront
BasePaletteRef         = SoTAPaletteDescriptionId
SearchSpaceRef         = TraditionComparisonSpace@ed=3
OutcomeSpaceRef        = AdoptionOutcomeSpace@ed=2
SpaceRefRelationKind   = distinctDeclaredSpaceFrom
SourceToOutcomeRelation = for each retained tradition profile, AdoptionEstimate@ed=1
                          uses its integration requirements and the named team's
                          capability and workload facts to estimate adoption cost
                          and expected benefit in AdoptionOutcomeSpace@ed=2
DistortionPosture      = metric/model-dependent; the estimate is conditional on those
                         team and workload facts and omits unmodelled adoption effects

The visible front stays a derived view over the recoverable palette. AdoptionEstimate@ed=1 supplies the stated conditional source-to-outcome mapping. A later interpretive or atlas view may reorganize the presentation while preserving that mapping and its model limitations.

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.3 - Boundary anti-case

One note says only that "the shortlist front is the published result for the current selector result" and names no source-to-outcome relation, no search-side space, no outcome-side space, and no posture.

This is not a substrate declaration. It is publication metadata over one already-selected set.

Apply G.5 or G.10 to that note.

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

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)