FPF Reference

    A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0 - Use this when

    Preface node heading:a-19-declared-substrate-interpretive-view-0-use-this-when:33603

    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

    Use this pattern when one already-declared substrate from A.19.SOURCE-SET-SPACE-SUBSTRATE is already in force, and the current passage either cites that substrate directly or works through one declared source-set entry point or set-result entry point that keeps the substrate recoverable, but the reader still needs one interpretive view to see how the line should be read in practice.

    Typical indicators are:

    • the substrate is already declared, but one thinner interpretive view is still needed so the active source set, search-side space, outcome-side space, or distortion posture stays understandable;
    • one fuller atlas-form reading may help collect several typed set views, active set results, cited spaces, declared map refs, or interpretive qualifiers without changing the underlying substrate;
    • one derived tradition or palette view must stay recoverable as a view over a base palette rather than silently becoming the palette's default meaning;
    • or one line needs optional qualifier refs such as OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, or BridgeDistortionNote, but those pins must stay qualifiers rather than the semantic center.

    This is the right pattern when the working need is no longer "what substrate is declared?" and not yet "what shortlist, publication form, or shipped result do we emit?".

    Not this pattern when:

    • you still need to declare the substrate itself, including source-set and search/outcome-space roles; use A.19.SOURCE-SET-SPACE-SUBSTRATE;
    • you only need CharacteristicSpace, its slots, or its typing hooks; use A.19;
    • you are publishing selector outcomes, shortlist identity, or shipping metadata; use G.5 or G.10;
    • you are setting live pool policy, retained-set policy, or enactment/planning posture; use C.19 or C.24;
    • you are defining a new generic view law, viewpoint bundle, or publication-view family rather than one domain-specific interpretive reading; use A.6.3, E.17.0, E.17, or E.17.1;
    • the line would change the EntityOfConcern rather than preserve it; use A.6.4 or the appropriate retargeting pattern.

    A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0.1 - What goes wrong if missed

    If this pattern is missed, interpretive-view work usually fails in one of four ways:

    • the substrate is forced to carry every inspection question itself, so A.19.SOURCE-SET-SPACE-SUBSTRATE starts reading as if it also governed interpretive views, atlas readings, or palette interpretation;
    • the word view appears as one fresh local theory, detached from existing U.EpistemicViewing and U.MultiViewDescribing, so viewpoint, view, and publication face start collapsing again;
    • one atlas-form reading quietly becomes the default meaning of the whole family, so a fuller interpretive form starts redefining the base palette or base source set;
    • or qualifier refs such as OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote either disappear into vague prose or are promoted into mandatory core everywhere.

    The reader then cannot tell whether a visible interpretation is one optional interpretive view, one fuller atlas reading, one publication face, or one new semantic head.

    A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0.2 - What this buys

    This pattern buys one disciplined middle layer:

    • the substrate remains the semantic center;
    • thinner interpretive views remain admissible when a full atlas form is unnecessary;
    • DeclaredSubstrateAtlasView remains available as one fuller reusable specialization, but not as the default head;
    • derived palette or tradition views keep their base palette and base source sets recoverable;
    • active set results, cited spaces, declared map refs, and qualifiers stay recoverable when the current reading uses them;
    • and publication, shipping, and pool-policy questions stay outside the view.

    The practical payoff is simple: the reader can use one interpretive view to understand the declared line better without mistaking that interpretive view for the line's ontology, output, or policy.

    Last Updated: 2026-10-12 — upstream FPF commit f2bc67dd (github.com/ailev/FPF)