7. Where Detailed Conformance Belongs

The Use Case Guide uses conformance verbs such as SHALL, SHOULD, MAY, and SHALL NOT to define functional Actor behavior. The transaction-specific files define exact message headers, MIME/XDM packaging, SubmissionSet and DocumentEntry metadata, Task and payload elements, and element-level conformance designations such as R, O, RE/R2, R/X, and R/O.

Read this guidance as the bridge between the conceptual model and the transaction specifications: it explains how to apply the principles consistently, while the transaction modules specify the exact wire-level and artifact-level requirements.