A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0.a - TERM/LEX token-status guard (local-first)
Preface node
heading:a-19-declared-substrate-interpretive-view-0-a-term-lex-token-status-guard-local-first:24875
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
Keep this token-status split explicit:
DeclaredSubstrateInterpretiveViewis the ordinary/common interpretive-view head introduced here for domain-specific reuse over one already-declared substrate-bearing basis: either the substrate line itself or one declared source set or declared set result that keeps the substrate recoverable.DeclaredSubstrateAtlasViewis the fuller specialization of that same family. It is not the common head and it is not automatically required.TypedSetViewsis one local plural field over already-declared set-view heads or ids. It is not a new generic set-result ontology.TraditionAtlasViewis one localG.2specialization ofDeclaredSubstrateAtlasView, not the family head for all interpretive-view use.OutcomeMapRef,SpaceMetricRef,TransitionRelationRef, andBridgeDistortionNoteare guarded neighboring refs or interpretive qualifiers reused here. This pattern may foreground them, but it does not mint them.inspection questionis one local declaration field naming the interpretive load the current reading helps with. It is not a replacement forU.Viewpoint.DerivedViewKindandBasePaletteRefstay local recoverability aids here; they do not silently turn the derived reading into the base ontology.
Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)