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 20:05:03 UTC

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:3 - Forces

ForceTension
Existing view law vs local usefulnessThe interpretive view must be useful in local substrate work, but it cannot invent a second view ontology beside A.6.3 and E.17.0.
Substrate stability vs interpretive helpReaders need one interpretive layer, but that interpretive layer must not redefine the substrate.
Thin interpretation vs atlas-form readingSome cases need only one light interpretive view; others genuinely need one fuller atlas-form reading. The pattern must admit both without making the fuller form default.
Recoverability vs convenienceDerived tradition or palette views help reading, but they must not hide the base palette, base source set, or active declared spaces.
Qualifier richness vs semantic inflationDeclared map refs, metrics, transition qualifiers, and distortion notes are often useful, but they must stay optional interpretive qualifiers rather than new mandatory core.
Readability vs downstream boundary disciplineThe interpretation should answer the inspection question while leaving selector outcomes, publication, live-pool policy and action planning to their governing patterns (§4.10).