E.10:2 - Problem

1. Polysemy drift. Process, function, service, agent, activity slide between structure, recipe, execution, and promise.
2. Cross-local collision. A label such as Owner is assumed to have one global meaning even though distinct sources, practices, or schemes use it differently.
3. Name-bloat and parochialism tension. Either hyper-specific domain names leak into core kinds, or vague umbrella names obscure invariants.
4. EntityOfConcern and Description-episteme boundary and specification-use collapse. Authors mix EntityOfConcern (the thing under concern), Description episteme (how we describe it), and specification use (testable criteria, formality, acceptance, and harness-gated use of a Description episteme).
5. Register soup. Tech terms bleed into Plain pedagogy and vice‑versa, inviting category errors.