E.17.AUD.OOTD:7 - Conformance Checklist

Checklist scope. Use this checklist when checking a claimed application of this pattern, not as nine required authoring steps. The one- or two-sentence ordinary declaration remains a complete result; inspect only the rows implicated by the actual unit, transition, EntityOfConcern projection, neighboring claim, or unit-architecture choice, and do not publish a nine-row record by default.

1. CC-OOTD-1 - One publication unit is explicit. The publication unit under review is explicitly identifiable as one note, memo, sheet, screen, table, or section meant to be read as one unit.
2. CC-OOTD-2 - Primary subject is explicit. The unit states what it is mainly about in ordinary language rather than asking readers to infer it from tone.
3. CC-OOTD-3 - Any EntityOfConcern projection is exact and conditional. The unit uses EntityOfConcern only for the exact entity participant of one identified claim-bearing episteme under C.2.1; a topic, kind, question, or interpretation is never substituted for that participant.
4. CC-OOTD-4 - Concern, carried move, downstream use, and outside work are distinct. The unit states which question it foregrounds, what it asserts or communicates, how readers may use it, and which wider work, approval, execution, decision, or reliance remains outside.
5. CC-OOTD-5 - Any transition is typed and explicit. If subject, concern, claim or carried move, downstream use, or the exact entity participant changes, the unit names which change occurred rather than quietly absorbing all of them into one interpretation.
6. CC-OOTD-6 - Local vs publication-unit repair choice is honest. Apply E.17.AUD.LHR (Local Head Restoration) first when local repair is enough; apply this pattern only when publication-unit interpretation instability remains after local repair.
7. CC-OOTD-7 - Neighboring-pattern boundary is explicit. If an entityOfConcernRef-preserving transform, explanation, bridge, comparative-review, ontology, gate, approval, or execution claim becomes primary, use the neighboring pattern that defines or constrains that claim rather than pretending this pattern still carries the case.
8. CC-OOTD-8 - Claim-bearing lens is stated when needed. If a claim or downstream use materially depends on a minimal modeling lens, exact C.2.1 projection, or downstream-decision policy, state that lens, projection, or policy rather than silently assuming it.
9. CC-OOTD-9 - Unit architecture is the least-cost honest choice. Retaining one unit, declaring a transition, keeping a sectioned multi-subject unit, or splitting is chosen from the current reader, use, reuse, dependency, and overread costs. The author does not split to satisfy a count and does not retain a vague umbrella to avoid a necessary split.