SIE.9:4.1 - Pattern-Use Unfolding

Name the receiver interaction. State who or what asks, the query/message/report action, timing, input parameters, and the next Work or decision that consumes the answer.
Select the interface form. Choose query, view, API, message, schema, report, file, or mixed human/machine form based on the receiving Work. Do not inherit the internal realization shape automatically.
Define semantic inputs. State required identifiers, schemes, configuration/effectivity, time windows, units, locale or code context, permissions, and validation of requests.
Define result claims and interpretation. For each output, state meaning, grain, scope, interval/effectivity, units/codes, source identifier behavior, accepted loss, and permitted use.
Expose qualified branches. Represent matched/qualified, unmatched, incompatible, unresolved identity, source-qualified conflict, non-comparability, stale, inaccessible, timeout/source error, and partial result where applicable.
Expose provenance and currentness. Provide source/edition or a stable reference, observation/retrieval time, mapping/composition rule version, derivation/trace reference, and freshness status needed by the receiver.
State access, protection, and authority assumptions. Explain what the interface verifies, what the caller supplies, what may be disclosed, and which actions remain unauthorized by the semantic result.
Provide challenge and return paths. A receiver must be able to identify the source, correspondence, identity, composition, mapping, or operational result that owns a defect or unresolved branch.
Bind service behavior without claiming it. State latency, availability, pagination/volume, ordering, idempotence or snapshot expectations only where semantic use depends on them; obtain implementation/operation evidence separately.
Define conformance and reopen. Give representative requests, responses, error branches, compatibility conditions, deprecation/change behavior, and observations that reopen the interface.