FPF Reference

    A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.4 - Use-situation spread

    Preface node heading:a-19-declared-substrate-interpretive-view-5-4-use-situation-spread:25216

    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 the interpretive-view family this way across different working situations:

    Working situationChooseWhat must stay explicitCommon miss avoided
    Archive-side QD line that only needs one metric cue so the reader can see local neighborhoodsThin interpretationOne base substrate, one inspection question, one active source set, and the specific metric qualifier doing work.Forcing atlas form into a case that only needs one simple reading aid.
    Palette-first synthesis line that really needs several declared views, spaces, declared map refs, and loss notes held togetherAtlas interpretation, with G.2 when the case is tradition-facingThe base palette, derived view, cited spaces, qualifying map-ref/distortion refs, and the reason thin interpretation is insufficient.Letting the most salient visible atlas overlay replace the palette-first base line.
    Derived tradition/front note that only needs to remind the reader how to read one already-declared substrateThin interpretationThe inspection question, derived-view recoverability, and the base palette when it would otherwise disappear.Treating every derived tradition reading as if it were already full atlas work.
    Passage that starts changing the outcome posture, survivor set, or publication resultDo not use this patternThe boundary out to substrate repair, publication, or policy stays explicit.Smuggling retargeting or policy decisions into interpretive-view prose.

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