FPF Reference

    A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:8 - Common Anti-Patterns and How to Avoid Them

    Preface node heading:a-19-declared-substrate-interpretive-view-8-common-anti-patterns-and-how-to-avoid-them:25253

    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

    Anti-patternWhy it failsRepair
    Writing as if A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW were a fresh autonomous theory of viewsIt duplicates existing A.6.3 and E.17.0 law and collapses U.Viewpoint, U.View, and publication-face discipline.State the docking to existing view law explicitly.
    Letting atlas language become the default meaning of every interpretive caseThe fullest visible interpretive form silently becomes the family head.Keep ordinary thinner interpretive views admissible and say when atlas form is actually needed.
    Treating qualifier refs as the view's semantic centerMetrics, transitions, or distortion notes then replace the base substrate.Keep the base substrate and inspection question explicit, and keep qualifier refs optional.
    Letting a derived tradition view replace its base paletteThe reader loses palette-first recoverability and mistakes one local interpretation for the default ontology.Keep DerivedViewKind and BasePaletteRef visible together.
    Turning the interpretive view into publication or pool policyThe reader can no longer tell whether the text is helping interpret the line or deciding what survives and gets published.Keep G.5, G.10, C.19, and C.24 outside this pattern.
    Forcing atlas form into every first readingSimple cases become over-typed and harder to use.Start with the thinner interpretive-view form and widen only when the current need genuinely requires it.

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