A.7:10.1 - EntityOfConcern and publication-boundary consequences

Benefits	Trade‑offs / Mitigations
Category-error detection and correction. Clear separation of System and Episteme, `EntityOfConcern` and Description-episteme boundary, specification use or refinement, and publication availability helps expose recurring modeling defects.	Name publication face, form, unit, carrier, and rendering uses when the distinction matters; E.8 supplies publication-face guidance.
Audit and pedagogy align. References distinguish the evidence episteme, its target claim, a carrier, and any current source-currentness claim; Normative face houses checklists; Plain face teaches; Tech face types.	Slight increase in pattern length; offset by predictable navigation and machine-checkable CC.
Cross-context and plane safety. Faces expose an obtaining F.9 Bridge only for two exact local senses and keep its bounded-use claim and optional `CL` separate; cross-plane use exposes its applicable plane relation.	Authors must name only current relations and policies; tooling may assist, but no penalty follows automatically from context, plane, Bridge, or `CL`.