FPF Reference

    A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.12 - Operator kit: choose, record, preserve, apply governing neighbor

    Preface node heading:a-19-declared-substrate-interpretive-view-4-12-operator-kit-choose-record-preserve-apply-governing-neighbor:25143

    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 compact kit whenever you need one interpretive view that can actually be used, checked, and bounded against neighboring patterns in practice.

    Decision pointWhat to do nowAdmissible resultStop or apply another pattern when...
    1. Which base line am I reading?Cite the base substrate or recoverable source-set entry point or set-result entry point.The interpretive view is anchored on one visible base line.The view still floats free of the line it is supposed to help read.
    2. What inspection question is this view answering?State the question directly in one sentence.The reader can tell what this view helps inspect.The view mostly repeats theory without naming the practical inspection load.
    3. Do I need thin interpretation or atlas interpretation?Choose ordinary DeclaredSubstrateInterpretiveView unless several views, spaces, declared map refs, or qualifiers must be held together at once.The interpretive head is chosen honestly.Atlas language appears by reflex, or thin interpretation would already solve the reading problem.
    4. Which source/result refs and qualifiers must stay recoverable?Keep the active source set, active set result, derived view, base palette, and cited qualifiers visible only when they truly do work.Recoverability stays proportional to the inspection question.The base palette or base source/result disappears behind the fullest visible overlay.
    5. Is the line still substrate-side only?Check whether the prose preserves the base substrate and its EntityOfConcern.The view remains one reading, not one rewrite of the underlying line.The prose is really changing the substrate, publishing outputs, or deciding policy.

    Use this compact interpretive view declaration when drafting or repairing the line:

    InterpretiveViewHead               = DeclaredSubstrateInterpretiveView | DeclaredSubstrateAtlasView
BaseSubstrateRef          = ...
InspectionQuestion           = ...
ActiveSourceSet       = ...
ActiveSetResult?         = ...
DerivedViewKind?          = ...
BasePaletteRef?           = ...
TypedSetViews?            = ...
CitedSpaceRefs?           = ...
InterpretiveQualifiers?        = ...
WhyThinIsEnough? /
WhyAtlasIsNeeded?         = ...

    Run this self-check before you leave the passage:

    • if the interpretive view would change the base relation or posture, reopen A.19.SOURCE-SET-SPACE-SUBSTRATE;
    • if the atlas-necessity line is empty, stay with thin interpretation;
    • if the next question under repair is naming repair, terminology precision, publication, or policy, apply [F.18](/generated/patterns/F.18), [A.6.P](/generated/patterns/A.6.P), [G.5](/generated/patterns/G.5), [G.10](/generated/patterns/G.10), [C.19](/generated/patterns/C.19), or [C.24](/generated/patterns/C.24) instead of stretching interpretive-view prose across those boundaries.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)