FPF Reference

    A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.3 - Interpretive-view declaration laws (IV-0..IV-8)

    Preface node heading:a-19-declared-substrate-interpretive-view-4-3-interpretive-view-declaration-laws-iv-0-iv-8:33773

    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

    IV-0 - View-law docking is explicit. An ordinary interpretive reading keeps its declared substrate recoverable. An asserted epistemic viewing follows A.6.3; an asserted U.View additionally satisfies E.17.0 viewpoint conformance, as specified in §4.8.

    IV-1 - The EntityOfConcern is preserved. The interpretation continues to concern the declared substrate. In an A.6.3 epistemic viewing, the source and receiving epistemes preserve the same EntityOfConcern while their ClaimGraphs or ReferenceSchemes may differ. Changing that EntityOfConcern requires a separate retargeting account.

    IV-2 - The base substrate remains the semantic center. The interpretive view may foreground aspects of the base line, but it does not replace or repair the base substrate declaration. Substrate repair belongs back in A.19.SOURCE-SET-SPACE-SUBSTRATE.

    IV-3 - Source, set-result, and palette recoverability are mandatory. The current source set, any active set result drawn from it, and any active derived view or base palette must remain recoverable while the interpretive view is active.

    IV-4 - Interpretive qualifiers remain foregrounding devices only. OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote may be foregrounded, but they do not become the interpretive view's ontology and they do not silently change the base relation or posture.

    IV-5 - Thin interpretation and atlas interpretation are different profiles. Ordinary DeclaredSubstrateInterpretiveView is a complete admissible profile, not a placeholder. DeclaredSubstrateAtlasView is used only when the fuller composite inspection question is real.

    IV-6 - Atlas form requires a complete composite record. If atlas form is active, the view must keep the base substrate, the active source or set result, the relevant TypedSetViews, any cited spaces, any cited declared map refs, and any qualifiers explicit enough that the reader can recover why thin interpretation was not enough.

    IV-7 - Local specialization stays local. If TraditionAtlasView is used, it remains one G.2 specialization of DeclaredSubstrateAtlasView; it does not become the common head of the family.

    IV-8 - Admission is fail-closed. If the current line would change the EntityOfConcern, add new generic view law, repair the substrate, decide publication, or decide policy, it is not a conforming interpretive view here. Apply the pattern that governs that question instead of stretching the family.

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