C.32.ADA:7 - Conformance Checklist

Requirement	Required result
`CC-ADA-1`	Declared use and stop condition are written before evaluation.
`CC-ADA-2`	The evaluated decision relation and optional ADR projection are cited.
`CC-ADA-3`	Every coordinate is scored `0 absent` through `5 exceptionallyExpressedForDeclaredUse` or marked `notTriggered` with a grounded reason.
`CC-ADA-4`	Every value has adjacent-value rationale, not only a number.
`CC-ADA-5`	No coordinate values are averaged or converted into one global score.
`CC-ADA-6`	Weak coordinates name repair pattern refs and repair instructions.
`CC-ADA-7`	Evidence, assurance, gate, measurement, eval, publication, Method, Work, and pattern-quality claims remain distinct subject assertions and cite their exact defining or constraining ClaimGraphs.
`CC-ADA-8`	A project-local ADA record names both `projectWorkOccurrenceRef` and `architectureDecisionEvaluationProjectUseRelationRef`; the evaluated decision’s relation, the suffix, or either field alone asserts no locality.
`CC-ADA-9`	A local evaluator kind and a System-classification judgment use separate optional refs and neither requires an assignment. Actual evaluation first recovers the evaluator through A.13 and names independently admitted A.15.1 Work. Assignment species, occurrence, and F.6 refs are optional and appear only when the ADA record or receiving use expressly represents precise assignment-bound attribution; a missing or failed relation leaves the Work intact. An operation application and result episteme remain separate. Kind, classification, assignment, Work, attribution, responsibility, application, and result imply none of the others.
`CC-ADA-10`	Every evaluation binds one exact `U.ClaimScope`, relevant A.2.6 `U.ContextSlice` membership, effective reference scheme and plane, evaluation window, and input projection; the declared-use label and coordinate table do not replace them.