A.2.3:12 - Didactic quick distinctions

• Promise content. A consumer-facing episteme stating the promised outcome, any eligibility predicate, effective reference scheme, claim scope, and acceptance specification; its optional accessSpec describes the access method.
• Method and method description. U.Method is the semantic way of doing. U.MethodDescription is an episteme describing that method; neither is delivery work.
• Delivery Work and affected subject. Follow the §4.3 route to identify the actual provider and admit the dated Work independently; add the separate F.6 check only if this use must also state the assignment under which the delivery was performed. Exact affected referents, pre-work and post-work states, and actual-change, production, delivery, or acceptance relations state what happened under their own governors. A mathematical Delta expression is optional and remains a separate lens for a named comparison.
• Evidence and evaluation. Evidence relations support delivery and satisfaction claims. A separately performed evaluation occurrence has an actual operation application with a declared result binding; any verdict episteme is separately constituted and governed.
• Provider and consumer participation. The promise-content fields typed by U.KindRef identify local provider and consumer system-role kinds. Assignment occurrences identify admitted holder Systems and assignment extents; their declared U.SystemRoleAssignment species define the participant meanings.
• Measures. U.Measure claims such as availability or lead-time readings derive from selected work facts through named characteristics, C.16 measurement templates, A.10 evidence relations, aggregation rules, and temporal policies; when a particular measurement method matters, its U.MethodDescription is cited.
• Structure boundary. Promise content is not a structural part. The systems that expose access or perform delivery retain their own parts, selected structures, and ArchitectureOf@Context relations.