Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-10-14 19:58:00 UTC · snapshot created 2026-10-14 19:58:38 UTC · last check 2026-10-15 05:30:05 UTC

E.4.CM:4.8.7 - Conformance Checklist

Recognition and assurance answer different questions. First identify the missing result and a plausible contribution. Then check only the claims on which the actual use relies, with the evidence and independence that their conclusion needs. Do not treat finding the right heading, obtaining a graph path or reading all patterns as assurance.

For a production result, ask whether the receiving action and stop are recoverable; whether sources and candidate evidence retain their roles; whether each merge, split and omission has a reason; whether the language keeps Method identity separate from body allocation; and whether a changed premise has an identifiable return. When the promised use spans several patterns, challenge at least the material relation on which that use depends. Broaden a check when the dependency boundary is unknown, not merely because the language is large.