E.14:2 - Problem Frame

Teams need one shared Working-Model to make decisions at speed. Historically this shared model either:

• drifts into jargon - different terms for one shared working-model value, slash-labels, partial overlaps; or
• calcifies into machinery - too formal for day-to-day design and review.

Both failure modes create friction between two audiences: (1) working users (engineers, programme managers, policy owners) who need a small, stable Working-Model text, and (2) assurance authors (ontologists, methodologists, auditors) who need to inspect the basis and limits of the Working-Model claims.

E.14 resolves the impasse by separating concerns:

• A Working-Model layer: curated kinds and relations expressed in plain terms, with simple human rules for using them.
• An Assurance stack beneath it — Mapping, Logical, Constructive, and Empirical when needed — that keeps arguments and accounts recoverable without crowding the Working-Model narrative.

This pattern dovetails with the framework’s unification stance (small Working-Model text, rigorous foundations) and with the constructional-mereology discipline that sum, set, and slice provide inspectable accounts of independently grounded assembly, collection, and aspect facts. Those forms do not create a relation occurrence or decide whole identity. The Kernel stays minimal and meta-only.