A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4 - Solution
Declare interpretive views as substrate-side only readings over one already-declared substrate-bearing basis, keep them explicitly under existing view law, and reserve atlas form for the cases that truly need it.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.1 - Declared-substrate interpretive-view record and outside work
Use this pattern to declare:
- one
DeclaredSubstrateInterpretiveView, the ordinary/common head of this interpretive-view family; - one substrate-side only reading over one already-declared substrate-bearing basis: either one explicit
A.19.SOURCE-SET-SPACE-SUBSTRATEline or one already-declared source set or declared set result whose declared spaces, declared map refs, and qualifiers remain recoverable through such a line; - the inspection question that makes this view worth showing;
- the recoverable source set or source sets that the interpretive view is reading;
- any active set result, derived view, or base palette that the current reading keeps in play;
- any cited spaces or declared map refs that the current reading depends on, provided those remain recoverable through declared refs or the cited substrate-bearing line;
- and any optional qualifiers that the current view genuinely needs.
DeclaredSubstrateAtlasView is one fuller specialization inside that same family. It is not the common head.
Do not use this pattern to declare:
CharacteristicSpaceitself;- the substrate role/relation stack from
A.19.SOURCE-SET-SPACE-SUBSTRATE; - selector outcomes, shortlist heads, or shipping outputs;
- live pool policy or enactment policy;
- or a new generic law for views, viewpoints, or publication faces.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.2 - Minimal interpretive view declaration
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.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.3 - Interpretive-view declaration laws (IV-0..IV-8)
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 - Distinguish substrate and view qualifications.
The view may foreground the substrate’s OutcomeMapRef, SpaceMetricRef, TransitionRelationRef or BridgeDistortionNote. It may also introduce a qualification of its own representation. State which relation a qualification concerns; changing the underlying source-to-outcome relation requires revising its substrate declaration.
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 for the reader to recover how those parts answer the inspection question.
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.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.4 - Profiles
Use one of these profiles explicitly:
- Thin-interpretation profile.
Use ordinary
DeclaredSubstrateInterpretiveViewwhen a direct explanation answers the inspection question. The number of cited references alone does not require atlas form. - Atlas-interpretation profile.
Use
DeclaredSubstrateAtlasViewwhen answering the question requires showing how several declared views, spaces, maps or qualifications relate within the same substrate.
If neither profile can be chosen honestly, the line is not ready as interpretive-view text.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.5 - Operational declaration sequence (fail-closed)
When declaring one interpretive view, proceed in this order:
- Entry test. Confirm that one already-declared substrate exists and that the current inspection question can cite it either directly or through one declared source-set entry point or set-result entry point that keeps it recoverable, rather than drifting into substrate repair, publication, or policy.
- Name the active interpretive head. Use ordinary
DeclaredSubstrateInterpretiveViewunless the current reading genuinely needs the fuller atlas form. - Cite the base line. Name the already-declared substrate the view is reading, or cite the source-set entry point or set-result entry point together with the recoverable substrate it depends on.
- State the inspection question directly. Say what the view helps the reader see that the substrate alone leaves hard to inspect.
- Keep the base source/result recoverable. Name the active source set, and if the view is over one declared front, archive, shortlist, palette, or other set result drawn from that source, keep that active set result recoverable too.
- Recover derived-view and palette structure when it matters. If the view depends on one derived tradition or palette reading, state
DerivedViewKindandBasePaletteRef. - Add the actual qualifiers. Add
TypedSetViews, cited spaces, declared map refs, metrics, transition qualifiers, or distortion notes only when the current reading truly depends on them. - Run the preservation check. If the interpretive prose would materially change the base source-to-outcome relation or the base distortion/uncertainty/error posture, stop and reopen the substrate declaration.
- Run the boundary check. If the prose starts changing the EntityOfConcern, minting new generic view law, publishing selected sets, shipping outputs, or deciding policy, apply the pattern that governs that question.
Incomplete declaration. Missing base recovery or an unresolved change to the underlying relation prevents the dependent interpretive-view claim. Preserve independently established content and resolve the missing basis. Split out any separate publication or policy decision and apply its governing pattern.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.6 - Thin interpretation remains a complete admissible form
Many cases need one interpretive view but not one atlas-form interpretation package.
Use thin interpretation when a direct explanation answers the inspection question, including when it cites a needed metric, map, transition or loss qualification.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.7 - Atlas form is fuller interpretation and needs a complete record
Use DeclaredSubstrateAtlasView when the inspection question requires showing how several declared views, spaces, maps or qualifications relate within the same substrate.
The minimal admissible atlas-form interpretation declaration therefore contains:
- the cited base substrate or source-set entry point or set-result entry point;
- the active source set and any active set result drawn from it;
TypedSetViewswhen several declared set views are being held together;- any cited
SearchSpaceRef,OutcomeSpaceRef, or other declared space refs that the atlas reading depends on; - any cited
OutcomeMapRef,SpaceMetricRef,TransitionRelationRef, orBridgeDistortionNotethat materially disciplines the reading; DerivedViewKindandBasePaletteRefwhenever the atlas reading is over one derived palette or tradition view;- the connections among these parts needed to answer the inspection question.
If the available basis cannot support the composite interpretation, retain what is established and state the missing basis. Use thin interpretation only if it still answers the inspection question; otherwise leave that question unresolved and use the pattern governing the missing basis if further work is needed.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.8 - No autonomous local view law is introduced here
Start with the declared substrate and the inspection question. An ordinary interpretation can stop with a recoverable explanation. When the use claims an A.6.3 epistemic viewing, identify the source episteme X whose ClaimGraph describes that substrate and the receiving episteme Y produced by the stated projection or re-expression. Both retain the same EntityOfConcern; state the transformed ClaimGraph and any changed ReferenceScheme explicitly.
Qualify Y as an E.17.0 U.View only when it independently conforms to the named U.Viewpoint for that concern. A return to A.6.3 alone does not establish viewpoint conformance. Keep the viewpoint, the view episteme and any E.17 publication face separate. A different EntityOfConcern requires the applicable retargeting account; changing or repairing the substrate returns to A.19.SOURCE-SET-SPACE-SUBSTRATE.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.9 - Qualifier refs stay substrate-side
OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote are admitted here only as interpretive qualifiers.
Qualifiers of the source-to-outcome relation are declared with the substrate and reused here. Qualifiers of the view itself belong to its representation account; for example, rounding displayed Coordinates can lose distinctions while the underlying Coordinates and map remain unchanged.
Use them when the current interpretive view genuinely needs them:
OutcomeMapRefwhen the current reading must show how one declared source or set result bears on one outcome-side declared space/ref;SpaceMetricRefwhen neighborhood, spread, reachability, or crowding claims are load-bearing in the current reading;TransitionRelationRefwhen the current reading depends on explicit transition or cross-scale state-change qualifier;BridgeDistortionNotewhen the reader must keep one declared loss or distortion visible near the current reading.
If a new loss, uncertainty or other qualification changes the underlying source-to-outcome relation, revise the substrate declaration and recheck dependent uses. Reuse unaffected content. A view-only qualification does not by itself change that relation.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.10 - Publication, set-result, and pool-policy boundaries
This pattern does not publish selected sets, declare shortlist heads, or decide which candidate lines stay live.
Keep the split explicit:
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWhelps the reader inspect one already-declared substrate;G.5declares selector outcomes and their source/publication metadata;G.10ships a Part-G SoTA pack with its publication faces and pins;C.19governs live candidate-pool and frontier policy;C.24plans tool or service calls after the action is fixed;E.24.PUBgoverns making an exact view or episteme available to an audience.
Other planning and enactment questions belong to the pattern governing the action. If the prose starts deciding who survives, what is published, or what is shipped, it has already left this pattern.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.11 - G.2 keeps the tradition-facing atlas specialization
When the current interpretive view is tradition-facing and palette-first recoverability matters, use the local specialization governed by G.2.
Read the relation this way:
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWstates the generic interpretive-view family and the generic fuller atlas formDeclaredSubstrateAtlasView;G.2keeps the palette-first, tradition-facing specializationTraditionAtlasView;TraditionAtlasViewis therefore one local specialization of the fuller atlas form, not the common head of the whole interpretive family.
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.13 - Using the interpretive view with neighboring patterns
Once the interpretation is sufficient, stop. Select a neighboring pattern only for a remaining question:
- Use
G.2when the interpretive view becomes palette-first, tradition-facing atlas work. That is one local specialization of atlas interpretation, not the common family head. - Use
F.18when the question under repair is label choice around interpretive-view, atlas, palette, or declared-map-ref language. Naming notes may explain the labels, but they do not change the base substrate or the inspection question. - Use
A.6.Pwhen one passage collapses view, surface, space, map, or palette into one umbrella word. Repair the layer split first, then continue. - Use
A.0when cold-reader glossing is what the current line lacks. Glosses help recognition; they do not replace the base interpretive view declaration. - Use the corresponding pattern in §4.10 when the remaining question concerns selector outcomes, shipping, publication, live-pool policy or action planning.
If a neighboring passage would change the EntityOfConcern or the base substrate posture, this pattern is no longer the governing pattern for that sentence. Reopen the base line or apply the pattern that governs the new question.