E.14:1 - Intent

Establish a single, human-centric Working-Model that practitioners can read, discuss, and evolve without first reading the full assurance account. A direct Working-Model statement needs no assurance field simply because it is published. When a publication elects B.3.5 or another named current assurance requirement applies, the author declares the posture that requirement calls for and attaches only the needed assurance shoulders — Mapping, Logical, Constructive, or Empirical Validation. Under B.3.5, covered claims declare validationMode; covered structural claims also carry the profile’s constructive grounding. The posture and its supports justify or challenge the published claim; they create neither the chosen model value nor a world-side relation occurrence. A postulate remains a pragmatic working claim within its stated scope: the author should add brief empirical cues that would help later validation. Choosing it does not say that evaluation or measurement Work occurred or that a result exists. The complete Work, result, and provenance account enters only when evaluation or measurement actually occurred and the current assurance use relies on that result; another named current requirement keeps its own obligations. Assurance shoulders sit beneath the Working-Model and never define its vocabulary.

Put bluntly: one model people work in; three assurance shoulders — plus empirical checks when the world is the judge.