Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:35:15 UTC

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

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.Separate the interpretation from selector, publication and live-pool decisions; apply their governing patterns in §4.10.
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.