A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.2 - Minimal interpretive view declaration
Preface node
heading:a-19-declared-substrate-interpretive-view-4-2-minimal-interpretive-view-declaration:37713
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
A conforming interpretive view makes the following explicit:
- which interpretive-family head is active: ordinary
DeclaredSubstrateInterpretiveViewor fullerDeclaredSubstrateAtlasView; - which already-declared substrate-bearing basis it is reading: either the explicit substrate line or the declared source-set entry point or set-result entry point that keeps that substrate recoverable;
- which inspection question the view is answering;
- which source set or source sets must stay recoverable while the view is active;
- which active set result, if any, the current reading is using over that source set;
- which cited spaces and declared map refs, if any, the current reading depends on, and how they remain recoverable;
- which optional qualifiers are genuinely doing work in the current case;
- and any use boundary needed to distinguish this interpretation from a substrate revision, publication or policy decision.
The minimum ordinary interpretive view declaration is therefore:
- one declared substrate-bearing basis from
A.19.SOURCE-SET-SPACE-SUBSTRATE: either the explicit base substrate line or one declared source set or declared set result whose substrate remains recoverable with it; - one explicit inspection question;
- one recoverable active source-set basis, plus any active set result drawn from it when the reading uses one;
- any cited spaces, maps and applicable uncertainty or distortion qualifications remain recoverable.
These are content requirements. Existing prose or a model can supply them; a separate record or repeated boundary statement is unnecessary when the content and use are already clear.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)