A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5 - Archetypal Grounding
Preface node
heading:a-19-declared-substrate-interpretive-view-5-archetypal-grounding:37871
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.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.1 - System
Tell. One QD archive has a declared substrate. A reader asks which candidates are neighbors of candidate p under its declared metric.
Show. In this constructed case, Archive-12 uses BehaviorCharacteristicSpace@ed=12 and ArchiveNeighborhoodMetric@ed=4. The declared neighborhood criterion is distance at most 0.3. Distances from p to q and r are 0.2 and 0.8 respectively. An ordinary DeclaredSubstrateInterpretiveView groups q with p and leaves r outside that neighborhood, showing the criterion alongside the grouping. The source Coordinates and metric remain recoverable.
Cash-out. The reader can recover why q is a neighbor and r is not. This grouping answers the inspection question; it does not itself select which candidates to retain. No fuller atlas is needed.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.2 - Episteme
Tell. One synthesis line already keeps a base SoTA palette and one derived tradition-facing reading. The reader now needs one fuller atlas-form interpretive view that keeps the base palette recoverable while showing how several tradition-facing views and cross-scale notes sit together.
Show. The active interpretive head is DeclaredSubstrateAtlasView. It reads one declared palette-facing substrate line whose source-set family remains TraditionPalette, whose active derived view remains TraditionFront, and whose base palette remains recoverable through SoTAPaletteDescriptionId. The cited spaces stay explicit as TraditionComparisonSpace@ed=3 and AdoptionOutcomeSpace@ed=2. The atlas reading keeps together the declared set views TraditionFront and TraditionArchive, the OutcomeMapRef value PaletteToAdoptionOutcomeMap@ed=1, the distortion note CrossTraditionComparisonLossNote@ed=1, and the local G.2 specialization TraditionAtlasView.
Cash-out. The reader follows a tradition profile from the palette into its front or archive view, then follows PaletteToAdoptionOutcomeMap@ed=1 to its conditional adoption outcome. The comparison-loss note stays beside comparisons that depend on it. These connections explain why the views are shown together; a front alone would hide the archive and its relation to the same palette. The atlas changes inspection, not membership of the base palette.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.3 - Boundary anti-case
Tell. One note starts from "atlas view" language, then quietly changes the base outcome posture and argues that only one shortlisted tradition should remain live.
Show. The changed-relation and retention claims need their own governing patterns.
Cash-out. Reopen the substrate if the base relation or posture changed. Use C.19 for the claim about which candidate traditions remain live; G.5 governs any declaration of a selector outcome.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.4 - Use-situation spread
Use the interpretive-view family this way across different working situations:
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)