FPF Reference

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

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

    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

    Tell. 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 layer into the space itself.

    Show.

    SourceSetFamily       = Archive
SearchSpaceRef          = BehaviorCharacteristicSpace@ed=12
OutcomeSpaceRef         = BehaviorCharacteristicSpace@ed=12
SpaceRefRelationKind    = sameDeclaredSpaceAs
SourceToOutcomeRelation = archive-retained candidates are navigated and judged
                          for local coverage gain in the same declared behavior
                          space
DistortionPosture       = metric/model-dependent; descriptor realization and
                          neighborhood metric qualifier are active
DescriptorMapRef        = QDDescriptorMap@ed=9
DistanceDefRef          = ArchiveNeighborhoodDistance@ed=4
SpaceMetricRef          = ArchiveNeighborhoodMetric@ed=4

    Cash-out. This line now says three distinct things cleanly: the active source set is one archive, both role-refs resolve to the same declared CharacteristicSpace, and the DescriptorMapRef plus DistanceDefRef are only interpretive layers over that shared space reference. A downstream selection or archive-maintenance discussion can reuse this line without pretending the archive itself is the space.

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

    Tell. 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.

    Show.

    SourceSetFamily       = Front
DerivedViewKind         = TraditionFront
BasePaletteRef          = SoTAPaletteDescriptionId
SearchSpaceRef          = TraditionComparisonSpace@ed=3
OutcomeSpaceRef         = AdoptionOutcomeSpace@ed=2
SpaceRefRelationKind    = distinctDeclaredSpaceFrom
SourceToOutcomeRelation = the visible tradition front is one derived reading
                          over the base palette and is compared against the
                          declared adoption outcome space through one explicit
                          cross-tradition outcome-bearing line
DistortionPosture       = lossy-bridge; derived-view selection and bridge-loss
                          notes must stay visible
BridgeDistortionNote    = CrossTraditionComparisonLossNote@ed=1

    Cash-out. The visible front stays a derived view over the palette, the base palette stays recoverable, and the outcome-side evaluation line stays explicit. A later interpretive view or atlas view may reorganize this story, but it may not silently change the declared source-to-outcome relation or erase the bridge-loss warning.

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

    Tell. 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.

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

    Cash-out. Apply G.5 or G.10 to that note. Do not pad it with pseudo-substrate words just to make it look deeper than it is.

    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. Fill the six core fields, then add descriptor/metric qualifier only if active.Archive as source set, both role-refs, sameDeclaredSpaceAs, and the active posture.Treating the archive or descriptor layer as if it were the space itself.
    Derived tradition/front line that is judged against one different outcome spaceUse the cross-space profile and keep DerivedViewKind plus BasePaletteRef visible.The derived view stays derived, the base palette stays recoverable, and the cross-space relation stays explicit.Letting the visible front replace the base palette or hiding the bridge-loss posture.
    Learned, adaptive, or uncertainty-bearing line where the space declaration is real but heavier qualification is still case-boundKeep the substrate core explicit and choose the honest posture token such as uncertainty-bearing, learned/adaptive, or unstable-under-refresh.The reader can see that the substrate is real without being promised fake geometric closure.Pretending every serious case is either fully transparent or fully described by one metric stack.
    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 directly.The note stays publication-facing instead of imitating substrate depth.Padding publication metadata with pseudo-substrate language.

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