SYSE.7:7 - Conformance Checklist

• One receiving engineering decision, its decision subject, and the decision Work are named.

• Every selected description has a source episteme and edition, claim content, EntityOfConcern, effective reference scheme, configuration or effectivity where material, modeled interval, and use.

• Actual Systems, intended referents, kinds, parts, configurations, and occurrences are not merged by name.

• Model purpose, assumptions, omissions, scale, units, tolerances, and interpretation are sufficient for the receiving decision.

• A U.View claim cites a viewpoint episteme and obtaining E.17.0 conformance; otherwise view stays ordinary source wording.

• Publication occurrence, form, carrier, rendering, and source episteme remain separate where their identities change reliance.

• Every material “trace” is resolved to a relation or marked as an unsupported correspondence.

• Cross-description comparison aligns or explicitly distinguishes subject, configuration, interval, reference scheme, scale, and tolerance.

• Claims about physical realization, benefit, safety, compliance, and acceptance use their own evidence; description consistency supplies only its stated comparison result.

• AI-generated, transformed, or summarized descriptions retain source provenance, subjects, check results, and reliance limits.

• The maintenance Agent, assignment, capability, authority, triggering observations, and refresh Work are stated for material entries.

• The returned account names contradictions, gaps, unsupported relations, accepted reliance limits, and the smallest decision or account to reopen.