E.14:10 - Consequences
| Benefits | Trade-offs and mitigations |
|---|---|
| Human-first clarity. Readers see the Working-Model layer as the canonical publication form. Direct claims carry no assurance fields by default; selected assurance remains purpose-driven and below the claims. | Extra author discipline only when assurance is current. Declaring the required posture and writing a short grounding account takes effort; the authoring template and style guide keep that addition bounded. |
| Progressive assurance. Teams can start with the direct claim and add Mapping, Logical, Constructive, or Empirical support deliberately without changing the visible relation. | Risk of “forever-light.” Some models may remain weakly assured; formal maturity checks and assurance prompts show where risk warrants more support. |
| Layer hygiene. Order and time remain outside mereology; structural identity is neither overloaded nor diluted. | Split attention. Authors must learn to keep relation families distinct; mitigated by the Tell-Show-Show pedagogy across architectural patterns. |
| Spec cohesion. The same section order and safety subsections (Bias‑Annotation, Conformance Checklist) keep patterns comparable and auditable. | Tighter prose. Patterns grow by a few concise checks; mitigated by the canonical template. |
Quotable closer. “One layer to speak, four layers to justify—only when needed.”